Re: mount_msdosfs anomaly
ALoha Malcolm I apologize, I should of answered yesterday. - Original Message - From: Malcolm Kay [EMAIL PROTECTED] Date: Friday, May 14, 2004 5:14 pm Subject: Re: mount_msdosfs anomaly On Saturday 15 May 2004 12:04, [EMAIL PROTECTED] wrote: - On Saturday 15 May 2004 08:59, [EMAIL PROTECTED] 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 operator4, 10 May 14 12:54 /dev/ad0 crw-r- 1 root operator4, 11 May 14 12:54 /dev/ad0s1 crw-r- 1 root operator4, 12 May 14 12:54 /dev/ad0s2 crw-r- 1 root operator4, 16 May 14 02:54 /dev/ad0s2a crw-r- 1 root operator4, 17 May 14 12:54 /dev/ad0s2b crw-r- 1 root operator4, 18 May 14 12:54 /dev/ad0s2c crw-r- 1 root operator4, 19 May 14 02:54 /dev/ad0s2d crw-r- 1 root operator4, 20 May 14 02:54 /dev/ad0s2e crw-r- 1 root operator4, 21 May 14 02:54 /dev/ad0s2f crw-r- 1 root operator4, 13 May 14 12:54 /dev/ad0s3 crw-r- 1 root operator4, 14 May 14 12:54 /dev/ad0s4 crw-r- 1 root operator4, 22 May 14 12:54 /dev/ad0s5 crw-r- 1 root operator4, 23 May 14 12:54 /dev/ad0s6 crw-r- 1 root operator4, 24 May 14 12:54 /dev/ad0s7 crw-r- 1 root operator4, 25 May 14 12:54 /dev/ad0s8 crw-r- 1 root operator4, 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
Re: mount_msdosfs anomaly
Malcolm Kay wrote: On Saturday 15 May 2004 12:04, [EMAIL PROTECTED] wrote: 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? Does someone out there know the significance of sysid 12 versus sysid 11? According to the fdisk output sysid 11 is DOS or Windows 95 with 32 bit FAT and sysid 12 is DOS or Windows 95 with 32 bit FAT (LBA) The difference is LBA although I thought that if you needed to use LBA then the _whole disk_ was LBA but since slice 3 is visible in Win98 I guess it's correct (probably just a case of FreeBSD reporting _accurately_ what's on the disk). It's a few years since I messed with FAT so I may not have remembered this correctly, but originally DOS could only support a single _active_ primary partition (which is why extended was invented). Somewhere in the Win9x line that changed; the OS still had to be on the first primary partition but other primary partitions were visible in the OS. The OP says that Win98 can see /dev/ados3 and write to it but, if you look at the fdisk output only slice 1 is flagged 'active'. The last time I had a machine with multiple OSes (Win98, W2K, and FreeBSD) I used BootMagic that comes with PartitionMagic which had a config option to choose which partitions/slices each OS could see. With FreeBSD the default setting hid _all_ the FAT NTFS slices (I got the same problem you have) so I had to change the settings. The first one or two bytes in each entry in the partition table determine whether the partition is 'active' (i.e. the one that is booted from) but also whether the partition is visible or hidden. When you choose an OS from BM's menu it edits the PT on the fly (which will set the BIOS boot sector anit-virus alarm off if it's enabled) and then continues the boot process. IIRC Win9x can see adso3 (in this case) by simply ignoring the visible flag, i.e. a kludge, in typical MS fashion. As to how to resolve it, if you are really brave you can edit the partition table flags directly but the changes may not hold (I have a feeling that Win98 may fix them next time you boot Win98) or install a boot manager like BM that allows you to set the visibility. If you run this # dd if=/dev/ad0 of=/tmp/foo bs=512 count=1 # hd /tmp/foo /tmp/foo.hd and post the last 6 lines of foo.hd it will help identify which byte is set wrong; I've a load of notes here about partition tables so I'll dig them out. HTH Regards, Mark ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: mount_msdosfs anomaly
- Original Message - From: Mark Ovens [EMAIL PROTECTED] Date: Saturday, May 15, 2004 2:18 am Subject: Re: mount_msdosfs anomaly Aloha Mark and thanks for responding. I'm sorry I wasn't able to get back to you sooner. I was in Kawaihae paddling in and outrigger canoe race. Alas, we didn't do very well. But, there's always next week. Malcolm Kay wrote: On Saturday 15 May 2004 12:04, [EMAIL PROTECTED] wrote: 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? Does someone out there know the significance of sysid 12 versus sysid 11? According to the fdisk output sysid 11 is DOS or Windows 95 with 32 bit FAT and sysid 12 is DOS or Windows 95 with 32 bit FAT (LBA) The difference is LBA although I thought that if you needed to use LBA then the _whole disk_ was LBA but since slice 3 is visible in Win98 I guess it's correct (probably just a case of FreeBSD reporting _accurately_ what's on the disk). It's a few years since I messed with FAT so I may not have remembered this correctly, but originally DOS could only support a single _active_ primary partition (which is why extended was invented). Somewhere in the Win9x line that changed; the OS still had to be on the first primary partition but other primary partitions were visible in the OS. The OP says that Win98 can see /dev/ados3 and write to it but, if you look at the fdisk output only slice 1 is flagged 'active'. The last time I had a machine with multiple OSes (Win98, W2K, and FreeBSD) I used BootMagic that comes with PartitionMagic which had a config option to choose which partitions/slices each OS could see. With FreeBSD the default setting hid _all_ the FAT NTFS slices (I got the same problem you have) so I had to change the settings. The first one or two bytes in each entry in the partition table determine whether the partition is 'active' (i.e. the one that is booted from) but also whether the partition is visible or hidden. When you choose an OS from BM's menu it edits the PT on the fly (which will set the BIOS boot sector anit-virus alarm off if it's enabled) and then continues the boot process. IIRC Win9x can see adso3 (in this case) by simply ignoring the visible flag, i.e. a kludge, in typical MS fashion. As to how to resolve it, if you are really brave you can edit the partition table flags directly but the changes may not hold (I have a feeling that Win98 may fix them next time you boot Win98) or install a boot manager like BM that allows you to set the visibility. I'm plenty brave as this is not a mission critical box! :) If you run this # dd if=/dev/ad0 of=/tmp/foo bs=512 count=1 # hd /tmp/foo /tmp/foo.hd and post the last 6 lines of foo.hd it will help identify which byte is set wrong; I've a load of notes here about partition tables so I'll dig them out. Here are the last few lines. I'm glad you know what we are looking at. 0180 cd 13 73 0f 4d 74 09 31 c0 cd 13 61 eb f1 b4 40 |..s.Mt.1...a...@| 0190 e9 46 ff 88 64 1f 8d 64 10 61 c3 c1 c0 04 e8 03 |.F..d..d.a..| 01a0 00 c1 c0 04 24 0f 27 04 f0 14 40 60 bb 07 00 b4 |$.'[EMAIL PROTECTED]| 01b0 0e cd 10 61 c3 00 00 00 b3 12 b0 3d cf c9 00 01 |...a...=| 01c0 01 00 0b fe bf 7d 3f 00 00 00 bf 64 9c 00 80 00 |.}?d
Re: mount_msdosfs anomaly
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. I still have the same error when trying to mount_msdosfs /dev/ad0s3 /shared or mount -t msdos /dev/ad0s3 /shared I know it is seen as a fat32 partition in Win98 because I format it and run scandisk on it and can write to it. So, I don't think the problem was a primary/logical partition problem. I need to swap data between the OS's and this should be the easiest way.:) Robert 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. I have a spare frankenputer if you can get to Kona, I'll loan it to you :) 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. snip 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 snip ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: mount_msdosfs anomaly
- On Saturday 15 May 2004 08:59, [EMAIL PROTECTED] 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? Robert ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: mount_msdosfs anomaly
On Saturday 15 May 2004 12:04, [EMAIL PROTECTED] wrote: - On Saturday 15 May 2004 08:59, [EMAIL PROTECTED] 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? You do have a device /dev/ad0s3 revealed by ls? Can you mount slice3 under slackware? You say MS reports the slice as FAT32, but has it actually been formatted? Can you write to it? Have you tried mounting the Slackware slice under FreeBSD? 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 ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: mount_msdosfs anomaly
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 Any help will be appreciated. Thanks Robert ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
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 ? Hendrik ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
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 ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: mount_msdosfs anomaly
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 operator4, 10 May 13 09:10 /dev/ad0 crw-r- 1 root operator4, 11 May 13 09:10 /dev/ad0s1 crw-r- 1 root operator4, 27 May 13 09:10 /dev/ad0s10 crw-r- 1 root operator4, 12 May 13 09:10 /dev/ad0s2 crw-r- 1 root operator4, 16 May 12 23:10 /dev/ad0s2a crw-r- 1 root operator4, 17 May 13 09:10 /dev/ad0s2b crw-r- 1 root operator4, 18 May 13 09:10 /dev/ad0s2c crw-r- 1 root operator4, 19 May 12 23:10 /dev/ad0s2d crw-r- 1 root operator4, 20 May 12 23:10 /dev/ad0s2e crw-r- 1 root operator4, 21 May 12 23:10 /dev/ad0s2f crw-r- 1 root operator4, 13 May 13 09:10 /dev/ad0s3 crw-r- 1 root operator4, 14 May 13 09:10 /dev/ad0s4 crw-r- 1 root operator4, 22 May 13 09:10 /dev/ad0s5 crw-r- 1 root operator4, 23 May 13 09:10 /dev/ad0s6 crw-r- 1 root operator4, 24 May 13 09:10 /dev/ad0s7 crw-r- 1 root operator4, 25 May 13 09:10 /dev/ad0s8 crw-r- 1 root operator4, 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 [EMAIL PROTECTED] 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 ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions- [EMAIL PROTECTED] ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: mount_msdosfs anomaly
On my system I have several Linux distros installed in the extended partition, and FBSD 5.2 shows slices as high as /dev/ad0s9. I am able to mount all of these with mount_ext2fs. Whether or not it is possible to mount msdos extended partitions, I can't say, since I don't have any installed on my hard drive. regards, RS On Thu, 13 May 2004 09:39:23 -0400 (EDT) Jerry McAllister [EMAIL PROTECTED] 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 Any help will be appreciated. Thanks Robert ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED] ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
mount_msdosfs anomaly
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. Any help will be appreciated. Thanks Robert ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
