Date: Thu, 13 May 2010 20:25:40 -0700 From: Jeremy Chadwick <freebsd@jdc.parodius.com> To: Fred Souza <fred@storming.org> Cc: freebsd-stable@freebsd.org Subject: Re: Mount root error / New device numbering? Message-ID: <20100514032540.GA85214@icarus.home.lan> In-Reply-To: <AANLkTikL9DLuPRV5JJ11TqdhOgO3QvkkvNDbjWxIdPW6@mail.gmail.com> References: <AANLkTimjQcgKXGqnEZT8jIu97zn61yh7avtgRAEQcuma@mail.gmail.com> <20100514030630.GA84755@icarus.home.lan> <AANLkTikL9DLuPRV5JJ11TqdhOgO3QvkkvNDbjWxIdPW6@mail.gmail.com>
next in thread | previous in thread | raw e-mail | index | archive | help
On Fri, May 14, 2010 at 12:16:47AM -0300, Fred Souza wrote: > > I'd recommend booting/trying an actual 8.0-STABLE snapshot image from > > here: > > > > ftp://ftp.freebsd.org/pub/FreeBSD/snapshots/201004/ > > > > This will allow you to boot and install 8.0-STABLE on your system. You > > should see devices ad10 and ad16 there as well. It would at least save > > you the pain of installing the kernel, rebooting, and finding you have > > to manually deal with /etc/fstab changes and so on. Give this a shot > > first. > > > > It also might help in debugging the "stray IRQ" problem you see (it > > would be useful to know what's sitting on IRQ 21; it may be an unused > > device in your BIOS which you can disable there, or try to find a > > FreeBSD driver for the device which can attach to the IRQ). > > I will try that, thank you very much. But as future reference.. Should > it work if I just get to that shell prompt, change /etc/fstab to match > those number changes and reboot? I'm asking because that sounded like > the way to go when I first encountered this problem, but I ended > making my system unusable. It is possible that I left anything out > when I tried that, or that I changed something incorrectly.. But the > idea should work, right? Absolutely. I've done it myself many times over the years, including remotely over serial console. However, you said you did that then typed "exit" rather than "reboot", and the end result was a kernel panic. Honestly, I'm not surprised; the system was probably still confused about the root device. I'm guessing some kernel innards (or maybe something picked up from boot2/loader) still referenced the "unknown root device" and caused the panic. > I do an exit on that shell just to get to a kernel panic message and a > quick reboot. I tried to unload the -STABLE kernel and boot from the > -RELEASE one, but now the system hangs right after it tries to find my > disks. Even on other operating systems, if I'm dropped (unintentionally or intentionally/by choice) into single-user mode, I reboot the system rather than exit out of single-user and hope that multi-user works from that point forward. I've seen "exit" on Solaris fail and cause all sorts of mayhem (all sorts of system startup services (not rc/init!) failing, machine ending up in some sort of catatonic state). -- | Jeremy Chadwick jdc@parodius.com | | Parodius Networking http://www.parodius.com/ | | UNIX Systems Administrator Mountain View, CA, USA | | Making life hard for others since 1977. PGP: 4BD6C0CB |
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20100514032540.GA85214>