Bug 110046 - Bootdisk.img diskette can't boot
Bootdisk.img diskette can't boot
Product: Fedora
Classification: Fedora
Component: anaconda (Show other bugs)
i386 Linux
medium Severity medium
: ---
: ---
Assigned To: Jeremy Katz
Mike McLean
Depends On:
  Show dependency treegraph
Reported: 2003-11-14 09:29 EST by Steve Bourland
Modified: 2007-11-30 17:10 EST (History)
0 users

See Also:
Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
Last Closed: 2003-11-14 12:53:18 EST
Type: ---
Regression: ---
Mount Type: ---
Documentation: ---
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---

Attachments (Terms of Use)

  None (edit)
Description Steve Bourland 2003-11-14 09:29:44 EST
From Bugzilla Helper:
User-Agent: Mozilla/5.0 (Windows; U; WinNT4.0; en-US; rv:1.5)
Gecko/20031007 Firebird/0.7

Description of problem:
Attempting to install Fedora Core from hard disk images.  

System begins boot process after pressing 'Enter' to begin graphical
installation, loads vmlinuz and initrd.img and then suffers a kernel
panic during the flurry of activity that follows.

Version-Release number of selected component (if applicable):

How reproducible:

Steps to Reproduce:
1.Generate installation diskette as indicated above
2.Attempt to boot computer using said diskette

Actual Results:  Kernel panic, can not mount root fs on 48:05

Expected Results:  Begin anaconda installation process without a
kernel panic

Additional info:

First attempt at reporting a bug, hope it makes sense.
Comment 1 Steve Bourland 2003-11-14 09:33:03 EST
Here is the last bit of information shown during the boot process:

NET4:  Unix Domain Sockets 1.0/SMP for Linux NET4.0
RAMDISK:  Compressed image found at block 0
crc error<6>Freeing initrd memory:  528k freed
VFS:  Cannot open root device "" or 48:05
Please append correct "root=" boot option
Kernel panic:  VFS:  Unable to mount root fs on 48:05

I have created several boot floppies via:

dd if=bootdisk.img of=/dev/fd0 bs=1440k

but they all demonstrate the same problem on two platforms (a P4 and
an ancient dual PPro) so I don't believe it is a problem with the
media or the hardware.  I was unable to find any other reports of a
similar problem so I don't believe this is a duplicate report.  The
md5sums checked OK on the iso images from which the bootdisk.img was
Comment 2 Jeremy Katz 2003-11-14 12:53:18 EST
This works fine here.  Please trying writing the floppy on a different
machine as the "crc error" says that it almost *has* to be a media or
drive problem.

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