From: Phil Turmel <philip@turmel.org>
To: Dave Gomboc <dave_gomboc@acm.org>
Cc: linux-raid@vger.kernel.org
Subject: Re: raid10 recovery assistance requested
Date: Mon, 23 Sep 2013 08:32:18 -0400 [thread overview]
Message-ID: <524034D2.4010407@turmel.org> (raw)
In-Reply-To: <CA+dwz-2CMaoquRso8d=FZ1X5cEWE0vz7ceR6zhwzR2xM=1FM9A@mail.gmail.com>
Good morning Dave,
On 09/23/2013 12:55 AM, Dave Gomboc wrote:
[trim /]
Good news.
> [Actually, I mounted these rw first, then realized that I shouldn't
> have, unmounted them, and re-mounted them read-only.]
>
> root@sysresccd /mnt % mount -o ro -t ext3 /dev/mapper/teramooch-root /mnt/root
> root@sysresccd /mnt % mount -o ro -t ext3 /dev/mapper/teramooch-home /mnt/home
> root@sysresccd /mnt % mount -o ro -t ext3 /dev/mapper/teramooch-tmp /mnt/tmp
> root@sysresccd /mnt % mount -o ro -t ext3 /dev/mapper/teramooch-usr /mnt/usr
> root@sysresccd /mnt % mount -o ro -t ext3 /dev/mapper/teramooch-var /mnt/var
> root@sysresccd /mnt % mount -o ro -t ext3 /dev/mapper/teramooch-opt /mnt/opt
>
> These mount attempts returned without error, and ls within the
> directories is possible.
>
> However, the large, important one doesn't mount:
>
> root@sysresccd /mnt % mount -o ro -t ext3 /dev/mapper/teramooch-srv /mnt/srv
> mount: wrong fs type, bad option, bad superblock on /dev/mapper/teramooch-srv,
> missing codepage or helper program, or other error
> In some cases useful info is found in syslog - try
> dmesg | tail or so
>
> root@sysresccd /mnt % mount -o ro /dev/mapper/teramooch-srv /mnt/srv
> NTFS signature is missing.
> Failed to mount '/dev/mapper/teramooch-srv': Invalid argument
> The device '/dev/mapper/teramooch-srv' doesn't seem to have a valid NTFS.
> Maybe the wrong device is used? Or the whole disk instead of a
> partition (e.g. /dev/sda, not /dev/sda1)? Or the other way around?
>
> 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.
Phil
next prev parent reply other threads:[~2013-09-23 12:32 UTC|newest]
Thread overview: 25+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-09-16 3:30 raid10 recovery assistance requested Dave Gomboc
2013-09-19 3:20 ` Dave Gomboc
2013-09-19 4:29 ` Stan Hoeppner
2013-09-20 5:29 ` Dave Gomboc
2013-09-22 17:15 ` Dave Gomboc
2013-09-22 21:52 ` Phil Turmel
2013-09-22 22:45 ` Dave Gomboc
2013-09-22 23:04 ` Dave Gomboc
2013-09-22 23:25 ` Phil Turmel
[not found] ` <CA+dwz-0eskPSQ44v0vgwfjwRpTbQaokQ3Q258Em1W2eRi1SO4w@mail.gmail.com>
2013-09-23 2:54 ` Phil Turmel
2013-09-23 3:19 ` Dave Gomboc
2013-09-23 3:27 ` Phil Turmel
2013-09-23 3:34 ` Dave Gomboc
2013-09-23 3:51 ` Phil Turmel
2013-09-23 4:04 ` Dave Gomboc
2013-09-23 4:12 ` Phil Turmel
2013-09-23 4:55 ` Dave Gomboc
2013-09-23 5:07 ` Dave Gomboc
2013-09-23 5:19 ` Adam Goryachev
2013-09-23 12:32 ` Phil Turmel [this message]
2013-09-23 12:57 ` Dave Gomboc
2013-09-24 0:29 ` Adam Goryachev
2013-09-24 5:55 ` Dave Gomboc
2013-09-28 15:47 ` Dave Gomboc
2013-09-28 16:01 ` Phil Turmel
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=524034D2.4010407@turmel.org \
--to=philip@turmel.org \
--cc=dave_gomboc@acm.org \
--cc=linux-raid@vger.kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).