Jump to content

I installed ubuntu yesterday and had a lot of trouble in managing to start it up. Now it's working but I can seem to access to my windows 10 partition anymore, here is how it turned out :

  • I installed Ubuntu on the same disk as windows, but without replacing it
  • My computer would not detect ubuntu at startup and only started on windows 10. In windows 10, it would not detect it either
  • I booted on ubuntu thanks to my ubuntu installation usb and performed a boot repair.
  • I then tweaked my bios to give priority to ubuntu
  • When booting into grub, there is no windows option anymore

I used the command sudo fdisk -l and here is what I got :

 

Disk /dev/ram0: 64 MiB, 67108864 bytes, 131072 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


Disk /dev/ram1: 64 MiB, 67108864 bytes, 131072 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


Disk /dev/ram2: 64 MiB, 67108864 bytes, 131072 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


Disk /dev/ram3: 64 MiB, 67108864 bytes, 131072 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


Disk /dev/ram4: 64 MiB, 67108864 bytes, 131072 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


Disk /dev/ram5: 64 MiB, 67108864 bytes, 131072 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


Disk /dev/ram6: 64 MiB, 67108864 bytes, 131072 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


Disk /dev/ram7: 64 MiB, 67108864 bytes, 131072 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


Disk /dev/ram8: 64 MiB, 67108864 bytes, 131072 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


Disk /dev/ram9: 64 MiB, 67108864 bytes, 131072 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


Disk /dev/ram10: 64 MiB, 67108864 bytes, 131072 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


Disk /dev/ram11: 64 MiB, 67108864 bytes, 131072 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


Disk /dev/ram12: 64 MiB, 67108864 bytes, 131072 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


Disk /dev/ram13: 64 MiB, 67108864 bytes, 131072 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


Disk /dev/ram14: 64 MiB, 67108864 bytes, 131072 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


Disk /dev/ram15: 64 MiB, 67108864 bytes, 131072 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


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: D12B70EA-7DF6-46BB-BC94-9A486CBADE4D

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 Lenovo boot partition
/dev/sda4    4630528   4892671    262144  128M Microsoft reserved
/dev/sda5    4892672 944373759 939481088  448G Microsoft basic data
/dev/sda6  944375808 976773119  32397312 15,5G Windows recovery environment


Disk /dev/sdb: 232,9 GiB, 250059350016 bytes, 488397168 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: dos
Disk identifier: 0x9bf7942f

Device     Boot     Start       End   Sectors   Size Id Type
/dev/sdb1  *         2048   1026047   1024000   500M  7 HPFS/NTFS/exFAT
/dev/sdb2         1026048 390816087 389790040 185,9G  7 HPFS/NTFS/exFAT
/dev/sdb3       390817790 488396799  97579010  46,5G  5 Extended
/dev/sdb5       390817792 480169983  89352192  42,6G 83 Linux
/dev/sdb6       480172032 488396799   8224768   3,9G 82 Linux swap / Solaris

 

Both systems should be installed on the 240GB disk (sdb in the command)

I'm pretty sure that the windows partition is the sdb2, but I still can't boot on it.

I had my sensible data saved before installing ubuntu, but I'd prefer to be able to boot on this partition rather than reinstalling.

I'd appreciate some help, as I'm completly lost and new to linux.

Thanks in advance,

Nastaliss.

Link to post
Share on other sites

10 hours ago, gabrielcarvfer said:

@nastaliss are you using Grub or Windows 10 bootloader? If grub, try mounting windows disk and then "update-grub" command.

I tried that already, i have a bunch of "windows recovery " in grub but none of them are working.

Link to post
Share on other sites

Quote

/dev/sda5    4892672 944373759 939481088  448G Microsoft basic data

--> your win 10 installation is not on sdb2, but on sda5

you entire partitioning is a bit... unfortunate, with win 10 and the bootloader on sda and linux on sdb, but it should still work just fine.

How did you install linux? as UEFI or BIOS? if you installed it as BIOS you can't boot windows (which is installed as UEFI) from grub, they both need to be the same. I had the same issue myself some time ago

Link to post
Share on other sites

where did you but your grub partition? Try adding windows to it.

 

u believe the best way is to install linux on the second partition with grub there and then add a point in the windows boot loader to grub.

 

this keeps both apart but has the down side of needing ti load 2 boot loaders.

 

                     ¸„»°'´¸„»°'´ Vorticalbox `'°«„¸`'°«„¸
`'°«„¸¸„»°'´¸„»°'´`'°«„¸Scientia Potentia est  ¸„»°'´`'°«„¸`'°«„¸¸„»°'´

Link to post
Share on other sites

8 minutes ago, vorticalbox said:

where did you but your grub partition? Try adding windows to it.

 

u believe the best way is to install linux on the second partition with grub there and then add a point in the windows boot loader to grub.

 

this keeps both apart but has the down side of needing ti load 2 boot loaders.

 

grub seems to be on sda2, which should be fine

I have to disagree with you, though, using 2 bootloaders only adds points of failures, and makes the entire boot process more complicated. Usually the best way is to have one bootloader (Grub) to start all possible OS's. It's the cleanest, fastest and easiest solution. However, therefore all OS's need to be either UEFI or BIOS, you cannot mix them or else Grub cannot boot them.

I have set up all my machines this way and never had any issues, no matter what OS I was booting

Link to post
Share on other sites

Can you verify if you have os-prober installed? This searches for other OSs on the system.

 

grub-install --target=i386-pc /dev/sdx

Or grub-update whatever you feel more comfortable with...

CPU: Intel i5-3470

GPU: MSI GTX 780

OS: GNU/Linux.

Link to post
Share on other sites

1 hour ago, KaasKop said:

Can you verify if you have os-prober installed? This searches for other OSs on the system.

 


grub-install --target=i386-pc /dev/sdx

Or grub-update whatever you feel more comfortable with...

I did grub-update and got nothing, I'll try your other command when I come back home

Link to post
Share on other sites

19 hours ago, laufersteppenwolf said:

grub seems to be on sda2, which should be fine

I have to disagree with you, though, using 2 bootloaders only adds points of failures, and makes the entire boot process more complicated. Usually the best way is to have one bootloader (Grub) to start all possible OS's. It's the cleanest, fastest and easiest solution. However, therefore all OS's need to be either UEFI or BIOS, you cannot mix them or else Grub cannot boot them.

I have set up all my machines this way and never had any issues, no matter what OS I was booting

The thing is, I don't really care about my windows partition, it's just a pain in the ass to reinstall all over again.
If I don't manage to salvage it, how could I install it alongside ubuntu in the way you described ?

Link to post
Share on other sites

3 hours ago, nastaliss said:

The thing is, I don't really care about my windows partition, it's just a pain in the ass to reinstall all over again.
If I don't manage to salvage it, how could I install it alongside ubuntu in the way you described ?

Personally, I'd wipe sda entirely, install windows from scratch (UEFI) but leaving one empty partition at the end of the drive for your linux distro. after installing windows I'd go on and install Linux on the empty partition. Ubuntu installers usually do a pretty good job installing grub and also detecting other OS's such as your windows installation.

During the entire process I'd remove sdb completely, so windows can't screw up the bootloader installation (sometimes windows installs everything on one drive, but the bootloader onto another).

After installing everything it's time to reinstall sdb and you can then mount it whichever way you want, possibly as /home for your linux installation to save some space on sda or whatever way you want really ;)

Link to post
Share on other sites

Create an account or sign in to comment

You need to be a member in order to leave a comment

Create an account

Sign up for a new account in our community. It's easy!

Register a new account

Sign in

Already have an account? Sign in here.

Sign In Now

×