Manual Root Filesystem Specification error
-
I used a LiveCD to install the latest version of PFSense to a 4 gig Microdrive connected to my computer through a USB writing device.
I then took the finished product, unaltered, and plugged it into my Soekris Net4801, which HAS been working on a 2 gig CF card.
When booting, I get the error:
List of GEOM managed disk devices:
Manual root filesystem specification:
<fstype>:<device> Mount <device>using filesystem <fstype>eg. ufs:da0s1a
? List valid disk boot devices
<empty line=""> Abort manual inputmountroot>
And it does NOT list ANY valid disk boot devices.
What is the problem, and how can I fix this?</empty></fstype></device></device></fstype>
-
http://blog.pfsense.org/?p=15
-
I then took the finished product, unaltered, and plugged it into my Soekris Net4801, which HAS been working on a 2 gig CF card.
I have no problems with CF cards. I do, however, have problems with Microdrives.
-
There are a number of threads about problems with CF cards, I'd suggest a search of the forum.
-
There are also quite a few threads around about geting microdrives to run.
I think theres even a devwiki-entry.
http://devwiki.pfsense.com -
Cry Havok:
I have no problems with CF cards. I do, however, have problems with Microdrives.
That's the second time I had to emphasize that. Please pay closer attention. My problem is NOT with a CF card, but with a Microdrive not being recognized during boot.
GruensFroeschli:
DevWiki tells me how to install pfsense on a Microdrive, which I already know. It doesn't tell me how to solve this particular problem.
Also previous posts did the same, as well as suggest IDE to CF adapters and changing the BIOS on ALIX and WRAPs. I use a Soekris, and the microdrive I use can operate under 3.3v, which undercuts the point of using a IDE to CF adapter. In addition, I can't fit any of those adapters in my current case.
The closest I've come to was using Grub to point it to the right device, but my problem is that the device is not even seen.
-
Oh yeah, I almost forgot….
In addition to the drive being able to run at 3.3v, it also has no built-in firmware or listed firmware versions. I understand that firmware could also be a reason a drive isn't recognized. This drive is built for this kind of operation.
-
I know on the ALIX there is a way to change how the drive will be addressed.
Do you have on the soekris something similar? -
Not that I'm aware of.
-
Well, after a bit of messing around, the BIOS does in fact SEE the drive, so all is functioning well.
It will boot a good portion, but always fails at:
Trying to mount root from ufs:/dev/da0s1a
Manual root filesystem specification:
<fstype>:<device> Mount <device>using filesystem <fstype>eg. ufs:da0s1a
? List valid disk boot devices
<empty line=""> Abort manual inputmountroot> ?
List of GEOM managed disk devices:
Manual root filesystem specification:
<fstype>:<device> Mount <device>using filesystem <fstype>eg. ufs:da0s1a
? List valid disk boot devices
<empty line=""> Abort manual inputmountroot>
See? Nothings listed. I don't understand.</empty></fstype></device></device></fstype></empty></fstype></device></device></fstype>
