Koozali.org: home of the SME Server

Legacy Forums => Experienced User Forum => Topic started by: Pat Erler on August 23, 2002, 01:32:04 PM

Title: SME 5.5: booting from bootdisk fails
Post by: Pat Erler on August 23, 2002, 01:32:04 PM
Hello!

i recently upgraded a fairly old pc from SME 5.1.2 to 5.5.

the pc has two 40 gb hd's (not mirrored) which are not detected by the bios, so that i created a bootdisk to boot the pc from.

when i upgraded to 5.5 I let the installer create a bootdisk. unfortunately, the box isn't booting from it. the SYSLINUX is loaded, but after pressing enter on the prompt all it says is "cannot find kernel: linux".

fortunately i still could boot from the old bootdisk, but would like to know what's the problem anyway, mainly in perspective of the upcoming 5.6 release with the new 2.4.x kernel and the definitive need for a new bootdisk then...

regards,

PAT
Title: Re: SME 5.5: booting from bootdisk fails
Post by: Bo Lind on August 23, 2002, 07:22:52 PM
i had the same problem at first. though making a new bootdisk fixed it.
Title: Re: SME 5.5: booting from bootdisk fails
Post by: Pat Erler on August 23, 2002, 07:25:24 PM
Bo Lind wrote:
>
> i had the same problem at first. though making a new bootdisk
> fixed it.
not in my case.. i tried with

   mkbootdisk --device /dev/fd0 2.2.19-7.0.8

any other ideas?

PAT
Title: Re: SME 5.5: booting from bootdisk fails
Post by: Michael Doerner on August 24, 2002, 02:20:35 AM
Hi,

I just had the same problem here on a 5.5 test server.

As a workaround, try typing in esmith at that prompt (when booting from floppy).
The config file is looking for a default image "linux" but the existing image/label to start is actually named "esmith".

Regards,
Michael Doerner

P.S.: I will report it to bugs. It might not be known yet.
Title: Re: SME 5.5: booting from bootdisk fails
Post by: Pat Erler on August 24, 2002, 01:37:32 PM
Michael Doerner wrote:

> As a workaround, try typing in esmith at that prompt (when
> booting from floppy).
> The config file is looking for a default image "linux" but
> the existing image/label to start is actually named "esmith".
and meanwhile change in /sbin/mkbootdisk line 190 from

   default linux

to

   default esmith