OPNsense Forum
Archive => 18.7 Legacy Series => Topic started by: Davesworld on July 18, 2018, 03:33:22 am
-
I did a fresh install of RC1 on my second firewall that uses Cellular Internet and it would appear that when the image is first booting, it looks for a ZFS to import but when the installer gui is invoked I saw no way to create a ZFS pool so I just reformatted the mirror it used previously.
As far as importing a config from a usb stick, it didn't, it complained of not being able to mount the device which uses the Fat32 filesystem which should be normal for removable storage of that type.
It should be noted that the only way OPNsense has been able to import a config from a previous install is if it is a single disk install, not Geom Mirror etc.
Other than the above, it seems to work fine.
EDIT: If one simply switches to development rather than do a fresh install, the notes mention that the ZFS installer is not ready yet.
-
Hi Davesworld,
Thanks for the feedback, highly appreciated! :)
Indeed, ZFS installer is still on my TODO list. 18.7-RC2 is out tomorrow with a lot of changes to free time and reduce the code churn while we wait for the final 18.7.
I'll have to look into that Fat32 issue. Can you provide the disk layout with a simple command from the command line:
# ls /dev/da*
I just need to know the output and which da device is the usb stick.
GEOM mirror and raid can be imported quite easily. It is a documentation issue
mirror/MirrorName
raid/RaidName
The mirrors and raids are listed in 18.7-RC1 for the early config importer when they exist in the system.
ZFS needs to be invoked manually using "zroot". It's not fully automatic.
Cheers,
Franco
-
root@phaedra:~ # ls /dev/da*
/dev/da0 /dev/da0s1
-
ZFS needs to be invoked manually using "zroot". It's not fully automatic.
Cheers,
Franco
At what point is this possible?
-
When the importer asks for a partition.
I've looked into the fat32 issue... if it doesn't mount FreeBSD doesn't support it for some reason. The layout looks correct but the final mount fails. To be continued. :)
Cheers,
Franco
-
When the importer asks for a partition.
I've looked into the fat32 issue... if it doesn't mount FreeBSD doesn't support it for some reason. The layout looks correct but the final mount fails. To be continued. :)
Cheers,
Franco
For me at least, there is no problem formatting the usb stick with something else that the BSD kernel supports as this is the absolute best time in an installation to import the config. It would reduce a clean install to fully functional install to mere minutes if on the same hardware. I'll post my results here.
-
I tried fat16 and ext2fs, made no difference. I think the importer looks for an installation rather than a config file in an empty directory as it has done all along. the zfs import does try to find it in zroot at least so far.
-
On your USB stick, do you use conf/config.xml or just config.xml ?
Cheers,
Franco
-
On your USB stick, do you use conf/config.xml or just config.xml ?
Cheers,
Franco
Just by your question I think I may be doing it wrong. I was leaving the config xml file exactly as downloaded from the gui under system configuration. Does it need to be renamed to ONLY config.xml and/or residing in a directory called conf? My guess by looking in the root directory of my installed firewalls is that you need a conf directory with conf.xml in it.
As far as filesystems go, at least the installed system does indeed have a module called msdosfs. I'm sure it is in the installer kernel as well?
-
> Just by your question I think I may be doing it wrong.
No, I have been explaining it badly. I'm sorry.
The config import assumes that it imports from an installation, which doesn't mean you need to put all files in place.
It only needs your main /conf/config.xml but you can also drop additional configs into /conf/backup/ or some other backup-related files, see here:
# ls /conf
backup config.xml dhcpleases.tgz rrd.tgz
captiveportal.sqlite dhcp6c_duid netflow.tgz sshd
> As far as filesystems go, at least the installed system does indeed have a module called msdosfs. I'm sure it is in the installer kernel as well?
Yes, it's always there.
Cheers,
Franco