Thanks Dave/Michael,

When you saw the issue in the ticket below, I know you didn't ever discover the root cause but how did you resolve this problem in the short term?  Did it just happen intermittently?  I have tried multiple different images using both l-m-c and the prebuilt ones from releases.linaro.org but nothing seems to shift the problem.

I have also tried manually playing about with the commands on a few of the boards as suggested and I couldn't see anything obvious that was going wrong which would cause this. I have also moved the boards to a new dispatcher to see if that somehow made a difference, just in case the image which was being deployed was getting screwed up on the dispatcher side.  Overall I have had no joy whatsoever.

I was thinking of putting a fresh master image on one of the boards and running the lava-first-boot scripts to see if this fixes things.  As different images and dispatcher environments don't make a difference, I am assuming the problem is related to the master image.  What release are you guys currently using for the master images on your vexpresstc2 devices?

In the lava-master-image-scripts, should running the following be enough for what I need?

./lava-create-master vexpresstc2

Cheers,
Dean

-----Original Message-----
From: Michael Hudson-Doyle [mailto:michael.hudson@linaro.org]
Sent: 05 November 2013 20:06
To: Dean Arnold; Dean Arnold; Dave Pigott
Cc: linaro-validation@lists.linaro.org Validation; Ian Spray; Basil
Eljuse
Subject: Re: [Linaro-validation] Cannot change ownership to uid 0, gid
1 when deploying linaro bootfs

Dean Arnold <Dean.Arnold@arm.com> writes:

Hi Dave,

The Ubuntu job fails yet again, even without using l-m-c.  Is there a

way to prevent LAVA from cleaning up the files after the job so that I
can check the permissions on the image?

I wonder if something has gone wrong with my dispatcher environment.

I have seen this before:
https://bugs.launchpad.net/lava-dispatcher/+bug/954870

We never really found out what was going on though -- it's bizarre, why
does sometimes tar start complaining about not being able to chown on a
vfat partition?  I agree with Dave that booting into the master image
and playing around with commands similar to those which fail might be
interesting.

Cheers,
mwh

-- IMPORTANT NOTICE: The contents of this email and any attachments are confidential and may also be privileged. If you are not the intended recipient, please notify the sender immediately and do not disclose the contents to any other person, use it for any purpose, or store or copy the information in any medium.  Thank you.

ARM Limited, Registered office 110 Fulbourn Road, Cambridge CB1 9NJ, Registered in England & Wales, Company No:  2557590
ARM Holdings plc, Registered office 110 Fulbourn Road, Cambridge CB1 9NJ, Registered in England & Wales, Company No:  2548782