Date: Tue, 04 Feb 2003 11:51:48 -0600 From: Oscar Ricardo Silva <osilva@scuff.cc.utexas.edu> To: Mike Meyer <mwm@mired.org>, questions@freebsd.org, stable@freebsd.org Subject: Re: filesystem disappeared following 4.2 -> 4.7 upgrade Message-ID: <5.1.0.14.2.20030204114538.02c46678@scuff.cc.utexas.edu> In-Reply-To: <15933.53926.966116.341750@guru.mired.org> References: <20030202202043.GA14875@kearneys.ca> <20030202185009.GA14514@kearneys.ca> <20030202185916.GA14615@kearneys.ca> <20030202191806.GA14696@kearneys.ca> <15933.30462.77008.33453@guru.mired.org> <20030202202043.GA14875@kearneys.ca>
next in thread | previous in thread | raw e-mail | index | archive | help
At 08:23 PM 2/2/2003 -0600, Mike Meyer, you wrote: >In <20030202202043.GA14875@kearneys.ca>, Brent Kearney <brent@kearneys.ca> >typed: > > What if this system were an all-IDE system? I was planning to update > > one soon, and will no doubt run into this problem. The root > > filesystem device node will change names, and according to this > > thread: > > > http://www.freebsd.org/cgi/getmsg.cgi?fetch=2388792+2394647+/usr/local/www/db/text/2003/freebsd-questions/20030112.freebsd-questions > >No, devices *may* change names. They don't have to. The article you >quoted changed names drastically because he wasn't using the onboard >IDE controller, but had all his drives on the Promise card (would you >verify that for me, Oscar)? One solution to the question asked in that >message is to disable the IDE on the motherboard so that the Promise >controller becomes ata0, and the first drive on it becomes ad0. That >also frees up a couple of IRQs, and may be worth doing in any >case. It's probably better to try changing /boot/loader.conf to set >root_disk_unit to solve the problem, though. Welllll ... yes and no. I wasn't putting the drive on the first and second IDE controllers. The motherboard had two additional IDE controllers, Promise ATA66, on it. On some BIOS, you can direct the machine to look at slot devices before onboard devices, that might help your situation. Not that it's any kind of solution, but in the end, while attempting to do another install on the system, I accepted the default sizes for the filesystems and it worked. Creating a / filesystem of 128MB ... and from there it booted fine. Oscar To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?5.1.0.14.2.20030204114538.02c46678>