Re: Installing bootblocks on 3.2 snapshot
Sean Cavanaugh <[email protected]> Thu, 24 Oct 2002 22:27:06 -0600
| Newsgroups | gmane.os.openbsd.vax |
|---|---|
| Message-ID | <[email protected]> |
Hugh Graham wrote: > On Thu, Oct 24, 2002 at 09:56:20PM -0600, Sean Cavanaugh wrote: > >>>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. > > > Hmm, yes, do try dd'ing over at least the first few cylinders of the > disk (just let it run for a while), then reboot and try an install > with no possibility of in-kernel baggage about a previous label. > >>>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 > > > I can't remember ever going from network to scsi successfully, > although scsi to network or network to mscp do seem to work. > Something to investigate... Yes, Network->scsi definately doesn't work. >>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. >> > > If it's less trouble than downloading then try the dd thing first. I pretty much have 3.2 snap and 3.1 release on my NFS server, so I started the install even before I sent the message. I have a feeling that the install won't fix it, so if it doesn't boot I'll just do the dd thing and try again. I'm just about done the install (for some reason I decided to install X, and I've been having intermittent trouble with my coax segment... It's taking a while =) -- Sean Cavanaugh - Email: seanc at unixgeeks period ca