Bug 170222
Summary: | First boot after upgrade fails when reading physical volumes | ||
---|---|---|---|
Product: | [Fedora] Fedora | Reporter: | petri.poyhonen |
Component: | kernel | Assignee: | Kernel Maintainer List <kernel-maint> |
Status: | CLOSED NOTABUG | QA Contact: | Brian Brock <bbrock> |
Severity: | high | Docs Contact: | |
Priority: | medium | ||
Version: | 4 | CC: | wtogami |
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: | 2005-10-29 16:33:11 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: |
Description
petri.poyhonen
2005-10-09 11:45:48 UTC
After booting with the rescue cd: "fsck /dev/hda" reports: WARNING: could not open /etc/fstab: no such file Could not find ext2 superblock, trying backup blocks ... fsck.ext2: Bad magic number in super-block while trying to open /dev/hda "e2fsck -b 8193 /dev/hda" reports: e2fsck 1.37 Bad magic number in super-block while trying to open /dev/hda Superblock backup does not work ? Upgrade from FC3 has corrupted the disk ? After this message is delivered Reading all physcial volumes. This may take a while ... ... the system apparently is confused by the cd-rom drive. error messages complaint that hdc device is not ready. cd-rom is the master device in the second IDE bus. system boots without problems, if cd-rom drive has a disk inserted, but hangs (for about 20 minutes), if the drive does not have a disk inserted when booting. is this a bug ? automount of cd-roms seems to work fine, after the system has successfully booted. This still looks like a bug. While "reading physical voumes", system is somehow stuck with the cd-rom drive. The indicator in the drive is blinking and it sounds like it would constantly try to wind the drive. After about 1 minute of this (and this is exceltional delay, according to my previous in how red hast boots) we get a message indicating that hdc drive is not ready for command. From that point the boot progresses normally. This is the behavior, if I have a disk inserted in the drive. In the absence of a disk, this leads to at least 20 min of hang with various error messages, and then eventually the boot continues. Changed the cd-rom drive again. Now the system boots as I would expect. Now looks lime hardware incompatibility, as this cd-rom worked fine with FC 3 (and a windows system before that). Not a bug. |