New issue
Advanced search Search tips

Issue 922113 link

Starred by 3 users

Issue metadata

Status: Unconfirmed
Owner: ----
Components:
EstimatedDays: ----
NextAction: ----
OS: Chrome
Pri: 2
Type: Bug

Blocked on:
issue 912801



Sign in to add a comment

Chromebox 3 hanging, no video output, file system & storage errors

Reported by josh@arreya.com, Jan 15

Issue description

UserAgent: Mozilla/5.0 (X11; CrOS x86_64 11151.59.1) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/71.0.3578.94 Safari/537.36
Platform: 11151.59.0 (Official Build) stable-channel fizz-unibuild (fizz jax kench sion teemo wukong)

Steps to reproduce the problem:
1. Setup Chromebox 3 in Kiosk mode
2. Wait
3. Observe Chromebox unresponsive, no video output

What is the expected behavior?

What went wrong?
We are seeing multiple devices deployed in single app kiosk mode failing to boot with no video output, and no signs of life. Power indicator shows solid white during this state. Have tried restarting with recovery button pressed, and disabling OS verification, then re-enabling to 'reset' device, this is unsuccessful and will return to hanging state with no video output on reboot.

Attached are device logs from multiple devices exhibiting the issue. All these devices were purchased and deployed over the last 2-8 weeks. 

Devices with daily log upload enabled in admin console have filesystem errors, write failures and hardware warnings prior to becoming unresponsive. We cannot get devices logs after they become unresponsive.

-----

2019-01-10T21:41:18.122948-06:00 ERR kernel: [46284.379563] ata2.00: failed command: WRITE FPDMA QUEUED  [Reason: Warning:Failure to write to storage] 
2019-01-10T21:41:18.122950-06:00 ERR kernel: [46284.379576] ata2.00: cmd 61/08:58:d8:f0:05/00:00:01:00:00/40 tag 11 ncq 4096 out
2019-01-10T21:41:18.122952-06:00 ERR kernel: [46284.379576]          res 40/00:a8:60:d8:85/00:00:01:00:00/40 Emask 0x50 (ATA bus error  [Reason: ALERT!!:Hardware device warning] )

2019-01-11T21:49:35.076876-06:00 WARNING kernel: [133182.450308] EXT4-fs warning (device sda1): ext4_end_bio:330: I/O error -5 writing to inode 261916 (offset 0 size 0 starting block 3218319)
2019-01-11T21:49:35.076879-06:00 ERR kernel: [133182.450317] Buffer I/O error on device sd  [Reason: ALERT!!:Hardware issue with solid state storage] a1, logical block 1081742
2019-01-11T21:49:35.076881-06:00 WARNING kernel: [133182.450339] EXT4-fs warning (device sda1): ext4_end_bio:330: I/O error -5 writing to inode 261916 (offset 0 size 0 starting block 3218320)
2019-01-11T21:49:35.076883-06:00 ERR kernel: [133182.450347] Buffer I/O error on device sd  [Reason: ALERT!!:Hardware issue with solid state storage] a1, logical block 1081743
2019-01-11T21:49:35.076885-06:00 WARNING kernel: [133182.450377] JBD2: Detected IO errors while flushing file data on sda1-8

2019-01-11T21:49:35.076893-06:00 ERR kernel: [133182.450409] Aborting journal on device  [Reason: ALERT!!:Filesystem error]  sda1-8.

2019-01-11T21:49:35.076911-06:00 CRIT kernel: [133182.450597] EXT4-fs error  [Reason: ALERT!!:Filesystem error]  (device sda1) in ext4_da_write_end:2914: IO failure

Did this work before? N/A 

Chrome version: 71.0.3578.94  Channel: stable
OS Version: 11151.59.0
Flash Version:
 
Logs attached
logs_20190114-2355.zip
243 KB Download
logs_20190113-1155.zip
177 KB Download
m_cb3.zip
372 KB Download
g_cb3.zip
153 KB Download
More logs attached
logs_20190112-0652.zip
372 KB Download
logs_20190111-0651.zip
508 KB Download
logs_20190109-0857.zip
214 KB Download

Comment 3 by gwendal@google.com, Jan 16 (6 days ago)

Blockedon: 912801

Sign in to add a comment