Hopefully someone can help me here. There's maybe an easy solution.

 

I have 6 drives, 1 being parity. I get a drive error and Unraid disables one of my drives. That's weird I think, so I do a short smart test and there's no issues. I decide to shut down the server, check all the cables are fully seated (which they are). I restart the server. The drive still shows as disabled with no option to enable it. I also can't seem to get any explanation of what this error is. I then stupidly do the following. Stopped the array, unassigned the problem drive, started the array, then stopped it and now trying to reassign the problem drive. Unraid now tells me this drive will be wiped. Oh... shit. Of course, it now no longer trusts this drive. That makes sense, but there's surely a way for me to re-insert this drive as if nothing had happened?

I know there may still be an issue with the drive, but I haven't even tried swapping cables out yet until I can get this configuration back to how it was! What am I missing?

Edited May 7, 20251 yr by Tag

2 minutes ago, Tag said:

Stopped the array, unassigned the problem drive, started the array, then stopped it and now trying to reassign the problem drive.

That is exactly the method for rebuilding onto the same disk.

 

https://docs.unraid.net/unraid-os/manual/storage-management/#rebuilding-a-drive-onto-itself

 

Which is probably what you need to do.

 

If you are hesitant to proceed without more detailed advice, just don't reassign the drive.

 

Then start the array in normal (not maintenance) mode and...

 

Attach Diagnostics ZIP to your NEXT post in this thread.

Diagnostics attached. 

 

The array is currently running in normal mode with the problem drive unassigned. Everything is running as normal with the contents emulated.

nodeone-diagnostics-20250507-1044.zip

 

*edit*

To further complicate matters, the array has written some data to it in the meantime with the problem drive unassigned. I'm assuming now the best thing to do is to simply rebuild the array onto the same disc rather than try to get Unraid to remember the old configuration?

Edited May 7, 20251 yr by Tag

SMART for disk5 looks OK, and emulated disk5 is mounted with lots of data.

 

syslog-previous seems to indicate a connection problem.

 

Rebuilding was always the correct thing to do anyway. The disk was kicked out of the array because a write to it had failed, but that initial failed write and all subsequent writes were emulated by updating parity. So the physical disk is out-of-sync and missing some writes.

 

You might check connections before starting the rebuild.

Thank you for the confirmation. I figured it was probably some sort of connection or cable issue but everything seemed fine at first glance. I'll swap the cables out and then start the rebuild.