Skip to contentSkip to conversation

EXT3-fs: unable to read superblock

linux-lvm Jean Chiappini 2 participants 4 messages Dec 11, 2006 – Dec 14, 2006

lore
Share & tools
lore
#0 lore raw

Hello all,

I have a server production with centos 4 with kernel 2.6.9-42 and lvm2-2.02.06 installed. All was working find, but today the server crashed. When I would reboot my server, I saw in the log that the lvm partiton wouldn't mount. This is the error -> kernel: EXT3-fs: unable to read superblock.

If I try to mount manually the partition, these errors appears :

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 alterate superblock:

I don't understand these errors, my partition if formated in ext3...

Someone could help me please ???

Regards

Jean

#1 lore raw
Quoted 7 lines · Jean Chiappini

Hello all,

I have a server production with centos 4 with kernel 2.6.9-42 and lvm2-2.02.06 installed. All was working find, but today the server crashed. When I would reboot my server, I saw in the log that the lvm partiton wouldn't mount. This is the error -> kernel: EXT3-fs: unable to read superblock.

I had this problem recently with a few systems. Try booting to single-user mode, and then do the following command:

tune2fs -j DEVICE-FILE-WITH-PROBLEM

This will create a new journal on the filesystem. I haven't tracked down why the journal disappears yet, but it seems to, and then the system (of course) won't mount it as ext3.

Signature · 2 lines
Evan Cofsky, The Architect <[email protected]>
http://www.theunixman.com/
#2 lore raw

Thank you for your answer, but when I do this command, this error appear :
tune2fs: Argument invalide while trying to open /dev/mapper/VolGroup00-mysqldata Couldn't find valid filesystem superblock.

The only solution I see now is to format this partition...

Quoted 24 lines · Evan Cofsky
Quoted 4 lines · Jean Chiappini

Hello all,

I have a server production with centos 4 with kernel 2.6.9-42 and lvm2-2.02.06 installed. All was working find, but today the server crashed. When I would reboot my server, I saw in the log that the lvm partiton wouldn't mount. This is the error -> kernel: EXT3-fs: unable to read superblock.

I had this problem recently with a few systems. Try booting to single-user mode, and then do the following command:

tune2fs -j DEVICE-FILE-WITH-PROBLEM

This will create a new journal on the filesystem. I haven't tracked down why the journal disappears yet, but it seems to, and then the system (of course) won't mount it as ext3.

------------------------------------------------------------------------

_______________________________________________
linux-lvm mailing list
[email protected]
https://www.redhat.com/mailman/listinfo/linux-lvm
read the LVM HOW-TO at http://tldp.org/HOWTO/LVM-HOWTO/

#3 lore raw
Quoted 4 lines · Jean Chiappini

Thank you for your answer, but when I do this command, this error appear :
tune2fs: Argument invalide while trying to open /dev/mapper/VolGroup00-mysqldata
Couldn't find valid filesystem superblock.

Have you tried e2fsck on it yet?

Signature · 2 lines
Evan Cofsky, The Architect <[email protected]>
http://www.theunixman.com/