LinuxQuestions.org
Latest LQ Deal: Complete CCNA, CCNP & Red Hat Certification Training Bundle
Go Back   LinuxQuestions.org > Forums > Non-*NIX Forums > General
User Name
Password
General This forum is for non-technical general discussion which can include both Linux and non-Linux topics. Have fun!

Notices


Reply
  Search this Thread
Old 11-18-2018, 05:10 AM   #1
lfs1121
Member
 
Registered: Nov 2018
Posts: 31

Rep: Reputation: Disabled
Unhappy Windows 10 disappeared after updating Ubuntu


Hello All,

I was on a dual boot using Windows 10 and Ubuntu. I installed Ubuntu alongside my Windows OS. Recently, I upgraded my Ubuntu OS to its new version Version 18.04. Below is the Ubuntu OS version running on my machine. After this upgrade my Windows disappeared from the boot menu. When I start my machine it only displays the login option for Ubuntu and Advanced option for Ubuntu. Windows is no longer there, however, when I check the disk partitions I see that my Windows 10 partition is still there. When I open the GParted menu on Ubuntu it displays the Windows 10 partition.
Code:
$ lsb_release -a
No LSB modules are available.
Distributor ID:	Ubuntu
Description:	Ubuntu 18.04.1 LTS
Release:	18.04
Codename:	bionic
I am a newbie on Ubuntu. I started using Ubuntu for most of the course requirement in my school.

Any help would be highly appreciated to recover my Windows and data on it.

P.S I have also attached a screenshot of GParted showing my Windows partition.

Best,
Attached Thumbnails
Click image for larger version

Name:	win10.png
Views:	12
Size:	68.6 KB
ID:	29006  

Last edited by lfs1121; 11-18-2018 at 05:11 AM.
 
Old 11-18-2018, 09:18 AM   #2
enorbet
Senior Member
 
Registered: Jun 2003
Location: Virginia
Distribution: Slackware = Main OpSys for decades while testing others to keep up
Posts: 2,015

Rep: Reputation: 1911Reputation: 1911Reputation: 1911Reputation: 1911Reputation: 1911Reputation: 1911Reputation: 1911Reputation: 1911Reputation: 1911Reputation: 1911Reputation: 1911
Did you label the two ntfs partitions "boot" and "diag"? It is my guess that the second ntfs partition, currently labelled "diag", is Windows' hidden boot partition and needs to be flagged to "boot". GParted will handle that easily and proper though you might have to run "update-grub" to let the change be recognized but I'm not certain since I use LILO.

If you'd prefer checking this out, besides being able to see what's on there and determine if such files as "ntldr" are present there and not on the partition you have labelled as "boot", you can download and install any number of live operating systems on a CD, DVD, or USB thumbdrive (affecting nothing on your hard drives) boot any of those to either Linux or what is often called MiniXP these days, and run all manner of diagnostic apps OR you could simply select one of the Boot Managers, like PLOP, which will allow you to engage any and every partition to see what boots and what doesn't.

One great example of such tool-heavy Live Distros is Hirens Boot CD which boots a scaled down version of Windows, a scaled up version of DOS, and a full Linux Desktop, each just laden with superb tools. BTW, these tools are also "sharp" so don't just explore and "try stuff" without a bit of research but diagnostic apps and boot loaders are entirely benign and safe. No worries.

Last edited by enorbet; 11-18-2018 at 09:35 AM.
 
Old 11-18-2018, 11:27 AM   #3
lfs1121
Member
 
Registered: Nov 2018
Posts: 31

Original Poster
Rep: Reputation: Disabled
Quote:
Originally Posted by enorbet View Post
Did you label the two ntfs partitions "boot" and "diag"? It is my guess that the second ntfs partition, currently labelled "diag", is Windows' hidden boot partition and needs to be flagged to "boot". GParted will handle that easily and proper though you might have to run "update-grub" to let the change be recognized but I'm not certain since I use LILO.

If you'd prefer checking this out, besides being able to see what's on there and determine if such files as "ntldr" are present there and not on the partition you have labelled as "boot", you can download and install any number of live operating systems on a CD, DVD, or USB thumbdrive (affecting nothing on your hard drives) boot any of those to either Linux or what is often called MiniXP these days, and run all manner of diagnostic apps OR you could simply select one of the Boot Managers, like PLOP, which will allow you to engage any and every partition to see what boots and what doesn't.

One great example of such tool-heavy Live Distros is Hirens Boot CD which boots a scaled down version of Windows, a scaled up version of DOS, and a full Linux Desktop, each just laden with superb tools. BTW, these tools are also "sharp" so don't just explore and "try stuff" without a bit of research but diagnostic apps and boot loaders are entirely benign and safe. No worries.
I ran update-grub several times but it did not fetch. I also ran some boot repair mentioned here https://help.ubuntu.com/community/Boot-Repair
I followed option 2 with the following instructions
Code:
sudo add-apt-repository ppa:yannubuntu/boot-repair
sudo apt-get update
sudo apt-get install -y boot-repair && boot-repair
At the end of the process, it generated a note and I saved it. It mentioned that if the problem did not fix, I email the link it generated to boot.repair@gmail.com Here is the link http://paste.ubuntu.com/p/HhMdNJkYbs/

I am waiting to receive from their end.

Last edited by lfs1121; 11-18-2018 at 11:44 AM.
 
Old 11-18-2018, 12:33 PM   #4
enorbet
Senior Member
 
Registered: Jun 2003
Location: Virginia
Distribution: Slackware = Main OpSys for decades while testing others to keep up
Posts: 2,015

Rep: Reputation: 1911Reputation: 1911Reputation: 1911Reputation: 1911Reputation: 1911Reputation: 1911Reputation: 1911Reputation: 1911Reputation: 1911Reputation: 1911Reputation: 1911
Quote:
Originally Posted by lfs1121 View Post
I ran update-grub several times but it did not fetch. I also ran some boot repair mentioned here https://help.ubuntu.com/community/Boot-Repair
I followed option 2 with the following instructions
Code:
sudo add-apt-repository ppa:yannubuntu/boot-repair
sudo apt-get update
sudo apt-get install -y boot-repair && boot-repair
At the end of the process, it generated a note and I saved it. It mentioned that if the problem did not fix, I email the link it generated to boot.repair@gmail.com Here is the link http://paste.ubuntu.com/p/HhMdNJkYbs/

I am waiting to receive from their end.
OK but did you change the flags on the ntfs partitions before you ran update-grub? or do you know for a fact that you overrode the default of creating a hidden boot partition making your current flags accurate? I suspect not.

Last edited by enorbet; 11-18-2018 at 12:35 PM.
 
Old 11-18-2018, 11:22 PM   #5
syg00
LQ Veteran
 
Registered: Aug 2003
Location: Australia
Distribution: Lots ...
Posts: 17,241

Rep: Reputation: 2638Reputation: 2638Reputation: 2638Reputation: 2638Reputation: 2638Reputation: 2638Reputation: 2638Reputation: 2638Reputation: 2638Reputation: 2638Reputation: 2638
There are several inconsistencies here.
- I find it hard to comprehend Win10 on a nvme disk that is not gpt. Was this a Win10 machine or Win7/8 that was upgraded to Win10 ?.
- No boot info summary
- os-prober can't find Windows loader code.

It looks like a "legacy mode" install (or update) has been done over the top of a UEFI (gpt) install. So that's screwed the partition table and wiped out what was the EFI partition /dev/nvme0n1p1. There is no way that should be ext4 if this was originally a Win10 machine.

You might be able to get to recover your data, annd you might be able to boot the recovery partition i you don't have any other Win10 media to recover from - I always create a recovery USB for myself.
 
Old 12-04-2018, 07:50 AM   #6
lfs1121
Member
 
Registered: Nov 2018
Posts: 31

Original Poster
Rep: Reputation: Disabled
Quote:
Originally Posted by syg00 View Post
There are several inconsistencies here.
- I find it hard to comprehend Win10 on a nvme disk that is not gpt. Was this a Win10 machine or Win7/8 that was upgraded to Win10 ?.
- No boot info summary
- os-prober can't find Windows loader code.

It looks like a "legacy mode" install (or update) has been done over the top of a UEFI (gpt) install. So that's screwed the partition table and wiped out what was the EFI partition /dev/nvme0n1p1. There is no way that should be ext4 if this was originally a Win10 machine.

You might be able to get to recover your data, annd you might be able to boot the recovery partition i you don't have any other Win10 media to recover from - I always create a recovery USB for myself.
Hello,

Yes, this was originally a Windows 10 machine and I installed Ubuntu later. I have a backup of all the data on my Win10 but not a backup of the OS itself. Even if I have to reinstall a new Win10, I am willing to do that.
 
Old 12-04-2018, 11:57 AM   #7
enorbet
Senior Member
 
Registered: Jun 2003
Location: Virginia
Distribution: Slackware = Main OpSys for decades while testing others to keep up
Posts: 2,015

Rep: Reputation: 1911Reputation: 1911Reputation: 1911Reputation: 1911Reputation: 1911Reputation: 1911Reputation: 1911Reputation: 1911Reputation: 1911Reputation: 1911Reputation: 1911
You should be able to view the data on each partition from Ubuntu. This might require checking to see if the Windows Boot Partition is flagged "Hidden" but toggling that will have no consequence just for temporary reading file names to check. There are admittedly other inconsistencies that should be addressed but first I strongly suspect the Win 10 OpSys is still intact. Linux does not by default delete other systems. If as I suspect, this is the case all you need do is repair the boot partition. Without changing anything you should be able to verify from Ubuntu (File Manager) that the main Win10 structure is intact.

There is The Windows Way of doing this https://www.howtogeek.com/howto/3252...ader-problems/ (same for Win10 only slightly different for both 7 and 10 on UEFI systems) and also numerous live CD/Thumbdrive repair disks/Utilities as well as some that will run right from Ubuntu. There should be no need for any expense other than a little time. I have yet to see a laptop come from the factory without some repair option. Once Windows Bootloader is repaired/restored you can add or delete Ubuntu as desired, or if UEFI, just leave that as is, though you might do well to research UEFI boot configuration for precise instruction.

Last edited by enorbet; 12-04-2018 at 11:58 AM.
 
  


Reply


Thread Tools Search this Thread
Search this Thread:

Advanced Search

Posting Rules
You may not post new threads
You may not post replies
You may not post attachments
You may not edit your posts

BB code is On
Smilies are On
[IMG] code is Off
HTML code is Off



Similar Threads
Thread Thread Starter Forum Replies Last Post
Swedish UI disappeared from Firefox after updating to 59.0 _HG_ Linux - Software 4 03-18-2018 07:36 PM
[SOLVED] Ubuntu 12.04: Updating via ssh. Dropped connection. Updating locked. How to continue robsbots Linux - General 10 10-02-2014 08:51 PM
rpm changes are not updating immediately and updating after some time. shri_22ram Linux - Newbie 1 05-13-2013 01:50 PM
Since updating to Ubuntu HH *.19 my restricted Nvidia driver has disappeared. SimbaSpirit Linux - Kernel 2 08-27-2008 12:39 AM
Updating VMWare After Updating CentOS Linux31 Red Hat 2 09-18-2007 03:49 PM

LinuxQuestions.org > Forums > Non-*NIX Forums > General

All times are GMT -5. The time now is 11:31 AM.

Main Menu
Advertisement
My LQ
Write for LQ
LinuxQuestions.org is looking for people interested in writing Editorials, Articles, Reviews, and more. If you'd like to contribute content, let us know.
Main Menu
Syndicate
RSS1  Latest Threads
RSS1  LQ News
Twitter: @linuxquestions
Facebook: linuxquestions Google+: linuxquestions
Open Source Consulting | Domain Registration