From: Nicholas Ipsen <NCLI@ncli-design.com>
To: linux-raid <linux-raid@vger.kernel.org>
Subject: Re: Trouble adding disk to degraded array
Date: Sat, 12 Jan 2013 00:01:09 +0000 [thread overview]
Message-ID: <CAJ=Lqma76UUcg154ChSW1e48ZxPCf8dG7WMNH6PpvQGYF_v7vw@mail.gmail.com> (raw)
In-Reply-To: <alpine.DEB.2.00.1301111505110.12098@uplift.swm.pp.se>
Yikes, I may really have stepped in it with that filesystem check... I
first mounted the filesystem, and everything looked fine after
replacing sdc1 with sdd1. I then
ran fsck -f /dev/md0, and it started to report problems after 10-15
minutes. Here's one of them, they all said the same except for the
block number:
"Error reading block 5767176 (Attempt to read block from filesystem
resulted in short read) while reading inode and block bitmaps. Ignore
error<y>?"
I just kept pressing y and then approving a forced rewrite, as I
thought it was just a few blocks, but after approving 40 or so
rewrites, I got cold feet, cancelled fsck, and tried to remount md0
through nautilus. But it wouldn't. Instead, I get this message:
Error mounting /dev/md0 at
/media/ubuntu/be265e78-0c46-41fb-96ba-fda269e74a60: Command-line
`mount -t "ext4" -o "uhelper=udisks2,nodev,nosuid" "/dev/md0"
"/media/ubuntu/be265e78-0c46-41fb-96ba-fda269e74a60"' exited with
non-zero exit status 32: mount: wrong fs type, bad option, bad
superblock on /dev/md0,
missing codepage or helper program, or other error
In some cases useful info is found in syslog - try
dmesg | tail or so
Naturally, I ran dmesg | tail, and got this;
[104349.032352] EXT4-fs (md0): can't read group descriptor 378
[104350.997625] EXT4-fs (md0): can't read group descriptor 250
[104739.002433] EXT4-fs (md0): can't read group descriptor 250
[104780.612995] EXT4-fs (md0): can't read group descriptor 250
I then stopped the array, and restarted it, which gave me this message:
mdadm: clearing FAULTY flag for device 1 in /dev/md0 for /dev/sdb1
Note that this is not the device that was giving me trouble before,
nor is it the on I replaced it with.
What have I done wrong here?
Nicholas Ipsen
next prev parent reply other threads:[~2013-01-12 0:01 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <CAJ=LqmbYG8H45M196ZuRcDMu9Ucz0t_pQenQbZtMKM9AhSqrpQ@mail.gmail.com>
2013-01-09 17:21 ` Trouble adding disk to degraded array Nicholas Ipsen(Sephiroth_VII)
2013-01-09 17:55 ` Phil Turmel
2013-01-09 21:18 ` Nicholas Ipsen(Sephiroth_VII)
2013-01-09 21:54 ` Phil Turmel
2013-01-09 22:33 ` Tudor Holton
2013-01-09 23:47 ` Nicholas Ipsen
2013-01-11 13:14 ` Nicholas Ipsen
2013-01-11 14:07 ` Mikael Abrahamsson
2013-01-12 0:01 ` Nicholas Ipsen [this message]
2013-01-12 0:24 ` 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='CAJ=Lqma76UUcg154ChSW1e48ZxPCf8dG7WMNH6PpvQGYF_v7vw@mail.gmail.com' \
--to=ncli@ncli-design.com \
--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).