Installation failure

Comments

13 comments

  • Tony Baloney

    .... use the Chromebook Recovery Tool & give it the .zip file as input. Do NOT try to unzip it to a .bin and using THAT as input.

  • Jonas Verbickas

    I installed cloudready v64 using Chromebook Recovery Tool (i passed in the .zip file) and now the os does not even boot from the flash drive.

  • Forrest Smith

    Jonas -

    Were you using v72.3 as your installer USB source when you got the error above? I would generally recommend against using v64 or any older version. The latest has the best error handling and support for various BIOS configs, as well as Secure Boot. Using an up-to-date installer should help you avoid needing to adjust as many, if any, BIOS settings.

     

    I've never seen the particular error you saw ("0/3670 Warning, had trouble writing out superblocks.") - it seems possible that this indicates that the internal storage is broken. but I would suggest you remake your installer USB (again, use the latest images and download them new to make sure your locally stored copy isn't corrupt or something) and try again.

  • Jonas Verbickas

    I'm sorry for being such a inconvenience, but I reinstalled cloudready into my flashdrive using the provided utility for windows. And now whenever I try to install the os using the UI it bugs out, I guess, it does not make any progress. I left it to install thought the night and when I woke up and checked it was still installing.

    I have also tried to install using this method https://neverware.zendesk.com/hc/en-us/articles/213131287-Manual-Installation-Via-the-Cmd-Line But whenever I try to that it errors:

    cloudready primary gpt header is invalid

    So I formatted the HDD as described in this thread: https://neverware.zendesk.com/hc/en-us/articles/212474598-How-do-I-format-a-HDD-prior-to-install- Sadly It didn't fix the aforementioned error.

    EDIT: changed the installation method link

  • Forrest Smith

    Jonas,

    CloudReady should not hang up on install overnight if you are using v72.3 or higher on your USB stick. Can you confirm that you latest re-imaged flash drive, when you boot into it, prior to installing, shows "72.3.32" somewhere in the top right corner? If not, you should remake your stick with the latest image.

     

    If you are using the latest image, you should find that it errors out if you try again. Once it errors, you should be able to send us logs. Have you seen that flow yet?

  • Jonas Verbickas

    I double checked it's running 72.3.32. So how do I go about sending you logs?

  • Forrest Smith

    On v72.3, if you attempt to install and then see an error message, you should be prompted by the UI to send logs. 

     

    If that is not happeing for you, please instead:

    * Attempt to install

    * wait at least 20 minutes

    * reboot

    * log in without attempting to install

    * press alt+shift+i and fill out the details

  • Jonas Verbickas

    OK. I have sent 2 log reports from r.verbickiene@gmail.com.

    Now after shutting down the pc when 20 minutes of installation passed, whenever I retry the installation it errors:

    [u'/usr/sbin/chromeos-install', u'--dst', u'/dev/sda', u'--yes', u'--skip_dst_removable', u'--target_bios', u'efi'] failed. returncode: 5, output: initctl: Unknown instance: This will install from '/dev/sdb' to '/dev/sda'. This will erase all data at this destination: /dev/sda 64+0 records in 64+0 records out 32768 bytes (33 kB, 32 KiB) copied, 0.00723747 s, 4.5 MB/s WARNING: Primary GPT header is invalid E5844ABF-9F1A-C743-8F14-0FB1409C26F2 start size part contents 0 1 PMBR (Boot GUID: E5844ABF-9F1A-C743-8F14-0FB1409C26F2) 1 1 Pri GPT header 2 32 Pri GPT table 64 1 1 Label: "CRDYSTUB" Type: ChromeOS reserved UUID: 17E0AC4B-E504-2C4D-A20B-17A0B6CCA02C 65 1 2 Label: "CRDYSTUB" Type: ChromeOS reserved UUID: E9C3238C-A3AF-D04F-A734-5FE28205EDE5 66 1 3 Label: "CRDYSTUB" Type: ChromeOS reserved UUID: 0DDE1E98-AC64-B34B-8704-7868E92EEB64 67 1 4 Label: "CRDYSTUB" Type: ChromeOS reserved UUID: B2D55FEC-50E0-0A4A-8468-DB1F561D923C 68 1 5 Label: "CRDYSTUB" Type: ChromeOS reserved UUID: 5C81BA29-1A26-8C47-8ACC-08C7AB747681 69 1 6 Label: "CRDYSTUB" Type: ChromeOS reserved UUID: C49DD4FE-8958-B642-A4B8-0483D8871260 70 1 7 Label: "CRDYSTUB" Type: ChromeOS reserved UUID: 8C4F71D4-186C-4442-A9DE-B545C2B08148 71 1 8 Label: "CRDYSTUB" Type: ChromeOS reserved UUID: 09A5486A-B1A1-2847-A03F-2BF6DC08316B 72 1 9 Label: "CRDYSTUB" Type: ChromeOS reserved UUID: ADB94A9A-654B-8546-8F6F-4A040C527A65 73 1 10 Label: "CRDYSTUB" Type: ChromeOS reserved UUID: 381591C4-CC88-D442-9631-9A632E3CEA4E 74 1 11 Label: "CRDYSTUB" Type: ChromeOS reserved UUID: F25BB9A6-C647-E643-9824-55D2F95DFFF7 75 1 12 Label: "CRDYSTUB" Type: ChromeOS reserved UUID: 0C10C8AA-1802-C645-B3B1-BD470E0240F3 76 1 13 Label: "CRDYSTUB" Type: ChromeOS reserved UUID: FFC009A1-40D5-FF44-A13F-28676FACE8CE 77 1 14 Label: "CRDYSTUB" Type: ChromeOS reserved UUID: 73746133-5366-CD40-B634-A2A3FC68F7A3 78 1 15 Label: "CRDYSTUB" Type: ChromeOS reserved UUID: CE0E0260-29DC-3D43-8B90-ED2630032FC2 14929936 961843184 16 Label: "STATE" Type: Linux data UUID: BA384969-731B-0845-99A3-7D9282AE80A9 20496 32768 17 Label: "KERN-A" Type: ChromeOS kernel UUID: DCE37D29-0B52-8342-82C0-7563395620B7 Attr: priority=15 tries=15 successful=0 8687632 6242304 18 Label: "ROOT-A" Type: ChromeOS rootfs UUID: A72A2883-2B5B-ED45-9E78-165D8C7CA6E9 53264 32768 19 Label: "KERN-B" Type: ChromeOS kernel UUID: 2743BF19-46DE-7240-8A7C-A0F3CE062615 Attr: priority=0 tries=15 successful=0 2445328 6242304 20 Label: "ROOT-B" Type: ChromeOS rootfs UUID: 01040D51-DE1A-C24F-B2ED-D982AB22FB2A 16464 1 21 Label: "KERN-C" Type: ChromeOS kernel UUID: 9E5B8986-BC43-434C-A539-EF8E9C101CA7 Attr: priority=0 tries=15 successful=0 16465 1 22 Label: "ROOT-C" Type: ChromeOS rootfs UUID: BBB5848E-4676-3840-8EE0-6672163E66C1 86032 2097152 23 Label: "OEM" Type: Linux data UUID: 297A7C4F-D402-D04B-9B61-BEF20352AF48 16466 1 24 Label: "reserved" Type: ChromeOS reserved UUID: C7322AFA-4079-B846-922E-038F6AFBA704 16467 1 25 Label: "reserved" Type: ChromeOS reserved UUID: 575F70FF-F93D-F34D-923A-94295BEFDAEE 80 16384 26 Label: "RWFW" Type: ChromeOS firmware UUID: E62526AD-6979-1341-B636-365A4E5E6966 2183184 131072 27 Label: "EFI-SYSTEM" Type: EFI System Partition UUID: E5844ABF-9F1A-C743-8F14-0FB1409C26F2 Attr: legacy_boot=1 976773135 32 Sec GPT table 976773167 1 Sec GPT header Clearing the stateful partition... mke2fs 1.44.1 (24-Mar-2018) Creating filesystem with 120230398 4k blocks and 30064640 inodes Filesystem UUID: fdc3d47a-497b-40fb-9b79-b34d6bf783ee Superblock backups stored on blocks: 32768, 98304, 163840, 229376, 294912, 819200, 884736, 1605632, 2654208, 4096000, 7962624, 11239424, 20480000, 23887872, 71663616, 78675968, 102400000 Allocating group tables: 0/3670 done Writing inode tables: 0/3670 done Creating journal (262144 blocks): done Writing superblocks and filesystem accounting information: 0/3670 4/3670 Warning, had trouble writing out superblocks. , traceback: Traceback (most recent call last): File "/opt/neverware/auto_install.py", line 264, in main install(dest) File "/opt/neverware/auto_install.py", line 222, in install run_chromeos_install(dest, is_efi) File "/opt/neverware/auto_install.py", line 173, in run_chromeos_install output = run_cmd(cmd) File "/opt/neverware/auto_install.py", line 115, in run_cmd output = subprocess.check_output(cmd, stderr=subprocess.STDOUT) File "/usr/lib64/python2.7/subprocess.py", line 573, in check_output raise CalledProcessError(retcode, cmd, output=output) CalledProcessError: Command '['/usr/sbin/chromeos-install', '--dst', '/dev/sda', '--yes', '--skip_dst_removable', '--target_bios', 'efi']' returned non-zero exit status 5

  • Forrest Smith

    Here's a (hopefully more readable) version of the error from your logs:

     

    Allocating group tables:    0/3670         done                            
    Writing inode tables:    0/3670         done                            
    Creating journal (262144 blocks): done
    Writing superblocks and filesystem accounting information:    0/3670   4/3670
    Warning, had trouble writing out superblocks.
    Traceback (most recent call last):
      File "/opt/neverware/auto_install.py", line 115, in run_cmd
        output = subprocess.check_output(cmd, stderr=subprocess.STDOUT)
      File "/usr/lib64/python2.7/subprocess.py", line 573, in check_output
        raise CalledProcessError(retcode, cmd, output=output)
    CalledProcessError: Command '['/usr/sbin/chromeos-install', '--dst', '/dev/sda', '--yes', '--skip_dst_removable', '--target_bios', 'efi']' returned non-zero exit status 5

     

    As that makes slightly clearer, the device starts writing to disk and then hits a snag shortly into the series of blocks it wants to write to (blocks are, I am pretty sure here, just a convenient way to break up the storage into chunks larger than individual bits).

     

    So possibilities are:

    1) Your disk is broken, corrupt, or otherwise not able to be written to

    2) Your device's BIOS is set to prevent this kind of writing to disk (sometimes there's a security feature, "noexec" function, write-protect, etc that can be disabled in there)

    3) Your device's HDD "mode" or other setting is set to the wrong mode. Any settings you can experiment with in BIOS would be a good thing to check out and play with

    4) CloudReady has a bug with your particular type of storage - you could try replacing the physical disk in there, which should avoid either #1 or  #4 here

    5) ???

  • Jonas Verbickas

    So today I went out and bought a new SSD. Then I tried to install chrome OS and I ran into the same problems that i had with the old HDD. So I put the SSD into another system and it still woundn't install the OS. So ran back to the hardware store and I bought a new usb flash drive. AND IT WORKED LIKE A CHARM! The installation was complete in under 5 minutes!

    Thanks for all the help! Hopefully somebody will find this info useful.

  • Forrest Smith

    Glad that helped! And thanks for the feedback.

    I'm not sure why I didn't think sooner to suggest changing to a different USB. Glad to hear you did.

    What brand and size was the USB that didn't work?

  • Jonas Verbickas

    Transcend 32gb 3.1usb

Please sign in to leave a comment.