From owner-freebsd-alpha@FreeBSD.ORG Thu Aug 26 09:06:55 2004 Return-Path: Delivered-To: freebsd-alpha@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 6A7E516A4CF for ; Thu, 26 Aug 2004 09:06:55 +0000 (GMT) Received: from gateway.nixsys.be (gateway.nixsys.be [195.144.77.33]) by mx1.FreeBSD.org (Postfix) with ESMTP id 1561643D49 for ; Thu, 26 Aug 2004 09:06:55 +0000 (GMT) (envelope-from philip@nixsys.be) Received: from loge.nixsys.be (loge.nixsys.be [195.144.77.45]) by gateway.nixsys.be (Postfix) with ESMTP id 3473682 for ; Thu, 26 Aug 2004 11:06:54 +0200 (CEST) Received: from loge.nixsys.be (philip@localhost [127.0.0.1]) by loge.nixsys.be (8.13.1/8.13.1) with ESMTP id i7Q96rth053185 for ; Thu, 26 Aug 2004 11:06:53 +0200 (CEST) (envelope-from philip@loge.nixsys.be) Received: (from philip@localhost) by loge.nixsys.be (8.13.1/8.13.1/Submit) id i7Q96rCg053184 for freebsd-alpha@freebsd.org; Thu, 26 Aug 2004 11:06:53 +0200 (CEST) (envelope-from philip) Date: Thu, 26 Aug 2004 11:06:53 +0200 From: Philip Paeps To: freebsd-alpha@freebsd.org Message-ID: <20040826090653.GC52970@loge.nixsys.be> Mail-Followup-To: freebsd-alpha@freebsd.org Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline X-Date-in-Rome: ante diem VII Kalendas Septembres MMDCCLVII ab Urbe Condida X-PGP-Fingerprint: FA74 3C27 91A6 79D5 F6D3 FC53 BF4B D0E6 049D B879 X-Message-Flag: Get a proper mailclient! User-Agent: Mutt/1.5.6i Subject: Recovering from b0rked loader? X-BeenThere: freebsd-alpha@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Porting FreeBSD to the Alpha List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 26 Aug 2004 09:06:55 -0000 Last week, while I was on holiday, one of my AlphaStations (which builds -current worlds and kernels periodically) managed to build a loader while it was broken. I'm wondering about how I would best go about getting it working again. This is how it dies: (boot dka100.1.0.9.0 -flags A) [...] jumping to bootstrap code Loading /boot/loader \ halted CPU 0 halt code = 2 kernel stack not valid halt PC = 0 boot failure >>> I thought about booting with a bootonly cdrom, but it appears the loader on the 5.3-BETA1 image (I haven't tested any others) only knows about the disk it's been booted from, not about other disks in the machine: FreeBSD/alpha SRM CD9660 boot, Revision 1.2 (root@ds10.wbnet, Mon Aug 23 08:53:04 UTC 2004) [...] OK lsdev disk devices: disk0: SRM drive SCSI 0 9 0 6 600 0 0 Any hints? I'd prefer not to have to go through a clean install. I have backups, but they're tedious :-) Thanks! - Philip -- Philip Paeps Please don't Cc me, I am philip@freebsd.org subscribed to the list. BOFH Excuse #116: the real ttys became pseudo ttys and vice-versa.