February 4, 20251 yr I'm running UnRaid 7.0.0, but I had this problem with earlier version like 6.2.13. i7-6700T replaced from i5-6400, 4 drives (2x2TB, 2x8TB), 1x 256GB cache. Running a fair share of dockers and plugins. Last year, I had a drive seemingly error with a "Unmountable: wrong or no file system". I replaced it, and for the second time it's got the same error. I had switched cables and ports for the drive, so I don't know what happened. Seems like it's after a reboot, or a restart of the system. This drive is mainly for Syncthing, but Syncthing doesnt seem to be causing it. I've attached my diagnostics below. Thanks for any help! tower-diagnostics-20250204-1823.zip
February 4, 20251 yr Community Expert Check filesystem on disk2 from the webUI, capture the output and post it.
February 4, 20251 yr Author There's also an option to fix, but have not pressed it yet. Apologies, not technical with UnRaid specifically. disk2 filesystem
February 4, 20251 yr Community Expert 1 hour ago, 2eFG2FXk said: but have not pressed it yet Click that.
February 4, 20251 yr Author Woah, really long error code when I tried to zero log it. Running it again to fix, any clue? Error Fix log
February 4, 20251 yr Author New one. Seems to be cyclical loop now of these two errors. Error Fix log
February 4, 20251 yr Community Expert Solution Results should be the same, but just to confirm, start the array in maintenance mode, and post the output from: xfs_repair -v /dev/md2p1
February 4, 20251 yr Author @JorgeB's comment seemed to have fixed it, thank you! For some further insight, what happened? Why did the command fix it but not the automated ones? How do I prevent it? Thanks again for your support @JorgeB
February 5, 20251 yr Community Expert Do you have a lost+found share now? If so, click Compute... for the share on the User Shares page to see how much repair couldn't figure out.
February 5, 20251 yr Author lost+found is 48.2MB lost. They're all empty text files with random names.
February 6, 20251 yr Community Expert 15 hours ago, 2eFG2FXk said: random names File and folder names are often lost on things that couldn't be fully repaired. If they had significant content then there are ways to try to figure out what they were.
April 7, 20251 yr Author On 2/7/2025 at 3:28 AM, trurl said: File and folder names are often lost on things that couldn't be fully repaired. If they had significant content then there are ways to try to figure out what they were. Just happened again, now lost+found is at 30GB. How can I can find out what they are?
April 7, 20251 yr Community Expert 3 hours ago, 2eFG2FXk said: How can I can find out what they are Only way is manual examination of the contents. The Linux ‘file’ command can be used to give you the content type of files.
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.