GerryGER Posted June 7, 2023 Share Posted June 7, 2023 Hi, yesterday my Disk 2 went "Unmountable: Wrong or no file system", so I tried "xfs_repair", but that went on for 6+ hours and I stopped it, since there was no indication on how long it would continue to take (endless spam of "...." and it initially started with an error about the superblock being damaged/not found). A friend of mine recommended me to just do a parity rebuild and be done with it. So I stopped the array, took Disk2 out, started the array, stopped it, re-added Disk 2 and started the Parity rebuild, 20 seconds later, the "Unmountable" option popped up again. How should I proceed? I didn't dare to format it, since there is the warning about "update Parity to reflect this", which sounded like the data can't be recovered by parity rebuild anymore... Quote Link to comment
Kilrah Posted June 7, 2023 Share Posted June 7, 2023 (edited) Parity rebuild cannot help with a corrupted filesystem, it'll just rebuild the same corrupted filesystem. xfs_repair is what you need, and of course never format anything you need to recover. Edited June 7, 2023 by Kilrah Quote Link to comment
JorgeB Posted June 7, 2023 Share Posted June 7, 2023 What was the command you've used with xfs_repair? Quote Link to comment
GerryGER Posted June 7, 2023 Author Share Posted June 7, 2023 1 minute ago, JorgeB said: What was the command you've used with xfs_repair? It was xfs_repair -v /dev/sdc Quote Link to comment
JorgeB Posted June 7, 2023 Share Posted June 7, 2023 Just now, GerryGER said: It was xfs_repair -v /dev/sdc That won't work, please see check filesystem and use the GUI. Quote Link to comment
GerryGER Posted June 7, 2023 Author Share Posted June 7, 2023 (edited) 10 minutes ago, JorgeB said: That won't work, please see check filesystem and use the GUI. "Phase 1 - find and verify superblock... bad primary superblock - bad sector size !!! 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." Ah I'm dumb, had -n on... after removing -n and going with only -v: Phase 1 - find and verify superblock... bad primary superblock - bad sector size !!! attempting to find secondary superblock... .found candidate secondary superblock... verified secondary superblock... writing modified primary superblock - block cache size set to 1420144 entries Phase 2 - using internal log - zero log... zero_log: head block 493884 tail block 493884 - scan filesystem freespace and inode maps... Metadata CRC error detected at 0x43d440, xfs_agf block 0x1/0x200 agf has bad CRC for ag 0 Metadata CRC error detected at 0x468740, xfs_agi block 0x2/0x200 agi has bad CRC for ag 0 bad magic # 0x0 for agf 0 bad version # 0 for agf 0 bad length 0 for agf 0, should be 268435455 bad uuid 00000000-0000-0000-0000-000000000000 for agf 0 bad magic # 0x0 for agi 0 bad version # 0 for agi 0 bad length # 0 for agi 0, should be 268435455 bad uuid 00000000-0000-0000-0000-000000000000 for agi 0 reset bad agf for ag 0 reset bad agi for ag 0 bad levels 0 for btbno root, agno 0 bad agbno 0 for btbno root, agno 0 bad levels 0 for btbcnt root, agno 0 bad agbno 0 for btbcnt root, agno 0 bad levels 0 for refcountbt root, agno 0 bad agbno 0 for refcntbt root, agno 0 bad levels 0 for inobt root, agno 0 bad agbno 0 for inobt root, agno 0 bad levels 0 for finobt root, agno 0 bad agbno 0 for finobt root, agno 0 agi unlinked bucket 0 is 0 in ag 0 (inode=0) agi unlinked bucket 1 is 0 in ag 0 (inode=0) agi unlinked bucket 2 is 0 in ag 0 (inode=0) agi unlinked bucket 3 is 0 in ag 0 (inode=0) agi unlinked bucket 4 is 0 in ag 0 (inode=0) agi unlinked bucket 5 is 0 in ag 0 (inode=0) agi unlinked bucket 6 is 0 in ag 0 (inode=0) agi unlinked bucket 7 is 0 in ag 0 (inode=0) agi unlinked bucket 8 is 0 in ag 0 (inode=0) agi unlinked bucket 9 is 0 in ag 0 (inode=0) agi unlinked bucket 10 is 0 in ag 0 (inode=0) agi unlinked bucket 11 is 0 in ag 0 (inode=0) agi unlinked bucket 12 is 0 in ag 0 (inode=0) agi unlinked bucket 13 is 0 in ag 0 (inode=0) agi unlinked bucket 14 is 0 in ag 0 (inode=0) agi unlinked bucket 15 is 0 in ag 0 (inode=0) agi unlinked bucket 16 is 0 in ag 0 (inode=0) agi unlinked bucket 17 is 0 in ag 0 (inode=0) agi unlinked bucket 18 is 0 in ag 0 (inode=0) agi unlinked bucket 19 is 0 in ag 0 (inode=0) agi unlinked bucket 20 is 0 in ag 0 (inode=0) agi unlinked bucket 21 is 0 in ag 0 (inode=0) agi unlinked bucket 22 is 0 in ag 0 (inode=0) agi unlinked bucket 23 is 0 in ag 0 (inode=0) agi unlinked bucket 24 is 0 in ag 0 (inode=0) agi unlinked bucket 25 is 0 in ag 0 (inode=0) agi unlinked bucket 26 is 0 in ag 0 (inode=0) agi unlinked bucket 27 is 0 in ag 0 (inode=0) agi unlinked bucket 28 is 0 in ag 0 (inode=0) agi unlinked bucket 29 is 0 in ag 0 (inode=0) agi unlinked bucket 30 is 0 in ag 0 (inode=0) agi unlinked bucket 31 is 0 in ag 0 (inode=0) agi unlinked bucket 32 is 0 in ag 0 (inode=0) agi unlinked bucket 33 is 0 in ag 0 (inode=0) agi unlinked bucket 34 is 0 in ag 0 (inode=0) agi unlinked bucket 35 is 0 in ag 0 (inode=0) agi unlinked bucket 36 is 0 in ag 0 (inode=0) agi unlinked bucket 37 is 0 in ag 0 (inode=0) agi unlinked bucket 38 is 0 in ag 0 (inode=0) agi unlinked bucket 39 is 0 in ag 0 (inode=0) agi unlinked bucket 40 is 0 in ag 0 (inode=0) agi unlinked bucket 41 is 0 in ag 0 (inode=0) agi unlinked bucket 42 is 0 in ag 0 (inode=0) agi unlinked bucket 43 is 0 in ag 0 (inode=0) agi unlinked bucket 44 is 0 in ag 0 (inode=0) agi unlinked bucket 45 is 0 in ag 0 (inode=0) agi unlinked bucket 46 is 0 in ag 0 (inode=0) agi unlinked bucket 47 is 0 in ag 0 (inode=0) agi unlinked bucket 48 is 0 in ag 0 (inode=0) agi unlinked bucket 49 is 0 in ag 0 (inode=0) agi unlinked bucket 50 is 0 in ag 0 (inode=0) agi unlinked bucket 51 is 0 in ag 0 (inode=0) agi unlinked bucket 52 is 0 in ag 0 (inode=0) agi unlinked bucket 53 is 0 in ag 0 (inode=0) agi unlinked bucket 54 is 0 in ag 0 (inode=0) agi unlinked bucket 55 is 0 in ag 0 (inode=0) agi unlinked bucket 56 is 0 in ag 0 (inode=0) agi unlinked bucket 57 is 0 in ag 0 (inode=0) agi unlinked bucket 58 is 0 in ag 0 (inode=0) agi unlinked bucket 59 is 0 in ag 0 (inode=0) agi unlinked bucket 60 is 0 in ag 0 (inode=0) agi unlinked bucket 61 is 0 in ag 0 (inode=0) agi unlinked bucket 62 is 0 in ag 0 (inode=0) agi unlinked bucket 63 is 0 in ag 0 (inode=0) sb_icount 146880, counted 212288 sb_ifree 1301, counted 727 sb_fdblocks 1475402857, counted 1098436740 root inode chunk not found Phase 3 - for each AG... - scan and clear agi unlinked lists... - process known inodes and perform inode discovery... - agno = 0 imap claims in-use inode 131 is free, correcting imap imap claims in-use inode 132 is free, correcting imap imap claims in-use inode 133 is free, correcting imap imap claims in-use inode 134 is free, correcting imap imap claims in-use inode 135 is free, correcting imap imap claims in-use inode 136 is free, correcting imap imap claims in-use inode 139 is free, correcting imap imap claims in-use inode 140 is free, correcting imap imap claims in-use inode 141 is free, correcting imap imap claims in-use inode 142 is free, correcting imap imap claims in-use inode 143 is free, correcting imap imap claims in-use inode 144 is free, correcting imap imap claims in-use inode 145 is free, correcting imap imap claims in-use inode 146 is free, correcting imap imap claims in-use inode 147 is free, correcting imap imap claims in-use inode 148 is free, correcting imap imap claims in-use inode 149 is free, correcting imap imap claims in-use inode 150 is free, correcting imap imap claims in-use inode 151 is free, correcting imap imap claims in-use inode 152 is free, correcting imap imap claims in-use inode 153 is free, correcting imap imap claims in-use inode 154 is free, correcting imap imap claims in-use inode 155 is free, correcting imap imap claims in-use inode 156 is free, correcting imap imap claims in-use inode 157 is free, correcting imap imap claims in-use inode 158 is free, correcting imap imap claims in-use inode 159 is free, correcting imap imap claims in-use inode 160 is free, correcting imap imap claims in-use inode 161 is free, correcting imap imap claims in-use inode 162 is free, correcting imap imap claims in-use inode 163 is free, correcting imap imap claims in-use inode 164 is free, correcting imap imap claims in-use inode 165 is free, correcting imap imap claims in-use inode 166 is free, correcting imap imap claims in-use inode 167 is free, correcting imap imap claims in-use inode 168 is free, correcting imap imap claims in-use inode 169 is free, correcting imap imap claims in-use inode 170 is free, correcting imap imap claims in-use inode 171 is free, correcting imap imap claims in-use inode 172 is free, correcting imap imap claims in-use inode 173 is free, correcting imap imap claims in-use inode 174 is free, correcting imap imap claims in-use inode 175 is free, correcting imap imap claims in-use inode 176 is free, correcting imap imap claims in-use inode 177 is free, correcting imap imap claims in-use inode 178 is free, correcting imap imap claims in-use inode 179 is free, correcting imap imap claims in-use inode 180 is free, correcting imap imap claims in-use inode 181 is free, correcting imap imap claims in-use inode 182 is free, correcting imap imap claims in-use inode 183 is free, correcting imap imap claims in-use inode 184 is free, correcting imap imap claims in-use inode 185 is free, correcting imap imap claims in-use inode 186 is free, correcting imap imap claims in-use inode 187 is free, correcting imap imap claims in-use inode 188 is free, correcting imap imap claims in-use inode 189 is free, correcting imap imap claims in-use inode 190 is free, correcting imap imap claims in-use inode 191 is free, correcting imap - agno = 1 - agno = 2 - agno = 3 - agno = 4 - agno = 5 - agno = 6 - agno = 7 - agno = 8 - agno = 9 - agno = 10 - agno = 11 - agno = 12 - process newly discovered inodes... Phase 4 - check for duplicate blocks... - setting up duplicate extent list... - check for inodes claiming duplicate blocks... - agno = 0 - agno = 2 - agno = 1 entry "Anime" in shortform directory 128 references non-existent inode 1097794569 junking entry "Anime" in directory inode 128 entry "Serien" in shortform directory 128 references non-existent inode 1654179027 junking entry "Serien" in directory inode 128 - agno = 3 entry "[SNIP PRIVATE ;)]" at block 0 offset 3320 in directory inode 131 references non-existent inode 470699848 clearing inode number in entry at offset 3320... entry "[SNIP PRIVATE ;)]" at block 1 offset 4008 in directory inode 131 references non-existent inode 470699851 clearing inode number in entry at offset 4008... entry "[SNIP PRIVATE ;)]" at block 2 offset 3520 in directory inode 131 references non-existent inode 1654179040 clearing inode number in entry at offset 3520... [a bit more of this] bad hash table for directory inode 4394447249 (no data entry): rebuilding rebuilding directory inode 4394447249 bad hash table for directory inode 4394448335 (no data entry): rebuilding rebuilding directory inode 4394448335 entry ".." in directory inode 4402441515 points to non-existent inode 947597284, marking entry to be junked bad hash table for directory inode 4402441515 (no data entry): rebuilding rebuilding directory inode 4402441515 entry ".." in directory inode 4402453480 points to non-existent inode 947620170, marking entry to be junked bad hash table for directory inode 4402453480 (no data entry): rebuilding rebuilding directory inode 4402453480 bad hash table for directory inode 4402459807 (no data entry): rebuilding rebuilding directory inode 4402459807 entry ".." in directory inode 4402462710 points to non-existent inode 947627638, marking entry to be junked bad hash table for directory inode 4402462710 (no data entry): rebuilding rebuilding directory inode 4402462710 entry ".." in directory inode 4402473729 points to non-existent inode 947633416, marking entry to be junked bad hash table for directory inode 4402473729 (no data entry): rebuilding rebuilding directory inode 4402473729 entry ".." in directory inode 4461736554 points to non-existent inode 1654179027, marking entry to be junked bad hash table for directory inode 4461736554 (no data entry): rebuilding rebuilding directory inode 4461736554 entry ".." in directory inode 4464777177 points to non-existent inode 2132507164, marking entry to be junked bad hash table for directory inode 4464777177 (no data entry): rebuilding rebuilding directory inode 4464777177 [more of this] bad hash table for directory inode 25774422906 (no data entry): rebuilding rebuilding directory inode 25774422906 - traversal finished ... - moving disconnected inodes to lost+found ... disconnected inode 159, moving to lost+found disconnected inode 160, moving to lost+found disconnected inode 161, moving to lost+found disconnected dir inode 2533438893, moving to lost+found disconnected dir inode 2533438895, moving to lost+found disconnected dir inode 2636384149, moving to lost+found disconnected dir inode 2638402822, moving to lost+found disconnected dir inode 2638402854, moving to lost+found disconnected dir inode 2638606000, moving to lost+found disconnected inode 2638606162, moving to lost+found disconnected inode 2638606163, moving to lost+found disconnected inode 2638606164, moving to lost+found disconnected inode 2638606165, moving to lost+found disconnected inode 2638606166, moving to lost+found disconnected inode 2638606167, moving to lost+found [...] Phase 7 - verify and correct link counts... resetting inode 128 nlinks from 15 to 13 resetting inode 131 nlinks from 145 to 141 resetting inode 137 nlinks from 2 to 1323 resetting inode 4368292562 nlinks from 42 to 38 resetting inode 8594108591 nlinks from 31 to 29 resetting inode 8729374599 nlinks from 7 to 6 resetting inode 8873887464 nlinks from 21 to 20 resetting inode 6725417451 nlinks from 28 to 26 resetting inode 11132024064 nlinks from 13 to 12 resetting inode 6727076067 nlinks from 16 to 15 resetting inode 8896771389 nlinks from 44 to 40 resetting inode 4394423285 nlinks from 18 to 17 resetting inode 8574919624 nlinks from 17 to 13 resetting inode 25784296244 nlinks from 5 to 4 Note - stripe unit (0) and width (0) were copied from a backup superblock. Please reset with mount -o sunit=,swidth= if necessary XFS_REPAIR Summary Wed Jun 7 12:07:23 2023 Phase Start End Duration Phase 1: 06/07 12:06:24 06/07 12:06:24 Phase 2: 06/07 12:06:24 06/07 12:06:25 1 second Phase 3: 06/07 12:06:25 06/07 12:06:47 22 seconds Phase 4: 06/07 12:06:47 06/07 12:06:47 Phase 5: 06/07 12:06:47 06/07 12:06:48 1 second Phase 6: 06/07 12:06:48 06/07 12:07:07 19 seconds Phase 7: 06/07 12:07:07 06/07 12:07:07 Total run time: 43 seconds done Edited June 7, 2023 by GerryGER Quote Link to comment
GerryGER Posted June 7, 2023 Author Share Posted June 7, 2023 (edited) Updated last post, how should I proceed? Contend on the disk is currently only emulated. Edited June 7, 2023 by GerryGER Quote Link to comment
JorgeB Posted June 7, 2023 Share Posted June 7, 2023 Start the array, it should mount now, then look for a lost+found folder. Quote Link to comment
GerryGER Posted June 7, 2023 Author Share Posted June 7, 2023 3 minutes ago, JorgeB said: Start the array, it should mount now, then look for a lost+found folder. Yeah that's there and filled with 3000 folders and files without a file ending. Should I move these files and folders and try to puzzle everything back together or...? No to mention that Parity is still not rebuild, since I started the rebuild and stopped it. Quote Link to comment
JorgeB Posted June 7, 2023 Share Posted June 7, 2023 You can try, but if there are a lot it might be easier to restore from a backup, if one exists. Quote Link to comment
GerryGER Posted June 7, 2023 Author Share Posted June 7, 2023 3 minutes ago, JorgeB said: You can try, but if there are a lot it might be easier to restore from a backup, if one exists. Only for a few of those (very personal stuff), but most is just Entertainment like movies etc., who don't get an extra backup. So: Move stuff out of lost+found and then do a parity rebuild? What happens with the lost+found folder during/after the rebuild? Quote Link to comment
JorgeB Posted June 7, 2023 Share Posted June 7, 2023 4 minutes ago, GerryGER said: What happens with the lost+found folder during/after the rebuild? Nothing unless you move the data yourself. Quote Link to comment
GerryGER Posted June 7, 2023 Author Share Posted June 7, 2023 5 minutes ago, JorgeB said: Nothing unless you move the data yourself. So that means I could just keep it there and start the Parity Rebuild? Quote Link to comment
Recommended Posts
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.