Re: Upgrade 5.0.6 to 5.0.7 - Failed
From: Bela Lubkin (belal_at_sco.com)
Date: 05/16/03
- Next message: Bela Lubkin: "Re: LOGIN: ERROR-Failed to initialize policy manager"
- Previous message: Bill Vermillion: "Re: Re; Cannot erase files"
- Maybe in reply to: Steve Burger: "Upgrade 5.0.6 to 5.0.7 - Failed"
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ] [ attachment ]
Date: Fri, 16 May 2003 07:32:59 GMT To: scomsc@xenitec.ca
Stevalyn wrote:
> Bela Lubkin wrote:
> >[reposting article that didn't make it through the mail->news gateway]
[I'm still having a lot of trouble with gateways. I'll try posting this
one through Ed's gateway instead of JP's. (Most oddly, I posted 11
articles containing the exact string "reposting article that didn't make
it through the mail->news gateway"; google has apparently received
_none_ of them, even though several of the messages have been replied
to, and the replies are in google, so searching on that string gets
several matches now.)]
> >Steve Burger wrote:
> >>I just did an upgrade on 5.0.6 to 5.0.7.
> >>I now get
> >>
> >>"not a directory
> >>
> >>boot not found
> >>Cannot open
> >>Stage 1 boot failure: error loading hd(40)/boot
> >>
> >>I can boot off floppy and root from the hard drive."
> Sorry for the delay in answering. The machine in question is my mail
> server and with it down I was kind of isolated.
>
> The problem seems to have been as a result of the "DOS Translation"
> option on the Adaptec controller being disabled. 5.0.7 would not boot
> even after a clean installation with this option disabled. Unfortunately
> enabling it then effectively changed the drive geometry on the old drive
> and made it unreadable.
>
> My solution was to do a fresh install on a new hard drive and recover
> from tape to a temporary location (ie /old) then use chroot /old /bin/sh
> to check the configuration of the original setup and re-configure the
> new installation.
>
> I still have the original drive on the shelf for reference.
> I'm not unable to try your suggestions at this time but yes this machine
> could have had a different controller in the past, possibly an Adaptec
> 2940U. I can not be sure if I did a fresh install when I upgraded to the
> 29160.
Ok, then I think I understand well enough. You must have "stamped" the
drive with its geometry in the past when you switched from the 2940 to
29160. This would have worked for 506. I've recently discovered a bug
in 507 that makes it unable to pay attention to the OpenServer "geometry
stamp" in the masterboot sector.
If you're willing to fiddle with the original drive, I believe this
would fix it:
- put it back in as boot drive
- verify it still doesn't boot ("boot not found", etc.) (adjust the
Adaptec BIOS settings if necessary to reproduce the scenario)
- boot from floppies, root from hard drive
- go to single-user mode
- run:
# dparam -w /dev/rhd00
# /etc/_fst -w /dev/rhd00 -
* 2/x
RESPONSE: 0x0:0x2: 0x17a
* 17a/h 10 <<-- using address ^^^ from above
RESPONSE: 0x0:0x17a: 0x0 = 0x10
* $q
# dparam /dev/rhd00 `dparam /dev/rhd00`
- now reboot from hard disk
OSR5's masterboot has a pointer at address 2, pointing to the beginning
of the disk parameter table. The first byte of the parameter table must
be 0x10, but isn't in OSR507. This causes the table to be ignored.
Here we're patching that byte back to the correct value; then stamping
the disk with its parameters.
If you can spare the time & downtime, I'd appreciate if you could try
this and tell me if it fixes the boot problem.
>Bela<
- Next message: Bela Lubkin: "Re: LOGIN: ERROR-Failed to initialize policy manager"
- Previous message: Bill Vermillion: "Re: Re; Cannot erase files"
- Maybe in reply to: Steve Burger: "Upgrade 5.0.6 to 5.0.7 - Failed"
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ] [ attachment ]
Relevant Pages
|
