Bug 240708
Summary: | FC6 is eating my hard drives | ||||||
---|---|---|---|---|---|---|---|
Product: | [Fedora] Fedora | Reporter: | Joseph A. Farmer <jfarmer99> | ||||
Component: | kernel | Assignee: | Kernel Maintainer List <kernel-maint> | ||||
Status: | CLOSED CURRENTRELEASE | QA Contact: | Brian Brock <bbrock> | ||||
Severity: | medium | Docs Contact: | |||||
Priority: | medium | ||||||
Version: | 6 | ||||||
Target Milestone: | --- | ||||||
Target Release: | --- | ||||||
Hardware: | i686 | ||||||
OS: | Linux | ||||||
Whiteboard: | |||||||
Fixed In Version: | 7 | Doc Type: | Bug Fix | ||||
Doc Text: | Story Points: | --- | |||||
Clone Of: | Environment: | ||||||
Last Closed: | 2007-11-10 19:05:12 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: | |||||||
Attachments: |
|
Description
Joseph A. Farmer
2007-05-21 00:34:14 UTC
Created attachment 155063 [details]
Screenshot of drive doom.
Ok, I dug into this deeper and it just got stranger on me as I went. The first problem was a stale mtab was confusing the system. That wasn't the real problem though. When the machine booted it failed on the boot screen as that screenshot showed. Running fsck on /dev/hdb1 and /dev/hdc1 returned "bad superblock, not ext3" on both. I ran smartctl and it claimed both drives were fine. I then ran fdisk and both partitions looked fine. Next up was fsck again and it persisted with the bad superblock thing. Running e2fsck direct with -p returned "drives clean, x number of files" so e2fsck was reading them fine while fsck on its own wasn't. I tried to edit fstab to delete the references to them but the root partition was mounted readonly and umount didn't help there. Booting the FC6 disk one resulted in hangs on the "loading ata_piix" screen (as happened originally on all 3 machines). I tracked down an FC5 test 3 CD and booted that into rescue mode and deleted the references. That is where it sits now. With a twist. If I put a reference to the drives into fstab it fails to boot with the "no superblock, not ext3" screen. If I run e2fsck it reports the drives are fine. If I wait until after boot and just mount manually: mount /dev/hdb1 /mnt/300 mount /dev/hdc1 /mnt/250 both drives mount fine. All files are there. It just won't boot with mount instructions in fstab. Odd and frustrating. Why fsck reports that the disks aren't ext3, while e2fsck -p has no issues, is a mystery and a pretty serious bug in fsck. I was about ready to reformat the drives before I discovered the e2fsck -p solution. e2fsck had a -v (verbose) option that is anything but and that's a bug also - the drive takes a long time to check and no text is reported until that completes so what part of that is "verbose" is not clear. So consider it a bug against fsck. Also one against stale mtab files. Current mtab: /dev/hda1 / ext3 rw 0 0 proc /proc proc rw 0 0 sysfs /sys sysfs rw 0 0 devpts /dev/pts devpts rw,gid=5,mode=620 0 0 tmpfs /dev/shm tmpfs rw 0 0 none /proc/sys/fs/binfmt_misc binfmt_misc rw 0 0 sunrpc /var/lib/nfs/rpc_pipefs rpc_pipefs rw 0 0 nfsd /proc/fs/nfsd nfsd rw 0 0 /dev/hdb1 /mnt/300 ext3 rw 0 0 /dev/hdc1 /mnt/250 ext3 rw 0 0 Note both drives are mounted ext3. I mounted them manually as stated. Please post contents of /etc/fstab Booting a new Fedora 7 CD and selecting "install" instead of upgrade cleared up the issue. Machine operates as expected now. fsck is probably still messed up. |