Menu="Device:1" Title="$name _(Settings)_" Tag="hdd-o" --- 0 ? $sheets[$i-1] : $sheets[$end]; $next = $i<$end ? $sheets[$i+1] : $sheets[0]; ?> "> ">
_(Name)_: : _(Name)_: : _(Comments)_: : :help12 > This text will appear under the *Comments* column for the share in Windows Explorer. > Enter anything you like, up to 256 characters. :end _(Partition size)_: : KB (K=1024) _(Partition format)_: : _(Spinup group(s))_: : _(Spin down delay)_: : _(Warning disk temperature threshold)_ (°): : :help9 > *Warning disk temperature* sets the warning threshold for this hard disk temperature. Exceeding this threshold will result in a warning notification. > > A value of zero will disable the warning threshold (including notifications). :end _(Critical disk temperature threshold)_ (°): : :help10 > *Critical disk temperature* sets the critical threshold for this hard disk temperature. Exceeding this threshold will result in an alert notification. > > A value of zero will disable the critical threshold (including notifications). :end _(File system status)_: :   _(File system type)_: : :help11 > Enter the desired file system type. Changing the file system type of a device will permit you to reformat > that device using the new file system. Be aware that **all existing data on the device will be lost**. :end 1):?> _(File system type)_: : _(File system type)_: :   _(Minimum free space)_: : placeholder="0"> :help41 > This represents a "floor" of the amount of free space remaining on the cache disk. If the free > space becomes less than this value, then new files written to user shares with cache enabled will go to > the array and not the cache disk. > > Enter a numeric value with one of these suffixes: > > **KB** = 1,000
> **MB** = 1,000,000
> **GB** = 1,000,000,000
> **TB** = 1,000,000,000,000 > > If no suffix, a count of 1024-byte blocks is assumed.
> > Examples: > > **2GB** => 2,000,000,000 bytes
> **2000000** => 2,048,000,000 bytes :end _(Warning disk utilization threshold)_ (%): : :help13 > *Warning disk utilization* sets the warning threshold for this hard disk utilization. Exceeding this threshold will result in a warning notification. > > When the warning threshold is set equal or greater than the critical threshold, there will be only critical notifications (warnings are not existing). > > A value of zero will disable the warning threshold (including notifications). :end _(Critical disk utilization threshold)_ (%): : :help14 > *Critical disk utilization* sets the critical threshold for this hard disk utilization. Exceeding this threshold will result in an alert notification. > > A value of zero will disable the critical threshold (including notifications). :end   : >_(Unassign **ALL** devices to delete this pool)_
_(Balance Status)_
_(btrfs filesystem df)_: : ".shell_exec("/sbin/btrfs filesystem df /mnt/$tag").""?> _(btrfs balance status)_: : ".implode("\n", $balance_status).""?>   : 1):?> *_(Perform full balance)_* :help15 > **Balance** will run the *btrfs balance* program to restripe the extents across all pool devices, for example, > to convert the pool from raid1 to raid0 or vice-versa. > > When a *full balance* is perfomred, it basically rewrites everything in the current filesystem. > > A *mode conversion* affects the btrfs data extents; metadata always uses raid1 and is converted to raid1 if necessary by any balance operation. > > The run time is potentially very long, depending on the filesystem size and speed of the device. > > Unraid uses these default options when creating a multiple-device pool: > > `-dconvert=raid1 -mconvert=raid1` > > For more complete documentation, please refer to the btrfs-balance [Manpage](https://btrfs.wiki.kernel.org/index.php/Manpage/btrfs-balance) > > *Note: raid5 and raid6 are generally still considered **experimental** by the Linux community* :end   : :help16 > **Cancel** will cancel the balance operation in progress. :end   : "._('Balance')." "._('is only available when array is Started') : sprintf(_('See %s Settings'),ucfirst(prefix($tag)))?>
_(Scrub Status)_
_(btrfs scrub status)_: : ".implode("\n", $scrub_status).""?>   : :help17 > **Scrub** runs the *btrfs scrub* program which will read all data and metadata blocks from all > devices and verify checksums. > > If *Repair corrupted blocks* is checked, *btrfs scrub* will repair corrupted blocks if there’s a correct copy available. :end   : :help18 > **Cancel** will cancel the Scrub operation in progress. :end   : "._('Scrub')." "._('is only available when array is Started') : sprintf(_('See %s Settings'),ucfirst(prefix($tag)))?>
_(Check Filesystem Status)_
_(btrfs check status)_: : ".implode("\n", $check_status).""?>   : _(Options (see Help))_ :help19 > **Check** will run the *btrfs check* program to check file system integrity on the device. > > The *Options* field is initialized with *--readonly* which specifies check-only. If repair is needed, you should run > a second Check pass, setting the *Options* to *--repair*; this will permit *btrfs check* to fix the file system. > > After starting a Check, you should Refresh to monitor progress and status. Depending on > how large the file system is, and what errors might be present, the operation can take **a long time** to finish (hours). > Not much info is printed in the window, but you can verify the operation is running by observing the read/write counters > increasing for the device on the Main page. :end   : *_(Running)_* :help20 > **Cancel** will cancel the Check operation in progress. :end   : **_(Check)_** _(is only available when array is Started in **Maintenance** mode)_.   : .
_(Check Filesystem Status)_
_(reiserfsck status)_: : ".implode("\n", $check_status).""?>   : _(Options (see Help))_ :help21 > **Check** will run the *reiserfsck* program to check file system integrity on the device. > > The *Options* field may be filled in with specific options used to fix problems in the file system. Typically, you > first run a Check pass leaving *Options* blank. Upon completion, if *reiserfsck* finds any problems, you must > run a second Check pass, using a specific option as instructed by the first *reiserfsck* pass. > > After starting a Check you should Refresh to monitor progress and status. Depending on > how large the file system is, and what errors might be present, the operation can take **a long time** to finish (hours). > Not much info is printed in the window, but you can verify the operation is running by observing the read/write counters > increasing for the device on the Main page. :end   : *_(Running)_* :help22 > **Cancel** will cancel the Check operation in progress. :end   : **_(Check)_** _(is only available when array is Started in **Maintenance** mode)_.
_(Check Filesystem Status)_
_(xfs_repair status)_: : ".implode("\n", $check_status).""?>   : _(Options (see Help))_ :help23 > **Check** will run the *xfs_repair* program to check file system integrity on the device. > > The *Options* field is initialized with *-n* which specifies check-only. If repair is needed, you should run > a second Check pass, setting the *Options* blank; this will permit *xfs_repair* to fix the file system. > > After starting a Check, you should Refresh to monitor progress and status. Depending on > how large the file system is, and what errors might be present, the operation can take **a long time** to finish (hours). > Not much info is printed in the window, but you can verify the operation is running by observing the read/write counters > increasing for the device on the Main page. :end   : *_(Running)_* :help24 > **Cancel** will cancel the Check operation in progress. :end   : **_(Check)_** _(is only available when array is Started in **Maintenance** mode)_.
_(SMART Settings)_
_(SMART notification value)_: : :help25 > SMART notifications are generated on either an increasing RAW value of the attribute, or a decreasing NORMALIZED value which reaches a predefined threshold set by the manufacturer. > > Each disk may have its own specific setting overruling the 'default' setting (see global SMART settings under Disk Settings). :end _(SMART notification tolerance level)_: : :help26 > A tolerance level may be given to prevent that small changes result in a notification. Setting a too high tolerance level may result in critical changes without a notification. > > Each disk may have its own specific setting overruling the 'default' setting (see global SMART settings under Disk Settings). :end _(SMART controller type)_: : /dev/ enter disk index and device name as applicable to your controller :help27 > By default automatic controller selection is done by smartctl to read the SMART information. Certain controllers however need specific settings for smartctl to work. > Use this setting to select your controller type and fill-in the specific disk index and device name for your situation. Use the manufacturer's documentation to find the relevant information. > > Each disk may have its own specific setting overruling the 'default' setting (see global SMART settings under Disk Settings). :end _(SMART attribute notifications)_: : _(Custom attributes (use comma to separate numbers))_   : >_(Attribute)_ = :help28 > The user can enable or disable notifications for the given SMART attributes. It is recommended to keep the default, which is ALL selected attributes, > when certain attributes are not present on your hard disk or do not provide the correct information, these may be excluded. > In addition custom SMART attributes can be entered to generate notifications. Be careful in this selection, > it may cause an avalance of notifcations if inappropriate SMART attributes are chosen. > > Each disk may have its own specific setting overruling the 'default' setting (see global SMART settings under Disk Settings). :end :