Re: Installing bootblocks on 3.2 snapshot

Hugh Graham wrote:
> On Wed, Oct 23, 2002 at 11:43:46PM -0600, Sean Cavanaugh wrote:
> 
>>Hi all,
>>
>>I am trying to install the (Oct 4) snapshot on my uVAX 3100-80 after 
>>trying out VMS for a while.
>>
>>I installed via netboot from my i386 machine, and everything went well. 
>>The problem is that it will *NOT* boot from the disk. I have booted 
>>several times from the network trying to manually install bootblocks 
>>using "disklabel -B sd1", "disklabel -B /dev/rds1c -b sdboot" and some 
>>other such variations, but the system refuses to boot. The output from 
>>the console mode is
>
> The method sounds correct..
> 
> Try the (known working) bootblocks from: xxx

Didn't work. I still get the same messages. I'll try installing 3.1, but 
maybe I need to try wiping the first few blocks on the disk. I did 
notice that the BSD part of the disk started at something like block 
1153 on the Fujutsu and 10?? on the RZ57

> Anything special about the drives?

One drive is a plain DEC RZ57, which used to have an OpenVMS 7.2 install 
on it, and the other is a Fujitsu M2494ES, which used to be in a Wintel box.

> It may be worth testing if boot.mop (once loaded over the network) is
> able to load a kernel off the drive. At the console chevron enter
> "boot esa0", and then at the openbsd boot prompt try "boot sd(0)bsd",
> or "boot sd(1,0)bsd". This is a longshot, and I'm not sure if it ever
> worked reliably with scsi, so a negative result won't tell much.

It says:

getdisklabel: no disk label
nfs_open: must mount first.
Boot failed: Invalid argument

> IIRC your system did run OpenBSD at one point. Does the release it
> previously ran still work? The boot code was changed substantially
> between 3.1 and 3.2, although it was tested working fine on systems
> similar to the mv3100m80.

It used to run 3.0 perfectly well, but I thought I'd try VMS (bleck), 
which required removing all the BSD stuff. I can try installing 3.0 or 
3.1 on the machine and see what happens, which is what I'll do next.


-- 
Sean Cavanaugh - Email: seanc at unixgeeks period ca