From: Mathias Mueller <raidfail@gmx.de>
To: Phil Turmel <philip@turmel.org>
Cc: Linux raid <linux-raid@vger.kernel.org>,
linux-raid-owner@vger.kernel.org
Subject: Re: broken raid level 5 array caused by user error
Date: Wed, 11 Nov 2015 00:47:39 +0100 [thread overview]
Message-ID: <ceee2de5aba3ca77efc1146e19896b90@pingofdeath.de> (raw)
In-Reply-To: <56426499.8000205@turmel.org>
Hi Phil
> You're not providing enough information. Show the new vs. old
> name/serial combinations, then show the --create and fsck
> command/output, one by one.
sorry, here you go:
sdb -> sde Serial Number: JK1170YBHYV6MD
sdc -> sdf Serial Number: JK1100YAG64A1T
sdd -> sdg Serial Number: JK1121YAG7YDLS
sde -> sdh Serial Number: ML0220F30PZUVD
> We know the possible order combinations:
> sdc1 sdb1 sdd1 sde1
> sdc1 sdd1 sdb1 sde1
> sde1 sdb1 sdd1 sdc1
> sde1 sdd1 sdb1 sdc1
so I used this combinations:
sdf1 sde1 sdg1 sdh1
sdf1 sdg1 sde1 sdh1
sdh1 sde1 sdg1 sdf1
sdh1 sdg1 sde1 sdf1
> For now, use data offset 2048 for all of them.
output of all eight combinations:
mdadm --create --assume-clean -l5 -n4 --chunk=64 --data-offset=2048
--metadata=1.2 /dev/md0 /dev/sdf1 /dev/sde1 /dev/sdg1 /dev/sdh1
mdadm: /dev/sdf1 appears to contain an ext2fs file system
size=1953513560K mtime=Thu Jan 1 01:00:00 1970
mdadm: /dev/sdf1 appears to be part of a raid array:
level=raid5 devices=4 ctime=Tue Nov 10 22:24:54 2015
mdadm: /dev/sde1 appears to contain an ext2fs file system
size=1953513560K mtime=Thu Jan 1 01:00:00 1970
mdadm: /dev/sde1 appears to be part of a raid array:
level=raid5 devices=4 ctime=Tue Nov 10 22:24:54 2015
mdadm: /dev/sdg1 appears to contain an ext2fs file system
size=1953512000K mtime=Wed May 11 17:58:03 2011
mdadm: /dev/sdg1 appears to be part of a raid array:
level=raid5 devices=4 ctime=Tue Nov 10 22:24:54 2015
mdadm: /dev/sdh1 appears to contain an ext2fs file system
size=1953513560K mtime=Mon Apr 8 11:04:10 2013
mdadm: /dev/sdh1 appears to be part of a raid array:
level=raid5 devices=4 ctime=Tue Nov 10 22:24:54 2015
Continue creating array? y
mdadm: array /dev/md0 started.
fsck -n /dev/md0
fsck from util-linux 2.23.2
e2fsck 1.42.9 (28-Dec-2013)
ext2fs_open2: Bad magic number in super-block
fsck.ext2: Superblock invalid, trying backup blocks...
fsck.ext2: Bad magic number in super-block while trying to open /dev/md0
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>
=======================
mdadm --create --assume-clean -l5 -n4 --chunk=512 --data-offset=2048
--metadata=1.2 /dev/md0 /dev/sdf1 /dev/sde1 /dev/sdg1 /dev/sdh1
mdadm: /dev/sdf1 appears to contain an ext2fs file system
size=1953513560K mtime=Thu Jan 1 01:00:00 1970
mdadm: /dev/sdf1 appears to be part of a raid array:
level=raid5 devices=4 ctime=Wed Nov 11 00:29:57 2015
mdadm: /dev/sde1 appears to contain an ext2fs file system
size=1953513560K mtime=Thu Jan 1 01:00:00 1970
mdadm: /dev/sde1 appears to be part of a raid array:
level=raid5 devices=4 ctime=Wed Nov 11 00:29:57 2015
mdadm: /dev/sdg1 appears to contain an ext2fs file system
size=1953512000K mtime=Wed May 11 17:58:03 2011
mdadm: /dev/sdg1 appears to be part of a raid array:
level=raid5 devices=4 ctime=Wed Nov 11 00:29:57 2015
mdadm: /dev/sdh1 appears to contain an ext2fs file system
size=1953513560K mtime=Mon Apr 8 11:04:10 2013
mdadm: /dev/sdh1 appears to be part of a raid array:
level=raid5 devices=4 ctime=Wed Nov 11 00:29:57 2015
Continue creating array? y
mdadm: array /dev/md0 started.
fsck -n /dev/md0
fsck from util-linux 2.23.2
e2fsck 1.42.9 (28-Dec-2013)
ext2fs_open2: Bad magic number in super-block
fsck.ext2: Superblock invalid, trying backup blocks...
fsck.ext2: Bad magic number in super-block while trying to open /dev/md0
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>
================================
================================
mdadm --create --assume-clean -l5 -n4 --chunk=64 --data-offset=2048
--metadata=1.2 /dev/md0 /dev/sdf1 /dev/sdg1 /dev/sde1 /dev/sdh1
mdadm: /dev/sdf1 appears to contain an ext2fs file system
size=1953513560K mtime=Thu Jan 1 01:00:00 1970
mdadm: /dev/sdf1 appears to be part of a raid array:
level=raid5 devices=4 ctime=Wed Nov 11 00:31:56 2015
mdadm: /dev/sdg1 appears to contain an ext2fs file system
size=1953512000K mtime=Wed May 11 17:58:03 2011
mdadm: /dev/sdg1 appears to be part of a raid array:
level=raid5 devices=4 ctime=Wed Nov 11 00:31:56 2015
mdadm: /dev/sde1 appears to contain an ext2fs file system
size=1953513560K mtime=Thu Jan 1 01:00:00 1970
mdadm: /dev/sde1 appears to be part of a raid array:
level=raid5 devices=4 ctime=Wed Nov 11 00:31:56 2015
mdadm: /dev/sdh1 appears to contain an ext2fs file system
size=1953513560K mtime=Mon Apr 8 11:04:10 2013
mdadm: /dev/sdh1 appears to be part of a raid array:
level=raid5 devices=4 ctime=Wed Nov 11 00:31:56 2015
Continue creating array? y
mdadm: array /dev/md0 started.
fsck -n /dev/md0
fsck from util-linux 2.23.2
e2fsck 1.42.9 (28-Dec-2013)
ext2fs_open2: Bad magic number in super-block
fsck.ext2: Superblock invalid, trying backup blocks...
fsck.ext2: Bad magic number in super-block while trying to open /dev/md0
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>
=====================
mdadm --create --assume-clean -l5 -n4 --chunk=512 --data-offset=2048
--metadata=1.2 /dev/md0 /dev/sdf1 /dev/sdg1 /dev/sde1 /dev/sdh1
mdadm: /dev/sdf1 appears to contain an ext2fs file system
size=1953513560K mtime=Thu Jan 1 01:00:00 1970
mdadm: /dev/sdf1 appears to be part of a raid array:
level=raid5 devices=4 ctime=Wed Nov 11 00:34:05 2015
mdadm: /dev/sdg1 appears to contain an ext2fs file system
size=1953512000K mtime=Wed May 11 17:58:03 2011
mdadm: /dev/sdg1 appears to be part of a raid array:
level=raid5 devices=4 ctime=Wed Nov 11 00:34:05 2015
mdadm: /dev/sde1 appears to contain an ext2fs file system
size=1953513560K mtime=Thu Jan 1 01:00:00 1970
mdadm: /dev/sde1 appears to be part of a raid array:
level=raid5 devices=4 ctime=Wed Nov 11 00:34:05 2015
mdadm: /dev/sdh1 appears to contain an ext2fs file system
size=1953513560K mtime=Mon Apr 8 11:04:10 2013
mdadm: /dev/sdh1 appears to be part of a raid array:
level=raid5 devices=4 ctime=Wed Nov 11 00:34:05 2015
Continue creating array? y
mdadm: array /dev/md0 started.
fsck -n /dev/md0
fsck from util-linux 2.23.2
e2fsck 1.42.9 (28-Dec-2013)
ext2fs_open2: Bad magic number in super-block
fsck.ext2: Superblock invalid, trying backup blocks...
fsck.ext2: Bad magic number in super-block while trying to open /dev/md0
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>
=====================
=====================
mdadm --create --assume-clean -l5 -n4 --chunk=64 --data-offset=2048
--metadata=1.2 /dev/md0 /dev/sdh1 /dev/sde1 /dev/sdg1 /dev/sdf1
mdadm: /dev/sdh1 appears to contain an ext2fs file system
size=1953513560K mtime=Mon Apr 8 11:04:10 2013
mdadm: /dev/sdh1 appears to be part of a raid array:
level=raid5 devices=4 ctime=Wed Nov 11 00:37:01 2015
mdadm: /dev/sde1 appears to contain an ext2fs file system
size=1953513560K mtime=Thu Jan 1 01:00:00 1970
mdadm: /dev/sde1 appears to be part of a raid array:
level=raid5 devices=4 ctime=Wed Nov 11 00:37:01 2015
mdadm: /dev/sdg1 appears to contain an ext2fs file system
size=1953512000K mtime=Wed May 11 17:58:03 2011
mdadm: /dev/sdg1 appears to be part of a raid array:
level=raid5 devices=4 ctime=Wed Nov 11 00:37:01 2015
mdadm: /dev/sdf1 appears to contain an ext2fs file system
size=1953513560K mtime=Thu Jan 1 01:00:00 1970
mdadm: /dev/sdf1 appears to be part of a raid array:
level=raid5 devices=4 ctime=Wed Nov 11 00:37:01 2015
Continue creating array? y
mdadm: array /dev/md0 started.
fsck -n /dev/md0
fsck from util-linux 2.23.2
e2fsck 1.42.9 (28-Dec-2013)
ext2fs_open2: Bad magic number in super-block
fsck.ext2: Superblock invalid, trying backup blocks...
fsck.ext2: Bad magic number in super-block while trying to open /dev/md0
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>
=====================
mdadm --create --assume-clean -l5 -n4 --chunk=512 --data-offset=2048
--metadata=1.2 /dev/md0 /dev/sdh1 /dev/sde1 /dev/sdg1 /dev/sdf1
mdadm: /dev/sdh1 appears to contain an ext2fs file system
size=1953513560K mtime=Mon Apr 8 11:04:10 2013
mdadm: /dev/sdh1 appears to be part of a raid array:
level=raid5 devices=4 ctime=Wed Nov 11 00:34:59 2015
mdadm: /dev/sde1 appears to contain an ext2fs file system
size=1953513560K mtime=Thu Jan 1 01:00:00 1970
mdadm: /dev/sde1 appears to be part of a raid array:
level=raid5 devices=4 ctime=Wed Nov 11 00:34:59 2015
mdadm: /dev/sdg1 appears to contain an ext2fs file system
size=1953512000K mtime=Wed May 11 17:58:03 2011
mdadm: /dev/sdg1 appears to be part of a raid array:
level=raid5 devices=4 ctime=Wed Nov 11 00:34:59 2015
mdadm: /dev/sdf1 appears to contain an ext2fs file system
size=1953513560K mtime=Thu Jan 1 01:00:00 1970
mdadm: /dev/sdf1 appears to be part of a raid array:
level=raid5 devices=4 ctime=Wed Nov 11 00:34:59 2015
Continue creating array? y
mdadm: array /dev/md0 started.
fsck -n /dev/md0
fsck from util-linux 2.23.2
e2fsck 1.42.9 (28-Dec-2013)
ext2fs_open2: Bad magic number in super-block
fsck.ext2: Superblock invalid, trying backup blocks...
fsck.ext2: Bad magic number in super-block while trying to open /dev/md0
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>
=====================
=====================
mdadm --create --assume-clean -l5 -n4 --chunk=64 --data-offset=2048
--metadata=1.2 /dev/md0 /dev/sdh1 /dev/sdg1 /dev/sde1 /dev/sdf1
mdadm: /dev/sdh1 appears to contain an ext2fs file system
size=1953513560K mtime=Mon Apr 8 11:04:10 2013
mdadm: /dev/sdh1 appears to be part of a raid array:
level=raid5 devices=4 ctime=Wed Nov 11 00:38:17 2015
mdadm: /dev/sdg1 appears to contain an ext2fs file system
size=1953512000K mtime=Wed May 11 17:58:03 2011
mdadm: /dev/sdg1 appears to be part of a raid array:
level=raid5 devices=4 ctime=Wed Nov 11 00:38:17 2015
mdadm: /dev/sde1 appears to contain an ext2fs file system
size=1953513560K mtime=Thu Jan 1 01:00:00 1970
mdadm: /dev/sde1 appears to be part of a raid array:
level=raid5 devices=4 ctime=Wed Nov 11 00:38:17 2015
mdadm: /dev/sdf1 appears to contain an ext2fs file system
size=1953513560K mtime=Thu Jan 1 01:00:00 1970
mdadm: /dev/sdf1 appears to be part of a raid array:
level=raid5 devices=4 ctime=Wed Nov 11 00:38:17 2015
Continue creating array? y
mdadm: array /dev/md0 started.
fsck -n /dev/md0
fsck from util-linux 2.23.2
e2fsck 1.42.9 (28-Dec-2013)
ext2fs_open2: Bad magic number in super-block
fsck.ext2: Superblock invalid, trying backup blocks...
fsck.ext2: Bad magic number in super-block while trying to open /dev/md0
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>
=====================
mdadm --create --assume-clean -l5 -n4 --chunk=512 --data-offset=2048
--metadata=1.2 /dev/md0 /dev/sdh1 /dev/sdg1 /dev/sde1 /dev/sdf1
mdadm: /dev/sdh1 appears to contain an ext2fs file system
size=1953513560K mtime=Mon Apr 8 11:04:10 2013
mdadm: /dev/sdh1 appears to be part of a raid array:
level=raid5 devices=4 ctime=Wed Nov 11 00:39:16 2015
mdadm: /dev/sdg1 appears to contain an ext2fs file system
size=1953512000K mtime=Wed May 11 17:58:03 2011
mdadm: /dev/sdg1 appears to be part of a raid array:
level=raid5 devices=4 ctime=Wed Nov 11 00:39:16 2015
mdadm: /dev/sde1 appears to contain an ext2fs file system
size=1953513560K mtime=Thu Jan 1 01:00:00 1970
mdadm: /dev/sde1 appears to be part of a raid array:
level=raid5 devices=4 ctime=Wed Nov 11 00:39:16 2015
mdadm: /dev/sdf1 appears to contain an ext2fs file system
size=1953513560K mtime=Thu Jan 1 01:00:00 1970
mdadm: /dev/sdf1 appears to be part of a raid array:
level=raid5 devices=4 ctime=Wed Nov 11 00:39:16 2015
Continue creating array? y
mdadm: array /dev/md0 started.
fsck -n /dev/md0
fsck from util-linux 2.23.2
e2fsck 1.42.9 (28-Dec-2013)
ext2fs_open2: Bad magic number in super-block
fsck.ext2: Superblock invalid, trying backup blocks...
fsck.ext2: Bad magic number in super-block while trying to open /dev/md0
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>
Thanks and best regards!
Mathias
next prev parent reply other threads:[~2015-11-10 23:47 UTC|newest]
Thread overview: 31+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-11-10 21:33 broken raid level 5 array caused by user error Mathias Mueller
2015-11-10 21:41 ` Phil Turmel
2015-11-10 23:47 ` Mathias Mueller [this message]
2015-11-10 23:59 ` Phil Turmel
[not found] ` <b0cdddd4394bbc1356980bb61ac199c3@pingofdeath.de>
2015-11-11 1:00 ` Phil Turmel
2015-11-11 17:53 ` Mathias Mueller
2016-01-18 15:33 ` Mathias Mueller
2016-01-18 19:09 ` Phil Turmel
2016-01-19 14:35 ` Mathias Mueller
2016-01-19 17:51 ` Phil Turmel
2016-01-19 19:37 ` Phil Turmel
2016-01-20 9:04 ` Mathias Mueller
2016-01-22 9:30 ` Mathias Mueller
2016-01-22 17:16 ` Phil Turmel
2016-01-22 17:39 ` Mathias Mueller
2016-01-22 19:13 ` Phil Turmel
2016-01-25 10:02 ` Mathias Mueller
2015-11-11 1:03 ` Phil Turmel
2015-11-11 1:29 ` Mathias Mueller
-- strict thread matches above, loose matches on Subject: below --
2015-11-09 11:27 Mathias Mueller
2015-11-09 11:56 ` Mikael Abrahamsson
2015-11-09 13:50 ` Phil Turmel
[not found] ` <07de4cd96f39ecb6154794d072ca12e7@pingofdeath.de>
[not found] ` <5640B8AD.3030800@turmel.org>
2015-11-09 15:41 ` Mathias Mueller
[not found] ` <d764bf541381927fa4183c9266fb3f5a@pingofdeath.de>
[not found] ` <5640C38B.4060503@turmel.org>
[not found] ` <a3a91665c4b7cdd70dacc7d8815cc365@pingofdeath.de>
2015-11-09 21:13 ` Phil Turmel
2015-11-10 8:37 ` Mathias Mueller
2015-11-10 13:55 ` Phil Turmel
2015-11-10 14:55 ` Mathias Mueller
2015-11-10 15:20 ` Mathias Mueller
2015-11-10 15:28 ` Phil Turmel
2015-11-10 21:02 ` Mathias Mueller
2015-11-10 21:11 ` 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=ceee2de5aba3ca77efc1146e19896b90@pingofdeath.de \
--to=raidfail@gmx.de \
--cc=linux-raid-owner@vger.kernel.org \
--cc=linux-raid@vger.kernel.org \
--cc=philip@turmel.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.