Linux install apparently destroyed my Windows MBR or Boot partition (Win7 on a separate hard drive)

AnneF · 01-16-2021, 06:17 PM

Quote:

Originally Posted by colorpurple21859

generate a boot-info file and post so someone can give good advice.
https://help.ubuntu.com/community/Boot-Info
on a side note windows 7 isn't normally installed in efi mode but legacy/csm mode. If the ubuntu is installed in efi mode, the grub boot-loader won't be able to boot windows 7. If windows 7 is still intact you may be able to go into the bios boot menu, select the hard drive option, not sure what it will be called, it won't have efi in the name.

I started off trying to do this, but one thing led to another that had to be done first, etc. and I got lost.

I'm going to try this tomorrow since the source.list has been fixed now (I think), so maybe I can get boot-info and produce a report.
I tried one boot-info repair disk site, but it was in French. I'll try again tomorrow.

UPDATE: Apparently sources.list is not fixed. Apt is still looking for repositories on a CDRom

Anne
.

quickbreakfast · 01-16-2021, 06:39 PM

Quote:

Originally Posted by AnneF

I also tried:

sudo update-grub

which was successful, but didn't change anything that I could see - still wouldn't boot windows with ubuntu booting first.
.

If you can now get into windows, then I'd leave the computer along. (to me it's like if I'm heading for London, then I don't particularly care whether I go via Singapore or Vancover as long as I, eventually, get to London.

However I did find this: Unable to boot into Windows after installing Ubuntu, how to fix? https://askubuntu.com/questions/2179...ntu-how-to-fix which might help. Sure the original post is 8 years old. But if it works, then I'll not argue.

Before you try to install anything, please update, and upgrade your ubuntu system.

Code:

 sudo update
sudo upgrade

By the way. I'm delighted to see you back cause I thought you might have given up on Linux.

Hope your extended family is on the mend.

yancek · 01-17-2021, 09:06 AM

Quote:

I'm going to try this tomorrow since the source.list has been fixed now (I think), so maybe I can get boot-info and produce a report.

It would be simpler to use the Ubuntu install USB to do this as then the sources.list file will not have been modified giving you all the problems you had with the installed Ubuntu. Boot the Ubuntu install USB and go to the site below and download boot repair according to the instructions on the site. When you run boot repair, do not try to make any repairs but select the option to Create BootInfo Summary and post the link you get when it finishes so members can review it.

https://help.ubuntu.com/community/Boot-Repair

In post 37, you have output from the parted command which shows your windows is on a GPT drive. According to Microsoft, windows on a GPT drive must be installed in EFI mode. That same post indicates that Ubuntu is on an msdos drive which would mean a Legacy install of Ubuntu. This also shows that you have an Extended partition on the Ubuntu drive which confirms an msdos (Legacy) drive as Extended partitions do not exist on a GPT drive, all partitions are primary. This is a problem as a Legacy install of Grub will not boot an EFI install of windows.

In post 50, you indicate that you actually booted windows once from Grub but then reinstalled Ubuntu. If that was the case, then both windows 7 and Ubuntu would have been installed in the same mode, both EFI or both Legacy and when you reinstalled Ubuntu you installed in the wrong mode. Since you indicate that windows 10 was originally on the machine, it was most likely installed EFI.

I would suggest that you run boot repair from the link above and use the instructions above (post 75) to mount the EFI partition. When you do that, look on the EFI partition for Microsoft and ubuntu folders. In the Microsoft folder there should be a Boot folder with a number of files. Look specifically there for a file named bootmgfw.efi. Also check to see if there is an ubuntu folder on the EFI partition and if there is, look for a grub.cfg file and post its contents here. It is a small file with only 3 lines. Mounting the EFI partition and checking those files will tell us which is installed EFI.

AnneF · 01-17-2021, 05:00 PM

Quote:

Originally Posted by yancek

It would be simpler to use the Ubuntu install USB to do this as then the sources.list file will not have been modified giving you all the problems you had with the installed Ubuntu. Boot the Ubuntu install USB and go to the site below and download boot repair according to the instructions on the site. When you run boot repair, do not try to make any repairs but select the option to Create BootInfo Summary and post the link you get when it finishes so members can review it.

https://help.ubuntu.com/community/Boot-Repair

Getting Boot-Repair
1. 1st option : get a disk including Boot-Repair
2. 2nd option : install Boot-Repair in Ubuntu
I had tried to do option 2, so that I would have boot-repair installed in Ubuntu (beating myself on the head), but it didn't work, looks like it was still looking for a CDRom. Here is the output:

Code:

xxx@YODA:~$ sudo add-apt-repository ppa:yannubuntu/boot-repair
[sudo] password for xxx:  
   Simple tool to repair frequent boot problems.
 Website: https://sourceforge.net/p/boot-repair/home
  More info: https://launchpad.net/~yannubuntu/+a...tu/boot-repair
 Press [ENTER] to continue or Ctrl-c to cancel adding it.
 Ign:1 cdrom://Ubuntu 20.04.1 LTS _Focal Fossa_ - Release amd64 (20200731) focal InRelease
 Err:2 cdrom://Ubuntu 20.04.1 LTS _Focal Fossa_ - Release amd64 (20200731) focal Release
   Please use apt-cdrom to make this CD-ROM recognized by APT. apt-get update cannot be used to add new CD-ROMs
 Hit:3 http://us.archive.ubuntu.com/ubuntu focal InRelease
 Get:4 http://security.ubuntu.com/ubuntu focal-security InRelease [109 kB]      
 Get:5 http://us.archive.ubuntu.com/ubuntu focal-updates InRelease [114 kB]     
 Hit:6 http://archive.canonical.com/ubuntu focal InRelease                      
 Hit:7 http://ppa.launchpad.net/yannubuntu/boot-repair/ubuntu focal InRelease   
 Get:8 http://security.ubuntu.com/ubuntu focal-security/main amd64 DEP-11 Metadata [24.2 kB]
 Get:9 http://us.archive.ubuntu.com/ubuntu focal-updates/main amd64 DEP-11 Metadata [264 kB]
 Reading package lists... Done              
 E: The repository 'cdrom://Ubuntu 20.04.1 LTS _Focal Fossa_ - Release amd64 (20200731) focal Release' does not have a Release file.
 N: Updating from such a repository can't be done securely, and is therefore disabled by default.
 N: See apt-secure(8) manpage for repository creation and user configuration details.

……......It seemed to still be looking for files on the CDRom
Then I realized I had a thumbdrive (empty) in the slot, so I removed it and tried again, thinking I still had the same command in the clipboard. However, I had copied the above to show you, and THAT is what I pasted into the terminal. What can I say – I’m 80, I make mistakes. Here is the output from that, in case I did something awful: (for me, just look at the prompts in the bottom lines).

Code:

xxx@YODA:~$ xxx@YODA:~$ sudo add-apt-repository ppa:yannubuntu/boot-repair
 xxx@YODA:~$: command not found
 xxx@YODA:~$ [sudo] password for xxx:  
 [sudo]: command not found
 xxx@YODA:~$  Simple tool to repair frequent boot problems.
 Simple: command not found
 xxx@YODA:~$  
 xxx@YODA:~$ Website: https://sourceforge.net/p/boot-repair/home
 Website:: command not found
 xxx@YODA:~$  More info: https://launchpad.net/~yannubuntu/+archive/ubuntu/boot-repair
 Command 'More' not found, did you mean:
   command 'kore' from deb kore (3.3.1-1)
   command 'more' from deb util-linux (2.34-0.1ubuntu9.1)
 Try: sudo apt install <deb name>
 xxx@YODA:~$ Press [ENTER] to continue or Ctrl-c to cancel adding it.
 Press: command not found
 xxx@YODA:~$  
 xxx@YODA:~$ Ign:1 cdrom://Ubuntu 20.04.1 LTS _Focal Fossa_ - Release amd64 (20200731) focal InRelease
 bash: syntax error near unexpected token `('
 xxx@YODA:~$ Err:2 cdrom://Ubuntu 20.04.1 LTS _Focal Fossa_ - Release amd64 (20200731) focal Release
 bash: syntax error near unexpected token `('
 xxx@YODA:~$   Please use apt-cdrom to make this CD-ROM recognized by APT. apt-get update cannot be used to add new CD-ROMs
 Please: command not found
 xxx@YODA:~$ Hit:3 http://us.archive.ubuntu.com/ubuntu focal InRelease
 Hit:3: command not found
 xxx@YODA:~$ Get:4 http://security.ubuntu.com/ubuntu focal-security InRelease [109 kB]      
 Get:4: command not found
 xxx@YODA:~$ Get:5 http://us.archive.ubuntu.com/ubuntu focal-updates InRelease [114 kB]     
 Get:5: command not found
 xxx@YODA:~$ Hit:6 http://archive.canonical.com/ubuntu focal InRelease                      
 Hit:6: command not found
 xxx@YODA:~$ Hit:7 http://ppa.launchpad.net/yannubuntu/boot-repair/ubuntu focal InRelease   
 Hit:7: command not found
 xxx@YODA:~$ Get:8 http://security.ubuntu.com/ubuntu focal-security/main amd64 DEP-11 Metadata [24.2 kB]
 Get:8: command not found
 xxx@YODA:~$ Get:9 http://us.archive.ubuntu.com/ubuntu focal-updates/main amd64 DEP-11 Metadata [264 kB]
 Get:9: command not found
 xxx@YODA:~$ Reading package lists... Done              
 Reading: command not found
 xxx@YODA:~$ E: The repository 'cdrom://Ubuntu 20.04.1 LTS _Focal Fossa_ - Release amd64 (20200731) focal Release' does not have a Release file.
 E:: command not found
 xxx@YODA:~$ N: Updating from such a repository can't be done securely, and is therefore disabled by default.
 > N: See apt-secure(8) manpage for repository creation and user configuration details.
 > sudo add-apt-repository ppa:yannubuntu/boot-repair
  >

Which left me stuck in a terminal window that has no proper prompt that understands "exit" - so I pretty much can't do anything in terminal until I know how to exit the process that it is in.

So I went back and tried to read about “getting a disk including boot-repair”:

"get a disk including Boot-Repair
The easiest way to use Boot-Repair is to create a disk containing the tool (eg Boot-Repair-Disk, a disk starting Boot-Repair automatically), and boot on it."
"Remark : it is recommended to install the ISO on a live-USB (eg via UnetBootin or LiliUSB or Universal USB Installer)."

"Do not burn it on a DVD if your computer has Windows8 pre-installed, or if your boot is in EFI mode."

Me: Windows7 definitely IS in EFI mode.

So, THEN I went to Unetbootin
UNetbootin - Downloads for Linux
Ubuntu Package

"To install UNetbootin from the Ubuntu PPA, run the commands:"

Code:

sudo add-apt-repository ppa:gezakovacs/ppa 
sudo apt-get update
 sudo apt-get install unetbootin

..which I can’t do right now because I’m stuck with no prompt in the terminal and can't reboot from thumbdrive for the same reason.
I’m sure its a simple matter to end the current process, I just don’t know what it is.
I need Unetbootin (app) and boot-repair (ISO) in order to CREATE a boot-repair disk, in order to get the boot-info needed to see what to do in order to repair the windows boot partition. However, I can get NONE of these because apt is apparently looking for a repository on CDRom, which brings us back to sources.list. Although, I will try to get UNetbootin with apt once I can shut the terminal down so I can reboot with my Ubuntu (try/install) thumbdrive.

I found and downloaded “boot-repair-disk-64bit.iso” from this site: https://www.majorgeeks.com/mg/getmir..._64_bit,1.html
Can I use that, and create a bootable USB with Rufus (which I do have on my original Ubuntu (try/install) thumbdrive)? I don't suppose UNetbootin might be on it too?

I haven't tried to get it from the terminal using my Ubuntu try/install thumbdrive, but I will do that next, as soon as I can close out the terminal process to reboot.

Sorry, I know this is a mess - I had to do a lot of cut and paste and I'm still having trouble with Libre Office - and still can't find Abiword for Ubuntu.
--Anne

yancek · 01-17-2021, 05:23 PM

Quote:

I’m stuck with no prompt in the terminal and can't reboot from thumbdrive for the same reason.

You can get out of the terminal by typing exit and hitting the Enter key OR you can simply click the little x in the orange circle in the upper right of of the terminal window.

Quote:

I haven't tried to get it from the terminal using my Ubuntu try/install thumbdrive, but I will do that next

That is your best option because it appears from your last post that your sources.list on the installed Ubuntu is still a mess. That won't happen booting from Ubuntu on the USB which you used to install Ubuntu. I would also suggest that you go to the site below instead of the other site to get boot repair and use the 2nd option on that site and, do not try to make any repairs but select the option to Create BootInfo Summary as explained at the link below.

https://help.ubuntu.com/community/Boot-Repair

AnneF · 01-17-2021, 05:27 PM

Quote:

Originally Posted by quickbreakfast

If you can now get into windows, then I'd leave the computer alone.

I'd be quite happy with either route, but I still can't get to London - by any means.

Quote:

However I did find this: Unable to boot into Windows after installing Ubuntu, how to fix? https://askubuntu.com/questions/2179...ntu-how-to-fix which might help.

I'll try that, thanks.

Quote:

Before you try to install anything, please update, and upgrade your ubuntu system.

Code:

 sudo update
 sudo upgrade

I've been afraid that might break something, but I did it and it popped up a little window with a progress bar, which never finished apparently - after hours, I closed it manually. I wonder if I just ought to backup my data and install Kubuntu and start fresh with Linux? Then try to fix Win7.
I have another internal 1TB HDD, I could install it there without touching the Ubuntu installation and maybe it would be working better and who knows, grub might pick up windows for booting?

Quote:

By the way. I'm delighted to see you back cause I thought you might have given up on Linux.

Thank you so much. I was afraid y'all might be getting tired of trying to help me with this. I don't give up easily, but I'm a bit slower these days and you all have been so generous already.

Code:

 Hope your extended family is on the mend.

Thank you for your well wishes. I'm afraid there won't be any mending. Primary Progressive Multiple Sclerosis is very like ALS (Lou Gerhig's Disease). I just pray that he doesn't suffer so much.

--Anne
.

AnneF · 01-17-2021, 06:06 PM

Quote:

Originally Posted by yancek

In post 37, you have output from the parted command which shows your windows is on a GPT drive. According to Microsoft, windows on a GPT drive must be installed in EFI mode. That same post indicates that Ubuntu is on an msdos drive which would mean a Legacy install of Ubuntu. This also shows that you have an Extended partition on the Ubuntu drive which confirms an msdos (Legacy) drive as Extended partitions do not exist on a GPT drive, all partitions are primary. This is a problem as a Legacy install of Grub will not boot an EFI install of windows.

From all my partition information, Win7 is GPT and EFI and FAT32 (although the BIOS LOOKS like legacy to me). Win10 was replaced with Win7 before I got the machine (prob why the EFI - they must not have done a clean install) Ubuntu is definitely legacy, because I specifically remember installing it that way.

If I install Kubuntu on my third HDD, should I install it as the other choice - I think it was UEFI. Is that more complicated to use? I think fixing Windows boot might be easier from a Linux distro that is actually working right itself, don't you?

Quote:

In post 50, you indicate that you actually booted windows once from Grub but then reinstalled Ubuntu.

I think I said I THINK I booted windows once from Ubuntu, but I was probably mistaken because Win7's boot flag is "boot, esp" (I think that was "esp" - something like that anyway). It shows as GPT, EFI, FAT32. It must have been that I booted Windows from the Lenovo's F10 boot interruption to select a boot drive.

I don't suppose there is any way to get Win7 boot onto a legacy partition, without reinstalling the whole system - and I'd have to buy another copy (installation copy) of Win7 to do that.

I'm a bit concerned about the difference in drive names when installing things. I know that Windows is on 500GB Disk0 (a Hatachi) according to BIOS, and sba according to Linux (boot on partition 1 in both cases). My other two internal drives are another 500GB WD and a 1TB WD, which I can tell apart by their size. But if the size isn't given and the disk mfg isn't given, I don't know how to tell which is which. Will Unbootin provide me with enough information to tell them apart?

Would Kubuntu work just as well on an EFI partition? (UEFI sounded more complicated)

.

AnneF · 01-17-2021, 06:15 PM

Quote:

Originally Posted by yancek

You can get out of the terminal by typing exit and hitting the Enter key OR you can simply click the little x in the orange circle in the upper right of of the terminal window.

I did that when trying to edit sources.list, but it created a ".save" file, & said the process was terminated incorrectly. I was instructed how to delete the extra file, but I'll bet that's why sources.list isn't fixed - the ".save" file I deleted must have been the one with the changes.

I tried "exit, enter" but apparently the ">" wasn't a prompt that understood "exit". I will go ahead and just close the terminal, then, if it won't hurt anything. Thanks. --Anne
.

quickbreakfast · 01-17-2021, 06:17 PM

Quote:

Originally Posted by AnneF

Code:

 Ign:1 cdrom://Ubuntu 20.04.1 LTS _Focal Fossa_ - Release amd64 (20200731) focal InRelease
 Err:2 cdrom://Ubuntu 20.04.1 LTS _Focal Fossa_ - Release amd64 (20200731) focal Release
             
 E: The repository 'cdrom://Ubuntu 20.04.1 LTS _Focal Fossa_ - Release amd64 (20200731) focal Release' does not have a Release file.
 N: Updating from such a repository can't be done securely, and is therefore disabled by default.
 N: See apt-secure(8) manpage for repository creation and user configuration details.

……......It seemed to still be looking for files on the CDRom

It does indeed look like it is looking for your cd rom. Have you editted your /etc/apt/sources.list and put a # infront of the lines which begin with cdrom and removed the # the supported mirrors?

Quote:

What can I say – I’m 80, I make mistakes. Here is the output from that, in case I did something awful: (for me, just look at the prompts in the bottom lines).

She who does nothing never makes a mistake.

For example I suggested the wrong code. Try

Code:

 sudo apt update
sudo apt upgrade

You can have several terminals open at the same time. Just don't ask two of them to be root or do the same job. And clicking the top right 'x" should close them (and stop whatever it was doing)

Quote:

Sorry, I know this is a mess - I had to do a lot of cut and paste and I'm still having trouble with Libre Office - and still can't find Abiword for Ubuntu.

Abiword will become available when you have connected to a mirror.

quickbreakfast · 01-17-2021, 06:27 PM

Quote:

Originally Posted by AnneF

I was instructed how to delete the extra file, but I'll bet that's why sources.list isn't fixed - the ".save" file I deleted must have been the one with the changes.

lets find out. Type

Code:

 ls /etc/apt/sources*

you should only have one file with sources.list as it's complete name. Let us know if there is anything after the word "list"

colorpurple21859 · 01-17-2021, 07:39 PM

open a terminal
This command should comment out the cdrom line in sources.list

Code:

sudo sed -e '/cdrom/ s/^#*/#/' -i /etc/apt/sources.list

and allow to run

Code:

sudo apt-update

yancek · 01-18-2021, 08:44 AM

In post 37, you posted the output of the parted command which you ran from Ubunu. This shows the hard drive on which your windows install exists is GPT requiring an EFI install for windows. The same output shows the drive on which you have Ubuntu installed is msdos or Legacy. Given that, the Ubuntu Grub bootloader will NOT boot an EFI install of windows, ever.

In post 78, you posted information indicating you were unable to get boot repair downloaded. The output explicitly shows that your sources.list still has problems. Looking back through your posts, I see that you started trying to fix this 18 days ago and several members have spent time trying to help. Question is, why? You don't need to do that when you have a perfectly good sources.list on the Ubuntu install USB. You can install boot-repair just as easily and with the same commands on the Ubuntu. I don't know why you keep trying to install boot repair on the installed Ubuntu as in all likelihood, you are going to have to reinstall it anyway.

https://help.ubuntu.com/community/Boot-Repair

In one of your posts yesterday you state: Windows7 definitely IS in EFI mode.

Why do you think that? Because you have an EFI partition on the windows drive? Doesn't mean anything as Ubuntu could have put its EFI boot files there and created that partition during the install. Simplest way to actually determine this is by mounting the EFI partition which I explained in one of my posts yesterday.

Quote:

I wonder if I just ought to backup my data and install Kubuntu and start fresh with Linux?

Yes to the first although you've indicated in multiple posts that you have backups? From the information you have posted, you are going to have to reinstall again, Ubuntu or Kubuntu.

Quote:

Then try to fix Win7.

Well, that's the problem isn't it? Since you have indicated that you cannot even boot windows 7 from the BIOS and you won't post information on the EFI partition, you're going to have a hard time booting windows and not likely to get it to boot from Ubuntu Grub either. Boot repair isn't magic, it will never enable anyone to boot a windows system that has corrupted/missing boot files. If you were able to get boot repair, there may be enough information so that someone could suggest an alternative.

And to repeat, stop trying to mess with your sources.list on the installed Ubuntu, use Ubuntu on the USB.

AnneF · 01-18-2021, 03:37 PM

Quote:

Originally Posted by yancek

Ubuntu Grub bootloader will NOT boot an EFI install of windows, ever.

In post 78, you posted information indicating you were unable to get boot repair downloaded. The output explicitly shows that your sources.list still has problems. Looking back through your posts, I see that you started trying to fix this 18 days ago and several members have spent time trying to help. Question is, why? You don't need to do that when you have a perfectly good sources.list on the Ubuntu install USB.

https://help.ubuntu.com/community/Boot-Repair

In one of your posts yesterday you state: Windows7 definitely IS in EFI mode.

Why do you think that? Because you have an EFI partition on the windows drive? Doesn't mean anything as Ubuntu could have put its EFI boot files there and created that partition during the install.

Boot repair isn't magic, it will never enable anyone to boot a windows system that has corrupted/missing boot files.
Since you have indicated that you cannot even boot windows 7 from the BIOS and you won't post information on the EFI partition, you're going to have a hard time booting windows and not likely to get it to boot from Ubuntu Grub either.

I'm going to install Kubuntu on my 3rd HDD, so I have something that is actually working properly that may let me follow the instructions as given.

I'm also going to go thru all of these suggestions, one at a time, to try to understand how to implement all of you all's recommendations. There is so much, and I know so little, I'm getting confused - I'm way slower than you guys are.

Give me some time to get my head around everything, say 2 weeks (I'll be out of town part of that time, to help with my grandson), and I'll come back with Kubuntu installed and (hopefully) with a boot-repair report, and with whatever else I've been able to learn/do with all this information, from a working copy of Kubuntu.

Oh, one question before I go....
I think Win7 boot is EFI because this pc originally contained Windows 10.
Should I install Kubuntu as UEFI?

--Anne
.

colorpurple21859 · 01-18-2021, 03:45 PM

Code:

Should I install Kubuntu as UEFI?

I think this is the best choice based on the your other posts in this thread.

quickbreakfast · 01-18-2021, 04:16 PM

Quote:

Originally Posted by AnneF

Give me some time to get my head around everything, say 2 weeks (I'll be out of town part of that time, to help with my grandson),

Enjoy the holiday.

Quote:

and I'll come back with Kubuntu installed ............ from a working copy of Kubuntu.

That's an interesting idea, but I doubt it'll be quite as simple as copying a working copy. However

If you know someone who's got a working copy of any of the ubuntu clan of distro's, you should be able to get them to sort out your ubuntu install just for the asking (and an explanation of what went wrong).

Which, considering you wanted to fix the problem(s), might not be what you wanted but it is gets you to London then I'd be content.

Quote:

Oh, one question before I go....
I think Win7 boot is EFI because this pc originally contained Windows 10.
Should I install Kubuntu as UEFI?.

BEFORE you install anything on your third HDD, please ensure you have backed up all the data on your third HDD.

imo, kubuntu should be installed with an UEFI partition/format. Not because of what was previously on the computer. But because your windows OS has a EFI partition.