Bug 74993
Summary: | can't boot win2k after upgrade to 8.0 | ||||||
---|---|---|---|---|---|---|---|
Product: | [Retired] Red Hat Linux | Reporter: | John Killian O'Brien <jkobrien> | ||||
Component: | anaconda | Assignee: | Jeremy Katz <katzj> | ||||
Status: | CLOSED WORKSFORME | QA Contact: | Brock Organ <borgan> | ||||
Severity: | medium | Docs Contact: | |||||
Priority: | high | ||||||
Version: | 8.0 | ||||||
Target Milestone: | --- | ||||||
Target Release: | --- | ||||||
Hardware: | i686 | ||||||
OS: | Linux | ||||||
Whiteboard: | |||||||
Fixed In Version: | Doc Type: | Bug Fix | |||||
Doc Text: | Story Points: | --- | |||||
Clone Of: | Environment: | ||||||
Last Closed: | 2002-10-30 16:08:33 UTC | Type: | --- | ||||
Regression: | --- | Mount Type: | --- | ||||
Documentation: | --- | CRM: | |||||
Verified Versions: | Category: | --- | |||||
oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | |||||
Cloudforms Team: | --- | Target Upstream Version: | |||||
Embargoed: | |||||||
Attachments: |
|
Description
John Killian O'Brien
2002-10-03 14:33:39 UTC
Created attachment 78364 [details]
lilo.conf
When the person answered "yes" to increasing swap space, the install procedure increased the swap space into and wrote over the dos partition; hence, the dos partiton is trashed. You will have to recreate and format the dos partition as well as reload the windows software. Can you attach /etc/lilo.conf.rpmsave? The upgrade didn't create /etc/lilo.conf.rpmsave I did a 'find . -name "*.rpmsave"' and only came up with four files, two of which predate the upgrade. I too suspected that what japeter suggested above might be the case, but don't konw how to check that. We default to putting additional swap space in Linux partitions as a swap file, so I highly doubt that japeter is correct there. Did you manually add the map-drive information to the lilo.conf yourself? Generally, all you need for lilo is other=/dev/hdb label=win2000 Ok, good. It makes sense that anaconda wouldn't invade other partitions for swap space. I can rule that out then. I got one thing backward in my original post. /etc/lilo.conf already has other=/dev/hdb and this gives the "Invalid system disk" error. Changing the line to hdb1 gives the "Loading win2000" freeze. Yes, I created the lilo.conf entry for Win2000 when we installed the new disk but didn't make any changes when I upgraded. I just now tried commenting out the lines after the two you quote but it had no effect. I doubt that it's relevant but here's how I added the second disk to my system a few months ago. Our (MS windows) sysadmin installed the new disk as the master and put win2000 on it. Our local linux expert then swapped the two disks around (not forgetting to change jumper switches) and did a clean reinstall of RH7.3 from CDs onto the old disk. We added the lilo.conf entries and everything worked fine. When I upgraded, I saved the ISOs onto /dev/hdb2 and read them from there. Would that have any bearing? I confirmed today that the windows installation is intact by removing the linux disk and configuring the windows disk as master. I was able to start up win2000 without any difficulty. Did you upgrade to a newer version of lilo? You might also want to look at trying grub instead of lilo. lilo is 21.4.4-20 which is, I presume, what came with RH7.3 Yeah, I've been putting off trying grub because I couldn't find a big-font, small-words how-to for exactly my configuration, but I bit the bullet today and... ...it worked! I can boot windows again. Actually what happens is that I see my grub.conf settings and then the same message as before, "Invalid system disk Replace disk and then press any key", but this time when I press a key windows does boot. I'll leave it to you to close the bug, as far as I'm concerned it's resolved. Time tracking values updated |