Date: Sat, 20 Nov 2010 01:20:07 +0100 From: Ivan Voras <ivoras@freebsd.org> To: "James R. Van Artsdalen" <james-freebsd-current@jrv.org> Cc: freebsd-current@freebsd.org Subject: Re: A big-ish machine, cannot boot Message-ID: <AANLkTim9jKQHjrsZrnoXDkQidSmQjYDAWLqxMueSf8-9@mail.gmail.com> In-Reply-To: <4CE6B147.4060203@jrv.org> References: <ic65q8$a76$1@dough.gmane.org> <4CE6B147.4060203@jrv.org>
next in thread | previous in thread | raw e-mail | index | archive | help
On 19 November 2010 18:17, James R. Van Artsdalen <james-freebsd-current@jrv.org> wrote: > Ivan Voras wrote: >> Unfortunately, the kernel hangs on boot. The loader finishes, the twirly >> starts spinning but then hangs. Enabling verbose booting results in >> nothing new - no kernel messages at all. > > I don't think "loader finishes" is correct. =C2=A0Can you break to the lo= ader > command line at the beastie menu? Yes. Everything in the loader itself works fine, including hardware detecti= on. > At the time of the twirlie I think that the loader is copying the kernel > to memory. =C2=A0Perhaps it is having trouble with disk reads, or has a b= ad > memory map. > > How many disks are attached, and what filesystem type does /boot live > on? =C2=A0And =C2=A0what does Fixit mode see (from whatever installed tha= t system)? There are three RAID volumes visible to the system, and all three are successfully detected and used. root and /boot are completely standard UFS. It is "legacy free" hardware in the sense that it doesn't have PS2 ports, and has the latest generation CPUs with a whole bunch of new technologies.
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?AANLkTim9jKQHjrsZrnoXDkQidSmQjYDAWLqxMueSf8-9>