Deryg

mediawhore-diagnostics-20230223-1024.zip

Here's the output. Let's pretend we don't see some of the more adult-oriented lost bit names Drive 5 disk check.txt

Drive 5 and 6 don't show as emulated though. They just show as not installed. did I miss something somewhere?

restarted in maintenance mode. check filesystem for drive 5 gives me this output: Phase 1 - find and verify superblock... bad primary superblock - bad CRC in superblock !!! attempting to find secondary superblock... .found candidate secondary superblock... verified secondary superblock... would write modified primary superblock Primary superblock would have been modified. Cannot proceed further in no_modify mode. Exiting now.

unraid tells me check filesystem only available in maintenance mode

Jsut to be clear, I didn't format the actual drives, I just set the filesystem on the missing drives to XFS, right?

mediawhore-diagnostics-20230222-2142.zip

Here we go mediawhore-diagnostics-20230222-2128.zip

New config, retain all done. assigned new drives to drive 5 and 6. started array in maintenance mode with parity marked valid mediawhore-diagnostics-20230222-1657.zip

1. Array has been stopped since issue came up. 2. yes, the new 4TB drives (one extra) are bigger or equal to the drives 5/6 that are existing but smaller than parity 8TB 3. Disabled autostart, shutdown and restarted. Diagnostics attached. Please confirm if I should have assigned the new drives to 5 and 6 at this point? If so I will repeat but assign new drives to 5 and 6 mediawhore-diagnostics-20230222-1545.zip

or should I pop it into unassigned, look at the files on there and I will be able to tell if it is indeed the drive that should have been in array?

hmmm, that is bizarre. I just noticed that. I did not think I messed with any assignments but I realize opening the diagnostic smart reports that they are indeed different drives... I did pull a 3TB seagate which should have been an unassigned device. Should I power down, swap it out with drive 5 and run diagnostics to see if it comes with the same ID which would mean I'd just mislabelled a cage? Update. I am holding that drive in my hand right now. Drive was in wrong cage. Should I swap it with the other drive and assign it to drive 5?

OK, all 3 drives have now finished preclear. 0 issues on the new drives. to recap, drive 6 was rebuilding itself when other drives dropped from array. Drive 5 redballed but was a dubious drive. I have 3 4 TB drives brand new (precleared) and tested that can be used to attempt corrective measures. Drive 7 (8TB) but it should be a good drive. I do not have a spare 8TB drive to rebuilt it onto. As instructed I have made no changes to the array and it remains stopped and spun down. Dockers are turned off. Now trying to figure out how to revive array and minimize (or eliminate) data loss with 2 drives dropped, one in aborted rebuild with only dual parity. I've rerun diagnostics after drive clearing done and attached here Awaiting further instructions and assistance (which I greatly appreciate) mediawhore-diagnostics-20230222-1336.zip

Et voila mediawhore-diagnostics-20230221-1928.zip

All the drives are in icy dock trays and cable goes from mobo to 5-in-3 cage. it's a much more secure connection now with the new cables too. some of the old cables were literally wobbling in their sockets. yikes

Other side note, now that it's rebooted (I just powered down to put in the new drives and replace the cables) It no longer says too many missing disk. Array shows stopped configuration valid rather than the invalid configuration it used to show

new drives are in. all sata cables replaced with decent latching cables. faulty molex connector replaced (the things you find when you open the case). I pulled the unassigned devices I had sitting there and used the cages to put in the new drives. They are now preclearing (51 percent pre-read). Will advise when the preclear is done. Side note, I did not procure another 8 TB drive as drive 7 is brand new and I have no idea why it dropped but am fairly certain it is fine (also annoyingly enough, it was put in last week to replace a 3TB drive which had gone sideways so data content on it is less than 3 TB)

This I knew but im still unsure how I can rebuild with 3 drives dropped from array

It is always safer to rebuild to another disk, but disks aren't free. So sometimes you consider the pros and cons. If everything is working well, maybe OK to rebuild on top. It's provincial. Family day. All the stores are closed and I have kids at home underfoot while I try to get some work done . As far as rebuilding on the same disk, that is a definite lesson learned. I was in a rush and figured if it went to crap, i'd just rebuild again with a different drive. Was not expecting to drop more drives during the rebuild. Never again. I have 3 drives on the way so I'll have a spare 4TB. Gonna need to go shop for a spare 8TB as well. I will NEVER rebuild on same drive again. Drives will arrive tomorrow. I assume I preclear them and then advise and wait for further instructions?

Not here in Ontario Canada. Everything is closed. Amazon.ca next day delivery to the rescue

I unfortunately was... i'll be chalking that one up to lessons learned

Damn, i forgot today is a holiday, so no replacement drives can be bought. all the stores are closed. Array will remain offline for another day. anything I can do in the meanwhile? I'm still unclear as to how to proceed as well once I do secure some new drives and cables. I did reseat my card (PERC H310), and reconnected all drive cables in case I had bad connections.

the problem is that I had started a rebuild on drive 6 when it all went to shit. as it was in the process of rebuilding, I assume that one is toast and unrecoverable?

I'm back online but will not have drives to begin the fix until after lunch as I need to buy some new ones. Have I mentioned how fantastic it is that you are taking the time to talk me through this and try to help? This is so appreciated, you have no idea.