March 30, 20251 yr I woke up today to a disabled unraid disk, however, after running an extended SMART test, I see that it is passed. Can someone help take a look at the Unraid diagnostics report in case I'm missing something? Not sure what to check for and if this is an issue. I assume that if everything is good, then I can rebuild the drive with these steps - https://docs.unraid.net/unraid-os/manual/storage-management/#rebuilding-a-drive-onto-itself prodesk-diagnostics-20250330-1854.zip prodesk-smart-20250330-1734.zip
March 30, 20251 yr Community Expert Solution Mar 24 03:01:02 Prodesk kernel: sd 9:0:0:0: attempting task abort!scmd(0x00000000bb3cabf6), outstanding for 15349 ms & timeout 15000 ms Mar 24 03:01:02 Prodesk kernel: sd 9:0:0:0: [sde] tag#854 CDB: opcode=0x85 85 06 20 00 00 00 00 00 00 00 00 00 00 40 e5 00 Mar 24 03:01:02 Prodesk kernel: scsi target9:0:0: handle(0x0009), sas_address(0x4433221100000000), phy(0) Mar 24 03:01:02 Prodesk kernel: scsi target9:0:0: enclosure logical id(0x5c81f660f54f7000), slot(3) Mar 24 03:01:06 Prodesk kernel: sd 9:0:0:0: task abort: SUCCESS scmd(0x00000000bb3cabf6) Mar 24 03:01:06 Prodesk kernel: sd 9:0:0:0: [sde] tag#867 UNKNOWN(0x2003) Result: hostbyte=0x00 driverbyte=DRIVER_OK cmd_age=19s Mar 24 03:01:06 Prodesk kernel: sd 9:0:0:0: [sde] tag#867 Sense Key : 0x2 [current] Mar 24 03:01:06 Prodesk kernel: sd 9:0:0:0: [sde] tag#867 ASC=0x4 ASCQ=0x0 Mar 24 03:01:06 Prodesk kernel: sd 9:0:0:0: [sde] tag#867 CDB: opcode=0x8a 8a 08 00 00 00 04 00 15 c3 68 00 00 00 08 00 00 Mar 24 03:01:06 Prodesk kernel: I/O error, dev sde, sector 17181295464 op 0x1:(WRITE) flags 0x20800 phys_seg 1 prio class 0 Mar 24 03:01:06 Prodesk kernel: md: disk4 write error, sector=17181295400 Several days since it became disabled, and of course, no further attempts to access a disabled disk. Looks like a problem communicating with the disk, cable connection, etc. Filesystem Size Used Avail Use% Mounted on /dev/md4p1 17T 9.7T 6.7T 60% /mnt/disk4 emulated disk4 is mounted 46 minutes ago, frosty_hedgehog said: I assume that if everything is good, then I can rebuild the drive with these steps - https://docs.unraid.net/unraid-os/manual/storage-management/#rebuilding-a-drive-onto-itself After checking/fixing connection, etc.
March 30, 20251 yr Community Expert 48 minutes ago, frosty_hedgehog said: woke up today to a disabled unraid disk 1 minute ago, trurl said: Several days since it became disabled Do you have Notifications setup to alert you immediately by email or other agent as soon as a problem is detected?
March 30, 20251 yr Community Expert Mar 30 04:30:02 Prodesk root: Fix Common Problems: Error: disk4 (ST18000NM002J-2TV133_ZR5A3FY7) is disabled Mar 30 04:30:02 Prodesk root: Fix Common Problems: Error: disk2 (ST18000NM002J-2TV133_ZR576ENL) has read errors Mar 30 04:30:02 Prodesk root: Fix Common Problems: Error: disk4 (ST18000NM002J-2TV133_ZR5A3FY7) has read errors ** Ignored Mar 30 04:30:02 Prodesk root: Fix Common Problems: Warning: Deprecated plugin ca.mover.tuning.plg You should not tell FCP to ignore read errors. Your mover tuning is way out-of-date.
March 30, 20251 yr Community Expert Mar 10 03:00:16 Prodesk kernel: sd 9:0:4:0: attempting task abort!scmd(0x00000000dc1544ca), outstanding for 15279 ms & timeout 15000 ms Mar 10 03:00:16 Prodesk kernel: sd 9:0:4:0: [sdi] tag#98 CDB: opcode=0x85 85 06 20 00 00 00 00 00 00 00 00 00 00 40 e5 00 Mar 10 03:00:16 Prodesk kernel: scsi target9:0:4: handle(0x000d), sas_address(0x4433221107000000), phy(7) Mar 10 03:00:16 Prodesk kernel: scsi target9:0:4: enclosure logical id(0x5c81f660f54f7000), slot(4) Mar 10 03:00:20 Prodesk kernel: sd 9:0:4:0: task abort: SUCCESS scmd(0x00000000dc1544ca) Mar 10 03:00:20 Prodesk kernel: sd 9:0:4:0: [sdi] tag#70 UNKNOWN(0x2003) Result: hostbyte=0x00 driverbyte=DRIVER_OK cmd_age=19s Mar 10 03:00:20 Prodesk kernel: sd 9:0:4:0: [sdi] tag#70 Sense Key : 0x2 [current] Mar 10 03:00:20 Prodesk kernel: sd 9:0:4:0: [sdi] tag#70 ASC=0x4 ASCQ=0x0 Mar 10 03:00:20 Prodesk kernel: sd 9:0:4:0: [sdi] tag#70 CDB: opcode=0x88 88 00 00 00 00 03 00 02 33 40 00 00 00 08 00 00 Mar 10 03:00:20 Prodesk kernel: I/O error, dev sdi, sector 12885046080 op 0x0:(READ) flags 0x0 phys_seg 1 prio class 0 Mar 10 03:00:20 Prodesk kernel: md: disk2 read error, sector=12885046016 Similar for disk2 nearly 3 weeks ago but no write error so not disabled. Seemed OK after that.
March 31, 20251 yr Community Expert Disks 2, 4 are on the same controller [9:0:0:0] disk ATA ST18000NM002J-2T PAL7 /dev/sde /dev/sg4 state=running queue_depth=32 scsi_level=7 type=0 device_blocked=0 timeout=30 dir: /sys/bus/scsi/devices/9:0:0:0 [/sys/devices/pci0000:00/0000:00:1b.4/0000:05:00.0/host9/port-9:0/end_device-9:0/target9:0:0/9:0:0:0] [9:0:4:0] disk ATA ST18000NM002J-2T PAL7 /dev/sdi /dev/sg8 state=running queue_depth=32 scsi_level=7 type=0 device_blocked=0 timeout=30 dir: /sys/bus/scsi/devices/9:0:4:0 [/sys/devices/pci0000:00/0000:00:1b.4/0000:05:00.0/host9/port-9:4/end_device-9:4/target9:0:4/9:0:4:0] 05:00.0 Serial Attached SCSI controller [0107]: Broadcom / LSI SAS2008 PCI-Express Fusion-MPT SAS-2 [Falcon] [1000:0072] (rev 03) Subsystem: Dell 6Gbps SAS HBA Adapter [1028:1f1c] Kernel driver in use: mpt3sas Kernel modules: mpt3sas
March 31, 20251 yr Author Thanks for taking a look! Based on what you've suggested I'll double check the cable connection and also reseat the HBA adapter. There are a few drives connected to it so I'm not sure if that'll be the root cause, no harm tyring I also just noticed my mover tuner is stuck on 2023.12.19, updating it doesn't work, will reinstall the masterwishx version per FCP recommendation I don't believe I have notifications setup right now, I'll look into that immediately. I only have this for backups failing Not sure why I ignored that FCP read error message but I'll fix that now. Will report back once this is all done and I recheck the system
March 31, 20251 yr Community Expert 1 hour ago, trurl said: Disks 2, 4 are on the same controller Does this controller get enough airflow?
March 31, 20251 yr Author Yes, the controller has a Noctua fan ziptied to it and has been that way for a few years now. I have checked in the past to make sure it doesn't get too hot when running and it seemed fine (just by feeling the heatsink during operations, didn't feel too hot to touch) After reseating the cables, the drive shows up as "not installed" but is now in unassigned disks. I'm assuming I can simply reassign it and it'll rebuild? For some reason, I had a second 4TB unassigned drive (ST4000LM024-2AN17V) suddenly become unavailable as well, no prior errors, separate SATA controller (connected to the MB) and separate SATA power line to the PSU. I'm quite confused on what happened there. Reconnecting the drive doesn't bring it back up. I'm going to try connecting externally to see if it shows up on my PC prodesk-diagnostics-20250331-0939.zip
March 31, 20251 yr Community Expert 7 minutes ago, frosty_hedgehog said: I can simply reassign it and it'll rebuild? yes
Join the conversation
You can post now and register later. If you have an account, sign in now to post with your account.
Note: Your post will require moderator approval before it will be visible.