Install on net6501
-
Try booting from this:
http://files.chi.pfsense.org/jimp/pfSense-memstick-serial-2.0.1-RELEASE-i386.img.gz
You can just do a full install to the mSATA from there.
-
Thank you every one for your help.
dotdash I am going to try the write on another machine when I get a sata to msata adapter in and try that.
Jimp I have been able to do an embedded install from the memstick file but everyone has scared me about this due to the msata being a Transcend 16GB MLC mSATA SSD.
-
Once you boot that you can run something like:
fetch -o - http://files.chi.pfsense.org/mirror/downloads/pfSense-2.0.1-RELEASE-4g-amd64-nanobsd.img.gz | gzip -dc | dd of=/dev/ad4 obs=64k
Where ad4 is the mSATA disk, not sure if it will be ad2, ad4, or ad6.
-
Once you boot that you can run something like:
fetch -o - http://files.chi.pfsense.org/mirror/downloads/pfSense-2.0.1-RELEASE-4g-amd64-nanobsd.img.gz | gzip -dc | dd of=/dev/ad4 obs=64k
Where ad4 is the mSATA disk, not sure if it will be ad2, ad4, or ad6.
Just to make sure Jimp:
but do you mean, when I get to the pfsense boot menu and i use menu #7 the enter the fetch line?
Once again thanks for helping a newbie, and sorry for the silly questions I ask, its been 30 years since I have really worked with anything but windows and dos.
-
boot the memstick I linked, then press 8 to go to a shell prompt, then type that
-
Thank you Jimp, I will try tonight and let you know tomorrow.
and once again thank you for the help it is much appreciated.
-
Hi Jimp,
Just to give you and update, I could not get the install going as you suggested with the memstick version. When it completed booting in the serial console, it would stop at Booting Complete, and not allow me to go to the shell command.
This is not an issue at this time as I have an adapter in shipment and will write the nanobsd to the msata and then change the drive location.
Thank you for your help, it was greatly appreciated, and I look forward to getting pfsense up and going next week.
-
Somebody has some notes on the 6501 which I'm too lazy to search for, but if it fails trying to mount root you need to hit a key at the countdown to interrupt the boot. Then you have to
set kern.cam.boot_delay=10000
boot
Once it boots, you have to create a loader.conf.local in /boot with
kern.cam.boot_delay=10000
to make it permanent. -
Somebody has some notes on the 6501 which I'm too lazy to search for, but if it fails trying to mount root you need to hit a key at the countdown to interrupt the boot. Then you have to
set kern.cam.boot_delay=10000
boot
Once it boots, you have to create a loader.conf.local in /boot with
kern.cam.boot_delay=10000
to make it permanent.No matter which image I use, I get the soekris memory test, the 5-4-3-2-1 countdown, and then nothing after that. I've ordered an mSATA converter, but it's frustrating that there isn't a good solution to this other than more hardware.
-
The fact that it works for everyone else but not you might indicate something wrong with your board or the process you're doing. Before anything else, make sure you're on the latest BIOS.
-
The fact that it works for everyone else but not you might indicate something wrong with your board or the process you're doing. Before anything else, make sure you're on the latest BIOS.
Either Soekris is in the habit of shipping bad boards, or something has changed. I read this thread and said, "Hmm. Sounds a lot like the thread I started 2-3 days ago saying the same things."
I used dd on a Mac to copy numerous images to the 4 GB USB drive. It never would boot on the Soekris 6501. I got the same thing: memory check, countdown 5-4-3-2-1. Then nothing.
How many people buy into the odds that Soekris shipped two bad units to two pfsense users scattered remotely apart from each other? I don't.
My firmware is 1.41a (USB-bootable, according to Soekris).
-
If you read back on the Soekris boards you'll also find that it's very picky about the USB sticks it will boot from, I was posting in a thread when the USB code came out with Soren and out of the dozen or so USB sticks I have, I only managed to get it to boot from one. He was trying to acquire a bunch of different sticks to try to narrow down the issue but I'm not sure what happened there, hasn't had an update in a while.
-
If you read back on the Soekris boards you'll also find that it's very picky about the USB sticks it will boot from, I was posting in a thread when the USB code came out with Soren and out of the dozen or so USB sticks I have, I only managed to get it to boot from one. He was trying to acquire a bunch of different sticks to try to narrow down the issue but I'm not sure what happened there, hasn't had an update in a while.
Well, this unit is using the 4GB Sandisk Cruiser (tiny thing) that Soekris sells WITH the unit. You'd think it would work…
-
You'd think so… I haven't had my hands on one of those, though. The one stick I was able to boot from was a Sandisk though. You might try some of the other ports on the box.
I have had lots of positive feedback from people using my serial memstick and it works for most of us.
-
Well, this unit is using the 4GB Sandisk Cruiser (tiny thing) that Soekris sells WITH the unit. You'd think it would work…
I used the 4GB Sandisk from Soekris in the last two 6501's I setup. They had the 1.41a bios. It works for me (TM)
Either you did something wrong, or there is an issue with your 6501 or USB stick.
I would try to boot a laptop or something with the USB image. If you can boot another machine with the USB stick, you will know the image is good.
P.S. It's generally considered poor form to hijack a 'related' thread when you have one of your own open. -
I installed my first Soekris 6501 today with cheapo usb stick, using the jimp serial image on files.pfsense.org.
I installed it to a 32GB Kingston SSD.
Worked like a charm. -
P.S. It's generally considered poor form to hijack a 'related' thread when you have one of your own open.
Yeah …. hijack ....... right. Someone started a new thread almost identical to the one I had started a day before with the same issue. You think I might be interested in comments on both threads since they relate ? ? ? ? ? Or did you think that someone might respond to mine and not his with different answers? In case you don't think so, read the two discussions. They have.
If he had commented on my already-open-thread and said, "I have the same issue," I wouldn't have minded a bit.
For those who miss the other thread, here's the update I posted there:
BUT NOW IT WILL BOOT OFF USB if I do not put the SSD card in the unit.
Here's what I did. Plugged an ethernet cable into the unit. That's it. No changes of any other kind.
It will boot off USB with the SATA drive in the Soekris but without the internal SSD.
It will NOT boot off the USB if the SSD drive is installed in EITHER SSD slot.
I don't know if this indicates a bad SSD drive, bad Soekris motherboard or what. It was all purchased from Soekris, so presumably they will make it good for the end customer who purchased it.
Strange…
-
It's also poor form to cop an attitude with people trying to help you. Good luck, I'm out of this one.
-
I have the exact same problem on soekris 6501, boots happily off the Sandisk USB but if I plug in my mSATA drive supplied by Soekris it won't boot anything :(
I wanted to boot off the USB then install onto my SATA drive in the installation menu.
Any update on this?
Cheers
-
Just to wrap this up for any future searchers on this problem I have found a solution that works for me.
With the USB SanDisk and mSata in the Soekris 6501 change the BootDrive to
81, FF ,FF, FF
with the command
set bootdrive=81
This forces the USB drive to boot first which then lets you install the pfsense onto the mSATA drives.
To boot from the mSata drive change the boot order back to 80 which is the mSata drive with
set bootdrive=80
This all works perfectly. This pissed me off all day but it works. I hate working with console cables and terminal screens!
Good luck
