Skip site navigation (1)Skip section navigation (2)
Date:      Mon, 16 Jun 2003 23:39:38 +0930
From:      Malcolm Kay <malcolm.kay@internode.on.net>
To:        Brian Astill <bastill@adam.com.au>, Andy Farkas <andyf@speednet.com.au>
Cc:        freebsd-questions@freebsd.org
Subject:   Re: Can't mount ad0s2 - sourced
Message-ID:  <200306162339.38981.malcolm.kay@internode.on.net>
In-Reply-To: <200306162242.24585.bastill@adam.com.au>
References:  <20030519151603.J93323-100000@hewey.af.speednet.com.au> <200306162042.44474.malcolm.kay@internode.on.net> <200306162242.24585.bastill@adam.com.au>

next in thread | previous in thread | raw e-mail | index | archive | help
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.
>
> <thinks> I wonder what would happen if I tried to mount ad0s2a?
> <tests> 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



Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?200306162339.38981.malcolm.kay>