Lanner 7522 + Toshiba HDD boot problem



  • Hello,

    I am finishing an install on a Lanner 7522-B a 1GHz device with 5 ports 4 Giga and one 10/100 Intel.
    http://www.lannerinc.com/x86_Network_Appliances/FW-7522 for detailed specs.

    So far I have successfully installed the system on a Compact Flash device, I only had to do :

    There is also a quirk with the bootloader.  The embedded image set the bootloader to use a serial console. That isn't necessary with these boxes (the BIOS does console redirection to the serial port for you) and causes the boot to hang.  After writing the embedded image to a disk, you need to mount it on another FreeBSD system and rewrite the bootloader (fdisk -B /dev/<disk>).</disk>

    http://forum.pfsense.org/index.php?topic=26238.0;all

    Following this advice I have a working procedure to configure CF cards.

    Regarding disks I had no luck so far…
    I have managed to install the system successfully on an old SATA disk that I had, but It has been a pain in the … to try to install It on the expected target disk : an industrial Toshiba disk MKxx76GSXZ http://storage.toshiba.eu/cms/en/hdd/industrial/product_detail.jsp?productid=407

    --

    The Lanner device is based on the following hardware specs :

    Processor: Intel Celeron M 1GHz
    Chipset: Intel 910GMLE + ICH6M

    So far I have been able to :

    • Install the device with an embedded kernel.
    • But at the end of the boot, I can not auto mount my HDD whatever I do !!

    I have to manually mount It using the prompt.

    […]
    gen1.1: <intel>at usbus1
    uhub1: <intel 1="" 9="" ehci="" root="" hub,="" class="" 0,="" rev="" 2.00="" 1.00,="" addr="">on usbus1
    ad0: 238475MB <toshiba mk2576gsxz="" gs001a="">at ata0-master UDMA100 SATA
    uhub0: 2 ports with 2 removable, self powered
    uhub1: 2 ports with 2 removable, self powered
    ugen0.2: <vendor 0x04d9="">at usbus0
    Loader variables:
    vfs.root.mountfrom=
    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</empty></fstype></device></device></fstype></vendor></toshiba></intel></intel>

    Then I have to manually specify the device to boot from :

    mountroot> ufs:/dev/ad1s1a

    Then It is ok.

    –-

    Weired thing is that /etc/fstab seems to be correct :

    [2.0-RELEASE][root@pfSense.localdomain]/root(1): more /etc/fstab

    Device                Mountpoint      FStype  Options        Dump    Pass#

    /dev/ad1s1a            /              ufs    rw              1      1
    /dev/ad1s1b            none            swap    sw              0      0

    I have updated /boot/loader.conf.local with these settings :

    [2.0-RELEASE][root@pfSense.localdomain]/root(2): more /boot/loader.conf.local
    kern.cam.boot_delay=10000
    vfs.root.mountfrom="/dev/ad1s1a"

    And It does nothing :-(

    Furthermore, I don't think this kernel (embedded) is the best for the device, I think multiproc should be better.

    When I try to intall this one, the system freezes after displaying the startup options…

    If you could help me solve these problems, I'd be very happy !

    Sincerely yours.

    Greg.



  • Strange that the system reports your hard drive is ad0

    ad0: 238475MB <toshiba mk2576gsxz="" gs001a="">at ata0-master UDMA100 SATA</toshiba>

    but you are trying your hardest to persuade it that the hard drive is ad1:

    [2.0-RELEASE][root@pfSense.localdomain]/root(2): more /boot/loader.conf.local
    kern.cam.boot_delay=10000
    vfs.root.mountfrom="/dev/ad1s1a"

    What have I missed?



  • @wallabybob:

    Strange that the system reports your hard drive is ad0

    ad0: 238475MB <toshiba mk2576gsxz="" gs001a="">at ata0-master UDMA100 SATA</toshiba>

    but you are trying your hardest to persuade it that the hard drive is ad1:

    [2.0-RELEASE][root@pfSense.localdomain]/root(2): more /boot/loader.conf.local
    kern.cam.boot_delay=10000
    vfs.root.mountfrom="/dev/ad1s1a"

    What have I missed?

    I have to check that first thing in the morning (Paris, CEST time).

    But most probably what you have identified as the source of the error is a copy / paste from two different sessions where the HD was connected to two different slots.

    I am suspecting the HD from Toshiba to be the source of my / our problems, another guy had the exact same problem reported here : http://forum.pfsense.org/index.php/topic,38418.0.html

    Because I have successfully installed pfSense-2.0-Release on another older SATA drive without any problem…  ???

    But I'll check that in 9+ hours (I am in France).



  • The startup should report the file system it is trying to mount; for example on my system:

    ad0: 955MB <transcend 20071207="">at ata0-master UDMA33
    ad2: DMA limited to UDMA33, device found non-ATA66 cable
    ad2: 955MB <transcend 20071207="">at ata1-master UDMA33
    Root mount waiting for: usbus3 usbus2 usbus1 usbus0
    uhub0: 2 ports with 2 removable, self powered
    uhub1: 2 ports with 2 removable, self powered
    uhub2: 2 ports with 2 removable, self powered
    Root mount waiting for: usbus3
    Root mount waiting for: usbus3
    uhub3: 6 ports with 6 removable, self powered
    Trying to mount root from ufs:/dev/ad0s1a</transcend></transcend>

    I suggest you verify your startup is attempting to mount the correct disk, a disk previously reported in the startup output.



  • http://doc.pfsense.org/index.php/Full_install_on_Netgate_Hamakua

    Somehow you have to create another partition to have that work.
    Follow that guide and It works very smoothly.

    Thanks for everybody's help !


Log in to reply