jrhamilt Posted January 7, 2023 Share Posted January 7, 2023 All, When logging into my array this morning, I got a notification that one of my disks (disk 5) is disabled, and it's contents are being emulated. Diagnostics are attached. The smart report for the drive basically shows that the drive isn't there, so there's nothing there at the moment. Looks like the errors occurred early this morning, but there might have been earlier issues. I know rule number one with unraid is to post before you do anything, so I haven't rebooted or anything else. I can buy another drive to replace the one at issue. I also have enough space on the array that I could move the contents onto other drives pretty easily - but I know that once there is a failure, things can get interesting, so I want to ask for advice before I move. Thank you! Jan 7 06:10:58 WhiteNAS kernel: ata7: SATA link up 6.0 Gbps (SStatus 133 SControl 300) Jan 7 06:10:58 WhiteNAS kernel: ata7.00: configured for UDMA/133 Jan 7 06:10:58 WhiteNAS kernel: ata7: EH complete Jan 7 06:28:47 WhiteNAS kernel: md: disk5 read error, sector=557471976 Jan 7 06:28:47 WhiteNAS kernel: md: disk5 read error, sector=557471984 Jan 7 06:28:47 WhiteNAS kernel: md: disk5 read error, sector=557471992 Jan 7 06:28:47 WhiteNAS kernel: md: disk5 read error, sector=557472000 Jan 7 06:28:47 WhiteNAS kernel: md: disk5 read error, sector=557472008 Jan 7 06:28:47 WhiteNAS kernel: md: disk5 read error, sector=557472016 Jan 7 06:28:47 WhiteNAS kernel: md: disk5 read error, sector=557472024 Jan 7 06:28:47 WhiteNAS kernel: md: disk5 read error, sector=557472032 Jan 7 06:28:47 WhiteNAS kernel: md: disk5 read error, sector=557472040 Jan 7 06:28:47 WhiteNAS kernel: md: disk5 read error, sector=557472048 Jan 7 06:28:47 WhiteNAS kernel: md: disk5 read error, sector=557472056 Jan 7 06:28:47 WhiteNAS kernel: md: disk5 read error, sector=557472064 Jan 7 06:28:47 WhiteNAS kernel: md: disk5 read error, sector=557472072 Jan 7 06:28:47 WhiteNAS kernel: md: disk5 read error, sector=557472080 Jan 7 06:28:47 WhiteNAS kernel: md: disk5 read error, sector=557472088 Jan 7 06:28:47 WhiteNAS kernel: md: disk5 read error, sector=557472096 Jan 7 06:28:47 WhiteNAS kernel: md: disk5 read error, sector=557472104 Jan 7 06:28:47 WhiteNAS kernel: md: disk5 read error, sector=557472112 Jan 7 06:28:47 WhiteNAS kernel: md: disk5 read error, sector=557472120 Jan 7 06:28:47 WhiteNAS kernel: md: disk5 read error, sector=557472128 Jan 7 06:28:47 WhiteNAS kernel: md: disk5 read error, sector=557472136 Jan 7 06:28:47 WhiteNAS kernel: md: disk5 read error, sector=557472144 Jan 7 06:28:47 WhiteNAS kernel: md: disk5 read error, sector=557472152 Jan 7 06:28:47 WhiteNAS kernel: md: disk5 read error, sector=557472160 Jan 7 06:28:47 WhiteNAS kernel: md: disk5 read error, sector=557472168 Jan 7 06:28:47 WhiteNAS kernel: md: disk5 read error, sector=557472176 Jan 7 06:28:47 WhiteNAS kernel: md: disk5 read error, sector=557472184 Jan 7 06:28:47 WhiteNAS kernel: md: disk5 read error, sector=557472192 Jan 7 06:28:47 WhiteNAS kernel: md: disk5 read error, sector=557472200 Jan 7 06:28:47 WhiteNAS kernel: md: disk5 read error, sector=557472208 Jan 7 06:28:47 WhiteNAS kernel: md: disk5 read error, sector=557472216 Jan 7 06:28:47 WhiteNAS kernel: md: disk5 read error, sector=557472224 Jan 7 06:28:47 WhiteNAS kernel: md: disk5 write error, sector=557471976 Jan 7 06:28:47 WhiteNAS kernel: md: disk5 write error, sector=557471984 Jan 7 06:28:47 WhiteNAS kernel: md: disk5 write error, sector=557471992 Jan 7 06:28:47 WhiteNAS kernel: md: disk5 write error, sector=557472000 Jan 7 06:28:47 WhiteNAS kernel: md: disk5 write error, sector=557472008 Jan 7 06:28:47 WhiteNAS kernel: md: disk5 write error, sector=557472016 Jan 7 06:28:47 WhiteNAS kernel: md: disk5 write error, sector=557472024 Jan 7 06:28:47 WhiteNAS kernel: md: disk5 write error, sector=557472032 Jan 7 06:28:47 WhiteNAS kernel: md: disk5 write error, sector=557472040 Jan 7 06:28:47 WhiteNAS kernel: md: disk5 write error, sector=557472048 Jan 7 06:28:47 WhiteNAS kernel: md: disk5 write error, sector=557472056 Jan 7 06:28:47 WhiteNAS kernel: md: disk5 write error, sector=557472064 Jan 7 06:28:47 WhiteNAS kernel: md: disk5 write error, sector=557472072 Jan 7 06:28:47 WhiteNAS kernel: md: disk5 write error, sector=557472080 Jan 7 06:28:47 WhiteNAS kernel: md: disk5 write error, sector=557472088 Jan 7 06:28:47 WhiteNAS kernel: md: disk5 write error, sector=557472096 Jan 7 06:28:47 WhiteNAS kernel: md: disk5 write error, sector=557472104 Jan 7 06:28:47 WhiteNAS kernel: md: disk5 write error, sector=557472112 Jan 7 06:28:47 WhiteNAS kernel: md: disk5 write error, sector=557472120 Jan 7 06:28:47 WhiteNAS kernel: md: disk5 write error, sector=557472128 Jan 7 06:28:47 WhiteNAS kernel: md: disk5 write error, sector=557472136 Jan 7 06:28:47 WhiteNAS kernel: md: disk5 write error, sector=557472144 Jan 7 06:28:47 WhiteNAS kernel: md: disk5 write error, sector=557472152 Jan 7 06:28:47 WhiteNAS kernel: md: disk5 write error, sector=557472160 Jan 7 06:28:47 WhiteNAS kernel: md: disk5 write error, sector=557472168 Jan 7 06:28:47 WhiteNAS kernel: md: disk5 write error, sector=557472176 Jan 7 06:28:47 WhiteNAS kernel: md: disk5 write error, sector=557472184 Jan 7 06:28:47 WhiteNAS kernel: md: disk5 write error, sector=557472192 Jan 7 06:28:47 WhiteNAS kernel: md: disk5 write error, sector=557472200 Jan 7 06:28:47 WhiteNAS kernel: md: disk5 write error, sector=557472208 Jan 7 06:28:47 WhiteNAS kernel: md: disk5 write error, sector=557472216 Jan 7 06:28:47 WhiteNAS kernel: md: disk5 write error, sector=557472224 Jan 7 06:29:01 WhiteNAS sSMTP[2326]: Creating SSL connection to host Jan 7 06:29:01 WhiteNAS sSMTP[2326]: SSL connection using TLS_AES_256_GCM_SHA384 whitenas-diagnostics-20230107-0942.zip Quote Link to comment
JorgeB Posted January 8, 2023 Share Posted January 8, 2023 SMART look OK, very strange that there are no controller errors though, ATA7 issues logged a few minutes earlier are form a different disk and controller. Try swapping that disk to the onboard SATA and see if it happens again, then and if the emulated disk is mounting you can rebuild on top. Quote Link to comment
Solution jrhamilt Posted January 10, 2023 Author Solution Share Posted January 10, 2023 I followed the steps of rebooting the server, checking the SMART reports, and rebuilding on the drive found here: https://wiki.unraid.net/Manual/Storage_Management#Rebuilding_a_drive_onto_itself Everything seems to be working alright. No issues in the rebuild. Everything working fine. Looks like it was just a read hiccup... 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.