Problem with dual booted system

[oceanna]

I'm definitely a beginner and I have no idea how to do anything. So, I dual booted in Linux Mint and Windows 10 a while ago. I asked about partitioning a while ago as well, but I wasn't sure what to actually do with the advice I got (viewtopic.php?f=46&t=336044). Now I can't seem to boot in Windows at all. When I boot up I get the GNU GRUB menu where I can choose Linux Mint, Linux Mint Advanced Options, Windows 10, and UEFI. When I select the options they all work except when I select Windows 10, which tells me that there is no bootable device. If I change the boot order in BIOS to my 1 TB drive and try to boot up it gives me a black screen with a blinking white line in the top left of the screen, but I can't type anything.

I also noticed when doing

Code: Select all

sudo fdisk -l

I get the following output:

Code: Select all

Disk /dev/loop0: 3.33 MiB, 3481600 bytes, 6800 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: 32.28 MiB, 33841152 bytes, 66096 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: 55.46 MiB, 58142720 bytes, 113560 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/loop3: 55.48 MiB, 58159104 bytes, 113592 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/loop4: 32.28 MiB, 33841152 bytes, 66096 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: 238.49 GiB, 256060514304 bytes, 500118192 sectors
Disk model: SAMSUNG MZ7LN256
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: 81774594-5AE8-4C13-8904-67F331CBCE05

Device       Start       End   Sectors   Size Type
/dev/sda1     2048   1085439   1083392   529M Windows recovery environment
/dev/sda2  1085440   1290239    204800   100M EFI System
/dev/sda3  1290240   1323007     32768    16M Microsoft reserved
/dev/sda4  1323008 500117503 498794496 237.9G Microsoft basic data


Disk /dev/sdb: 931.53 GiB, 1000204886016 bytes, 1953525168 sectors
Disk model: ST1000DM003-1CH1
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: dos
Disk identifier: 0xe54ddc02

Device     Boot   Start        End    Sectors   Size Id Type
/dev/sdb1          2048    1050623    1048576   512M  b W95 FAT32
/dev/sdb2  *    1050624    2101247    1050624   513M ef EFI (FAT-12/16/32)
/dev/sdb3       2103294 1953523711 1951420418 930.5G  5 Extended
/dev/sdb5       2103296 1953523711 1951420416 930.5G 83 Linux

Partition 3 does not start on physical sector boundary.

I've also attached some pictures of the disks program. I don't quite understand all of the information being presented. Is Windows 10 on my 256 GB Disk, and if so then why won't it boot when I select it (Am I accidentally trying to boot into Windows RE or something)? Is Linux on my 1 TB Hard Disk (/dev/sdb5) and if so then why would changing the boot order to my 1 TB Hard Disk not boot into Mint?

Why can't I boot in Windows? How do I fix the partitioning so that it's correct?

[spamhog]

It's a bit of a long shot, but try selecting Windows from the BIOS.

For every PC brand it can be different, but there should be a recover-boot button (e.g. on Lenovo) or a F-something key to keep pressing on boot that will call upsome options like
- enter system settings (BIOS)
- boot normally
- recovery (usually pointing to a Windows recovery partition, which might kill Linux boot as a priority)
- BOOT SELECTOR

The last option should bring up the list of systems known to the BIOS, mostly detected and added automatically pretty much like grub-update adds them at every Linux kernel update.

If you have more than one drive you should also see the raw drives usually my brand and capacity, but all that does is to point to the boot managers on each.

You can take a look at that and rearrange the boot priority through efibootmgr from within Mint.

I don't think you can add an entry through efibootmgs or the BIOS setup.

There are a lot of emergency boot systems for Windows out there, I have no experience but some that works to make Windows bootable again must exist. You may move the problem to making Linux nonbootable, but there is a lot of literature on fixing that.
https://www.slant.co/topics/859/~best-s ... or-windows