OPNsense Forum
Archive => 16.7 Legacy Series => Topic started by: roro on October 27, 2016, 10:17:53 pm
-
Hello,
during upgrading my opnsense box via serial com1 (soekris, cfcard, nano), I lost internet connection.
System was at point Fetching base-16.7.7-i386.txz and stopped upgrading.
I rebooted the system via console and did upgrade again.
Fetching base-16.7.7-i386.txz.
Fetching base-16.7.7-i386.obsolete.
Fetching kernel-16.7.7-i386.txz.
Installing kernel-16.7.7-i386.txz.
Installing base-16.7.7-i386.txz.
Installing base-16.7.7-i386.obsolete.
System did an automated reboot, but now I get the following error:
Trying to mount root from ufs:/dev/ufs/OPNsense1 [rw,async,noatime]...
mountroot: waiting for device /dev/ufs/OPNsense1 ...
Mounting from ufs:/dev/ufs/OPNsense1 failed with error 19.
Loader variables:
vfs.root.mountfrom=ufs:/dev/ufs/OPNsense1
vfs.root.mountfrom.options=rw,async,noatime
Manual root filesystem specification:
<fstype>:<device> [options]
Mount <device> using filesystem <fstype>
and with the specified (optional) option list.
eg. ufs:/dev/da0s1a
zfs:tank
cd9660:/dev/acd0 ro
(which is equivalent to: mount -t cd9660 -o ro /dev/acd0 /)
? List valid disk boot devices
. Yield 1 second (for background tasks)
<empty line> Abort manual input
mountroot>
Any hints to solve this issue.
Thank you.
Roro
-
Hi Roro,
Ok, looks like a nano install?
The firmware update aborts prior to doing anything disruptive, so you did the right thing by issuing the console update again.
/dev/ufs/OPNsense1 should really be /dev/ufs/OPNsense0, did you modify /boot/loader.conf(.local) at any time?
Try typing:
ufs:/dev/ufs/OPNsense0
The oddity with the two-slice system on nano is that we only ever use the first one. Switching slices is not supported and may lead to undefined behaviour (having partial upgrades on one, reverting to older configs on the other). Just need to make sure we're not missing something here. :)
Cheers,
Franco
-
Hi Franco,
I get the following:
uhub0: 4 ports with 4 removable, self powered
Root mount waiting for: usbus1
uhub1: 4 ports with 4 removable, self powered
Trying to mount root from ufs:/dev/ufs/OPNsense0 [rw,async,noatime]...
mountroot: waiting for device /dev/ufs/OPNsense0 ...
Mounting from ufs:/dev/ufs/OPNsense0 failed with error 19.
Loader variables:
vfs.root.mountfrom=ufs:/dev/ufs/OPNsense0
vfs.root.mountfrom.options=rw,async,noatime
Manual root filesystem specification:
<fstype>:<device> [options]
Mount <device> using filesystem <fstype>
and with the specified (optional) option list.
eg. ufs:/dev/da0s1a
zfs:tank
cd9660:/dev/acd0 ro
(which is equivalent to: mount -t cd9660 -o ro /dev/acd0 /)
? List valid disk boot devices
. Yield 1 second (for background tasks)
<empty line> Abort manual input
mountroot
Invalid file system specification.
mountroot> ufs:/dev/ufs/OPNsense0
Trying to mount root from ufs:/dev/ufs/OPNsense0 []...
mountroot: waiting for device /dev/ufs/OPNsense0 ...
Mounting from ufs:/dev/ufs/OPNsense0 failed with error 19.
Greetz,
Roro
-
and when I give an enter I get the following:
mountroot>
panic: mountroot: unable to (re-)mount root.
cpuid = 0
KDB: enter: panic
[ thread pid 1 tid 100002 ]
Stopped at kdb_enter+0x3d: movl $0,kdb_why
db>
-
Oh dear, to me this looks like the card gave in. It's true that the update writes a fair amount of data, but it shouldn't disintegrate both file systems, the latter being unreachable/unmounted. :(
-
Franco, no problem I will reinstall opnsense.
Thanks for the support.
Roro.
-
Alright, thank you.