September 15, 20223 yr Just now I received a pushbullet notification for an error with a particular drive. I haven't done anything, didn't reboot nothing as I'm coming here to ask what should I do and since some logs disappear after I reboot I've done nothing so far. Here's the log I got: Sep 1 15:05:44 Tower kernel: sd 5:0:0:0: [sdf] 15628053168 512-byte logical blocks: (8.00 TB/7.28 TiB) Sep 1 15:05:44 Tower kernel: sd 5:0:0:0: [sdf] 4096-byte physical blocks Sep 1 15:05:44 Tower kernel: sd 5:0:0:0: [sdf] Write Protect is off Sep 1 15:05:44 Tower kernel: sd 5:0:0:0: [sdf] Mode Sense: 00 3a 00 00 Sep 1 15:05:44 Tower kernel: sd 5:0:0:0: [sdf] Write cache: enabled, read cache: enabled, doesn't support DPO or FUA Sep 1 15:05:44 Tower kernel: sdf: sdf1 Sep 1 15:05:44 Tower kernel: sd 5:0:0:0: [sdf] Attached SCSI disk Sep 1 15:06:15 Tower emhttpd: ST8000DM004-2CX188_ZCT128DJ (sdf) 512 15628053168 Sep 1 15:06:15 Tower kernel: mdcmd (5): import 4 sdf 64 7814026532 0 ST8000DM004-2CX188_ZCT128DJ Sep 1 15:06:15 Tower kernel: md: import disk4: (sdf) ST8000DM004-2CX188_ZCT128DJ size: 7814026532 Sep 1 15:06:15 Tower emhttpd: read SMART /dev/sdf Sep 1 15:10:02 Tower emhttpd: shcmd (259): echo 128 > /sys/block/sdf/queue/nr_requests Sep 4 13:18:47 Tower emhttpd: shcmd (8734): echo 128 > /sys/block/sdf/queue/nr_requests Sep 4 13:19:18 Tower emhttpd: shcmd (8772): echo 128 > /sys/block/sdf/queue/nr_requests Sep 4 13:19:24 Tower emhttpd: shcmd (8789): echo 128 > /sys/block/sdf/queue/nr_requests Sep 4 13:19:28 Tower emhttpd: shcmd (8810): echo 128 > /sys/block/sdf/queue/nr_requests Sep 4 13:19:36 Tower emhttpd: shcmd (8840): echo 128 > /sys/block/sdf/queue/nr_requests Sep 4 13:19:36 Tower emhttpd: spinning down /dev/sdf Sep 4 13:19:42 Tower emhttpd: shcmd (8876): echo 128 > /sys/block/sdf/queue/nr_requests Sep 4 13:19:51 Tower emhttpd: shcmd (8924): echo 128 > /sys/block/sdf/queue/nr_requests Sep 7 09:28:49 Tower emhttpd: read SMART /dev/sdf Sep 7 18:28:50 Tower emhttpd: spinning down /dev/sdf Sep 10 09:57:19 Tower emhttpd: read SMART /dev/sdf Sep 10 20:47:15 Tower emhttpd: spinning down /dev/sdf Sep 12 10:44:08 Tower emhttpd: read SMART /dev/sdf Sep 13 03:43:08 Tower emhttpd: spinning down /dev/sdf Sep 13 11:16:35 Tower emhttpd: read SMART /dev/sdf Sep 13 20:17:37 Tower emhttpd: spinning down /dev/sdf Sep 14 11:15:44 Tower emhttpd: read SMART /dev/sdf Sep 14 19:18:15 Tower kernel: sd 5:0:0:0: [sdf] Synchronizing SCSI cache Sep 14 19:18:49 Tower kernel: sd 5:0:0:0: [sdf] Synchronize Cache(10) failed: Result: hostbyte=0x04 driverbyte=DRIVER_OK Sep 14 19:18:49 Tower kernel: sd 5:0:0:0: [sdf] Stopping disk Sep 14 19:18:49 Tower kernel: sd 5:0:0:0: [sdf] Start/Stop Unit failed: Result: hostbyte=0x04 driverbyte=DRIVER_OK Is the drive dead? Replace? I can't access any SMART data because the drive is offline. Drive is connected using SATA, as I've googled some questions with this error on the forum and it was related to USB. So, what do I do?
September 15, 20223 yr Community Expert 52 minutes ago, TheFreemancer said: what do I do? attach diagnostics to your NEXT post in this thread
September 15, 20223 yr Author tower-smart-20220915-1037.zip tower-diagnostics-20220915-1039.zip I've rebooted the server and the drive wasn't showing up. I replaced the SATA cable and it showed up again but good 15 UDMC errors, I remember this drive had UDMC errors before. The drive is showing up again but still disabled. There's an option I never seen before "Read-check", I'm starting it as I don't think it will hurt, if I shouldn't do it I'll stop it. EDIT: I remember something similar when a drive got disabled and the solution was to rebuild on top of that particular drive. But this is dangerous because if it starts to rebuild and the drive actually fails, all data is gone if I remember correctly. Tbh, I don't remember how to do this and I'm not sure if this is the right thing to do. Edited September 15, 20223 yr by TheFreemancer
September 15, 20223 yr Author 2 minutes ago, JorgeB said: Do you have the diags before rebooting? Yes I have tower-diagnostics-20220915-1009.zip Edited September 15, 20223 yr by TheFreemancer
September 15, 20223 yr Community Expert It does look like it was a SATA cable problem, emulated disk is mounting, assuming contents look correct you can rebuild on top.
September 15, 20223 yr Author Just now, JorgeB said: It does look like it was a SATA cable problem, emulated disk is mounting, assuming contents look correct you can rebuild on top. How do I do it? When rebooting the server I can assign the disk to the same slot but it is still disabled. Do I have to start it once with the slot disk set to none, reboot and assign the disk to that same slot again? Also when I set the disk4 slot to none the drive shows up as unsassigned device. Can the unassigned devices plugin do any harm to the files?
September 15, 20223 yr Community Expert Solution https://wiki.unraid.net/Manual/Storage_Management#Rebuilding_a_drive_onto_itself
September 15, 20223 yr Author Ok It's rebuilding now. Thanks for the help, hopefully everything goes well.
September 15, 20223 yr Community Expert 2 hours ago, TheFreemancer said: dangerous because if it starts to rebuild and the drive actually fails, all data is gone if I remember correctly If the drive actually fails, it is still emulated by other disks in the array and can still be rebuilt to another drive. There are other reasons why it might be a good idea to rebuild to a spare though. If the emulated drive is unmountable, for example.
September 15, 20223 yr Author So far so good. If the drive indeed fails, I can get another one and start rebuilding again, right?
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.