Hey everyone,

 

I am trying to run the SMART extended self-test on a single disk in my array, but clicking the START button immediately changes it to STOP, then back to START again. It's like it's trying to start the test, fails, and then goes back to the starting position again. Disk 2 is showing some read errors, so I want to run the extended test to make sure it's not on the verge of failing

 

I can, however, run SMART short self-tests just fine.

 

Before clicking START:

 

 

After seeing STOP briefly, then back to START:

 

 

Here's the report of test results as well:

 

 

If I try to run what I think is the correct command from the CLI, I get the following:

 

root@ih-nas01:~# smartctl -d ata -tlong /dev/md2
smartctl 7.3 2022-02-28 r5338 [x86_64-linux-5.19.17-Unraid] (local build)
Copyright (C) 2002-22, Bruce Allen, Christian Franke, www.smartmontools.org

Read Device Identity failed: Inappropriate ioctl for device

If this is a USB connected device, look at the various --device=TYPE variants
A mandatory SMART command failed: exiting. To continue, add one or more '-T permissive' options.

 

I'm attaching the diagnostic/support bundle as well. Thank you in advance for any help you can provide!

ih-nas01-diagnostics-20231009-1201.zip

Edited October 9, 20232 yr by crescentwire
Added image showing test results

Try setting on of the Smart Controller Types in Main, Click on the Disk#, SMART Settings.

Hi @Squid, here are the settings I see in that drop-down menu:

 

 

I'm running SAS disks , so I would guess I want ATA. Are there any others you'd suggest I try here?

 

(FWIW, running that "smartctl" command with "-d ata" didn't work, so I'm hesitant to try that same option here.)

 

Either way, it sounds like the approach would be:

 

1. Set the controller type and apply changes.

2. Re-run the extended self-test to see what the results are.

3. Rinse and repeat previous two steps for other controller types.

 

Let me know if you think I should try any others. Thanks very much!

Edited October 9, 20232 yr by crescentwire
Formatting

GUI doesn't support SMART tests for SAS devices, you can run it manually:

 

smartctl -t long /dev/sdi

 

Thanks, @JorgeB, but running that command from the CLI gives me this error:

 

root@ih-nas01:~# smartctl -t long /dev/md2
smartctl 7.3 2022-02-28 r5338 [x86_64-linux-5.19.17-Unraid] (local build)
Copyright (C) 2002-22, Bruce Allen, Christian Franke, www.smartmontools.org

/dev/md2: Unable to detect device type
Please specify device type with the -d option.

Use smartctl -h to get a usage summary

 

And if I try to specify the device type (like ATA), I get this error:

 

root@ih-nas01:~# smartctl -d ata -t long /dev/md2
smartctl 7.3 2022-02-28 r5338 [x86_64-linux-5.19.17-Unraid] (local build)
Copyright (C) 2002-22, Bruce Allen, Christian Franke, www.smartmontools.org

Read Device Identity failed: Inappropriate ioctl for device

If this is a USB connected device, look at the various --device=TYPE variants
A mandatory SMART command failed: exiting. To continue, add one or more '-T permissive' options.

 

I can run through every single option listed under -d, but I'd love to know if there's one I should be using in particular.

 

(This is a Dell PowerEdge R520 server running with flashed PERC H310 RAID controller, to allow the OS direct access to each SAS drive.)

45 minutes ago, crescentwire said:

but running that command from the CLI gives me this error:

That's not what I typed, use the sdX device.

Here's what I see running "df -h":

 

root@ih-nas01:~# df -h
Filesystem      Size  Used Avail Use% Mounted on
rootfs           79G  1.1G   78G   2% /
tmpfs            32M  1.7M   31M   6% /run
/dev/sda1       7.3G  398M  6.9G   6% /boot
overlay          79G  1.1G   78G   2% /lib/firmware
overlay          79G  1.1G   78G   2% /lib/modules
devtmpfs        8.0M     0  8.0M   0% /dev
tmpfs            79G     0   79G   0% /dev/shm
cgroup_root     8.0M     0  8.0M   0% /sys/fs/cgroup
tmpfs           128M   39M   90M  31% /var/log
tmpfs           1.0M     0  1.0M   0% /mnt/disks
tmpfs           1.0M     0  1.0M   0% /mnt/remotes
tmpfs           1.0M     0  1.0M   0% /mnt/addons
tmpfs           1.0M     0  1.0M   0% /mnt/rootshare
/dev/md1        3.7T  2.8T  932G  76% /mnt/disk1
/dev/md2        3.7T  2.4T  1.4T  64% /mnt/disk2
/dev/md3        3.7T  2.0T  1.8T  53% /mnt/disk3
/dev/md4        3.7T  1.9T  1.9T  51% /mnt/disk4
/dev/sdh1       954G  737G  217G  78% /mnt/cache
shfs             15T  8.8T  5.8T  61% /mnt/user0
shfs             15T  8.8T  5.8T  61% /mnt/user
/dev/loop3      1.0G  6.3M  903M   1% /etc/libvirt
/dev/loop2       50G   16G   34G  33% /var/lib/docker

 

/dev/sdi doesn't exist in this list. But, if I run it anyway, here's what I get:

 

root@ih-nas01:~# smartctl -t long /dev/sdi
smartctl 7.3 2022-02-28 r5338 [x86_64-linux-5.19.17-Unraid] (local build)
Copyright (C) 2002-22, Bruce Allen, Christian Franke, www.smartmontools.org

Long (extended) offline self test failed [unsupported field in scsi command]

 

Sorry if this is super obvious to you and I'm just not getting it... but which device should I run the "smartctl" command on, please? "/dev/md2" represents the physical disk I'm trying to check for errors.

 

Thanks very much for your help on this.

Bump

On 10/9/2023 at 6:17 PM, crescentwire said:

/dev/sdi doesn't exist in this list

It's not on that list, it's what you see on main, e.g.:

 

 

 

On 10/9/2023 at 6:17 PM, crescentwire said:

[unsupported field in scsi command]

This looks like a device error, try a different disk, ideally from a different brand/model.

Here's what I see under Main:

 

 

With that in mind, "/dev/sdi" would be correct. Would you agree?

 

I don't have any other array disks in my server--these are all HGST 4 TB SAS drives. It sounds like I'm unable to run an extended SMART self-test with these drives. Whether that's a limitation of them being SAS or the exact make/model, I'm not sure. 

 

Are there any other options I have to assess the health of this disk, given the read errors I'm seeing?

Swap cables/slot with a different disk and run a parity check, if the errors follow the disk it's likely a disk problem.