SG1000 upgrade issues from 2.4.3_1 to 2.4.4_1.
-
Hello I just try to upgrade my SG1000 pfsense.
I have:
- Reboot successfully the device BEFORE doing the upgrade
- Done the upgrade by the console ( all look good no error messages )
- When the unit reboot I see at the serial console:
codFilesystems are clean, continuing... Mounting filesystems... /lib/libxo.so.0: invalid file format [: -eq: unexpected operator /lib/libm.so.5: invalid file format rm: /conf: Read-only file system /lib/libm.so.5: invalid file format /lib/libcrypt.so.5: invalid file formatAnd after around 300 lines of
__ _ __ / _|___ ___ _ __ ___ ___ | '_ \| |_/ __|/ _ \ '_ \/ __|/ _ \ | |_) | _\__ \ __/ | | \__ \ __/ | .__/|_| |___/\___|_| |_|___/\___| |_| Welcome to (Patch 1)... rm: /COPYRIGHT: Read-only file system rm: /bin/cat: Read-only file system rm: /bin/chflags: Read-only file system . And nothing more.....What can i do to fix the
Read-only file system? -
You can try running a FSCK and see if that resolves the issue:
- At the SG-3100 console press any key to interrupt the boot loader when you see:
Hit [Enter] to boot immediately, or any other key for command prompt.
At the prompt enter: boot -s
That will boot in single user mode to a question asking for a path to the shell, just press return to reach the # prompt.
- At the # prompt run the following command: /sbin/fsck -y /
Run the fsck command at least 3 times; Repeat the command until no errors are reported, even if fsck claims the filesystem has been marked "clean".
- Reboot by running: /sbin/reboot
It should boot normally and with no residual long-term issues.
Please let us know the results.
- At the SG-3100 console press any key to interrupt the boot loader when you see:
-
boot -sandentergive me a shell
Nothing a type has any effect at this pointmmcsd0: 4GB <MMCHC M62704 0.1 SN 034FA523 MFG 06/2017 by 112 0x0000> at mmc1 48.0MHz/8bit/65535-block mmcsd0boot0: 2MB partion 1 at mmcsd0 mmcsd0boot1: 2MB partion 2 at mmcsd0 mmcsd0rpmb: 524kB partion 3 at mmcsd0 Trying to mount root from ufs:/dev/ufsid/5af4c96aa287b62c [rw,noatime]... Warning: no time-of-day clock registered, system time will not be set accurately random: unblocking device. # ls # mount # ps /lib/libm.so.5: invalid file format #I found the /rescue folder which work better:
# /rescue/fsck -y / ** /dev/ufsid/5af4c96aa287b62c USE JOURNAL? yes ** SU+J Recovering /dev/ufsid/5af4c96aa287b62c Journal timestamp does not match fs mount time ** Skipping journal, falling through to full fsck ** Last Mounted on / ** Root file system ** Phase 1 - Check Blocks and Sizes ** Phase 2 - Check Pathnames ** Phase 3 - Check Connectivity ** Phase 4 - Check Reference Counts ** Phase 5 - Check Cyl groups 19169 files, 201957 used, 684802 free (1834 frags, 85371 blocks, 0.2% fragmentation) ***** FILE SYSTEM IS CLEAN ***** # /rescue/fsck -y / ** /dev/ufsid/5af4c96aa287b62c USE JOURNAL? yes ** SU+J Recovering /dev/ufsid/5af4c96aa287b62c Journal timestamp does not match fs mount time ** Skipping journal, falling through to full fsck ** Last Mounted on / ** Root file system ** Phase 1 - Check Blocks and Sizes ** Phase 2 - Check Pathnames ** Phase 3 - Check Connectivity ** Phase 4 - Check Reference Counts ** Phase 5 - Check Cyl groups 19169 files, 201957 used, 684802 free (1834 frags, 85371 blocks, 0.2% fragmentation) ***** FILE SYSTEM IS CLEAN ***** # /rescue/fsck -y / ** /dev/ufsid/5af4c96aa287b62c USE JOURNAL? yes ** SU+J Recovering /dev/ufsid/5af4c96aa287b62c Journal timestamp does not match fs mount time ** Skipping journal, falling through to full fsck ** Last Mounted on / ** Root file system ** Phase 1 - Check Blocks and Sizes ** Phase 2 - Check Pathnames ** Phase 3 - Check Connectivity ** Phase 4 - Check Reference Counts ** Phase 5 - Check Cyl groups 19169 files, 201957 used, 684802 free (1834 frags, 85371 blocks, 0.2% fragmentation) ***** FILE SYSTEM IS CLEAN *****the content of the /lib seems a little off:
# /rescue/ls -l /lib total 7832 drwxr-xr-x 2 root wheel 512 May 10 2018 casper drwxr-xr-x 2 root wheel 512 May 10 2018 geom -r--r--r-- 1 root wheel 0 Dec 15 15:00 lib80211.so.1 -r--r--r-- 1 root wheel 0 Dec 15 15:00 libalias.so.7 -r--r--r-- 1 root wheel 0 Dec 15 15:00 libalias_cuseeme.so -r--r--r-- 1 root wheel 0 Dec 15 15:00 libalias_dummy.so -r--r--r-- 1 root wheel 0 Dec 15 15:00 libalias_ftp.so -r--r--r-- 1 root wheel 0 Dec 15 15:00 libalias_irc.so -r--r--r-- 1 root wheel 0 Dec 15 15:00 libalias_nbt.so -r--r--r-- 1 root wheel 0 Dec 15 15:00 libalias_pptp.so -r--r--r-- 1 root wheel 0 Dec 15 15:00 libalias_skinny.so -r--r--r-- 1 root wheel 0 Dec 15 15:00 libalias_smedia.so -r--r--r-- 1 root wheel 0 Dec 15 15:00 libavl.so.2 -r--r--r-- 1 root wheel 0 Dec 15 15:00 libbegemot.so.4 -r--r--r-- 1 root wheel 144772 May 10 2018 libbsdxml.so.4 -r--r--r-- 1 root wheel 1364340 May 10 2018 libc.so.7 -r--r--r-- 1 root wheel 0 Dec 15 15:00 libcam.so.7 -r--r--r-- 1 root wheel 0 Dec 15 15:00 libcrypt.so.5 -r--r--r-- 1 root wheel 1663728 May 10 2018 libcrypto.so.8 -r--r--r-- 1 root wheel 0 Dec 15 15:00 libctf.so.2 -r--r--r-- 1 root wheel 0 Dec 15 15:00 libcxxrt.so.1 -r--r--r-- 1 root wheel 0 Dec 15 15:00 libdevstat.so.7 -r--r--r-- 1 root wheel 0 Dec 15 15:00 libdtrace.so.2 -r--r--r-- 1 root wheel 175120 May 10 2018 libedit.so.7 -r--r--r-- 1 root wheel 0 Dec 15 15:00 libelf.so.2 -r--r--r-- 1 root wheel 26356 May 10 2018 libgcc_s.so.1 -r--r--r-- 1 root wheel 0 Dec 15 15:00 libgeom.so.5 -r--r--r-- 1 root wheel 0 Dec 15 15:00 libipsec.so.4 -r--r--r-- 1 root wheel 0 Dec 15 15:00 libjail.so.1 -r--r--r-- 1 root wheel 0 Dec 15 15:00 libkiconv.so.4 -r--r--r-- 1 root wheel 0 Dec 15 15:00 libkvm.so.7 -r--r--r-- 1 root wheel 0 Dec 15 15:00 libm.so.5 -r--r--r-- 1 root wheel 0 Dec 15 15:00 libmd.so.6 -r--r--r-- 1 root wheel 0 Dec 15 15:00 libmt.so.5 -r--r--r-- 1 root wheel 0 Dec 15 15:00 libncurses.so.8 -r--r--r-- 1 root wheel 321428 May 10 2018 libncursesw.so.8rebooting give me the same issues (no change):
. . . mmcsd0: 4GB <MMCHC M62704 0.1 SN 034FA523 MFG 06/2017 by 112 0x0000> at mmc1 48.0MHz/8bit/65535-block mmcsd0boot0: 2MB partion 1 at mmcsd0 mmcsd0boot1: 2MB partion 2 at mmcsd0 mmcsd0rpmb: 524kB partion 3 at mmcsd0 Trying to mount root from ufs:/dev/ufsid/5af4c96aa287b62c [rw,noatime]... Warning: no time-of-day clock registered, system time will not be set accurately Dec 15 15:11:53 init: login_getclass: unknown class 'daemon' Dec 15 15:11:53 init: login_getclass: no default/fallback class 'default' /lib/libcrypt.so.5: invalid file format /etc/pfSense-rc: /usr/local/sbin/-led.sh: not found Configuring crash dumps... Filesystems are clean, continuing... Mounting filesystems... /lib/libxo.so.0: invalid file format [: -eq: unexpected operator /lib/libm.so.5: invalid file format rm: /conf: Read-only file system /lib/libm.so.5: invalid file format /lib/libcrypt.so.5: invalid file format __ _ __ / _|___ ___ _ __ ___ ___ | '_ \| |_/ __|/ _ \ '_ \/ __|/ _ \ | |_) | _\__ \ __/ | | \__ \ __/ | .__/|_| |___/\___|_| |_|___/\___| |_| Welcome to (Patch 1)... rm: /COPYRIGHT: Read-only file system -
I would reinstall that:
https://www.netgate.com/docs/pfsense/solutions/sg-1000/reinstall-pfsense.html
-
Yes look like it,
Now i have trouble finding the negate image on the net, will try with the pfsense one.... -
No. Please open a ticket at go.netgate.com. There is no CE image for the SG-1000.
-
With the image provide by the support my sg-1000 work now like a charm (after the re-install)
Thanks !!
-
Great to hear. Thank you for the feedback.
Copyright 2025 Rubicon Communications LLC (Netgate). All rights reserved.