cros-beefy19-c2 failing to init partition table |
|||||||
Issue descriptionSee: https://logs.chromium.org/v/?s=chromeos%2Fbb%2Fchromeos%2Fcave-release%2F1859%2F%2B%2Frecipes%2Fsteps%2FArchive%2F0%2Fstdout INFO : Using image type factory_install INFO : Using disk layout /mnt/host/source/src/overlays/baseboard-glados/scripts/disk_layout.json WARNING: Primary GPT header is invalid WARNING: Secondary GPT header is invalid INFO : Creating FS for partition 8 with format ext4. INFO : Creating FS for partition 12 with format vfat. INFO : Creating FS for partition 3 with format ext2. INFO : Creating FS for partition 1 with format ext4. mount: wrong fs type, bad option, bad superblock on /dev/loop3, missing codepage or helper program, or other error In some cases useful info is found in syslog - try dmesg | tail or so. ERROR : mount failed: device=/mnt/host/source/src/build/images/cave/R65-10313.0.0-a3/factory_install_shim.bin target=/mnt/host/source/src/build/images/cave/R65-10313.0.0-a3/esp format=vfat ro/rw=rw options=offset=127926272 ERROR : Tue Jan 16 04:26:05 PST 2018 ERROR : PGID PPID PID ELAPSED TIME %CPU COMMAND ERROR : Arguments of 911: '--from' '/mnt/host/source/src/build/images/cave/R65-10313.0.0-a3/factory_install_shim.bin' '--rootfs_mountpt' '/mnt/host/source/src/build/images/cave/R65-10313.0.0-a3/rootfs' '--stateful_mountpt' '/mnt/host/source/src/build/images/cave/R65-10313.0.0-a3/stateful' '--esp_mountpt' '/mnt/host/source/src/build/images/cave/R65-10313.0.0-a3/esp' ERROR : Backtrace: (most recent call is last) ERROR : mount_gpt_image.sh:478:main(), called: mount_image ERROR : mount_gpt_image.sh:393:mount_image(), called: die 'Failed to mount all partitions in /mnt/host/source/src/build/images/cave/R65-10313.0.0-a3/factory_install_shim.bin' ERROR : ERROR : Error was: ERROR : Failed to mount all partitions in /mnt/host/source/src/build/images/cave/R65-10313.0.0-a3/factory_install_shim.bin
,
Jan 16 2018
I'm suspicious this isn't actually a builder issue -- we should see if this build_image failure happens on other builders
,
Jan 16 2018
It's probably build a builder issue, but a problem the build virtual disk image produced by the build. If it reproduces consistently, I would expect it to reproduce on a different builder, or even on a developers desktop. PS: If you can link the build, not just the log, that would be helpful.
,
Jan 16 2018
Um... words are hard. "It's probably not a builder issue,"...
,
Jan 16 2018
,
Jan 16 2018
Re-assign to sheriff to find out the image issue
,
Jan 16 2018
It looks like I don't have access to this bot: https://chrome-internal.googlesource.com/infra/infra_internal/+/master/doc/ssh.md#connecting-to-cros_beefy_c2-machines
,
Jan 16 2018
builder: https://luci-milo.appspot.com/buildbot/chromeos/cave-release/1859 error: Error was: ERROR : Failed to mount all partitions in /mnt/host/source/src/build/images/cave/R65-10313.0.0-a3/factory_install_shim.bin I guess this is something wrong with the binary file? This is not an infra issue.
,
Jan 16 2018
Yes, we need to get more information about why it failed to mount, such as errors in dmesg.
,
Jan 16 2018
I'm pretty sure that it can be reproduced locally with: cros tryjob --local cave-release-tryjob
,
Jan 17 2018
It looks like this particular failure didn't repeat in the next build -- https://luci-milo.appspot.com/buildbot/chromeos/cave-release/1860 some kind of flake relating to loop devices?
,
Mar 13 2018
+Ben Close this?
,
Mar 13 2018
This looks like maybe a duplicate of crbug.com/796254 ?
,
Mar 14 2018
cros-beefy19-c2 is not managed buy Chrome Labs. Removing our component
,
May 10 2018
|
|||||||
►
Sign in to add a comment |
|||||||
Comment 1 by shuqianz@chromium.org
, Jan 16 2018