Bug 144851
Summary: | Unable to mount additional drives during bootup, but manually does just fine. | ||
---|---|---|---|
Product: | [Fedora] Fedora | Reporter: | Ivo Sarak <ivo> |
Component: | kernel | Assignee: | Dave Jones <davej> |
Status: | CLOSED ERRATA | QA Contact: | Brian Brock <bbrock> |
Severity: | high | Docs Contact: | |
Priority: | medium | ||
Version: | 3 | CC: | pfrields, wtogami |
Target Milestone: | --- | ||
Target Release: | --- | ||
Hardware: | athlon | ||
OS: | Linux | ||
Whiteboard: | |||
Fixed In Version: | Doc Type: | Bug Fix | |
Doc Text: | Story Points: | --- | |
Clone Of: | Environment: | ||
Last Closed: | 2005-02-13 04:21:29 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
Ivo Sarak
2005-01-11 22:44:32 UTC
Even the "fsck /dev/sda1" and "fsck /dev/sdb1" are not reporting anything as being wrong. The issue is not SATA related after all, all drives what were added after FC3 install complain the same error: "/dev/XXX The superblock could not be read or does not describe a correct ext2 filesystem. If the device is valid and really contains an ext2 filesystem (and not swap or ufs or something else), then the superblock is corrupt, and you might try sunning efsck with an alternate superblock: e2fsck -b 8193 <device> fsck.ext3: No such file or directory while trying to open /dev/XXX" After "yum install kernel" I got it working! Yum installed: kernel-2.6.10-1.741_FC3 |