Please attach the entire curtin install.log in debug mode; It's
critical to see what the storage configuration was, what curtin
cleared from the disks.

On Wed, Mar 21, 2018 at 7:15 AM, Ante Karamatić
<email address hidden> wrote:
> Another occurrence:
>
> Mar 21 12:14:34 infra3 cloud-init[2891]:         mdadm: stop failed, retrying in 0.2 seconds
> Mar 21 12:14:34 infra3 cloud-init[2891]:         mdadm: stop on /dev/md127 attempt 6
> Mar 21 12:14:34 infra3 cloud-init[2891]:         /sys/class/block/md127/md/sync_action/sync_max = recover
> Mar 21 12:14:34 infra3 cloud-init[2891]:         mdadm: setting array sync_action=idle
> Mar 21 12:14:34 infra3 cloud-init[2891]:         /sys/class/block/md127/md/sync_max/sync_max = 0
> Mar 21 12:14:34 infra3 cloud-init[2891]:         Running command ['mdadm', '--manage', '--stop', '/dev/md127'] with allowed return codes [0] (capture=True)
> Mar 21 12:14:34 infra3 cloud-init[2891]:         mdadm stop failed, retrying
> Mar 21 12:14:34 infra3 cloud-init[2891]:         /proc/mdstat:
> Mar 21 12:14:34 infra3 cloud-init[2891]:         Personalities : [raid6] [raid5] [raid4] [linear] [multipath] [raid0] [raid1] [raid10]
> Mar 21 12:14:34 infra3 cloud-init[2891]:         md127 : active raid5 sdd[3] sdc[1] sdb[0]
> Mar 21 12:14:34 infra3 cloud-init[2891]:               1953262592 blocks super 1.2 level 5, 512k chunk, algorithm 2 [3/2] [UU_]
> Mar 21 12:14:34 infra3 cloud-init[2891]:               [>....................]  recovery =  0.1% (1029720/976631296) finish=1016251.6min speed=0K/sec
> Mar 21 12:14:34 infra3 cloud-init[2891]:               bitmap: 2/8 pages [8KB], 65536KB chunk
> Mar 21 12:14:34 infra3 cloud-init[2891]:
> Mar 21 12:14:34 infra3 cloud-init[2891]:         unused devices: <none>
> Mar 21 12:14:34 infra3 cloud-init[2891]:
> Mar 21 12:14:34 infra3 cloud-init[2891]:         mdadm: stop failed, retrying in 0.2 seconds
> Mar 21 12:14:34 infra3 cloud-init[2891]:         mdadm: stop on /dev/md127 attempt 7
> Mar 21 12:14:34 infra3 cloud-init[2891]:         /sys/class/block/md127/md/sync_action/sync_max = recover
> Mar 21 12:14:34 infra3 cloud-init[2891]:         mdadm: setting array sync_action=idle
> Mar 21 12:14:34 infra3 cloud-init[2891]:         /sys/class/block/md127/md/sync_max/sync_max = 0
> Mar 21 12:14:34 infra3 cloud-init[2891]:         Running command ['mdadm', '--manage', '--stop', '/dev/md127'] with allowed return codes [0] (capture=True)
> Mar 21 12:14:34 infra3 cloud-init[2891]:         mdadm stop failed, retrying
> Mar 21 12:14:34 infra3 cloud-init[2891]:         /proc/mdstat:
> Mar 21 12:14:34 infra3 cloud-init[2891]:         Personalities : [raid6] [raid5] [raid4] [linear] [multipath] [raid0] [raid1] [raid10]
> Mar 21 12:14:34 infra3 cloud-init[2891]:         md127 : active raid5 sdd[3] sdc[1] sdb[0]
> Mar 21 12:14:34 infra3 cloud-init[2891]:               1953262592 blocks super 1.2 level 5, 512k chunk, algorithm 2 [3/2] [UU_]
> Mar 21 12:14:34 infra3 cloud-init[2891]:               [>....................]  recovery =  0.1% (1029720/976631296) finish=1016251.6min speed=0K/sec
> Mar 21 12:14:34 infra3 cloud-init[2891]:               bitmap: 2/8 pages [8KB], 65536KB chunk
>
> --
> You received this bug notification because you are subscribed to the bug
> report.
> https://bugs.launchpad.net/bugs/1750519
>
> Title:
>   An error occured handling 'bcache0': ValueError - Invalid number 0 of
>   holding devices: "[]"
>
> To manage notifications about this bug go to:
> https://bugs.launchpad.net/curtin/+bug/1750519/+subscriptions