From owner-freebsd-alpha@FreeBSD.ORG Thu Aug 26 10:48:46 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 2659816A4CE for ; Thu, 26 Aug 2004 10:48:46 +0000 (GMT) Received: from tigra.ip.net.ua (tigra.ip.net.ua [82.193.96.10]) by mx1.FreeBSD.org (Postfix) with ESMTP id EC8AE43D62 for ; Thu, 26 Aug 2004 10:48:43 +0000 (GMT) (envelope-from ru@ip.net.ua) Received: from heffalump.ip.net.ua (heffalump.ip.net.ua [82.193.96.213]) by tigra.ip.net.ua (8.12.11/8.12.11) with ESMTP id i7QAmdKE020891 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO) for ; Thu, 26 Aug 2004 13:48:40 +0300 (EEST) (envelope-from ru@ip.net.ua) Received: (from ru@localhost) by heffalump.ip.net.ua (8.13.1/8.13.1) id i7QAmibS089014 for freebsd-alpha@freebsd.org; Thu, 26 Aug 2004 13:48:44 +0300 (EEST) (envelope-from ru) Date: Thu, 26 Aug 2004 13:48:43 +0300 From: Ruslan Ermilov To: freebsd-alpha@freebsd.org Message-ID: <20040826104843.GB79903@ip.net.ua> References: <20040826090653.GC52970@loge.nixsys.be> Mime-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-sha1; protocol="application/pgp-signature"; boundary="qlTNgmc+xy1dBmNv" Content-Disposition: inline In-Reply-To: <20040826090653.GC52970@loge.nixsys.be> User-Agent: Mutt/1.5.6i X-Virus-Scanned: by amavisd-new Subject: Re: 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 10:48:46 -0000 --qlTNgmc+xy1dBmNv Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Content-Transfer-Encoding: quoted-printable On Thu, Aug 26, 2004 at 11:06:53AM +0200, Philip Paeps wrote: > 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. >=20 It was broken for quite a long time actually. ;) > I'm wondering about how I would best go about getting it working > again. >=20 > This is how it dies: >=20 > (boot dka100.1.0.9.0 -flags A) > [...] > jumping to bootstrap code > Loading /boot/loader > \ > halted CPU 0 > =20 > halt code =3D 2 > kernel stack not valid halt > PC =3D 0 =20 > boot failure > >>> >=20 > 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 di= sk > it's been booted from, not about other disks in the machine: >=20 > 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 >=20 > Any hints? I'd prefer not to have to go through a clean install. I have > backups, but they're tedious :-) >=20 > Thanks! >=20 Is your /boot/loader.old also broken? If not, it's possible to use it, by pressing a spare while in boot1 boot block, and typing its name: "/boot/loader.old". Cheers, --=20 Ruslan Ermilov ru@FreeBSD.org FreeBSD committer --qlTNgmc+xy1dBmNv Content-Type: application/pgp-signature Content-Disposition: inline -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.2.5 (FreeBSD) iD8DBQFBLcALqRfpzJluFF4RAoG1AJwMXPa3F4+PRtbAD5H9yRu1mrfPOACggGyh bQ0A2rguPwz0pc8MmSgkfOk= =x0ey -----END PGP SIGNATURE----- --qlTNgmc+xy1dBmNv--