Kevin T

My new drive is arriving today so I wanted to attempt this tonight, here is my diagnostics. Thank you, Kevin unraid-diagnostics-20221001-1815.zip

The drive that stopped working sounds like it keeps trying to spin up, but I have tried it in 2 different systems and the BIOS does not recognize it at all. When I swap for a different drive it recognized the new one in the same position immediately and they are hot swap bays so it's not a connection issue. I can turn it on and send a diagnostics, I just like to keep it turned off right now since I have no protection.

That is very helpful thank you, I am ordering another drive and will try what you suggest after I receive it, I just have a few questions: Does a New Config only overwrite the disk identification related settings or everything like shares, etc.? Would you recommend using the older pre-issue parity or the most recent parity when the issues occurred? They are from the same day just hours apart and since the array won't mount, the server has been offline since. When rebuilding the drive, if there is some corruption, that will only affect the drive that is rebuilding and not the other drives that are okay, correct? Is there a way to scan for / detect any corruption while the drive is being emulated that I can maybe try to fix? Thank you, Kevin

I have a 1 parity unRAID system, I was preparing to upgrade multiple drives to larger sizes. First I did the parity drive (Drive 1) upgrade which was okay. After that completed I tried upgrading another drive (Drive 5) and during the rebuild it completely failed and isn't even recognized after rebooting. While that drive was bad, I just tried to copy a small file from another drive (Drive 2) and the server locked up. Then that Drive 2 is now not being recognized by the BIOS and doesn't seem to be spinning up. I was wondering if there is a way I can read-only mount the array using my original parity drive (Drive 1) and my original Drive 5 without the Drive 2 being present where I can emulate the data on it and copy it off to another drive? The system was somewhat unchanged during this process but I am not sure if my new parity drive had more data written to it than my original parity drive so I figured that might be the best option. I understand there may be a few files where the parity may fail. The GUI now thinks all the swapping attempts are new drives so it doesn't see the Drives 1 and 5 now being part of the array, so I'm not sure if it can be done in a commandline or if I can modify some config files? Thank you, Kevin