That's all there was in installation log. Installation couldn't go further
without the disk, so that was all.

On Tue, Aug 30, 2016 at 4:10 PM Ryan Harper <email address hidden>
wrote:

> OK, if you do run into it again or reproduce it, the entire log is
> important, not just the stack trace.
>
> On Tue, Aug 30, 2016 at 8:54 AM, Ante Karamatić <
> <email address hidden>> wrote:
>
> > I don't have from that specific machine, because I had to move on. But
> > error was pretty much the same as this one (maybe md3 instead of md4):
> >
> > Error: /dev/sda: unrecognised disk labelAn error occured handling
> > 'sda': ProcessExecutionError - Unexpected error while running
> > command.Command: ['mdadm', '--assemble', '--scan']Exit code: 3Reason:
> > -Stdout: ''Stderr: u'mdadm: /dev/md/4 assembled from 3 drives - not
> > enough to start the array.\n'Unexpected error while running
> > command.Command: ['mdadm', '--assemble', '--scan']Exit code: 3Reason:
> > -Stdout: ''Stderr: u'mdadm: /dev/md/4 assembled from 3 drives - not
> > enough to start the array.\n'Installation failed with exception:
> > Unexpected error while running command.Command: ['curtin',
> > 'block-meta', 'custom']Exit code: 3Reason: -Stdout: "Error: /dev/sda:
> > unrecognised disk label\nAn error occured handling 'sda':
> > ProcessExecutionError - Unexpected error while running
> > command.\nCommand: ['mdadm', '--assemble', '--scan']\nExit code:
> > 3\nReason: -\nStdout: ''\nStderr: u'mdadm: /dev/md/4 assembled from 3
> > drives - not enough to start the array.\\n'\nUnexpected error while
> > running command.\nCommand: ['mdadm', '--assemble', '--scan']\nExit
> > code: 3\nReason: -\nStdout: ''\nStderr: u'mdadm: /dev/md/4 assembled
> > from 3 drives - not enough to start the array.\\n'\n"Stderr: ''
> >
> >
> > On Tue, Aug 30, 2016 at 3:40 PM Ryan Harper <email address hidden>
> > wrote:
> >
> > > Hi Ante,
> > >
> > > Can you attach the install.log reported back to maas?  It should be on
> > the
> > > node details page.
> > >
> > > https://gist.github.com/smoser/2610e9b78b8d7b54319675d9e3986a1b
> > >
> > > On Tue, Aug 30, 2016 at 7:02 AM, Ante Karamatić <
> > > <email address hidden>> wrote:
> > >
> > > > I forgot to mention, this is curtin in 14.04. I'd assume that's
> > > > 0.1.0~bzr399-0ubuntu1~16.04.1.
> > > >
> > > > --
> > > > You received this bug notification because you are subscribed to
> > curtin.
> > > > Matching subscriptions: curtin-bugs-all
> > > > https://bugs.launchpad.net/bugs/1618429
> > > >
> > > > Title:
> > > >   Curtin doesn't clean up previous MD configuration
> > > >
> > > > To manage notifications about this bug go to:
> > > > https://bugs.launchpad.net/curtin/+bug/1618429/+subscriptions
> > > >
> > >
> > > --
> > > You received this bug notification because you are subscribed to the
> bug
> > > report.
> > > https://bugs.launchpad.net/bugs/1618429
> > >
> > > Title:
> > >   Curtin doesn't clean up previous MD configuration
> > >
> > > To manage notifications about this bug go to:
> > > https://bugs.launchpad.net/curtin/+bug/1618429/+subscriptions
> > >
> > --
> > Ante Karamatić
> > <email address hidden>
> > Canonical
> >
> > --
> > You received this bug notification because you are subscribed to curtin.
> > Matching subscriptions: curtin-bugs-all
> > https://bugs.launchpad.net/bugs/1618429
> >
> > Title:
> >   Curtin doesn't clean up previous MD configuration
> >
> > To manage notifications about this bug go to:
> > https://bugs.launchpad.net/curtin/+bug/1618429/+subscriptions
> >
>
> --
> You received this bug notification because you are subscribed to the bug
> report.
> https://bugs.launchpad.net/bugs/1618429
>
> Title:
>   Curtin doesn't clean up previous MD configuration
>
> To manage notifications about this bug go to:
> https://bugs.launchpad.net/curtin/+bug/1618429/+subscriptions
>
-- 
Ante Karamatić
<email address hidden>
Canonical