New issue
Advanced search Search tips
Note: Color blocks (like or ) mean that a user may not be available. Tooltip shows the reason.
Starred by 2 users

Issue metadata

Status: Verified
Closed: Feb 2018
EstimatedDays: ----
NextAction: ----
OS: Chrome
Pri: 1
Type: Bug

Sign in to add a comment

Issue 809570: Paladins sometimes can't mount chroot

Reported by, Feb 6 2018 Project Member

Issue description

WARNING: Failed to activate VG on try 1.

ERROR: <class 'chromite.lib.cros_build_lib.RunCommandError'>: return code: 32; command: sudo -n 'CROS_CACHEDIR=/b/c/cbuild/repository/.cache' 'CROS_SUDO_KEEP_ALIVE=unknown' -- mount -text4 -onoatime /dev/cros_b+c+cbuild+repository+chroot_000/chroot /b/c/cbuild/repository/chroot

mount: special device /dev/cros_b+c+cbuild+repository+chroot_000/chroot does not exist

Comment 1 by, Feb 6 2018

Looks like the VG setup didn't complete quickly enough.  The previous two runs (and all the other paladins) worked fine, so this sounds like a race condition in LVM.  I'll look into adding some retry logic.

Comment 2 by, Feb 6 2018

Summary: Paladins sometimes can't mount chroot (was: edgar-paladin can't mount chroot)
This has sporadically hit a couple of other paladins:

Looking to see if there's any commonality about when it happens.

Comment 3 by, Feb 6 2018


Comment 4 by, Feb 7 2018

Project Member
The following revision refers to this bug:

commit 31cf629aad061dbe68a77ed49240c3353eba8d23
Author: Benjamin Gordon <>
Date: Wed Feb 07 02:19:03 2018

cros_build_lib: Wait for LV to appear before mounting

Sometimes after running lvchange, the device takes a few seconds to
appear.  Check for the device and retry a couple of times as needed to
wait for it.  This is similar to the logic that was previously added to
wait for vgchange.

BUG= chromium:809570 
TEST=cros tryjob edgar-paladin-tryjob

Change-Id: I77648232a7af36285253f5267ae2f90c4dfad063
Commit-Ready: Benjamin Gordon <>
Tested-by: Benjamin Gordon <>
Reviewed-by: Benjamin Gordon <>


Comment 5 by, Feb 7 2018

Are recent failures of betty-arc64-paladin related to this? I filed Issue 809957.

Comment 6 by, Feb 7 2018

Issue 809957 has been merged into this issue.

Comment 7 by, Feb 7 2018

Status: Verified (was: Assigned)
The underlying race was triggered on one build in the latest CQ run (  The change in handled it correctly, so I'm calling this fixed.

Sign in to add a comment