May 23, 20242 yr Community Expert Now start the array in normal mode, the disk should mount, check contents to see if they look OK, also look for a lost+found folder.
May 23, 20242 yr Author 3 minutes ago, JorgeB said: Now start the array in normal mode, the disk should mount, check contents to see if they look OK, also look for a lost+found folder. im still getting this
May 23, 20242 yr Author 2 hours ago, JorgeB said: Reboot to clear the logs and post new diags after array start. friday-diagnostics-20240523-1916.zip
May 24, 20242 yr Community Expert There are still filesystem issues, that's strange since xfs_repair usually only requires one run, but run it again, since there's no parity, just stop the array and type: xfs_repair -v /dev/sdb1 Then post the results from that.
May 24, 20242 yr Author 8 hours ago, JorgeB said: There are still filesystem issues, that's strange since xfs_repair usually only requires one run, but run it again, since there's no parity, just stop the array and type: xfs_repair -v /dev/sdb1 Then post the results from that. it encountered a fatal error Phase 1 - find and verify superblock... - block cache size set to 1462784 entries Phase 2 - using internal log - zero log... zero_log: head block 61642 tail block 61642 - scan filesystem freespace and inode maps... Metadata corruption detected at 0x43e420, xfs_agf block 0x1/0x200 Metadata corruption detected at 0x43e420, xfs_agf block 0x17fffffe9/0x200 Metadata corruption detected at 0x43e420, xfs_agf block 0x1ffffffe1/0x200 Metadata corruption detected at 0x43e420, xfs_agf block 0xfffffff1/0x200 Metadata corruption detected at 0x469d68, xfs_agi block 0x2/0x200 bad uuid db398da9-fd5b-4bf0-b679-372ac3053b16 for agf 0 bad uuid db398da9-fd5b-4bf0-b679-372ac3053b16 for agi 0 reset bad agf for ag 0 reset bad agi for ag 0 Metadata corruption detected at 0x469d68, xfs_agi block 0x17fffffea/0x200 bad uuid db398da9-fd5b-4bf0-b679-372ac3053b16 for agf 3 bad uuid db398da9-fd5b-4bf0-b679-372ac3053b16 for agi 3 reset bad agf for ag 3 reset bad agi for ag 3 Metadata corruption detected at 0x43e420, xfs_agf block 0x27fffffd9/0x200 Metadata corruption detected at 0x469d68, xfs_agi block 0x1ffffffe2/0x200 bad uuid db398da9-fd5b-4bf0-b679-372ac3053b16 for agf 4 bad uuid db398da9-fd5b-4bf0-b679-372ac3053b16 for agi 4 reset bad agf for ag 4 reset bad agi for ag 4 Metadata corruption detected at 0x469d68, xfs_agi block 0xfffffff2/0x200 bad uuid db398da9-fd5b-4bf0-b679-372ac3053b16 for agf 2 bad uuid db398da9-fd5b-4bf0-b679-372ac3053b16 for agi 2 reset bad agf for ag 2 reset bad agi for ag 2 Metadata corruption detected at 0x43e420, xfs_agf block 0x7ffffff9/0x200 Metadata corruption detected at 0x43e0c8, xfs_agfl block 0x3/0x200 Metadata corruption detected at 0x43e0c8, xfs_agfl block 0x17fffffeb/0x200 Metadata corruption detected at 0x469d68, xfs_agi block 0x27fffffda/0x200 bad uuid db398da9-fd5b-4bf0-b679-372ac3053b16 for agf 5 bad uuid db398da9-fd5b-4bf0-b679-372ac3053b16 for agi 5 reset bad agf for ag 5 reset bad agi for ag 5 Metadata corruption detected at 0x43e0c8, xfs_agfl block 0x1ffffffe3/0x200 Metadata corruption detected at 0x43e0c8, xfs_agfl block 0xfffffff3/0x200 Metadata corruption detected at 0x469d68, xfs_agi block 0x7ffffffa/0x200 bad uuid db398da9-fd5b-4bf0-b679-372ac3053b16 for agf 1 bad uuid db398da9-fd5b-4bf0-b679-372ac3053b16 for agi 1 reset bad agf for ag 1 reset bad agi for ag 1 Metadata corruption detected at 0x458f90, xfs_bnobt block 0x68/0x1000 btree block 0/13 is suspect, error -117 Metadata corruption detected at 0x458f90, xfs_bnobt block 0x180000008/0x1000 btree block 3/4 is suspect, error -117 Metadata corruption detected at 0x43e0c8, xfs_agfl block 0x27fffffdb/0x200 Metadata corruption detected at 0x458f90, xfs_bnobt block 0x200000000/0x1000 btree block 4/4 is suspect, error -117 Metadata corruption detected at 0x458f90, xfs_bnobt block 0x100000010/0x1000 btree block 2/4 is suspect, error -117 Metadata corruption detected at 0x43e0c8, xfs_agfl block 0x7ffffffb/0x200 Metadata corruption detected at 0x458f90, xfs_cntbt block 0x70/0x1000 btree block 0/14 is suspect, error -117 Metadata corruption detected at 0x458f90, xfs_cntbt block 0x180000010/0x1000 btree block 3/5 is suspect, error -117 Metadata corruption detected at 0x458f90, xfs_bnobt block 0x27ffffff8/0x1000 btree block 5/4 is suspect, error -117 Metadata corruption detected at 0x458f90, xfs_cntbt block 0x200000008/0x1000 btree block 4/5 is suspect, error -117 Metadata corruption detected at 0x458f90, xfs_cntbt block 0x100000018/0x1000 btree block 2/5 is suspect, error -117 Metadata corruption detected at 0x458f90, xfs_bnobt block 0x80000018/0x1000 btree block 1/4 is suspect, error -117 Metadata corruption detected at 0x458f90, xfs_refcountbt block 0x60/0x1000 btree block 0/12 is suspect, error -117 Metadata corruption detected at 0x458f90, xfs_refcountbt block 0x180000000/0x1000 btree block 3/3 is suspect, error -117 Metadata corruption detected at 0x458f90, xfs_cntbt block 0x280000000/0x1000 btree block 5/5 is suspect, error -117 Metadata corruption detected at 0x458f90, xfs_refcountbt block 0x1fffffff8/0x1000 btree block 4/3 is suspect, error -117 Metadata corruption detected at 0x458f90, xfs_refcountbt block 0x100000008/0x1000 btree block 2/3 is suspect, error -117 Metadata corruption detected at 0x458f90, xfs_cntbt block 0x80000020/0x1000 btree block 1/5 is suspect, error -117 Metadata corruption detected at 0x458f90, xfs_inobt block 0xc0/0x1000 btree block 0/24 is suspect, error -117 Metadata corruption detected at 0x458f90, xfs_inobt block 0x17ffffff0/0x1000 btree block 3/1 is suspect, error -117 Metadata corruption detected at 0x458f90, xfs_refcountbt block 0x27ffffff0/0x1000 btree block 5/3 is suspect, error -117 Metadata corruption detected at 0x458f90, xfs_inobt block 0x1ffffffe8/0x1000 btree block 4/1 is suspect, error -117 Metadata corruption detected at 0x458f90, xfs_inobt block 0xfffffff8/0x1000 btree block 2/1 is suspect, error -117 Metadata corruption detected at 0x458f90, xfs_refcountbt block 0x80000010/0x1000 btree block 1/3 is suspect, error -117 Metadata corruption detected at 0x458f90, xfs_finobt block 0x17ffffff8/0x1000 btree block 3/2 is suspect, error -117 Metadata corruption detected at 0x458f90, xfs_inobt block 0x27fffffe0/0x1000 btree block 5/1 is suspect, error -117 Metadata corruption detected at 0x458f90, xfs_finobt block 0x1fffffff0/0x1000 btree block 4/2 is suspect, error -117 Metadata corruption detected at 0x458f90, xfs_finobt block 0x100000000/0x1000 btree block 2/2 is suspect, error -117 Metadata corruption detected at 0x458f90, xfs_inobt block 0x80000000/0x1000 btree block 1/1 is suspect, error -117 Metadata corruption detected at 0x458f90, xfs_finobt block 0x27fffffe8/0x1000 btree block 5/2 is suspect, error -117 Metadata corruption detected at 0x458f90, xfs_finobt block 0x80000008/0x1000 btree block 1/2 is suspect, error -117 Metadata corruption detected at 0x458f90, xfs_finobt block 0x132bf8/0x1000 btree block 0/157055 is suspect, error -117 undiscovered finobt record, ino 128 (0/128) root inode chunk not found Phase 3 - for each AG... - scan and clear agi unlinked lists... found inodes not in the inode allocation tree - process known inodes and perform inode discovery... - agno = 0 UUID mismatch on inode 128 UUID mismatch on inode 129 UUID mismatch on inode 130 UUID mismatch on inode 131 UUID mismatch on inode 132 UUID mismatch on inode 133 UUID mismatch on inode 134 UUID mismatch on inode 135 UUID mismatch on inode 136 UUID mismatch on inode 137 UUID mismatch on inode 138 UUID mismatch on inode 139 UUID mismatch on inode 140 UUID mismatch on inode 141 UUID mismatch on inode 142 UUID mismatch on inode 143 UUID mismatch on inode 144 UUID mismatch on inode 145 UUID mismatch on inode 146 UUID mismatch on inode 147 UUID mismatch on inode 148 UUID mismatch on inode 149 UUID mismatch on inode 150 UUID mismatch on inode 151 UUID mismatch on inode 152 UUID mismatch on inode 153 UUID mismatch on inode 154 UUID mismatch on inode 155 UUID mismatch on inode 156 UUID mismatch on inode 157 UUID mismatch on inode 158 UUID mismatch on inode 159 UUID mismatch on inode 160 UUID mismatch on inode 161 UUID mismatch on inode 162 UUID mismatch on inode 163 UUID mismatch on inode 164 UUID mismatch on inode 165 UUID mismatch on inode 166 UUID mismatch on inode 167 UUID mismatch on inode 168 UUID mismatch on inode 169 UUID mismatch on inode 170 UUID mismatch on inode 171 UUID mismatch on inode 172 UUID mismatch on inode 173 UUID mismatch on inode 174 UUID mismatch on inode 175 UUID mismatch on inode 176 UUID mismatch on inode 177 UUID mismatch on inode 178 UUID mismatch on inode 179 UUID mismatch on inode 180 UUID mismatch on inode 181 UUID mismatch on inode 182 UUID mismatch on inode 183 UUID mismatch on inode 184 UUID mismatch on inode 185 UUID mismatch on inode 186 UUID mismatch on inode 187 UUID mismatch on inode 188 UUID mismatch on inode 189 UUID mismatch on inode 190 UUID mismatch on inode 191 UUID mismatch on inode 128 cleared root inode 128 UUID mismatch on inode 129 cleared realtime bitmap inode 129 UUID mismatch on inode 130 cleared realtime summary inode 130 UUID mismatch on inode 131 cleared inode 131 UUID mismatch on inode 132 cleared inode 132 UUID mismatch on inode 133 cleared inode 133 UUID mismatch on inode 134 cleared inode 134 UUID mismatch on inode 135 cleared inode 135 UUID mismatch on inode 136 cleared inode 136 UUID mismatch on inode 137 cleared inode 137 UUID mismatch on inode 138 cleared inode 138 UUID mismatch on inode 139 cleared inode 139 UUID mismatch on inode 140 cleared inode 140 UUID mismatch on inode 141 cleared inode 141 UUID mismatch on inode 142 cleared inode 142 UUID mismatch on inode 143 cleared inode 143 UUID mismatch on inode 144 cleared inode 144 UUID mismatch on inode 145 cleared inode 145 UUID mismatch on inode 146 cleared inode 146 UUID mismatch on inode 147 cleared inode 147 UUID mismatch on inode 148 cleared inode 148 UUID mismatch on inode 149 cleared inode 149 UUID mismatch on inode 150 cleared inode 150 UUID mismatch on inode 151 cleared inode 151 UUID mismatch on inode 152 cleared inode 152 UUID mismatch on inode 153 cleared inode 153 UUID mismatch on inode 154 cleared inode 154 UUID mismatch on inode 155 cleared inode 155 UUID mismatch on inode 156 cleared inode 156 UUID mismatch on inode 157 cleared inode 157 UUID mismatch on inode 158 cleared inode 158 UUID mismatch on inode 159 cleared inode 159 imap claims inode 160 is present, but inode cluster is sparse, correcting imap imap claims inode 161 is present, but inode cluster is sparse, correcting imap imap claims inode 162 is present, but inode cluster is sparse, correcting imap imap claims inode 163 is present, but inode cluster is sparse, correcting imap imap claims inode 164 is present, but inode cluster is sparse, correcting imap imap claims inode 165 is present, but inode cluster is sparse, correcting imap imap claims inode 166 is present, but inode cluster is sparse, correcting imap imap claims inode 167 is present, but inode cluster is sparse, correcting imap imap claims inode 168 is present, but inode cluster is sparse, correcting imap imap claims inode 169 is present, but inode cluster is sparse, correcting imap imap claims inode 170 is present, but inode cluster is sparse, correcting imap imap claims inode 171 is present, but inode cluster is sparse, correcting imap imap claims inode 172 is present, but inode cluster is sparse, correcting imap imap claims inode 173 is present, but inode cluster is sparse, correcting imap imap claims inode 174 is present, but inode cluster is sparse, correcting imap imap claims inode 175 is present, but inode cluster is sparse, correcting imap imap claims inode 176 is present, but inode cluster is sparse, correcting imap imap claims inode 177 is present, but inode cluster is sparse, correcting imap imap claims inode 178 is present, but inode cluster is sparse, correcting imap imap claims inode 179 is present, but inode cluster is sparse, correcting imap imap claims inode 180 is present, but inode cluster is sparse, correcting imap imap claims inode 181 is present, but inode cluster is sparse, correcting imap imap claims inode 182 is present, but inode cluster is sparse, correcting imap imap claims inode 183 is present, but inode cluster is sparse, correcting imap imap claims inode 184 is present, but inode cluster is sparse, correcting imap imap claims inode 185 is present, but inode cluster is sparse, correcting imap imap claims inode 186 is present, but inode cluster is sparse, correcting imap imap claims inode 187 is present, but inode cluster is sparse, correcting imap imap claims inode 188 is present, but inode cluster is sparse, correcting imap imap claims inode 189 is present, but inode cluster is sparse, correcting imap imap claims inode 190 is present, but inode cluster is sparse, correcting imap imap claims inode 191 is present, but inode cluster is sparse, correcting imap - agno = 1 - agno = 2 - agno = 3 - agno = 4 - agno = 5 - process newly discovered inodes... Phase 4 - check for duplicate blocks... - setting up duplicate extent list... root inode lost - check for inodes claiming duplicate blocks... - agno = 0 - agno = 1 - agno = 3 - agno = 4 - agno = 2 - agno = 5 Phase 5 - rebuild AG headers and trees... - agno = 0 - agno = 1 - agno = 2 - agno = 3 - agno = 4 - agno = 5 - reset superblock... Phase 6 - check inode connectivity... reinitializing root directory reinitializing realtime bitmap inode reinitializing realtime summary inode - resetting contents of realtime bitmap and summary inodes - traversing filesystem ... - agno = 0 - agno = 1 - agno = 2 - agno = 3 - agno = 4 - agno = 5 - traversal finished ... - moving disconnected inodes to lost+found ... Phase 7 - verify and correct link counts... SB summary counter sanity check failed Metadata corruption detected at 0x47c2cb, xfs_sb block 0x0/0x200 libxfs_bwrite: write verifier failed on xfs_sb bno 0x0/0x1 SB summary counter sanity check failed Metadata corruption detected at 0x47c2cb, xfs_sb block 0x0/0x200 libxfs_bwrite: write verifier failed on xfs_sb bno 0x0/0x1 xfs_repair: Releasing dirty buffer to free list! xfs_repair: Refusing to write a corrupt buffer to the data device! xfs_repair: Lost a write to the data device! fatal error -- File system metadata writeout failed, err=117. Re-run xfs_repair.
May 24, 20242 yr Community Expert With the array stopped run xfs_repair on the other disk, as of last diags it was sdc, if it's still that: xfs_repair -v /dev/sdc1
May 24, 20242 yr Author 17 minutes ago, JorgeB said: With the array stopped run xfs_repair on the other disk, as of last diags it was sdc, if it's still that: xfs_repair -v /dev/sdc1 oh ok that makes sense. i did (xfs_repair -v /dev/sdb) and it s now just spewing ....................... attached screen shotn of it Edited May 24, 20242 yr by Uncommon
May 24, 20242 yr Community Expert Not sure why you are doing it on /dev/sdb 1 hour ago, JorgeB said: xfs_repair -v /dev/sdc1
May 24, 20242 yr Author 16 minutes ago, JorgeB said: Not sure why you are doing it on /dev/sdb oh i did it as drive one is sdb i tried the sdc1 and and i keep getting fatal error im going to restart and try again ]
May 24, 20242 yr Community Expert If you get the fatal error with both sdb1 and sdc1 I'm afraid there's not much else we can do, remaining options would be to contact the xfs mailing list or use a file recovery app, like UFS explorer.
May 24, 20242 yr Author 1 hour ago, JorgeB said: If you get the fatal error with both sdb1 and sdc1 I'm afraid there's not much else we can do, remaining options would be to contact the xfs mailing list or use a file recovery app, like UFS explorer. ah well dang thank you anyway for everything
May 24, 20242 yr Author i suppose tomorrow ill download some xfs recovery software, ill give ufs ago, and just hope that goes well if not i suppose ill be restarting everything
May 27, 20242 yr Community Expert You don't specifically say whether or not you tried to repair sdb1. xfs_repair /dev/sdb is definitely the wrong command.
May 28, 20242 yr Author 14 hours ago, trurl said: You don't specifically say whether or not you tried to repair sdb1. xfs_repair /dev/sdb is definitely the wrong command. Oh ye I did try that and sdb1 both didn't work. I have wiped both now and have re starter everything I can. Thank you all for the help none the less
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.