> Good morning Dave,
Good morning!
>> It should be ext3, not NTFS.
>
> Since you are sure it is ext3, then you should use "fsck.ext3 -y" to fix
> it. I usually try that operation first with "-n" instead of "-y", but
> your mount attempts show that the "-n" would be superfluous. If fsck
> scrambles that volume worse, then you'll have to recopy from your
> backups and redo the forced assembly. Or try with the other two disks.
I'm pretty darn sure it's ext3. I guess there is a small chance that
all of them were upgraded to ext4 from ext3.
I saw Adam's post before yours, so I did first try various
command-lines using -n:
fsck.ext3 -n /dev/mapper/teramooch-srv
e2fsck 1.42.7 (21-Jan-2013)
ext2fs_open2: Bad magic number in super-block
fsck.ext3: Superblock invalid, trying backup blocks...
fsck.ext3: Bad magic number in super-block while trying to open
/dev/mapper/teramooch-srv
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>
[man fsck.ext3 mentions a backup superblock possibly being located at
8193, 16384, or 32768].
root@sysresccd /root % fsck.ext3 -n -b 8193 /dev/mapper/teramooch-srv
e2fsck 1.42.7 (21-Jan-2013)
fsck.ext3: Bad magic number in super-block while trying to open
/dev/mapper/teramooch-srv
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>
root@sysresccd /root % fsck.ext3 -n -b 16384 /dev/mapper/teramooch-srv
e2fsck 1.42.7 (21-Jan-2013)
fsck.ext3: Bad magic number in super-block while trying to open
/dev/mapper/teramooch-srv
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>
root@sysresccd /root % fsck.ext3 -n -b 32768 /dev/mapper/teramooch-srv
e2fsck 1.42.7 (21-Jan-2013)
fsck.ext3: Bad magic number in super-block while trying to open
/dev/mapper/teramooch-srv
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>
[The same commands, except using fsck.ext4 instead of fsck.ext3, also
gave the same generic output. Finally, I tried the -y:]
root@sysresccd /root % fsck.ext3 -y /dev/mapper/teramooch-srv
e2fsck 1.42.7 (21-Jan-2013)
ext2fs_open2: Bad magic number in super-block
fsck.ext3: Superblock invalid, trying backup blocks...
fsck.ext3: Bad magic number in super-block while trying to open
/dev/mapper/teramooch-srv
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>
The above output was also returned instantaneously, despite the use of -y.
I have to head to work, but I would be happy to make further attempts
when I'm home again.
Dave
--
To unsubscribe from this list: send the line "unsubscribe linux-raid" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at http://vger.kernel.org/majordomo-info.html
