Need help with installation getting an error message!!

Comments

19 comments

  • Forrest Smith

    Hi,

     

    Our documentation lists that installing this way will not work for dualboot.

     

    Instead: try running 

    sudo python /opt/neverware/auto_install.py --dualboot 

    and post any errors you see

    0
    Comment actions Permalink
  • Vignesh Mohit Mohan

    Hi forrest,
    Thanks for the quick reply.
    I did just run that code and it returned the following:
    Raise calledprocesseserror(recode, cmd, output=output)
    Subprocess. Calledprocesseserror:command '[' (the old code I used sudo Chromeos etc in parts)
    Ed non-zero exit status 1
    Thanks again

    0
    Comment actions Permalink
  • Forrest Smith

    Hi,

     

    Can you paste more of the error output? I need to see where the sub-process call failed.

    0
    Comment actions Permalink
  • Vignesh Mohit Mohan

    HI,

    I have taken a picture of the error. please see below.

     

    thanks

    0
    Comment actions Permalink
  • Forrest Smith

    Hi,

     

    1) You should use a shell from the desktop (ctl+alt+t and then "shell" cmd)- this will work the same way but allow you to copy-paste output

     

    2) Can you run "sudo fdisk -l" and copy/paste the entire output?

     

    0
    Comment actions Permalink
  • Vignesh Mohit Mohan
    crosh> shell
    chronos@localhost / $ sudo fdisk -l
    Password: 
    Disk /dev/loop0: 349.5 MiB, 366428160 bytes, 715680 sectors
    Units: sectors of 1 * 512 = 512 bytes
    Sector size (logical/physical): 512 bytes / 512 bytes
    I/O size (minimum/optimal): 512 bytes / 512 bytes
    
    
    Disk /dev/sda: 1.4 TiB, 1500301910016 bytes, 2930277168 sectors
    Units: sectors of 1 * 512 = 512 bytes
    Sector size (logical/physical): 512 bytes / 4096 bytes
    I/O size (minimum/optimal): 4096 bytes / 4096 bytes
    Disklabel type: gpt
    Disk identifier: 9731E7FF-5179-4715-8A42-4802CF4F9C65
    
    Device          Start        End    Sectors  Size Type
    /dev/sda1        2048    1333247    1331200  650M Windows recovery environment
    /dev/sda2     1333248    1865727     532480  260M EFI System
    /dev/sda3     1865728    2127871     262144  128M Microsoft reserved
    /dev/sda4     2127872 2800545792 2798417921  1.3T Microsoft basic data
    /dev/sda5  2800545793 2817179648   16633856    8G Linux swap
    /dev/sda6  2817179649 2818938880    1759232  859M Windows recovery environment
    /dev/sda7  2818938881 2863157248   44218368 21.1G Microsoft basic data
    
    Partition 5 does not start on physical sector boundary.
    Partition 6 does not start on physical sector boundary.
    Partition 7 does not start on physical sector boundary.
    
    
    Disk /dev/sdb: 14.4 GiB, 15479597056 bytes, 30233588 sectors
    Units: sectors of 1 * 512 = 512 bytes
    Sector size (logical/physical): 512 bytes / 512 bytes
    I/O size (minimum/optimal): 512 bytes / 512 bytes
    Disklabel type: gpt
    Disk identifier: 24744743-B830-514C-83D1-CCEFAE3C8279
    
    Device       Start      End Sectors  Size Type
    /dev/sdb1       64       64       1  512B ChromeOS reserved
    /dev/sdb2       65       65       1  512B ChromeOS reserved
    /dev/sdb3       66       66       1  512B ChromeOS reserved
    /dev/sdb4       67       67       1  512B ChromeOS reserved
    /dev/sdb5       68       68       1  512B ChromeOS reserved
    /dev/sdb6       69       69       1  512B ChromeOS reserved
    /dev/sdb7       70       70       1  512B ChromeOS reserved
    /dev/sdb8       71       71       1  512B ChromeOS reserved
    /dev/sdb9       72       72       1  512B ChromeOS reserved
    /dev/sdb10      73       73       1  512B ChromeOS reserved
    /dev/sdb11      74       74       1  512B ChromeOS reserved
    /dev/sdb12      75       75       1  512B ChromeOS reserved
    /dev/sdb13      76       76       1  512B ChromeOS reserved
    /dev/sdb14      77       77       1  512B ChromeOS reserved
    /dev/sdb15      78       78       1  512B ChromeOS reserved
    /dev/sdb16 8593474 11083841 2490368  1.2G Microsoft basic data
    /dev/sdb17   20546    53313   32768   16M ChromeOS kernel
    /dev/sdb18 2351170  8593473 6242304    3G ChromeOS root fs
    /dev/sdb19   53314    86081   32768   16M ChromeOS kernel
    /dev/sdb20 2347074  2351169    4096    2M ChromeOS root fs
    /dev/sdb21   16514    16514       1  512B ChromeOS kernel
    /dev/sdb22   16515    16515       1  512B ChromeOS root fs
    /dev/sdb23   86082  2183233 2097152    1G Microsoft basic data
    /dev/sdb24   16516    16516       1  512B ChromeOS reserved
    /dev/sdb25   16517    16517       1  512B ChromeOS reserved
    /dev/sdb26     130    16513   16384    8M unknown
    /dev/sdb27 2314306  2347073   32768   16M EFI System
    
    Partition table entries are not in disk order.
    
    
    Disk /dev/mapper/encstateful: 349.5 MiB, 366428160 bytes, 715680 sectors
    Units: sectors of 1 * 512 = 512 bytes
    Sector size (logical/physical): 512 bytes / 512 bytes
    I/O size (minimum/optimal): 512 bytes / 512 bytes
    0
    Comment actions Permalink
  • Forrest Smith

    I think this is what's happening:

    your C drive is small - 21 Gb (yeah?) and you have a secondary partition for storage that is very large.

     

    CloudReady expects the main Windows partition to be the largest, and will try to use 32 GB from that partition to make room for CloudReady.

     

    I think the script is failing because of that. Can you transfer ~40 GB from your larger parititon into the 21GB main partition?

    0
    Comment actions Permalink
  • Vignesh Mohit Mohan

    i did the steps and got this 

    chronos@localhost / $ sudo python /opt/neverware/auto_install.py --dualboot
    Password: 
    Sorry, try again.
    Password: 
    Partition 5 does not start on physical sector boundary.
    Partition 6 does not start on physical sector boundary.
    Partition 7 does not start on physical sector boundary.
    Traceback (most recent call last):
      File "/opt/neverware/auto_install.py", line 278, in <module>
        main()
      File "/opt/neverware/auto_install.py", line 248, in main
        install(dest, args.dualboot)
      File "/opt/neverware/auto_install.py", line 198, in install
        run_chromeos_install(dest, is_efi, dualboot)
      File "/opt/neverware/auto_install.py", line 124, in run_chromeos_install
        output = run_cmd(cmd)
      File "/opt/neverware/auto_install.py", line 65, 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)
    subprocess.CalledProcessError: Command '['/usr/sbin/chromeos-install', '--dst', '/dev/sda', '--yes', '--skip_dst_removable', '--target_bios', 'efi', '--dualboot']' returned non-zero exit status 1

    the above code was in shell in the actual code it took a while this time and said that 900 something mb copied and returned the same error.
    thanks again
    0
    Comment actions Permalink
  • Vignesh Mohit Mohan

    Also just to confirm my C: is the bigger one. The 21 gb that you mentioned is D: and is classified as recovery..no idea why. Maybe something by hp?

     

    thanks forrest. appreciate the help

    0
    Comment actions Permalink
  • Forrest Smith

    Thanks for the correction - that helps, though it removed my primary guess.

     

    Based on the error, we need to delve deeper by running the failing subprocess cmd:

     

    sudo /usr/sbin/chromeos-install --dst /dev/sda --yes --skip_dst_removable --target_bios efi --dualboot

     

    this should give a more detailed error output since it will now be the top level cmd. Once again, as much of the output as you can copy in would be helpful

    0
    Comment actions Permalink
  • Vignesh Mohit Mohan

    hey forrest, thanks and sorry for the delayed response.

    i got the following error this time

    crosh> shell
    chronos@localhost / $ sudo /usr/sbin/chromeos-install --dst /dev/sda --yes --skip_dst_removable --target_bios efi --dualboot
    Password: 
    initctl: Unknown instance: 
    This will install from '/dev/sdb' to '/dev/sda'.
    This will erase all data at this destination: /dev/sda
    ERROR: Starting LBA overlaps
    ERROR: -i 7 -l CRDYSTUB -b 2127878 -s 1 -t 2E0A753D-9E48-43B0-8337-B15192CB1B5E
    0
    Comment actions Permalink
  • Forrest Smith

    Have you tried running from the GUI since you switched to Kingston USB? Does it hang forever? or does it give a different error?

    0
    Comment actions Permalink
  • Vignesh Mohit Mohan

    Hey
    It gets stuck in an endless loop. No idea why

    0
    Comment actions Permalink
  • Forrest Smith

    Hi,

     

    So at this point I think there's just a some small offset between where the partition table expects data to begin and where it does.

     

    I think we need to try some disk cleaning:

     

    1) Make sure hibernation is off (again)

    2) Make sure bitlocker / any other encryption is off

    3) in Windows, open a cmd prompt as administrator and run "chkdsk /f" - hopefully this will tell you to reboot and let the disk repair run twice

     

    If #3 works, try install again (try GUI, try the python auto_install.py cmd, AND try the chromeos-install cmd - any one of them might have changed behavior).

     

    If #3 doesn't work, try this:

    1) run 

    sudo mount -o rw,remount /

    2) run 

    mkdir /tmp/t

    3) Now, partition by partition, mount each one of your Windows partitions to /tmp/t like this:

    sudo mount /dev/sdaX /tmp/t

    Where X is each number you see in /dev/sda when running fdisk -l.

     

    The hope there will be that mounting one or more of them will give an error instead of working properly, and then we'll use that error to learn more about what is wrong.

    0
    Comment actions Permalink
  • Forrest Smith

    I'll point out here that a good way to short circuit this would be to reinstall Windows.

     

    I don't know what your backup situation is like, so I haven't suggested it yet, but if it isn't a pain for you to reinstall Windows we can skip all this and probably get you squared away no problem.

    0
    Comment actions Permalink
  • Vignesh Mohit Mohan

    Hey forrest I just reinstalled Windows and tried it. The same issue persists.

    0
    Comment actions Permalink
  • Vignesh Mohit Mohan

    Hey,
    I don't know if this will Help but I have the hp p199sa laptop.. That's the one I am Trying to install this on.
    Thanks again!

    0
    Comment actions Permalink
  • Forrest Smith

    Hi,

     

    Just to confirm - 

     

    1) Did you reinstall Windows from external media? Or did you use some internal recovery tool?

     

    2) After this reinstall, do you see the same exact error of:

    ERROR: Starting LBA overlaps
    ERROR: -i 7 -l CRDYSTUB -b 2127878 -s 1 -t 2E0A753D-9E48-43B0-8337-B15192CB1B5E

    ?

     

    3) Did you get a chance to try the suggestions in my previous post?

    0
    Comment actions Permalink
  • Vignesh Mohit Mohan

    Hi
    Sorry I was unclear. I used an internal recovery tool. And yes the same error persists. And I didn't try the mounting one as I reinstalled the windows.. Thanks

    0
    Comment actions Permalink

Please sign in to leave a comment.