Bug 81595 – making boot disk fails on good disk

Bugzilla will be upgraded to version 5.0 on a still to be determined date in the near future. The original upgrade date has been delayed.

Bug 81595 - making boot disk fails on good disk

Summary:	making boot disk fails on good disk

Status:	CLOSED DUPLICATE of bug 82298

Aliases:	None

Product:	Red Hat Linux
Classification:	Retired
Component:	anaconda (Show other bugs)
Sub Component:
Version:	9
Hardware:	All Linux

Priority	medium Severity medium
Target Milestone:	---
Target Release:	---
Assigned To:	Jeremy Katz
QA Contact:	Mike McLean
Docs Contact:

URL:
Whiteboard:
Keywords:

Depends On:
Blocks:	79579 80605
	Show dependency tree / graph

Reported:	2003-01-10 18:00 EST by Mike McLean
Modified:	2008-01-17 12:49 EST (History)
CC List:	0 users

See Also:
Fixed In Version:
Doc Type:	Bug Fix
Doc Text:
Story Points:	---
Clone Of:
Environment:
Last Closed:	2006-02-21 13:51:06 EST
Type:	---
Regression:	---
Mount Type:	---
Documentation:	---
CRM:
Verified Versions:
Category:	---
oVirt Team:	---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team:	---

Attachments	(Terms of Use)
Add an attachment (proposed patch, testcase, etc.)

Groups: None (edit)

Description Mike McLean 2003-01-10 18:00:06 EST

* -re0110.nightly
* nfs gui install
* usb floppy

while trying to make a boot disk in the installer, I get the invalid boot floppy
dialog.  various trials of badblocks insist the floppy is good, and the
kernel+initrd fits with room to spare, but initrd size on VC3 disagrees with the
initrd that is written to the floppy (the one on the floppy is *larger* by 31237
bytes).

note that this is a usb floppy drive.

The floppy fails to boot with a simple "Boot failed" message.

Comment 1 Mike McLean 2003-01-15 17:40:21 EST

* -re0115.nightly
* hdiso upgrade from 7.2min

observed with non-usb floppy drive

Comment 2 Jeremy Katz 2003-01-28 01:01:21 EST

Consolidating

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

Comment 3 Red Hat Bugzilla 2006-02-21 13:51:06 EST

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.