© 2004
Canonical Ltd.
•
Terms of use
•
Data privacy
•
Contact Launchpad Support
•
Blog
•
Careers
•
System status
•
bbfa235
(Get the code!)
After further investigation today, and discussion with colleague, it is possible that this has been caused by creating the array manually using the mdadm command, then subsequently, when rebooted detects and starts the array.
However, when adding the new drive and growing the array, it reads in the mdadm command, which mentions HOMEHOST <system> parameter, and it is assigned to the new device, which after a reboot refuses to play with the rest of the array... Possibility but not certain...
Indicators are that the UUID was different (even though it was added to the array (5 devices, 0 spare) for 12 days, and that the 'disk5' also mentions (local to host FeistyFawn) which none of the other drives mention.