Installing Ubuntu 18.04 can't see my partitioned HDD

Clash Royale CLAN TAG#URR8PPP up vote
1
down vote
favorite
My computer is running on Windows 10 and I want to dual boot it with Ubuntu 18.04.
Disk Sizes are:
C: 148GB
D: 399GB
E: 199GB
F: 155GB
I: 349MB(System Reserved)
I have freed up 25GB unallocated space from F: drive (which was 180GB). I have MBR partitions and not GPT. Previously my disc was dynamic then I learnt that Ubuntu needs basic disk to be installed. Hence it showed: 
I converted my dynamic disks to basic disk using AOMEI Dynamic Disk Manager Pro. Here is what my Windows disk management shows:

but now I see this green box line that says these 4 partition are now "Extended Partition".
I went ahead to install Ubuntu, but all I see in the installer is:

From the Ubuntu installer, I have run some commands from the terminal, those are:
Also I have run GParted and it shows:

Please help me regarding this so that I can install Ubuntu in the free space which I had allocated for it, I am stuck in it for a long time.
Edit: After executing the commands given by David Foerster, I decided to run the Ubuntu installer again and the option "Install alongside Windows 10" was also available, but I chose to install Ubuntu in the free space which I created for it by going to the "Something Else" option.

dual-boot partitioning system-installation ubiquity
 |Â
show 7 more comments
up vote
1
down vote
favorite
My computer is running on Windows 10 and I want to dual boot it with Ubuntu 18.04.
Disk Sizes are:
C: 148GB
D: 399GB
E: 199GB
F: 155GB
I: 349MB(System Reserved)
I have freed up 25GB unallocated space from F: drive (which was 180GB). I have MBR partitions and not GPT. Previously my disc was dynamic then I learnt that Ubuntu needs basic disk to be installed. Hence it showed: 
I converted my dynamic disks to basic disk using AOMEI Dynamic Disk Manager Pro. Here is what my Windows disk management shows:

but now I see this green box line that says these 4 partition are now "Extended Partition".
I went ahead to install Ubuntu, but all I see in the installer is:

From the Ubuntu installer, I have run some commands from the terminal, those are:
Also I have run GParted and it shows:

Please help me regarding this so that I can install Ubuntu in the free space which I had allocated for it, I am stuck in it for a long time.
Edit: After executing the commands given by David Foerster, I decided to run the Ubuntu installer again and the option "Install alongside Windows 10" was also available, but I chose to install Ubuntu in the free space which I created for it by going to the "Something Else" option.

dual-boot partitioning system-installation ubiquity
1
You should not have made conversion from GPT to MBR. i guess your system is Booting in the mode "UEFI". Are you able to Boot to Windows at this time? Can you confirm booting mode first to proceed further?
â PRATAP
Jun 7 at 4:19
No my computer has MBR and is running on UEFI mode
â Apurba
Jun 7 at 7:15
windows 10 cant be run on MBR if the boot mode is in UEFI. are you able to boot to windows in UEFI mode? can you send the pic like this we.tl/HtAe4qiPmI (in windows diskmgmt.msc, select disk0, properties, Volumes tab)
â PRATAP
Jun 7 at 8:30
Sorry for the mistake in the previous comment, I meant to say: "No my computer has MBR and is running on BIOS mode". There is no volumes tab when I click on properties on the drives except for the unallocated 25 GB free space. i.stack.imgur.com/cLU28.png
â Apurba
Jun 7 at 8:45
1
how do I know which is disk 0? For me, it is labelled as Entertainment (E:), Gaming (D:), System (C:) and Stuffs (F:).
â Apurba
Jun 7 at 8:50
 |Â
show 7 more comments
up vote
1
down vote
favorite
up vote
1
down vote
favorite
My computer is running on Windows 10 and I want to dual boot it with Ubuntu 18.04.
Disk Sizes are:
C: 148GB
D: 399GB
E: 199GB
F: 155GB
I: 349MB(System Reserved)
I have freed up 25GB unallocated space from F: drive (which was 180GB). I have MBR partitions and not GPT. Previously my disc was dynamic then I learnt that Ubuntu needs basic disk to be installed. Hence it showed: 
I converted my dynamic disks to basic disk using AOMEI Dynamic Disk Manager Pro. Here is what my Windows disk management shows:

but now I see this green box line that says these 4 partition are now "Extended Partition".
I went ahead to install Ubuntu, but all I see in the installer is:

From the Ubuntu installer, I have run some commands from the terminal, those are:
Also I have run GParted and it shows:

Please help me regarding this so that I can install Ubuntu in the free space which I had allocated for it, I am stuck in it for a long time.
Edit: After executing the commands given by David Foerster, I decided to run the Ubuntu installer again and the option "Install alongside Windows 10" was also available, but I chose to install Ubuntu in the free space which I created for it by going to the "Something Else" option.

dual-boot partitioning system-installation ubiquity
My computer is running on Windows 10 and I want to dual boot it with Ubuntu 18.04.
Disk Sizes are:
C: 148GB
D: 399GB
E: 199GB
F: 155GB
I: 349MB(System Reserved)
I have freed up 25GB unallocated space from F: drive (which was 180GB). I have MBR partitions and not GPT. Previously my disc was dynamic then I learnt that Ubuntu needs basic disk to be installed. Hence it showed: 
I converted my dynamic disks to basic disk using AOMEI Dynamic Disk Manager Pro. Here is what my Windows disk management shows:

but now I see this green box line that says these 4 partition are now "Extended Partition".
I went ahead to install Ubuntu, but all I see in the installer is:

From the Ubuntu installer, I have run some commands from the terminal, those are:
Also I have run GParted and it shows:

Please help me regarding this so that I can install Ubuntu in the free space which I had allocated for it, I am stuck in it for a long time.
Edit: After executing the commands given by David Foerster, I decided to run the Ubuntu installer again and the option "Install alongside Windows 10" was also available, but I chose to install Ubuntu in the free space which I created for it by going to the "Something Else" option.

dual-boot partitioning system-installation ubiquity
edited Jun 9 at 16:50
asked Jun 7 at 4:02
Apurba
156
156
1
You should not have made conversion from GPT to MBR. i guess your system is Booting in the mode "UEFI". Are you able to Boot to Windows at this time? Can you confirm booting mode first to proceed further?
â PRATAP
Jun 7 at 4:19
No my computer has MBR and is running on UEFI mode
â Apurba
Jun 7 at 7:15
windows 10 cant be run on MBR if the boot mode is in UEFI. are you able to boot to windows in UEFI mode? can you send the pic like this we.tl/HtAe4qiPmI (in windows diskmgmt.msc, select disk0, properties, Volumes tab)
â PRATAP
Jun 7 at 8:30
Sorry for the mistake in the previous comment, I meant to say: "No my computer has MBR and is running on BIOS mode". There is no volumes tab when I click on properties on the drives except for the unallocated 25 GB free space. i.stack.imgur.com/cLU28.png
â Apurba
Jun 7 at 8:45
1
how do I know which is disk 0? For me, it is labelled as Entertainment (E:), Gaming (D:), System (C:) and Stuffs (F:).
â Apurba
Jun 7 at 8:50
 |Â
show 7 more comments
1
You should not have made conversion from GPT to MBR. i guess your system is Booting in the mode "UEFI". Are you able to Boot to Windows at this time? Can you confirm booting mode first to proceed further?
â PRATAP
Jun 7 at 4:19
No my computer has MBR and is running on UEFI mode
â Apurba
Jun 7 at 7:15
windows 10 cant be run on MBR if the boot mode is in UEFI. are you able to boot to windows in UEFI mode? can you send the pic like this we.tl/HtAe4qiPmI (in windows diskmgmt.msc, select disk0, properties, Volumes tab)
â PRATAP
Jun 7 at 8:30
Sorry for the mistake in the previous comment, I meant to say: "No my computer has MBR and is running on BIOS mode". There is no volumes tab when I click on properties on the drives except for the unallocated 25 GB free space. i.stack.imgur.com/cLU28.png
â Apurba
Jun 7 at 8:45
1
how do I know which is disk 0? For me, it is labelled as Entertainment (E:), Gaming (D:), System (C:) and Stuffs (F:).
â Apurba
Jun 7 at 8:50
1
1
You should not have made conversion from GPT to MBR. i guess your system is Booting in the mode "UEFI". Are you able to Boot to Windows at this time? Can you confirm booting mode first to proceed further?
â PRATAP
Jun 7 at 4:19
You should not have made conversion from GPT to MBR. i guess your system is Booting in the mode "UEFI". Are you able to Boot to Windows at this time? Can you confirm booting mode first to proceed further?
â PRATAP
Jun 7 at 4:19
No my computer has MBR and is running on UEFI mode
â Apurba
Jun 7 at 7:15
No my computer has MBR and is running on UEFI mode
â Apurba
Jun 7 at 7:15
windows 10 cant be run on MBR if the boot mode is in UEFI. are you able to boot to windows in UEFI mode? can you send the pic like this we.tl/HtAe4qiPmI (in windows diskmgmt.msc, select disk0, properties, Volumes tab)
â PRATAP
Jun 7 at 8:30
windows 10 cant be run on MBR if the boot mode is in UEFI. are you able to boot to windows in UEFI mode? can you send the pic like this we.tl/HtAe4qiPmI (in windows diskmgmt.msc, select disk0, properties, Volumes tab)
â PRATAP
Jun 7 at 8:30
Sorry for the mistake in the previous comment, I meant to say: "No my computer has MBR and is running on BIOS mode". There is no volumes tab when I click on properties on the drives except for the unallocated 25 GB free space. i.stack.imgur.com/cLU28.png
â Apurba
Jun 7 at 8:45
Sorry for the mistake in the previous comment, I meant to say: "No my computer has MBR and is running on BIOS mode". There is no volumes tab when I click on properties on the drives except for the unallocated 25 GB free space. i.stack.imgur.com/cLU28.png
â Apurba
Jun 7 at 8:45
1
1
how do I know which is disk 0? For me, it is labelled as Entertainment (E:), Gaming (D:), System (C:) and Stuffs (F:).
â Apurba
Jun 7 at 8:50
how do I know which is disk 0? For me, it is labelled as Entertainment (E:), Gaming (D:), System (C:) and Stuffs (F:).
â Apurba
Jun 7 at 8:50
 |Â
show 7 more comments
1 Answer
1
active
oldest
votes
up vote
0
down vote
accepted
Your partition table is invalid: primary partition #3 lies within the range of primary partition #4, which isn't too bad because #4 is an extended partition meant to contain logical partitions and #3 doesn't overlap with any of those logical partition, but it's still invalid and a careful partition manager will fail and do nothing instead of making things worse.
You can use fixparts to fix this issue (according to its manual page):
Back up the current Master Boot Record (including the partition table) in case something goes wrong:
sudo dd if=/dev/sda count=1 > /path/to/sda.mbrThe path of the back-up file
/path/to/sda.mbrshould lie on a persistent storage device, e. g. a connected USB drive, as opposed to the ephemeral file system of a live system.If something does go wrong and after you verified that
/dev/sdastill refers to desired drive (which may change on every boot) you can restore it with the following command:sudo dd if=/path/to/sda.mbr of=/dev/sda count=1
sudo partprobe /dev/sda
Run
fixpartswith the âÂÂlogicalâ (on partition 3), âÂÂsortâ and âÂÂwriteâ (confirmed with yes) commands:printf '%sn' l 3 s w y | sudo fixparts /dev/sda
Yes! after executing all the above commands, I decided to run the Ubuntu installer and it finally showed the unallocated 25 GB free space where I successfully installed Ubuntu. Thanks for your help.
â Apurba
Jun 8 at 5:59
@Apurba. It's nice to hear that you have succeeded. I would like to know what did you put here "path/to/sda.sfdisk" insudo sfdisk - d /dev/sda > /path/to/sda.sfdiskand how much time it took to take backup after giving this command. Thank you.
â PRATAP
Jun 8 at 19:13
@David Forester you mentioned /path/to/sda.sfdisk do we need to edit /path/to/sda or is it a part of command?
â PRATAP
Jun 9 at 4:22
@PRATAP: I clarified the relevant section of my answer. It really needed that improvement. Thanks for pointing it out.
â David Foerster
Jun 9 at 7:54
@DavidFoerstersudo sfdisk -d /dev/sda > /path/to/sda.sfdiskDidn't work for me, so I triedsfdisk -d /dev/sda > sda.partition.table.08-06-2018.txtand it worked. @PRATAP it didn't take any time, as soon as I executed the command, a text file named sda.partition.table.08-06-2018.txt was created in Home
â Apurba
Jun 9 at 16:34
 |Â
show 1 more comment
1 Answer
1
active
oldest
votes
1 Answer
1
active
oldest
votes
active
oldest
votes
active
oldest
votes
up vote
0
down vote
accepted
Your partition table is invalid: primary partition #3 lies within the range of primary partition #4, which isn't too bad because #4 is an extended partition meant to contain logical partitions and #3 doesn't overlap with any of those logical partition, but it's still invalid and a careful partition manager will fail and do nothing instead of making things worse.
You can use fixparts to fix this issue (according to its manual page):
Back up the current Master Boot Record (including the partition table) in case something goes wrong:
sudo dd if=/dev/sda count=1 > /path/to/sda.mbrThe path of the back-up file
/path/to/sda.mbrshould lie on a persistent storage device, e. g. a connected USB drive, as opposed to the ephemeral file system of a live system.If something does go wrong and after you verified that
/dev/sdastill refers to desired drive (which may change on every boot) you can restore it with the following command:sudo dd if=/path/to/sda.mbr of=/dev/sda count=1
sudo partprobe /dev/sda
Run
fixpartswith the âÂÂlogicalâ (on partition 3), âÂÂsortâ and âÂÂwriteâ (confirmed with yes) commands:printf '%sn' l 3 s w y | sudo fixparts /dev/sda
Yes! after executing all the above commands, I decided to run the Ubuntu installer and it finally showed the unallocated 25 GB free space where I successfully installed Ubuntu. Thanks for your help.
â Apurba
Jun 8 at 5:59
@Apurba. It's nice to hear that you have succeeded. I would like to know what did you put here "path/to/sda.sfdisk" insudo sfdisk - d /dev/sda > /path/to/sda.sfdiskand how much time it took to take backup after giving this command. Thank you.
â PRATAP
Jun 8 at 19:13
@David Forester you mentioned /path/to/sda.sfdisk do we need to edit /path/to/sda or is it a part of command?
â PRATAP
Jun 9 at 4:22
@PRATAP: I clarified the relevant section of my answer. It really needed that improvement. Thanks for pointing it out.
â David Foerster
Jun 9 at 7:54
@DavidFoerstersudo sfdisk -d /dev/sda > /path/to/sda.sfdiskDidn't work for me, so I triedsfdisk -d /dev/sda > sda.partition.table.08-06-2018.txtand it worked. @PRATAP it didn't take any time, as soon as I executed the command, a text file named sda.partition.table.08-06-2018.txt was created in Home
â Apurba
Jun 9 at 16:34
 |Â
show 1 more comment
up vote
0
down vote
accepted
Your partition table is invalid: primary partition #3 lies within the range of primary partition #4, which isn't too bad because #4 is an extended partition meant to contain logical partitions and #3 doesn't overlap with any of those logical partition, but it's still invalid and a careful partition manager will fail and do nothing instead of making things worse.
You can use fixparts to fix this issue (according to its manual page):
Back up the current Master Boot Record (including the partition table) in case something goes wrong:
sudo dd if=/dev/sda count=1 > /path/to/sda.mbrThe path of the back-up file
/path/to/sda.mbrshould lie on a persistent storage device, e. g. a connected USB drive, as opposed to the ephemeral file system of a live system.If something does go wrong and after you verified that
/dev/sdastill refers to desired drive (which may change on every boot) you can restore it with the following command:sudo dd if=/path/to/sda.mbr of=/dev/sda count=1
sudo partprobe /dev/sda
Run
fixpartswith the âÂÂlogicalâ (on partition 3), âÂÂsortâ and âÂÂwriteâ (confirmed with yes) commands:printf '%sn' l 3 s w y | sudo fixparts /dev/sda
Yes! after executing all the above commands, I decided to run the Ubuntu installer and it finally showed the unallocated 25 GB free space where I successfully installed Ubuntu. Thanks for your help.
â Apurba
Jun 8 at 5:59
@Apurba. It's nice to hear that you have succeeded. I would like to know what did you put here "path/to/sda.sfdisk" insudo sfdisk - d /dev/sda > /path/to/sda.sfdiskand how much time it took to take backup after giving this command. Thank you.
â PRATAP
Jun 8 at 19:13
@David Forester you mentioned /path/to/sda.sfdisk do we need to edit /path/to/sda or is it a part of command?
â PRATAP
Jun 9 at 4:22
@PRATAP: I clarified the relevant section of my answer. It really needed that improvement. Thanks for pointing it out.
â David Foerster
Jun 9 at 7:54
@DavidFoerstersudo sfdisk -d /dev/sda > /path/to/sda.sfdiskDidn't work for me, so I triedsfdisk -d /dev/sda > sda.partition.table.08-06-2018.txtand it worked. @PRATAP it didn't take any time, as soon as I executed the command, a text file named sda.partition.table.08-06-2018.txt was created in Home
â Apurba
Jun 9 at 16:34
 |Â
show 1 more comment
up vote
0
down vote
accepted
up vote
0
down vote
accepted
Your partition table is invalid: primary partition #3 lies within the range of primary partition #4, which isn't too bad because #4 is an extended partition meant to contain logical partitions and #3 doesn't overlap with any of those logical partition, but it's still invalid and a careful partition manager will fail and do nothing instead of making things worse.
You can use fixparts to fix this issue (according to its manual page):
Back up the current Master Boot Record (including the partition table) in case something goes wrong:
sudo dd if=/dev/sda count=1 > /path/to/sda.mbrThe path of the back-up file
/path/to/sda.mbrshould lie on a persistent storage device, e. g. a connected USB drive, as opposed to the ephemeral file system of a live system.If something does go wrong and after you verified that
/dev/sdastill refers to desired drive (which may change on every boot) you can restore it with the following command:sudo dd if=/path/to/sda.mbr of=/dev/sda count=1
sudo partprobe /dev/sda
Run
fixpartswith the âÂÂlogicalâ (on partition 3), âÂÂsortâ and âÂÂwriteâ (confirmed with yes) commands:printf '%sn' l 3 s w y | sudo fixparts /dev/sda
Your partition table is invalid: primary partition #3 lies within the range of primary partition #4, which isn't too bad because #4 is an extended partition meant to contain logical partitions and #3 doesn't overlap with any of those logical partition, but it's still invalid and a careful partition manager will fail and do nothing instead of making things worse.
You can use fixparts to fix this issue (according to its manual page):
Back up the current Master Boot Record (including the partition table) in case something goes wrong:
sudo dd if=/dev/sda count=1 > /path/to/sda.mbrThe path of the back-up file
/path/to/sda.mbrshould lie on a persistent storage device, e. g. a connected USB drive, as opposed to the ephemeral file system of a live system.If something does go wrong and after you verified that
/dev/sdastill refers to desired drive (which may change on every boot) you can restore it with the following command:sudo dd if=/path/to/sda.mbr of=/dev/sda count=1
sudo partprobe /dev/sda
Run
fixpartswith the âÂÂlogicalâ (on partition 3), âÂÂsortâ and âÂÂwriteâ (confirmed with yes) commands:printf '%sn' l 3 s w y | sudo fixparts /dev/sda
edited Jul 4 at 19:08
answered Jun 7 at 22:51
David Foerster
25.7k1361105
25.7k1361105
Yes! after executing all the above commands, I decided to run the Ubuntu installer and it finally showed the unallocated 25 GB free space where I successfully installed Ubuntu. Thanks for your help.
â Apurba
Jun 8 at 5:59
@Apurba. It's nice to hear that you have succeeded. I would like to know what did you put here "path/to/sda.sfdisk" insudo sfdisk - d /dev/sda > /path/to/sda.sfdiskand how much time it took to take backup after giving this command. Thank you.
â PRATAP
Jun 8 at 19:13
@David Forester you mentioned /path/to/sda.sfdisk do we need to edit /path/to/sda or is it a part of command?
â PRATAP
Jun 9 at 4:22
@PRATAP: I clarified the relevant section of my answer. It really needed that improvement. Thanks for pointing it out.
â David Foerster
Jun 9 at 7:54
@DavidFoerstersudo sfdisk -d /dev/sda > /path/to/sda.sfdiskDidn't work for me, so I triedsfdisk -d /dev/sda > sda.partition.table.08-06-2018.txtand it worked. @PRATAP it didn't take any time, as soon as I executed the command, a text file named sda.partition.table.08-06-2018.txt was created in Home
â Apurba
Jun 9 at 16:34
 |Â
show 1 more comment
Yes! after executing all the above commands, I decided to run the Ubuntu installer and it finally showed the unallocated 25 GB free space where I successfully installed Ubuntu. Thanks for your help.
â Apurba
Jun 8 at 5:59
@Apurba. It's nice to hear that you have succeeded. I would like to know what did you put here "path/to/sda.sfdisk" insudo sfdisk - d /dev/sda > /path/to/sda.sfdiskand how much time it took to take backup after giving this command. Thank you.
â PRATAP
Jun 8 at 19:13
@David Forester you mentioned /path/to/sda.sfdisk do we need to edit /path/to/sda or is it a part of command?
â PRATAP
Jun 9 at 4:22
@PRATAP: I clarified the relevant section of my answer. It really needed that improvement. Thanks for pointing it out.
â David Foerster
Jun 9 at 7:54
@DavidFoerstersudo sfdisk -d /dev/sda > /path/to/sda.sfdiskDidn't work for me, so I triedsfdisk -d /dev/sda > sda.partition.table.08-06-2018.txtand it worked. @PRATAP it didn't take any time, as soon as I executed the command, a text file named sda.partition.table.08-06-2018.txt was created in Home
â Apurba
Jun 9 at 16:34
Yes! after executing all the above commands, I decided to run the Ubuntu installer and it finally showed the unallocated 25 GB free space where I successfully installed Ubuntu. Thanks for your help.
â Apurba
Jun 8 at 5:59
Yes! after executing all the above commands, I decided to run the Ubuntu installer and it finally showed the unallocated 25 GB free space where I successfully installed Ubuntu. Thanks for your help.
â Apurba
Jun 8 at 5:59
@Apurba. It's nice to hear that you have succeeded. I would like to know what did you put here "path/to/sda.sfdisk" in
sudo sfdisk - d /dev/sda > /path/to/sda.sfdisk and how much time it took to take backup after giving this command. Thank you.â PRATAP
Jun 8 at 19:13
@Apurba. It's nice to hear that you have succeeded. I would like to know what did you put here "path/to/sda.sfdisk" in
sudo sfdisk - d /dev/sda > /path/to/sda.sfdisk and how much time it took to take backup after giving this command. Thank you.â PRATAP
Jun 8 at 19:13
@David Forester you mentioned /path/to/sda.sfdisk do we need to edit /path/to/sda or is it a part of command?
â PRATAP
Jun 9 at 4:22
@David Forester you mentioned /path/to/sda.sfdisk do we need to edit /path/to/sda or is it a part of command?
â PRATAP
Jun 9 at 4:22
@PRATAP: I clarified the relevant section of my answer. It really needed that improvement. Thanks for pointing it out.
â David Foerster
Jun 9 at 7:54
@PRATAP: I clarified the relevant section of my answer. It really needed that improvement. Thanks for pointing it out.
â David Foerster
Jun 9 at 7:54
@DavidFoerster
sudo sfdisk -d /dev/sda > /path/to/sda.sfdisk Didn't work for me, so I tried sfdisk -d /dev/sda > sda.partition.table.08-06-2018.txt and it worked. @PRATAP it didn't take any time, as soon as I executed the command, a text file named sda.partition.table.08-06-2018.txt was created in Homeâ Apurba
Jun 9 at 16:34
@DavidFoerster
sudo sfdisk -d /dev/sda > /path/to/sda.sfdisk Didn't work for me, so I tried sfdisk -d /dev/sda > sda.partition.table.08-06-2018.txt and it worked. @PRATAP it didn't take any time, as soon as I executed the command, a text file named sda.partition.table.08-06-2018.txt was created in Homeâ Apurba
Jun 9 at 16:34
 |Â
show 1 more comment
Sign up or log in
StackExchange.ready(function ()
StackExchange.helpers.onClickDraftSave('#login-link');
var $window = $(window),
onScroll = function(e)
var $elem = $('.new-login-left'),
docViewTop = $window.scrollTop(),
docViewBottom = docViewTop + $window.height(),
elemTop = $elem.offset().top,
elemBottom = elemTop + $elem.height();
if ((docViewTop elemBottom))
StackExchange.using('gps', function() StackExchange.gps.track('embedded_signup_form.view', location: 'question_page' ); );
$window.unbind('scroll', onScroll);
;
$window.on('scroll', onScroll);
);
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
StackExchange.ready(
function ()
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2faskubuntu.com%2fquestions%2f1044346%2finstalling-ubuntu-18-04-cant-see-my-partitioned-hdd%23new-answer', 'question_page');
);
Post as a guest
Sign up or log in
StackExchange.ready(function ()
StackExchange.helpers.onClickDraftSave('#login-link');
var $window = $(window),
onScroll = function(e)
var $elem = $('.new-login-left'),
docViewTop = $window.scrollTop(),
docViewBottom = docViewTop + $window.height(),
elemTop = $elem.offset().top,
elemBottom = elemTop + $elem.height();
if ((docViewTop elemBottom))
StackExchange.using('gps', function() StackExchange.gps.track('embedded_signup_form.view', location: 'question_page' ); );
$window.unbind('scroll', onScroll);
;
$window.on('scroll', onScroll);
);
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Sign up or log in
StackExchange.ready(function ()
StackExchange.helpers.onClickDraftSave('#login-link');
var $window = $(window),
onScroll = function(e)
var $elem = $('.new-login-left'),
docViewTop = $window.scrollTop(),
docViewBottom = docViewTop + $window.height(),
elemTop = $elem.offset().top,
elemBottom = elemTop + $elem.height();
if ((docViewTop elemBottom))
StackExchange.using('gps', function() StackExchange.gps.track('embedded_signup_form.view', location: 'question_page' ); );
$window.unbind('scroll', onScroll);
;
$window.on('scroll', onScroll);
);
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Sign up or log in
StackExchange.ready(function ()
StackExchange.helpers.onClickDraftSave('#login-link');
var $window = $(window),
onScroll = function(e)
var $elem = $('.new-login-left'),
docViewTop = $window.scrollTop(),
docViewBottom = docViewTop + $window.height(),
elemTop = $elem.offset().top,
elemBottom = elemTop + $elem.height();
if ((docViewTop elemBottom))
StackExchange.using('gps', function() StackExchange.gps.track('embedded_signup_form.view', location: 'question_page' ); );
$window.unbind('scroll', onScroll);
;
$window.on('scroll', onScroll);
);
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
1
You should not have made conversion from GPT to MBR. i guess your system is Booting in the mode "UEFI". Are you able to Boot to Windows at this time? Can you confirm booting mode first to proceed further?
â PRATAP
Jun 7 at 4:19
No my computer has MBR and is running on UEFI mode
â Apurba
Jun 7 at 7:15
windows 10 cant be run on MBR if the boot mode is in UEFI. are you able to boot to windows in UEFI mode? can you send the pic like this we.tl/HtAe4qiPmI (in windows diskmgmt.msc, select disk0, properties, Volumes tab)
â PRATAP
Jun 7 at 8:30
Sorry for the mistake in the previous comment, I meant to say: "No my computer has MBR and is running on BIOS mode". There is no volumes tab when I click on properties on the drives except for the unallocated 25 GB free space. i.stack.imgur.com/cLU28.png
â Apurba
Jun 7 at 8:45
1
how do I know which is disk 0? For me, it is labelled as Entertainment (E:), Gaming (D:), System (C:) and Stuffs (F:).
â Apurba
Jun 7 at 8:50