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

Issue 731840 link

Starred by 1 user

Issue metadata

Status: Archived
Owner:
Closed: Jun 2017
Cc:
EstimatedDays: ----
NextAction: ----
OS: Chrome
Pri: 2
Type: Bug



Sign in to add a comment

enguarde-release: PaygenTestDev failed with kFilesystemVerifierError before update_stateful

Project Member Reported by mcchou@chromium.org, Jun 9 2017

Issue description

Builder: enguarde-release

Build:   https://chromegw.corp.google.com/i/chromeos/builders/enguarde-release/builds/1332

Observation:
It seems to be a different issue from  crbug.com/730141  where update_stateful error came later. In build #1332, PaygenTestDev failed with ErrorCode::kFilesystemVerifierError(47) before update_stateful, and the autoupdater raise an exception about failing to complete the update command. But I am not sure about if this is related to  crbug.com/730141 , so assigned to gwendal@ for now.

Logs from https://pantheon.corp.google.com/storage/browser/chromeos-autotest-results/122412878-chromeos-test/chromeos4-row10-rack2-host21/:
06/09 07:32:50.651 DEBUG|          ssh_host:0286| Running (ssh) '/usr/bin/update_engine_client --update --omaha_url=http://100.115.219.133:60622/update'
06/09 07:32:50.860 ERROR|             utils:0298| [stderr] [0609/073250:INFO:update_engine_client.cc(471)] Forcing an update by setting app_version to ForcedUpdate.
06/09 07:32:50.861 ERROR|             utils:0298| [stderr] [0609/073250:INFO:update_engine_client.cc(473)] Initiating update check and install.
06/09 07:32:50.861 ERROR|             utils:0298| [stderr] [0609/073250:INFO:update_engine_client.cc(502)] Waiting for update to complete.
06/09 07:47:30.339 ERROR|             utils:0298| [stderr] [0609/074730:ERROR:update_engine_client.cc(217)] Update failed, current operation is UPDATE_STATUS_IDLE, last error code is ErrorCode::kFilesystemVerifierError(47)
06/09 07:47:30.341 DEBUG|       autoupdater:0175| exception in update handler: command execution error
* Command: 
    /usr/bin/ssh -a -x    -o ControlPath=/tmp/_autotmp_S5aVTOssh-
    master/socket -o StrictHostKeyChecking=no -o UserKnownHostsFile=/dev/null
    -o BatchMode=yes -o ConnectTimeout=30 -o ServerAliveInterval=900 -o
    ServerAliveCountMax=3 -o ConnectionAttempts=4 -o Protocol=2 -l root -p 22
    chromeos4-row10-rack2-host21 "export LIBC_FATAL_STDERR_=1; if type
    \"logger\" > /dev/null 2>&1; then logger -tag \"autotest\"
    \"server[stack::GenericRetry|_base_update_handler_no_retry|wrapper] ->
    ssh_run(/usr/bin/update_engine_client --update
    --omaha_url=http://100.115.219.133:60622/update)\";fi;
    /usr/bin/update_engine_client --update
    --omaha_url=http://100.115.219.133:60622/update"
Exit status: 1
Duration: 879.60787487

stderr:
[0609/073250:INFO:update_engine_client.cc(471)] Forcing an update by setting app_version to ForcedUpdate.
[0609/073250:INFO:update_engine_client.cc(473)] Initiating update check and install.
[0609/073250:INFO:update_engine_client.cc(502)] Waiting for update to complete.
[0609/074730:ERROR:update_engine_client.cc(217)] Update failed, current operation is UPDATE_STATUS_IDLE, last error code is ErrorCode::kFilesystemVerifierError(47)
06/09 07:47:30.343 DEBUG|        retry_util:0133| ending retries with error: <class 'autotest_lib.client.common_lib.error.AutoservRunError'>(command execution error
* Command: 
    /usr/bin/ssh -a -x    -o ControlPath=/tmp/_autotmp_S5aVTOssh-
    master/socket -o StrictHostKeyChecking=no -o UserKnownHostsFile=/dev/null
    -o BatchMode=yes -o ConnectTimeout=30 -o ServerAliveInterval=900 -o
    ServerAliveCountMax=3 -o ConnectionAttempts=4 -o Protocol=2 -l root -p 22
    chromeos4-row10-rack2-host21 "export LIBC_FATAL_STDERR_=1; if type
    \"logger\" > /dev/null 2>&1; then logger -tag \"autotest\"
    \"server[stack::GenericRetry|_base_update_handler_no_retry|wrapper] ->
    ssh_run(/usr/bin/update_engine_client --update
    --omaha_url=http://100.115.219.133:60622/update)\";fi;
    /usr/bin/update_engine_client --update
    --omaha_url=http://100.115.219.133:60622/update"
Exit status: 1
Duration: 879.60787487
 
Cc: diand...@chromium.org
Owner: ----
looking into the messages file I see real mmc error:
2017-06-09T07:35:31.031961-07:00 ERR kernel: [  195.292092] blk_update_request: I/O error, dev mmcblk0, sector 21079
2017-06-09T07:35:31.031966-07:00 ERR kernel: [  195.292099] Buffer I/O error on dev mmcblk0p2, logical block 74, async page read

The eMMC use MMC 4.5 so I can not see how old the eMMC is.

Looks like a hardware error to me.

I've locked the device. Looking at it's history, it has a lot of provision failures, but sees occasional success.
b/62496539 covers getting the hardware swapped out.
Cc: jrbarnette@chromium.org
Owner: dgarr...@chromium.org
Status: Fixed (was: Untriaged)
Marking this fixed in favor of the other bug.

Comment 5 by dchan@chromium.org, Jan 22 2018

Status: Archived (was: Fixed)

Sign in to add a comment