-
Disk Unmountable after reboot, even with 2nd new drive
Just happened again, now lost+found is at 30GB. How can I can find out what they are?
-
Disk Unmountable after reboot, even with 2nd new drive
lost+found is 48.2MB lost. They're all empty text files with random names.
-
Disk Unmountable after reboot, even with 2nd new drive
@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
-
Disk Unmountable after reboot, even with 2nd new drive
xfs_repaor
-
Disk Unmountable after reboot, even with 2nd new drive
Third time, nothing still. Same printouts.
-
Disk Unmountable after reboot, even with 2nd new drive
New one. Seems to be cyclical loop now of these two errors. Error Fix log
-
Disk Unmountable after reboot, even with 2nd new drive
Woah, really long error code when I tried to zero log it. Running it again to fix, any clue? Error Fix log
-
Disk Unmountable after reboot, even with 2nd new drive
There's also an option to fix, but have not pressed it yet. Apologies, not technical with UnRaid specifically. disk2 filesystem
-
2eFG2FXk started following Disk Unmountable after reboot, even with 2nd new drive
-
Disk Unmountable after reboot, even with 2nd new drive
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
2eFG2FXk
Members
-
Joined
-
Last visited