Date: Fri, 08 Jun 2001 22:11:03 -0700 From: Kent Stewart <kstewart@urx.com> To: Doug Poland <doug@polands.org> Cc: freebsd-questions@freebsd.org Subject: Re: HELP! Cannot boot after changing from ATA66 to ATA100 Message-ID: <3B21AFE7.43FB8EAB@urx.com> References: <20010608232534.A3382@polands.org>
next in thread | previous in thread | raw e-mail | index | archive | help
Doug Poland wrote: > > The good news: I discovered my IBM DTLA drive was connected > to my VIA ATA66 controller and was able to move it to my Promise > ATA100 controller socket. > > The bad news: I cannot boot! The device names of my harddrive > have changed. This is what it looked like before: (4.3-STABLE) Move it back and build a kernel with "ATA_STATIC_ID" commented out. Changed your fstab to sequential devices, make the other devices just in case. Reboot and see if you have it right. If you do, then, move your cable back to the ATA-100 controller and try it. Your drives should start with ata1, ata2, and etc. Kent > > dmesg | grep -i ata > atapci0: <VIA 82C686 ATA66 controller> port 0xd800-0xd80f at device 4.1 on pci0 > ata0: at 0x1f0 irq 14 on atapci0 > ata1: at 0x170 irq 15 on atapci0 > atapci1: <Promise ATA100 controller> port 0x8000-0x803f,0x8400-0x8403,0x8800-0x8807,0x9000-0x9003,0x9400-0x9407 mem +0xce800000-0xce81ffff irq 10 at device 17.0 on pci0 > ad0: 43979MB <IBM-DTLA-307045> [89355/16/63] at ata0-master UDMA66 > acd0: CD-RW <RICOH DVD/CDRW MP9060> at ata1-master using PIO4 > > Now that I've moved the HD cable to the ATA100 socket, this is what I see: > > atapci0: <VIA 82C686 ATA66 controller> port 0xd800-0xd80f at device 4.1 on pci0 > ata1: at 0x170 irq 15 on atapci0 > ata2: at 0x9600 on atapci1 > atapci1: <Promise ATA100 controller> port 0x8000-0x803f,0x8400-0x8403,0x8800-0x8807,0x9000-0x9003,0x9400-0x9407 mem +0xce800000-0xce81ffff irq 10 at device 17.0 on pci0 > ad4: 43979MB <IBM-DTLA-307045> [89355/16/63] at ata1-master UDMA100 > acd0: CD-RW <RICOH DVD/CDRW MP9060> at ata1-master using PIO4 > > I've managed to mount /dev/ad4s3a as a read-only filesystem. I was hoping > to change fstab entries from ad0/ad4 but I have no ad4* devices in /dev. > And, I cannot mount / read-write. > > So how can I fix this? I've tried using the live filesystem CD in fixit mode. > I can mount /dev/ad4s3 (my / partition of old) rw but cannot do a ./MAKEDEV > ad4. It returns error messages (I can get them if necessary). > > Thanks for the help. It sucks having to boot into windows to type this > email :( > > -- > > Regards, > Doug > > To Unsubscribe: send mail to majordomo@FreeBSD.org > with "unsubscribe freebsd-questions" in the body of the message -- Kent Stewart Richland, WA mailto:kbstew99@hotmail.com http://kstewart.urx.com/kstewart/index.html FreeBSD News http://daily.daemonnews.org/ 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?3B21AFE7.43FB8EAB>