Topic: Out of the blue - reboot now stops at LI (LILO?)

[Robert Harlow]

Sirs

Last week I converted a SME5.5 server-only to SME5.6 server-gateway and this week have been running up a whole bunch of addons. Apparently *something" (unspecified) has very recently occurred or been inflicted on the server:-| All reboots now stop at the LI point. The *rescue floppy* is able to continue the boot and all later appears well enough;~/  Would you please direct me through some sort of boot repair process?

My searches for *LI* in your database needed a bit of tweaking. Kept hitting the 30sec time-out with all the returns. Nevertheless by restricting the searches to just the header and plugging in the following NOT switches...

li -client -charlie -public -link -list -installing -satelli -sateli -compatibili -compatabili -killi -scalabili -lib -lim -alia -replic -deliv -prolia -lin -lik -invali -abili -applic -publi -ali -poli -utili -chili -liv -dupli -cli -lic -mulit -lit -trilli -compli -replies -light -mutli -familia -liebert -etablish -establish -lif -appli

...I got through to some 70 mostly appropriate hits on the topic of LI. What I found suggested that I really ought to get some expert guidance on the repair;~/ Think you may need to see...

--------------------------------------------------------
# contents of /etc/lilo.conf        
prompt
timeout=50
default=Mitel-SME
boot=/dev/sda
map=/boot/map
install=/boot/boot.b
message=/boot/mitel.pcx
linear
image=/boot/vmlinuz-2.4.18-5
   label=Mitel-SME
   initrd=/boot/initrd-2.4.18-5.img
   read-only
   root=/dev/sda3
--------------------------------------------------------

...and if you need anything else do please let me know:-)

best wishes, Robert

[Duncan]

LI usually means a geometry mismatch (1024 limit). Try running /sbin/lilo and see what happens.

Regards Duncan

[Robert Harlow]

Duncan

I was mistaken when I implicated the bunch of addons. In actual fact this issue arises *right after* running Update2. Please see all the further information in my newer thread running under the title of...
*Clean Install 5.6 --> Updater2 --> boot stops at LI*

Do you have a reason to suspect that running Update2 has a specific or actual impact on any or all of my drives' geometry? It's happened twice now - after running Update2. The last time it was via a clean install.

I have done as you suggested, the following nonsense was returned:
(manually retyped across the room from another workstation)...
---------------------------------------------------------->>
Warning: BIOS drive 0x82 may not be accessible
Warning: BIOS drive 0x82 may not be accessible
Warning: BIOS drive 0x82 may not be accessible
Warning: BIOS drive 0x82 may not be accessible
Warning: BIOS drive 0x82 may not be accessible
Added Mitel-SME *
<<---------------------------------------------------------
...for copious information on the issue perhaps you'd be good enough to either read the thread I quoted above or, better still, join the latter with a response to this issue, which is seemingly straight from an as yet undiscovered episode out from Alice In Wonderland;~/

best wishes, Robert