> > snv_57 can manually mount the CF card but doesn't do it automatically.
> > Solaris 10 Update 3 does automatically mount it. So something that used
> > to work in Solaris 10 is now broken?
>
> I'm having similar issues here, a usb-stick refuses
> to automount on snv_57, while the same stick mounts
> fine back on snv_37. Other usb-sticks work on both
> without problems.
>
> I even put a single new FAT32 partition on the
> failing device, no effect.
So, first find out if the failing hot-plugged usb stick is recognized as
a new disk device, by looking at "iostat -En" output. That should
reveal the stick's Solaris' cXt0d0 device name. Let's assume it has
found the stick as device c3t0d0, or /dev/dsk/c3t0d0p0. If there is
no solaris disk device for the usb memory stick, we would have an
issue in Solaris' usb device drivers.
Next thing that is interesting is, if there is any fdisk partition table
on the device, check with: fdisk -RW - /dev/rdsk/c3t0d0p0
"fstyp -v" for the four primary fdisk partitions is interesting too:
fstyp -v /dev/rdsk/c3t0d0p1
fstyp -v /dev/rdsk/c3t0d0p2
fstyp -v /dev/rdsk/c3t0d0p3
fstyp -v /dev/rdsk/c3t0d0p4
Using "eject -l" you can find out if hald has found the new hot-plugged
device and if it was mounted.
The output of the command "hal-device" is interesting, too. It could
contain whatever information hald has found out about the hot
plugged usb disk device, and the filesystems found on it.
This message posted from opensolaris.org
