-
Disk in Error State - Unraid 6.11.5
I'm back. Thank you so much, it it looks like your advice fixed the issue. New diagnostic attached. Everything appears to be running well for the past 24hrs. Let me know what you think? Server-diagnostics 11-9-23.zip
-
Disk in Error State - Unraid 6.11.5
Sounds like a plan. I've startedthe rebuild and didn't put the array in Maintenance mode. I need to read some files from the server. Currently set to take around 20 hours. I'll report back when it's done. Thanks again for the guidance. I really appreciate it.
-
Disk in Error State - Unraid 6.11.5
Sorry for all the questions, but based on the info in the link you provided, would you recommend startin in Maintenance mode? Does the rebuild take the same time as a standard parity check?
-
Disk in Error State - Unraid 6.11.5
Thanks for this, Started the array. Diagnostics attached. The disk looks mounted and the contents look as they should from what i can tell. I'll look at the rebuild now. Should I have all my dockers shut down while doing this, or does it matter? Server-diagnostics-20230609-1535.zip
-
Disk in Error State - Unraid 6.11.5
Sorry, Should i have stared the array first? I set the array not to autostart - just to be on the safe side. Let me know if I need to start the array first and i can upload the diagnostics again.
-
Disk in Error State - Unraid 6.11.5
Thanks for the reply. I just got a chance to get up to the server today. After disconnecting and reconnecting the drive as you suggested, it's now showing in the main tab as disabled. SMART report for that drive and new diagnostics attached. Thanks for taking a look. server-smart-20230609-1423.zip server-diagnostics-20230609-1425.zip
-
skidmcmarx started following Disk in Error State - Unraid 6.11.5
-
Disk in Error State - Unraid 6.11.5
Hi there, I hope someone can help. Very worried at the moment. I logged into my server GUI for the first time in a few days (i must have turned notifications off at some point) and noticed one of my disks was disabled. It's hot here at the moment and this happend right after a successful parity check on the 1st/2nd of the month. Can I simply swap the drive out and resync parity? Like i would if i was adding a new drive. Like this post: Could i just reenable the drive to see if it works? Diagnostics attached for anyone who can help. Thanks in advance Server-diagnostics-20230608-1108.zip
skidmcmarx
Members
-
Joined
-
Last visited