From owner-freebsd-questions@FreeBSD.ORG Mon Apr 26 11:57:03 2010 Return-Path: Delivered-To: freebsd-questions@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 5D0E0106564A for ; Mon, 26 Apr 2010 11:57:03 +0000 (UTC) (envelope-from neil@cymru.com) Received: from obelisk11.ord01.cymru.com (obelisk11.ord01.cymru.com [38.229.66.8]) by mx1.freebsd.org (Postfix) with ESMTP id 407098FC20 for ; Mon, 26 Apr 2010 11:57:03 +0000 (UTC) Received: from [192.168.251.100] (vpn-72-32.svcs.ord07.cymru.com [172.16.72.32]) by obelisk11.ord01.cymru.com (Postfix) with ESMTP id A6662B00F1 for ; Mon, 26 Apr 2010 11:39:49 +0000 (GMT) Message-Id: <89FD4584-5271-42A2-8E7D-9F40B9CA5E23@cymru.com> From: Neil Long To: freebsd-questions@freebsd.org Content-Type: text/plain; charset=US-ASCII; format=flowed; delsp=yes Content-Transfer-Encoding: 7bit Mime-Version: 1.0 (Apple Message framework v936) Date: Mon, 26 Apr 2010 12:39:47 +0100 X-Mailer: Apple Mail (2.936) Subject: boot0 problem - strange character for default drive? X-BeenThere: freebsd-questions@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: User questions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 26 Apr 2010 11:57:03 -0000 Hi Yesterday I had a problem with a gmirror configuration and one drive started squeaking rather unpleasantly. If I physically remove one of the drives I don't get a normal boot0 screen i.e. F1 for FreeBSD and F5 is Drive 0 - typical for gmirror??) but some strange character after the 'F' - I can't find the ascii number for it but it looks like a capital "I" (more of an I-Beam i.e. distinct flats top and bottom) with a diamond in the centre. Hitting any key just gives a # and left to itself there is a series of '#". I gave up and left it overnight and today I was able to boot the good disk and even deactivate/insert the bad disk which completed. All seemed fine, no errors in dmesg but on reboot - all I get is the above state. I tried the SATA controller on the mobo and a plug-in PCI cheap one (tried two). Makes no difference. It boots fine off an IDE drive. It boots fine using the same SATA controllers for an older non-gmirror drive (then I simply get the F1: FreeBSD option) so I don't think it is the cpu/memory/mobo?? I now have the same boot0 problem with either drive from the gmirror Anyone else seen this and have a fix? I don't want to zap the drives since there is a working system there but just can't get to it :-) Thanks Neil