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@xxxxxxxxxx> 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@xxxxxxxxxxxxxxxxxxx>
>> 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@xxxxxxxxxxxxxxx
>>> 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@xxxxxxxxxxxxxxx
>> More majordomo info at http://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@xxxxxxxxxxxxxxx
More majordomo info at http://vger.kernel.org/majordomo-info.html
