Manual Installation Via the Cmd Line

Follow

Comments

125 comments

  • Matt Christian

    In the NOTE line, the parameter should be --skip_src_removable . You need the underscores _ between the terms for the chromeos-install command to process correctly.

  • Forrest Smith

    Matt:
    Thus corrected.

    Thanks for the sharp eye!

  • Matt Christian

    Forrest, found another issue: ./ should not be prefixed to the chromeos-install commands. Otherwise bash/sudo cannot find the command in the PATH.

  • Tom Miller

    If you get a "seek" failure during the messages the install will fail after reading the file blocks for a "test".
    After you answer yes I am getting the following:
    32+0 records in
    32+0 records out
    16384 bytes (16 KB) 0.0133879 s, 1.2 MB/s
    dd: '/dev/sda' : cannot seek: Invalid argument
    0+0 records in
    0+0 records out
    0 bytes (0 B) copied, 0.0143947 s, 0.0 kB/s
    Running a hw diagnostics test -- this might take a couple of minutes.....

    It does that, displays stuff to fast to read and quits.

    This also happens if you re-format the HD. The only variation on the instructions is I have switched to the command line after I have attempted to use the UI install button without logging in at all (eg. Network has been set).

    I can't even get to that setup screen again without re-loading the thumb drive and installed Flash again.

  • Mark Howell

    +1 Tom Miller's seek issue. I also could not install due to my 8 GB SATA SSD not supporting SMART error logging. Any way around that?

  • Nick Athanassov

    My installer couldn't find /usr/sbin
    I did ls and couldn't find /usr directory either.
    What am I missing?

  • Forrest Smith

    Nick,

    If you give us some more info about the specific steps you're taking, we may be able to help. What and how are you attempting this?

  • Ian Richardson

    I've followed the command above but just have counting numbers down the left hand side. This has gone on for 30+ minutes. Have I done something wrong?

  • Forrest Smith

    Ian,

    It's tough to be sure here - I'd let things run their course for another hour or so, and then cancel the install (ctrl-c).

    The most informative thing would be the immediate output after initiating the install (as compared to the running number which could just be progress or something else healthy).

    Start a new thread if you want to dog deeper please!

  • Paul Cassatta

    So how do I get to the command prompt if I have already gone through the initial setup and connected to a network?  cntrl-alt-f2 does not work.

     

  • Forrest Smith
    Paul, If ctrl alt F2 isn't working try ctrl alt Fn f2
  • Joel Alzate

    I followed the above instructions for my DELL XPS M1330 and worked like a charm. Just remember to cross your fingers...

  • Tom Miller

    X ;)

  • Torrasque Li

    Forrest Smith, I have followed your steps until I got a "A mandatory SMART command failed: existing. To continue, add one or more '-T permissive' options." message and failed.
    What should I do? Can you help me?

  • Christian Viazzo

    For whatever reason when I enter in the 'sudo fdisk -l' command it list all the drives in an sda#PUTNUMBERHERE# format, but when I go to type in the '--dst/dev/sda16' (16 is the number of my desired drive) it say that doesn't exist. I'm not sure what I'm doing wrong and I'm still going to fiddle around because I think it's something small that I'm doing wrong. Hopefully those of you that have successfully followed this process can help me out. Thank you.

  • Christian Viazzo

    nevermind, I'm just stupid, didn't put a space between '--dst' and '/dev/...'

  • Forrest Smith

    Christian -

    Also note that /dev/sda# is a partition on the drive /dev/sda. You can only install CloudReady to an entire device, not to a single partition, so you'll probably need to specify your destination as /dev/sda .

    Torrasque Li - Please open a new thread under "Machine Compatibility" and include as much info as possible about your hardware - we'll work there to see if we can get this working.

  • Christian Viazzo

    I've managed to get things rolling, but for whatever reason when I get to partition 18 in the installation everything just chokes up. I left my computer on over night let it install and when I woke up it was still on partition 18. Would this be something wrong with the harddrive or the computer itself. The computer is a HP Pavilion a1129n.

  • Christian Viazzo

    I got it to finish, but now I'm crying because it is still at a black screen. I honestly think it's the hard drive to blame.

  • ismail faisal

    Hi i cant find my drive. after fdisk NO SUCH FILE OR DIRECTORY comes up

  • Forrest Smith

    Ismail -
    Make sure you do this order:

    1) ctrl+alt+t to open a terminal
    2) type 'shell' and enter to ger a bash shell
    3) "sudo fdisk -l"

  • Brandon Jernigan

    Thanks Forrest, I followed this after getting the UEFI error upon trying to do a standalone install. This worked and I'm up and running on a Latitude D520. I crossed my fingers during the final reboot so I would recommend that to others as well.

  • Marius Perijoc

    Is there a way to install via the command line and specify dualboot? adding --dualboot to the above steps, still wants to format /dev/sda and I don't really want that :)

  • Forrest Smith

    Marius -

    your guess is exactly right - IF you specify --duaboot then the dualboot install will be attempted.

    The dualboot install, very specifically, will

    1) Find the biggest HDD or SSD
    2) Find the main Windows partition in that drive
    3) Carve out 32 GB of space on that partition
    4) In that 32GB of space the main write some buffer partitions in there, and then write CloudReady in.

    No flexibility in the process is available, but you can trigger it via cmd line.

     

    The warning that /dev/sda will be formatted is false, as long as you trigger "--dualboot" properly

  • Marius Perijoc

    Hey Forrest,

    Thanks for your answer! I'll backup the data, then try it tonight and come back with the results. I'm a bit skittish about the "fake" warning that sda will be formatted though. :)

    One more question: does it matter where the parameter goes in the fold?
    sudo chromeos-install --dst /dev/sdX --dualboot
    vs
    sudo chromeos-install --dualboot --dst /dev/sdX

    Thanks,
    Marius

  • Forrest Smith

    Marius -

    Flag order doesn't matter, no.

    Just make sure you're *totally* sure about your device name, and only specify whole devices ("/dev/sdz"), never partitions ("/dev/sdz1").

  • Marius Perijoc

    Thanks for the confirmation, and reminder! Will do!

  • Paul Essen

    Was there ever any solution to the problem mentioned by Tom Miller from November of last year? I am getting a similar error where the installer appears to just bail out back to the command line. The last thing it says is:

    Selective self-test flags (0x0):
    After scanning selected spans, do NOT read-scan remainder of disk. If Selective self-test is pending on power-up, resume after 0 minute delay.

  • Brandon B

    Getting the same problem as Tom, a hw diagnostic test starts to run and after says smartctl requires a device name. Did anyone ever figure this out?

  • Forrest Smith

    Brandon -

    If you're doing a standalone install, I'd recommend wiping the disk first before initiating install. No guarantees but it could help:
    https://neverware.zendesk.com/hc/en-us/articles/212474598-Formatting-HDD-Prior-to-Install-

Please sign in to leave a comment.