June 8, 20251 yr Hi allI 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 imageall shares gonedisk 1 cannot be used because of faulty file systemTried 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.2root@UNRAID:~# xfs_repair /dev/md1p1Phase 1 - find and verify superblock...Phase 2 - using internal log - zero log... - scan filesystem freespace and inode maps...clearing needsrepair flag and regenerating metadatasb_icount 64, counted 32sb_ifree 61, counted 29sb_fdblocks 732208903, counted 732208907 - found root inode chunkPhase 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 = 3Phase 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 failedMetadata corruption detected at 0x49c4e5, xfs_sb block 0x0/0x200libxfs_bwrite: write verifier failed on xfs_sb bno 0x0/0x1SB summary counter sanity check failedMetadata corruption detected at 0x49c4e5, xfs_sb block 0x0/0x200libxfs_bwrite: write verifier failed on xfs_sb bno 0x0/0x1xfs_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
June 8, 20251 yr Community Expert 1 hour ago, ictkris said:Re-run xfs_repair.xfs_repair is aborting, I assume you have already tried this? If yes, the only option would be to use a file recovery app, like UFS explorer, or ask for help on the XFS mailing list.
June 8, 20251 yr Author Thank you for your messageYes 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.
June 9, 20251 yr Community Expert This is an issue with XFS, not directly related to Unraid, it can happen with any other Linux distro using it.
June 9, 20251 yr Community Expert Filesystem corruption is often a sign of hardware issues like bad RAM.
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.