Date: Thu, 13 May 2004 16:25:33 -0400 (EDT) From: Jerry McAllister <jerrymc@clunix.cl.msu.edu> To: hoe-waa@hawaii.rr.com Cc: questions@freebsd.org Subject: Re: mount_msdosfs anomaly Message-ID: <200405132025.i4DKPYc27703@clunix.cl.msu.edu> In-Reply-To: <af6113afa1f8.afa1f8af6113@socal.rr.com> from "hoe-waa@hawaii.rr.com" at May 13, 2004 09:26:34 AM
next in thread | previous in thread | raw e-mail | index | archive | help
> > Aloha > I first used a win98 boot disk to set slice 1(partition 1) a 5 Gig for > my win98 slice. After installing win98, I used the freebsd 5.2.1 CD to > set up the freebsd slice 2 at 20 Gig. OK. I haven't had time (or a spare machine) to play with 5.xxx yet. > After installing freebsd I used Slackware 9.1 CD and the cfdisk program > on it to partition the rest of the disk. Slice/partition3 is a primary. > Slice 4 is extended with logical slices/partitions 5 through 10. I > installed Slackware on slice 8 with a linux swap on slice 9 and a 2.7Gig > fat32 on slice 10. Well, that (using Slackware and being logical partitions within an extended ) explains some things about how you got those slices. I believe FreeBSD is quite limited in its ability to talk to MS extended partitions. > > Here is the output of ls -l /dev/ad* First time I have seen slice numbers that high. But, since they are special, I am not sure it mean anything. Hopefully someone else will know more about that. ////jerry > $ ls -l /dev/ad* > crw-r----- 1 root operator 4, 10 May 13 09:10 /dev/ad0 > crw-r----- 1 root operator 4, 11 May 13 09:10 /dev/ad0s1 > crw-r----- 1 root operator 4, 27 May 13 09:10 /dev/ad0s10 > crw-r----- 1 root operator 4, 12 May 13 09:10 /dev/ad0s2 > crw-r----- 1 root operator 4, 16 May 12 23:10 /dev/ad0s2a > crw-r----- 1 root operator 4, 17 May 13 09:10 /dev/ad0s2b > crw-r----- 1 root operator 4, 18 May 13 09:10 /dev/ad0s2c > crw-r----- 1 root operator 4, 19 May 12 23:10 /dev/ad0s2d > crw-r----- 1 root operator 4, 20 May 12 23:10 /dev/ad0s2e > crw-r----- 1 root operator 4, 21 May 12 23:10 /dev/ad0s2f > crw-r----- 1 root operator 4, 13 May 13 09:10 /dev/ad0s3 > crw-r----- 1 root operator 4, 14 May 13 09:10 /dev/ad0s4 > crw-r----- 1 root operator 4, 22 May 13 09:10 /dev/ad0s5 > crw-r----- 1 root operator 4, 23 May 13 09:10 /dev/ad0s6 > crw-r----- 1 root operator 4, 24 May 13 09:10 /dev/ad0s7 > crw-r----- 1 root operator 4, 25 May 13 09:10 /dev/ad0s8 > crw-r----- 1 root operator 4, 26 May 13 09:10 /dev/ad0s9 > > It shows ad0s10 but I'm not sure that it can be mounted. Has anyone ever done it? > > Thanks for all of the responses. > Robert > > ----- Original Message ----- > From: Jerry McAllister <jerrymc@clunix.cl.msu.edu> > Date: Thursday, May 13, 2004 4:02 am > Subject: Re: mount_msdosfs anomaly > > > > > > > Jerry McAllister wrote: > > > >> Aloha > > > >> > > > >> I have a 80 gig hard drive that I have sliced up for multiple > > > >> distros of linux and freebsd. I have win98 on slice 1 and freebsd > > > >> on slice 2. On slice 10 I have a 2.7 Gig slice formatted as fat32 > > > >> for data sharing between all distros. > > > >> > > > >> When logged into frebsd (5.2.1) i can mount the win98 slice with > > > >> "mount_msdosfs /dev/ad0s1 /win98" without any trouble. > > > >> > > > >> When I attempt to mount slice 10 with "mount_msdosfs /dev/ad0s10 > > > >> /shared" I get the following error: > > > >> > > > >> mount_msdosfs: /dev/ad0s10: invalid argument. > > > >> > > > >> Slice 10 was formatted in win98 and scan disk was run. I have a > > > >> text file and two jpeg photos in the slice. > > > >> > > > > > > > > > > > > Only 4 primary slices are recognized. FreeBSD will not talk > > to a > > > > slice 10 and I don't think anything MS will either in a standard > > > > manner. That is why they came up with extended partitions. What > > > > did you use to create the extra slices? > > > > > > > > ////jerry > > > > > > Isn't ad?s5 and up used for the extended partitions? Which > > devices show > > > up in /dev ? > > > > Well, I have never messed with MS extended "partitions" so I don't > > really know much details. My /dev only goes up to s4 for either > > ad or da. > > But, I am not surprised if mount_msdosfs thinks /dev/ad0s10 is not > > valid.I suppose the person could try creating those devices in /dev > > and see > > what falls down (or if it works). > > > > ////jerr > > > > > > > > Hendrik > > > > > > > _______________________________________________ > > freebsd-questions@freebsd.org mailing list > > http://lists.freebsd.org/mailman/listinfo/freebsd-questions > > To unsubscribe, send any mail to "freebsd-questions- > > unsubscribe@freebsd.org" > >
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?200405132025.i4DKPYc27703>