Re: Can't mount ad0s2 - sourced
On Mon, 16 Jun 2003 22:42, Brian Astill wrote: > On Mon, 16 Jun 2003 08:42 pm, Malcolm Kay wrote: > > > > > > Sure there is [a solution]. Show us what fdisk and disklabel > > > > > > say. > > > > > > referring to my being unable to access ad0s2 from FBSD. > > > The drive is partitioned DOS-DOS-FBSD. > > > If I set up the partitions Primary1-Primary2-Primary3, WinNT > > > "hides" Primary2, and I have to "unhide" using Partition Magic > > > every time I boot into that hateful OS. However, I CAN acess > > > Primary2 from FBSD. > > > However, If I set up the partitions > > > Primary1-Logical1-Primary2, WinNT is happy, but Logical1 cannot be > > > mounted by FBSD. > > > > Never had occassion to use this but:- > > It's my understanding that so called logical partitions/slices are > > available to FreeBSD as slice 5, 6 ... > > Thus you should be able to mount the elusive partition as ad0s5. > > Agreed. Sorry, been there, done that. Doesn't work if I use > Primary/Logical/Primary. /dev/ad0s5 exists. > > #mount -t msdos /dev/ad0s2 /mnt/edrive > doesn't work, either, if I use Primary/Logical/Primary. /dev/ad0s2 > does exist. > > I wonder what would happen if I tried to mount ad0s2a? > Neither ad0s2a not ad0s2e succeed :-( > Keeps saying "invalid argument" - /dev/ad0s2a and e both exist, so does > /mnt/edrive. > So I'm stuck. I must say I find this surprising; I wonder whether Partition Magic has done something to the boot record of the extended partition, especially the partition table. What does: # fdisk /dev/ad0s2 report? Malcolm ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: Can't mount ad0s2 - sourced
On Mon, 16 Jun 2003 08:42 pm, Malcolm Kay wrote: > > > > > Sure there is [a solution]. Show us what fdisk and disklabel > > > > > say. > > > > referring to my being unable to access ad0s2 from FBSD. > > The drive is partitioned DOS-DOS-FBSD. > > If I set up the partitions Primary1-Primary2-Primary3, WinNT > > "hides" Primary2, and I have to "unhide" using Partition Magic > > every time I boot into that hateful OS. However, I CAN acess > > Primary2 from FBSD. > > However, If I set up the partitions > > Primary1-Logical1-Primary2, WinNT is happy, but Logical1 cannot be > > mounted by FBSD. > > Never had occassion to use this but:- > It's my understanding that so called logical partitions/slices are > available to FreeBSD as slice 5, 6 ... > Thus you should be able to mount the elusive partition as ad0s5. Agreed. Sorry, been there, done that. Doesn't work if I use Primary/Logical/Primary. /dev/ad0s5 exists. #mount -t msdos /dev/ad0s2 /mnt/edrive doesn't work, either, if I use Primary/Logical/Primary. /dev/ad0s2 does exist. I wonder what would happen if I tried to mount ad0s2a? Neither ad0s2a not ad0s2e succeed :-( Keeps saying "invalid argument" - /dev/ad0s2a and e both exist, so does /mnt/edrive. So I'm stuck. -- Regards, Brian ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: Can't mount ad0s2 - sourced
On Mon, 16 Jun 2003 10:58, Brian Astill wrote: > On Mon, 19 May 2003 02:52 pm, Andy Farkas wrote: > > > > Sure there is [a solution]. Show us what fdisk and disklabel say. > > referring to my being unable to access ad0s2 from FBSD. > The drive is partitioned DOS-DOS-FBSD. > > If I set up the partitions Primary1-Primary2-Primary3, WinNT "hides" > Primary2, and I have to "unhide" using Partition Magic every time I > boot into that hateful OS. However, I CAN acess Primary2 from FBSD. > If I set up the partitions Primary1-Logical1-Primary2, WinNT is happy, > but Logical1 cannot be mounted by FBSD. > Never had occassion to use this but:- It's my understanding that so called logical partitions/slices are available to FreeBSD as slice 5, 6 ... Thus you should be able to mount the elusive partition as ad0s5. Of course you'll probably need to first make the device:- #cd /dev #./MAKEDEV ad0s5 > herewith details of the latter case: > As you can see, fdisk can see the extended partition, but not the > logical partition inside it. (tho' windoze is happy) > > #fdisk /dev/ad0 > *** Working on device /dev/ad0 *** > parameters extracted from in-core disklabel are: > cylinders=1027 heads=255 sectors/track=63 (16065 blks/cyl) > > Figures below won't work with BIOS for partitions not in cyl 1 > parameters to be used for BIOS calculations are: > cylinders=1027 heads=255 sectors/track=63 (16065 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 6,(Primary 'big' DOS (> 32MB)) > start 63, size 2056257 (1004 Meg), flag 80 (active) > beg: cyl 0/ head 1/ sector 1; > end: cyl 127/ head 254/ sector 63 > The data for partition 2 is: > sysid 5,(Extended DOS) > start 2056320, size 2088450 (1019 Meg), flag 0 > beg: cyl 128/ head 0/ sector 1; > end: cyl 257/ head 254/ sector 63 > The data for partition 3 is: > sysid 165,(FreeBSD/NetBSD/386BSD) > start 4144770, size 12353985 (6032 Meg), flag 0 > beg: cyl 258/ head 0/ sector 1; > end: cyl 1023/ head 254/ sector 63 > The data for partition 4 is: > > Since logical slices are rather like primary slices but referenced from a primary slice or another logical slice, rather than the MBR, they can usually be "viewed" by pointing fdisk at a slice instead of the entire disk: #fdisk /dev/ad0s2 Malcolm ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: Can't mount ad0s2 - sourced
On Mon, 19 May 2003 02:52 pm, Andy Farkas wrote: > > > Sure there is. Show us what fdisk and disklabel say. referring to my being unable to access ad0s2 from FBSD. herewith: As you can see, fdisk can see the extended partition, but not the logical partition inside it. (tho' windoze is happy) #fdisk /dev/ad0 *** Working on device /dev/ad0 *** parameters extracted from in-core disklabel are: cylinders=1027 heads=255 sectors/track=63 (16065 blks/cyl) Figures below won't work with BIOS for partitions not in cyl 1 parameters to be used for BIOS calculations are: cylinders=1027 heads=255 sectors/track=63 (16065 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 6,(Primary 'big' DOS (> 32MB)) start 63, size 2056257 (1004 Meg), flag 80 (active) beg: cyl 0/ head 1/ sector 1; end: cyl 127/ head 254/ sector 63 The data for partition 2 is: sysid 5,(Extended DOS) start 2056320, size 2088450 (1019 Meg), flag 0 beg: cyl 128/ head 0/ sector 1; end: cyl 257/ head 254/ sector 63 The data for partition 3 is: sysid 165,(FreeBSD/NetBSD/386BSD) start 4144770, size 12353985 (6032 Meg), flag 0 beg: cyl 258/ head 0/ sector 1; end: cyl 1023/ head 254/ sector 63 The data for partition 4 is: #disklabel /dev/ad0 # /dev/ad0: type: unknown disk: amnesiac label: fictitious flags: bytes/sector: 512 sectors/track: 63 tracks/cylinder: 255 sectors/cylinder: 16065 cylinders: 1027 sectors/unit: 16514064 rpm: 3600 interleave: 1 trackskew: 0 cylinderskew: 0 headswitch: 0 # milliseconds track-to-track seek: 0 # milliseconds drivedata: 0 8 partitions: #size offsetfstype [fsize bsize bps/cpg] c: 165140640unused0 0 # (Cyl.0 - 1027*) -- Regards, Brian ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "[EMAIL PROTECTED]"
