On Sun, 26 Dec 2004, lonblu wrote: > $ 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 > *
The part above is uninteresting. The partition table is stored starting at offset 1be and ending at offset 1fd, with 0x10 bytes per entry: > 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 As you can see, only the first entry contains non-zero values. Thus there really is only one partition in the table. > 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 Can you post the dmesg output showing what happens first at the time you plug in the device and then when you run supermount? Maybe it's just a question of loading the proper modules. > > I don't believe that for a moment. > I'm sorry you don't... I didn't mean to cast aspersions or make you feel bad! I just meant that unplugging a device while it is mounted is a dangerous thing to do, no matter what software you are running. > > 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) There may be something wrong with the hotplug scripts. Fedora 2 uses a 2.4 version of the Linux kernel, right? Under 2.4 the device naming with usb-storage works differently from under 2.6. (Not just naming, in fact -- the whole notion of device persistence is different.) That could easily explain the change in behavior you have seen. Alan Stern ------------------------------------------------------- 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
