Date: Wed, 4 Dec 2002 15:06:39 -0800 (PST) From: adsf adsf <mail2@winterland.dhs.org> To: freebsd-questions@FreeBSD.org Subject: need help mounting ext3 partitions from new freebsd 4.7 install Message-ID: <20021204230639.E1A804618@sitemail.everyone.net>
next in thread | raw e-mail | index | archive | help
I recently put an old hard drive in my system to install freebsd 4.7 onto, never having installed a bsd before
my previous setup was this -
/dev/hda 80 gig maxtor on primary on-board ide controller
/dev/hde 120 gig maxtor on promise tx1332 controller card (dont know why it got stuck with hd"e")
redhat 8 boots from /dev/hda. I added an 8 gig drive to the promise controller. linux saw it as /dev/hdf/
I unplugged the power to the 80 and 120 gig drives, which are ext3, and only left the 8 gig (didnt want to accidentaly hose my linux install with fbsd) I installed bsd onto the 8 gig successfully.
now freebsd is identifying this 8 gig drive which is all freebsd as:
/dev/ad5s1 (partitions are /dev/ad5s1a, f, g, and e - which fbsd auto-partitioned)
I plugged my linux drives back in and booted into freebsd (I added freebsd's info into grub.conf since the system boots to the bootloader on the 80 gig redhat 8 drive)
it boots into freebsd, still on /ad5s1. I want to mount my ext3 partitions but I dont know what their device address is
"fdisk" defaults to /dev/ad0 which appears to be the 80 gig attatched to the mobo ide controller, I will try to see if i can mount that, but I cant find the 120 gig on the promise card, I would think it would be at /dev/ad5s0 since it is the 1st drive on the promise card and bsd sees the 2nd drive on the promise card (8 gig freebsd install) as /dev/ad5s1, but "fdisk /dev/ad5s0" gives No such file or directory.
fdisk /dev/ad5s2 gives something -
******* Working on device /dev/ad5s2 *******
parameters extracted from in-core disklabel are:
cylinders=1 heads=1 sectors/track=1 (1 blks/cyl)
parameters to be used for BIOS calculations are:
cylinders=1 heads=1 sectors/track=1 (1 blks/cyl)
fdisk: invalid fdisk partition table found
fdisk: /boot/mbr: length must be a multiple of sector size
so it cant seem to read the ext3 partitions on the 120 gig, but it can see the partitions on the 80 gig /dev/ad0 ok:
******* Working on device /dev/ad0 *******
parameters extracted from in-core disklabel are:
cylinders=9964 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=9964 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 131,(Linux filesystem)
start 63, size 5124672 (2502 Meg), flag 80 (active)
beg: cyl 0/ head 1/ sector 1;
end: cyl 318/ head 254/ sector 63
The data for partition 2 is:
sysid 131,(Linux filesystem)
start 5124735, size 1012095 (494 Meg), flag 0
beg: cyl 319/ head 0/ sector 1;
end: cyl 381/ head 254/ sector 63
The data for partition 3 is:
sysid 130,(Linux swap or Solaris x86)
start 6136830, size 1012095 (494 Meg), flag 0
beg: cyl 382/ head 0/ sector 1;
end: cyl 444/ head 254/ sector 63
The data for partition 4 is:
sysid 15,(Extended DOS, LBA)
start 7148925, size 152922735 (74669 Meg), flag 0
beg: cyl 445/ head 0/ sector 1;
end: cyl 1023/ head 254/ sector 63
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?20021204230639.E1A804618>