DragonFly BSD
DragonFly bugs List (threaded) for 2004-07
[Date Prev][Date Next]  [Thread Prev][Thread Next]  [Date Index][Thread Index]

Re: FAT32?


From: "M. Schatzl" <lists@xxxxxxxxxxxxxxx>
Date: Fri, 23 Jul 2004 17:57:28 +0200

Adonijah wrote:
Simon 'corecode' Schubert wrote:

On 22.07.2004, at 02:27, M. Schatzl wrote:

I encountered strange behaviour related to FAT32-partitions. Since I have 3 IDE's in the box, the mount-command would be (see fdisk output at the end of the message):
mount_msdos /dev/ad2s4 /mnt


This fails with an "mount_msdos /dev/ad2s4: Invalid argument". Same error if i append a "c" at the end. This machine has another FAT32 partition on the first disk. Exactly the same here.


[snipsnap]

******* Working on device /dev/ad2 *******
parameters extracted from in-core disklabel are:
cylinders=159560 heads=16 sectors/track=63 (1008 blks/cyl)

Figures below won't work with BIOS for partitions not in cyl 1
parameters to be used for BIOS calculations are:
cylinders=159560 heads=16 sectors/track=63 (1008 blks/cyl)

Media sector size is 512
Warning: BIOS sector numbering starts with sector 1
Information from DOS bootblock is:
The data for partition 1 is:
sysid 131,(Linux filesystem)
    start 63, size 97713 (47 Meg), flag 80 (active)
        beg: cyl 0/ head 1/ sector 1;
        end: cyl 96/ head 15/ sector 63
The data for partition 2 is:
sysid 130,(Linux swap or Solaris x86)
    start 97776, size 2539152 (1239 Meg), flag 0
        beg: cyl 97/ head 0/ sector 1;
        end: cyl 1023/ head 15/ sector 63
The data for partition 3 is:
sysid 131,(Linux filesystem)
    start 2636928, size 5859504 (2861 Meg), flag 0
        beg: cyl 1023/ head 15/ sector 63;
        end: cyl 1023/ head 15/ sector 63
The data for partition 4 is:
sysid 5,(Extended DOS)
    start 8496432, size 152340048 (74384 Meg), flag 0
        beg: cyl 1023/ head 15/ sector 63;
        end: cyl 1023/ head 15/ sector 63



this is not a FAT slice. it's a extended slice. the FAT slices are *inside* of that. This reminds me of rewriting fdisk...


you have to specify the simulated extended slice number 5 (at least) to access it, like chris already wrote: ad2s5/ad2s5c


Actually, I have an extended DOS partition and to access the logical partition within I had to create as0s5, as06, ad0s7, ad0s8 and so on. That worked, nothing else did.

A new world created obviously a lot of additional device nodes. But even when I try looping over all ad2*-devices to get the ones which mount without error, there is exactly no data on them. I verified the existance of data on that disks several time with serveral systems. Got to track this down a bit more.


/m



[Date Prev][Date Next]  [Thread Prev][Thread Next]  [Date Index][Thread Index]