Date: Tue, 15 Aug 2000 03:31:01 -0500 From: Zach Johnson <xopl@execpc.com> To: hornback@wireco.net Cc: questions@freebsd.org Subject: Re: ATA100 bus... can't find root fs Message-ID: <3998FFC4.B7CD451F@execpc.com> References: <008401c00594$98956480$d4776bce@challenger>
next in thread | previous in thread | raw e-mail | index | archive | help
Ok... so I installed FreeBSD 4.1 while connected to the primary ATA66 bus because it couldn't find any harddrives when they were connected to the integrated HightPoint Tech HPT370 ATA100 bus. Then, I moved the harddrive back to the ATA100... It boots. I go to the boot prompt and do an lsdev. I see my floppy and my harddrive listed... disk1s2a is where root is according to the output. I continue the boot. An ATA66 controller from HighPoint Tech is found apparently located where I think the ATA100 is. (same IRQ, etc.. ??) No 'ad' devices are listed on the screen... but some atapci and ata ones are. The boot fails when it tries to talk to the primary and secondary ATA buses (the 66's) and can't find the root file system. I get the mount root> prompt. If I type in say, ufs:/dev/ad1s2a is tells me there is no device 'ad.' It doesn't matter what numbers I put after ad, it is like the device doesn't exist. Why is it at the boot prompt I can view files on my harddrives and see all its divisions, including where the root filesystem is, and then I can't get FreeBSD to read from it afterwards.... While connected to the ATA66 bus, can I make a kernel that will help me and then load that kernel from the boot prompt after reconnecting the drive to the ATA100 bus? Anything else I could try? Do I have to just give up and plug the drive into the ATA66 bus? I appreciate any help, Zach Johnson 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?3998FFC4.B7CD451F>