> > fdisk -l /dev/sda > > > > Disk /dev/sda: 128 MB, 128450560 bytes > > 16 heads, 32 sectors/track, 490 cylinders > > Units = cylinders of 512 * 512 = 262144 bytes > > > > Device Boot Start End Blocks Id System > > /dev/sda1 * 1 490 125424 6 FAT16 > > That looks pretty clear. This device has only one partition, not two. > If you really want to be certain about it, do > > dd if=/dev/sda bs=512 count=1 | hexdump
$ dd if=/.dev/sda bs=512 count=1 | hexdump 1+0 records in 1+0 records out 512 bytes transferred in 0.037893 seconds (13512 bytes/sec) 0000000 befa 7c00 00bf b97a 0100 0efc 0e1f f307 0000010 eaa5 7a16 0000 bebb 337b 80c9 803f 0675 0000020 c5fe f38b 07eb 3f80 7500 fe02 83c1 10c3 0000030 fb81 7bfe e572 f983 7404 810b 03f9 7401 0000040 bb0a 7aa5 2ceb 87bb eb7a 8b27 024c 148b 0000050 01b8 bb02 7c00 13cd 0573 bcbb eb7a 2e13 0000060 fea1 3d7d aa55 0574 bcbb eb7a ea05 7c00 0000070 0000 8a2e 3c07 7400 530c 07bb b400 cd0e 0000080 5b10 eb43 ebed 4efe 206f 6f62 746f 6261 0000090 656c 7020 7261 6974 6f74 206e 6e69 7420 00000a0 6261 656c 4900 766e 6c61 6469 5020 7261 00000b0 6974 6f74 206e 6174 6c62 0065 6e49 6176 00000c0 696c 2064 726f 6420 6d61 6761 6465 4220 00000d0 6f6f 6174 6c62 2065 6170 7472 7469 6f69 00000e0 006e 0000 0000 0000 0000 0000 0000 0000 00000f0 0000 0000 0000 0000 0000 0000 0000 0000 * 00001b0 0000 0000 0000 0000 4c14 4d77 0000 0180 00001c0 0001 0f06 e960 0020 0000 d3e0 0003 0000 00001d0 0000 0000 0000 0000 0000 0000 0000 0000 * 00001f0 0000 0000 0000 0000 0000 0000 0000 aa55 0000200 Yes , another problem I found : -4- the kernel doesn't find any partition (/proc/partition) when I plug in the pen; I need to mount (access with supermount) /.dev/sda1 so the kernel shows up sda ed sda1 in /proc/partition > If the transfer remains slow, it might be because the device is generating > errors. If you turn on the usb-storage verbose debugging option in the > kernel configuration, maybe some error messages will show up in the system > log. Ok I'm compiling a new kernel with verbose debug > I don't believe that for a moment. I'm sorry you don't... > No matter what software you're > running, once the device is unplugged the compouter won't be able to write > out its dirty buffers. The only possible way to avoid problems is to make > sure there _are_ no dirty buffers, by using the "sync" option with mount, > for instance -- which reduces performance tremendously. Even with ext3 > it's possible to encounter data loss if you unplug a device without > unmounting it first. > > It's clear enough why the device name changed, though. The old name, > /dev/sda, was still in use because you hadn't unmounted the partition. With Supermount you don't have to umount things, it's done automagically... it is something like a journaled filesystem...always up.... and I'm really sorry Its development isn't so active. anyway I was using happily fedora 2 with supermount without having this problem... The device didn't change to sdb1,I think the problem is something with the scripts (in udev or hotplug maybe) ------------------------------------------------------- SF email is sponsored by - The IT Product Guide Read honest & candid reviews on hundreds of IT Products from real users. Discover which products truly live up to the hype. Start reading now. http://productguide.itmanagersjournal.com/ _______________________________________________ [email protected] To unsubscribe, use the last form field at: https://lists.sourceforge.net/lists/listinfo/linux-usb-users
