Mailinglist Archive: opensuse (3337 mails)

< Previous Next >
Re: [SLE] strange boot problem after YOU
  • From: Daniel Bauer <linux@xxxxxxxxxxxxxxxx>
  • Date: Mon, 3 Apr 2006 08:40:09 +0200
  • Message-id: <200604030840.09999.linux@xxxxxxxxxxxxxxxx>
Am Sonntag, 2. April 2006 18:33 schrieb Anders Johansson:
> On Sun, 2006-04-02 at 13:20 +0200, Daniel Bauer wrote:
> > - why does my "normal" SUSE 10 (same kernel, no separate /boot partition)
> > boot without any poblem?
> > - why did the new SUSE 10 boot easily before the YOU update?
> When you install a package, where exactly it gets written on the
> partition isn't predetermined. The YOU update included an updated grub
> and/or kernel. It seems likely that before the update, they were placed
> where the BIOS could read them, but after the update they got placed
> elsewhere. If you have an old BIOS things like this can happen.
> This is why you should have a separate /boot partition entirely located
> within the 1024 cylinder limit, to prevent things like this from
> happening. If you have a partition that extends beyond it, it may work
> or it may not, it's up to the file system.

I could try this, but I am afraid of adding an additional partition because,
as you can see, I have other patitions on /dev/hda used by the working

What happens to /dev/hda2-7, including the "extended partition" /dev/hda4,
when I split /dev/hda1 in two partitions (/boot and /)? Then they will get
other numbers, don't they? And what will my now working installation "think"
of this? Sorry, if these questions are stupid, but I'd rather be too careful
than a bit too little...

> On the other hand, you may also want to check for an updated BIOS that
> doesn't have this limitation

I don't want to do this, as my "normal" system just runs perfect and also here
I am afraid that with a change or update I could ruin something...

Daniel Bauer photographer Basel Switzerland
professional photography:
special interest site:

< Previous Next >