From: NeilBrown <neilb@suse.de>
To: Phillip Susi <phillsusi@gmail.com>
Cc: Linux RAID <linux-raid@vger.kernel.org>
Subject: Re: Kernel says there is not a valid superblock, but there is
Date: Tue, 21 Oct 2014 08:09:37 +1100 [thread overview]
Message-ID: <20141021080937.69aaf214@notabene.brown> (raw)
In-Reply-To: <544525C7.7000803@gmail.com>
[-- Attachment #1: Type: text/plain, Size: 2361 bytes --]
On Mon, 20 Oct 2014 11:09:59 -0400 Phillip Susi <phillsusi@gmail.com> wrote:
> When trying to assemble, the kernel complains:
Which kernel?
uname -a
and may as well add
mdadm -V
as well.
NeilBrown
>
> md: md1 stopped.
> md: sda2 does not have a valid v1.2 superblock, not importing!
> md: md_import_device returned -22
> md: sdb2 does not have a valid v1.2 superblock, not importing!
> md: md_import_device returned -22
>
> Yet the superblock looks perfectly fine according to mdadm -E:
>
> /dev/sda2:
> Magic : a92b4efc
> Version : 1.2
> Feature Map : 0x0
> Array UUID : 34e89993:37821273:5498dc63:07233b2c
> Name : devserv2:1
> Creation Time : Mon Jun 16 11:24:00 2014
> Raid Level : raid1
> Raid Devices : 2
>
> Avail Dev Size : 3900907520 (1860.10 GiB 1997.26 GB)
> Array Size : 158334976 (151.00 GiB 162.14 GB)
> Used Dev Size : 316669952 (151.00 GiB 162.14 GB)
> Data Offset : 262144 sectors
> Super Offset : 8 sectors
> State : clean
> Device UUID : 40c38a87:88807f78:5bf71f34:4c9b2215
>
> Update Time : Mon Oct 20 09:56:25 2014
> Checksum : d2369656 - correct
> Events : 303
>
>
> Device Role : Active device 0
> Array State : AA ('A' == active, '.' == missing)
>
> /dev/sdb2:
> Magic : a92b4efc
> Version : 1.2
> Feature Map : 0x0
> Array UUID : 34e89993:37821273:5498dc63:07233b2c
> Name : devserv2:1
> Creation Time : Mon Jun 16 11:24:00 2014
> Raid Level : raid1
> Raid Devices : 2
>
> Avail Dev Size : 3900907520 (1860.10 GiB 1997.26 GB)
> Array Size : 158334976 (151.00 GiB 162.14 GB)
> Used Dev Size : 316669952 (151.00 GiB 162.14 GB)
> Data Offset : 262144 sectors
> Super Offset : 8 sectors
> State : clean
> Device UUID : 0fb85e8f:e697a9a0:7bd6eac4:03b8851d
>
> Update Time : Mon Oct 20 10:08:35 2014
> Checksum : 9b63a13c - correct
> Events : 311
>
>
> Device Role : Active device 1
> Array State : .A ('A' == active, '.' == missing)
> --
> To unsubscribe from this list: send the line "unsubscribe linux-raid" in
> the body of a message to majordomo@vger.kernel.org
> More majordomo info at http://vger.kernel.org/majordomo-info.html
[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 828 bytes --]
next prev parent reply other threads:[~2014-10-20 21:09 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-10-20 15:09 Kernel says there is not a valid superblock, but there is Phillip Susi
2014-10-20 21:09 ` NeilBrown [this message]
2014-10-21 14:07 ` Phillip Susi
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=20141021080937.69aaf214@notabene.brown \
--to=neilb@suse.de \
--cc=linux-raid@vger.kernel.org \
--cc=phillsusi@gmail.com \
/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).