wes.crockett Posted July 6, 2021 Share Posted July 6, 2021 Hello all, I have 5 3tb disks with 2 additional as parity. While away, we had a power outage which brought the system down. Got home today and brought the array back online. Now getting a red X on the disk1 showing 'Device is Disabled, contents emulating... click to spin down device.' I cannot access any SMART data and it doesn't do anything when I hit to test. Here are snippets from the log: Jul 3 15:12:14 Kuiper kernel: mdcmd (2): import 1 sdh 64 2930266532 0 Hitachi_HUS724030ALE641_P8GUXJYP Jul 3 15:12:14 Kuiper kernel: md: import disk1: (sdh) Hitachi_HUS724030ALE641_P8GUXJYP size: 2930266532 Jul 5 14:36:47 Kuiper kernel: blk_update_request: I/O error, dev sdh, sector 0 op 0x1:(WRITE) flags 0x800 phys_seg 0 prio class 0 Jul 5 14:36:47 Kuiper kernel: blk_update_request: I/O error, dev sdh, sector 3820608 op 0x0:(READ) flags 0x0 phys_seg 128 prio class 0 Jul 5 14:36:47 Kuiper kernel: md: disk1 read error, sector=3820544 Jul 5 14:36:47 Kuiper kernel: md: disk1 read error, sector=3820552 Jul 5 14:36:47 Kuiper kernel: md: disk1 read error, sector=3820560 Jul 5 14:36:47 Kuiper kernel: md: disk1 read error, sector=3820568 Jul 5 14:36:47 Kuiper kernel: md: disk1 read error, sector=3820576 Jul 5 14:36:47 Kuiper kernel: md: disk1 read error, sector=3820584 Jul 5 14:36:47 Kuiper kernel: md: disk1 read error, sector=3820592 Jul 5 14:36:47 Kuiper kernel: md: disk1 read error, sector=3820600 Jul 5 14:36:47 Kuiper kernel: md: disk1 read error, sector=3820608 Jul 5 14:36:47 Kuiper kernel: md: disk1 read error, sector=3820616 Jul 5 14:36:47 Kuiper kernel: md: disk1 read error, sector=3820624 Jul 5 14:36:47 Kuiper kernel: md: disk1 read error, sector=3820632 Jul 5 14:36:47 Kuiper kernel: md: disk1 read error, sector=3820640 Jul 5 14:36:47 Kuiper kernel: md: disk1 read error, sector=3820648 Jul 5 14:36:47 Kuiper kernel: md: disk1 read error, sector=3820656 Jul 5 14:36:47 Kuiper kernel: blk_update_request: I/O error, dev sdh, sector 3821632 op 0x0:(READ) flags 0x0 phys_seg 128 prio class 0 Jul 5 14:36:47 Kuiper kernel: md: disk1 read error, sector=3821568 Jul 5 14:36:47 Kuiper kernel: md: disk1 read error, sector=3821576 Jul 5 14:36:47 Kuiper kernel: md: disk1 read error, sector=3821584 Jul 5 14:36:47 Kuiper kernel: md: disk1 read error, sector=3821592 Jul 5 14:36:47 Kuiper kernel: md: disk1 read error, sector=3821600 Jul 5 14:36:47 Kuiper kernel: md: disk1 read error, sector=3821608 Jul 5 14:36:47 Kuiper kernel: md: disk1 read error, sector=3821616 Jul 5 14:36:47 Kuiper kernel: md: disk1 read error, sector=3821624 Jul 5 14:36:47 Kuiper kernel: md: disk1 read error, sector=3821632 Jul 5 14:44:00 Kuiper root: Fix Common Problems Version 2021.05.03 Jul 5 14:44:01 Kuiper root: Fix Common Problems: Error: disk1 (Hitachi_HUS724030ALE641_P8GUXJYP) is disabled Jul 5 14:44:01 Kuiper root: Fix Common Problems: Error: disk1 (Hitachi_HUS724030ALE641_P8GUXJYP) has read errors Jul 5 22:02:53 Kuiper unassigned.devices: Error: shell_exec(/usr/sbin/smartctl -n standby -A /dev/sdi | /bin/awk 'BEGIN{t='*'} =='Temperature:'{t=;exit};==190||==194{t=0;exit} END{print t}') took longer than 10s! Jul 5 22:02:53 Kuiper unassigned.devices: Error: shell_exec(/usr/sbin/smartctl -n standby -A /dev/sdi | /bin/awk 'BEGIN{t='*'} =='Temperature:'{t=;exit};==190||==194{t=0;exit} END{print t}') took longer than 10s! Jul 5 22:02:57 Kuiper unassigned.devices: Error: shell_exec(/usr/sbin/smartctl -n standby -A /dev/sdi | /bin/awk 'BEGIN{t='*'} =='Temperature:'{t=;exit};==190||==194{t=0;exit} END{print t}') took longer than 10s! Jul 5 22:02:57 Kuiper unassigned.devices: Error: shell_exec(/usr/sbin/smartctl -n standby -A /dev/sdi | /bin/awk 'BEGIN{t='*'} =='Temperature:'{t=;exit};==190||==194{t=0;exit} END{print t}') took longer than 10s! I have attached the syslog and smart report. I assume the drive is toast? I have ordered a new one already, but want to make sure I understand what is wrong too... Just in case it may not be the drive. Any ideas? anything I need to try? We are headed back out for the week tomorrow... I may take the system offline for that time just in case there are more power outages. Also... Will be getting a UPS for this system. kuiper-syslog-20210706-0554.zip kuiper-smart-20210705-2214.zip Quote Link to comment
JorgeB Posted July 6, 2021 Share Posted July 6, 2021 Next time please post the complete diagnostics instead, disk dropped offline and reconnect with a different letter, post output of: smartctl -x /dev/sdi 1 Quote Link to comment
wes.crockett Posted July 6, 2021 Author Share Posted July 6, 2021 Thanks Jorge. Sorry about not posting the complete diagnostics. I do see 1 unassigned device as you said (that I didn't notice last night). How do I tell it to put that disk back as SDH? smartctl output.txt Quote Link to comment
JorgeB Posted July 6, 2021 Share Posted July 6, 2021 Disk look mostly OK, still not a bad idea to run an extended SMART test before using it again, if it passes and only if the emulated disk is mounting correctly you should replace/swap cables to rule that out then can rebuild on top: https://wiki.unraid.net/Manual/Storage_Management#Rebuilding_a_drive_onto_itself 1 Quote Link to comment
wes.crockett Posted July 6, 2021 Author Share Posted July 6, 2021 Awesome! I couldn't get SMART data to show up or run until I unassigned the disk. It shows 100 reallocated sectors, so replacing it is probably a good idea anyways. As far as connections, all drives connect to a backplane, so there isn't a single cable going to each disk. I'm running an extended SMART test now. Thanks for your help! Quote Link to comment
Recommended Posts
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.