curtin

Bug #1520400
Comment #5

Comment 5 for bug 1520400

Revision history for this message

Ryan Harper (raharper) wrote on 2015-12-21: Re: [Bug 1520400] Re: curtin error on arm64 wily deployment for xgene-2 Soc

Check how much memory is available... the overlayroot fs (root and /tmp)
are housed in host ram. If you have too little then it's possible that
writes fail.
I've seen this testing in VMs with too little ram.

On Sun, Dec 20, 2015 at 11:04 PM, Newell Jensen <<email address hidden>
> wrote:

> Here is some more information on my efforts to get xgene-2 working with
> MAAS.
>
> With the correct patches in place I am now seeing this error with my
> deployment:
>
> Processing triggers for initramfs-tools (0.103ubuntu4.2) ...
> update-initramfs: Generating /boot/initrd.img-3.13.0-71-generic
> WARNING: missing /lib/modules/3.13.0-71-generic
> Device driver support needs thus be built-in linux image!
> depmod: ERROR: could not open directory /lib/modules/3.13.0-71-generic: No
> such file or directory
> depmod: FATAL: could not search modules: No such file or directory
> cryptsetup: WARNING: failed to detect canonical device of /media/root-ro/
> cryptsetup: WARNING: could not determine root device from /etc/fstab
> W: mdadm: /etc/mdadm/mdadm.conf defines no arrays.
> depmod: WARNING: could not open
> /tmp/mkinitramfs_ctfNOX/lib/modules/3.13.0-71-generic/modules.order: No
> such file or directory
> depmod: WARNING: could not open
> /tmp/mkinitramfs_ctfNOX/lib/modules/3.13.0-71-generic/modules.builtin: No
> such file or directory
> Unsupported platform on EFI system, doing nothing.
> Processing triggers for ureadahead (0.100.0-16) ...
> Processing triggers for ufw (0.34~rc-0ubuntu2) ...
> mdadm: No arrays found in config file or automatically
> Creating new GPT entries.
> The operation has completed successfully.
>
>
> Not entirely sure why the headers would not be installed to cause this
> error because when I examine the root-image they are there. Seems like
> maybe there is some issue with overlayroot not working properly.
> For the entire deployment console output, please see the below:
>
> http://paste.ubuntu.com/14125038/
>
> --
> You received this bug notification because you are subscribed to curtin.
> Matching subscriptions: curtin-bugs-all
> https://bugs.launchpad.net/bugs/1520400
>
> Title:
> curtin error on arm64 wily deployment for xgene-2 Soc
>
> To manage notifications about this bug go to:
> https://bugs.launchpad.net/curtin/+bug/1520400/+subscriptions
>

Check how much memory is available... the overlayroot fs (root and /tmp)
are housed in host ram.  If you have too little then it's possible that
writes fail.
I've seen this testing in VMs with too little ram.

On Sun, Dec 20, 2015 at 11:04 PM, Newell Jensen <newell.jensen@canonical.com
> wrote:

> Here is some more information on my efforts to get xgene-2 working with
> MAAS.
>
> With the correct patches in place I am now seeing this error with my
> deployment:
>
> Processing triggers for initramfs-tools (0.103ubuntu4.2) ...
> update-initramfs: Generating /boot/initrd.img-3.13.0-71-generic
> WARNING: missing /lib/modules/3.13.0-71-generic
> Device driver support needs thus be built-in linux image!
> depmod: ERROR: could not open directory /lib/modules/3.13.0-71-generic: No
> such file or directory
> depmod: FATAL: could not search modules: No such file or directory
> cryptsetup: WARNING: failed to detect canonical device of /media/root-ro/
> cryptsetup: WARNING: could not determine root device from /etc/fstab
> W: mdadm: /etc/mdadm/mdadm.conf defines no arrays.
> depmod: WARNING: could not open
> /tmp/mkinitramfs_ctfNOX/lib/modules/3.13.0-71-generic/modules.order: No
> such file or directory
> depmod: WARNING: could not open
> /tmp/mkinitramfs_ctfNOX/lib/modules/3.13.0-71-generic/modules.builtin: No
> such file or directory
> Unsupported platform on EFI system, doing nothing.
> Processing triggers for ureadahead (0.100.0-16) ...
> Processing triggers for ufw (0.34~rc-0ubuntu2) ...
> mdadm: No arrays found in config file or automatically
> Creating new GPT entries.
> The operation has completed successfully.
>
>
> Not entirely sure why the headers would not be installed to cause this
> error because when I examine the root-image they are there.  Seems like
> maybe there is some issue with overlayroot not working properly.
> For the entire deployment console output, please see the below:
>
> http://paste.ubuntu.com/14125038/
>
> --
> You received this bug notification because you are subscribed to curtin.
> Matching subscriptions: curtin-bugs-all
> https://bugs.launchpad.net/bugs/1520400
>
> Title:
>   curtin error on arm64 wily deployment for xgene-2 Soc
>
> To manage notifications about this bug go to:
> https://bugs.launchpad.net/curtin/+bug/1520400/+subscriptions
>