First thanks for the great product, the hard work and commitment!
There's one particular thing what i woud like to suggest. When a data disk (GPT, UFS) has errors, NAS4Free won't start (i.e. the web interface and services like SSH), which is cumbersome. Since my server has no screen or keyboard attached and is locked up in the meter box, so to resolve the issue (running fsck), I need to take my server out of the meter box, reconnect and attach a keyboard and screen to run fsck (and subsequently put everything back again)
Why does a failing disk (no system or boot disk) prevent NAS4Free from starting properly? I would really appreciate if this can ce changed (so i can run fsck using SSH from my desktop)...
Please let me know,
Maarten
This is the old XigmaNAS forum in read only mode,
it will taken offline by the end of march 2021!
I like to aks Users and Admins to rewrite/take over important post from here into the new fresh main forum!
Its not possible for us to export from here and import it to the main forum!
it will taken offline by the end of march 2021!
I like to aks Users and Admins to rewrite/take over important post from here into the new fresh main forum!
Its not possible for us to export from here and import it to the main forum!
NAS4Free won't start when a non-system disk has errors
-
maarten
- Starter
- Posts: 38
- Joined: 17 Jul 2012 20:20
- Status: Offline
-
jamaroney
- Advanced User
- Posts: 245
- Joined: 13 Aug 2012 17:32
- Location: Stroudsburg, PA
- Status: Offline
Re: NAS4Free won't start when a non-system disk has errors
in the WebGUI, under "Disks" -> "Mount Point", is "Enable foreground/background file system consistency check during boot process" selected for each disk? That should run fsck automatically on startup.
With the latest N4F version, I had similar problems to yours with my EXT3 USB drive because N4F couldn't find fsck_ext2fs on startup. So I had to set up a PreInit command ("/usr/local/sbin/e2fsck /dev/da0s1") in "System" -> "Advanced" -> "Command Scripts". You may have to try something similar for your disks.
With the latest N4F version, I had similar problems to yours with my EXT3 USB drive because N4F couldn't find fsck_ext2fs on startup. So I had to set up a PreInit command ("/usr/local/sbin/e2fsck /dev/da0s1") in "System" -> "Advanced" -> "Command Scripts". You may have to try something similar for your disks.