October 9, 20241 yr I hit the wrong button with New Config and wiped out my array except the pools. It should have been no issue as I had a screenshot of the config, but then Windows blue screened when I used my KVM to get my second monitor. It rebooted my laptop and now my array settings are cleared minus the cache pool that I actually checked to retain. I have been in the process of shuffling drives. I wiped out a couple of really large backup shares and I removing the 12 TB drives and keeping the much newer 14 tb drives. 2x 14TB drives were Parity, most of the data was already on the 14TB drives, one of which I was planning to swap in for an empty 12tb drive. I'm confident the parity is correct, everything was just checked a couple days ago when I swapped the 12 and 14 TB parity drives. How do I identify which drives are parity and which are data so I can slot them correctly and fire up the array?
October 9, 20241 yr Community Expert Solution Read this section of the Manual: https://docs.unraid.net/unraid-os/troubleshooting/data-recovery/#lost-array-configuration
October 9, 20241 yr Author I found this is the logs from an array restart earlier this morning. I'm guessing this is my array and how it is setup? Is disk0 Parity1 and disk 29 the Parity 2? The 2 12 TB drives were data disks 1-3 , and 4 other 14TB drives were data 4-7. 1 12TB was not assigned, it was the old parity drive. Oct 9 10:26:28 Tower kernel: mdcmd (1): import 0 sdc 64 13672382412 0 WDC_WD140EDGZ-11B1PA0_9MHGJE3T Oct 9 10:26:28 Tower kernel: md: import disk0: (sdc) WDC_WD140EDGZ-11B1PA0_9MHGJE3T size: 13672382412 Oct 9 10:26:28 Tower kernel: mdcmd (2): import 1 sdg 64 11718885324 0 WDC_WD120EMAZ-11BLFA0_8CK9VZRF Oct 9 10:26:28 Tower kernel: md: import disk1: (sdg) WDC_WD120EMAZ-11BLFA0_8CK9VZRF size: 11718885324 Oct 9 10:26:28 Tower kernel: mdcmd (3): import 2 sde 64 11718885324 0 WDC_WD120EMFZ-11A6JA0_Z2GWUJ5T Oct 9 10:26:28 Tower kernel: md: import disk2: (sde) WDC_WD120EMFZ-11A6JA0_Z2GWUJ5T size: 11718885324 Oct 9 10:26:28 Tower kernel: mdcmd (4): import 3 sdf 64 11718885324 0 WDC_WD120EMFZ-11A6JA0_9RGUGEAC Oct 9 10:26:28 Tower kernel: md: import disk3: (sdf) WDC_WD120EMFZ-11A6JA0_9RGUGEAC size: 11718885324 Oct 9 10:26:28 Tower kernel: mdcmd (5): import 4 sdh 64 13672382412 0 WDC_WUH721414ALE604_Z2HS9SET Oct 9 10:26:28 Tower kernel: md: import disk4: (sdh) WDC_WUH721414ALE604_Z2HS9SET size: 13672382412 Oct 9 10:26:28 Tower kernel: mdcmd (6): import 5 sdi 64 13672382412 0 WDC_WUH721414ALE604_Z2GLS0MT Oct 9 10:26:28 Tower kernel: md: import disk5: (sdi) WDC_WUH721414ALE604_Z2GLS0MT size: 13672382412 Oct 9 10:26:28 Tower kernel: mdcmd (7): import 6 sdj 64 13672382412 0 WDC_WUH721414ALE604_Z2J2UDBT Oct 9 10:26:28 Tower kernel: md: import disk6: (sdj) WDC_WUH721414ALE604_Z2J2UDBT size: 13672382412 Oct 9 10:26:28 Tower kernel: mdcmd (8): import 7 sdk 64 13672382412 0 WDC_WUH721414ALE604_9JHDTB9T Oct 9 10:26:28 Tower kernel: md: import disk7: (sdk) WDC_WUH721414ALE604_9JHDTB9T size: 13672382412 Oct 9 10:26:28 Tower kernel: mdcmd (9): import 8 Oct 9 10:26:28 Tower kernel: mdcmd (10): import 9 Oct 9 10:26:28 Tower kernel: mdcmd (11): import 10 Oct 9 10:26:28 Tower kernel: mdcmd (12): import 11 Oct 9 10:26:28 Tower kernel: mdcmd (13): import 12 Oct 9 10:26:28 Tower kernel: mdcmd (14): import 13 Oct 9 10:26:28 Tower kernel: mdcmd (15): import 14 Oct 9 10:26:28 Tower kernel: mdcmd (16): import 15 Oct 9 10:26:28 Tower kernel: mdcmd (17): import 16 Oct 9 10:26:28 Tower kernel: mdcmd (18): import 17 Oct 9 10:26:28 Tower kernel: mdcmd (19): import 18 Oct 9 10:26:28 Tower kernel: mdcmd (20): import 19 Oct 9 10:26:28 Tower kernel: mdcmd (21): import 20 Oct 9 10:26:28 Tower kernel: mdcmd (22): import 21 Oct 9 10:26:28 Tower kernel: mdcmd (23): import 22 Oct 9 10:26:28 Tower kernel: mdcmd (24): import 23 Oct 9 10:26:28 Tower kernel: mdcmd (25): import 24 Oct 9 10:26:28 Tower kernel: mdcmd (26): import 25 Oct 9 10:26:28 Tower kernel: mdcmd (27): import 26 Oct 9 10:26:28 Tower kernel: mdcmd (28): import 27 Oct 9 10:26:28 Tower kernel: mdcmd (29): import 28 Oct 9 10:26:28 Tower kernel: mdcmd (30): import 29 sdb 64 13672382412 0 WDC_WD140EDGZ-11B1PA0_9MHAHKBJ Oct 9 10:26:28 Tower kernel: md: import disk29: (sdb) WDC_WD140EDGZ-11B1PA0_9MHAHKBJ size: 13672382412
October 9, 20241 yr Author 1 minute ago, Frank1940 said: Read this section of the Manual: https://docs.unraid.net/unraid-os/troubleshooting/data-recovery/#lost-array-configuration Thanks. I'll see if I can get this recovered.
October 9, 20241 yr Author 13 minutes ago, Frank1940 said: Read this section of the Manual: https://docs.unraid.net/unraid-os/troubleshooting/data-recovery/#lost-array-configuration Thanks, that brought everything back up. Those instructions to lack one step though. Between 5 and 6 there should be a step saying to unassign the unmountable drives and assign then to the parity slots. I moved both, moved my data drives up in the slots, and checked the box to not redo parity as i knew it was current and did not need to be rebuilt. This also gives me a better understanding of how the New Config works. It keeps what you checks and clears what is marked as unassigned.
October 9, 20241 yr Community Expert 28 minutes ago, quietas said: I moved both, moved my data drives up in the slots, and checked the box to not redo parity as i knew it was current and did not need to be rebuilt. Parity is independent of the position in the array BUT Parity2 is a complex matrix computation which is dependent on each data drive's position in the array. (If it were I, I would first check and make sure that it looks like all of the data files are there. Assuming that everything looks alright, I would start a non-parity correcting check. If it does find not any errors in the first half hour, parity is probably correct. If it finds any errors, you will have to run a correcting parity check (i.e., parity rebuild).)
October 9, 20241 yr Author 1 hour ago, Frank1940 said: Parity is independent of the position in the array BUT Parity2 is a complex matrix computation which is dependent on each data drive's position in the array. (If it were I, I would first check and make sure that it looks like all of the data files are there. Assuming that everything looks alright, I would start a non-parity correcting check. If it does find not any errors in the first half hour, parity is probably correct. If it finds any errors, you will have to run a correcting parity check (i.e., parity rebuild).) Thanks. I kicked that off an hour ago and if definitely has some problems with my drive changes. Rebuild it is.
Join the conversation
You can post now and register later. If you have an account, sign in now to post with your account.
Note: Your post will require moderator approval before it will be visible.