SG-2440 cant boot
-
Anybody seem this message before? My guess is that the SG-2440 can't handle a power failure.
Was running a pfsense 2.2.5.
_ __ / / | ___ _ __ ___ ___
| ' | |_ \ / _ \ '_ / |/ _
| |) | |) | / | | _ \ /
| ./|| |___/ _|| ||/_|
||+–----------Welcome to pfSense-----------+
| | ______
| 1. Boot Multi User | /
| 2. Boot ingle User | / f
| 3. ape to loader prompt | / \ /
| 4. Reboot | / p _/ Sense
| | \ /
| Options: | _____/
| 5. ernel: kernel (1 of 2) | \ /
| 6. Configure Boot ptions... | ______/
| |
| |
| |
+-----------------------------------------+/boot/kernel/kernel text=0x1223df0 inflate: invalid code lengths set
readin failed
elf64_loadimage: read failed
can't load file '/boot/kernel/kernel': input/output error
Error while including /boot/menu.rc, in the line:
menu-display
/
Hit to boot immediately, or any other key for command prompt.
Booting [/boot/kernel/kernel]…
/boot/kernel/kernel text=0x1223df0 inflate: invalid distance codereadin failed
elf64_loadimage: read failed
can't load 'kernel'Type '?' for a list of commands, 'help' for more detailed help.
OK -
looks like you will want to reinstall
-
@jwt:
looks like you will want to reinstall
Yeah.. :/ Working after a reflash. I have 3x SG-2440 running 24/7 and this is the second time i have to do this within 1 year. Not sure if it was the same unit.
I guess that the units already is using some kind of journaling to prevent corruption on power failure?
-
This is the awesome UFS/SU+J in action… actually, the "journaling" is making it worse, because it's buggy and noone gives a damn (when you ignore an issue for years, it will vanish... ::)) Add absolutely useless fsck that either makes a kaboom and does nothing at all, or requires 5-10 manual runs to get work done, and there you go. The default FreeBSD filesystem in all its glory.
-
to prevent corruption on power failure?
APC is selling units to prevent from a power failure or complete loss in this situation.
Also a widget or deamon could installed in pfSense to "talk" to this units. -
This is the awesome UFS/SU+J in action… actually, the "journaling" is making it worse, because it's buggy and noone gives a damn (when you ignore an issue for years, it will vanish... ::)) Add absolutely useless fsck that either makes a kaboom and does nothing at all, or requires 5-10 manual runs to get work done, and there you go. The default FreeBSD filesystem in all its glory.
So abrasive…
Kirk has forgotten more about filesystems than you'll ever learn.
I'm looking at ZFS for a 3.0.
-
@jwt:
This is the awesome UFS/SU+J in action… actually, the "journaling" is making it worse, because it's buggy and noone gives a damn (when you ignore an issue for years, it will vanish... ::)) Add absolutely useless fsck that either makes a kaboom and does nothing at all, or requires 5-10 manual runs to get work done, and there you go. The default FreeBSD filesystem in all its glory.
So abrasive…
Kirk has forgotten more about filesystems than you'll ever learn.
I'm looking at ZFS for a 3.0.Yes. That appears to be the only usable alternative, considering that FreeBSD managed to screw up ext[234] as well with "improvements" ported from the horrible UFS thing. (That wiki article is very amusing reading, BTW. When it comes to robustness/resiliency, UFS ranks on par with FAT, except that FAT has a better working chkdsk and doesn't perform like POS on CF/SD and co. ::))
Finally, a link people who don't want to wait for 3.0 to get somewhat stable FS… (Been using that on multiple boxes for ~6 months now without issues such as the ones mentioned here.)
-
and hundreds of thousands of people use UFS without incident, too.
ZFS is in the system for a reason, and I'm not exposing it just yet. (cmb was going to take it out, and I said, "No".)
cmb is right in that it's not a good fit for a typical pfSense box.