First boot, wizard is forced
-
I was annoyed because I could see no way of escaping the wizard. I just wanted to load my configuration by restoring from a backup file.
This is on 2.1 Beta.
-
Woops, after I restored from my backup, the system rebooted and got caught on the "mountroot" step. I went to look at the fstab and found this:
/dev/ufs/pfsense0 / ufs ro,sunc,noatime 1 1 /dev/ufs/cf /cf ufs ro,sunc,noatime 1 1Not what I expected, and I'm not sure how to modify it to work.
I made two assumptions, one or both of which may be wrong and causing the problem:
-
I can put an embedded image on a USB flash drive.
-
I can backup the configuration from a hard drive install, and then restore that configuration into an embedded install.
Did I goof?
-
-
Click the logo at the top of the wizard. No more wizard.
NanoBSD filesystems are kept read-only to preserve the integrity of the drive. You can change this under Diag > NanoBSD.
Your points 1 and 2 are correct, those both work.
For point #1, make sure you do this:
http://doc.pfsense.org/index.php/Boot_Troubleshooting#Booting_from_USB -
Yeah, I already figured out I had to take option 3 on the boot. But I'm just realizing I might have forgot on the reboot after the restore, because it looks like it works now.
I was just wondering about the construction, "/dev/ufs/pfsense0". I'm unfamiliar with that. I was expecting something like "/dev/da0s1a", that's all.
I know about the read-only business in nanobsd, except for a couple details: I'm guessing a restore operation automatically mounts the cf partition rw? It had to have, otherwise my restore wouldn't have worked. I'm a little shakey on where the gui automatically mounts it rw, and where I have to do it manually. I will dig into that some more.
As to clicking on the logo, that makes little sense. What's wrong with a nice, obvious "cancel" button? Then people don't have to field so many newbie questions in the forum. :)
This is a nifty piece of software…
-
I was just wondering about the construction, "/dev/ufs/pfsense0". I'm unfamiliar with that. I was expecting something like "/dev/da0s1a", that's all.
It's a GEOM label, so we can refer to the slice by name instead of by its physical designation. So we don't have to worry about the disk driver/device name at all, we use our own label for the filesystem.
I know about the read-only business in nanobsd, except for a couple details: I'm guessing a restore operation automatically mounts the cf partition rw? It had to have, otherwise my restore wouldn't have worked. I'm a little shakey on where the gui automatically mounts it rw, and where I have to do it manually. I will dig into that some more.
It handles that automatically for changes made in the GUI. If you want to manually make changes at the shell or over scp, etc, then you'll need to switch it manually.
As to clicking on the logo, that makes little sense. What's wrong with a nice, obvious "cancel" button? Then people don't have to field so many newbie questions in the forum. :)
I added some text to the wizard to state that clicking the logo gets out of it.
