> 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.
Check with the below commands (run them as user "root"), if the "BS_BootSig" byte (at offset 0x26 for FAT12 & FAT16, or offset 0x42 for FAT32) contains the expected value of "29": FAT12, FAT16: ============= # echo '0x26?BnaXna11Cna8C' | adb /dev/dsk/c3t0d0p1 0x26: 29 0x27: 0 0x2b: Flashdisk 0x36: FAT16 FAT32: ====== # echo '0x42?BnaXna11Cna8C' | adb /dev/dsk/c4t0d0p1 0x42: 29 0x43: 0 0x47: NONAME 0x52: FAT32 Replace the disk device argument after "adb" with the appropriate device name for the fdisk partition for your usb memory stick, that is supposed to containing the fat filesystem. The first output line from the above command should list the value of "29". If it's different from 29, Tamarack / hald is unable to identify it as a pcfs filesystem and won't automount it. Second line is a fat "volume id" and could be any number (but in the above two samples it isn't set and contains 0). Third line is the fat "volume label". Fourth line should contain "FAT12 ", "FAT16 " or "FAT32 ". If the first line doesn't show the expected value of "29", but the other three are ok (especially line four), patching the "BS_BootSig" byte in the first sector of the fat filesystem to a value of hex "29" should fix the problem with hald not auto-mounting the stick any more. > I even put a single new FAT32 partition on the > failing device, no effect. Which OS did you use to create the new FAT32 partition and filesystem? Solaris? Windows? Something else? This message posted from opensolaris.org
