Bug 13614 - lilo's "Warning: %s is not on the first disk" is not handled
Summary: lilo's "Warning: %s is not on the first disk" is not handled
Status: CLOSED DUPLICATE of bug 14204
Alias: None
Product: Red Hat Linux
Classification: Retired
Component: anaconda
Version: 7.1
Hardware: i386
OS: Linux
Target Milestone: ---
Assignee: Michael Fulbright
QA Contact:
: 17358 18660 (view as bug list)
Depends On:
TreeView+ depends on / blocked
Reported: 2000-07-09 01:25 UTC by Jay Freeman
Modified: 2008-05-01 15:37 UTC (History)
0 users

Clone Of:
Last Closed: 2001-02-08 20:36:36 UTC

Attachments (Terms of Use)

Description Jay Freeman 2000-07-09 01:25:11 UTC
When installing lilo on the boot record of a drive that isn't the boot 
drive, the installation gets the message (hdc1 used for example):

Warning: hdc1 is not on the first disk

printed over it (which it then prints partly over with the boot-disk 
creation dialog).  This should really be handled better, maybe grab the 
stderr from lilo and return it to the installer in a dialog box.  What 
would REALLY be nice is if the user could be warned of stuff like that 
before he ever got that far in the process, though.

Comment 1 Glen Foster 2000-07-18 20:08:17 UTC
This defect is considered MUST-FIX for Winston Beta-5

Comment 2 Glen Foster 2000-07-21 18:10:48 UTC
This defect has been re-classified as MUST-FIX for Winston Gold-release

Comment 3 Michael Fulbright 2000-08-11 15:48:50 UTC
The installer team has decided to handle this issue as a future feature.

Comment 4 Michael Fulbright 2000-09-26 16:10:50 UTC

Comment 5 Michael Fulbright 2000-09-26 16:56:31 UTC

Comment 6 Michael Fulbright 2000-09-29 17:04:50 UTC
*** Bug 17358 has been marked as a duplicate of this bug. ***

Comment 7 Michael Fulbright 2000-10-27 19:45:05 UTC
*** Bug 18660 has been marked as a duplicate of this bug. ***

Comment 8 Michael Fulbright 2000-12-21 22:22:50 UTC
How did you get the MBR written to something other than the first drive?

I cannot reproduce this problem w/o more information.


Comment 9 Michael Fulbright 2001-01-19 21:36:14 UTC
Closing due to inactivity.

Comment 10 Jay Freeman 2001-01-24 23:42:31 UTC
OK, apparently I only _thought_ I replied to this bug.  Here goes:

I never said "master boot record", I said "boot record".  I was installing to 
hdc1 on a computer that had Windows 2000 on hda1.  It was complaining because, 
even though it was writing LILO to disk, it wasn't going to get executed as 
hdc1 wasn't active and hdc wasn't even the boot drive.  Hence a "warning" and 
not an "error", it is just saying "this isn't going to help much unless you 
rearrange your drives".

I would _much_ rather see a generic error handling system than trying to solve 
this particular problem.  I seriously thought you were joking asking me how 
to "reproduce the problem", and now I see this "closing due to inactivity" 
notice.  Just go into the code, find wherever it is you exec lilo, redirect its 
stderr to its stdout, change it to a popen, grab the output, and shove it in a 
window.  A general solution to "what happens when LILO generates an error" is 
the way to go here, that way when LILO gets some new error ability added you 
don't need to keep screwing with the installation program.

Comment 11 Michael Fulbright 2001-02-08 20:36:30 UTC
Related to bug 14204.

*** This bug has been marked as a duplicate of 14204 ***

Note You need to log in before you can comment on or make changes to this bug.