Dave wrote:
> 've got a Sony vaio VGN-Sz4XWN/C laptop running Solaris 10 Developer
> Edition 1/08 (snv 79). I just bought two PNY 2 GB flash drives. As soon
> as I fit one, the file manager opens and shows the drive.
>
>
> I can see it in df too.
>
> /dev/dsk/c3t0d0p0:1 1.9G 64K 1.9G 1% /media/UDISK
>
>
> and dmesg shows it:
>
> Apr 29 14:49:05 kingfisher usba: [ID 912658 kern.info] USB 2.0 device
> (usb90c,1000) operating at hi speed (USB 2.x) on USB 2.0 root hub:
> storage@3, scsa2usb0 at bus address 2
> Apr 29 14:49:05 kingfisher usba: [ID 349649 kern.info] USB DISK 2.0
> J22O5GPYT9MZV3JZ
> Apr 29 14:49:05 kingfisher genunix: [ID 936769 kern.info] scsa2usb0 is
> /pci@0,0/pci104d,81e6@1d,7/storage@3
> Apr 29 14:49:05 kingfisher genunix: [ID 408114 kern.info]
> /pci@0,0/pci104d,81e6@1d,7/storage@3 (scsa2usb0) online
> Apr 29 14:49:05 kingfisher scsi: [ID 193665 kern.info] sd1 at scsa2usb0:
> target 0 lun 0
> Apr 29 14:49:05 kingfisher genunix: [ID 936769 kern.info] sd1 is
> /pci@0,0/pci104d,81e6@1d,7/storage@3/disk@0,0
> Apr 29 14:49:06 kingfisher genunix: [ID 408114 kern.info]
> /pci@0,0/pci104d,81e6@1d,7/storage@3/disk@0,0 (sd1) online
> Apr 29 14:49:06 kingfisher genunix: [ID 314293 kern.info] device
> pci8086,27a2@2(display#0) keeps up device sd@0,0(disk#1), but the latter
> is not power managed
>
> BUT when I insert the second one, there is a popup which says "Cannot
> mount volume". No matter what USB slot the drives are entered, the first
> one always mounts. I can mount either drive, but not both at the same
> time. This is what dmes shows.
>
>
> Apr 29 14:50:05 kingfisher usba: [ID 912658 kern.info] USB 2.0 device
> (usb90c,1000) operating at hi speed (USB 2.x) on USB 2.0 root hub:
> storage@1, scsa2usb1 at bus address 3
> Apr 29 14:50:05 kingfisher usba: [ID 349649 kern.info] USB DISK 2.0
> 5EO8LJMRWRAYON3R
> Apr 29 14:50:05 kingfisher genunix: [ID 936769 kern.info] scsa2usb1 is
> /pci@0,0/pci104d,81e6@1d,7/storage@1
> Apr 29 14:50:05 kingfisher genunix: [ID 408114 kern.info]
> /pci@0,0/pci104d,81e6@1d,7/storage@1 (scsa2usb1) online
> Apr 29 14:50:05 kingfisher scsi: [ID 193665 kern.info] sd2 at scsa2usb1:
> target 0 lun 0
> Apr 29 14:50:05 kingfisher genunix: [ID 936769 kern.info] sd2 is
> /pci@0,0/pci104d,81e6@1d,7/storage@1/disk@0,0
> Apr 29 14:50:05 kingfisher genunix: [ID 408114 kern.info]
> /pci@0,0/pci104d,81e6@1d,7/storage@1/disk@0,0 (sd2) online
> Apr 29 14:50:05 kingfisher genunix: [ID 314293 kern.info] device
> pci8086,27a2@2(display#0) keeps up device sd@0,0(disk#2), but the latter
> is not power managed
>
>
>
> Since I can fit either flash drive into either USB slot, I know both the
> drives and USB sockets are ok. BUT if I try to put both flash drives
> into the system the second one does not mount.
>
> Any ideas? I thought that since one of them is /dev/dsk/c3t0d0p0:1, so
> the other would be /dev/dsk/c??????? But cant see such a device
>
> bash-3.2$ ls /dev/dsk/c3t*
> /dev/dsk/c3t0d0p0 /dev/dsk/c3t0d0s1 /dev/dsk/c3t0d0s15
> /dev/dsk/c3t0d0s7
> /dev/dsk/c3t0d0p1 /dev/dsk/c3t0d0s10 /dev/dsk/c3t0d0s2 /dev/dsk/c3t0d0s8
> /dev/dsk/c3t0d0p2 /dev/dsk/c3t0d0s11 /dev/dsk/c3t0d0s3 /dev/dsk/c3t0d0s9
> /dev/dsk/c3t0d0p3 /dev/dsk/c3t0d0s12 /dev/dsk/c3t0d0s4
> /dev/dsk/c3t0d0p4 /dev/dsk/c3t0d0s13 /dev/dsk/c3t0d0s5
> /dev/dsk/c3t0d0s0 /dev/dsk/c3t0d0s14 /dev/dsk/c3t0d0s6
>
> Any ideas??????????

Have you found any documentation that says flash drives are supported?
If so, and if you are paying for support, you could log a call and maybe
get it fixed.

Otherwise consider yourself fortunate that ONE works. And note that the
Solaris source is available. If all else fails, you can attempt to fix
it yourself!

Richard B. Gilbert wrote:
> Dave wrote:
>> 've got a Sony vaio VGN-Sz4XWN/C laptop running Solaris 10 Developer
>> Edition 1/08 (snv 79). I just bought two PNY 2 GB flash drives. As
>> soon as I fit one, the file manager opens and shows the drive.


>
> Have you found any documentation that says flash drives are supported?

No, but following my earlier post " ZFS mirror with USB disks on Blade
2000 ??" Ian Colins said using USB sticks was a good way to play with
ZFS. (I was asking about a SPARC, but this is an x86 box.) So I thought
I'd buy a couple and try them, with a view to learning about ZFS.

> If so, and if you are paying for support, you could log a call and maybe
> get it fixed.

No I am not.

> Otherwise consider yourself fortunate that ONE works.

I was far more painless than I expected. I was rather expecting to have
to find a device file, make a file system on it, but none of that. It
just worked as soon as I inserted it.

> And note that the
> Solaris source is available. If all else fails, you can attempt to fix
> it yourself!

Having the source is one thing. Understanding it is another quite
different thing.

Dave wrote:
> Richard B. Gilbert wrote:
>> Dave wrote:
>>> 've got a Sony vaio VGN-Sz4XWN/C laptop running Solaris 10 Developer
>>> Edition 1/08 (snv 79). I just bought two PNY 2 GB flash drives. As
>>> soon as I fit one, the file manager opens and shows the drive.
>
>
>>
>> Have you found any documentation that says flash drives are supported?
>
> No, but following my earlier post " ZFS mirror with USB disks on Blade
> 2000 ??" Ian Colins said using USB sticks was a good way to play with
> ZFS. (I was asking about a SPARC, but this is an x86 box.) So I thought
> I'd buy a couple and try them, with a view to learning about ZFS.
>
>> If so, and if you are paying for support, you could log a call and
>> maybe get it fixed.
>
> No I am not.
>
>> Otherwise consider yourself fortunate that ONE works.
>
> I was far more painless than I expected. I was rather expecting to have
> to find a device file, make a file system on it, but none of that. It
> just worked as soon as I inserted it.
>
>> And note that the Solaris source is available. If all else fails, you
>> can attempt to fix it yourself!
>
> Having the source is one thing. Understanding it is another quite
> different thing.

I agree! I doubt if I could do it myself. Wrapping your mind around
any large piece of code is not a chore to be undertaken lightly. Even
extremely well written and well documented code can require a great
amount of effort, almost equivalent to writing and debugging it yourself!

If you are unable to do it yourself, your remaining options are to pay
someone to do it for you or to resign yourself to using one flash drive
at a time.

In article <48173070@212.67.96.135>, Dave wrote:
>Any ideas? I thought that since one of them is /dev/dsk/c3t0d0p0:1, so
>the other would be /dev/dsk/c??????? But cant see such a device
>
>bash-3.2$ ls /dev/dsk/c3t*
>/dev/dsk/c3t0d0p0 /dev/dsk/c3t0d0s1 /dev/dsk/c3t0d0s15
>/dev/dsk/c3t0d0s7
>/dev/dsk/c3t0d0p1 /dev/dsk/c3t0d0s10 /dev/dsk/c3t0d0s2
>/dev/dsk/c3t0d0s8
>/dev/dsk/c3t0d0p2 /dev/dsk/c3t0d0s11 /dev/dsk/c3t0d0s3
>/dev/dsk/c3t0d0s9
>/dev/dsk/c3t0d0p3 /dev/dsk/c3t0d0s12 /dev/dsk/c3t0d0s4
>/dev/dsk/c3t0d0p4 /dev/dsk/c3t0d0s13 /dev/dsk/c3t0d0s5
>/dev/dsk/c3t0d0s0 /dev/dsk/c3t0d0s14 /dev/dsk/c3t0d0s6

You can run run "devfsadm -C" as root to clean up dangling
device links and create new ones.

Do you see the second USB storage device with cfgadm(1M)?

If you add a second, but different type USB storage device,
then does it mount?

John
groenveld@acm.org

John D Groenveld wrote:
> In article <48173070@212.67.96.135>, Dave wrote:
>> Any ideas? I thought that since one of them is /dev/dsk/c3t0d0p0:1, so
>> the other would be /dev/dsk/c??????? But cant see such a device
>>
>> bash-3.2$ ls /dev/dsk/c3t*
>> /dev/dsk/c3t0d0p0 /dev/dsk/c3t0d0s1 /dev/dsk/c3t0d0s15
>> /dev/dsk/c3t0d0s7
>> /dev/dsk/c3t0d0p1 /dev/dsk/c3t0d0s10 /dev/dsk/c3t0d0s2
>> /dev/dsk/c3t0d0s8
>> /dev/dsk/c3t0d0p2 /dev/dsk/c3t0d0s11 /dev/dsk/c3t0d0s3
>> /dev/dsk/c3t0d0s9
>> /dev/dsk/c3t0d0p3 /dev/dsk/c3t0d0s12 /dev/dsk/c3t0d0s4
>> /dev/dsk/c3t0d0p4 /dev/dsk/c3t0d0s13 /dev/dsk/c3t0d0s5
>> /dev/dsk/c3t0d0s0 /dev/dsk/c3t0d0s14 /dev/dsk/c3t0d0s6
>
> You can run run "devfsadm -C" as root to clean up dangling
> device links and create new ones.

After a cleanup, /dev/dsk shows the following created today (and I only
bought the devices today).

lrwxrwxrwx 1 root root 60 Apr 29 14:31 c3t0d0s0 ->
.../../devices/pci@0,0/pci104d,81e6@1d,7/storage@1/disk@0,0:a
lrwxrwxrwx 1 root root 60 Apr 29 14:31 c3t0d0s1 ->
.../../devices/pci@0,0/pci104d,81e6@1d,7/storage@1/disk@0,0:b
lrwxrwxrwx 1 root root 60 Apr 29 14:31 c3t0d0s2 ->
.../../devices/pci@0,0/pci104d,81e6@1d,7/storage@1/disk@0,0:c
lrwxrwxrwx 1 root root 60 Apr 29 14:31 c3t0d0s3 ->
.../../devices/pci@0,0/pci104d,81e6@1d,7/storage@1/disk@0,0:d
lrwxrwxrwx 1 root root 60 Apr 29 14:31 c3t0d0s4 ->
.../../devices/pci@0,0/pci104d,81e6@1d,7/storage@1/disk@0,0:e
lrwxrwxrwx 1 root root 60 Apr 29 14:31 c3t0d0s5 ->
.../../devices/pci@0,0/pci104d,81e6@1d,7/storage@1/disk@0,0:f
lrwxrwxrwx 1 root root 60 Apr 29 14:31 c3t0d0s6 ->
.../../devices/pci@0,0/pci104d,81e6@1d,7/storage@1/disk@0,0:g
lrwxrwxrwx 1 root root 60 Apr 29 14:31 c3t0d0s7 ->
.../../devices/pci@0,0/pci104d,81e6@1d,7/storage@1/disk@0,0:h
lrwxrwxrwx 1 root root 60 Apr 29 14:31 c3t0d0s8 ->
.../../devices/pci@0,0/pci104d,81e6@1d,7/storage@1/disk@0,0:i
lrwxrwxrwx 1 root root 60 Apr 29 14:31 c3t0d0s9 ->
.../../devices/pci@0,0/pci104d,81e6@1d,7/storage@1/disk@0,0:j
lrwxrwxrwx 1 root root 60 Apr 29 14:31 c3t0d0s10 ->
.../../devices/pci@0,0/pci104d,81e6@1d,7/storage@1/disk@0,0:k
lrwxrwxrwx 1 root root 60 Apr 29 14:31 c3t0d0s11 ->
.../../devices/pci@0,0/pci104d,81e6@1d,7/storage@1/disk@0,0:l
lrwxrwxrwx 1 root root 60 Apr 29 14:31 c3t0d0s12 ->
.../../devices/pci@0,0/pci104d,81e6@1d,7/storage@1/disk@0,0:m
lrwxrwxrwx 1 root root 60 Apr 29 14:31 c3t0d0s13 ->
.../../devices/pci@0,0/pci104d,81e6@1d,7/storage@1/disk@0,0:n
lrwxrwxrwx 1 root root 60 Apr 29 14:31 c3t0d0s14 ->
.../../devices/pci@0,0/pci104d,81e6@1d,7/storage@1/disk@0,0
lrwxrwxrwx 1 root root 60 Apr 29 14:31 c3t0d0s15 ->
.../../devices/pci@0,0/pci104d,81e6@1d,7/storage@1/disk@0,0
lrwxrwxrwx 1 root root 60 Apr 29 14:31 c3t0d0p0 ->
.../../devices/pci@0,0/pci104d,81e6@1d,7/storage@1/disk@0,0:q
lrwxrwxrwx 1 root root 60 Apr 29 14:31 c3t0d0p1 ->
.../../devices/pci@0,0/pci104d,81e6@1d,7/storage@1/disk@0,0:r
lrwxrwxrwx 1 root root 60 Apr 29 14:31 c3t0d0p2 ->
.../../devices/pci@0,0/pci104d,81e6@1d,7/storage@1/disk@0,0:s
lrwxrwxrwx 1 root root 60 Apr 29 14:31 c3t0d0p3 ->
.../../devices/pci@0,0/pci104d,81e6@1d,7/storage@1/disk@0,0:t
lrwxrwxrwx 1 root root 60 Apr 29 14:31 c3t0d0p4 ->
.../../devices/pci@0,0/pci104d,81e6@1d,7/storage@1/disk@0,0:u
#


>
> Do you see the second USB storage device with cfgadm(1M)?


I dont have time to read the man page, as I have a train to catch in
quite a short time, but I see:

# cfgadm
Ap_Id Type Receptacle Occupant
Condition
pcic0.pccard0 unknown empty unconfigured
unknown
pcie2 unknown empty unconfigured
unknown
pcie3 unknown/hp connected configured ok
pcie4 etherne/hp connected configured ok
pcie5 unknown empty unconfigured
unknown
usb0/1 unknown empty unconfigured ok
usb0/2 unknown empty unconfigured ok
usb1/1 unknown empty unconfigured ok
usb1/2 unknown empty unconfigured ok
usb2/1 usb-device connected configured ok
usb2/2 unknown empty unconfigured ok
usb3/1 unknown empty unconfigured ok
usb3/2 usb-device connected configured ok
usb4/1 usb-storage connected configured ok
usb4/2 unknown empty unconfigured ok
usb4/3 usb-storage connected configured ok
usb4/4 unknown empty unconfigured ok
usb4/5 unknown empty unconfigured ok
usb4/6 unknown disconnected unconfigured ok
usb4/7 unknown empty unconfigured ok
usb4/8 unknown empty unconfigured ok

> If you add a second, but different type USB storage device,
> then does it mount?

Not tried. I will try to find another one when I get home. I'm not sure
if I can find the only one I have, which is only 128 MB, so quite old.

>
> John
> groenveld@acm.org

Dave writes:

> I dont have time to read the man page, as I have a train to catch in
> quite a short time, but I see:
>
> # cfgadm
> Ap_Id Type Receptacle Occupant
....
> usb4/1 usb-storage connected configured ok
.....
> usb4/3 usb-storage connected configured ok


It is unclear which one of the above two failed to mount;
but try to (re)configure both of them:

cfgadm -y -c disconnect usb4/1
cfgadm -y -c configure usb4/1

and

cfgadm -y -c disconnect usb4/3
cfgadm -y -c configure usb4/3