Try the following:
mdadm --stop /dev/md126
Check /proc/mdstat and make sure there is nothing there
Check dmesg output and note the last line, you will need to paste
everything after this line into your next email
madam --assemble /dev/md126 /dev/sd[abcdef]1
Adjust the devices listed above as applicable
Post the output of the above command, the dmesg output, and also
/proc/mdstat afterwards.
You can also try stopping the array/clearing it again, and then try
adding --force to the above command. Make sure to post the results.
Regards,
Adam
On 31/03/2016 17:09, Peter Knight wrote:
Thank you for the reply Phil.
Unfortunately that didn't work, I get the following message:
root@Wheal-Peevor:~# mdadm --run /dev/md126
mdadm: failed to start array /dev/md126: Input/output error
Thanks
Peter
On 30 March 2016 at 23:17, Phil Turmel <philip@xxxxxxxxxx> wrote:
On 03/30/2016 05:19 PM, Peter Knight wrote:
Hi,
I hope someone can explain what is going on and hopefully help me
recover my data.
What is causing this? and how can I get it reassembled so I can read the data?
When mdadm assembles an array during boot that has fewer devices than
when it was last shut down (cleanly), it generally declines to start it.
Probably, all you need is:
mdadm --run /dev/md126
{ --detail may not be accurate on an inactive device. The member
--examine data is trustworthy. }
Phil
--
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
