Bug 62069 - Installer will never finish making of bootdisk in case of faulty disk.
Summary: Installer will never finish making of bootdisk in case of faulty disk.
Keywords:
Status: CLOSED NOTABUG
Alias: None
Product: Red Hat Linux
Classification: Retired
Component: anaconda
Version: 9
Hardware: i386
OS: Linux
medium
medium
Target Milestone: ---
Assignee: Jeremy Katz
QA Contact: Brock Organ
URL:
Whiteboard:
Depends On:
Blocks: 61590
TreeView+ depends on / blocked
 
Reported: 2002-03-27 07:09 UTC by Ivo Sarak
Modified: 2008-01-17 17:49 UTC (History)
0 users

Fixed In Version:
Clone Of:
Environment:
Last Closed: 2006-02-21 18:48:38 UTC
Embargoed:


Attachments (Terms of Use)

Description Ivo Sarak 2002-03-27 07:09:39 UTC
From Bugzilla Helper:
User-Agent: Mozilla/4.0 (compatible; MSIE 5.5; Windows 98; T312461)

Description of problem:
I put a disk to 3.5" drive when installer came to a point of making bootdisk 
and it did copied some files, but never finished (I let it hang for about 5 
minutes), until I took the disk out of the drive.
At any point installer didn't say as there a is a problem with drive or disk.
Files what where copied to disk:
initrd.img 40960 bytes
Ldlinux.sys 6656 bytes
vmlinuz 1057280 bytes


How reproducible:
Didn't try


Actual Results:  I got a non-working bootdisk.

Expected Results:  Working bootdisk.

Comment 1 Matt Wilson 2002-04-02 20:01:16 UTC
what kind of floppy drive do you have attached?  Please go to the 4rh virtual
terminal by pressing Ctrl+Alt+F4.  Are there any odd kernel messages there?  If
so, go to VT2 by pressing Alt+F2.  Insert a known good DOS formatted floppy and
type:

mcopy /tmp/syslog a:

and attach that file to this bug.


Comment 2 Michael Fulbright 2002-04-25 21:22:50 UTC
Closing due to inactivity.

Comment 3 Michael Fulbright 2002-05-23 16:55:39 UTC
Closing due to inactivity - please reopen if you have additional comments to add
to this bug.

Comment 4 Red Hat Bugzilla 2006-02-21 18:48:38 UTC
Changed to 'CLOSED' state since 'RESOLVED' has been deprecated.


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