AuraFross

Thank You!!! I'm so grateful for all the help. I was in a panic tell everything started to show up again!!! All my containers are back up and running! Your the BEST!!!

Shares are now showing but Docker container are not. also Thank you So much for the help! edit: to say thanks server-diagnostics-20240211-1808.zip

Okay, Will do and not a problem just wanted to make sure it was the right info. with out anything- Phase 1 - find and verify superblock... Phase 2 - using internal log - zero log... 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. using -L 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 destroyed because the -L option was used. - scan filesystem freespace and inode maps... clearing needsrepair flag and regenerating metadata sb_fdblocks 131107915, counted 133525088 - 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 inode 2659144457 - bad extent starting block number 4494804531550553, offset 2299110006768767 correcting nextents for inode 2659144457 bad data fork in inode 2659144457 cleared inode 2659144457 - 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 = 1 - agno = 3 - agno = 2 entry "docker.img" in shortform directory 2643368695 references free inode 2659144457 junking entry "docker.img" in directory inode 2643368695 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... Maximum metadata LSN (34:2696426) is ahead of log (1:2). Format log to cycle 37. done

Is this what your referring to?

I've had the Unraid server running on Ryzen for over 2 years and this just started to happen.

Hello, So I've been having some weird issue where my hosted containers would ping down and then back up 5 mins later threw Cloudflare Tunnel. In both proxmox and unraid. for example unraid hosting Apache guacamole, and Proxmox running Immich. I don't know if this has anything to do with the hard Crash unraid just had but when rebooting it. It would say no boot media detected tell I powered it off and moved the USB to another port. and once it did boot all my shares are gone. all the HDD show and the USERS but my shares are gone. I'm fairly new to self hosting and running unraid, any help would be greatly appreciated. attached is the Diagnostics if there anything else let me know. server-diagnostics-20240211-1629.zip