* More information on linux raid partition problem
@ 2016-02-18 16:12 d c
[not found] ` <56C5F6A4.4040205@digitallyhosted.com>
0 siblings, 1 reply; 8+ messages in thread
From: d c @ 2016-02-18 16:12 UTC (permalink / raw)
To: linux-raid
For anyone who can help me here is some more information on my linux
raid partition problem.
As stated before, I only have two disks from a three disk raid 5.
When I try:
mdadm --assemble /dev/md0 /dev/hdd2 /dev/hde2
I get the following error:
mdadm: cannot open device /dev/hdd2: No such file or directory
mdadm: /dev/hdd2 has no superblock - assembly aborted
When I do a mdadm examine, I get a different number of events:
mdadm --examine /dev/sdd2 | egrep Event
Events : 60541
mdadm --examine /dev/sde2 | egrep Event
Events : 60544
Also mdadm examine gives different States:
mdadm --examine /dev/sdd2 | egrep State
State : active
mdadm --examine /dev/sde2 | egrep State
State : clean
But mdadm shows that their Magic and UUID numbers are the same.
Can anyone give suggestions on how I can repair this?
Here are the full mdadm --examine outputs:
mdadm --examine /dev/sdd2
/dev/sdd2:
Magic : a92b4efc
Version : 0.90.00
UUID : 1787919b:a8648f43:ae108b15:09b5fb69
Creation Time : Fri Jan 7 17:54:08 2005
Raid Level : raid5
Used Dev Size : 48194816 (45.96 GiB 49.35 GB)
Array Size : 96389632 (91.92 GiB 98.70 GB)
Raid Devices : 3
Total Devices : 2
Preferred Minor : 126
Update Time : Tue May 1 15:55:58 2012
State : active
Active Devices : 2
Working Devices : 2
Failed Devices : 0
Spare Devices : 0
Checksum : b53ef3cf - correct
Events : 60541
Layout : left-symmetric
Chunk Size : 128K
Number Major Minor RaidDevice State
this 2 8 66 2 active sync /dev/sde2
0 0 0 0 0 removed
1 1 8 50 1 active sync /dev/sdd2
2 2 8 66 2 active sync /dev/sde2
mdadm --examine /dev/sde2
/dev/sde2:
Magic : a92b4efc
Version : 0.90.00
UUID : 1787919b:a8648f43:ae108b15:09b5fb69
Creation Time : Fri Jan 7 17:54:08 2005
Raid Level : raid5
Used Dev Size : 48194816 (45.96 GiB 49.35 GB)
Array Size : 96389632 (91.92 GiB 98.70 GB)
Raid Devices : 3
Total Devices : 2
Preferred Minor : 126
Update Time : Tue May 1 15:56:20 2012
State : clean
Active Devices : 1
Working Devices : 1
Failed Devices : 1
Spare Devices : 0
Checksum : b53fe060 - correct
Events : 60544
Layout : left-symmetric
Chunk Size : 128K
Number Major Minor RaidDevice State
this 1 8 50 1 active sync /dev/sdd2
0 0 0 0 0 removed
1 1 8 50 1 active sync /dev/sdd2
2 2 0 0 2 faulty removed
^ permalink raw reply [flat|nested] 8+ messages in thread
* Re: More information on linux raid partition problem
[not found] ` <56C5F6A4.4040205@digitallyhosted.com>
@ 2016-02-18 17:17 ` d c
2016-02-18 17:26 ` Benjamin ESTRABAUD
0 siblings, 1 reply; 8+ messages in thread
From: d c @ 2016-02-18 17:17 UTC (permalink / raw)
To: Admin@DH; +Cc: linux-raid
Thank you for the reply.
Yes that was just a typo when I rerun the command for the e-mail.
Originally I typed it correct (and that does not work either)
mdadm --assemble /dev/md0 /dev/sdd2 /dev/sde2
mdadm: cannot open device /dev/sdd2: Device or resource busy
mdadm: /dev/sdd2 has no superblock - assembly aborted
On Thu, Feb 18, 2016 at 5:51 PM, Admin@DH <admin@digitallyhosted.com> wrote:
> You typed:
>
> mdadm --assemble /dev/md0 /dev/hdd2 /dev/hde2
>
> It should be:
>
> mdadm --assemble /dev/md0 /dev/sdd2 /dev/sde2
>
> Was that just a typo?
>
>
> On 18/02/2016 16:12, d c wrote:
>
> For anyone who can help me here is some more information on my linux
> raid partition problem.
>
> As stated before, I only have two disks from a three disk raid 5.
>
> When I try:
>
> mdadm --assemble /dev/md0 /dev/hdd2 /dev/hde2
>
> I get the following error:
>
> mdadm: cannot open device /dev/hdd2: No such file or directory
> mdadm: /dev/hdd2 has no superblock - assembly aborted
>
> When I do a mdadm examine, I get a different number of events:
>
> mdadm --examine /dev/sdd2 | egrep Event
> Events : 60541
> mdadm --examine /dev/sde2 | egrep Event
> Events : 60544
>
> Also mdadm examine gives different States:
>
> mdadm --examine /dev/sdd2 | egrep State
> State : active
> mdadm --examine /dev/sde2 | egrep State
> State : clean
>
> But mdadm shows that their Magic and UUID numbers are the same.
>
> Can anyone give suggestions on how I can repair this?
>
> Here are the full mdadm --examine outputs:
>
> mdadm --examine /dev/sdd2
> /dev/sdd2:
> Magic : a92b4efc
> Version : 0.90.00
> UUID : 1787919b:a8648f43:ae108b15:09b5fb69
> Creation Time : Fri Jan 7 17:54:08 2005
> Raid Level : raid5
> Used Dev Size : 48194816 (45.96 GiB 49.35 GB)
> Array Size : 96389632 (91.92 GiB 98.70 GB)
> Raid Devices : 3
> Total Devices : 2
> Preferred Minor : 126
>
> Update Time : Tue May 1 15:55:58 2012
> State : active
> Active Devices : 2
> Working Devices : 2
> Failed Devices : 0
> Spare Devices : 0
> Checksum : b53ef3cf - correct
> Events : 60541
>
> Layout : left-symmetric
> Chunk Size : 128K
>
> Number Major Minor RaidDevice State
> this 2 8 66 2 active sync /dev/sde2
>
> 0 0 0 0 0 removed
> 1 1 8 50 1 active sync /dev/sdd2
> 2 2 8 66 2 active sync /dev/sde2
>
> mdadm --examine /dev/sde2
> /dev/sde2:
> Magic : a92b4efc
> Version : 0.90.00
> UUID : 1787919b:a8648f43:ae108b15:09b5fb69
> Creation Time : Fri Jan 7 17:54:08 2005
> Raid Level : raid5
> Used Dev Size : 48194816 (45.96 GiB 49.35 GB)
> Array Size : 96389632 (91.92 GiB 98.70 GB)
> Raid Devices : 3
> Total Devices : 2
> Preferred Minor : 126
>
> Update Time : Tue May 1 15:56:20 2012
> State : clean
> Active Devices : 1
> Working Devices : 1
> Failed Devices : 1
> Spare Devices : 0
> Checksum : b53fe060 - correct
> Events : 60544
>
> Layout : left-symmetric
> Chunk Size : 128K
>
> Number Major Minor RaidDevice State
> this 1 8 50 1 active sync /dev/sdd2
>
> 0 0 0 0 0 removed
> 1 1 8 50 1 active sync /dev/sdd2
> 2 2 0 0 2 faulty removed
> --
> To unsubscribe from this list: send the line "unsubscribe linux-raid" in
> the body of a message tomajordomo@vger.kernel.org
> More majordomo info athttp://vger.kernel.org/majordomo-info.html
>
^ permalink raw reply [flat|nested] 8+ messages in thread
* Re: More information on linux raid partition problem
2016-02-18 17:17 ` d c
@ 2016-02-18 17:26 ` Benjamin ESTRABAUD
2016-02-18 18:03 ` d c
0 siblings, 1 reply; 8+ messages in thread
From: Benjamin ESTRABAUD @ 2016-02-18 17:26 UTC (permalink / raw)
To: d c, Admin@DH; +Cc: linux-raid
sdd2 must be opened by something already. Maybe a RAID is already
assembled with that particular device? What does "cat /proc/mdstat" outputs?
Otherwise "lsof|grep sdd" might help to find out what has a open handle
on that drive.
Regards,
Ben.
On 18/02/16 17:17, d c wrote:
> Thank you for the reply.
>
> Yes that was just a typo when I rerun the command for the e-mail.
>
> Originally I typed it correct (and that does not work either)
>
> mdadm --assemble /dev/md0 /dev/sdd2 /dev/sde2
> mdadm: cannot open device /dev/sdd2: Device or resource busy
> mdadm: /dev/sdd2 has no superblock - assembly aborted
>
> On Thu, Feb 18, 2016 at 5:51 PM, Admin@DH <admin@digitallyhosted.com> wrote:
>> You typed:
>>
>> mdadm --assemble /dev/md0 /dev/hdd2 /dev/hde2
>>
>> It should be:
>>
>> mdadm --assemble /dev/md0 /dev/sdd2 /dev/sde2
>>
>> Was that just a typo?
>>
>>
>> On 18/02/2016 16:12, d c wrote:
>>
>> For anyone who can help me here is some more information on my linux
>> raid partition problem.
>>
>> As stated before, I only have two disks from a three disk raid 5.
>>
>> When I try:
>>
>> mdadm --assemble /dev/md0 /dev/hdd2 /dev/hde2
>>
>> I get the following error:
>>
>> mdadm: cannot open device /dev/hdd2: No such file or directory
>> mdadm: /dev/hdd2 has no superblock - assembly aborted
>>
>> When I do a mdadm examine, I get a different number of events:
>>
>> mdadm --examine /dev/sdd2 | egrep Event
>> Events : 60541
>> mdadm --examine /dev/sde2 | egrep Event
>> Events : 60544
>>
>> Also mdadm examine gives different States:
>>
>> mdadm --examine /dev/sdd2 | egrep State
>> State : active
>> mdadm --examine /dev/sde2 | egrep State
>> State : clean
>>
>> But mdadm shows that their Magic and UUID numbers are the same.
>>
>> Can anyone give suggestions on how I can repair this?
>>
>> Here are the full mdadm --examine outputs:
>>
>> mdadm --examine /dev/sdd2
>> /dev/sdd2:
>> Magic : a92b4efc
>> Version : 0.90.00
>> UUID : 1787919b:a8648f43:ae108b15:09b5fb69
>> Creation Time : Fri Jan 7 17:54:08 2005
>> Raid Level : raid5
>> Used Dev Size : 48194816 (45.96 GiB 49.35 GB)
>> Array Size : 96389632 (91.92 GiB 98.70 GB)
>> Raid Devices : 3
>> Total Devices : 2
>> Preferred Minor : 126
>>
>> Update Time : Tue May 1 15:55:58 2012
>> State : active
>> Active Devices : 2
>> Working Devices : 2
>> Failed Devices : 0
>> Spare Devices : 0
>> Checksum : b53ef3cf - correct
>> Events : 60541
>>
>> Layout : left-symmetric
>> Chunk Size : 128K
>>
>> Number Major Minor RaidDevice State
>> this 2 8 66 2 active sync /dev/sde2
>>
>> 0 0 0 0 0 removed
>> 1 1 8 50 1 active sync /dev/sdd2
>> 2 2 8 66 2 active sync /dev/sde2
>>
>> mdadm --examine /dev/sde2
>> /dev/sde2:
>> Magic : a92b4efc
>> Version : 0.90.00
>> UUID : 1787919b:a8648f43:ae108b15:09b5fb69
>> Creation Time : Fri Jan 7 17:54:08 2005
>> Raid Level : raid5
>> Used Dev Size : 48194816 (45.96 GiB 49.35 GB)
>> Array Size : 96389632 (91.92 GiB 98.70 GB)
>> Raid Devices : 3
>> Total Devices : 2
>> Preferred Minor : 126
>>
>> Update Time : Tue May 1 15:56:20 2012
>> State : clean
>> Active Devices : 1
>> Working Devices : 1
>> Failed Devices : 1
>> Spare Devices : 0
>> Checksum : b53fe060 - correct
>> Events : 60544
>>
>> Layout : left-symmetric
>> Chunk Size : 128K
>>
>> Number Major Minor RaidDevice State
>> this 1 8 50 1 active sync /dev/sdd2
>>
>> 0 0 0 0 0 removed
>> 1 1 8 50 1 active sync /dev/sdd2
>> 2 2 0 0 2 faulty removed
>> --
>> To unsubscribe from this list: send the line "unsubscribe linux-raid" in
>> the body of a message tomajordomo@vger.kernel.org
>> More majordomo info athttp://vger.kernel.org/majordomo-info.html
>>
> --
> 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
>
^ permalink raw reply [flat|nested] 8+ messages in thread
* Re: More information on linux raid partition problem
2016-02-18 17:26 ` Benjamin ESTRABAUD
@ 2016-02-18 18:03 ` d c
2016-02-19 14:40 ` George Rapp
0 siblings, 1 reply; 8+ messages in thread
From: d c @ 2016-02-18 18:03 UTC (permalink / raw)
To: Benjamin ESTRABAUD; +Cc: Admin@DH, linux-raid
Ben,
You are correct, sdd2 was tied up. This must have been caused by my
experimenting on mounting md0.
[root@server ~]# cat /proc/mdstat
Personalities : [raid6] [raid5] [raid4]
md0 : inactive sdd2[2](S)
48194880 blocks
. . .
I rebooted the system and now both sdd2 and sde2 show "clean" with a
mdadm --examine.
But I still can not assemble the raid:
mdadm --assemble /dev/md0 /dev/sdd2 /dev/sde2
mdadm: cannot open device /dev/sde2: Device or resource busy
mdadm: /dev/sde2 has no superblock - assembly aborted
I hope you have more ideas.
donald
On Thu, Feb 18, 2016 at 6:26 PM, Benjamin ESTRABAUD <be@mpstor.com> wrote:
> sdd2 must be opened by something already. Maybe a RAID is already assembled
> with that particular device? What does "cat /proc/mdstat" outputs?
>
> Otherwise "lsof|grep sdd" might help to find out what has a open handle on
> that drive.
>
> Regards,
> Ben.
>
>
> On 18/02/16 17:17, d c wrote:
>>
>> Thank you for the reply.
>>
>> Yes that was just a typo when I rerun the command for the e-mail.
>>
>> Originally I typed it correct (and that does not work either)
>>
>> mdadm --assemble /dev/md0 /dev/sdd2 /dev/sde2
>> mdadm: cannot open device /dev/sdd2: Device or resource busy
>> mdadm: /dev/sdd2 has no superblock - assembly aborted
>>
>> On Thu, Feb 18, 2016 at 5:51 PM, Admin@DH <admin@digitallyhosted.com>
>> wrote:
>>>
>>> You typed:
>>>
>>> mdadm --assemble /dev/md0 /dev/hdd2 /dev/hde2
>>>
>>> It should be:
>>>
>>> mdadm --assemble /dev/md0 /dev/sdd2 /dev/sde2
>>>
>>> Was that just a typo?
>>>
>>>
>>> On 18/02/2016 16:12, d c wrote:
>>>
>>> For anyone who can help me here is some more information on my linux
>>> raid partition problem.
>>>
>>> As stated before, I only have two disks from a three disk raid 5.
>>>
>>> When I try:
>>>
>>> mdadm --assemble /dev/md0 /dev/hdd2 /dev/hde2
>>>
>>> I get the following error:
>>>
>>> mdadm: cannot open device /dev/hdd2: No such file or directory
>>> mdadm: /dev/hdd2 has no superblock - assembly aborted
>>>
>>> When I do a mdadm examine, I get a different number of events:
>>>
>>> mdadm --examine /dev/sdd2 | egrep Event
>>> Events : 60541
>>> mdadm --examine /dev/sde2 | egrep Event
>>> Events : 60544
>>>
>>> Also mdadm examine gives different States:
>>>
>>> mdadm --examine /dev/sdd2 | egrep State
>>> State : active
>>> mdadm --examine /dev/sde2 | egrep State
>>> State : clean
>>>
>>> But mdadm shows that their Magic and UUID numbers are the same.
>>>
>>> Can anyone give suggestions on how I can repair this?
>>>
>>> Here are the full mdadm --examine outputs:
>>>
>>> mdadm --examine /dev/sdd2
>>> /dev/sdd2:
>>> Magic : a92b4efc
>>> Version : 0.90.00
>>> UUID : 1787919b:a8648f43:ae108b15:09b5fb69
>>> Creation Time : Fri Jan 7 17:54:08 2005
>>> Raid Level : raid5
>>> Used Dev Size : 48194816 (45.96 GiB 49.35 GB)
>>> Array Size : 96389632 (91.92 GiB 98.70 GB)
>>> Raid Devices : 3
>>> Total Devices : 2
>>> Preferred Minor : 126
>>>
>>> Update Time : Tue May 1 15:55:58 2012
>>> State : active
>>> Active Devices : 2
>>> Working Devices : 2
>>> Failed Devices : 0
>>> Spare Devices : 0
>>> Checksum : b53ef3cf - correct
>>> Events : 60541
>>>
>>> Layout : left-symmetric
>>> Chunk Size : 128K
>>>
>>> Number Major Minor RaidDevice State
>>> this 2 8 66 2 active sync /dev/sde2
>>>
>>> 0 0 0 0 0 removed
>>> 1 1 8 50 1 active sync /dev/sdd2
>>> 2 2 8 66 2 active sync /dev/sde2
>>>
>>> mdadm --examine /dev/sde2
>>> /dev/sde2:
>>> Magic : a92b4efc
>>> Version : 0.90.00
>>> UUID : 1787919b:a8648f43:ae108b15:09b5fb69
>>> Creation Time : Fri Jan 7 17:54:08 2005
>>> Raid Level : raid5
>>> Used Dev Size : 48194816 (45.96 GiB 49.35 GB)
>>> Array Size : 96389632 (91.92 GiB 98.70 GB)
>>> Raid Devices : 3
>>> Total Devices : 2
>>> Preferred Minor : 126
>>>
>>> Update Time : Tue May 1 15:56:20 2012
>>> State : clean
>>> Active Devices : 1
>>> Working Devices : 1
>>> Failed Devices : 1
>>> Spare Devices : 0
>>> Checksum : b53fe060 - correct
>>> Events : 60544
>>>
>>> Layout : left-symmetric
>>> Chunk Size : 128K
>>>
>>> Number Major Minor RaidDevice State
>>> this 1 8 50 1 active sync /dev/sdd2
>>>
>>> 0 0 0 0 0 removed
>>> 1 1 8 50 1 active sync /dev/sdd2
>>> 2 2 0 0 2 faulty removed
>>> --
>>> To unsubscribe from this list: send the line "unsubscribe linux-raid" in
>>> the body of a message tomajordomo@vger.kernel.org
>>> More majordomo info athttp://vger.kernel.org/majordomo-info.html
>>>
>> --
>> 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
>>
>
^ permalink raw reply [flat|nested] 8+ messages in thread
* Re: More information on linux raid partition problem
2016-02-18 18:03 ` d c
@ 2016-02-19 14:40 ` George Rapp
2016-02-19 14:43 ` George Rapp
0 siblings, 1 reply; 8+ messages in thread
From: George Rapp @ 2016-02-19 14:40 UTC (permalink / raw)
To: d c; +Cc: Benjamin ESTRABAUD, Admin@DH, Linux-RAID
On Thu, Feb 18, 2016 at 1:03 PM, d c <c866e866e@gmail.com> wrote:
> Ben,
>
> You are correct, sdd2 was tied up. This must have been caused by my
> experimenting on mounting md0.
>
> [root@server ~]# cat /proc/mdstat
> Personalities : [raid6] [raid5] [raid4]
> md0 : inactive sdd2[2](S)
> 48194880 blocks
> . . .
>
> I rebooted the system and now both sdd2 and sde2 show "clean" with a
> mdadm --examine.
>
> But I still can not assemble the raid:
>
> mdadm --assemble /dev/md0 /dev/sdd2 /dev/sde2
> mdadm: cannot open device /dev/sde2: Device or resource busy
> mdadm: /dev/sde2 has no superblock - assembly aborted
Donald -
Try "mdadm --stop /dev/md0" before --assemble. Even though md0 is
inactive, it still locks its component partitions.
I don't see /dev/sde2 in the truncated output of /proc/mdstat - is it
possible it's being used for something else other than the md0 array?
--
George Rapp (Pataskala, OH) Home: george.rapp -- at -- gmail.com
LinkedIn profile: https://www.linkedin.com/in/georgerapp
Phone: +1 740 936 RAPP (740 936 7277)
^ permalink raw reply [flat|nested] 8+ messages in thread
* Re: More information on linux raid partition problem
2016-02-19 14:40 ` George Rapp
@ 2016-02-19 14:43 ` George Rapp
2016-02-19 19:01 ` d c
0 siblings, 1 reply; 8+ messages in thread
From: George Rapp @ 2016-02-19 14:43 UTC (permalink / raw)
To: d c; +Cc: Benjamin ESTRABAUD, Admin@DH, Linux-RAID
On Fri, Feb 19, 2016 at 9:40 AM, George Rapp <george.rapp@gmail.com> wrote:
> On Thu, Feb 18, 2016 at 1:03 PM, d c <c866e866e@gmail.com> wrote:
>>
>> mdadm --assemble /dev/md0 /dev/sdd2 /dev/sde2
>> mdadm: cannot open device /dev/sde2: Device or resource busy
>> mdadm: /dev/sde2 has no superblock - assembly aborted
>
> Donald -
>
> Try "mdadm --stop /dev/md0" before --assemble. Even though md0 is
> inactive, it still locks its component partitions.
>
> I don't see /dev/sde2 in the truncated output of /proc/mdstat - is it
> possible it's being used for something else other than the md0 array?
>
Sorry for replying to myself, but I noticed something further down in
the thread. Because the event counts on /dev/sdd2 and /dev/sde2 are
different, you may need to add --force to your mdadm --assemble
command.
--
George Rapp (Pataskala, OH) Home: george.rapp -- at -- gmail.com
LinkedIn profile: https://www.linkedin.com/in/georgerapp
Phone: +1 740 936 RAPP (740 936 7277)
^ permalink raw reply [flat|nested] 8+ messages in thread
* Re: More information on linux raid partition problem
2016-02-19 14:43 ` George Rapp
@ 2016-02-19 19:01 ` d c
2016-02-19 19:31 ` George Rapp
0 siblings, 1 reply; 8+ messages in thread
From: d c @ 2016-02-19 19:01 UTC (permalink / raw)
To: George Rapp; +Cc: Benjamin ESTRABAUD, Admin@DH, Linux-RAID
George,
Thank you for staying with me. I tried both commands you sent to me,
but still does not work.
Here is my session:
[root@server ~]# mdadm --stop /dev/md0
mdadm: error opening /dev/md0: No such file or directory
[root@server ~]#
[root@server ~]# mdadm --assemble --force /dev/md0 /dev/sdd2 /dev/sde2
mdadm: cannot open device /dev/sde2: No such file or directory
mdadm: /dev/sde2 has no superblock - assembly aborted
thank you,
donald
On Fri, Feb 19, 2016 at 3:43 PM, George Rapp <george.rapp@gmail.com> wrote:
> On Fri, Feb 19, 2016 at 9:40 AM, George Rapp <george.rapp@gmail.com> wrote:
>> On Thu, Feb 18, 2016 at 1:03 PM, d c <c866e866e@gmail.com> wrote:
>>>
>>> mdadm --assemble /dev/md0 /dev/sdd2 /dev/sde2
>>> mdadm: cannot open device /dev/sde2: Device or resource busy
>>> mdadm: /dev/sde2 has no superblock - assembly aborted
>>
>> Donald -
>>
>> Try "mdadm --stop /dev/md0" before --assemble. Even though md0 is
>> inactive, it still locks its component partitions.
>>
>> I don't see /dev/sde2 in the truncated output of /proc/mdstat - is it
>> possible it's being used for something else other than the md0 array?
>>
> Sorry for replying to myself, but I noticed something further down in
> the thread. Because the event counts on /dev/sdd2 and /dev/sde2 are
> different, you may need to add --force to your mdadm --assemble
> command.
>
> --
> George Rapp (Pataskala, OH) Home: george.rapp -- at -- gmail.com
> LinkedIn profile: https://www.linkedin.com/in/georgerapp
> Phone: +1 740 936 RAPP (740 936 7277)
^ permalink raw reply [flat|nested] 8+ messages in thread
* Re: More information on linux raid partition problem
2016-02-19 19:01 ` d c
@ 2016-02-19 19:31 ` George Rapp
0 siblings, 0 replies; 8+ messages in thread
From: George Rapp @ 2016-02-19 19:31 UTC (permalink / raw)
To: d c; +Cc: Benjamin ESTRABAUD, Admin@DH, Linux-RAID
On Fri, Feb 19, 2016 at 2:01 PM, d c <c866e866e@gmail.com> wrote:
>
> George,
>
> Thank you for staying with me. I tried both commands you sent to me,
> but still does not work.
>
> Here is my session:
>
> [root@server ~]# mdadm --stop /dev/md0
> mdadm: error opening /dev/md0: No such file or directory
> [root@server ~]#
> [root@server ~]# mdadm --assemble --force /dev/md0 /dev/sdd2 /dev/sde2
> mdadm: cannot open device /dev/sde2: No such file or directory
> mdadm: /dev/sde2 has no superblock - assembly aborted
The only other thing I can think to try is --re-add:
# mdadm --manage /dev/md0 --re-add /dev/sde2
Not sure if that will re-create the superblock, though.
--
George Rapp (Pataskala, OH) Home: george.rapp -- at -- gmail.com
LinkedIn profile: https://www.linkedin.com/in/georgerapp
Phone: +1 740 936 RAPP (740 936 7277)
^ permalink raw reply [flat|nested] 8+ messages in thread
end of thread, other threads:[~2016-02-19 19:31 UTC | newest]
Thread overview: 8+ messages (download: mbox.gz follow: Atom feed
-- links below jump to the message on this page --
2016-02-18 16:12 More information on linux raid partition problem d c
[not found] ` <56C5F6A4.4040205@digitallyhosted.com>
2016-02-18 17:17 ` d c
2016-02-18 17:26 ` Benjamin ESTRABAUD
2016-02-18 18:03 ` d c
2016-02-19 14:40 ` George Rapp
2016-02-19 14:43 ` George Rapp
2016-02-19 19:01 ` d c
2016-02-19 19:31 ` George Rapp
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).