Ignoring my dumb decision to not have backed up my flash drive in recent years nor having taken any pictures of the array setup.  The flash drive I was using seems to be dead. Pulled it out and tried on other PCs and it doesn't seem to show up at all. If there are any tips on how to get the configs back from this drive so I can just move them onto the current one, I'd appreciate that.

 

Currently, I've already moved my license onto a new USB drive and the hardware is fine. I'm just not really sure how to best proceed from here in order to keep my data intact. I was running dual parity, with 12 data drives and 2 cache SSD drives.

 

I can easily identify which drives were the parity ones (they are the only 2 14TB drives on the array), although I'm not 100% sure which one was Parity 1 and Parity 2 exactly. I do not know the order of the 12 data drives however. The cache drives are 2 TB drives that I had pooled together to have a single 4TB cache that had all my dockers and recent downloads for the server before they got processed by the mover.

 

Right now I'm doing a parity check for now which will take over a day (without auto-correct) and it indeed is showing a ton of sync errors. I'd love to maintain the data as it was pre-flash drive failure, I know I'm a dumbass for not having backed up properly. I may have placed a backup on the array itself though, if there are any tips for how to be able to navigate the array.

 

How to best proceed? Only thing I can think of right now is to have the dual parity parity correct the twelve data drives. However I'm not 100% sure on Parity Drives 1 and 2 being exactly correct (I know which two drives, but I do not know which of the two is exactly #1 and #2). I think the best solution would be if I could somehow recover the data on the previous flash drive and copy that over.

Edited June 14, 20242 yr by ktoen

3 hours ago, ktoen said:

Right now I'm doing a parity check for now which will take over a day (without auto-correct) and it indeed is showing a ton of sync errors.

I assume this means you've already assigned the disks? Parity2 requires all the data disks assigned to the correct slots to be valid, getting parity 1 and 2 right is 50/50, in any case your data will be fine, as long as you din't assign a data disk to parity, if you are doing a correcting check it will likely be faster if you do a parity sync instead, but if you got lucky with parity 1 and 2, you may be able to set the one as valid now, making the array protected while you sync parity2, post the current diags, they should give a good idea about that.

Yeah I've already assigned the disks, and I had some book-keeping I did where I knew the order for the first 10 out of 12 data drives (stopped taking notes after that). Stopped the parity check and re-assigned but its making me, or at least,  I started a rebuild on the two disks on the order I was not sure about for #11 and #12. I know I got the right two parity disks, just not sure if they're in the exact #1 and #2 assigned parity drives.

 

Cache pool was fine and the dockers are fine too, just had to grab them again and make the same mappings. Just gotta deal with the plug-ins now. I think I'm past the point of no return as far after this data rebuild though, most I can do after is just parity sync, right? Luckily, it doesn't hold anything that I can't just fetch again, but I'm assuming I've lost some things if the order is wrong somewhere during assignment?

tower-diagnostics-20240614-1910.zip

Not sure why your are rebuilding disks?

 

Just assigning the disks would never start a rebuild, even if they were in the wrong order, at most you would need to re-sync parity. Did those disks have data?