TekWarfare Posted March 16, 2023 Share Posted March 16, 2023 (edited) Just received the following two e-mail notifications: Event: Unraid Disk 1 error Subject: Alert [BIGBOX] - Disk 1 in error state (disk dsbl) Description: WDC_WD120EDAZ-11F3RA0_5PG85VEF (sdd) Importance: alert Event: Unraid array errors Subject: Warning [BIGBOX] - array has errors Description: Array has 1 disk with read errors Importance: warning Disk 1 - WDC_WD120EDAZ-11F3RA0_5PG85VEF (sdd) (errors 9) I've re-named my server to BIGBOX in the e-mails so I'm not publicly declaring my server name. My understanding is that this is likely (and hopefully) a power or SATA cable issue. As such, I've attached the diagnostics file now before doing anything. Question 1: Am I correct in doing the following?: A. Shutdown server B. Replace SATA and/or Power cable - even reseating SATA cable in different SATA port C. Power on server D. Follow the instructions here: https://wiki.unraid.net/Manual/Storage_Management#Rebuilding_a_drive_onto_itself Question 2: Following the rebuild steps, the preamble states "There can be cases where it is determined that the reason a disk was disabled is due to an external factor and the disk drive appears to be fine." How do I determine the disk is "fine"? That it shows up under Main after a reboot? Question 3: I'm running an expired trial, and I believe Unraid won't allow me to start the array after a reboot. Is there any way around this for the time being? DISK 1 primarily stores TV shows. I've checked nearly 10 shows at random at various seasons and episodes and they all playback perfectly. Question 4: Is this data being inferred on-the-fly by the difference between the remaining Parity and Data disks? Quote If a drive is being emulated then you can carry out recovery actions on the emulated drive before starting the rebuild process. Question 5: Accordingly, am I fine to copy a few important files and folders over SMB? (I am aware of having backup plans) I greatly appreciate any help in the matter. BIGBOX-diagnostics-20230316-1448.zip Edited March 16, 2023 by TekWarfare Quote Link to comment
JorgeB Posted March 16, 2023 Share Posted March 16, 2023 Disk1 dropped offline, this is usually a power/connection issue but since it dropped there's no SMART, you'd need to check/replace cables then post new diags after array start, but 33 minutes ago, TekWarfare said: I'm running an expired trial this will a problem. Quote Link to comment
TekWarfare Posted March 16, 2023 Author Share Posted March 16, 2023 Ran a SMART short self-test and attached the SMART report. Also included new diagnostics file after reboot, but not array start BIGBOX-diagnostics-20230316-2049.zip BIGBOX-smart-20230316-2047.zip Quote Link to comment
TekWarfare Posted March 16, 2023 Author Share Posted March 16, 2023 Attached diagnostics after array start - bought the licence BIGBOX-diagnostics-20230316-2100.zip Quote Link to comment
Solution JorgeB Posted March 17, 2023 Solution Share Posted March 17, 2023 SMART looks fine, there's a recent UDMA CRC error, so the issue was likely caused by a bad SATA cable, replace that cable and since the emulated disk is mounting and assuming contents look correct you can rebuild on top: https://wiki.unraid.net/Manual/Storage_Management#Rebuilding_a_drive_onto_itself 1 Quote Link to comment
TekWarfare Posted March 17, 2023 Author Share Posted March 17, 2023 Thank you for the guidance, JorgeB. I left the array started overnight - not performed any of the rebuilding steps yet - and now Parity disk has increased UDMA CRC errors from 6 (before shutdown in OP) to 10 (now). It's the exact same cable as the one used by DISK 1 so looks like they've both gone funny at the same time, or I've accidentally knocked PARITY's SATA cable when re-doing DISK 1's. I'm going to shutdown the server and give PARITY a new cable too. Then I'll perform a SMART shot self-test and post the results I guess. Quote Link to comment
TekWarfare Posted March 17, 2023 Author Share Posted March 17, 2023 Replaced the SATA cable to PARITY now. Ran SMART short self-test on all disks, but had to reboot due to "Array Stopped Stale Configuration" bug in Firefox. Rebooted and used Edge. Diagnostics after starting array attached. BIGBOX-diagnostics-20230317-1917.zip Quote Link to comment
JorgeB Posted March 17, 2023 Share Posted March 17, 2023 If the emulated disk is still mounting you can rebuild. Quote Link to comment
TekWarfare Posted March 20, 2023 Author Share Posted March 20, 2023 On 3/17/2023 at 7:32 PM, JorgeB said: If the emulated disk is still mounting you can rebuild. Rebuild finished successfully. I was confused as to why I couldn't connect to mapped network drives afterwards, but soon realized it was because I started the array in maintenance mode. Thank you for the help, JorgeB. 🙂 Is it fine to remove the offending disk from Historical Devices? Same with the cache drive in the attached picture. There's no point keeping either any more is there? Quote Link to comment
JorgeB Posted March 20, 2023 Share Posted March 20, 2023 9 hours ago, TekWarfare said: Is it fine to remove the offending disk from Historical Devices? Yes, that's from the UD plugin. 1 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.