Re: Failure to Mount
From: CWO4 Dave Mann (misterfixit_at_loveable.com)
Date: 08/30/05
- Next message: CWO4 Dave Mann: "Re: Failure to Mount"
- Previous message: ajtiM: "Re: Linux. It's all about LIES AND DENIAL."
- In reply to: Dances With Crows: "Re: Failure to Mount"
- Next in thread: Dances With Crows: "Re: Failure to Mount"
- Reply: Dances With Crows: "Re: Failure to Mount"
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
Date: Tue, 30 Aug 2005 11:51:21 -0500
On Tue, 30 Aug 2005 10:50:50 -0500, Dances With Crows wrote:
> On Tue, 30 Aug 2005 09:41:15 -0500, CWO4 Dave Mann staggered into the
> Black Sun and said:
>> /dev/VolGroup00/LogVol00 / ext3 defaults 1 1
>> /dev/VolGroup00/LogVol01 swap swap defaults 0 0
>> /dev/hdb1 /mnt/storage1 ext3 rw,user,auto 0 0
>> /dev/hdb2 /mnt/storage2 ext3 rw,user,auto 0 0
>> /dev/hdb3 /mnt/storage3 ext3 rw,user,auto 0 0
>>
>> When attempting to mount storage2, "wrong fs type, bad superblock, etc"
>> message appears.
>>
>> hda is 100GB with usual partitions
>
> ? Your fstab says different. Having only one / partition is certainly
> not usual. Most of the time, you want /home separate from / , and /usr
> and /var are typically separate as well. You also appear to be using
> LVM.
Sorry, I'm getting logical and primary confused. hda was set up by FC3
automatically when doing the initial install of FC to a new hda.
>> hdb is 200GB with 3 logical partitions
>
> fstab says that hdb has 3 primary partitions, not logical partitions. On
> the x86, "logical partition" typically refers to a partition within an
> extended partition. Logical partitions always have numbers >= 5. What
> does "fdisk -l /dev/hdb" say?
Here is my fdisk output:
Disk /dev/hdb: 160.0 GB, 160041885696 bytes
255 heads, 63 sectors/track, 19457 cylinders
Units = cylinders of 16065 * 512 = 8225280 bytes
Device Boot Start End Blocks Id System
/dev/hdb1 * 1 13 104391 83 Linux
/dev/hdb2 14 4111 32917185 8e Linux LVM
/dev/hdb3 4112 19457 123266745 83 Linux
> Anyway, the error points to a problem with the filesystem on hdb2, or
> maybe the filesystem was made without -j and is ext2 instead of 3, or
> possibly a bad device name if fstab isn't synced with the partition
> table on hdb. Check the partition table. If it reports 3 primary
> partitions of type 0x83, run "dumpe2fs /dev/hdb2 | head -n20" . If it
> doesn't display "has_journal" in the features line, it's ext2. tune2fs
> -j the filesystem or mount it as ext2. If it does have a journal, you
> need to e2fsck it. If fsck complains that it can't find the superblock,
> add "-b 32768" to use the first backup superblock.
I wonder if this is the problem. Long ago, I got some error messages
about the start and end blocks being off or duplicated or something but
those errors went away. Sorry I am so vague about it.
Anyway, here is the dump output:
dumpe2fs 1.36 (05-Feb-2005)
ext2fs_read_bb_inode: Invalid argument
Filesystem volume name: /
Last mounted on: <not available>
Filesystem UUID: f5d984c6-2818-4d5f-970f-5c4f4dac1b5b
Filesystem magic number: 0xEF53
Filesystem revision #: 1 (dynamic)
Filesystem features: has_journal ext_attr dir_index filetype sparse_super
Default mount options: (none)
Filesystem state: clean with errors
Errors behavior: Continue
Filesystem OS type: Linux
Inode count: 19283968
Block count: 38535918
Reserved block count: 1926795
Free blocks: 36189040
Free inodes: 18956525
First block: 0
Block size: 4096
Fragment size: 4096
Blocks per group: 32768
Fragments per group: 32768
It says clean with errors, so, I ran fsck:
[root@localhost sbin]# umount /dev/hdb1
[root@localhost sbin]# umount /dev/hdb2
umount: /dev/hdb2: not mounted
[root@localhost sbin]# umount /dev/hdb3
[root@localhost sbin]# ./fsck /dev/hdb
fsck 1.36 (05-Feb-2005)
e2fsck 1.36 (05-Feb-2005)
Couldn't find ext2 superblock, trying backup blocks...
fsck.ext2: Bad magic number in super-block while trying to open /dev/hdb
The superblock could not be read or does not describe a correct ext2
filesystem. If the device is valid and it really contains an ext2
filesystem (and not swap or ufs or something else), then the superblock
is corrupt, and you might try running e2fsck with an alternate superblock:
e2fsck -b 8193 <device>
Running fsck looking for the backup superblock:
[root@localhost sbin]# ./fsck -b 32768 /dev/hdb
fsck 1.36 (05-Feb-2005)
e2fsck 1.36 (05-Feb-2005)
fsck.ext2: Bad magic number in super-block while trying to open /dev/hdb
The superblock could not be read or does not describe a correct ext2
filesystem. If the device is valid and it really contains an ext2
filesystem (and not swap or ufs or something else), then the superblock
is corrupt, and you might try running e2fsck with an alternate superblock:
e2fsck -b 8193 <device>
Running tune1fs -j
[root@localhost sbin]# ./tune2fs -j /dev/hdb
tune2fs 1.36 (05-Feb-2005)
./tune2fs: Bad magic number in super-block while trying to open /dev/hdb
Couldn't find valid filesystem superblock
Running tune2fs -l
[root@localhost sbin]# ./tune2fs -l /dev/hdb
tune2fs 1.36 (05-Feb-2005)
./tune2fs: Bad magic number in super-block while trying to open /dev/hdb
Couldn't find valid filesystem superblock.[root@localhost sbin]# ./tune2fs
-l /dev/hdb tune2fs 1.36 (05-Feb-2005)
./tune2fs: No such file or directory while trying to open /dev/hdb
Couldn't find valid filesystem superblock.
Looks like I'm screwed.
I am sure the entire hdb is ext3.
Ideas? Recommendations?
TIA
Dave
- Next message: CWO4 Dave Mann: "Re: Failure to Mount"
- Previous message: ajtiM: "Re: Linux. It's all about LIES AND DENIAL."
- In reply to: Dances With Crows: "Re: Failure to Mount"
- Next in thread: Dances With Crows: "Re: Failure to Mount"
- Reply: Dances With Crows: "Re: Failure to Mount"
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
Relevant Pages
|
