From: Mike Tran <mhtran@us.ibm.com>
To: JaniD++ <djani22@dynamicweb.hu>
Cc: linux-raid@vger.kernel.org
Subject: Re: assembly aborted, superblock is missing. (need help!)
Date: Mon, 19 Sep 2005 17:27:17 -0500 [thread overview]
Message-ID: <432F3B45.1010304@us.ibm.com> (raw)
In-Reply-To: <008801c5bc54$b9fd57f0$0400a8c0@dcccs>
Hi Janos,
The problem with disappearing MD superblock must be investigated. :(
It is safe to re-create the raid0 array:
mdadm -C /dev/md31 -l 0 -c 32 -n 4 /dev/md1 /dev/md2 /dev/md3 /dev/md4
--
Regards,
Mike Tran
JaniD++ wrote:
>Hello list!
>
>I have try to switch from 2.6.13 to 14-rc1, but this kernel breaks my
>device!
>
>The problem:
># mdadm -A -R -f /dev/md31 /dev/md1 /dev/md2 /dev/md3 /dev/md4
>mdadm: no RAID superblock on /dev/md1
>mdadm: /dev/md1 has no superblock - assembly aborted
>
>
>md31 is a 8TB raid0 device.
>
>the 2. dev:
># mdadm -E /dev/md2
>/dev/md2:
> Magic : a92b4efc
> Version : 00.90.02
> UUID : 9a99d340:ab8f6bfc:bc8d42ed:79ce440e
> Creation Time : Sun Jul 17 19:50:11 2005
> Raid Level : raid0
> Device Size : 1953583232 (1863.08 GiB 2000.47 GB)
> Raid Devices : 4
> Total Devices : 4
>Preferred Minor : 31
>
> Update Time : Sun Jul 17 19:50:11 2005
> State : active
> Active Devices : 4
>Working Devices : 4
> Failed Devices : 0
> Spare Devices : 0
> Checksum : 1fd71b51 - correct
> Events : 0.2
>
> Chunk Size : 32K
>
> Number Major Minor RaidDevice State
>this 1 9 2 1 active sync /dev/md2
>
> 0 0 9 1 0 active sync /dev/md1
> 1 1 9 2 1 active sync /dev/md2
> 2 2 9 3 2 active sync /dev/md3
> 3 3 9 4 3 active sync /dev/md4
>
>the 3. dev:
>
># mdadm -E /dev/md3
>/dev/md3:
> Magic : a92b4efc
> Version : 00.90.02
> UUID : 9a99d340:ab8f6bfc:bc8d42ed:79ce440e
> Creation Time : Sun Jul 17 19:50:11 2005
> Raid Level : raid0
> Device Size : 1953583232 (1863.08 GiB 2000.47 GB)
> Raid Devices : 4
> Total Devices : 4
>Preferred Minor : 31
>
> Update Time : Sun Jul 17 19:50:11 2005
> State : active
> Active Devices : 4
>Working Devices : 4
> Failed Devices : 0
> Spare Devices : 0
> Checksum : 1fd71b54 - correct
> Events : 0.2
>
> Chunk Size : 32K
>
> Number Major Minor RaidDevice State
>this 2 9 3 2 active sync /dev/md3
>
> 0 0 9 1 0 active sync /dev/md1
> 1 1 9 2 1 active sync /dev/md2
> 2 2 9 3 2 active sync /dev/md3
> 3 3 9 4 3 active sync /dev/md4
>
>
>
>the 4.dev:
>
># mdadm -E /dev/md4
>/dev/md4:
> Magic : a92b4efc
> Version : 00.90.02
> UUID : 9a99d340:ab8f6bfc:bc8d42ed:79ce440e
> Creation Time : Sun Jul 17 19:50:11 2005
> Raid Level : raid0
> Device Size : 1953583232 (1863.08 GiB 2000.47 GB)
> Raid Devices : 4
> Total Devices : 4
>Preferred Minor : 31
>
> Update Time : Sun Jul 17 19:50:11 2005
> State : active
> Active Devices : 4
>Working Devices : 4
> Failed Devices : 0
> Spare Devices : 0
> Checksum : 1fd71b57 - correct
> Events : 0.2
>
> Chunk Size : 32K
>
> Number Major Minor RaidDevice State
>this 3 9 4 3 active sync /dev/md4
>
> 0 0 9 1 0 active sync /dev/md1
> 1 1 9 2 1 active sync /dev/md2
> 2 2 9 3 2 active sync /dev/md3
> 3 3 9 4 3 active sync /dev/md4
>
>
>but the md1 (the first dev) is this:
># mdadm -E /dev/md1
>mdadm: No super block found on /dev/md1 (Expected magic a92b4efc, got
>56dfa32e)
>
>
>How can I fix this?
>Can somebody help?
>
>Thanks
>Janos
>
>-
>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
>
>
>
next prev parent reply other threads:[~2005-09-19 22:27 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-09-15 20:11 Good, recent FS comparison? Ewan Grantham
2005-09-16 3:10 ` Tyler
2005-09-16 3:44 ` Jon Lewis
2005-09-16 7:35 ` Tyler
2005-09-16 21:17 ` Al Boldi
2005-09-18 9:15 ` Tyler
2005-09-18 11:29 ` Raz Ben-Jehuda(caro)
2005-09-18 12:32 ` Al Boldi
2005-09-18 13:27 ` assembly aborted, superblock is missing. (need help!) JaniD++
2005-09-19 22:27 ` Mike Tran [this message]
2005-09-18 16:34 ` Good, recent FS comparison? Matt Stegman
2005-09-20 21:00 ` George N. White III
2005-12-27 23:33 ` James Northrup
2005-12-28 1:45 ` Randy.Dunlap
2005-12-28 2:02 ` James Northrup
2005-09-21 15:37 ` Jamie Lokier
2005-09-21 21:34 ` Al Boldi
2005-09-22 12:14 ` Jamie Lokier
2005-09-22 13:55 ` Al Boldi
2005-09-18 17:54 ` Jonathan Schmidt
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=432F3B45.1010304@us.ibm.com \
--to=mhtran@us.ibm.com \
--cc=djani22@dynamicweb.hu \
--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).