Recovering from b0rked loader?

[Ruslan Ermilov]

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.
> 
It was broken for quite a long time actually.  ;)

> 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 at 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!
> 
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,
-- 
Ruslan Ermilov
ru at FreeBSD.org
FreeBSD committer
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: application/pgp-signature
Size: 187 bytes
Desc: not available
Url : http://lists.freebsd.org/pipermail/freebsd-alpha/attachments/20040826/5dcb0673/attachment.bin