Thanks for the utterly broken 2.1 update.
-
The memstick serial image is to write onto a usb stick. Then you boot from the USB stick, all the output is on the serial console, and install to the HD just like the CD. If you select the embedded kernel during the install you will then have a serial console by default when you then boot from the HD.
Alternatively you can remove the HD and install pfSense to it in another machine from the CD. Once you have it installed and running you can enable a serial console in the webgui so that you have console access when you transfer it back to the soekris box.
Steve
-
"Alternatively you can remove the HD and install pfSense to it in another machine from the CD. Once you have it installed and running you can enable a serial console in the webgui so that you have console access when you transfer it back to the soekris box."
So you end up with a full install and a working console? Correct? I like this plan for a 250GB WD HDD.
-
Yes, exactly. I'm not sure quite what you get by selecting the embedded kernel, it used to be no packages but that isn't the case now, everything seems available - more than nano even. I have used this process for HD install on a firebox X-core-e but it's more difficult in that box. The process is described for an older box, and older pfSense, here:
https://doc.pfsense.org/index.php/Soekris_4801_Hard_Drive_InstallationSome stuff in that document no longer applies; you can choose the standard install and select serial console later, you don't need to do any VLAN stuff because you only need one interface to get up and running.
When you tarnsfer back the HD and boot the box it will dump you at the assign interfaces dialogue because the NICs will (probably) be different in the Soekris box to the laptop.
Steve
-
When I did this before (Transplanting a HDD) It worked right away because I went from having an EM0 and EM1 to a totally different box that still had an EM0 and EM1. Just dumb luck.
-
I've used the memstick serial to a USB stick of 4GB - Booted the Soekris, installed per default using the full 250GB disk in the Soekris (instead of nanoBSDs 4GB partition).
Then selected "Embedded kernel" near the end and it seems to work so far. Trying to set up interfaces and stuff now. I just finished installing 5 minutes ago.So far so good…
-
Since you've not come back I hope it turned out OK. Sorry your upgrade experience wasn't the smooth transition everyone hopes for. :)
Steve
-
I've tried to upgrade my other soekris which also failed… Guess I need to re-install it with the memstick thing too, tomorrow...
Which seems to work.When I dd in a copy of the NanoBSD variant the config keeps getting erased after a reboot. Somethings not right with the 4G image I think. But I can't really confirm.
-
Hmm, strange. Unless you really need the space, and I suggest you don't, then I would recommend you use the 2GB image on 4GB cards. The actual size of most 4GB cards is often less than 4GB, sometimes substantially. It's possible the config slice is corrupt because it not getting completely written to the card. If 2.0.3 worked though that shouldn't be an issue. :-\
Steve
-
Sounds like his settings were being saved in RAM not Disk. Not sure how that would happen though.
-
It could not, or at least I've never seen or heard of it and can't think how it could!
Completely missing config file, not just interface re-assign, is usually either corrupt storage somehow or mistakenly running live.Steve
-
Live would do it…
-
I just wanted to note that the embedded kernel is mainly intended for running on devices that can't run the regular kernel because of lack of VGA, etc. It does not change anything about how pfSense writes to disk, where it writes to disk, or how often it writes to disk. Some people have the mistaken notion that selecting the embedded kernel changes those aspects somehow, but it does not. The partition layout and configuration of the internal scripts are what do that, which the kernel selection does not change.
-
Today I "fixed" the other soekris with the Memstick version which went without a hitch. yay!
Both are now running pfSense 2.1.As mentioned earlier; Neither was upgradable from 2.0.3 using the 4G nanoBSD variant. Still not sure why.
However, with the tips/ideas given here I think both systems now run faster than before. So it's not all bad. Just a day wasted on fixing stuff :-\See attached image if you're curious where your help went :)
-
It looks considerably more neat than my table-o-network down in the basement ;D
Mine is old 65w dual core dell with a motley collection of Intel NICs, a 19inch CRT (with a tube) from before my kids were born and a keyboard from the 90s that just keeps going… Looks like steampunk pfsense...
Switches are all pretty new stuff - I couldn't find any 90s looking gigabit managed switches to match :P
-
HAHAHAHAHAHAHAHAHA!!
-
Cute installation there.
-
Supermule - I assume you are laughing with me… not at me... Hmmmmm??? ::)
The other day my 17 year old boy asked me "Daddy - What is that big thing on the front of your car?" I said "Thats called a bumper".
Yeah... I'm nostalgic you might say.
-
The cases + half of the interior came with the building i'm renting :) All the cabling into the office space was already in place too. Luckily… Saved us a ton of money.
I just had to fill the gaps with switches and stuff to make it work! -
So, now that all is right with your pfsense the moderators can rename this thread "Thanks for the utterly awesome 2.1 update."?
-
Well the update never worked. As mentioned above. Failed multiple times.
But fresh installs did work.
