Date: Thu, 17 Oct 2002 16:00:28 -0700 From: Nick Jennings <nkj@namodn.com> To: freebsd-questions@freebsd.org Subject: problems mounting extended partitions and fdisk. Message-ID: <20021017160028.C10984@namodn.com>
next in thread | raw e-mail | index | archive | help
Hi All,
I am trying to access a logical partition on a second disk in this machine.
It is a Linux partition (ext3). I am having trouble because, first of
all the device does not seems to exist, second of all, I cannot even
get into an interactive fdisk to see if it's there at all. I have been
able to access this partition from other linux installs on this machine.
I am not sure if this is normal behavior or not, but whenever I try to
use 'fdisk' it just prints out some partition information, and does
not put me into an interactive mode, where I can view things in
detail, and perhaps change things.
su-2.05b# fdisk /dev/ad1
******* Working on device /dev/ad1 *******
parameters extracted from in-core disklabel are:
cylinders=2586 heads=240 sectors/track=63 (15120 blks/cyl)
Figures below won't work with BIOS for partitions not in cyl 1
parameters to be used for BIOS calculations are:
cylinders=2586 heads=240 sectors/track=63 (15120 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 131,(Linux filesystem)
start 63, size 151137 (73 Meg), flag 80 (active)
beg: cyl 0/ head 1/ sector 1;
end: cyl 9/ head 239/ sector 63
The data for partition 2 is:
sysid 130,(Linux swap or Solaris x86)
start 151200, size 680400 (332 Meg), flag 0
beg: cyl 10/ head 0/ sector 1;
end: cyl 54/ head 239/ sector 63
The data for partition 3 is:
sysid 131,(Linux filesystem)
start 831600, size 483840 (236 Meg), flag 0
beg: cyl 55/ head 0/ sector 1;
end: cyl 86/ head 239/ sector 63
The data for partition 4 is:
sysid 5,(Extended DOS)
start 1315440, size 37784880 (18449 Meg), flag 0
beg: cyl 87/ head 0/ sector 1;
end: cyl 1023/ head 239/ sector 63
su-2.05b#
The reason I wanted to view this disk with fdisk is because for some
reason I am unable to mount one of the extended partitions on this
disk (I think it's ext3 if that matters, which I don't think it does).
The device /dev/ad1s4 is an extended partition (as you can see above),
that contains more logical partitions. The problem is I can mount
/dev/ad1s5,6,7 but not 8, (which is the one I need to mount) the final
logical partition on that disk.
The partition setup on that disk is like this (forgive me for using
linux device names, but thats the way I can view the partition table
currently).
hdb1 /
hdb2 <swap>
hdb3 /tmp
hdb4 <extended>
hdb5 /var
hdb6 /usr
hdb7 /usr/local
hdb8 /home
In FreeBSD, I try to mount it (first the /usr/local partition <hda7>,
then /home <hda8>).
su-2.05b# mount_ext2fs /dev/ad1s7 /mnt/debian/
su-2.05b# umount /mnt/debian/
su-2.05b# mount_ext2fs /dev/ad1s8 /mnt/debian/
mount_ext2fs: /dev/ad1s8: No such file or directory
su-2.05b# ls /dev/ad1*
/dev/ad1 /dev/ad1e /dev/ad1s1a /dev/ad1s1f /dev/ad1s4
/dev/ad1a /dev/ad1f /dev/ad1s1b /dev/ad1s1g /dev/ad1s5
/dev/ad1b /dev/ad1g /dev/ad1s1c /dev/ad1s1h /dev/ad1s6
/dev/ad1c /dev/ad1h /dev/ad1s1d /dev/ad1s2 /dev/ad1s7
/dev/ad1d /dev/ad1s1 /dev/ad1s1e /dev/ad1s3
su-2.05b#
I have been able to access this partition just fine under any of the
other Linux installs I have on this machine (3 Linux distro's, 1 FreeBSD,
1 Win98), so I know the partition table is not corrupt.
Any Ideas?
--
Nick Jennings
nkj@namodn.com
To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-questions" in the body of the message
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20021017160028.C10984>