-
Corrupt XFS filesystem
Thank you for your message Yes I tried a re-run multiple times. I just can't understand why the system seems to be so fragile. I understand I need to start all over, think I'm going to ditch Unraid and go back to the NAS I came from. This is such a dissapointment.
-
ictkris started following Corrupt XFS filesystem
-
Corrupt XFS filesystem
Hi all I installed Jellyfin and things started to go down. Tried to play an ISO file as I read this was possible and the whole system hung. After 5 hours it still hung, I could not even log in anymore. Saw no other option than to remove power and start again. After that problems were even worse: no more docker image all shares gone disk 1 cannot be used because of faulty file system Tried putting the array in mainentance mode and fix it but no solution. I must say that I lost a bit of trust: have 3 disks, one parity and one cache but all that is not even helping me to keep the system up. Can someone help me? Unraid starter 7.1.2 root@UNRAID:~# xfs_repair /dev/md1p1 Phase 1 - find and verify superblock... Phase 2 - using internal log - zero log... - scan filesystem freespace and inode maps... clearing needsrepair flag and regenerating metadata sb_icount 64, counted 32 sb_ifree 61, counted 29 sb_fdblocks 732208903, counted 732208907 - 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 - process newly discovered inodes... Phase 4 - check for duplicate blocks... - setting up duplicate extent list... - check for inodes claiming duplicate blocks... - agno = 1 - agno = 0 - agno = 2 - agno = 3 Phase 5 - rebuild AG headers and trees... - reset superblock... Phase 6 - check inode connectivity... - resetting contents of realtime bitmap and summary inodes - traversing filesystem ... - 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 0x49c4e5, 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 0x49c4e5, 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. unraid-diagnostics-20250608-1121.zip
-
ictkris joined the community
-
Corrupt XFS filesystem
Hi all I have installed Jellyfin and after trying to play a file it seems the whole system hung. I could not even log into the system, not even after 5hrs. There did not seem to be any other option than forcefully turning off. Now - once rebooting - I have following problems: no more shares no more docker images notification first disk is un readable - SMART seems to be OK. I tried running the array in maintenance mode and doing a disk check, this does not seem to fix it. Tried XFS_Repair in terminal of dev/md1p1 but same result. Must say that I am losing a bit my trust, have 3 disks + one parity and one cache but all that does not seem to keep me from losing everything. Thanks in advance Unraid starter 7.1.2 root@UNRAID:~# xfs_repair -v /dev/md1p1 Phase 1 - find and verify superblock... - block cache size set to 348728 entries Phase 2 - using internal log - zero log... zero_log: head block 0 tail block 0 - scan filesystem freespace and inode maps... clearing needsrepair flag and regenerating metadata sb_icount 64, counted 32 sb_ifree 61, counted 29 sb_fdblocks 732208903, counted 732208907 - 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 - 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 - agno = 3 Phase 5 - rebuild AG headers and trees... - agno = 0 - agno = 1 - agno = 2 - agno = 3 - 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 - 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 0x49c4e5, 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 0x49c4e5, 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.
ictkris
Members
-
Joined
-
Last visited