I did a clean install of the latest 9.3, only to revert to 9.2, because 9.3 lacks fsck_ext2fs.
I have an external USB drive formatted in EXT3 (for very good reasons). 9.3 says it can't find fsck_ext2fs for my drive, and won't even start!
If I disconnect the drive, 9.3 starts OK. I will then setup the EXT3 drive properly via WebGUI, but when I reboot, N4F again won't start if the USB drive stays connected.
I looked for fsck_ext2fs, and it's nowhere to be found. So, for now I went back to 9.2.
Should I assume that this is an oversight? Otherwise, why would it not be included in the new firmware?
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!
NO fsck_ext2fs in 9.3.0.2.1310
-
jamaroney
- Advanced User
- Posts: 245
- Joined: 13 Aug 2012 17:32
- Location: Stroudsburg, PA
- Status: Offline
-
jamaroney
- Advanced User
- Posts: 245
- Joined: 13 Aug 2012 17:32
- Location: Stroudsburg, PA
- Status: Offline
Re: NO fsck_ext2fs in 9.3.0.2.1310
Here's what appears on the screen when I start N4F 9.3.0.2.1310 (embedded) with my EXT3 formatted USB HDD attached:
>>>>>>>>>>>>>>>>>>>>>>>>
Starting file system checks:
fsck: exec fsck_ext2fs for /dev/da0sa1 in /sbin: /usr/sbin: No such file or directory
fsck: exec fsck_ext2fs for /dev/da0sa1 in /sbin: /usr/sbin: No such file or directory
Unknown error; help!
ERROR: ABORTING BOOT (sending SIGTERM to parent)!
Jan 29 09:18:37 init: /bin/sh on /etc/rc terminated abnormally, going to single user mode
Enter full pathname of shell or RETURN for /bin/sh:
>>>>>>>>>>>>>>>>>>>>>>>>>
If I go to the shell and run "e2fsck /dev/da0s1", the disk is reported as clean, but I can't continue.
It seems that the new N4F has eliminated fsck_extfs, but the startup apparently doesn't redirect to e2fsck for ext2/3 disks.
How can this glitch be bypassed? Or must I simply wait until a new release fixes the error?
>>>>>>>>>>>>>>>>>>>>>>>>
Starting file system checks:
fsck: exec fsck_ext2fs for /dev/da0sa1 in /sbin: /usr/sbin: No such file or directory
fsck: exec fsck_ext2fs for /dev/da0sa1 in /sbin: /usr/sbin: No such file or directory
Unknown error; help!
ERROR: ABORTING BOOT (sending SIGTERM to parent)!
Jan 29 09:18:37 init: /bin/sh on /etc/rc terminated abnormally, going to single user mode
Enter full pathname of shell or RETURN for /bin/sh:
>>>>>>>>>>>>>>>>>>>>>>>>>
If I go to the shell and run "e2fsck /dev/da0s1", the disk is reported as clean, but I can't continue.
It seems that the new N4F has eliminated fsck_extfs, but the startup apparently doesn't redirect to e2fsck for ext2/3 disks.
How can this glitch be bypassed? Or must I simply wait until a new release fixes the error?