Menu="Device:1" Title="$name Settings" Tag="hdd-o" --- 0 ? $sheets[$i-1] : $sheets[$end]; $next = $i<$end ? $sheets[$i+1] : $sheets[0]; ?>
Name: : Partition size: : KB (K=1024) Partition format: : Spinup group(s): : Spin down delay: : Warning disk temperature threshold (°): : > *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). Critical disk temperature threshold (°): : > *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). File system status: :   File system type: : > 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**. 1):?> File system type: : File system type: :   Comments: : > This text will appear under the *Comments* column for the share in Windows Explorer. > Enter anything you like, up to 256 characters. Warning disk utilization threshold (%): : > *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). Critical disk utilization threshold (%): : > *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).   :
Balance Status
btrfs filesystem df: : ".shell_exec("/sbin/btrfs filesystem df /mnt/{$disk['name']}")."";?> btrfs balance status: : " . implode("\n", $balance_status) . "";?>   : Options (see Help) > **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. > > Without any options specified a "full balance" is performed which will basically rewrite everything in the filesystem. > The run time is potentially very long, depending on the filesystem size. > > 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).   : *Running* > **Cancel** will cancel the balance operation in progress.   : Balance is only available when array is Started." : "See Cache Settings."?>
Scrub Status
btrfs scrub status: : " . implode("\n", $scrub_status) . "";?>   : > **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.   : *Running* > **Cancel** will cancel the Scrub operation in progress.   : Scrub is only available when array is Started." : "See Cache Settings."?>
Check Filesystem Status
btrfs check status: : " . implode("\n", $check_status) . "";?>   : Options (see Help) > **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.   : *Running* > **Cancel** will cancel the Check operation in progress.   : **Check** is only available when array is Started in **Maintenance** mode.   : See Cache Settings.
Check Filesystem Status
reiserfsck status: : " . implode("\n", $check_status) . "";?>   : Options (see Help) > **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.   : *Running* > **Cancel** will cancel the Check operation in progress.   : **Check** is only available when array is Started in **Maintenance** mode.
Check Filesystem Status
xfs_repair status: : " . implode("\n", $check_status) . "";?>   : Options (see Help) > **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.   : *Running* > **Cancel** will cancel the Check operation in progress.   : **Check** is only available when array is Started in **Maintenance** mode.
SMART Settings
SMART notification value: : > 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). SMART notification tolerance level: : > 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). SMART controller type: : /dev/ enter disk index and device name as applicable to your controller > 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). SMART attribute notifications: : Custom attributes (use comma to separate numbers)   : >Attribute = > 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). :