1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
58
59
60
61
62
63
64
65
66
67
68
69
70
71
72
73
74
75
76
77
78
79
80
81
82
83
84
85
86
87
88
89
90
91
92
93
94
95
96
97
98
99
100
101
102
103
104
105
106
107
108
109
110
111
112
113
114
115
116
117
118
119
120
121
122
123
124
125
126
127
128
129
130
131
132
133
134
135
136
137
138
139
140
141
142
143
144
145
146
147
148
149
150
151
152
153
154
155
156
157
158
159
160
161
162
163
164
165
166
167
168
169
170
171
172
173
174
175
176
177
178
179
180
181
182
183
184
185
186
187
188
189
190
191
192
193
194
195
196
197
198
199
200
201
202
203
204
205
206
207
208
209
210
211
212
213
214
215
216
217
218
219
220
221
222
223
224
225
226
227
228
229
230
231
232
233
234
235
236
237
238
239
240
241
242
243
244
245
246
247
248
249
250
251
252
253
254
255
256
257
258
259
260
261
262
263
264
265
266
267
268
269
270
271
272
273
274
275
276
277
278
279
280
281
282
283
284
285
286
287
288
289
290
291
292
293
294
295
296
297
298
299
300
301
302
303
304
305
306
307
308
309
310
311
312
313
314
315
316
317
318
319
320
321
322
323
324
325
326
327
328
329
330
331
332
333
334
335
336
337
338
339
340
341
342
343
344
345
346
347
348
349
350
351
352
353
354
355
356
357
358
359
360
361
362
363
364
365
366
367
368
369
370
371
372
373
374
375
376
377
378
379
380
381
382
383
384
385
386
387
388
389
390
391
392
393
394
395
396
397
398
399
400
401
402
403
404
405
406
407
408
409
410
411
412
413
414
415
416
417
418
419
420
421
422
423
424
425
426
427
428
429
430
431
432
433
434
435
436
437
438
439
440
441
442
443
444
445
446
447
448
449
450
451
452
453
454
455
456
457
458
459
460
461
462
463
464
465
466
467
468
469
470
471
472
473
474
475
476
477
478
479
480
481
482
483
484
485
486
487
488
489
490
491
492
493
494
495
496
497
498
499
500
501
502
503
504
505
506
507
508
509
510
511
512
513
514
515
516
517
518
519
520
521
522
523
524
525
526
527
528
529
530
531
532
533
534
535
536
537
538
539
540
541
542
543
544
545
546
547
548
549
550
551
552
553
554
555
556
557
558
559
560
561
562
563
564
565
566
567
568
569
570
571
572
573
574
575
576
577
578
579
580
581
582
583
584
585
586
587
588
589
590
591
592
593
594
595
596
597
598
599
600
601
602
603
604
605
606
607
608
609
610
611
612
613
614
615
616
617
618
619
620
621
622
623
624
625
626
627
628
629
630
631
632
633
634
635
636
637
638
639
640
641
642
643
644
645
646
647
648
649
650
651
652
653
654
655
656
657
658
659
660
661
662
663
664
665
666
667
668
669
670
671
672
673
674
675
676
677
678
679
680
681
682
683
684
685
686
687
688
689
690
691
692
693
694
695
696
697
698
699
700
701
702
703
704
705
706
707
708
709
710
711
712
713
714
715
716
717
718
719
720
721
722
|
<!--startcut ======================================================= -->
<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 3.2//EN">
<html>
<head>
<META NAME="generator" CONTENT="lgazmail v1.3E.t">
<TITLE>The Answer Gang 65: Help on LILO stopping at LI</TITLE>
</HEAD><BODY BGCOLOR="#FFFFFF" TEXT="#000000"
LINK="#3366FF" VLINK="#A000A0">
<!-- ::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::: -->
<P> <hr>
<CENTER>
<!-- *** BEGIN navbar *** -->
<!-- *** END navbar *** -->
</CENTER>
</p>
<P> <hr> <P>
<!-- ::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::: -->
<center>
<H1><A NAME="answer">
<img src="../../gx/dennis/qbubble.gif" alt="(?)"
border="0" align="middle">
<font color="#B03060">The Answer Gang</font>
<img src="../../gx/dennis/bbubble.gif" alt="(!)"
border="0" align="middle">
</A></H1>
<BR>
<H4>By Jim Dennis, Ben Okopnik, Dan Wilder, Breen, Chris, and the Gang,
the Editors of Linux Gazette...
and You!
<br>Send questions (or interesting answers) to
<a href="mailto:linux-questions-only@ssc.com">linux-questions-only@ssc.com</a>
</H4>
<p><em><font color="#990000">There is no guarantee that your questions
here will <b>ever</b> be answered. You can be published anonymously
- just let us know!
</font></em></p>
</center>
<p><hr><p>
<!-- endcut ======================================================= -->
<!-- begin 4 -->
<H3 align="left"><img src="../../gx/dennis/qbubble.gif"
height="50" width="60" alt="(?) " border="0"
>Help on LILO stopping at LI</H3>
<p><strong>From Alessio Frenquelli
</strong></p>
<p align="right"><strong>Answered By Heather Stern
<br></strong></p>
<!-- sig -->
<p><strong>
Hello,
<br>I start thanking you for any help ... I am stuck at this stage, I am not a
GURU on LINUX and I cannot overcome the problem.
</strong><p>
<P><STRONG>
Therefore I cannot really point to what has been changed or went wrong.
</STRONG></P>
<P><STRONG>
Under the Internet I found many, many errors entries pointing to LILO not
being able to load in a disk that is above the 1024 cylinders
</STRONG></P>
<BLOCKQUOTE><IMG SRC="../../gx/dennis/bbub.gif" ALT="(!)"
HEIGHT="28" WIDTH="50" BORDER="0"
> [Heather]
Yes, it used to be LILO's biggest bug, though not its loudest (that one is
people using it wrong and then wailing what are they going to do now that
their MBR is mangled).
</BLOCKQUOTE>
<BLOCKQUOTE>
But ever since the new version those are old messages. The normal solution
until it came out, was to create a tiny <TT>/boot</TT> near the beginning of the
free space - even most dual booters could manage to slip a 20 Mb partition
below the boundary. This works because on the <EM>kernel</EM> and <EM>bootmap</EM> needs
to be below the line; once the kernel is loaded you are no longer working
with real mode BIOS issues at all, you are fully in protected mode and can
access everything the kernel is built for.
</BLOCKQUOTE>
<P><STRONG><IMG SRC="../../gx/dennis/qbub.gif" ALT="(?)"
HEIGHT="28" WIDTH="50" BORDER="0"
>
In my case LILO always worked so far, and I did not surely changed the disk
size, done any repartitioning under Windows NT nor under Linux.
</STRONG></P>
<P><STRONG>
Under Windows, I have run Program => PartitionMagic =>PartitionInfo and I am
attaching the output of the command to this email in case you need to see in
details my machine's partitioning.
</STRONG></P>
<BLOCKQUOTE><IMG SRC="../../gx/dennis/bbub.gif" ALT="(!)"
HEIGHT="28" WIDTH="50" BORDER="0"
> []
So you normally use partition magic for your dual boot menu, I'm guessing.
If so, that is what is presently in your MBR, and would be overwritten
(***warning warning danger will robinson*** or at least look real carefully
that you've set up stanzas for NT also first!) if you change boot = <TT>/dev/hda</TT>
</BLOCKQUOTE>
<h4>ENVIRONMENT</h4>
<p><strong>
Dual bootable Laptop, Toshiba Tecra 8100; one partition is Windows NT
workstation, the other is Linux RedHat 6.1.
</strong><p>
<h4>PROBLEM</h4>
<p><strong>
Linux 6.1 LILO does not longer boot properly. Just stop at the word "LI".
</strong><p>
<h4>SOME TROUBLESHOOTING INFO</h4>
<strong>
Fortunately I have the boot diskette, and booting from it, I can
successfully get to Linux.
</strong><p>
<p><strong>
When running : << <TT>/sbin/lilo</TT> >> I got messages:
</strong><p>
<strong><pre>[root@afrenquelli /etc]# lilo
Warning: device 0x0305 exceeds 1024 cylinder limit
Warning: device 0x0305 exceeds 1024 cylinder limit
Warning: device 0x0305 exceeds 1024 cylinder limit
Warning: device 0x0305 exceeds 1024 cylinder limit
Added linux *
[root@afrenquelli /etc]#
</pre></strong>
<BLOCKQUOTE><IMG SRC="../../gx/dennis/bbub.gif" ALT="(!)"
HEIGHT="28" WIDTH="50" BORDER="0"
> [Heather]
You used to get this before, or you now have a bigger disk than you
used to?
</BLOCKQUOTE>
<BLOCKQUOTE>
By the way, Redhat 6.1 is a bit old, and lilo itself was updated last
year so that 1024 cylinder issues are not a problem for it. (You'll
also want to keep up to date on RH security updates, not quite as
drastic as upgrading the system entirely.)
</BLOCKQUOTE>
<BLOCKQUOTE>
With the newer version, you can add the keyword
</BLOCKQUOTE>
<blockquote><code><font color="#000033"><br> LBA32
</font></code></blockquote>
<BLOCKQUOTE>
into the top of your <TT>/etc/lilo.conf</TT> and it would use a different method
to know where things are on the disk.
</BLOCKQUOTE>
<BLOCKQUOTE>
Being a boot loader, it's critical for lilo to know <EM>precisely</EM> where
the kernel resides on your drive. Moving your kernel file (even if you
then moved it back) or your system maps is a good reason to run <TT>/sbin/lilo.</TT>
</BLOCKQUOTE>
<P><STRONG><IMG SRC="../../gx/dennis/qbub.gif" ALT="(?)"
HEIGHT="28" WIDTH="50" BORDER="0"
>
Some machine's characteristics:
</STRONG></P>
<pre><strong>[root@afrenquelli /tmp]# df -k
Filesystem 1k-blocks Used Available Use% Mounted on
/dev/hda7 1510032 1201268 232056 84% /
/dev/hda5 23302 2648 19451 12% /boot
</strong></pre>
<BLOCKQUOTE><IMG SRC="../../gx/dennis/bbub.gif" ALT="(!)"
HEIGHT="28" WIDTH="50" BORDER="0"
> [Heather]
No relation. Lilo puts its bits into the Master Boot Record, which is
not shown here. If ordered to, it could also use the superblock but,
that is also not shown here, as it's reserved space for the filesystem
driver.
</BLOCKQUOTE>
<Pre><STRONG><IMG SRC="../../gx/dennis/qbub.gif" ALT="(?)"
HEIGHT="28" WIDTH="50" BORDER="0"
>[root@afrenquelli /etc]# lilo
Warning: device 0x0305 exceeds 1024 cylinder limit.
Use of the 'lba32' option may help on newer (EDD BIOS) systems.
Fatal: sector 19926490 too large for linear mode (try 'lba32' instead)
</pre></strong>
<P><STRONG>
------------------------------------- file <TT>/etc/lilo.conf</TT> contains
</STRONG></P>
<pre><strong>boot=/dev/hda7
</strong></pre>
<BLOCKQUOTE><IMG SRC="../../gx/dennis/bbub.gif" ALT="(!)"
HEIGHT="28" WIDTH="50" BORDER="0"
> [Heather]
This says put it in the superblock of the 7 partition ... your /
</BLOCKQUOTE>
<BLOCKQUOTE>
Most people would have it in the MBR ... <TT>/dev/hda</TT> with no number.
Do you have an NT boot menu pointing you into Linux? Because I also
notice that you don't have a chain loader stanza, to ask the item
below to offer you your NT boot setup.
</BLOCKQUOTE>
<Pre><STRONG><IMG SRC="../../gx/dennis/qbub.gif" ALT="(?)"
HEIGHT="28" WIDTH="50" BORDER="0"
>
map=/boot/map
install=/boot/boot.b
prompt
timeout=50
vga=791
</pre></strong>
<BLOCKQUOTE><IMG SRC="../../gx/dennis/bbub.gif" ALT="(!)"
HEIGHT="28" WIDTH="50" BORDER="0"
> [Heather]
a nice framebuffer text mode
<IMG SRC="../../gx/dennis/smily.gif" ALT=":)"
height="24" width="20" align="middle">
</BLOCKQUOTE>
<Pre><STRONG><IMG SRC="../../gx/dennis/qbub.gif" ALT="(?)"
HEIGHT="28" WIDTH="50" BORDER="0"
>
linear
</pre></strong>
<BLOCKQUOTE><IMG SRC="../../gx/dennis/bbub.gif" ALT="(!)"
HEIGHT="28" WIDTH="50" BORDER="0"
> [Heather]
"this is a big disk"
</BLOCKQUOTE>
<Pre><STRONG><IMG SRC="../../gx/dennis/qbub.gif" ALT="(?)"
HEIGHT="28" WIDTH="50" BORDER="0"
>
default=linux
image=/boot/vmlinuz-2.2.12-20
label=linux
initrd=/boot/initrd-2.2.12-20.img
read-only
root=/dev/hda7
</pre></strong>
<BLOCKQUOTE><IMG SRC="../../gx/dennis/bbub.gif" ALT="(!)"
HEIGHT="28" WIDTH="50" BORDER="0"
> [Heather]
The stock redhat kernel, I see.
</BLOCKQUOTE>
<P><STRONG><IMG SRC="../../gx/dennis/qbub.gif" ALT="(?)"
HEIGHT="28" WIDTH="50" BORDER="0"
>
I did not "fiddle" with Linux at all before this error appeared !
</STRONG></P>
<BLOCKQUOTE><IMG SRC="../../gx/dennis/bbub.gif" ALT="(!)"
HEIGHT="28" WIDTH="50" BORDER="0"
> [Heather]
WHat do you normally use Linux for?
</BLOCKQUOTE>
<P><STRONG><IMG SRC="../../gx/dennis/qbub.gif" ALT="(?)"
HEIGHT="28" WIDTH="50" BORDER="0"
>
So , I changed in <TT>/etc/lilo.conf</TT> the value "linear" with "lba32", and then
<TT>/sbin/lilo</TT> runs fine with :
</strong></p>
<strong><pre>c[root@afrenquelli /etc]# lilo -v
LILO version 21.6-1, Copyright (C) 1992-1998 Werner Almesberger
Linux Real Mode Interface library Copyright (C) 1998 Josh Vanderhoof
Development beyond version 21 Copyright (C) 1999-2000 John Coffman
Released 16-Dec-2000 and compiled at 17:04:30 on Jan 9 2001.
Reading boot sector from /dev/hda7
Merging with /boot/boot.b
Boot image: /boot/vmlinuz-2.2.12-20
Mapping RAM disk /boot/initrd-2.2.12-20.img
Added linux *
/boot/boot.0307 exists - no backup copy made.
Writing boot sector.
</pre></strong>
<p><strong>
At this stage I "REALLY" hoped that the problem went away, but I still get
only "LI" at boot time,
I can only use the boot diskette to get into Linux.
</strong></p>
<P><STRONG><IMG SRC="../../gx/dennis/qbub.gif" ALT="(?)"
HEIGHT="28" WIDTH="50" BORDER="0"
>
ATTEMPTS TO SOLVE IT
===================
</STRONG></P>
<P><STRONG>
Thinking that the latest version of LILO "could" have fixed this problem, I
have downloaded LILO 21.6.1-1 from
<A HREF="http://rpmfind.net/linux/RPM/contrib/libc6/i386/lilo-21.6.1-1.i386.html"
>http://rpmfind.net/linux/RPM/contrib/libc6/i386/lilo-21.6.1-1.i386.html</A>
</STRONG></P>
<P><STRONG><CODE>
I have then upgraded my LILO with : "rpm -Uhv <nomefile>.rpm"
</CODE></STRONG></P>
<BLOCKQUOTE><IMG SRC="../../gx/dennis/bbub.gif" ALT="(!)"
HEIGHT="28" WIDTH="50" BORDER="0"
> [Heather]
Good deal! Yay!
</BLOCKQUOTE>
<BLOCKQUOTE>
You should also keep up to date on RedHat security updates for RH 6.1.
(Not directly related to this, just a good idea)
</BLOCKQUOTE>
<BLOCKQUOTE>
Any other recent installs or upgrades?
</BLOCKQUOTE>
<P><STRONG><IMG SRC="../../gx/dennis/qbub.gif" ALT="(?)"
HEIGHT="28" WIDTH="50" BORDER="0"
>
The upgrade completed fine, and then when I try to run <TT>/sbin/lilo</TT> I got:
</STRONG></P>
<pre><strong>[root@afrenquelli /etc]# lilo
Warning: device 0x0305 exceeds 1024 cylinder limit.
Use of the 'lba32' option may help on newer (EDD BIOS) systems.
Fatal: sector 19926490 too large for linear mode (try 'lba32' instead)
</strong></pre>
<BLOCKQUOTE><IMG SRC="../../gx/dennis/bbub.gif" ALT="(!)"
HEIGHT="28" WIDTH="50" BORDER="0"
> [Heather]
Even better, I'm glad they provide useful error messages ... that tell you
what to do about an error.
</BLOCKQUOTE>
<P><STRONG><IMG SRC="../../gx/dennis/qbub.gif" ALT="(?)"
HEIGHT="28" WIDTH="50" BORDER="0"
>
So , I changed in <TT>/etc/lilo.conf</TT> the value "linear" with "lba32", and then
<TT>/sbin/lilo</TT> runs fine with :
</STRONG></P>
<pre><strong>c[root@afrenquelli /etc]# lilo -v
LILO version 21.6-1, Copyright (C) 1992-1998 Werner Almesberger
Linux Real Mode Interface library Copyright (C) 1998 Josh Vanderhoof
Development beyond version 21 Copyright (C) 1999-2000 John Coffman
Released 16-Dec-2000 and compiled at 17:04:30 on Jan 9 2001.
Reading boot sector from /dev/hda7
Merging with /boot/boot.b
Boot image: /boot/vmlinuz-2.2.12-20
Mapping RAM disk /boot/initrd-2.2.12-20.img
Added linux *
/boot/boot.0307 exists - no backup copy made.
Writing boot sector.
</strong></pre>
<P><STRONG>
At this stage I "REALLY" hoped that the problem went away, but I still get
only "LI" at boot time,
I can only use the boot diskette to get into Linux.
</STRONG></P>
<BLOCKQUOTE><IMG SRC="../../gx/dennis/bbub.gif" ALT="(!)"
HEIGHT="28" WIDTH="50" BORDER="0"
> [Heather]
That's weird
<IMG SRC="../../gx/dennis/unsmily.gif" ALT=":("
height="24" width="20" align="middle">
</BLOCKQUOTE>
<BLOCKQUOTE>
Maybe you need to take the linear or lba32 mark <EM>out</EM> ??
</BLOCKQUOTE>
<h4><IMG SRC="../../gx/dennis/qbub.gif" ALT="(?)"
HEIGHT="28" WIDTH="50" BORDER="0"
>
WHAT'S NEXT ?
</h4>
<P><STRONG>
If I could avoid to rebuild the LINUX partition would be GREATLY
appreciated, since I am not a Linux expert and I would need some guidance
also lots of other software is installed and I would like to avoid to
reinstall the all lot !
</STRONG></P>
<BLOCKQUOTE><IMG SRC="../../gx/dennis/bbub.gif" ALT="(!)"
HEIGHT="28" WIDTH="50" BORDER="0"
> [Heather]
Although I'd like to note at this time that making sure your backups of your
personal data on both OS setups are in current state, and good working
condition... and not stored on the same disk. Tapes or a CD-R or a stack
of ZIP cartridges maybe.
</BLOCKQUOTE>
<P><STRONG><IMG SRC="../../gx/dennis/qbub.gif" ALT="(?)"
HEIGHT="28" WIDTH="50" BORDER="0"
>
Could I just de-install LILO and re-install LILO ?
</STRONG></P>
<BLOCKQUOTE><IMG SRC="../../gx/dennis/bbub.gif" ALT="(!)"
HEIGHT="28" WIDTH="50" BORDER="0"
> [Heather]
should be able to. lilo -u to put the backup bits from <TT>/boot/boot.0307</TT>
back into the superblock <TT>/dev/hda7</TT> (where it hopefully came from). If
it whines abotu timestamps, lilo -U insists.
</BLOCKQUOTE>
<BLOCKQUOTE>
Then, you should be able to run lilo again to install it as a fresher
instance.
</BLOCKQUOTE>
<P><STRONG><IMG SRC="../../gx/dennis/qbub.gif" ALT="(?)"
HEIGHT="28" WIDTH="50" BORDER="0"
>
Or should I add something into the <TT>/etc/lilo.conf</TT> and try to run "lilo"
again ?
</STRONG></P>
<P><STRONG>
Could I somehow just rebuild the "booting" portion of the Linux, and if so,
could you please provide detailed instructions on how to do it ?
</STRONG></P>
<BLOCKQUOTE><IMG SRC="../../gx/dennis/bbub.gif" ALT="(!)"
HEIGHT="28" WIDTH="50" BORDER="0"
> [Heather]
lilo has actually very excellent documentation that comes with it... much
finer than many application packages in fact. If you run 'locate lilo'
a bunch of things will scroll by, and several be from the doc directory
tree somewhere on your disk. I'm guessing <TT>/usr/doc/lilo-</TT> (some version
number) but I'm not near a RedHat system right now to look. Anyways
on my <A HREF="http://www.suse.com/">SuSE</A> system it's in <TT>/usr/doc/packages/lilo</TT> ... I have some dvi
files (readable or printable by LaTeX tools) and some compressed postscript
files (but ghostview ... the command gv ... is glad to show these to me).
</BLOCKQUOTE>
<BLOCKQUOTE>
The README, however, is the right place to start, because unlike most
readme files around here (which can be summarized "so this is the foo
program, I created it because bla bla. It's under the GPL/artistic/whatever
license, see COPYING. If there are any bugs (hope not) get in contact
with me at ...") it has some serious data in it. Consider it your quickstart
guide to a working LILO.
</BLOCKQUOTE>
<BLOCKQUOTE>
You've already done a number of the obvious things, so, let us know if the
uninstall/reinstall trick works, and if that readme isn't helpful to you
we may be able to translate it to plainer english.
</BLOCKQUOTE>
<P><STRONG><IMG SRC="../../gx/dennis/qbub.gif" ALT="(?)"
HEIGHT="28" WIDTH="50" BORDER="0"
>
Kind regards,
<br>alessio
</STRONG></P>
<BLOCKQUOTE><IMG SRC="../../gx/dennis/bbub.gif" ALT="(!)"
HEIGHT="28" WIDTH="50" BORDER="0"
> [Heather]
Our best hopes for your system, Alessio. We'd really like to hear back
what fixed it, if you manage to solve it.
</BLOCKQUOTE>
<BLOCKQUOTE><IMG SRC="../../gx/dennis/bbub.gif" ALT="(!)"
HEIGHT="28" WIDTH="50" BORDER="0"
> [Ben]
Ah - an opportunity to shill for one of my scripts!
<IMG SRC="../../gx/dennis/smily.gif" ALT=":)"
height="24" width="20" align="middle">
</BLOCKQUOTE>
<BLOCKQUOTE>
Here's where my "doc" script would come in really handy: all you'd have to
do is type something like "doc lil", and it would give you a numbered list
of all the subdirectories in your "doc" directory that start with 'lil'.
Typing that number enters the directory and shows you a numbered file list;
typing one of <EM>those</EM> numbers displays the file, no matter what its format
is. When you exit the viewer, it shows you the list again, and gives you a
chance to "fish around" in subdirectories and other files.
</BLOCKQUOTE>
<BLOCKQUOTE>
I know I sent it into LG as a 2-cent tip quite a while ago, but I believe
I've made a few improvements since then, so here it is:
</BLOCKQUOTE>
<p align="center">See attached <a href="../misc/tag/doc.bash.txt">doc.bash.txt</a></p>
<!-- . . . . . . . . . . . . . . . . . . . -->
<HR WIDTH="40%" ALIGN="center">
<P><strong><img src="../../gx/dennis/bbubble.gif"
height="50" width="60" alt="(!) " border="0"
>
Heather,
<br>thank you for your complete and prompt reply.
</strong></p>
<p><strong>
I will provide here some answers from the queries that you had.
At this stage it seems that the problem is caused by one of our product,
that I have recently installed under Linux. After reporting the LI problem
to our support team, I received a reply where they state that this product
ast times seems to affect LILO, and to cause the problem that I have
described to you.
</strong></p>
<p><strong>
I am still awaiting from our support team, if they know how to fix the
problem of LILO.
</strong></p>
<p><strong>
And now to your questions:
</strong></p>
<BLOCKQUOTE><IMG SRC="../../gx/dennis/bbub.gif" ALT="(!)"
HEIGHT="28" WIDTH="50" BORDER="0"
> [Heather]
Any recent changes? The next L should represent finding the second stage
loader so the kernel can get going. These could be disk-ish things like
you caught a virus and successfully cleaned it out, had a hard crash and
needed to reboot, etc
</blockquote>
<P><STRONG><IMG SRC="../../gx/dennis/qbub.gif" ALT="(?)"
HEIGHT="28" WIDTH="50" BORDER="0"
>
Yes, I have installed a new Micromuse Package under LINUX. After the
installation I rebooted few times without problem, but then one day, LI
started to happen.
</strong></p>
<pre>
Warning: device 0x0305 exceeds 1024 cylinder limit
</pre>
<BLOCKQUOTE><IMG SRC="../../gx/dennis/bbub.gif" ALT="(!)"
HEIGHT="28" WIDTH="50" BORDER="0"
> [Heather]
You used to get this before, or you now have a bigger disk than you
used to?
</blockquote>
<P><STRONG><IMG SRC="../../gx/dennis/qbub.gif" ALT="(?)"
HEIGHT="28" WIDTH="50" BORDER="0"
>
No changes on disk size, or disk partitioning under Linux or under NT. I
never run /sbin/lilo before , so I cannot tell you if this was a problem.
But LILO always worked before.
</strong></p>
<p>
I did not "fiddle" with Linux at all before this error appeared !
</p>
<BLOCKQUOTE><IMG SRC="../../gx/dennis/bbub.gif" ALT="(!)"
HEIGHT="28" WIDTH="50" BORDER="0"
> [Heather]
WHat do you normally use Linux for?
</blockquote>
<P><STRONG><IMG SRC="../../gx/dennis/qbub.gif" ALT="(?)"
HEIGHT="28" WIDTH="50" BORDER="0"
>
I use Linux to run Micromuse products, and as I said, the problem started to
happen since I installed one of our package. Other people installed it on
their laptop, but they did not report the error. Support told me that at
times this product is know to cause some problem with LILO, but they are not
too sure.
</strong></p>
<BLOCKQUOTE><IMG SRC="../../gx/dennis/bbub.gif" ALT="(!)"
HEIGHT="28" WIDTH="50" BORDER="0"
> [Heather]
That's weird
<IMG SRC="../../gx/dennis/unsmily.gif" ALT=":("
height="24" width="20" align="middle">
<br> Maybe you need to take the linear or lba32 mark *out* ??
</blockquote>
<P><STRONG><IMG SRC="../../gx/dennis/qbub.gif" ALT="(?)"
HEIGHT="28" WIDTH="50" BORDER="0"
>
You mean, remove linear or lba32 from lilo.conf and try to run lilo again ?
I will try this.
</strong></p>
<BLOCKQUOTE><IMG SRC="../../gx/dennis/bbub.gif" ALT="(!)"
HEIGHT="28" WIDTH="50" BORDER="0"
> [Heather]
Then, you should be able to run lilo again to install it as a fresher
instance.
</blockquote>
<P><STRONG><IMG SRC="../../gx/dennis/qbub.gif" ALT="(?)"
HEIGHT="28" WIDTH="50" BORDER="0"
>
So I should just run :
</strong></p>
<p><strong><ol>
<li>lilo -u or lilo -U
<li>Then how do I re-install LILO ? Just running /sbin/lilo or do I need to
download the LILO package from somewhere and the install it with "rpm -Uhv
<nomefile>.rpm" or something similar ?
</ol></strong></p>
<p><strong>
Thank you for your help once again, I will keep you posted !
<br>ciao, alessio
</strong></p>
<!-- . . . . . . . . . . . . . . . . . . . -->
<HR WIDTH="40%" ALIGN="center">
<P><strong><img src="../../gx/dennis/bbubble.gif"
height="50" width="60" alt="(!) " border="0"
>
Heather,
</p></strong>
<p><strong>
here is how I got this problem fixed with the help of the support personnel
in our company
</p></strong>
<p><strong>
Thank you once again for your support !!!
</p></strong>
<p><strong>
Support adviced me that the following recovery procedure for LILO problems
is to be used for Laptop that have dual boot partition, NT & Linux, when the
menu received at boot time shows OS LOADER, and then it presents 2 choice ,
Windows NT or Linux.
</p></strong>
<p><strong>
Steps taken:
</p></strong>
<p><strong><ol start="0">
<li> Boot Linux from bootdisk
<li> Run /sbin/lilo -v (make sure no errors are displayed)
<li> Insert a new diskette and mount it:
<blockquote><code><font color="#000033"><br> mount -t msdos /dev/fd0 /mnt/floppy
</font></code></blockquote>
<li> df -k gives me 2 filesystems:
<blockquote><code><font color="#000033"><br> /dev/hda7 Mounted /
<br> /dev/hda5 Mounted /boot
</font></code></blockquote>
<li> run command :
<blockquote><code><font color="#000033"><br> dd if=/dev/hda7 of=/tmp/bootsect.lnx bs=512 count=1
</font></code></blockquote>
<li><tt> cp /tmp/bootsect.lnx /mnt/floopy</TT>
<li> shutdown and reboot under NT
<li><tt> copy c:\bootsect.lnx c:\bootsect.lnx_old</tt>
<li><tt> copy a:\bootsect.lnx c:\bootsect.lnx</tt>
<li> reboot under Linux
</ol></strong><p>
<p><strong>
PROBLEM solved, LILO loads correctly.
</strong></p>
<p><strong>
Ciao, alessio
</strong></p>
<!-- end 4 -->
<!--startcut ======================================================= -->
<P> <hr> </p>
<!-- *** BEGIN copyright *** -->
<H5 align="center">This page edited and maintained by the Editors
of <I>Linux Gazette</I>
<a href="http://www.linuxgazette.com/copying.html"
>Copyright ©</a> 2001
<BR>Published in issue 65 of <I>Linux Gazette</I> April 2001</H5>
<H6 ALIGN="center">HTML script maintained by
<A HREF="mailto:star@starshine.org">Heather Stern</a> of
Starshine Technical Services,
<A HREF="http://www.starshine.org/">http://www.starshine.org/</A>
</H6>
<!-- *** END copyright *** -->
<P> <hr>
<!-- begin tagnav ::::::::::::::::::::::::::::::::::::::::::::::::::-->
<p align="center">
<table width="100%" border="0"><tr>
<td align="right" valign="center"
><IMG ALT="" SRC="../../gx/navbar/left.jpg"
WIDTH="14" HEIGHT="45" BORDER="0" ALIGN="middle" border="0"
><A HREF="..//"
><IMG SRC="../../gx/navbar/toc.jpg" align="middle"
ALT="[ Table Of Contents ]" border="0"></A
><A HREF="../lg_answer65.html"
><IMG SRC="../../gx/dennis/answertoc.jpg" align="middle"
ALT="[ Answer Guy Current Index ]" border="0"></A></td>
<td align="center" valign="center"><A HREF="../lg_answer65.html#greeting"><img align="middle"
src="../../gx/dennis/smily.gif" alt="greetings" border="0"></A>
<A HREF="1.html">1</A>
<A HREF="2.html">2</A>
<A HREF="3.html">3</A>
<A HREF="4.html">4</A>
<A HREF="5.html">5</A>
<A HREF="6.html">6</A>
<A HREF="7.html">7</A>
<A HREF="8.html">8</A>
<A HREF="9.html">9</A>
<A HREF="10.html">10</A>
<A HREF="11.html">11</A>
<A HREF="12.html">12</A>
<A HREF="13.html">13</A>
<A HREF="14.html">14</A>
<A HREF="15.html">15</A>
<A HREF="16.html">16</A>
<A HREF="17.html">17</A>
<A HREF="18.html">18</A>
<A HREF="19.html">19</A>
<A HREF="20.html">20</A>
<A HREF="21.html">21</A>
<A HREF="22.html">22</A>
<A HREF="23.html">23</A>
<A HREF="24.html">24</A>
<A HREF="25.html">25</A>
<A HREF="26.html">26</A>
<A HREF="27.html">27</A>
<A HREF="28.html">28</A>
<A HREF="29.html">29</A></td>
<td align="left" valign="center"><A HREF="../../tag/kb.html"
><IMG SRC="../../gx/dennis/answerpast.jpg" align="middle"
ALT="[ Index of Past Answers ]" border="0"></A
><IMG ALT="" SRC="../../gx/navbar/right.jpg" align="middle"
WIDTH="14" HEIGHT="45" BORDER="0"></td></tr></table>
</p>
<!-- end tagnav ::::::::::::::::::::::::::::::::::::::::::::::::::::-->
<P> <hr>
<CENTER>
<!-- *** BEGIN navbar *** -->
<!-- *** END navbar *** -->
</CENTER>
</p>
<!-- ::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::: -->
</BODY></HTML>
<!--endcut ========================================================= -->
|
