Date: Sun, 13 Jul 2003 08:10:44 -0500 From: "bill mcmilleon" <mcmilwj@hotmail.com> To: freebsd-questions@freebsd.org Subject: 4.5 to 4.8, disks not mounting now Message-ID: <BAY7-F53SxvjPkQTGpa00008a42@hotmail.com>
next in thread | raw e-mail | index | archive | help
I have a Pentium 233 that was running 4.5-RELEASE whose boot drive went belly up last week. Fortunately, I have a "atapci1: <Promise TX2 ATA133 controller>" which provides access to my primary data drives, so merely replacing the failed boot drive that lived on the onboard ide controller would not result in a loss of critical data. Unfortunately, it appears that the fresh install of 4.8-RELEASE on a new, replacement boot drive is unable to mount the "old" drives on the Promise controller. Dmesg output still conveys that the controller and drive names (ad4, ad5, ad7) are found, but disklabel reports "disklabel: bad pack magic number (label is damaged, or pack is unlabeled)" and attempts to mount fail. Please see below. I am inexperienced at migrations like this, and fear the loss of this large amount of critical data. See details below. Any help is appreciated. Thx. --Bill McMilleon Selected dmesg output: atapci0: <Intel PIIX3 ATA controller> port 0xf000-0xf00f at device 7.1 on pci0 ata0: at 0x1f0 irq 14 on atapci0 ata1: at 0x170 irq 15 on atapci0 pci0: <Intel 82371SB (PIIX3) USB controller> at 7.2 irq 10 atapci1: <Promise TX2 ATA133 controller> port 0x7400-0x740f,0x7000-0x7003,0x6c00 -0x6c07,0x6800-0x6803,0x6400-0x6407 mem 0xe0020000-0xe0023fff irq 9 at device 13 .0 on pci0 ata2: at 0x6400 on atapci1 ata3: at 0x6c00 on atapci1 . . . ad0: 8809MB <QUANTUM FIREBALLP KA9.1> [17898/16/63] at ata0-master WDMA2 ad4: 117800MB <IC35L120AVVA07-0> [239340/16/63] at ata2-master UDMA100 ad5: 171705MB <WDC WD1800BB-00DAA0> [348861/16/63] at ata2-slave UDMA100 ad7: 156334MB <Maxtor 4G160J8> [317632/16/63] at ata3-slave UDMA133 acd0: DVD-ROM <AOpen Inc. DVD-ROM DVD-1640 PRO 0122> at ata1-master PIO4 Mounting root from ufs:/dev/ad0s1a WARNING: R/W mount of /i120g denied. Filesystem is not clean - run fsck (I know fsck is probably Fstab (failing mounts commented out): /dev/ad0s1b none swap sw 0 0 /dev/ad0s1a / ufs rw 1 1 /dev/ad0s1f /tmp ufs rw 2 2 /dev/ad0s1g /usr ufs rw 2 2 /dev/ad0s1e /var ufs rw 2 2 /dev/acd0c /cdrom cd9660 ro,noauto 0 0 #/dev/ad4s1e /disks/stash ufs rw 2 2 #/dev/ad5s1e /disks/main ufs rw 2 2 #/dev/ad7s1e /disks/media ufs rw 2 2 proc /proc procfs rw 0 0 Typical fdisk output (ad5 and ad7 are similar): fs3# fdisk -s ad4 /dev/ad4: 15017 cyl 255 hd 63 sec Part Start Size Type Flags 1: 63 241248042 0xa5 0x80 Typical disklabel output (again, ad5 and ad7 similar): fs3# disklabel ad4 # /dev/ad4: type: unknown disk: amnesiac label: fictitious flags: bytes/sector: 512 sectors/track: 63 tracks/cylinder: 255 sectors/cylinder: 16065 cylinders: 15017 sectors/unit: 241254720 rpm: 3600 interleave: 1 trackskew: 0 cylinderskew: 0 headswitch: 0 # milliseconds track-to-track seek: 0 # milliseconds drivedata: 0 8 partitions: # size offset fstype [fsize bsize bps/cpg] c: 241254720 0 unused 0 0 # (Cyl. 0 - 15017*) _________________________________________________________________ STOP MORE SPAM with the new MSN 8 and get 2 months FREE* http://join.msn.com/?page=features/junkmail
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?BAY7-F53SxvjPkQTGpa00008a42>