Bug 5930

Summary: udevd failed to execute /etc/udev/scripts/mount.sh (1.4.3 RC)
Product: [Build System, Metadata & Runtime] BSPs Reporter: Stoicescu Cornel <corneliux.stoicescu>
Component: bsps-meta-minnowAssignee: Paul Eggleton <bluelightning>
Status: VERIFIED FIXED QA Contact:
Severity: normal    
Priority: Medium CC: bluelightning, dvhart, poky.bs.watcher, poky.watcher, scott.a.garman, sgw
Version: 1.4.2   
Target Milestone: 1.4.3   
Hardware: x86   
OS: Multiple   
Whiteboard:
OS type for building Yocto: --- Type of Regression: Regression (Used to work)
Verified: Documentation change: No (bug/feature does not impact docs)
Attachments:
Description Flags
autobuilder build proprieties none

Description Stoicescu Cornel 2014-03-07 15:59:15 UTC 
poky dylan:7ab82abcad9ede847c42c01d2a4f4c2c18877e6f (1.4.3 Release Candidate)

When installing the image, the following message is shown:
udevd[429]: failed to execute '/etc/udev/scripts/mount.sh' '/etc/udev/scripts/mount.sh': No such file or directory


This was fixed in dylan (bug 5233) and does not appear on the atom-pc image installation. The commit mentioned in the bug is contained in this RC. Could this be related to meta-minnow?
Comment 1 Saul Wold 2014-03-10 16:16:02 UTC 
More details would be very helpful, can you confirm which image you are building, the build configuration (SRCREVs of all layers), are you doing a live boot or image install?

Is there a test case associated with the failure so that we can try to reproduce it.
Comment 2 Stoicescu Cornel 2014-03-11 08:53:50 UTC 
Created attachment 1805 [details]
autobuilder build proprieties

This was tested with 1.4.3 RC3. See attached autobuilder build proprieties.
Comment 3 Stoicescu Cornel 2014-03-11 08:55:24 UTC 
Also, as long as it's available, here is the link to the builder:
http://autobuilder.yoctoproject.org/main/builders/minnow/builds/77
Comment 4 Stoicescu Cornel 2014-03-11 09:17:07 UTC 
In order to reproduce the issue, attempt to install the image from USB. After selecting the storage device to be installed on, the following message will appear multiple times. Please note that the installation finishes but the resulting installation gives the error described in bug 5928.

Also please look at bug 5233 as it seems to be the same issue.
Comment 5 Stoicescu Cornel 2014-03-11 13:43:57 UTC 
NOTE: We used the core-image-sato-sdk-minnow.hddimg image.

Also found this issue using core-image-sato-sdk-sugarbay during the install procedure, the difference being that the installed image works without issues. This is looking a lot like bug 5233. 

Will rename the bug because it's not minnow-related.
Comment 6 Paul Eggleton 2014-03-11 15:25:47 UTC 
I'm guessing we can just backport 1917544d2f554a68f853fcd5d4c475f3567021cb to solve this.
Comment 8 Stoicescu Cornel 2014-03-21 15:07:02 UTC 
poky dylan:c397b69e681d5f1ffe0a0bfd9d43ee880fc27553

I can still see this message on core-image-lsb-sdk-sugarbay. Will investigate with more images from this commit.
Comment 9 Stoicescu Cornel 2014-03-25 08:47:12 UTC 
I can confirm this is still present on core-image-sato-sdk-sugarbay with the following configuration:

meta-intel 6ea7c0f0af5ad20bffba3cf21b17da892e842f82
poky c397b69e681d5f1ffe0a0bfd9d43ee880fc27553
Comment 10 Stoicescu Cornel 2014-03-28 16:51:19 UTC 
I have tested both images on sugarbay(sato-sdk and lsb-sdk) and the issue is not present anymore. I don't understand why this showed up the first time.

Changing back to resolved.
Comment 11 Stoicescu Cornel 2014-03-28 16:51:38 UTC 
And now to Verified.