DragonFly cannot detect existing FreeBSD partitions during install and cannot detect SanDisk USB flash drive during install

[Archimedes Gaviola]

On Sat, Jul 26, 2008 at 1:32 PM, Matthew Dillon
<dillon at apollo.backplane.com> wrote:
>
> :Hi,
> :
> :I have a notebook PC with existing FreeBSD disk partitions of 6.2 and
> :5.5 releases and then to install DragonFly 2.0 for multiple OS
> :booting. Before I begin installing DragonFly, I already created a
> :slice for it using FreeBSD-6.2 installer and I assume the same slice
> :type of 165 that DragonFly is using but somehow it failed to detect
> :existing FreeBSD partitions.  So, what I did next is to try installing
> :DragonFly on my 1GB SanDisk USB flash drive but somehow it failed to
> :detect the device during installation. Although I know this USB
> :drive's driver is supported by DragonFly as I've have tried plugging
> :it on another PC with DragonFly.
> :
> :da0 at umass-sim0 bus 0 target 0 lun 0
> :da0: <SanDisk U3 Cruzer Micro 3.21> Removable Direct Access SCSI-2 device
> :da0: Serial Number \^_
> :da0: 1.000MB/s transfers
> :da0: 973MB (1994385 512 byte sectors: 64H 32S/T 973C)
> :
> :Thanks,
> :Archimedes
>
>    If the installer isn't seeing the usb device it could be that
>    booting from the live CD or equivalent isn't loading all the necessary
>    modules.  You'd have to play with it manually from a root prompt.
>    Try kldload'ing the ehci driver maybe.
>
>    Maybe we could figure out what is going on from the dmesg output
>    on the laptop after booting the DFly live-cd?
>
>                                        -Matt
>                                        Matthew Dillon
>                                        <dillon at backplane.com>
>

Hi Matt,

Yes, you are right. After kldload'ing the ehci driver manually, it
automatically detects my SanDisk USB flash drive. I proceeded to
installation and got successful with it. However when booting after
installation, it stops somewhere while mounting the device. Below is
the error encountered.

Mounting root from ufs:/dev/da0s1a
no disk named 'da0s1a'
setrootbyname failed
ffs_mountroot: can't find rootvp
root mount failed: 6

Manual root filesystem specification:
<fstype>:<device>  Specify root (e.g. ufs:da0s1a)
?                           List valid disk boot devices
panic                     Just panic
abort                      Abort manual input
mountroot>

mountroot> ?
Possibly valid device for 'ufs' root:
"cd" "md" "ad" "acd" "mfs"

Here, I typed  "?" where it doesn't show any "da" device

mountroot> panic or abort
panic  :panic from console
Trace beginning at frame 0xc07bdcb8
panic (c07bdcdc,a,c07bdce5,62,c07bdd6c) at panic+0x8c
panic (c0539aee,c07bdce0,696e6170,c16a0063,80283) at panic+0x8c
vfs_mountroot_ask (c05d6ef8,cb286c20,c07bdd98,c02a54c8,0) at
vfs_mountroot_ask+0x1cb
vfs_mountroot(0,ffff,7bac00,7c8000,7c8000) at vfs_mountroot + 0xa9
mi_starup (7ba000,d,c0613ab8,c07bdc64,c07bdc54) at mi_startup+0x92
begin () at begin+0x42
Debugger ("panic")
Stopped at         Debugger+0x34 :  movb    $0,in_Debugger.3949
db>

Panic is displayed when I invoked "abort" or "panic". Is this a bug?

Thanks,
Archimedes