Re: Old indy2 rendered unbootable... (long post)

From: gprs (dbishop_at_ehvert.com)
Date: 01/30/04 

Date: 30 Jan 2004 05:40:54 -0800

Brent sent me a message directly suggesting a resetenv. He also
provided some env settings.

AutoLoad=Y
OSLoadFilename=/unix
OSLoadOptions=auto
OSLoadPartition=scsi(0)disk(1)rdisk(0)partition(0)
OSLoader=sash
SystemPartition=scsi(0)disk(1)rdisk(0)partition(8)
diagmode=v

i have put these in, they didn't exist and the resetenv just didn't do
anything, so that my env looks lik this:

AutoLoad=Y
OSLoadFilename=/unix
OSLoadOptions=auto
OSLoadPartition=scsi(0)disk(1)rdisk(0)partition(0)
OSLoader=sash
SystemPartition=scsi(0)disk(1)rdisk(0)partition(8)
diagmode=v
TimeZone=PST8PDT
Console=g
Diagmode=v
Diskless=0
Dbaud=9600
Volume=80
Sgilogo=y
Autopower=y
Netaddr=192.0.2.1
Eaddr=03:00:69:07:bb:6c
ConsoleOut=video()
ConsoleIn=keyboard()
Cpufreq=150
Gfx=alive

Still no dice. Is anything missing?

when i try to issue a:
boot dksc(0,1,8)sash

i get:

dsk0d1s8: volume header not valid
No volume header on device: scsi(0)disk(1)rdisk(0)partition(8)/sash.

am i still looking at a disk label problem?

thanks tons,
dean