mount_msdosfs anomaly
hoe-waa at hawaii.rr.com
hoe-waa at hawaii.rr.com
Sun May 16 12:34:01 PDT 2004
ALoha Malcolm
I apologize, I should of answered yesterday.
----- Original Message -----
From: Malcolm Kay <malcolm.kay at internode.on.net>
Date: Friday, May 14, 2004 5:14 pm
Subject: Re: mount_msdosfs anomaly
> On Saturday 15 May 2004 12:04, hoe-waa at hawaii.rr.com wrote:
> > -
> >
> > > On Saturday 15 May 2004 08:59, hoe-waa at hawaii.rr.com wrote:
> > > > Aloha Again
> > > >
> > > > Okay, I had some time and since I had just installed
> Slackware, I
> > >
> > > didn't> mind blowing it away.
> > >
> > > > Using cfdisk from the Slackware CD, I re-partitioned slices 3
> > >
> > > and up. I
> > >
> > > > now have a fat32 3Gig slice in primary partition/slice ad0s3. I
> > >
> > > then have
> > >
> > > > four 12 Gig slices (5 - 8) set up as linux partitions. Finally
> > >
> > > slice 9
> > >
> > > > (ad0s9/hda9) is linux swap.
> > >
> > > Do you still have Fat32 in slice 1?
> > >
> > > It is my impression that MS will not allow more than 1 MS primary
> > > slice. It
> > > will force 2nd and subsequent MS file systems into extended
> > > partitions. Of
> > > course if you created "and formatted" the slice outside of MS then
> > > the
> > > comment is irrelevant.
> > >
> > > Posting the output of fdisk (on FreeBSD) might help.
> > >
> > > Malcolm
> >
> > Aloha Malcolm
> >
> > Thanks for responding. Here is the output of fdisk when ran from
> FBSD:> frankie# fdisk
> > ******* Working on device /dev/ad0 *******
> > parameters extracted from in-core disklabel are:
> > cylinders=155061 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=155061 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 11 (0x0b),(DOS or Windows 95 with 32 bit FAT)
> > start 63, size 10249407 (5004 Meg), flag 0
> > beg: cyl 0/ head 1/ sector 1;
> > end: cyl 637/ head 254/ sector 63
> > The data for partition 2 is:
> > sysid 165 (0xa5),(FreeBSD/NetBSD/386BSD)
> > start 10249470, size 40949685 (19994 Meg), flag 80 (active)
> > beg: cyl 638/ head 0/ sector 1;
> > end: cyl 1023/ head 254/ sector 63
> > The data for partition 3 is:
> > sysid 12 (0x0c),(DOS or Windows 95 with 32 bit FAT (LBA))
> > start 51199155, size 5863725 (2863 Meg), flag 0
> > beg: cyl 1023/ head 254/ sector 63;
> > end: cyl 1023/ head 254/ sector 63
> > The data for partition 4 is:
> > sysid 5 (0x05),(Extended DOS)
> > start 57062880, size 99233505 (48453 Meg), flag 0
> > beg: cyl 1023/ head 254/ sector 63;
> > end: cyl 1023/ head 254/ sector 63
> > frankie#
> > As you can see, I still have 98SE on partition 1 and partition 3
> shows as
> > fat32. Slackware was re-installed and is working on P-8 with
> linux-swap 0n
> > P-9.
> >
> > Is this weird that I cannot mount ad0s3?
> >
>
> OK, this has moved beyond my ken; but it has aroused my curiosity.
>
> What is the precise message when trying to mount ad0s3?
>
$ su
Password:
frankie# mount_msdosfs /dev/ad0s3 /shared
mount_msdosfs: /dev/ad0s3: Invalid argument
frankie#
> You do have a device /dev/ad0s3 revealed by ls?
>
Yes
frankie# ls -l /dev/ad*
crw-r----- 1 root operator 4, 10 May 14 12:54 /dev/ad0
crw-r----- 1 root operator 4, 11 May 14 12:54 /dev/ad0s1
crw-r----- 1 root operator 4, 12 May 14 12:54 /dev/ad0s2
crw-r----- 1 root operator 4, 16 May 14 02:54 /dev/ad0s2a
crw-r----- 1 root operator 4, 17 May 14 12:54 /dev/ad0s2b
crw-r----- 1 root operator 4, 18 May 14 12:54 /dev/ad0s2c
crw-r----- 1 root operator 4, 19 May 14 02:54 /dev/ad0s2d
crw-r----- 1 root operator 4, 20 May 14 02:54 /dev/ad0s2e
crw-r----- 1 root operator 4, 21 May 14 02:54 /dev/ad0s2f
crw-r----- 1 root operator 4, 13 May 14 12:54 /dev/ad0s3
crw-r----- 1 root operator 4, 14 May 14 12:54 /dev/ad0s4
crw-r----- 1 root operator 4, 22 May 14 12:54 /dev/ad0s5
crw-r----- 1 root operator 4, 23 May 14 12:54 /dev/ad0s6
crw-r----- 1 root operator 4, 24 May 14 12:54 /dev/ad0s7
crw-r----- 1 root operator 4, 25 May 14 12:54 /dev/ad0s8
crw-r----- 1 root operator 4, 26 May 14 12:54 /dev/ad0s9
frankie#
> Can you mount slice3 under slackware?
>
No. But I don't receive any error. Also, I have fstab in Slack supposedly auto mounting hda3 but it doesn't happen. curiouser and curiouser!
> You say MS reports the slice as FAT32, but has it actually been
> formatted?Can you write to it?
>
Yes and Yes. In win98se I formated what appears as drive D: and then did a full scan disk. I have written 2 jpeg files and 1 text file to the drive for test purposes.
> Have you tried mounting the Slackware slice under FreeBSD?
>
Unfortunately, Slck is installed as reiserfs.
> Does someone out there know the significance of "sysid 12" versus
> "sysid 11"?
>
> I incidently I've found you can see inside an extended partition by
> targeting
> the extended partition/slice with fdisk instead of the entire
> physical disk.
> (Which is probably quite irrelenent to your problem.)
>
> Malcolm
>
Thanks again for your response and help. With all the brains working on this, I know a solution is forthcoming :)
Robert
More information about the freebsd-questions
mailing list