December 27, 20223 yr Author root@Monstruo:~# xfs_repair -n /dev/sdx1 Phase 1 - find and verify superblock... Phase 2 - using internal log - zero log... ALERT: The filesystem has valuable metadata changes in a log which is being ignored because the -n option was used. Expect spurious inconsistencies which may be resolved by first mounting the filesystem to replay the log. - scan filesystem freespace and inode maps... Metadata CRC error detected at 0x44108d, xfs_bnobt block 0xe8e05f38/0x1000 btree block 2/1 is suspect, error -74 bad magic # 0x4fc37090 in btbno block 2/1 Metadata CRC error detected at 0x44108d, xfs_cntbt block 0xe8e05f40/0x1000 btree block 2/2 is suspect, error -74 bad magic # 0x6df45080 in btcnt block 2/2 agf_freeblks 10312971, counted 0 in ag 2 agf_longest 2916269, counted 0 in ag 2 Metadata CRC error detected at 0x44108d, xfs_bnobt block 0x74702fa0/0x1000 btree block 1/1 is suspect, error -74 bad magic # 0xfcaf665b in btbno block 1/1 Metadata CRC error detected at 0x46fd5d, xfs_inobt block 0xe8e05f48/0x1000 btree block 2/3 is suspect, error -74 bad magic # 0xa6f13819 in inobt block 2/3 Metadata CRC error detected at 0x46fd5d, xfs_inobt block 0x15d508ee0/0x1000 btree block 3/3 is suspect, error -74 bad magic # 0xdedcec39 in inobt block 3/3 Metadata CRC error detected at 0x44108d, xfs_cntbt block 0x74702fa8/0x1000 btree block 1/2 is suspect, error -74 bad magic # 0xecf7febd in btcnt block 1/2 agf_freeblks 15647096, counted 0 in ag 1 agf_longest 7341807, counted 0 in ag 1 inode chunk claims untracked block, finobt block - agno 2, bno 476940, inopb 8 inode chunk claims untracked block, finobt block - agno 2, bno 476941, inopb 8 inode chunk claims untracked block, finobt block - agno 2, bno 476942, inopb 8 inode chunk claims untracked block, finobt block - agno 2, bno 476943, inopb 8 inode chunk claims untracked block, finobt block - agno 2, bno 476944, inopb 8 inode chunk claims untracked block, finobt block - agno 2, bno 476945, inopb 8 inode chunk claims untracked block, finobt block - agno 2, bno 476946, inopb 8 inode chunk claims untracked block, finobt block - agno 2, bno 476947, inopb 8 undiscovered finobt record, ino 4298782816 (2/3815520) undiscovered finobt record, ino 4305958752 (2/10991456) undiscovered finobt record, ino 4305975552 (2/11008256) undiscovered finobt record, ino 4305982944 (2/11015648) undiscovered finobt record, ino 4305983296 (2/11016000) undiscovered finobt record, ino 4341756096 (2/46788800) undiscovered finobt record, ino 4341756864 (2/46789568) undiscovered finobt record, ino 4341790048 (2/46822752) undiscovered finobt record, ino 4341804896 (2/46837600) undiscovered finobt record, ino 4341837440 (2/46870144) inode chunk claims untracked block, finobt block - agno 3, bno 3467496, inopb 8 inode chunk claims untracked block, finobt block - agno 3, bno 3467497, inopb 8 inode chunk claims untracked block, finobt block - agno 3, bno 3467498, inopb 8 inode chunk claims untracked block, finobt block - agno 3, bno 3467499, inopb 8 inode chunk claims untracked block, finobt block - agno 3, bno 3467500, inopb 8 inode chunk claims untracked block, finobt block - agno 3, bno 3467501, inopb 8 inode chunk claims untracked block, finobt block - agno 3, bno 3467502, inopb 8 inode chunk claims untracked block, finobt block - agno 3, bno 3467503, inopb 8 undiscovered finobt record, ino 4341839424 (2/46872128) undiscovered finobt record, ino 6470190912 (3/27739968) undiscovered finobt record, ino 4350566592 (2/55599296) undiscovered finobt record, ino 6470191808 (3/27740864) undiscovered finobt record, ino 4361066432 (2/66099136) undiscovered finobt record, ino 6502355808 (3/59904864) undiscovered finobt record, ino 4372845952 (2/77878656) undiscovered finobt record, ino 6502356960 (3/59906016) undiscovered finobt record, ino 4373009184 (2/78041888) undiscovered finobt record, ino 6502357728 (3/59906784) undiscovered finobt record, ino 5096362720 (2/801395424) undiscovered finobt record, ino 6502358368 (3/59907424) agi_count 8960, counted 0 in ag 2 undiscovered finobt record, ino 6502363488 (3/59912544) agi_freecount 103, counted 0 in ag 2 undiscovered finobt record, ino 6510636512 (3/68185568) undiscovered finobt record, ino 6662690336 (3/220239392) undiscovered finobt record, ino 6662690976 (3/220240032) undiscovered finobt record, ino 7015763712 (3/573312768) Metadata CRC error detected at 0x46fd5d, xfs_inobt block 0x74702fb0/0x1000 undiscovered finobt record, ino 7312148512 (3/869697568) btree block 1/3 is suspect, error -74 bad magic # 0xf5625fc6 in inobt block 1/3 agi_count 7296, counted 0 in ag 3 agi_freecount 84, counted 0 in ag 3 inode chunk claims untracked block, finobt block - agno 1, bno 1000280, inopb 8 inode chunk claims untracked block, finobt block - agno 1, bno 1000281, inopb 8 inode chunk claims untracked block, finobt block - agno 1, bno 1000282, inopb 8 inode chunk claims untracked block, finobt block - agno 1, bno 1000283, inopb 8 inode chunk claims untracked block, finobt block - agno 1, bno 1000284, inopb 8 inode chunk claims untracked block, finobt block - agno 1, bno 1000285, inopb 8 inode chunk claims untracked block, finobt block - agno 1, bno 1000286, inopb 8 inode chunk claims untracked block, finobt block - agno 1, bno 1000287, inopb 8 undiscovered finobt record, ino 2155485888 (1/8002240) undiscovered finobt record, ino 2155487040 (1/8003392) undiscovered finobt record, ino 2155734272 (1/8250624) undiscovered finobt record, ino 2258856128 (1/111372480) undiscovered finobt record, ino 2258858304 (1/111374656) undiscovered finobt record, ino 2258864608 (1/111380960) undiscovered finobt record, ino 2258865280 (1/111381632) undiscovered finobt record, ino 2258866528 (1/111382880) undiscovered finobt record, ino 2258878368 (1/111394720) undiscovered finobt record, ino 2258878912 (1/111395264) undiscovered finobt record, ino 2258879936 (1/111396288) undiscovered finobt record, ino 2258906336 (1/111422688) undiscovered finobt record, ino 2266728864 (1/119245216) undiscovered finobt record, ino 2266744800 (1/119261152) undiscovered finobt record, ino 2267221856 (1/119738208) undiscovered finobt record, ino 2267231936 (1/119748288) undiscovered finobt record, ino 2267528896 (1/120045248) agi_count 4800, counted 0 in ag 1 agi_freecount 71, counted 0 in ag 1 sb_icount 32704, counted 11648 sb_ifree 426, counted 168 sb_fdblocks 539327502, counted 514834453 - found root inode chunk Phase 3 - for each AG... - scan (but don't clear) agi unlinked lists... found inodes not in the inode allocation tree
December 27, 20223 yr Community Expert A xfs filesystem exists in that disk, but it's not being identified as one, hence the UD issue, also looks like the fs has corruption, but lets see if it can be mounted first to replay the log: mkdir /x mount -v -t xfs /dev/sdx1 /x
December 27, 20223 yr Author Sorry but I had to restart the server... Now is (sdt)monstruo-diagnostics-20221227-2040.zip
December 27, 20223 yr Community Expert 34 minutes ago, gideva said: Now is (sdt) Then change the command to sdt 1 hour ago, JorgeB said: A xfs filesystem exists in that disk, but it's not being identified as one, hence the UD issue, also looks like the fs has corruption, but lets see if it can be mounted first to replay the log: mkdir /x mount -v -t xfs /dev/sdt1 /x
December 28, 20223 yr Author This is what I got: root@Monstruo:~# mkdir /x root@Monstruo:~# mount -v -t xfs /dev/sdt1 /x mount: /x: wrong fs type, bad option, bad superblock on /dev/sdt1, missing codepage or helper program, or other error. dmesg(1) may have more information after failed mount system call. root@Monstruo:~#
December 28, 20223 yr Author root@Monstruo:~# xfs_repair -v /dev/sdt1 Phase 1 - find and verify superblock... bad primary superblock - bad magic number !!! attempting to find secondary superblock... .found candidate secondary superblock... verified secondary superblock... writing modified primary superblock - block cache size set to 1496280 entries sb realtime bitmap inode value 18446744073709551615 (NULLFSINO) inconsistent with calculated value 97 resetting superblock realtime bitmap inode pointer to 97 sb realtime summary inode value 18446744073709551615 (NULLFSINO) inconsistent with calculated value 98 resetting superblock realtime summary inode pointer to 98 Phase 2 - using internal log - zero log... zero_log: head block 2492958 tail block 2492954 ERROR: The filesystem has valuable metadata changes in a log which needs to be replayed. Mount the filesystem to replay the log, and unmount it before re-running xfs_repair. If you are unable to mount the filesystem, then use the -L option to destroy the log and attempt a repair. Note that destroying the log may cause corruption -- please attempt a mount of the filesystem before doing this. root@Monstruo:~#
December 28, 20223 yr Author Now the MOUNT option is not gray anymore but if I selct it it does not mount anyway the disk... I used the -L option and this is what I got root@Monstruo:~# xfs_repair -v /dev/sdt1 -L Phase 1 - find and verify superblock... - block cache size set to 1496272 entries Phase 2 - using internal log - zero log... zero_log: head block 2492970 tail block 2492970 xfs_repair: libxfs_device_zero write failed: Input/output error root@Monstruo:~#
December 28, 20223 yr Author Here the diags if you need it for any reason monstruo-diagnostics-20221228-1350.zip
December 28, 20223 yr Community Expert 28 minutes ago, gideva said: Input/output error This is usually is a disk read/write error, and there are logged errors in the syslog, try replacing/swapping cables for that disk (both power and SATA) and run it again.
December 28, 20223 yr Author root@Monstruo:~# xfs_repair -v /dev/sdt1 -L Phase 1 - find and verify superblock... - block cache size set to 1496272 entries Phase 2 - using internal log - zero log... totally zeroed log zero_log: head block 0 tail block 0
December 28, 20223 yr Community Expert Not seeing any disk errors for now, since UD now recognizes the fs check filesystem again using UD, by clicking on the small check mark below the disk, though the result will likely be the same.
December 28, 20223 yr Author Shall I post the result of the Files System check? It is a kind of long... Is there any way I can move the data out of the disk? I can see that he can recognize some folder and files but I do not have any idea on how I can access the disk
December 28, 20223 yr Community Expert 20 minutes ago, gideva said: It is a kind of long... text zips very nicely
December 28, 20223 yr Community Expert 22 minutes ago, gideva said: Shall I post the result of the Files System check? If it finished the repair without errors it's not really needed.
December 28, 20223 yr Community Expert 26 minutes ago, gideva said: Is there any way I can move the data out of the disk? If the disk mounts in UD, you can share it on the network to access its files. And Dynamix File Manager plugin will let you work with files directly on the server. UD mounts are in /mnt/disks.
December 28, 20223 yr Author Well... it seems full of error to me (but I cannot really tell). It is not mounting anyway... repair log.rtf
December 28, 20223 yr Community Expert xfs_repair: libxfs_device_zero write failed: Input/output error it's still failing, which is not unexpected since it's just a different way of running xfs_repair, since there are no disk errors it looks like a xfs_repair problem, it should always finish a filesystem repair, with more or less data loss, never abort, so looks like the fs is currently corrupt beyond repair, you could ask on the xfs mailing list to see if they can help.
December 28, 20223 yr Author Thanks for the patience and help! Will try there and see if I can do something
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.