Disabling Fast Startup

Comments

15 comments

  • Tom Miller

    I am not sure.  But does the bios have a startup delay option?  Maybe that is what it is talking about?

  • Darin Meyer

    Not that I'm aware of, but I'll poke around to see.

  • Russell Zager

    I'm having the same issue on an HP Stream 13. I've also confirmed Fast Startup is disabled but the installer keeps complaining about it. 

  • Forrest Smith

    Hi guys,

     

    What're central to the Fast-Startup turn off is that Hibernation of all  kinds must be disabled.

     

    It is possible that your machines are still hibernating. It is also possible that we're falseely reporting a hibernation error when really the machine is having a different error - one example that is likely for newer machines is that your storage is mmc and so your destination needs to be somethign like "/dev/mmcblk0" but it is "/dev/sda" by default.

     

    You should be able to check for this using "sudo fdisk -l" and then do a manual install to the correct device. 

  • S P

    Had a similar problem, although I turned Hibernation off, on closer inspection I still had a hyberfil.sys file on my disk. The way to delete that file and really turn Hibernation off:

    - run a Command Prompt as an Administrator

    - type "powercfg -h off" (without the quotes)

  • Russell Zager

    I disabled hibernation as you suggested and am still getting the fast startup error.

  • Bas Keetelaar

    I also disabled fast startup and hibernation, but I'm getting the same message.

  • Forrest Smith

    Hey all - 

     

    Thought this might be relevant for you all:

     

    https://neverware.zendesk.com/hc/en-us/community/posts/208078028-Installation-on-HP-Stream-11-Notebook?page=1#community_comment_212563957

     

    looks like this error comes up for mmc-type storage, which can (perhaps?) be partially worked around by specifying the device more specifically through a manual cmd line install (instructions linked in the thread referenced). Would appreciate any further info from anyone who has the time to try this as a next step!

  • Marius Perijoc

    The same happens to me on a Lenovo ideapat P400 Touch. 

    I get the prompt to remove "Fast Startup" from windows, but it is already disabled. Hibernation is not active. 

     

    so far, I tried the following: 

    - fast start disabled from windows - NOK 

    - fast start enabled from windows - NOK

    - fast start disabled, sleep removed from menu - NOK 

    - ran powercfg -h off from command line - NOK (at this step, hibernation went away from the power button options in control panel) 

    - was not able to locate the hiberfile.sys file anywhere... 

     

     

  • Forrest Smith

    Marius - 

     

    Are you using a Sandisk USB?

     

    Try holding shift while initiating, and throughout , shutdown of Windows.

  • Marius Perijoc

    Not Sandisk, just a generic, no-name usb stick I got at some conference... 

    I did however read in another thread [edit: and also here apparently... :) ]to try and shut down my PC plus holding the shift key when clicking on the shutdown command... 

    I'll cross my fingers, and give that a run also, before going to command line... I'll get back with results  

  • Marius Perijoc

    Holding shift when shutting down removed the fast start error, but now I see 

    "Sorry, something went wrong and we were unable to install CloudReady."

    Looking at he latest log: 

    chronos@localhost / $ cat /var/log/cloudready-install.log.latest 
    INFO:root:found 2 disks
    INFO:root:filtering out root disk, 1 remaining
    INFO:root:filtering out disks smaller than 6442450944, 1 remaining
    INFO:root:best disk: Disk(device_path='/dev/sda', is_installer=False, is_removable=False, is_root=False, size_in_bytes=500107862016L)
    INFO:root:Running from installer; installing to /dev/sda
    INFO:root:running umount /dev/sda8
    DEBUG:root:output: 
    INFO:root:running umount /dev/sda7
    ERROR:root:Error calling ['umount', '/dev/sda7']
    output: umount: /dev/sda7: not mounted
    Traceback (most recent call last):
      File "/opt/neverware/auto_install.py", line 64, in run_cmd
        output = subprocess.check_output(cmd, stderr=subprocess.STDOUT)
      File "/usr/lib/python2.7/subprocess.py", line 544, in check_output
        raise CalledProcessError(retcode, cmd, output=output)
    CalledProcessError: Command '['umount', '/dev/sda7']' returned non-zero exit status 32
    ERROR:root:Error unmounting /dev/sda7: umount: /dev/sda7: not mounted
    
    INFO:root:running umount /dev/sda6
    DEBUG:root:output: 
    INFO:root:running umount /dev/sda5
    DEBUG:root:output: 
    INFO:root:running umount /dev/sda4
    ERROR:root:Error calling ['umount', '/dev/sda4']
    output: umount: /dev/sda4: not mounted
    Traceback (most recent call last):
      File "/opt/neverware/auto_install.py", line 64, in run_cmd
        output = subprocess.check_output(cmd, stderr=subprocess.STDOUT)
      File "/usr/lib/python2.7/subprocess.py", line 544, in check_output
        raise CalledProcessError(retcode, cmd, output=output)
    CalledProcessError: Command '['umount', '/dev/sda4']' returned non-zero exit status 32
    ERROR:root:Error unmounting /dev/sda4: umount: /dev/sda4: not mounted
    
    INFO:root:running umount /dev/sda3
    DEBUG:root:output: 
    INFO:root:running umount /dev/sda2
    ERROR:root:Error calling ['umount', '/dev/sda2']
    output: umount: /dev/sda2: not mounted
    Traceback (most recent call last):
      File "/opt/neverware/auto_install.py", line 64, in run_cmd
        output = subprocess.check_output(cmd, stderr=subprocess.STDOUT)
      File "/usr/lib/python2.7/subprocess.py", line 544, in check_output
        raise CalledProcessError(retcode, cmd, output=output)
    CalledProcessError: Command '['umount', '/dev/sda2']' returned non-zero exit status 32
    ERROR:root:Error unmounting /dev/sda2: umount: /dev/sda2: not mounted
    
    INFO:root:running umount /dev/sda1
    DEBUG:root:output: 
    INFO:root:Checking if EFI is enabled
    INFO:root:EFI enabled: True
    INFO:root:No existing CloudReady install could be found on this machine
    DEBUG:root:ntfs-3g.probe succeeded on /dev/sda1
    DEBUG:root:ntfs-3g.probe succeeded on /dev/sda5
    DEBUG:root:ntfs-3g.probe succeeded on /dev/sda6
    DEBUG:root:ntfs-3g.probe failed with 13 for /dev/sda7
    DEBUG:root:ntfs-3g.probe output: ntfs_mst_post_read_fixup_warn: magic: 0x44414142  size: 1024   usa_ofs: 53009  usa_count: 25570: Invalid argument
    Record 0 has no FILE magic (0x44414142)
    Failed to load $MFT: Input/output error
    
    INFO:root:No existing CloudReady install could be found on this machine
    ERROR:root:hibernation error
    Traceback (most recent call last):
      File "/opt/neverware/auto_install.py", line 231, in main
        install(dest, args.dualboot)
      File "/opt/neverware/auto_install.py", line 181, in install
        neverware_repartition.repartition_for_install(dest)
      File "/opt/neverware/neverware_repartition.py", line 955, in repartition_for_install
        check_system_hibernation(disk)
      File "/opt/neverware/neverware_repartition.py", line 311, in check_system_hibernation
        call_ntfs3g_probe(get_partname(partition))
      File "/opt/neverware/neverware_repartition.py", line 258, in call_ntfs3g_probe
        exception.returncode)
    WindowsHibernationError: Hibernation check failed on partition:/dev/sda7 with output:
    ntfs_mst_post_read_fixup_warn: magic: 0x44414142  size: 1024   usa_ofs: 53009  usa_count: 25570: Invalid argument
    Record 0 has no FILE magic (0x44414142)
    Failed to load $MFT: Input/output error
    
    chronos@localhost / $ 

     

  • Marius Perijoc

    Running from command line in the terminal, starts checking /dev/sda which takes about 1.5 hours, and that's not fun, with no smart errors or warnings, then just exits... 

    However, I noticed that fdisk reports sda has changed from its initial state, and more partitons showed up on the sda drive: 

     

    chronos@localhost / $ sudo fdisk -l 
    Password: 
    
    Disk /dev/loop0: 292.8 MiB, 306991104 bytes, 599592 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: 465.8 GiB, 500107862016 bytes, 976773168 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: A0E7AC49-918F-4037-9ED3-DECA495EA3FC
    
    Device         Start       End   Sectors   Size Type
    /dev/sda1       2048   2050047   2048000  1000M Windows recovery environment
    /dev/sda2    2050048   2582527    532480   260M EFI System
    /dev/sda3    2582528   4630527   2048000  1000M unknown
    /dev/sda4    4630528   4892671    262144   128M Microsoft reserved
    /dev/sda5    4892672 828385280 823492609 392.7G Microsoft basic data
    /dev/sda6  828385281 829327360    942080   460M Windows recovery environment
    /dev/sda7  829327361 881756160  52428800    25G Microsoft basic data
    /dev/sda8  948865024 976773119  27908096  13.3G Windows recovery environment
    /dev/sda9  976773128 976773128         1   512B ChromeOS reserved
    /dev/sda10 976773129 976773129         1   512B ChromeOS reserved
    /dev/sda11 976773130 976773130         1   512B ChromeOS reserved
    /dev/sda12 976773131 976773131         1   512B ChromeOS reserved
    /dev/sda13 976773132 976773132         1   512B ChromeOS reserved
    /dev/sda14 976773133 976773133         1   512B ChromeOS reserved
    /dev/sda15 976773134 976773134         1   512B ChromeOS reserved
    
    Partition 7 does not start on physical sector boundary.
    
    Partition 8 does not start on physical sector boundary.
    
    Partition 11 does not start on physical sector boundary.
    
    Partition 12 does not start on physical sector boundary.
    
    Partition 13 does not start on physical sector boundary.
    
    Partition 14 does not start on physical sector boundary.
    
    Partition 15 does not start on physical sector boundary.
    
    Partition 16 does not start on physical sector boundary.
    
    
    Disk /dev/sdb: 7.7 GiB, 8283750400 bytes, 16179200 sectors
  • Jeff Miller
    /dev/sda5 4892672 828385280 823492609 392.7G Microsoft basic data
    /dev/sda6 828385281 829327360 942080 460M Windows recovery environment
    /dev/sda7 829327361 881756160 52428800 25G Microsoft basic data
    /dev/sda8 948865024 976773119 27908096 13.3G Windows recovery environment

    The installer fails if it has issues with any partitions it thinks could be hibernated windows partitions. It is confused about the 25G partition at /dev/sda7. Are there multiple windows installations on this drive? Can that partition be removed or mounted in windows cleanly and brought down?

    It may complete if you are able to resize the 400G partition in windows then run the installer.

    If you could get the installer to skip the hibernation check it may be able to complete.

     

     

  • Tom Miller

    Windows 10 keeps a copy of the OS it upgrades from for at least a month.  It looked like it store mine in a "System Recovery" partition.  I am not certain how to distinguish which is what in your case but I speculate that is why it looks like you have 2 windows OS's installed.

Please sign in to leave a comment.