Topic: Boot Floppy

[Duncan Drury]

I have SME Server 5.5 set up on an old machine that has a BIOS unable to recognise hard drives over 32Gb.  In order to get around that and be able to use the full 40Gb on the hard drives I am booting SME Server from the "emergency" floppy.  The problem is that the floppy automatically tries to boot "Linux" when in fact you need to boot "esmith".  This means that every time the server goes down or needs rebooting I actually have to go to the computer and type esmith.  This is a pain - how can I fix what is on the floppy so it automatically boots SME Server.

Duncan

[Duncan Drury]

Ok, I figured it out on my own.

The boot floppy that is created by SME Server 5.6 setup isn't quite configured right.

You need to edit the file syslinux.cfg on the floppy.

Change the line that reads:

default linux

to

default esmith

Now your boot floppy will boot up SME Server unattended!

Dunx

[Michiel]

> The boot floppy that is created by SME Server 5.6 setup isn't
> quite configured right.

Would you mind mailing  this to smebugs@mitel.com? This loks like a bug.

[Duncan Drury]

Sorry, that should have been SME Server 5.5 not 5.6 - should I still put it forward as a bug?

[Michiel]

A little e-mail never hurts.

[Charlie Brady]

Michiel wrote:

> A little e-mail never hurts.

In this case it does. It wastes time. 5.5 is no longer being maintained by Mitel (and its use is deprecated).

Unless this bug exists in 5.6 and/or 6.0beta, then smebugs@mitel.com shouldn't be bothered.

Thanks

Charlie

[Duncan Drury]

Damnit!  I thought I had it all sorted, but now I find out that SME Server has a bug in the Raid1 implementation, and the only workaround published relies on the BIOS reporting the correct drive size.  Now instead of being limited to 32Gb I am limited to 19Gb because RAID1 can only see half of the drives.

Not good at all...

[Charlie Brady]

Duncan Drury wrote:
>
> Damnit!  I thought I had it all sorted, but now I find out
> that SME Server has a bug in the Raid1 implementation,...

No, "had" a bug. Backup (to tape), install 6.0b3+updates, and restore.
 and you should see all your disk.

Charlie