Date: Tue, 24 May 2011 18:32:25 -0300 From: Eduardo <sathler90@gmail.com> To: freebsd-hackers@freebsd.org Subject: Re: upgrade to version 8 - can not mount root Message-ID: <BANLkTikg3XoWWxQpeiYvnPAP3E3kkD3ZRQ@mail.gmail.com> In-Reply-To: <4DDA5D5A.4060509@FreeBSD.org> References: <BANLkTinOoHKrCL3nDmjm4kFNo=L_xRUutA@mail.gmail.com> <4DDA5D5A.4060509@FreeBSD.org>
next in thread | previous in thread | raw e-mail | index | archive | help
Thanks to all the replies... I did solve this problem by doing a low level format of the disk... I also saw another thread where this bug was reported ... http://www.freebsd.org/cgi/query-pr.cgi?pr=3D130698 I have to find out now, how to indentify this potencial problem on my other servers, so I would know beforehand that a standard upgrade will not work. Cheers. On Mon, May 23, 2011 at 10:12 AM, Andriy Gapon <avg@freebsd.org> wrote: > on 20/05/2011 20:36 Eduardo said the following: >> da0 at ahc0 bus0 scbus0 target 5 lun 0 >> da0 messages ... >> da0 at ahc0 bus0 scbus0 target 6 lun 0 >> da1 messages ... >> Trying to mount root from ufs:/dev/da0s1a >> ROOT MOUNT ERROR: >> If you have invalid mount options, reboot, and first try the following >> from the loader prompt: >> set vfs.root.mountfrom.options=3Drw >> and then remove invalid mount options from /etc/fstab >> Loader variables: >> vfs.root.mountfrom=3Dufs:/dev/da0s1a >> vfs.root.mountfrom.options=3Drw >> >> Manual root filesystem specification: =A0...etc.. >> >> mountroot> <enter> >> >> pani: Root mount failed, startup aborted. >> cpuid=3D0 >> KBD: stack backtrace: >> #0 0xc08ebe67 at kdb_backtrace+0x47 >> #1 0xc08bc627 at panic+0x117 >> #2 0xc0943fc7 at vfs_mountroot+0x4f7 >> #3 0xc08737c0 at start_init+0x60 >> #4 0xc0890f51 at fork_exit+0x91 >> #5 0xc0bd5b84 at fork_trampoline+0x8 >> >> I can boot the old kernel at 7.2 and recompile again with debug flags as= needed. >> >> One thing I did try just now was to install 8.2 from the CD ... after >> I choose install options and he goes to create the filesystems I get >> these error messages: >> >> >> Unable to find device node for /dev/da0s1b in /dev! >> The creation of filesystems will be aborted. > > First, this is not really a question for hackers@. =A0Perhaps stable@, ge= om@ or fs@ > would be better choices. > > To the subject matter, it seems like you could have an MBR that is reject= by code > in in 8. =A0Have you tried to get a lit of devices that kernel sees at th= e mountroot > prompt? =A0What are those? > > It could also be useful to boot from 8 or 9 live disk and examine how the= system > sees your disks. > > -- > Andriy Gapon >
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?BANLkTikg3XoWWxQpeiYvnPAP3E3kkD3ZRQ>