Date: Mon, 13 Nov 2006 14:14:48 +0100 (CET) From: Ivan Voras <ivoras@geri.cc.fer.hr> To: Pete French <petefrench@ticketswitch.com> Cc: freebsd-stable@freebsd.org Subject: Re: Cruel and unusual problems with Proliant ML350 Message-ID: <20061113141033.Y9445@geri.cc.fer.hr> In-Reply-To: <E1GjZoe-0003Kl-OX@dilbert.firstcallgroup.co.uk> References: <E1GjZoe-0003Kl-OX@dilbert.firstcallgroup.co.uk>
next in thread | previous in thread | raw e-mail | index | archive | help
On Mon, 13 Nov 2006, Pete French wrote: >> There's something unusual going on and I don't know what else to try. >> Finally, after fiddling with various options, I've sort-of got it to >> work by creating two slices (s1, s2), setting root partition on s1a and >> the rest (/usr, /var, etc.) on s2. Now, the "F1 prompt" boot stage >> behaves like this: > > [snip] > > This sounds similar to a Compaq machine I used to have with a SMART RAID > in it. I had 3 drives - a SCSI, and two on the RAID. It would beep > at F1 as well. I had to press F5 3 times to cycle through all the drives, > but then when I got back to the original I could press F1 and it would now > boot fine. > > I never solved it, aand eventually changed machine (though not the > hardware). At the time it did not matter so much as the machine was > a server so when booted would just run until it manually needed to be > restarted. Hmm, it looks like it's a bug in boot0. I've replaced it with ports/sysutils/extipl and the machine boots fine now. Btw. I can confirm extipl works on amd64, so ONLY_FOR_ARCHS line can be updated now. Grub still doesn't. -- Things Mr Welch Cannot Do During An RPG: 135. I cannot demand payment in electrum, backrubs or bubblewrap.
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20061113141033.Y9445>