Project

General

Profile

Actions

Bug #495

closed

USB drive fails to mount during boot

Added by Jeppe Oland about 14 years ago. Updated over 8 years ago.

Status:
Resolved
Priority:
Normal
Assignee:
-
Category:
Operating System
Target version:
Start date:
04/10/2010
Due date:
% Done:

0%

Estimated time:
Plus Target Version:
Release Notes:
Affected Version:
2.0
Affected Architecture:

Description

I installed pfSense-2.0-BETA1-20100407-1435 on a new SuperMicro X7SPA-H board.
The drive used was a 512 MB USB stick.
(During installation I removed the SWAP partition since otherwise there was not enough space).

After installing, it correctly boots from the USB stick and passes the initial pfSense option screen.
Then it fails to mount the drive like this:

--------------------- LOG FOLLOWS

If you have invalid mount options, reboot, and first try the following from the loader prompt:
da0 at umass-sim0 bus 0 scbus0 target 0 lun 0

da0: set vfs.root.mountfrom.options=rw
<CBM Flash Disk 5.00> Removable Direct Access SCSI-2 device

da0: 40.000MB/s transferand then remove invalid mount options from
/etc/fstab.
da0: 482MB (987136 512 byte sectors: 64H 32S/T 482C)

Loader variables:
vfs.root.mountfrom=ufs:/dev/da0s1a
vfs.root.mountfrom.options=rw

Manual root filesystem specification:
<fstype>:<device> Mount <device> using filesystem <fstype>
eg: ufs:/dev/da0s1a
eg: cd9660:/dev/acd0
This is equivalent to: mount -t cd9660 /dev/acd0 /

?                  List valid disk boot devices
&lt;empty line&gt; Abort manual input

mountroot> ?

List of GEOM managed disk devices:
ufsid/4bc0604f03725fe0 da0s1a da0s1 da0
Loader variables:
vfs.root.mountfrom=ufs:/dev/da0s1a
vfs.root.mountfrom.options=rw

Manual root filesystem specification:
<fstype>:<device> Mount <device> using filesystem <fstype>
eg: ufs:/dev/da0s1a
eg: cd9660:/dev/acd0
This is equivalent to: mount -t cd9660 /dev/acd0 /

?                  List valid disk boot devices
&lt;empty line&gt; Abort manual input

mountroot> ufs:/dev/da0s1a

--------------------- LOG ENDS

After entering the boot device manually, it continues booting just fine.

pfSense 1.2.3 worked fine on the same hardware.

Actions

Also available in: Atom PDF