Server Fault is a question and answer site for system and network administrators. Join them; it only takes a minute:

Sign up
Here's how it works:
  1. Anybody can ask a question
  2. Anybody can answer
  3. The best answers are voted up and rise to the top

I need to know if i can still mount the volume when i tell fsck "no" in that question.

i dont need to repair all the files in the volume, i just need recover one single file for this event. the volume got some big files that put fsck stuck for hours if i say "Yes". has 753108 multiply-claimed block(s), shared with 3 file(s):

The volume if over LVM and runs a EXT3 Filesistem.

share|improve this question
possible duplicate of Huge amounts of "multiply-claimed blocks" during fsck – Michael Hampton May 26 '13 at 1:11

Don't repair it. Mount it read only and get your file. When you're done, wipe the drive.

Since you have a superblock error, you can try to mount the filesystem using an alternate superblock. See

(if someone could edit in the instructions I would appreciate it. I'm on a phone.)

share|improve this answer
it told me the there was no superblock – Freaktor May 26 '13 at 0:32
the damage was done with a buggy hybrid sata raid controller – Freaktor May 26 '13 at 0:35
See my edit. You can mount read only using an alternate superblock. – longneck May 26 '13 at 3:44

You should be able to mount the filesystem even though it has multiply-claimed blocks. Do this on an image (I assume you're already working from a bitwise image of the partition, but it never hurts to check).

Multiply claimed blocks will cause corruption for sure if you try to write to them, but you should be able to read from the file you want if this is the only problem (and hopefully fsck can make that so).

share|improve this answer

Your Answer


By posting your answer, you agree to the privacy policy and terms of service.

Not the answer you're looking for? Browse other questions tagged or ask your own question.