on dual-boot, Windows decided not to boot

Questions about Grub, UEFI,the liveCD and the installer
Forum rules
Before you post read how to get help. Topics in this forum are automatically closed 6 months after creation.
bucktails
Level 1
Level 1
Posts: 22
Joined: Tue Jan 08, 2019 6:22 pm

on dual-boot, Windows decided not to boot

Post by bucktails »

I'm not entirely new to Linux, but I am still quite ignorant. I've used my machine for several years without a hitch (probably why I'm still ignorant), but it just decided not to boot into windows when I chose that option. It's been working fine. Can't seem to get it to work now. I get the error message "cannot load image.

Code: Select all

buck@buck-Satellite-L55-B ~ $ inxi -Fxz
System:    Host: buck-Satellite-L55-B Kernel: 4.4.0-31-generic x86_64 (64 bit gcc: 5.3.1)
           Desktop: Cinnamon 3.6.7 (Gtk 3.18.9-1ubuntu3.3)
           Distro: Linux Mint 18.3 Sylvia
Machine:   System: TOSHIBA product: Satellite L55-B v: PSKT4U-07T00G
           Mobo: Type2 - Board Vendor Name1 model: Type2 - Board Product Name1 v: Type2 - Board Version
           Bios: INSYDE v: 2.00 date: 12/11/2014
CPU:       Dual core Intel Core i5-4210U (-HT-MCP-) cache: 3072 KB
           flags: (lm nx sse sse2 sse3 sse4_1 sse4_2 ssse3 vmx) bmips: 9577
           clock speeds: max: 2700 MHz 1: 1702 MHz 2: 1728 MHz 3: 888 MHz
           4: 1572 MHz
Graphics:  Card: Intel Haswell-ULT Integrated Graphics Controller
           bus-ID: 00:02.0
           Display Server: X.Org 1.18.4 drivers: intel (unloaded: fbdev,vesa)
           Resolution: 1366x768@60.00hz
           GLX Renderer: Mesa DRI Intel Haswell Mobile
           GLX Version: 3.0 Mesa 11.2.0 Direct Rendering: Yes
Audio:     Card-1 Intel 8 Series HD Audio Controller
           driver: snd_hda_intel bus-ID: 00:1b.0
           Card-2 Intel Haswell-ULT HD Audio Controller
           driver: snd_hda_intel bus-ID: 00:03.0
           Sound: Advanced Linux Sound Architecture v: k4.4.0-31-generic
Network:   Card-1: Qualcomm Atheros AR9485 Wireless Network Adapter
           driver: ath9k bus-ID: 07:00.0
           IF: wlp7s0 state: up mac: <filter>
           Card-2: Realtek RTL8101/2/6E PCI Express Fast/Gigabit Ethernet controller
           driver: r8169 v: 2.3LK-NAPI port: 3000 bus-ID: 08:00.0
           IF: enp8s0 state: up speed: 100 Mbps duplex: full mac: <filter>
Drives:    HDD Total Size: 1016.2GB (5.1% used)
           ID-1: /dev/sda model: HGST_HTS541010A9 size: 1000.2GB
           ID-2: USB /dev/sdb model: Cruzer_Glide size: 16.0GB
Partition: ID-1: / size: 416G used: 41G (11%) fs: ext4 dev: /dev/sda5
           ID-2: swap-1 size: 8.51GB used: 0.00GB (0%) fs: swap dev: /dev/sda6
RAID:      No RAID devices: /proc/mdstat, md_mod kernel module present
Sensors:   System Temperatures: cpu: 42.0C mobo: N/A
           Fan Speeds (in rpm): cpu: N/A
Info:      Processes: 217 Uptime: 2 min Memory: 562.7/7903.6MB
           Init: systemd runlevel: 5 Gcc sys: 5.4.0
           Client: Shell (bash 4.3.481) inxi: 2.2.35 
I've tried changing Bios to disable Secure Boot, but that didn't work. I've tried running sudo update-grub, but I don't know if it worked. Can someone please guide me through this?
Last edited by LockBot on Wed Dec 28, 2022 7:16 am, edited 2 times in total.
Reason: Topic automatically closed 6 months after creation. New replies are no longer allowed.
kukamuumuka

Re: on dual-boot, Windows decided not to boot

Post by kukamuumuka »

What is the result for the next command?

Code: Select all

inxi -po | grep sd ; sudo parted -l ; sudo os-prober
bucktails
Level 1
Level 1
Posts: 22
Joined: Tue Jan 08, 2019 6:22 pm

Re: on dual-boot, Windows decided not to boot

Post by bucktails »

Code: Select all

buck@buck-Satellite-L55-B ~ $ inxi -po | grep sd ; sudo parted -l ; sudo os-prober
Partition: ID-1: / size: 416G used: 41G (11%) fs: ext4 dev: /dev/sda5
           ID-2: /boot/efi size: 96M used: 53M (55%) fs: vfat dev: /dev/sda2
           ID-3: swap-1 size: 8.51GB used: 0.00GB (0%) fs: swap dev: /dev/sda6
           ID-17: /dev/sda1 size: 1.07G label: System uuid: 3E9C2E479C2DFA53
           ID-18: /dev/sda3 size: 0.13G label: N/A uuid: 96B43177B4315B47
           ID-19: /dev/sda4 size: 526.86G
           ID-20: /dev/sda7 size: 9.54G label: Recovery uuid: 08CA6C2BCA6C16EA
           ID-21: /dev/sdb1 size: 1.90G
           ID-22: /dev/sdb2 size: 0.00G
Last edited by Moem on Sun Jan 13, 2019 3:54 pm, edited 1 time in total.
Reason: Adding [code] tags. They retain some formatting that makes your output easier to read.
kukamuumuka

Re: on dual-boot, Windows decided not to boot

Post by kukamuumuka »

That is not the command output.
bucktails
Level 1
Level 1
Posts: 22
Joined: Tue Jan 08, 2019 6:22 pm

Re: on dual-boot, Windows decided not to boot

Post by bucktails »

I don't understand.
philotux

Re: on dual-boot, Windows decided not to boot

Post by philotux »

bucktails wrote: Sun Jan 13, 2019 3:05 pm I don't understand.
Run the commands one at the time if you want and post back the output:

Code: Select all

inxi -po | grep sd 

Code: Select all

sudo parted -l 
(that is lowercase L)

Code: Select all

sudo os-prober
bucktails
Level 1
Level 1
Posts: 22
Joined: Tue Jan 08, 2019 6:22 pm

Re: on dual-boot, Windows decided not to boot

Post by bucktails »

I thought maybe you meant that I should run them one at a time. Sorry!

buck@buck-Satellite-L55-B ~ $ inxi -po | grep sd
Partition: ID-1: / size: 416G used: 42G (11%) fs: ext4 dev: /dev/sda5
ID-2: /boot/efi size: 96M used: 53M (55%) fs: vfat dev: /dev/sda2
ID-3: swap-1 size: 8.51GB used: 0.00GB (0%) fs: swap dev: /dev/sda6
ID-17: /dev/sda1 size: 1.07G label: System uuid: 3E9C2E479C2DFA53
ID-18: /dev/sda3 size: 0.13G label: N/A uuid: 96B43177B4315B47
ID-19: /dev/sda4 size: 526.86G
ID-20: /dev/sda7 size: 9.54G label: Recovery uuid: 08CA6C2BCA6C16EA
buck@buck-Satellite-L55-B ~ $ sudo parted -l
[sudo] password for buck:
Model: ATA HGST HTS541010A9 (scsi)
Disk /dev/sda: 1000GB
Sector size (logical/physical): 512B/4096B
Partition Table: gpt
Disk Flags:

Number Start End Size File system Name Flags
1 1049kB 1075MB 1074MB ntfs Basic data partition hidden, diag
2 1075MB 1180MB 105MB fat32 Basic data partition boot, esp
3 1180MB 1314MB 134MB ntfs Basic data partition msftres
4 1314MB 528GB 527GB ntfs Basic data partition msftdata
5 528GB 981GB 453GB ext4
6 981GB 990GB 8506MB linux-swap(v1)
7 991GB 1000GB 9541MB ntfs Basic data partition hidden, diag


buck@buck-Satellite-L55-B ~ $ sudo os-prober
/dev/sda2@/EFI/Microsoft/Boot/bootmgfw.efi:Windows Boot Manager:Windows:efi
buck@buck-Satellite-L55-B ~ $
kukamuumuka

Re: on dual-boot, Windows decided not to boot

Post by kukamuumuka »

Disable Secure Boot from BIOS settings.
https://bugs.launchpad.net/ubuntu/+sour ... ug/1091464
bucktails
Level 1
Level 1
Posts: 22
Joined: Tue Jan 08, 2019 6:22 pm

Re: on dual-boot, Windows decided not to boot

Post by bucktails »

Could not try your suggestion, because, in the meantime, I did something else wrong. I turned off my machine using the power button, because I couldn't get out of where I was.
Now I have this screen, black with white writing:

BusyBox v1.22.1 (ubuntu 1:1.22.0-15ubuntu1) built-in shell (ash)
enter “help” for a list of built-in commands.

(initramfs) help
. : [alias break cd chdir command continue echo eval exec exit
export false getopts hash help history let local printf pwd read
readonly return set shift test times trap true type ulimit umask
unalias unset wait [ [[ acpid ash awk basename blockdev cat chmod
chroot chvt clear cmp cp cut deallocvt devmem df dnsdomainname
du dumpkmap echo egrep env expr false fbset fdflush fgrep find
fstrim grep gunzip gzip hostname hwlock ifconfig ip kill ln
loadfont loadkmap ls lzop lzopcat mkdir mkfifo mkmod mkswap mktemp
modinfo more mount mv openvt pidof printf ps pwd readlink reset
rm rmdir sed seq setkeycodes sh sleep sort stat static-sh stty
switch_root sync tail tee test touch tr true tty umount uname
uniq unlzoip wc wget which yes zcat

I didn't know what to do here, so I tried to exit:

(initramfs) exit
/dev/sda5 contains a file system with errors, check forced.
Inodes that were a part of a corrupted orphan linked list found.

/dev/sda5: UNEXPECTED INCONSISTENCY; RUN fsck MANUALLY.
(i.e., without -a or -p options)
fsck exited with status code 4
the root filesystem on /dev/sda5 requires a manual fsck

BusyBox v1.22.1 (ubuntu 1:1.22.0-15ubuntu1) built-in shell (ash)
enter “help” for a list of built-in commands.

Here, I ran the fsck command:

(initramfs) fsck
fsck from util-linux 2.27.1
(initramfs) _

I have no idea where to go from here. Thanks in advance for any help.
philotux

Re: on dual-boot, Windows decided not to boot

Post by philotux »

bucktails wrote: Sat Jan 19, 2019 11:14 am /dev/sda5 contains a file system with errors, check forced.
Inodes that were a part of a corrupted orphan linked list found.

/dev/sda5: UNEXPECTED INCONSISTENCY; RUN fsck MANUALLY.
(i.e., without -a or -p options)
fsck exited with status code 4
the root filesystem on /dev/sda5 requires a manual fsck
At initramfs, run:

Code: Select all

fsck -y /dev/sda5
bucktails
Level 1
Level 1
Posts: 22
Joined: Tue Jan 08, 2019 6:22 pm

Re: on dual-boot, Windows decided not to boot

Post by bucktails »

GREAT!! Linux booted. But when I tried to go to Windows, I got this:

at the top of the screen is: GNU GRUB version 2.02~beta2-36unbuntu3.2

*Linux Mint 18.3 Cinnamon 64-bit
Advanced options for Linux Mint 18.3 64-bit
Windows boot manager (on /dev/sda2)
System setup

Duh! That's my boot screen. Anyway, now, when I try to boot to windows from this screen I get:
error: cannot load image
bucktails
Level 1
Level 1
Posts: 22
Joined: Tue Jan 08, 2019 6:22 pm

Re: on dual-boot, Windows decided not to boot

Post by bucktails »

administrollaattori wrote: Tue Jan 15, 2019 4:55 pm Disable Secure Boot from BIOS settings.
https://bugs.launchpad.net/ubuntu/+sour ... ug/1091464
I have already disabled Secure Boot. It doesn't seem to make any difference. :( Still get error: cannot read image
bucktails
Level 1
Level 1
Posts: 22
Joined: Tue Jan 08, 2019 6:22 pm

Re: on dual-boot, Windows decided not to boot

Post by bucktails »

I really don't know what I'm doing, but just nosing around, I found this in my grub.cfg file. It's just a small portion almost at the end, but since it mentioned the Windows chainloader, I thought it might have some significance.

buck@buck-Satellite-L55-B ~ $ cat /boot/grub/grub.cfg
#
# DO NOT EDIT THIS FILE

### BEGIN /etc/grub.d/30_os-prober ###
menuentry 'Windows Boot Manager (on /dev/sda2)' --class windows --class os $menuentry_id_option 'osprober-efi-DA2F-2AFB' {
insmod part_gpt
insmod fat
set root='hd0,gpt2'
if [ x$feature_platform_search_hint = xy ]; then
search --no-floppy --fs-uuid --set=root --hint-bios=hd0,gpt2 --hint-efi=hd0,gpt2 --hint-baremetal=ahci0,gpt2 DA2F-2AFB
else
search --no-floppy --fs-uuid --set=root DA2F-2AFB
fi
chainloader /EFI/Microsoft/Boot/bootmgfw.efi
}
set timeout_style=menu
if [ "${timeout}" = 0 ]; then
set timeout=10
fi
### END /etc/grub.d/30_os-prober ###
philotux

Re: on dual-boot, Windows decided not to boot

Post by philotux »

bucktails wrote: Sun Jan 20, 2019 8:18 pm

Code: Select all

### BEGIN /etc/grub.d/30_os-prober ###
menuentry 'Windows Boot Manager (on /dev/sda2)' --class windows --class os $menuentry_id_option 'osprober-efi-DA2F-2AFB' {
	insmod part_gpt
	insmod fat
	set root='hd0,gpt2'
	if [ x$feature_platform_search_hint = xy ]; then
	  search --no-floppy --fs-uuid --set=root --hint-bios=hd0,gpt2 --hint-efi=hd0,gpt2 --hint-baremetal=ahci0,gpt2  DA2F-2AFB
	else
	  search --no-floppy --fs-uuid --set=root DA2F-2AFB
	fi
	chainloader /EFI/Microsoft/Boot/bootmgfw.efi
}
set timeout_style=menu
if [ "${timeout}" = 0 ]; then
  set timeout=10
fi
### END /etc/grub.d/30_os-prober ###
That looks exactly like mine apart from the UUID of the EFI-partition for obvious reasons. So nothing wrong there, it seems.
Could you try to get into BIOS and choose Windows Boot Manager from the boot options in there to see if it will boot?
bucktails
Level 1
Level 1
Posts: 22
Joined: Tue Jan 08, 2019 6:22 pm

Re: on dual-boot, Windows decided not to boot

Post by bucktails »

I'm going in circles here! I went back into BIOS to check for the Windows bootloader, but didn't find one!? Somehow, when I tried to reboot, I got this:

INTEL UNDI, PXE-2.1 (build083)
Copyright (C) 1997-2000 Intel Corp

Realtek PCIe FE FAMILY Controller series v1.34 (10/07/13)
CLIENT MAC ADDR: C4 54 44 E6 E0 2E GUIDE: 39CA3EF9-AF40-422D-B22B-46527977157F
PXE-m0F: Exiting ROM.
No bootable device--insert boot disk and press any key

When I did this, I had the bootable thumb drive in and I decided to try a clean install. The problem was, it wanted to install alongside the Mint 18.3 that was already installed. I didn't want to do that, so I looked at the devices. It showed (what I think was) the Linux partition, the hard drive, and my thumb drive. When I clicked on the Linux partition, it gave:
/media/mint/871adaO5-od783-44e1-a874-288d8 aec 66c2(/dev/sda5)
Then I clicked on the harddrive and got all this:

Unable to mount TI106997OOB
Error mounting /dev/sda4 at /media/mint/TI106997OOB: command line 'mount -t "ntfs" -o" uhelper=udisk2, nodev, nosuid, uid=999.9id=999" =/dev/sda4" "media/mint/TI106997OOB" exited with non-zero exit status 14:
Windows is hibernated, refused to mount.
Failed to mount '/dev/sda4': Operation not permitted.
The NTSF partition is in an unsafe state.
Please resume and shutdown Windows fully (no hibernation or fast restarting), or mount the volume read-only with the 'ro' mount system.

Sorry, but I'm lost here. My command-line knowledge is very limited. Thanks again for any guidance.
kukamuumuka

Re: on dual-boot, Windows decided not to boot

Post by kukamuumuka »

Run

Code: Select all

sudo ntfsfix -d -b /dev/sda4
bucktails
Level 1
Level 1
Posts: 22
Joined: Tue Jan 08, 2019 6:22 pm

Re: on dual-boot, Windows decided not to boot

Post by bucktails »

administrollaattori wrote: Mon Jan 21, 2019 3:25 pm Run

Code: Select all

sudo ntfsfix -d -b /dev/sda4
This may be a duplicate. I thought I had submitted my reply, but I don't
see it.

Anyway, thanks for your reply. This is what I got:

mint@mint ~ $ sudo ntfsfix -d -b /dev/sda4
Mounting volume... Windows is hibernated, refused to mount.
FAILED
Attempting to correct errors...
Processing $MFT and $MFTMirr...
Reading $MFT... OK
Reading $MFTMirr... OK
Comparing $MFTMirr to $MFT... OK
Processing of $MFT and $MFTMirr completed successfully.
Setting required flags on partition... OK
Going to empty the journal ($LogFile)... OK
Windows is hibernated, refused to mount.
Remount failed: Operation not permitted
mint@mint ~ $
philotux

Re: on dual-boot, Windows decided not to boot

Post by philotux »

I am not sure but I wonder what could the significance of:
Windows is hibernated, refused to mount.
Remount failed: Operation not permitted
be for the current issue? probably nothing.

Since the Windows bootmgr is correctly captured by os-peober, I suspect maybe some form of corruption in the bootmgr prevents Windows to boot up. But all this is guess work on my part. I think you need assistance from advanced users of the forums to troubleshoot further and find a solution.
bucktails
Level 1
Level 1
Posts: 22
Joined: Tue Jan 08, 2019 6:22 pm

Re: on dual-boot, Windows decided not to boot

Post by bucktails »

Thanks, philotux. I'll be waiting for someone to reply.
bucktails
Level 1
Level 1
Posts: 22
Joined: Tue Jan 08, 2019 6:22 pm

Re: on dual-boot, Windows decided not to boot

Post by bucktails »

Since my results for "sudo ntfsfix -d -b /dev/sda4" gave me these results:

mint@mint ~ $ sudo ntfsfix -d -b /dev/sda4
Mounting volume... Windows is hibernated, refused to mount.
FAILED
Attempting to correct errors...
Processing $MFT and $MFTMirr...
Reading $MFT... OK
Reading $MFTMirr... OK
Comparing $MFTMirr to $MFT... OK
Processing of $MFT and $MFTMirr completed successfully.
Setting required flags on partition... OK
Going to empty the journal ($LogFile)... OK
Windows is hibernated, refused to mount.
Remount failed: Operation not permitted
mint@mint ~ $

I've been trying to find out how to fix the Windows hibernation problem. Most fixes tell you to go into Windows to fix it. That's my problem - I can't get into Windows! What do I do now? I really need to get into Windows.
Locked

Return to “Installation & Boot”