Bug? System crash/don't boot if 3G USB stick is installed
I'm using pfSense 2.1.5 on PC Engines APU.1C. I have a HUAWEI E1820 3G stick and he is working fine so far. But if I reboot, system hangs at:
System going down IMMEDIATELY pfSense is now shutting down ... Nov 27 14:30:28 lighttpd: (server.c.1558)Waiting (max 60 seconds) for system process `vnlru' to stop...done Waiting (max 60 seconds) for system process `bufdaemon' to stop...done g (max 60 seconds) for system process `syncer' to stop...Syncing disks, vnodes remaining...0 0 done All buffers synced. Uptime: 1h10m40s re1: link state changed to DOWN re1: link state changed to UP re2: link state changed to DOWN usbus0: Controller shutdown uhub0: at usbus0, port 1, addr 1 (disconnected) re2: link state changed to UP usbus0: Controller shutdown complete usbus1: Controller shutdown uhub1: at usbus1, port 1, addr 1 (disconnected) ugen1.2: <huawei technologies=""> at usbus1 (disconnected) u3g0: at uhub1, port 5, addr 2 (disconnected)</huawei>
I have to power off by hand. I found out, if I add "hw.usb.no_shutdown_wait="1"" to loader.conf, system reboots fine. But then after a reboot, it hangs at:
SMP: AP CPU #1 Launched! cd0 at umass-sim0 bus 0 scbus0 target 0 lun 0 cd0: <huawei mass="" storage="" 2.31="">Removable CD-ROM SCSI-2 device cd0: 40.000MB/s transfers cd0: cd present [65536 x 2048 byte records] da0 at umass-sim1 bus 1 scbus1 target 0 lun 0 da0: <huawei tf="" card="" storage="">Removable Direct Access SCSI-2 device da0: 40.000MB/s transfers da0: Attempt to query device size failed: NOT READY, Medium not present da1 at umass-sim2 bus 2 scbus2 target 0 lun 0 da1: <multiple card ="" reader="" 1.00="">Removable Direct Access SCSI-4 device da1: 40.000MB/s transfers da1: 7580MB (15523840 512 byte sectors: 255H 63S/T 966C) Trying to mount root from ufs:/dev/da0s1a ROOT MOUNT ERROR: If you have invalid mount options, reboot, and first try the following from the loader prompt: set vfs.root.mountfrom.options=rw and then remove invalid mount options from /etc/fstab. 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 <empty line="">Abort manual input mountroot></empty></fstype></device></device></fstype></multiple></huawei></huawei>
I tried "ufs:/dev/da0s1a" but it don't works. I have to unplug the 3G USB and replug it, press Enter and the pfSense reboots fine.
I think this is a bug, isn't it? What can I do?
cmb last edited by
You should try on 2.2 for the first issue, might be better in that regard.
The second issue is because the card has a drive/card storage in it, which shifts your internal SSD/hard drive to a different identifier. It's da1 when the 3G card is in, da0 when it's not. You need to set your card to modem-only mode so it doesn't present that "drive".
Thank you! Just testet 2.2 and first issue is gone :)
But second issue is still present. How do I do that, to set it as modem only?
This is the bootup from coldstart, that works:
da0: 7580MB (15523840 512 byte sectors: 255H 63S/T 966C) da0: quirks=0x2 <no_6_byte>cd0 at umass-sim1 bus 1 scbus9 target 0 lun 0 cd0: <huawei mass="" storage="" 2.31="">Removable CD-ROM SCSI-2 device cd0: 40.000MB/s transfers cd0: Attempt to query device size failed: NOT READY, Medium not present cd0: quirks=0x10<10_BYTE_ONLY> da1 at umass-sim2 bus 2 scbus10 target 0 lun 0 da1: <huawei tf="" card="" storage="">Removable Direct Access SCSI-2 device da1: 40.000MB/s transfers da1: Attempt to query device size failed: NOT READY, Medium not present da1: quirks=0x2 <no_6_byte>Trying to mount root from ufs:/dev/da0s1a [rw]... Configuring crash dumps... Using /dev/da0s1b for dump device. Mounting filesystems... ___ ___/ f \ / p \___/ Sense \___/ \ \___/</no_6_byte></huawei></huawei></no_6_byte>
cmb last edited by
Follow the instructions here:
Got that. But after warmstart the same error is still present. And I also see more interfaces as cuaU0.0 (which should be the modem?!)
OK, I was to fast. It works now, thank you! :)