This is a discussion on Re: Sun Solaris USB Flash Drive mount command (scsa2usb driver) within the Sun Solaris Hardware forums, part of the Solaris Operating System category; --> Jan Birk <jb@hulen.biz> wrote in message news:<3F73CADF.5090406@hulen.biz>... > I use this device for my Sun Solaris keyring ramdisk (USB1): ...
| |||||||
| Register | FAQ | Members List | Calendar | Search | Today's Posts | Mark Forums Read |
| ||||
| Jan Birk <jb@hulen.biz> wrote in message news:<3F73CADF.5090406@hulen.biz>... > I use this device for my Sun Solaris keyring ramdisk (USB1): > mount -F pcfs /dev/dsk/c3t0d0s2:1 /usb > I don't know if the ':1' and ':c' does a difference :-) I do NOT have USB flash sticks mounted on Solaris yet, but, it seems from what I've read if the USB media to be mounted contains a valid FDISK partition table & the DOS filesystem is inside a separate FDISK partition, then you need the additional colon-FAT designation after /dev/dsk/c#t#d#s# (i.e., /dev/dsk/c#t#d#s#:{a-h} I don't know much, but, in Sun Solaris 8, there is apparently a problem with vold & the use or non-use of fdisk partition tables on the removable media. I'm told, for a USB flash card, the FAT filesystem on the device handled by the Solaris 8 scsa2usb driver seems to be hidden inside an fdisk partition ... but vold refuses to use that fdisk partition information. Reputedly vold only checks the whole '/dev/dsk/...p0' (x86) or '/dev/dsk/...s2' (Sparc) device Purportedly, for DOS USB devices, you have to manually mount the colon-FAT filesystem inside the FDISK partition from the camera using: csh# mount '/dev/dsk/...p0:c' (x86) or '/dev/dsk/...s2:c' (Sparc) syntax: csh# mount -r -F pcfs /dev/dsk/c2d0s0p0:c /usb csh# mount -r -F pcfs /dev/dsk/c4t0d0s2:c /usb The trick (for me) is determining exactly which of the following to mount for the Sun Solaris 8 USB removable device in each USB port: /dev/dsk/c#t#d#s7:h /dev/dsk/c#t#d#s6:g /dev/dsk/c#t#d#s5:f /dev/dsk/c#t#d#s4:e /dev/dsk/c#t#d#s3:d /dev/dsk/c#t#d#s2:c /dev/dsk/c#t#d#s1:b /dev/dsk/c#t#d#s0:a Q: Assuming I plugged into my Sun Solaris 8 SunBlade 1000 two USB flash cards; do you know how to tell EXACTLY which USB device (including the colon-letter FAT filesystem inside the fdisk partition) each flash card is plugged into? 'cause if I knew that ... I could then manually mount the USB drive. |
| ||||
| Eunice Santorini wrote: > The trick (for me) is determining exactly which of the following to > mount for the Sun Solaris 8 USB removable device in each USB port: > /dev/dsk/c#t#d#s7:h > /dev/dsk/c#t#d#s6:g > /dev/dsk/c#t#d#s5:f > /dev/dsk/c#t#d#s4:e > /dev/dsk/c#t#d#s3:d > /dev/dsk/c#t#d#s2:c > /dev/dsk/c#t#d#s1:b > /dev/dsk/c#t#d#s0:a > > Q: Assuming I plugged into my Sun Solaris 8 SunBlade 1000 two USB > flash cards; do you know how to tell EXACTLY which USB device > (including the colon-letter FAT filesystem inside the fdisk partition) > each flash card is plugged into? Well, it's really unlikely to be :d through :h. If you gave information about what's on the flash drive, it would be possible to be more specific. Does it have an FDISK partition on it? If so, then :a corresponds to the first FDISK partition, :b to the second, etc. > 'cause if I knew that ... I could then manually mount the USB drive. You can determine the c#t#d# part of it by looking in /dev/dsk and using the process of elimination. Try typing "format" to get a list of disks you already have. You could also try "df -k". Nobody can tell you which c# it is specifically, because these are assigned dynamically by the system and will depend on the particulars of what hardware you have, what order you installed it, etc. You'll have to figure that out for yourself. But anyway, once you have gone through the process of elimination and determined the /dev/dsk/c#t#d# part of the device name, the remaining possibilities are few enough that you should be able to try them all. I'd start with s0:a through s0:c, then try s2:a through s2:c. I've set followups to comp.unix.solaris and comp.sys.sun.admin, because I don't really think figuring out which /dev/dsk entry corresponds to something is relevant for the other groups. - Logan |