rambi-e-release-group fails to build image in archive step |
|||||
Issue descriptionlosetup: /dev/loop0: detach failed: No such device or address WARNING : losetup -d /dev/loop0 failed (try 1) + sudo losetup -a + grep -H /dev/loop0 /proc/mounts + true + set +x losetup: /dev/loop0: detach failed: No such device or address WARNING : losetup -d /dev/loop0 failed (try 2) + sudo losetup -a + grep -H /dev/loop0 /proc/mounts + true + set +x losetup: /dev/loop0: detach failed: No such device or address WARNING : losetup -d /dev/loop0 failed (try 3) + sudo losetup -a + grep -H /dev/loop0 /proc/mounts + true + set +x losetup: /dev/loop0: detach failed: No such device or address WARNING : losetup -d /dev/loop0 failed (try 4) + sudo losetup -a + grep -H /dev/loop0 /proc/mounts + true + set +x losetup: /dev/loop0: detach failed: No such device or address WARNING : losetup -d /dev/loop0 failed (try 5) + sudo losetup -a + grep -H /dev/loop0 /proc/mounts + true + set +x INFO : Creating FS for partition 12 with format vfat. losetup: /dev/loop0: detach failed: No such device or address WARNING : losetup -d /dev/loop0 failed (try 1) + sudo losetup -a + grep -H /dev/loop0 /proc/mounts + true + set +x losetup: /dev/loop0: detach failed: No such device or address WARNING : losetup -d /dev/loop0 failed (try 2) + sudo losetup -a + grep -H /dev/loop0 /proc/mounts + true + set +x losetup: /dev/loop0: detach failed: No such device or address WARNING : losetup -d /dev/loop0 failed (try 3) + sudo losetup -a + grep -H /dev/loop0 /proc/mounts + true + set +x losetup: /dev/loop0: detach failed: No such device or address WARNING : losetup -d /dev/loop0 failed (try 4) + sudo losetup -a + grep -H /dev/loop0 /proc/mounts + true + set +x losetup: /dev/loop0: detach failed: No such device or address WARNING : losetup -d /dev/loop0 failed (try 5) + sudo losetup -a + grep -H /dev/loop0 /proc/mounts + true + set +x INFO : Creating FS for partition 3 with format ext2. tune2fs: Invalid argument while trying to open /dev/loop0 Couldn't find valid filesystem superblock. Full log: https://uberchromegw.corp.google.com/i/chromeos/builders/rambi-e-release-group/builds/1027/steps/Archive%20%5Borco%5D/logs/stdio Build: https://uberchromegw.corp.google.com/i/chromeos/builders/rambi-e-release-group/builds/1027 Sounds like an infrastructure problem if /dev/loop0 does not exist on the builder? Gabe, Gwendal, I saw you were working on similar issues before, can you help me triage this?
,
Apr 20 2016
+deputy Interesting. I'll log into the builder and poke around.
,
Apr 20 2016
As a note, the archive step for 'heli' is working just fine.
,
Apr 20 2016
Could the disk layout for orco be invalid? The problem would only have to be with the factory shim image layout. src/overlays/overlay-orco/scripts/disk_layout.json Hum... that doesn't seem to pan out. That file hasn't been modified since it was created, and there have been successful orco release builds in the past.
,
Apr 20 2016
I was able to allocate (and release) a loopback device on the builder, and don't see any general signs of a config problem.
,
Apr 20 2016
Passing to deputy to find a better owner.
,
Apr 20 2016
,
May 26 2016
Reopen if this is still a problem |
|||||
►
Sign in to add a comment |
|||||
Comment 1 by gabeblack@chromium.org
, Apr 20 2016