Acer c710 recovery_reason: 0x02 recovery button pressed

[harry rokytnji]

Some history on this issue. I opened my one screw back cover plate to look at the hard drive bay size for upgrading the ssd.
Closed it back up. Rebooted.
I was greeted with the screen "Chrome OS is missing or damaged. Please insert a USB stick."

NOT panicking I grabbed my 4 gig sandisk recovery usb I made when I first recieved my chromebook in the mail.
I let it verify and was displayed the
Unexpected error
error message

My recovery image is PARROT DORADO A-5111

Netbook specs:

• Screen Size: 11.6"
• Screen Resolution: 1366 x 768
• Processor Type: Intel
• Processor Model: Celeron 847
• Processor Speed: 1.1GHz
• Processor Core: Dual-core
• Cache: 2MB
• Operating System: Chrome OS
• System Memory (RAM): 4GB
• RAM Expandable To: 4GB
• Type of Memory (RAM): DDR3
• Hard Drive Type: SSD
• Hard Drive Size: 16GB
• Hard Drive RPM: Not Available
• Optical Drive Type: Not Available
• Optical Drive Speeds: Not Available
• Digital Media Reader: Yes
• Graphics: Intel HD
• Video Memory: Shared
• Built-in Webcam: Yes
• Networking: Integrated 10/100Mbps
• Wireless Networking: Wi-Fi 802.11a/b/g/n
• Bluetooth-Enabled: Not Available
• USB Ports: 3
• Battery Life: 3.5hrs
• System Version: Not Available
• HDMI Output: Yes
• Included Software: Not Available
• Graphics Chip: Not Available
• Display Screen Type: Active Matrix TFT Color LCD LED
• Display Screen Technology: CineCrystal
• ENERGYSTAR Qualified: Yes
• Dimensions: 11.2" x 1.1" x 8.0"
• Product Weight: 3lbs
• Product Number: C710-2457

I have made recovery media using pny 8gig, kingston 4 gig, HP 4gig, and Sandisk 4 gig usb flash drives. Using Windows recovery tool, Linux.sh recovery tool.
Chrome Browser recovery center tool.

Still would get the unexpected error message. So I figured. I'll buy me "A 7MM Kingston 60 gig ssd now" drive and try recovery with that in case something happened with the 16gig ssd drive. Still received the  unexpected error message

Recovery media was made on pny,kingston,HP,and Sandisk flash drives. 4 gig or 8 gig. Same error. Recovery media was made on Linux.sh recovery file, ChromeOS recovery for Windows .exe, and also Chrome Browser recovery center. No joy in using any of these methods to get rid of the "unexpected error" message.

I even bought a 60 gig Kingston SSD Now V300 7mm SV300S37A/60G that dropped right in hoping this would fix this error. No joy going that route either.

So I contact a ninja. Our emails"

to me

Thanks for contacting the Chrome Ninja Team.

You’ll hear from us shortly. In the meantime, visit the Chrome Device Help Center at http://support.google.com/chromeos to see available troubleshooting information.

If you have other questions or concerns, just reply to this email.

Thanks,
The Chrome Ninja Team

 

Hi Harry,

Thank you for contacting Google. My name is Jonathan and I would be happy to assist you today.

If you are having trouble recovering, when you get to the recovery screen, please press the tab key on your keyboard. This should trigger the page to give you a recovery_reason or Recovery Reason code.

Please let me know what message and code it gives you so I can help you with the next steps.

Thanks,

Jonathan
The Chrome Ninja Team

My reply:

 

to chromeos-suppo.

HWID: PARROT DORADO A-E 5111

recovery_reason: 0x5a No bootable storage device in system

VbSD, flags: 0x00000640

VbNv, raw, 70 00 00 00 00 00 00 00 00 00 00 00 00 00 00 20

dev_boot_usb: 0

dev_boot_signed_only: 0

TPM: fwver=0x00010003 kernver=0x00030001

gbb.flags: 0x00000000

gbb.rootkey: 9f59876c7f7dc881f02d934786c6b7c2c17daac

gbb.recovery_key: 7f03c648d2bb4ab3979cb87633da51ed90267f03

read-only firmware id: Google_Parrot.2685.54.0

active firmware id: Google Parrot.2685.54.0

This is with the Kingston 7mm 60 gig sata ssd inserted. If I need to put the 16 gig original ssd back in. Let me know.

My preference is to run the chromebook with the 60 gig Kingston though since I bought it new in the package.

But if it makes a difference. I will re-insert the 16gig Sandisk SSD. I just want it to work.

Ninjas reply:

 

to me

Hi Harry,

Thank you for contacting Google.

The Chromebook is designed to only work with specific hardware so I would suggest putting back the original SSD if you have already removed it. If you still get the same error with the original SSD, you will want to look into repair options for your Chromebook with Acer. Since you have already removed the hard drive, your warranty will be void with Acer however you still can contact them here:

ACER site: http://us.acer.com/ac/en/US/content/service

If you have any more questions, please reply to this email so I can continue to assist you.

So. I am here hoping to find some more knowledgeable answer on my problem. I have reinserted the 16gig Sandisk stock ssd again. Pressing the tab key gives this error message
on the screen

HWID:PARROT DORADO A-E 5111
recovery_reason: 0x02 recovery button pressed
VbSD.flags:0x000000670
VbNv.raw: 70 20 00 00 00 00 00 00 00 00 00 00 00 d4
dev_boot_usb: 0
dev_boot_signed_only: 0
TPM: fwver=0x00010003 kernver=0x00030001
gbb.flags: 0x000000000
gbb.rootkey: 9f59876c7f7dc881f02d934786c667c2c17dcaac
gbb.recovery_key: 7f03c648d2bb4ab3979cb87633da51ed90267f03
read-only firmware id: Google_Parrot.2685.54.0
active firmware id: Google Parrot.2685.54.0

Having myself checked out https://johnlewis.ie/mediawiki/index.php?title=Flashing_stock_firmware_to_a_coreboot_build_on_Acer_C7_%28C710%29

It seems that ChromeOS must be running to flash the bios to enable usb booting so I could install a linux operating system
since Chrome OS will not recover. Kind of a catch 22 type of situation.
I am comfortable running Linux operating systems and using command line in a terminal shell environment.
I am comfortable in maneuvering via command line through a linux file structure.

 harry@biker1:~$ ls
boot_messages  Documents  Music     Public     screeny    Videos
Desktop        Downloads  Pictures  puppy_iso  Templates  Wallpaper
harry@biker1:~$ cd puppy_iso
harry@biker1:~/puppy_iso$ ls
puppy-arcade-11-k2.6.32.59.iso
harry@biker1:~/puppy_iso$
harry@biker1:~/puppy_iso$ cd ~
harry@biker1:~$ cat /etc/issue
Ubuntu 14.04.1 LTS \n \l

So I am not a unexperienced computer user. This Acer C710 chromebook was not mistreated. It has hardly any use on it also. It is only a few months old. I hope I have given enough info on my problem.

Happy Trails, Rok



[harry rokytnji]

Just info on how I ran linuxrecovery.sh

harry@biker1:~/ChromeOS_recoverysh$ sudo chmod 755 linux_recovery.sh
[sudo] password for harry:
harry@biker1:~/ChromeOS_recoverysh$ sudo bash linux_recovery.sh
Working in /tmp/tmp.crosrec/
Downloading config file from https://dl.google.com/dl/edgedl/chromeos/recovery/recovery.conf

If you know the Model string displayed at the recovery screen,
type some or all of it; otherwise just press Enter: PARROT DORADO A-E 5111

This may take a few minutes to print the full list...

There are 32 recovery images to choose from:

0 - <quit>
1 - Lenovo Thinkpad X131e Chromebook 2GB
      channel:  stable-channel
2 - LG Chromebase
      channel:  stable-channel
3 - HP Pavilion Chromebook
      channel:  stable-channel
4 - Lenovo N20 Chromebook
      channel:  stable-channel
5 - HP Chromebook
      channel:  stable-channel
6 - HP Chromebook 11
      channel:  stable-channel
7 - Samsung Chromebook
      channel:  stable-channel
8 - HP Chromebook 14
      channel:  stable-channel
9 - Lenovo ThinkPad 11e Chromebook
      channel:  stable-channel
10 - Toshiba Chromebook
      channel:  stable-channel
11 - Google Chromebook Pixel
      channel:  stable-channel
12 - Samsung Chromebook Series 5 550
      channel:  stable-channel
13 - ASUS Chromebox
      channel:  stable-channel
14 - Acer C7 Chromebook IVB
      channel:  stable-channel
      model:    PARROT DORADO A-E 5111
15 - Acer C7 Chromebook
      channel:  stable-channel
16 - Samsung Chromebook 2 13"
      channel:  stable-channel
17 - Samsung Chromebook 2 11"
      channel:  stable-channel
18 - Asus Chromebook C300
      channel:  stable-channel
19 - Asus Chromebook C200
      channel:  stable-channel
20 - Lenovo Thinkpad X131e Chromebook
      channel:  stable-channel
21 - Dell Chromebook 11
      channel:  stable-channel
22 - Samsung Chromebook Series 5 US-Wifi
      channel:  stable-channel
23 - Samsung Chromebook Series 5 Non-US-Wifi
      channel:  stable-channel
24 - Samsung Chromebook Series 5 Non-US 3G
      channel:  stable-channel
25 - Samsung Chromebook Series 5 US-3G
      channel:  stable-channel
26 - Cr-48
      channel:  stable-channel
27 - Acer AC700-1099 Wifi
      channel:  stable-channel
28 - Acer AC700-1529 3G
      channel:  stable-channel
29 - HP Chromebox
      channel:  stable-channel
30 - Acer C720 Chromebook
      channel:  stable-channel
31 - Samsung Chromebox Series 3
      channel:  stable-channel
32 - Education Chromebook
      channel:  stable-channel

Please select a recovery image to download: 14

Downloading image zipfile from https://dl.google.com/dl/edgedl/chromeos/recovery/chromeos_5712.88.0_parrot-ivb_recovery_stable-channel_mp-v3.bin.zip

  % Total    % Received % Xferd  Average Speed   Time    Time     Time  Current
                                 Dload  Upload   Total   Spent    Left  Speed
 60  459M   60  279M    0     0   363k      0  0:21:34  0:13:08  0:08:26  364k
<snip>
 % Total    % Received % Xferd  Average Speed   Time    Time     Time  Current
                                 Dload  Upload   Total   Spent    Left  Speed
100  459M  100  459M    0     0   362k      0  0:21:38  0:21:38 --:--:--  364k
Unpacking the zipfile
Archive:  chromeos_5712.88.0_parrot-ivb_recovery_stable-channel_mp-v3.bin.zip
  inflating: chromeos_5712.88.0_parrot-ivb_recovery_stable-channel_mp-v3.bin 
I found 1 USB drive.  We need one with at least 1490MB capacity.

0 - <quit>

1 - Use /dev/sdb 8166MB PNY      USB 2.0 FD     


Tell me what to do (or just press Enter to scan again): 1

Is this the device you want to put the recovery image on?

  /dev/sdb 8166MB PNY      USB 2.0 FD     

You must enter 'YES' (all uppercase) to continue: YES


I'm really going to erase this device. This will permanently ERASE
whatever you may have on that drive. You won't be able to undo it.

  /dev/sdb 8166MB PNY      USB 2.0 FD     

If you're sure that's correct, enter 'DoIt' now (case is important): DoIt


Installing the recovery image


unmounting...
copying... (this may take several minutes)
372+1 records in
373+0 records out
1564475392 bytes (1.6 GB) copied, 318.075 s, 4.9 MB/s


Done. Remove the USB drive and insert it in your Chrome notebook.


Shall I remove the temporary files now? [y/n] y
harry@biker1:~/ChromeOS_recoverysh$

--
--
Chromium OS discuss mailing list: chromium-...@chromium.org
View archives, change email options, or unsubscribe:
http://groups.google.com/a/chromium.org/group/chromium-os-discuss?hl=en

To unsubscribe from this group and stop receiving emails from it, send an email to chromium-os-dis...@chromium.org.

[Mike Frysinger]

not all hard drives work which is why trying to use recovery won't always help.  the fact that your message stated:

  0x5a No bootable storage device in system

that means the firmware couldn't find any disks in your system.  put in the original drive and check the physical connections.

the second message you quoted:

  0x02 recovery button pressed

that happens when you ... press the recovery button.  so don't press it when you boot.  power it off, then just press the power button.

-mike

[harry rokytnji]

Thanks for the reply Mike. I t have read a lot of your posts so know you walk the walk so to speak.
I figured the Kingston lacked a GPT flag or something like that for the Acer to pick it up.
My 16 gig is acting flacky where the error message changes form 0x02 to now oxo5 no bootable media found.
So I may have a lemon sandisk ssd since the error message changed on me with no extra anything done from me.
I will recheck connections, the ribbon and the mini sata slots.
I may have to save up again and just buy another sandisk 16 gig ssd.
Again, thanks for reading and replying.
If I find out anything new. I will come back here and report on what I did to get it working.

Happy Trails, Rok

[Mike Frysinger]

there were threads in the past (i think in the chromebook central google groups) where people detailed exact hd models that they used in the C710 that were known to work.  unfortunately, we really only test the specific ssd/hdd models that ship rather than do a larger survey of devices, so usually by the time we notice & fix a bug, it missed the release for the platform and only helps newer devices.

note that you aren't really in a catch 22 wrt damaged hd's -- once you put your system into dev mode, you can always boot directly from USB (not a recovery image) and then run whatever you like.  of course, you really need the firmware to recognize the ssd/hdd as booting from USB all the time would be a pita.

-mike

[Randall Spangler]

If you're really feeling ambitious, and since you've cracked the case anyway, you can remove the firmware write protect screw and rekey the machine with dev keys.  That won't help with your SSD, but it will make the system recognize your dev-built USB key as a valid recovery image.  So when it fails to find the SSD, it'll at least automatically boot your USB key (rather than needing you to press Ctrl+U at the dev warning screen).

The usual warnings about playing with normally-read-only firmware apply here; if something goes wrong with the process you'll have a completely unbootable brick.

[Richard Barnette]

On 8/25/14, 1:34 AM, Mike Frysinger wrote:
> not all hard drives work which is why trying to use recovery won't
> always help. the fact that your message stated:
> 0x5a No bootable storage device in system
> that means the firmware couldn't find any disks in your system. put in
> the original drive and check the physical connections.
>

Recovery error 0x5a is pretty definitive: The new SSD isn't
working. And like vapier@ has suggested, the two likely
explanations are either an unsupported SSD device, or a poorly
seated connection.

The recovery software on the USB stick actually provides more
information. Plug your stick into a convenient Linux system,
and mount partition 1 off of the stick. In the mounted file
system, you'll find a file named 'log/recovery.log'. That's
got 'sh -x' output from the recovery installation procedure.

Given what you've said so far, I think what you'll find is that
the chromeos-recovery script complains about the install target
device. As it happens, that script will try to run disk
diagnostics in the event of failure, so there may be more
information in the logs.

> the second message you quoted:
> 0x02 recovery button pressed
> that happens when you ... press the recovery button. so don't press it
> when you boot. power it off, then just press the power button.
> -mike
>
>
> On Mon, Aug 25, 2014 at 3:27 AM, harry rokytnji <hkh...@gmail.com
> <mailto:hkh...@gmail.com>> wrote:
>
> Some history on this issue. I opened my one screw back cover plate
> to look at the hard drive bay size for upgrading the ssd.
> Closed it back up. Rebooted.
> I was greeted with the screen "Chrome OS is missing or damaged.
> Please insert a USB stick."
>
> NOT panicking I grabbed my 4 gig sandisk recovery usb I made when I
> first recieved my chromebook in the mail.
> I let it verify and was displayed the
> Unexpected error
> error message
>
> My recovery image is PARROT DORADO A-5111
>
> Netbook specs:
>
>

> # *Screen Size: *11.6"
> # *Screen Resolution: *1366 x 768
> # *Processor Type: *Intel
> # *Processor Model: *Celeron 847
> # *Processor Speed: *1.1GHz
> # *Processor Core: *Dual-core
> # *Cache: *2MB
> # *Operating System: *Chrome OS
> # *System Memory (RAM): *4GB
> # *RAM Expandable To: *4GB
> # *Type of Memory (RAM): *DDR3
> # *Hard Drive Type: *SSD
> # *Hard Drive Size: *16GB
> # *Hard Drive RPM: *Not Available
> # *Optical Drive Type: *Not Available
> # *Optical Drive Speeds: *Not Available
> # *Digital Media Reader: *Yes
> # *Graphics: *Intel HD
> # *Video Memory: *Shared
> # *Built-in Webcam: *Yes
> # *Networking: *Integrated 10/100Mbps
> # *Wireless Networking: *Wi-Fi 802.11a/b/g/n
> # *Bluetooth-Enabled: *Not Available
> # *USB Ports: *3
> # *Battery Life: *3.5hrs
> # *System Version: *Not Available
> # *HDMI Output: *Yes
> # *Included Software: *Not Available
> # *Graphics Chip: *Not Available
> # *Display Screen Type: *Active Matrix TFT Color LCD LED
> # *Display Screen Technology: *CineCrystal
> # *ENERGYSTAR Qualified: *Yes
> # *Dimensions: *11.2" x 1.1" x 8.0"
> # *Product Weight: *3lbs
> # *Product Number: *C710-2457

>
>
>
> I have made recovery media using pny 8gig, kingston 4 gig, HP 4gig,
> and Sandisk 4 gig usb flash drives. Using Windows recovery tool,
> Linux.sh recovery tool.
> Chrome Browser recovery center tool.
>
> Still would get the unexpected error message. So I figured. I'll buy
> me "A 7MM Kingston 60 gig ssd now" drive and try recovery with that
> in case something happened with the 16gig ssd drive. Still received
> the unexpected error message
>
> Recovery media was made on pny,kingston,HP,and Sandisk flash drives.
> 4 gig or 8 gig. Same error. Recovery media was made on Linux.sh
> recovery file, ChromeOS recovery for Windows .exe, and also Chrome
> Browser recovery center. No joy in using any of these methods to get
> rid of the "unexpected error" message.
>
> I even bought a 60 gig Kingston SSD Now V300 7mm SV300S37A/60G that
> dropped right in hoping this would fix this error. No joy going that
> route either.
>
> So I contact a ninja. Our emails"
>
>
> to me

> Thanks for contacting the Chrome Ninja Team.
>
> You’ll hear from us shortly. In the meantime, visit the Chrome

> Device Help Center at http://support.google.com/chro__meos

> <http://support.google.com/chromeos> to see available
> troubleshooting information.
>
> If you have other questions or concerns, just reply to this email.
>
> Thanks,
> The Chrome Ninja Team
>
> Hi Harry,
>
> Thank you for contacting Google. My name is Jonathan and I would
> be happy to assist you today.
>
> If you are having trouble recovering, when you get to the
> recovery screen, please press the tab key on your keyboard. This
> should trigger the page to give you a recovery_reason or
> Recovery Reason code.
>
> Please let me know what message and code it gives you so I can
> help you with the next steps.
>
> Thanks,
>
> Jonathan
> The Chrome Ninja Team
>
>
> My reply:
>
>
> to chromeos-suppo.

> HWID: PARROT DORADO A-E 5111
> recovery_reason: 0x5a No bootable storage device in system
> VbSD, flags: 0x00000640
> VbNv, raw, 70 00 00 00 00 00 00 00 00 00 00 00 00 00 00 20
> dev_boot_usb: 0
> dev_boot_signed_only: 0
> TPM: fwver=0x00010003 kernver=0x00030001
> gbb.flags: 0x00000000

> gbb.rootkey: 9f59876c7f7dc881f02d934786c6b7__c2c17daac
> gbb.recovery_key: 7f03c648d2bb4ab3979cb87633da51__ed90267f03

> read-only firmware id: Google_Parrot.2685.54.0
> active firmware id: Google Parrot.2685.54.0
>
> This is with the Kingston 7mm 60 gig sata ssd inserted. If I
> need to put the 16 gig original ssd back in. Let me know.
> My preference is to run the chromebook with the 60 gig Kingston
> though since I bought it new in the package.
> But if it makes a difference. I will re-insert the 16gig Sandisk
> SSD. I just want it to work.
>
>
>
> Ninjas reply:
>
>
> to me

> Hi Harry,
>
> Thank you for contacting Google.
>
> The Chromebook is designed to only work with specific hardware
> so I would suggest putting back the original SSD if you have
> already removed it. If you still get the same error with the
> original SSD, you will want to look into repair options for your
> Chromebook with Acer. Since you have already removed the hard
> drive, your warranty will be void with Acer however you still
> can contact them here:
>

> ACER site: http://us.acer.com/ac/en/US/__content/service

> <mailto:chromium-...@chromium.org>

> View archives, change email options, or unsubscribe:
> http://groups.google.com/a/chromium.org/group/chromium-os-discuss?hl=en
>
>
> --
> --
> Chromium OS discuss mailing list: chromium-...@chromium.org
> View archives, change email options, or unsubscribe:
> http://groups.google.com/a/chromium.org/group/chromium-os-discuss?hl=en
>

--
--jrb

[harry rokytnji]

I have the 16 gig ssd pulled out. It is acting pretty flaky folks. I am using a external sata to usb with external power supply harness so you can maybe imagine what I am going to describe next.

I tried using the Chrome Browser uninstall gear to erase a recovery usb drive of recovery media. But it did not see the ssd drive through my harness. So one idea shot to hell.

I made myself a live gparted 0.19.1-1.i486 live cdrw disk. Booted it up and gparted saw the ssd as /dev/sdb. All those little partitions and one big partition showed and I was a happy camper. Finally. Something I could see. So first. I unmounted and deleted everything till I had a empty drive. Apply and done. Then I told gparted to make me a new partition table of the whole drive and to write it as GPT. (This is all poke and hope trial and error from a harley riding linux user with a GED education).

So apply and done. Then I tell it to make me a new partition and format it as ext4 file system and I label it as /. This is just just done out of practice and linux experience.
Apply and done. I put the chrome book back together.

Recovery message on tab key 0x05a - no bootable media found.
So as a experiment.
I hold the escape and refresh key and hit the power button. Then the tab key because I do not not get the dev mode screen with the red explanation point.
tab error message states: 0x02 : recovery button pressed.

either way. If I insert the 8 gig pny recovery usb. Unexpected error with the google url shows.

So I guess 0x02 is a red herring and the main error is that 16gig original Sandisk ssd of mine is flaky. That 0x05a is the real and only error. I seem to habe induced the 0x02 error with my using the esc+refresh+powerbutton then tab after getting a recovery screen. My bad on that.

I say flaky because I pulled it out again. Hooked it up to the external sata to usb harness.

~ # dmesg | tail
[  209.172126] Buffer I/O error on device sdb, logical block 0
[  209.172196] ldm_validate_partition_table(): Disk read failed.
[  209.172219] Dev sdb: unable to read RDB block 0
[  209.172252]  sdb: unable to read partition table
[  209.172441] sd 7:0:0:0: [sdb] READ CAPACITY failed
[  209.172445] sd 7:0:0:0: [sdb] 
[  209.172446] Result: hostbyte=DID_NO_CONNECT driverbyte=DRIVER_OK
[  209.172449] sd 7:0:0:0: [sdb] Sense not available.
[  209.172477] sd 7:0:0:0: [sdb] Attached SCSI disk
[  986.488753] perf interrupt took too long (2509 > 2500), lowering kernel.perf_event_max_sample_rate to 50000


It won't mount in Linux though I formatted as ext4 and labeled it root. It won't show in gparted sometimes, then it shows.
Like my dogs sometimes. Sometimes they come when I call. Sometimes they act deaf. It takes a bag of fritos being shaken
for them to hear me all of a sudden. I have not had this chromebook long or booted it maybe more than 50 times.
But I seem to be all thumbs with it.

But I promised to give a update on what I tried. And it looks like this hole is getting deeper.
I am grinning as I write this so don't take me wrong.
I think I need to buy me another used sandisk 16gig ssd from ebay that was "washed" .

Next step is to try the 60 gig 7mm Kingston ssd now drive. What I did with the sandisk 16 gig ssd. I also did the same on the Kingston.
Maybe I'll get lucky. Maybe not. I'll see here later on today.

Thats all folks. Happy Trails, Rok

[harry rokytnji]

so there may be more
information in the logs.

Made a pastebin in case anyone is interested

I have not looked through yet in detail myself yet. Just posting the link for reference later.

 

[Richard Barnette]

On 8/25/14, 12:12 PM, harry rokytnji wrote:
>
>
> so there may be more
> information in the logs.
>
>

> Made a pastebin <http://pastebin.com/1DAitYAE> in case anyone is interested

>
> I have not looked through yet in detail myself yet. Just posting the
> link for reference later.
>

OK. The executive summary of the log is that recovery failed to
find a destination device for the install. Apparently, the only
disk storage that the kernel found was the USB stick. This is
consistent with the 0x5a error from the firmware, so you're back
to "check device seating; if that doesn't work, try a brand/model
of SSD that has a track record of success."

>
>
>
> --
> --
> Chromium OS discuss mailing list: chromium-...@chromium.org
> View archives, change email options, or unsubscribe:
> http://groups.google.com/a/chromium.org/group/chromium-os-discuss?hl=en
>

--jrb

[harry rokytnji]

Closing this thread with the following because I am out of ideas.

Tried the Kingston as a GPT formatted as ext4, then tried ext2 file systems. No joy.

Pulled the Apple GPT 180 gig ssd drive I use in another laptop I have. No joy.

Tried the 16 gig in my Samsung RV 510 laptop and booted gparted live iso and formatted as msdos partition and fat32. No joy in the Acer.

All give 0x05a . Since I don't even know how to format the original drive (16gig SSD ) so it passes Acer drm muster.

I am outa ideas. But. I gave it a good try I guess. I can use the 16 gig drive on other projects. I guess I'll have to spring for a used
Acer C710 washed drive and go from there.

Thanks for the ideas and support folks. I really appreciate it. It just was not meant to be I guess.
Leaving with a link I started this idea/experiment off with.

The part that snagged me.

Kingston SSDNow V300 Series SV300S37A/120G 2.5" 120GB SATA III Internal Solid State Drive (SSD)

120G

7mm, sata 3 (6Gb/sec). This drive initially had issues, but writing the GPT seemed to correct the issue and install was successful.

Happy Trails, Rok
All connections were triple checked.