dimtank

Bonjour Julien, à tous, Suite à la lecture de ce fil, j'aimerai savoir si tu peux m'aiguiller et si mon problème est similaire au tien. Suite à un reboot, mon serveur UNRAID ne boot plus à cause de ma clé USB, il ne détecte plus rien dessus (testée sur windows et mac). J'aimerai savoir si tu as eu ce problème là et si la "reconstruction" de la clé avec leur utilitaire est possible sans avoir fait de sauvegarde de cette clé. Pour info, j'ai une licence unraid. Merci pour ton éclairage.

Hello, I did a xfs_repair -nv command, here is the result : Phase 1 - find and verify superblock... - block cache size set to 644392 entries Phase 2 - using internal log - zero log... zero_log: head block 4 tail block 4 - scan filesystem freespace and inode maps... Metadata corruption detected at 0x43d200, xfs_agf block 0x17fffffe9/0x200 Metadata corruption detected at 0x468588, xfs_agi block 0x17fffffea/0x200 bad uuid 7ecda8e7-ab28-4cbb-ae49-359cafcf85a9 for agf 3 bad uuid 7ecda8e7-ab28-4cbb-ae49-359cafcf85a9 for agi 3 would reset bad agf for ag 3 would reset bad agi for ag 3 Metadata corruption detected at 0x43d200, xfs_agf block 0x1ffffffe1/0x200 Metadata corruption detected at 0x43d200, xfs_agf block 0xfffffff1/0x200bad uncorrected agheader 3, skipping ag... Metadata corruption detected at 0x468588, xfs_agi block 0xfffffff2/0x200 Metadata corruption detected at 0x468588, xfs_agi block 0x1ffffffe2/0x200 bad uuid 7ecda8e7-ab28-4cbb-ae49-359cafcf85a9 for agf 2 bad uuid 7ecda8e7-ab28-4cbb-ae49-359cafcf85a9 for agi 2 would reset bad agf for ag 2 bad uuid 7ecda8e7-ab28-4cbb-ae49-359cafcf85a9 for agf 4 bad uuid 7ecda8e7-ab28-4cbb-ae49-359cafcf85a9 for agi 4 would reset bad agf for ag 4 would reset bad agi for ag 4 bad uncorrected agheader 4, skipping ag... would reset bad agi for ag 2 bad uncorrected agheader 2, skipping ag... Metadata corruption detected at 0x43d200, xfs_agf block 0x2ffffffd1/0x200 Metadata corruption detected at 0x43d200, xfs_agf block 0x47fffffb9/0x200 Metadata corruption detected at 0x468588, xfs_agi block 0x2ffffffd2/0x200 bad uuid 7ecda8e7-ab28-4cbb-ae49-359cafcf85a9 for agf 6 bad uuid 7ecda8e7-ab28-4cbb-ae49-359cafcf85a9 for agi 6 would reset bad agf for ag 6 would reset bad agi for ag 6 bad uncorrected agheader 6, skipping ag... Metadata corruption detected at 0x468588, xfs_agi block 0x47fffffba/0x200 bad uuid 7ecda8e7-ab28-4cbb-ae49-359cafcf85a9 for agf 9 bad uuid 7ecda8e7-ab28-4cbb-ae49-359cafcf85a9 for agi 9 would reset bad agf for ag 9 would reset bad agi for ag 9 bad uncorrected agheader 9, skipping ag... Metadata corruption detected at 0x43d200, xfs_agf block 0x27fffffd9/0x200 Metadata corruption detected at 0x43d200, xfs_agf block 0x1/0x200Metadata corruption detected at 0x43d200, xfs_agf block 0x37fffffc9/0x200 Metadata corruption detected at 0x468588, xfs_agi block 0x27fffffda/0x200 Metadata corruption detected at 0x43d200, xfs_agf block 0x3ffffffc1/0x200 bad uuid 7ecda8e7-ab28-4cbb-ae49-359cafcf85a9 for agf 5 bad uuid 7ecda8e7-ab28-4cbb-ae49-359cafcf85a9 for agi 5 would reset bad agf for ag 5 would reset bad agi for ag 5 bad uncorrected agheader 5, skipping ag... Metadata corruption detected at 0x468588, xfs_agi block 0x3ffffffc2/0x200 bad uuid 7ecda8e7-ab28-4cbb-ae49-359cafcf85a9 for agf 8 bad uuid 7ecda8e7-ab28-4cbb-ae49-359cafcf85a9 for agi 8 would reset bad agf for ag 8 would reset bad agi for ag 8 Metadata corruption detected at 0x43d200, xfs_agf block 0x57fffffa9/0x200Metadata corruption detected at 0x468588, xfs_agi block 0x2/0x200 Metadata corruption detected at 0x468588, xfs_agi block 0x37fffffca/0x200 bad uuid 7ecda8e7-ab28-4cbb-ae49-359cafcf85a9 for agf 0 bad uuid 7ecda8e7-ab28-4cbb-ae49-359cafcf85a9 for agf 7 bad uuid 7ecda8e7-ab28-4cbb-ae49-359cafcf85a9 for agi 7 would reset bad agf for ag 7 would reset bad agi for ag 7 bad uncorrected agheader 7, skipping ag... bad uuid 7ecda8e7-ab28-4cbb-ae49-359cafcf85a9 for agi 0 would reset bad agf for ag 0 Metadata corruption detected at 0x468588, xfs_agi block 0x57fffffaa/0x200 bad uuid 7ecda8e7-ab28-4cbb-ae49-359cafcf85a9 for agf 11 bad uuid 7ecda8e7-ab28-4cbb-ae49-359cafcf85a9 for agi 11 would reset bad agf for ag 11 Metadata corruption detected at 0x43d200, xfs_agf block 0x7ffffff9/0x200would reset bad agi for ag 0 would reset bad agi for ag 11 bad uncorrected agheader 0, skipping ag... bad uncorrected agheader 11, skipping ag... bad uncorrected agheader 8, skipping ag... Metadata corruption detected at 0x43d200, xfs_agf block 0x5ffffffa1/0x200 Metadata corruption detected at 0x468588, xfs_agi block 0x7ffffffa/0x200 bad uuid 7ecda8e7-ab28-4cbb-ae49-359cafcf85a9 for agf 1 Metadata corruption detected at 0x468588, xfs_agi block 0x5ffffffa2/0x200bad uuid 7ecda8e7-ab28-4cbb-ae49-359cafcf85a9 for agi 1 Metadata corruption detected at 0x43d200, xfs_agf block 0x4ffffffb1/0x200 would reset bad agf for ag 1 would reset bad agi for ag 1 bad uncorrected agheader 1, skipping ag... bad uuid 7ecda8e7-ab28-4cbb-ae49-359cafcf85a9 for agf 12 bad uuid 7ecda8e7-ab28-4cbb-ae49-359cafcf85a9 for agi 12 would reset bad agf for ag 12 would reset bad agi for ag 12 bad uncorrected agheader 12, skipping ag... Metadata corruption detected at 0x468588, xfs_agi block 0x4ffffffb2/0x200 bad uuid 7ecda8e7-ab28-4cbb-ae49-359cafcf85a9 for agf 10 bad uuid 7ecda8e7-ab28-4cbb-ae49-359cafcf85a9 for agi 10 would reset bad agf for ag 10 would reset bad agi for ag 10 bad uncorrected agheader 10, skipping ag... sb_icount 64, counted 0 sb_ifree 3, counted 0 sb_fdblocks 3417539001, counted 0 root inode chunk not found Phase 3 - for each AG... - scan (but don't clear) agi unlinked lists... - 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 would clear root inode 128 UUID mismatch on inode 129 would clear realtime bitmap inode 129 UUID mismatch on inode 130 would clear realtime summary inode 130 UUID mismatch on inode 131 would have cleared inode 131 UUID mismatch on inode 132 would have cleared inode 132 UUID mismatch on inode 133 would have cleared inode 133 UUID mismatch on inode 134 would have cleared inode 134 UUID mismatch on inode 135 would have cleared inode 135 UUID mismatch on inode 136 would have cleared inode 136 UUID mismatch on inode 137 would have cleared inode 137 UUID mismatch on inode 138 would have cleared inode 138 UUID mismatch on inode 139 would have cleared inode 139 UUID mismatch on inode 140 would have cleared inode 140 UUID mismatch on inode 141 would have cleared inode 141 UUID mismatch on inode 142 would have cleared inode 142 UUID mismatch on inode 143 would have cleared inode 143 UUID mismatch on inode 144 would have cleared inode 144 UUID mismatch on inode 145 would have cleared inode 145 UUID mismatch on inode 146 would have cleared inode 146 UUID mismatch on inode 147 would have cleared inode 147 UUID mismatch on inode 148 would have cleared inode 148 UUID mismatch on inode 149 would have cleared inode 149 UUID mismatch on inode 150 would have cleared inode 150 UUID mismatch on inode 151 would have cleared inode 151 UUID mismatch on inode 152 would have cleared inode 152 UUID mismatch on inode 153 would have cleared inode 153 UUID mismatch on inode 154 would have cleared inode 154 UUID mismatch on inode 155 would have cleared inode 155 UUID mismatch on inode 156 would have cleared inode 156 UUID mismatch on inode 157 would have cleared inode 157 UUID mismatch on inode 158 would have cleared inode 158 UUID mismatch on inode 159 would have 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 - 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... root inode would be lost - check for inodes claiming duplicate blocks... - agno = 0 - agno = 1 - agno = 3 UUID mismatch on inode 128 would clear root inode 128 UUID mismatch on inode 129 - agno = 4 would clear realtime bitmap inode 129 - agno = 6 - agno = 7 UUID mismatch on inode 130 - agno = 8 - agno = 5 - agno = 9 would clear realtime summary inode 130 UUID mismatch on inode 131 - agno = 10 - agno = 12 - agno = 11 - agno = 2 would have cleared inode 131 UUID mismatch on inode 132 would have cleared inode 132 UUID mismatch on inode 133 would have cleared inode 133 UUID mismatch on inode 134 would have cleared inode 134 UUID mismatch on inode 135 would have cleared inode 135 UUID mismatch on inode 136 would have cleared inode 136 UUID mismatch on inode 137 would have cleared inode 137 UUID mismatch on inode 138 would have cleared inode 138 UUID mismatch on inode 139 would have cleared inode 139 UUID mismatch on inode 140 would have cleared inode 140 UUID mismatch on inode 141 would have cleared inode 141 UUID mismatch on inode 142 would have cleared inode 142 UUID mismatch on inode 143 would have cleared inode 143 UUID mismatch on inode 144 would have cleared inode 144 UUID mismatch on inode 145 would have cleared inode 145 UUID mismatch on inode 146 would have cleared inode 146 UUID mismatch on inode 147 would have cleared inode 147 UUID mismatch on inode 148 would have cleared inode 148 UUID mismatch on inode 149 would have cleared inode 149 UUID mismatch on inode 150 would have cleared inode 150 UUID mismatch on inode 151 would have cleared inode 151 UUID mismatch on inode 152 would have cleared inode 152 UUID mismatch on inode 153 would have cleared inode 153 UUID mismatch on inode 154 would have cleared inode 154 UUID mismatch on inode 155 would have cleared inode 155 UUID mismatch on inode 156 would have cleared inode 156 UUID mismatch on inode 157 would have cleared inode 157 UUID mismatch on inode 158 would have cleared inode 158 UUID mismatch on inode 159 would have cleared inode 159 No modify flag set, skipping phase 5 Phase 6 - check inode connectivity... would reinitialize root directory would reinitialize realtime bitmap inode would reinitialize realtime summary inode - traversing filesystem ... - agno = 0 - agno = 1 - agno = 2 - agno = 3 - agno = 4 - agno = 5 - agno = 6 - agno = 7 - agno = 8 - agno = 9 - agno = 10 - agno = 11 - agno = 12 - traversal finished ... - moving disconnected inodes to lost+found ... Phase 7 - verify link counts... No modify flag set, skipping filesystem flush and exiting. XFS_REPAIR Summary Mon Mar 6 15:15:46 2023 Phase Start End Duration Phase 1: 03/06 15:15:46 03/06 15:15:46 Phase 2: 03/06 15:15:46 03/06 15:15:46 Phase 3: 03/06 15:15:46 03/06 15:15:46 Phase 4: 03/06 15:15:46 03/06 15:15:46 Phase 5: Skipped Phase 6: 03/06 15:15:46 03/06 15:15:46 Phase 7: 03/06 15:15:46 03/06 15:15:46 Then xfs_repair -v : Phase 1 - find and verify superblock... - block cache size set to 644392 entries Phase 2 - using internal log - zero log... zero_log: head block 4 tail block 4 - scan filesystem freespace and inode maps... Metadata corruption detected at 0x43d200, xfs_agf block 0x7ffffff9/0x200 Metadata corruption detected at 0x43d200, xfs_agf block 0xfffffff1/0x200 Metadata corruption detected at 0x43d200, xfs_agf block 0x1ffffffe1/0x200 Metadata corruption detected at 0x468588, xfs_agi block 0x7ffffffa/0x200 Metadata corruption detected at 0x468588, xfs_agi block 0xfffffff2/0x200 bad uuid 7ecda8e7-ab28-4cbb-ae49-359cafcf85a9 for agf 1 bad uuid 7ecda8e7-ab28-4cbb-ae49-359cafcf85a9 for agf 2 bad uuid 7ecda8e7-ab28-4cbb-ae49-359cafcf85a9 for agi 2 reset bad agf for ag 2 reset bad agi for ag 2 Metadata corruption detected at 0x468588, xfs_agi block 0x1ffffffe2/0x200 bad uuid 7ecda8e7-ab28-4cbb-ae49-359cafcf85a9 for agf 4 bad uuid 7ecda8e7-ab28-4cbb-ae49-359cafcf85a9 for agi 4 reset bad agf for ag 4 reset bad agi for ag 4 Metadata corruption detected at 0x43cea8, xfs_agfl block 0xfffffff3/0x200 bad uuid 7ecda8e7-ab28-4cbb-ae49-359cafcf85a9 for agi 1 reset bad agf for ag 1 reset bad agi for ag 1 Metadata corruption detected at 0x43cea8, xfs_agfl block 0x1ffffffe3/0x200 Metadata corruption detected at 0x43d200, xfs_agf block 0x2ffffffd1/0x200 Metadata corruption detected at 0x43d200, xfs_agf block 0x17fffffe9/0x200 Metadata corruption detected at 0x468588, xfs_agi block 0x2ffffffd2/0x200 Metadata corruption detected at 0x43d200, xfs_agf block 0x27fffffd9/0x200 bad uuid 7ecda8e7-ab28-4cbb-ae49-359cafcf85a9 for agf 6 Metadata corruption detected at 0x468588, xfs_agi block 0x17fffffea/0x200 Metadata corruption detected at 0x4579a0, xfs_bnobt block 0x200000000/0x1000 btree block 4/4 is suspect, error -117 Metadata corruption detected at 0x4579a0, xfs_bnobt block 0x100000010/0x1000Metadata corruption detected at 0x468588, xfs_agi block 0x27fffffda/0x200 bad uuid 7ecda8e7-ab28-4cbb-ae49-359cafcf85a9 for agf 5 btree block 2/4 is suspect, error -117 bad uuid 7ecda8e7-ab28-4cbb-ae49-359cafcf85a9 for agi 5 reset bad agf for ag 5 reset bad agi for ag 5 bad uuid 7ecda8e7-ab28-4cbb-ae49-359cafcf85a9 for agi 6 reset bad agf for ag 6 reset bad agi for ag 6 bad uuid 7ecda8e7-ab28-4cbb-ae49-359cafcf85a9 for agf 3 bad uuid 7ecda8e7-ab28-4cbb-ae49-359cafcf85a9 for agi 3 reset bad agf for ag 3 reset bad agi for ag 3 Metadata corruption detected at 0x43d200, xfs_agf block 0x5ffffffa1/0x200 Metadata corruption detected at 0x43cea8, xfs_agfl block 0x7ffffffb/0x200 Metadata corruption detected at 0x43cea8, xfs_agfl block 0x17fffffeb/0x200 Metadata corruption detected at 0x43cea8, xfs_agfl block 0x2ffffffd3/0x200 Metadata corruption detected at 0x43d200, xfs_agf block 0x1/0x200Metadata corruption detected at 0x4579a0, xfs_cntbt block 0x200000008/0x1000 btree block 4/5 is suspect, error -117 Metadata corruption detected at 0x43d200, xfs_agf block 0x4ffffffb1/0x200 Metadata corruption detected at 0x43d200, xfs_agf block 0x47fffffb9/0x200 Metadata corruption detected at 0x468588, xfs_agi block 0x5ffffffa2/0x200 Metadata corruption detected at 0x43d200, xfs_agf block 0x3ffffffc1/0x200 Metadata corruption detected at 0x4579a0, xfs_bnobt block 0x80000018/0x1000 btree block 1/4 is suspect, error -117 Metadata corruption detected at 0x4579a0, xfs_bnobt block 0x180000008/0x1000 btree block 3/4 is suspect, error -117 Metadata corruption detected at 0x468588, xfs_agi block 0x3ffffffc2/0x200 bad uuid 7ecda8e7-ab28-4cbb-ae49-359cafcf85a9 for agf 8 bad uuid 7ecda8e7-ab28-4cbb-ae49-359cafcf85a9 for agi 8 reset bad agf for ag 8 Metadata corruption detected at 0x4579a0, xfs_cntbt block 0x100000018/0x1000 reset bad agi for ag 8 Metadata corruption detected at 0x4579a0, xfs_cntbt block 0x80000020/0x1000 Metadata corruption detected at 0x468588, xfs_agi block 0x47fffffba/0x200Metadata corruption detected at 0x468588, xfs_agi block 0x4ffffffb2/0x200 Metadata corruption detected at 0x4579a0, xfs_refcountbt block 0x1fffffff8/0x1000bad uuid 7ecda8e7-ab28-4cbb-ae49-359cafcf85a9 for agf 10 bad uuid 7ecda8e7-ab28-4cbb-ae49-359cafcf85a9 for agi 10 reset bad agf for ag 10 reset bad agi for ag 10 bad uuid 7ecda8e7-ab28-4cbb-ae49-359cafcf85a9 for agf 12 bad uuid 7ecda8e7-ab28-4cbb-ae49-359cafcf85a9 for agi 12 reset bad agf for ag 12 Metadata corruption detected at 0x4579a0, xfs_cntbt block 0x180000010/0x1000Metadata corruption detected at 0x4579a0, xfs_bnobt block 0x2fffffff0/0x1000bad uuid 7ecda8e7-ab28-4cbb-ae49-359cafcf85a9 for agf 9 btree block 1/5 is suspect, error -117 Metadata corruption detected at 0x43cea8, xfs_agfl block 0x4ffffffb3/0x200Metadata corruption detected at 0x43d200, xfs_agf block 0x57fffffa9/0x200btree block 2/5 is suspect, error -117 Metadata corruption detected at 0x43d200, xfs_agf block 0x37fffffc9/0x200 btree block 4/3 is suspect, error -117 Metadata corruption detected at 0x468588, xfs_agi block 0x2/0x200btree block 3/5 is suspect, error -117 Metadata corruption detected at 0x43cea8, xfs_agfl block 0x3ffffffc3/0x200bad uuid 7ecda8e7-ab28-4cbb-ae49-359cafcf85a9 for agi 9 Metadata corruption detected at 0x468588, xfs_agi block 0x57fffffaa/0x200reset bad agf for ag 9 reset bad agi for ag 12 Metadata corruption detected at 0x43cea8, xfs_agfl block 0x27fffffdb/0x200bad uuid 7ecda8e7-ab28-4cbb-ae49-359cafcf85a9 for agf 11 bad uuid 7ecda8e7-ab28-4cbb-ae49-359cafcf85a9 for agi 11 Metadata corruption detected at 0x4579a0, xfs_refcountbt block 0x80000010/0x1000Metadata corruption detected at 0x468588, xfs_agi block 0x37fffffca/0x200 reset bad agf for ag 11 btree block 6/4 is suspect, error -117 reset bad agi for ag 11 Metadata corruption detected at 0x4579a0, xfs_refcountbt block 0x100000008/0x1000 btree block 2/3 is suspect, error -117 Metadata corruption detected at 0x4579a0, xfs_bnobt block 0x4ffffffd0/0x1000Metadata corruption detected at 0x4579a0, xfs_inobt block 0x1ffffffe8/0x1000 reset bad agi for ag 9 Metadata corruption detected at 0x43cea8, xfs_agfl block 0x5ffffffa3/0x200Metadata corruption detected at 0x4579a0, xfs_cntbt block 0x2fffffff8/0x1000 Metadata corruption detected at 0x43cea8, xfs_agfl block 0x47fffffbb/0x200 bad uuid 7ecda8e7-ab28-4cbb-ae49-359cafcf85a9 for agf 0 bad uuid 7ecda8e7-ab28-4cbb-ae49-359cafcf85a9 for agi 0 btree block 6/5 is suspect, error -117 btree block 10/4 is suspect, error -117 Metadata corruption detected at 0x4579a0, xfs_inobt block 0xfffffff8/0x1000 btree block 2/1 is suspect, error -117 btree block 4/1 is suspect, error -117 bad uuid 7ecda8e7-ab28-4cbb-ae49-359cafcf85a9 for agf 7 bad uuid 7ecda8e7-ab28-4cbb-ae49-359cafcf85a9 for agi 7 Metadata corruption detected at 0x4579a0, xfs_bnobt block 0x3ffffffe0/0x1000Metadata corruption detected at 0x4579a0, xfs_bnobt block 0x47fffffd8/0x1000Metadata corruption detected at 0x4579a0, xfs_bnobt block 0x5ffffffc0/0x1000 Metadata corruption detected at 0x4579a0, xfs_refcountbt block 0x2ffffffe8/0x1000Metadata corruption detected at 0x43cea8, xfs_agfl block 0x57fffffab/0x200 Metadata corruption detected at 0x4579a0, xfs_cntbt block 0x4ffffffd8/0x1000btree block 6/3 is suspect, error -117 btree block 12/4 is suspect, error -117 Metadata corruption detected at 0x4579a0, xfs_bnobt block 0x27ffffff8/0x1000 btree block 5/4 is suspect, error -117 btree block 1/3 is suspect, error -117 reset bad agf for ag 7 btree block 9/4 is suspect, error -117 Metadata corruption detected at 0x4579a0, xfs_finobt block 0x1fffffff0/0x1000Metadata corruption detected at 0x4579a0, xfs_bnobt block 0x57fffffc8/0x1000reset bad agi for ag 7 Metadata corruption detected at 0x4579a0, xfs_inobt block 0x80000000/0x1000 btree block 8/4 is suspect, error -117 Metadata corruption detected at 0x4579a0, xfs_cntbt block 0x280000000/0x1000Metadata corruption detected at 0x4579a0, xfs_cntbt block 0x5ffffffc8/0x1000 btree block 11/4 is suspect, error -117 btree block 1/1 is suspect, error -117 Metadata corruption detected at 0x4579a0, xfs_refcountbt block 0x180000000/0x1000 Metadata corruption detected at 0x4579a0, xfs_finobt block 0x100000000/0x1000btree block 12/5 is suspect, error -117 btree block 5/5 is suspect, error -117 btree block 10/5 is suspect, error -117 Metadata corruption detected at 0x4579a0, xfs_finobt block 0x80000008/0x1000 btree block 1/2 is suspect, error -117 Metadata corruption detected at 0x4579a0, xfs_cntbt block 0x47fffffe0/0x1000 Metadata corruption detected at 0x4579a0, xfs_cntbt block 0x57fffffd0/0x1000 Metadata corruption detected at 0x4579a0, xfs_refcountbt block 0x5ffffffb8/0x1000 Metadata corruption detected at 0x4579a0, xfs_cntbt block 0x3ffffffe8/0x1000btree block 12/3 is suspect, error -117 btree block 9/5 is suspect, error -117 Metadata corruption detected at 0x4579a0, xfs_inobt block 0x2ffffffd8/0x1000 btree block 6/1 is suspect, error -117 Metadata corruption detected at 0x43cea8, xfs_agfl block 0x37fffffcb/0x200 Metadata corruption detected at 0x4579a0, xfs_refcountbt block 0x27ffffff0/0x1000 btree block 5/3 is suspect, error -117 btree block 11/5 is suspect, error -117 Metadata corruption detected at 0x4579a0, xfs_finobt block 0x2ffffffe0/0x1000 btree block 6/2 is suspect, error -117 Metadata corruption detected at 0x4579a0, xfs_refcountbt block 0x4ffffffc8/0x1000 Metadata corruption detected at 0x4579a0, xfs_refcountbt block 0x47fffffd0/0x1000 Metadata corruption detected at 0x4579a0, xfs_inobt block 0x5ffffffa8/0x1000 Metadata corruption detected at 0x4579a0, xfs_refcountbt block 0x57fffffc0/0x1000btree block 12/1 is suspect, error -117 btree block 9/3 is suspect, error -117 btree block 4/2 is suspect, error -117 reset bad agf for ag 0 btree block 10/3 is suspect, error -117 Metadata corruption detected at 0x4579a0, xfs_inobt block 0x27fffffe0/0x1000 btree block 11/3 is suspect, error -117 btree block 5/1 is suspect, error -117 btree block 3/3 is suspect, error -117 Metadata corruption detected at 0x4579a0, xfs_bnobt block 0x37fffffe8/0x1000 Metadata corruption detected at 0x4579a0, xfs_inobt block 0x47fffffc0/0x1000 btree block 7/4 is suspect, error -117 btree block 2/2 is suspect, error -117 Metadata corruption detected at 0x4579a0, xfs_inobt block 0x57fffffb0/0x1000 btree block 11/1 is suspect, error -117 Metadata corruption detected at 0x4579a0, xfs_inobt block 0x17ffffff0/0x1000Metadata corruption detected at 0x4579a0, xfs_finobt block 0x5ffffffb0/0x1000btree block 9/1 is suspect, error -117 Metadata corruption detected at 0x4579a0, xfs_inobt block 0x4ffffffb8/0x1000btree block 8/5 is suspect, error -117 Metadata corruption detected at 0x4579a0, xfs_cntbt block 0x37ffffff0/0x1000 Metadata corruption detected at 0x4579a0, xfs_finobt block 0x27fffffe8/0x1000btree block 10/1 is suspect, error -117 Metadata corruption detected at 0x4579a0, xfs_finobt block 0x57fffffb8/0x1000 reset bad agi for ag 0 btree block 7/5 is suspect, error -117 btree block 3/1 is suspect, error -117 btree block 12/2 is suspect, error -117 Metadata corruption detected at 0x4579a0, xfs_finobt block 0x47fffffc8/0x1000Metadata corruption detected at 0x4579a0, xfs_refcountbt block 0x3ffffffd8/0x1000btree block 5/2 is suspect, error -117 Metadata corruption detected at 0x4579a0, xfs_finobt block 0x4ffffffc0/0x1000 btree block 11/2 is suspect, error -117 btree block 10/2 is suspect, error -117 btree block 9/2 is suspect, error -117 btree block 8/3 is suspect, error -117 Metadata corruption detected at 0x43cea8, xfs_agfl block 0x3/0x200 Metadata corruption detected at 0x4579a0, xfs_refcountbt block 0x37fffffe0/0x1000 btree block 7/3 is suspect, error -117 Metadata corruption detected at 0x4579a0, xfs_finobt block 0x17ffffff8/0x1000 btree block 3/2 is suspect, error -117 Metadata corruption detected at 0x4579a0, xfs_inobt block 0x3ffffffc8/0x1000 btree block 8/1 is suspect, error -117 Metadata corruption detected at 0x4579a0, xfs_inobt block 0x37fffffd0/0x1000 btree block 7/1 is suspect, error -117 Metadata corruption detected at 0x4579a0, xfs_finobt block 0x3ffffffd0/0x1000 btree block 8/2 is suspect, error -117 Metadata corruption detected at 0x4579a0, xfs_finobt block 0x37fffffd8/0x1000 btree block 7/2 is suspect, error -117 Metadata corruption detected at 0x4579a0, xfs_bnobt block 0x3190/0x1000 btree block 0/1586 is suspect, error -117 Metadata corruption detected at 0x4579a0, xfs_cntbt block 0x3198/0x1000 btree block 0/1587 is suspect, error -117 Metadata corruption detected at 0x4579a0, xfs_refcountbt block 0x3188/0x1000 btree block 0/1585 is suspect, error -117 Metadata corruption detected at 0x4579a0, xfs_inobt block 0xc0/0x1000 btree block 0/24 is suspect, error -117 Metadata corruption detected at 0x4579a0, xfs_finobt block 0x3180/0x1000 btree block 0/1584 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 - 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... root inode lost - check for inodes claiming duplicate blocks... - agno = 0 - agno = 2 - agno = 1 - agno = 5 - agno = 4 - agno = 7 - agno = 8 - agno = 9 - agno = 10 - agno = 6 - agno = 3 - agno = 11 - agno = 12 Phase 5 - rebuild AG headers and trees... - agno = 0 - agno = 1 - agno = 2 - agno = 3 - agno = 4 - agno = 5 - agno = 6 - agno = 7 - agno = 8 - agno = 9 - agno = 10 - agno = 11 - agno = 12 - 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 - agno = 6 - agno = 7 - agno = 8 - agno = 9 - agno = 10 - agno = 11 - agno = 12 - 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 0x47a15b, 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 0x47a15b, 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. and then I did a xfs-repair -v again : Phase 1 - find and verify superblock... - block cache size set to 644392 entries Phase 2 - using internal log - zero log... zero_log: head block 4 tail block 4 - scan filesystem freespace and inode maps... clearing needsrepair flag and regenerating metadata sb_icount 64, counted 32 sb_ifree 3, counted 29 sb_fdblocks 3417539001, counted 3417573793 - found root inode chunk Phase 3 - for each AG... - scan and clear agi unlinked lists... - process known inodes and perform inode discovery... - agno = 0 - 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 = 1 - agno = 3 - agno = 2 - agno = 4 - agno = 6 - agno = 8 - agno = 7 - agno = 10 - agno = 11 - agno = 12 - agno = 5 - agno = 9 Phase 5 - rebuild AG headers and trees... - agno = 0 - agno = 1 - agno = 2 - agno = 3 - agno = 4 - agno = 5 - agno = 6 - agno = 7 - agno = 8 - agno = 9 - agno = 10 - agno = 11 - agno = 12 - reset superblock... Phase 6 - check inode connectivity... - resetting contents of realtime bitmap and summary inodes - traversing filesystem ... - agno = 0 - agno = 1 - agno = 2 - agno = 3 - agno = 4 - agno = 5 - agno = 6 - agno = 7 - agno = 8 - agno = 9 - agno = 10 - agno = 11 - agno = 12 - 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 0x47a15b, 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 0x47a15b, 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. Looks like I should try a testdisk now ? Or start a Parity-Check and write corrections to parity ? What do you think ? Thanks a lot.

Hello, After some mistakes manipulations with disks I got "Unmountable: Wrong or no file system". Attached are diagnostics if someone can advise me. Thanks a lot. unraid-dt-diagnostics-20230227-1153.zip

Bonjour à tous, J'ai un petit casse-tête à soumettre. Contexte: J'ai 4 HDD (2 x 14To, dont 1 de parité et 2x 2To), un cache ssd et ma flash. 1 disque de 2To était défaillant et m'affichait toujours des erreurs. je souhaitais donc le remplacer mais par un disque plus petit de 1,5 To. Résumons mes bêtises : - Retrait du disque de 2To et remplacement par le disque de 1,5 To (plus petit) - Inversion de mon 1er disque de parité avec mon second disque de données - Avant de m'apercevoir de mon inversion j'ai lancé "new config" et lancé ce qui semble une reconstruction de la parité. - Redémarrage de mon serveur et certainement la perte du syslog J'en suis à présent à remettre ma config initiale de cette manière : et tenter de voir ce qui est récupérable... Je me retrouve face à mon disk 1 de 14 To qui contenait la majeur partie de mes données : Voilà, Dois-je lancer un "check" (Check will start Read-Check of all array disks.) Y a-t-il un moyen de récupérer les données du disque ? Dois-je tenter de monter ce disque au format xfs dans un OS linux et jouer avec un utilitaire style dd et xfs_repair ? Souhaitais-je vraiment flinguer mon serveur ? Merci beaucoup pour vos conseils.