TheTechnoPilot

It is the original disk yes, but unfortunately it has already had a rebuild started on it that I cancelled when it took off claiming it was rebuilding at 22GB/s which was truly impossible across even a PCI interface, let alone SATA.. As I understand, I need to bring the array back online with the other disks, as just a parity rebuild on ST8000DM004-2CX188_WCT07A05 Oh I will just note that it originally needed a rebuild as mentioned, only because the device ID changed when I switched the underlying SATA controller on that disk to one that properly reported its ID. Perhaps I should have come on here first to see if one of you wizards could have told unraid to ignore the ID and trust the disk was the same.

To be clear, I unselected the parity disk from the array and restarted it, to then hopefully re-add it again confirming valid parity. Not the New Configuration method, which now looking at specifically says it will make recovery of a failed disk, what I am essentially (because I was rewriting the disk) am trying to recover from, impossible.

I just did as you outlined and when I went to reselect the parity after stopping the array, it is now listed as a new disk (blue) as well and now the array also won't restart like it first did with only drive 2 (my original problem) missing and now without even having it selected and still listed as unassigned! Please note that my issue NEVER was originally a problem with my parity drive. Please tell me I am not in an even worst boat now as it is feeling. I have attached the new diagnostics. coultonstudios-diagnostics-20200103-1627.zip

Here are my diagnostics! coultonstudios-diagnostics-20200103-1602.zip

Hi all, A little bit of a panicking UnRaid newbie over here and need some help from the experts! I have been in the process of building up my UnRaid system to replace my old hackintosh build for video and photo editing work including 5 high capacity hard drives (1x12TB, 2x10TB, 2x8TB) and a 1TB NVME cache drive on a Ryzen 3900X B450 ITX system with 64GB ram. Today after doing a full parity check over the last couple days, had to migrate my system from using a two port NVME SATA port card to a proper five port unit that passed through the actual drive IDs unlike the original which didn't as it could only operate either in hardware RAID or amassed JBOD which had one of my 8TB HDDs plugged into. I swapped out the unit and re-ran all my cables and on boot-up as expected, UnRAID didn't recognize the now correct Seagate drive ID of the rewired 8TB drive, so I reselected it in to the same place in the array for rebuild and started the process. All looked well with it parity sync going at 150MB/s, so I then went to start up my MacOS VM that lives predominately on my cache drive (primary virtual disk location), after boot-up I noticed that for some odd reason my sync was now paused, so I unpaused it. Suddenly the sync said it was running at 22GB/s and took off chugging through up to 10% rebuild which made no sense for having it running for only 5 minutes at this point, so I immediately paused the sync again and hard stopped the virtual machine. I then tried cancelling the rebuild and taking the array offline and restarting the system, hoping for the option to restart the parity sync, which on boot this time did show the emulated drive orange triangle next to the drive, but when restarting the array didn't offer to rebuild and now showed the drive as unmountable and my array usage from my actual 83% now up at 91%. Reading through the forums for an answer I saw it noted that to allow me to re-add the same drive to the missing disk as if for fresh rebuild, I should unassign the disk and restart the array without it to unmatch the name and then pull it back off-line to re-add it back again, I held my breath and followed those steps. Now however instead of having the option to re-add it like in a parity sync operation it is showing a blue square of a new device and "Too many wrong and/or missing disks!" in the array start box with it selected and an red 'X' on my 12TB parity drive listing it as disabled. Rebooting the system doesn't change this. How do I get back to the start of this last stressful hour and tell the system to rebuild from the parity data on the 8TB drive? PLEASE HELP!!!

I'm going to jump in here even though it is a little bit of an old topic because it still applies. I also have been racking my brain trying to get UnRaid to boot on a 32gb SanDisk Ultra Fit and having the same exact issue, all configured on a Mac. I too bought it on the recommendation from Limetech and because the 32gb was only a couple bucks more...