Last known dual boot image

Comments

16 comments

  • Forrest Smith

    Hi,

    The cmd you reference there will work to install dualboot in v64 the same way that the dualboot install UI worked in earlier versions, except you'll need to do one extra step in advance.

    Before running that command, you'll need to clear 32GB of free, unpartitioned space from the main Windows drive.

    Generally, you can do that by going to the Disk/Partition Manager in Windows, finding the main Windows partition that has plenty of free space, and shrinking that partitions total size by 32 GB or more. That will leave your disk with 32GB of free, unpartitioned space. If you make a new partition that's 32 GB in size it won't work - it must be unallocated disk space.

     

    Note that we don't recommend this. As originally announced and planned, we removed the ability to install new CloudReady machines in dualboot in v64 because by v66 we will no longer test or support these machines, which means that after that point CloudReady updates could fail, or even cause issues for your Windows installation.

    0
    Comment actions Permalink
  • SignedAdam

    Could I also get a link to the previous images that did support dual boot Forrest, 32-bit image and 64-bit image

    0
    Comment actions Permalink
  • Forrest Smith

    Hi,

    Since v64.4 is stable, we're not currently distributing older images, sorry. If you're dead set on using dualboot, the cmd line install you described is your best bet.

    0
    Comment actions Permalink
  • SignedAdam

    Are you sure you couldn’t sent me a email of it, I wish to keep it as a backup FOREVER!

    And it’s been along time since I used the command line in CloudReady, how do I enter it again 😭

    * I never had a problem with reinstalling the os after a windows update, I never complained about it so I’m very annoyed that this ability is going away, as my computers hardware can do a lot more than just the internet, it won’t ever just have CloudReady ☁️ on it, who ever came up with the idea of getting ride of dual boot is in the clouds, because windows and chrome come in hand in hand in my eyes, this is a disaster !!!

    0
    Comment actions Permalink
  • SignedAdam

    * In your blog post you did state that we could install CloudReady in Dualboot mode up in till June, can’t really do that with out the installer actually allowing me to do it in the UI - PS you know how long I’ve been using CloudReady for, letting my devices send back diagnostics  data, even coming back here and sharing my ideas, I don’t think it’s to much to ask, to have you guys supply the previous images

    0
    Comment actions Permalink
  • SignedAdam
    chronos@localhost / $ sudo fdisk -l
    
    We trust you have received the usual lecture from the local System
    Administrator. It usually boils down to these three things:
    
        #1) Respect the privacy of others.
        #2) Think before you type.
        #3) With great power comes great responsibility.
    
    Disk /dev/loop0: 635.1 MiB, 665997312 bytes, 1300776 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/loop1: 100 GiB, 107374182400 bytes, 209715200 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/loop2: 2 GiB, 2147483648 bytes, 4194304 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: 232.9 GiB, 250059350016 bytes, 488397168 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: xxxxxx
    
    Device         Start       End   Sectors   Size Type
    /dev/sda1       2048    923647    921600   450M Windows recovery environment
    /dev/sda2     923648   1126399    202752    99M EFI System
    /dev/sda3    1126400   1159167     32768    16M Microsoft reserved
    /dev/sda4    1159168 419769275 418610108 199.6G Microsoft basic data
    /dev/sda5  487356416 488394751   1038336   507M Windows recovery environment
    
    
    Disk /dev/sdb: 14.9 GiB, 16008609792 bytes, 31266816 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: xxxxxxxxx
    
    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 13131841 4538368  2.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: 635.1 MiB, 665997312 bytes, 1300776 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/zram0: 11.3 GiB, 12084199424 bytes, 2950244 sectors
    Units: sectors of 1 * 4096 = 4096 bytes
    Sector size (logical/physical): 4096 bytes / 4096 bytes
    I/O size (minimum/optimal): 4096 bytes / 4096 bytes
    
    
    Disk /dev/mapper/docker-259:0-20860-pool: 100 GiB, 107374182400 bytes, 209715200 sectors
    Units: sectors of 1 * 512 = 512 bytes
    Sector size (logical/physical): 512 bytes / 512 bytes
    I/O size (minimum/optimal): 65536 bytes / 65536 bytes
    chronos@localhost / $ sudo python /opt/neverware/auto_install.py --dualboot
    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
    chronos@localhost / $
    0
    Comment actions Permalink
  • Forrest Smith

     

    You can get to a cmd line by logging in and press ctrl+alt+t, or you can press ctrl+alt+f2 to go to a terminal prior to login.

     

    - - - 

     

    I understand that you don't feel that CloudReady alone makes sense for your use case, but for some of our users it does, and our goals for CloudReady, along with the need for us to avoid the instability caused by Windows, is a the guiding factor here.

    Encouraging or facilitating use of out-of-date versions of our software isn't something we can do. Our team is small, and there are financial and operation costs to keeping legacy infrastructure, hosting, and testing going for out-of-date versions. 

    I genuinely am sorry - we love all of our users, especially active community members like you, but if we made exceptions and did special favor for every person who felt strongly we could never make any real progress.

     

    - - -

     

    Our blog post says:

    In CloudReady v64 (expected start of April 2018 ) dualboot will no longer be available for new installs.

    I hope that wasn't misleading - we have always planned to remove the ability to install in dualboot mode in v64.

    - - -

     

    0
    Comment actions Permalink
  • Forrest Smith

    If your copy/paste dump above is meant as a problem report - you're working on unsupported functionality, but you might find more details or info if you visit file:///var/log/cloudready-install.log in your browser URL bar.

    0
    Comment actions Permalink
  • SignedAdam

    I can now boot in to windows and CloudReady, please keep this feature in the command area as some of us will just reinstall CloudReady when windows brakes it, some of us aren’t noobs

     

    My mistake,

    /dev/sda5  487356416 488394751   1038336   507M Windows recovery environment

    was stopping the install

     

    i put the usb stick in, clicked on the uefi boot entry, for the usb, pressed on open as a guest, pressed ctrl alt and T, then typed the following : 

    Loading extra module: /usr/share/crosh/removable.d/50-crosh.sh
    Loading extra module: /usr/share/crosh/dev.d/50-crosh.sh
    Welcome to crosh, the Chrome OS developer shell.
    
    If you got here by mistake, don't panic!  Just close this tab and carry on.
    
    Type 'help' for a list of commands.
    
    If you want to customize the look/behavior, you can use the options page.
    Load it by using the Ctrl+Shift+P keyboard shortcut.
    
    crosh> shell
    chronos@localhost / $ sudo python /opt/neverware/auto_install.py --dualboot
    chronos@localhost / $ 
    1
    Comment actions Permalink
  • SignedAdam

    @Phil - I cant find any download links, command line is a pain as its extra steps, if you know of where i can get my hands on the build before this one then id be very happy

    0
    Comment actions Permalink
  • SignedAdam

    @Forrest Smith - I’ll make a post with instructions, clearly laying out what to do if your team can reassure me that —dualboot flag won’t be going anywhere, I understand that it won’t be a supported feature and all support for Making sure it plays nice with windows will be gone, but the only way to get a dualboot install working with windows and CloudReady is by making free space and running that command, which let’s face it, won’t be easy, so it’s out the way, and unknown about unless you look in to it, which there are definitely drawbacks to it, after June, my point is, the normal user won’t know what they are doing, so leaving it in shouldn’t be a problem, 

    0
    Comment actions Permalink
  • Forrest Smith

    Hi again,

    I think we may be misunderstanding one another. We are sunsetting dualboot because we don't think it can give a reliable, stable experience to our users. We don't really want a post with instructions, because that would encourage some people to keep using it. No matter how aware of the potentially issues you may be, not everyone who follows a guide in the forum instructions will be prepared for the issues. We've made the hard decision to purposefully prevent those scenarios by removing dualboot.

     

    I'm sorry, but I also can't make any guarantees about the installer flag for dualboot.

    Dropping support for a feature means engineering and QA teams cease work to maintain or test that functionality. When the  inevitably comes where the legacy dualboot installer flag is causing a problem or broken, we aren't going to fix it or work around it. We won't be able to expend engineering resources on fixing or preserving an unsupported feature.

     

     

     

    I know these are the answers you want, but I want to make sure there's no ambiguity here: this is not a feature we want you to use, or that you should expect to work in any reliable way after June 2018. 

    0
    Comment actions Permalink
  • SignedAdam

    @Forrest Smith - I’m well aware of the issues I may face after June, and I will clearly address that in my instructions, I am prepared, to over come the problems alone and I understand that you and your team will have nothing to do with the —dualboot flag/option after June, I think you and your team are underestimating some of us, we aren’t all home users, but advanced linux distro users, we aren't afraid of the command prompt, and we are quite capable of backing up our data and reinstalling both windows and CloudReady again, or even restoring the boot flag for The CloudReady install, because that’s all windows is doing to brake the install after it updates, if a basic user follows the instructions then they will be taking on the responsibility of maintaining both CloudReady and windows, they will be fully aware of the responsibility, taking the options / flag away from the command prompt will upset and discriminate people like me who can support our selfs, you seem to think you only have one community here, you don’t, you have two types of users here, don’t throw it back in our face, don’t throw away an option that you guys have spent time making, unsupport it by all means, but there’s no need to strip it out completely, what a waste of time

    0
    Comment actions Permalink
  • SignedAdam

    And another thing, haven’t I already proven my self in this same post, the installer wasn’t installing! I asked you for support and you told me to supply a bug report dump, I just looked at the data my self, and sorted out the problem my self! Even sharing with you why it wasn’t working!

    0
    Comment actions Permalink
  • SignedAdam

    https://www.neverware.com/blogcontent/2017/4/12/cloudready-home-edition-update-v563-available-on-the-stable-channel

     

    ^-- seems to be the last dual boot image, backup backup BACKUP! :D

     

    *untested

    0
    Comment actions Permalink
  • SignedAdam

    As of build 72.4.27

    —dualboot flag is unrecognized!

    They have now screwed over there Advanced users

    Thank you Neverware

    0
    Comment actions Permalink

Post is closed for comments.