"
Hi Franco. Thanks for replying. I will try a different USB now. I'm using a YUMI USB that also has a few Linux distros on. I did wonder if that was an issue...
BINGO! It worked. Thanks a lot Franco!
BINGO! It worked. Thanks a lot Franco!
This section allows you to view all posts made by this member. Note that you can only see posts made in areas you currently have access to.
Pages1
#1
26.1 Series / Re: Tripped up at the first hurdle! "OPNsense_Install failed with error 19"
February 20, 2026, 06:59:19 PM #2
26.1 Series / Tripped up at the first hurdle! "OPNsense_Install failed with error 19"
February 20, 2026, 03:37:46 PM
Hi folks. I don't know how to fix this problem. I know very little about IT and computers (hence the username), so please be gentle with me!
I'm installing on a SimplyNUC NUC10EGC. I was trying to follow Home Network Guy's OPNsense installation guide but I can't even get to the first option to choose! I get the following error:
Mounting from ufs:/dev/ufs/OPNsense_Install failed with error 19
Loader variables:
vfs.root.mountfrom=ufs:/dev/ufs/OPNsense_Install
vfs.root.mountfrom.options=ro,noatime
Manual root filesystem specification:
<ftype>:<device> [options]
Mount <device> using filesystem <fstype>
and with the specified (optional) option list.
eg. ufs:/dev/da0s1a
zfs:zroot/ROOT/default
cd9660:dev/cd0 ro
(which is equivalent ro: mount -t cd9660 -o ro /dev/cd0 /)
I thought at first this means OPNsense installer can't find the hard drive to install onto, but if I enter '?' to 'list valid boot devices', I get this:
List of GEOM managed disk devices:
msdosfs/VTOYEFI da0s2 da0s1 diskid/DISK-S425NB0KC32465p2 diskid/DISKS425NB0KC32465p1 da0 gptid/ald94a9c-blah-etc-and-so-on gptid/b685b511-blah-etc-and-so-on diskid/DISK-S425NB0KC32465 nda0p2 nda0p1 nda0 mmcsboot1 mmcsdboot0 diskid/DISK-391712A0 mmcsd0
...I think the 'S425NB0KC32465' must refer to the Samsung SSD, that is assigned nda0, as further up it says:
nda0: <SAMSUNG MZVLB256HAHQ-000H1 EXD70H1Q S425NB0KC32465
... and then 5 lines lower it sees the live USB installer, as it says:
da0: <USB SanDisk 3.2 long-serial-number
... but those should be the only two disks attached. So it does see the disks. Does this mean I just need to type in a line of code to mount the Samsung SSD so it knows where to install?
I have looked at a lot of posts for the last 3 hours, including some on a 10 year old FreeBSD forum, but it's too advanced for me to be honest.
Thanks for reading, and if I may be so bold and presumptuous to ask that if you do take the time to respond, please dumb it down as much as possible lol! I want to learn but I know next to nothing and am having to search every acronym I see pretty much.
Cheers :)
EDIT: I hope this wasn't stoopid, but I tried typing 'ufs:/dev/nda0' after 'mountroot>' to see if that would mount the SSD, but it said (many times!):
...
Failed, superblock has critical errors
Attempted recovery for standard superblock: failed
Attempt to find boot zone recovery data.
Finding an alternate superblock failed.
Check for only non-critical errors in standard superblock
Failed, superblock has critical errors
Mounting from ufs:/dev/nda0 failed with error 2.
mountroot>
I'm installing on a SimplyNUC NUC10EGC. I was trying to follow Home Network Guy's OPNsense installation guide but I can't even get to the first option to choose! I get the following error:
Mounting from ufs:/dev/ufs/OPNsense_Install failed with error 19
Loader variables:
vfs.root.mountfrom=ufs:/dev/ufs/OPNsense_Install
vfs.root.mountfrom.options=ro,noatime
Manual root filesystem specification:
<ftype>:<device> [options]
Mount <device> using filesystem <fstype>
and with the specified (optional) option list.
eg. ufs:/dev/da0s1a
zfs:zroot/ROOT/default
cd9660:dev/cd0 ro
(which is equivalent ro: mount -t cd9660 -o ro /dev/cd0 /)
I thought at first this means OPNsense installer can't find the hard drive to install onto, but if I enter '?' to 'list valid boot devices', I get this:
List of GEOM managed disk devices:
msdosfs/VTOYEFI da0s2 da0s1 diskid/DISK-S425NB0KC32465p2 diskid/DISKS425NB0KC32465p1 da0 gptid/ald94a9c-blah-etc-and-so-on gptid/b685b511-blah-etc-and-so-on diskid/DISK-S425NB0KC32465 nda0p2 nda0p1 nda0 mmcsboot1 mmcsdboot0 diskid/DISK-391712A0 mmcsd0
...I think the 'S425NB0KC32465' must refer to the Samsung SSD, that is assigned nda0, as further up it says:
nda0: <SAMSUNG MZVLB256HAHQ-000H1 EXD70H1Q S425NB0KC32465
... and then 5 lines lower it sees the live USB installer, as it says:
da0: <USB SanDisk 3.2 long-serial-number
... but those should be the only two disks attached. So it does see the disks. Does this mean I just need to type in a line of code to mount the Samsung SSD so it knows where to install?
I have looked at a lot of posts for the last 3 hours, including some on a 10 year old FreeBSD forum, but it's too advanced for me to be honest.
Thanks for reading, and if I may be so bold and presumptuous to ask that if you do take the time to respond, please dumb it down as much as possible lol! I want to learn but I know next to nothing and am having to search every acronym I see pretty much.
Cheers :)
EDIT: I hope this wasn't stoopid, but I tried typing 'ufs:/dev/nda0' after 'mountroot>' to see if that would mount the SSD, but it said (many times!):
...
Failed, superblock has critical errors
Attempted recovery for standard superblock: failed
Attempt to find boot zone recovery data.
Finding an alternate superblock failed.
Check for only non-critical errors in standard superblock
Failed, superblock has critical errors
Mounting from ufs:/dev/nda0 failed with error 2.
mountroot>
Pages1
