Bug 110046
| Summary: | Bootdisk.img diskette can't boot | ||
|---|---|---|---|
| Product: | [Fedora] Fedora | Reporter: | Steve Bourland <steve_bourland> |
| Component: | anaconda | Assignee: | Jeremy Katz <katzj> |
| Status: | CLOSED NOTABUG | QA Contact: | Mike McLean <mikem> |
| Severity: | medium | Docs Contact: | |
| Priority: | medium | ||
| Version: | 1 | ||
| Target Milestone: | --- | ||
| Target Release: | --- | ||
| Hardware: | i386 | ||
| OS: | Linux | ||
| Whiteboard: | |||
| Fixed In Version: | Doc Type: | Bug Fix | |
| Doc Text: | Story Points: | --- | |
| Clone Of: | Environment: | ||
| Last Closed: | 2003-11-14 17:53:18 UTC | Type: | --- |
| Regression: | --- | Mount Type: | --- |
| Documentation: | --- | CRM: | |
| Verified Versions: | Category: | --- | |
| oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | |
| Cloudforms Team: | --- | Target Upstream Version: | |
| Embargoed: | |||
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 pulled. 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. |
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): severn-i386-disc1.iso How reproducible: Always Steps to Reproduce: 1.Generate installation diskette as indicated above 2.Attempt to boot computer using said diskette 3. 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.