New issue
Advanced search Search tips
Starred by 1 user

Issue metadata

Status: Archived
Owner: ----
Closed: Feb 2018
EstimatedDays: ----
NextAction: ----
OS: Chrome
Pri: 2
Type: Feature

Sign in to add a comment

Issue 680528: ChromeOS faulty SSD recognition process / end user notification completely broken

Reported by, Jan 12 2017

Issue description

UserAgent: Mozilla/5.0 (X11; CrOS x86_64 8872.76.0) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/55.0.2883.105 Safari/537.36
Platform: 8872.76.0 (Official Build) stable-channel auron_paine

Steps to reproduce the problem:
1. Break your Chromebook SSD
2. Restart your Chromebook with a recovery USB stick prepared
3. Start the recovery process from the USB stick
4. After integrity verification the installation/recovery process ends in "An unexpected error has occurred" message pointing to the Google Chromebook support pages

What is the expected behavior?
When Chromebook cannot book ChromeOS or start a recovery installation from a recovery USB *due to* an unrecognizable, broken, or faulty SSD, the UI should tell the end user so.

Only way to find out about the broken SSD is to press TABULATOR during one of the error screens. It then displays some boot log.

It would be really nice to have the official, normal UI clearly state that the Chromebook's SSD is broken or it cannot be found. The current behaviour leads to confusion: is the _unexpected error_ about the USB stick that you have flashed since it popped up right after USB stick integrity verification?

What went wrong?
The UI doesn't clearly state that the SSD is broken when a Chromebook cannot find it but gives a confusing error message that has no real value and leads to confusion.

Did this work before? No 

Chrome version: 55.0.2883.105  Channel: stable
OS Version: 8872.76.0
Flash Version: Shockwave Flash 24.0 r0

I understand that this is not going to be a priority feature for any dev, but it would be really nice to have it. I spent a couple of hours flashing my USB sticks only to find out that the error message had nothing to do with them even though it seemed like that.

Thank you very much!

Comment 1 by, Feb 14 2017

Components: Platform>Apps>RecoveryTool Internals>Installer

Comment 2 by, Feb 15 2018

Project Member
Status: Archived (was: Unconfirmed)
Issue has not been modified or commented on in the last 365 days, please re-open or file a new bug if this is still an issue.

For more details visit - Your friendly Sheriffbot

Sign in to add a comment