Bug 157502 - Can't boot after upgrade
Summary: Can't boot after upgrade
Status: RESOLVED WONTFIX
Alias: None
Product: SUSE Linux 10.1
Classification: openSUSE
Component: YaST2 (show other bugs)
Version: Beta 7
Hardware: i586 SuSE Linux 10.1
: P3 - Medium : Normal (vote)
Target Milestone: ---
Assignee: Olaf Dabrunz
QA Contact: Klaus Kämpf
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2006-03-12 22:18 UTC by Vladimir Nadvornik
Modified: 2007-05-10 12:44 UTC (History)
1 user (show)

See Also:
Found By: Other
Services Priority:
Business Priority:
Blocker: ---
Marketing QA Status: ---
IT Deployment: ---

Attachments
y2logs.tgz (761.78 KB, application/x-compressed-tar)
2006-03-12 22:19 UTC, Vladimir Nadvornik 		Details
grub configuration (961 bytes, application/x-compressed-tar)
2006-03-13 11:33 UTC, Vladimir Nadvornik 		Details
View All Add an attachment (proposed patch, testcase, etc.)

Note You need to log in before you can comment on or make changes to this bug.
Description Vladimir Nadvornik 2006-03-12 22:18:49 UTC 
The machine had one instance of grub installed on /dev/hda and
second on /dev/hda3. The grub on /dev/hda3 was installed as a part of 10.0
and was run by the grub on /dev/hda by chainloader.
After upgrade 10.0 -> 10.1 beta7 on hda3 the system could no longer boot,
only a message "No installed OS" (or something similar) appeared.
Booting rescue system and reinstalling grub on /dev/hda fixed this and 
I could finish the installation.
Comment 1 Vladimir Nadvornik 2006-03-12 22:19:50 UTC 
Created attachment 72469 [details]
y2logs.tgz
Comment 2 Michael Gross 2006-03-13 10:23:05 UTC 
Please also attach `fdisk -l', /etc/grub.conf and /boot/grub/menu.lst here, possibly the faulty one.
Comment 3 Vladimir Nadvornik 2006-03-13 11:33:30 UTC 
Created attachment 72520 [details]
grub configuration

The configuration looks good now. Unfortunately I don't know how it looked before installation.

From yast2 logs I could find that:

1. examine_mbr.pl failed because of missing perl modules

2. yast2 decided to replace the grub mbr with a generic one. It seems like there was no partition
set as bootable (or wrong partition, maybe hda1).
With the originally installed grub mbr it did not matter.
Comment 4 Michael Gross 2006-03-14 11:16:43 UTC 
OK then it looks like a YaST problem.
Comment 5 Vladimir Nadvornik 2006-03-23 10:51:34 UTC 
The same happened with update beta7 -> beta8.

I tried to debug it and I have found that:

- the mbr installed by yast can boot only from hda1. For hda2 or hda3
  it writes the message 'No operating system'.
- grub (loaded from floppy) can boot with chainloader from
  all partitions (hda1, hda2, hda3)
- there are no other changes except setting active partition
Comment 6 Stefan Fent 2007-05-10 12:44:18 UTC 
I'll close this bug 'wontfix'.
If you can reproduce this with openSUSE 10.3, please feel free to reopen (and adjust product)