5. Usb flash - pfsense 2.0 no support?

Usb flash - pfsense 2.0 no support?

  • S

    Hello! i'm sorry bad english :(
    install pfsense 2.0 nano 1g (physdiskwrite 0.5.2).

    boot…...

    
ugen2.2: <jetflash>at usbus2
umass0: <jetflash 0="" 2="" mass="" storage="" device,="" class="" 0,="" rev="" 2.00="" 1.41,="" addr="">on usbus2
Root mount waiting for: usbus2
Trying to mount root from ufs:/dev/ufs/pfsense0
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/ufs/pfsense0
vfs.root.mountfrom.options=ro,sync,noatime

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></jetflash></jetflash>

    device "JetFlash Mass Storage Device" no set da0 :(

    boot 1.2.3…......

    
da0 at umass-sim0 bus 0 target 0 lun 0
da0: <jetflash mass="" storage="" device="">Removable Direct Access SCSI-2 device
da0: 40.000MB/s transfers
da0: 3856MB (7897088 512 byte sectors: 255H 63S/T 491C)</jetflash>

    usb flash loading pfsense 1.2.3 ok

    usb flash no support pfsense 2.0?

    0
  • Rebel Alliance Developer Netgate

    Are you using a full install of 1.2.3 or nanobsd?

    2.0 should have the same (and more) drivers as 1.2.3.

    0
  • S

    @jimp:

    Are you using a full install of 1.2.3 or nanobsd?

    i use nanobsd (hp t5520 - no hdd). nanobsd 1.2.3 work good, 2.0 no boot :(

    2.0 should have the same (and more) drivers as 1.2.3.

    But doesn't work 2.0 :(

    0
  • Rebel Alliance Developer Netgate

    Can you post the full boot log from 1.2.3 and 2.0?

    That would help us figure it out.

    0
  • S

    @jimp:

    Can you post the full boot log from 1.2.3 and 2.0?

    That would help us figure it out.

    Yes I can, but only tomorrow!

    0
  • W

    Some time ago I bought a number of USB adapters for note book drives. Some worked with FreeBSD and some didn't. I discovered in the FreeBSD sources there was a table for USB devices with "quirks" and code work arounds for the quirks. The devices that worked used a different chip than the devices that didn't and there was no "quirk" entry for either device.

    Speculation: You may have a quirky USB device that FreeBSD 8.0 doesn't know about. (A simple editing error might have meant the knowledge of this quirk in previous versions of FreeBSD was lost to FreeBSD 8.0. If I recall correctly, the USB stack was reworked in FreeBSD 8.0.)

    Suggestion: See if you can read the whole USB drive on a FreeBSD 8.0 system by the shell command (or some suitable variant):```

    dd if=/dev/da1 of=/dev/null

    
Alternatively you could try using a device from a better known supplier such as SanDisk or Kingston or … though I don't know this would guarantee you would have a compatible device.
    0
  • S

    @wallabybob:

    Some time ago I bought a number of USB adapters for note book drives. Some worked with FreeBSD and some didn't. I discovered in the FreeBSD sources there was a table for USB devices with "quirks" and code work arounds for the quirks. The devices that worked used a different chip than the devices that didn't and there was no "quirk" entry for either device.

    Speculation: You may have a quirky USB device that FreeBSD 8.0 doesn't know about. (A simple editing error might have meant the knowledge of this quirk in previous versions of FreeBSD was lost to FreeBSD 8.0. If I recall correctly, the USB stack was reworked in FreeBSD 8.0.)

    Suggestion: See if you can read the whole USB drive on a FreeBSD 8.0 system by the shell command (or some suitable variant):```

    dd if=/dev/da1 of=/dev/null

    
Alternatively you could try using a device from a better known supplier such as SanDisk or Kingston or … though I don't know this would guarantee you would have a compatible device.

    Probably it so.
    If will boot with cd-rom pfsense 2.0 and to instal the device usb flash….
    system.log

    
Jun 18 06:20:24 router kernel: ugen3.3: <jetflash>at usbus3
Jun 18 06:20:24 router kernel: umass0: <jetflash 0="" 3="" mass="" storage="" device,="" class="" 0,="" rev="" 2.00="" 1.41,="" addr="">on usbus3
Jun 18 06:20:24 router kernel: umass0:  SCSI over Bulk-Only; quirks = 0x0100
Jun 18 06:20:26 router kernel: umass0:0:0:-1: Attached to scbus0
Jun 18 06:20:26 router kernel: (probe0:umass-sim0:0:0:0): TEST UNIT READY. CDB: 0 0 0 0 0 0
Jun 18 06:20:26 router kernel: (probe0:umass-sim0:0:0:0): CAM status: SCSI Status Error
Jun 18 06:20:26 router kernel: (probe0:umass-sim0:0:0:0): SCSI status: Check Condition
Jun 18 06:20:26 router kernel: (probe0:umass-sim0:0:0:0): SCSI sense: UNIT ATTENTION asc:28,0 (Not ready to ready change, medium may have changed)
Jun 18 06:20:26 router kernel: da0 at umass-sim0 bus 0 scbus0 target 0 lun 0
Jun 18 06:20:26 router kernel: da0: <jetflash ts2gjfv10="" 8.07="">Removable Direct Access SCSI-2 device
Jun 18 06:20:26 router kernel: da0: 40.000MB/s transfers
Jun 18 06:20:26 router kernel: da0: 1956MB (4005888 512 byte sectors: 255H 63S/T 249C)
Jun 18 06:20:26 router kernel: GEOM: da0s1: geometry does not match label (16h,63s != 255h,63s).
Jun 18 06:20:26 router kernel: GEOM: da0s2: geometry does not match label (16h,63s != 255h,63s).

# mount /dev/da0s1a /mnt
mount: /dev/da0s1a : Operation not permitted
# df -h
Filesystem     Size    Used   Avail Capacity  Mounted on
/dev/ad0s1a    8.5G    177M    7.7G     2%    /
devfs          1.0K    1.0K      0B   100%    /dev
/dev/md0       3.6M     42K    3.3M     1%    /var/run
#</jetflash></jetflash></jetflash>

    Something not so with this device

    loading cd-pfsense 1.2.3…. and set usb flash

    
umass1: <jetflash 0="" 4="" mass="" storage="" device,="" class="" 0,="" rev="" 2.00="" 1.41,="" addr="">on uhub3
(probe0:umass-sim1:1:0:0): TEST UNIT READY. CDB: 0 0 0 0 0 0
(probe0:umass-sim1:1:0:0): CAM Status: SCSI Status Error
(probe0:umass-sim1:1:0:0): SCSI Status: Check Condition
(probe0:umass-sim1:1:0:0): UNIT ATTENTION asc:28,0
(probe0:umass-sim1:1:0:0): Not ready to ready change, medium may have changed
(probe0:umass-sim1:1:0:0): Retrying Command (per Sense Data)
da1 at umass-sim1 bus 1 target 0 lun 0
da1: <jetflash ts2gjfv10="" 8.07="">Removable Direct Access SCSI-2 device
da1: 40.000MB/s transfers
da1: 1956MB (4005888 512 byte sectors: 255H 63S/T 249C)

# mount /dev/da1s1a /mnt
WARNING: R/W mount of /mnt denied.  Filesystem is not clean - run fsck
mount: /dev/da1s1a : Operation not permitted</jetflash></jetflash>

    i can be not correct ver 2.0 i write a file img on usb flash? i use the program physdiskwrite 0.5.2

    0
  • S

    Version 2.0 has earned!
    Through usb hub, on a straight line to t5520 (http://www.computerland.kiev.ua/uploads/imgs/58734.jpg) does not wish to work.
    As occurs and with 3G modem.
    In version 2.0 all works only through usb hub.

    0
Log in to reply
 

Products

Services

Support

News

Resources

Company

Our Mission

We provide leading-edge network security at a fair price - regardless of organizational size or network sophistication. We believe that an open-source security model offers disruptive pricing along with the agility required to quickly address emerging threats.

Subscribe to our Newsletter

Product information, software announcements, and special offers. See our newsletter archive for past announcements.

© 2020 Rubicon Communications, LLC | Privacy Policy