-
UNMOUNTABLE: NO FILE SYSTEM
Okay, I finally got it to complete and it ended with. ................Sorry, could not find valid secondary superblock Exiting now. Honestly at this point, i'm fine with just sacrificing whatever data was on the drive to get my array back to being complete and fully mountable.
-
UNMOUNTABLE: NO FILE SYSTEM
Ended up using SSH instead of the web terminal since it kept resetting. I'll update again once it has finished.
-
UNMOUNTABLE: NO FILE SYSTEM
There's nothing important or irreplaceable on the server, so I don't have any data backups currently. I used to use backblaze when I had important documents saved. I do have a backup of the Unraid flashdrive and my appdata though.
-
UNMOUNTABLE: NO FILE SYSTEM
I had assumed the disk being unmountable was a hardware issue, not an array issue. I guess that makes sense why the replacement drive didn't work either. I've started xfs_repair again. If the web terminal keeps resetting, I may have to setup SSH.
-
UNMOUNTABLE: NO FILE SYSTEM
I tried running the xfs_repair, but every time my PC goes to sleep, the terminal resets so I can’t see the results of the repair. Is there a way to run it and log to a file? I did actually try adding another disk to the array to put in place of the unmountable drive, but it also showed as unmountable.
-
UNMOUNTABLE: NO FILE SYSTEM
Parity and rebuild finished and were fine. I've started the xfs_repair again and will just let it run. A few posts online say it can take quite a while, so I'll update when I have the output.
-
UNMOUNTABLE: NO FILE SYSTEM
Here they are. It has also started a parity-sync/data-rebuild which will probably take about 7 hours. hpdl380pg8-diagnostics-20230608-1036.zip
-
UNMOUNTABLE: NO FILE SYSTEM
To be completely honest, that drive may have still not had any data on it since I formatted and installed it a few months ago. On the array webUI, it's file system shows as "auto" instead of XFS. That could also be part of the problem.
-
UNMOUNTABLE: NO FILE SYSTEM
I used the command line because I couldn't find the webUI button for it. I was following the wiki instructions. My exact command was xfs_repair -v /dev/md5 It had the comment about the primary superblock magic number then for the secondary block it just endlessly printed out "......" in the command line. Perhaps I didn't let it run long enough.
-
lostengineer started following UNMOUNTABLE: NO FILE SYSTEM
-
UNMOUNTABLE: NO FILE SYSTEM
I had an unclean shutdown due to a power outage this morning and when I restarted the array, disk 5 showed as unmountable: no file system. I tried xfs_repair in maintenance mode, but it couldn't find the superblock because of a bad magic number. I'm not sure how to fix this. Any help is greatly appreciated. I've attached my diagnostics to help out. hpdl380pg8-diagnostics-20230608-0932.zip
lostengineer
Members
-
Joined
-
Last visited