PSI am not trolling. I feel you should either learn to use a live cd + chroot to fix such problems. If you don't like that, there is supergrubdisk. In any case, you shouldn't be needing either too often unless you like to break your system on a regular basis.
@x33a @Jristz I don't have blank CD's at the moment. What I do have at the moment is an external USB SATA drive case that I can just plop drives into for repair, modifying, etc. Being able to easily install something like Boot-Repair would be very handy as opposed to getting up and having to skate or ride my bike 120 downtown-sized blocks to the nearest Walmart just to buy blank disks or a thumb drive. Plus all my Arch apps aren't in the Live CD.
Regarding your resistance to using the arch iso on removable media: I personally don't understand how anyone runs any distro without having rescue media at hand. Ask someone you know to pick you up a cheap usb stick whenever they're passing the shop, since you're too lazy to go there yourself.
I ended up finding my old Arch media so I updated all the media's packages after booting, mounted the hard drive with the broken system, then changed the root and cache directories in pacman.conf and re-installed and configured the needed packages. I got lucky.
I want to use boot-repair-disk on my pc. This is a program that is previously burned in a removable media such as CD/DVD/USB stick, and then you boot on it (power off the computer, press the BIOS menu and select the media to boot from there).
Justification Why I need this program to boot:It's a recommended tool for fixing problems of booting, for recovering the system, and for uninstalling OS Ubuntu (what I want to do) it's the recommended way. By the way, Ubuntu it's totally corrupted, I can't boot in it and uninstall from it, because it crashes and the only way out is removing the battery, Ubuntu got corrupted during a update error.
So the situation is this: I downloaded iso for Boot repair disk 64, which is linked in the Ubuntu article from before, and in that article it very clearly says can be written in usb sticks, and also in this instructions from above. I'm insisting on this point because the program is called boot repair disk but of course that's only the name.
I wrote that image into usb-sticks three times with different burners and into two different usb sticks, in all attempts followed this procedure, wich has worked other times with different images (that were Ubuntu 14.04 LTS 64 bit and Debian Jessie 8 64bit), the procedure which is the normal one is:Powering off, inserting usb stick, power on, change boot order to give priority to usb stick, and save changes. And the it boots from the hard drive into the normal GRUB2, like it couldn't boot from usb stick and resorts to the next option, wich is the Hard drive. So I can't use the program. There is not any text or log showing any error or failure, it just ignores it.
For some reason I can't boot from this one. I think maybe it's not a hybrid ISO image, but I don't have sufficient knowledge about that... But I did saw this question, and did the first answer recommendation and in fact it seems like this image wasn't recognized the same way as another one (the Ubuntu one). The Ubuntu one displayed a big output with many options, the image I want to boot displayed a error.
Edit: I forgot to say that it actually boots from a cd r, written with brasero on linux debian. But I still have reasons for wanting it from usb stick, one of them it's slow and cd it's scratched, so it may crash, wich is dangerous because it's a session live from a cd, the only way out is removing power ( the batterie).
I use Boot Repair Disk 64 bit in a multiboot on Yumi (Windows version) and it seems to work fine. I recently lost GRUB on my Win7/Mint dual boot, so only Windows could boot. I ran BRD, clicked on one-click recommended fix option and GRUB was back again. Yumi is a great tool (recently updated and fixed). You can try dd tool too, but be careful: it can be a tricky tool if you're not experienced with it and command line in general. Rufus is a great tool as well (even better than Yumi if you want to burn only one ISO) and it works fine with BRD: in addition on Rufus you can change the partition scheme and target system type: BIOS, UEFI, MBR, GPT...
I checked the ISO, it is not a hybrid. So an image burn won't work, you need either 1) a tool that will make it bootable (unetbootin should do it?) or 2) a smart BIOS that will recognize the USB stick. Try formatting it as FAT32 and just copying the files from inside the ISO to it
Now my question is:
Could I reinstall GRUB on the other SSD where Zorin is installed (is this even possible?) and then take care of the NVME drive and install Windows back on it or should I try to do it the other way around?
I've never had success with Boot Repair disk or any GRUB repair option.
I would use EasyBCD from NeoSmart Technologies solution. This uses Windows MBR so that stays intact and just point the NeoSmart solution to the Linux install. My Vimeo tutorial on dual booting Windows 7 and Zorin 9 covered this.
1 hour 24 mins 15 seconds in.
I finally managed to take on the task. It was dead easy with Boot Repair Disk (64 bit version). The only thing I had to do was to create a partition for GRUB to install, but the ISO even came with GPARTED pre-installed, so that was perfect!
Now I have one bootloader for each drive, which I should have done in the first place. So on start-up I press F9 (boot menu on my HP laptop) if I need to start Windows. Otherwise it automatically boots into Zorin.
I thought this could be a good alternative for me as a linux noob to save my systemdisk and have
the programm for permanent use on the systemdrive in an extra partition. Seems to look to good
to be true ? But if you read the specs on their website it should be possible.
Boot the Debian Wheezy netinst image and pick repair from the options. You can fix your bootloader that way. No matter what, you won't lose your data. If you had to reinstall, you would disconnect your data drives and reconnect after installation.
Super Grub2 - I have a couple extra partitions on my OMV NAS and one has mint installed. For the life of me I cant get grub config to see it. So I just boot super grub and search for the drives and it pops up the other system and I can boot it. I should try boot repair on it eh?!!
Boot Repair Disk - I used this just yesterday when I used clonezilla to restore a partition to a drive. Since I didnt restore the mbr like your problem it just said missing os. BRD found and rebuilt the mbr/grub and I was able to boot the partition I had just restored. Plus its GUI based so extremely easy to use.
Willri, glad to hear the boot repair worked for you! I tried it on my OMV and it showed both bootable raids (MD3=OMV and MD4=MINT) so I THOUGHT it was working. It completed the repair process and I STILL only see the option to boot OMV. I will keep messing with it..
Firstly I installed Linux Mint then Windows 10 on a secondary partition.
Because I forgot to make a separate boot partition... I moved everything 1000MB to the right, and created a ext4 boot partition at the beginning of sda.
Running boot repair on a live Ubuntu USB with the options:
Trying to get my laptop going again. It will not boot to Windows 10 and I used the Boot-Repair-Disk from a USB stick. It completed successfully but still will not boot to windows. It shows the blue windows icon and the circular status indicator near the bottom of the screen and then screen goes dark. During the screen blackout, the power light and hard drive light stay on and about every minute or so, the hard drive light goes off and then solid on again.
If all else fails, boot to a Win10 recovery disk, when you get to the 1st part, press shift+10 to open a command prompt, open a notepad and use it to access your files from the hard drive. Copy said files and paste them to an external drive.
Once I waited a few hours came back to a Windows Screen that I thought was fixed. Keyboard was unresponsive when trying to press Ctrl-Alt-Delete to login. the mouse was active but nothing from keyboard and just the Windows logon screen.
I was handed a hard drive today and told to make a clone. The clone is supposed to be inserted in a workstation and booted up. I've never seen the hardware from the original, but I'm certain it doesn't match that of the workstation. The cloning went smoothly, but when ever I boot the clone it brings up system repair. No matter what I select, it is impossible to recover the system. It cites hardware changes, so maybe because the workstation is different, it won't boot? How can I get a working, bootable copy of this hard drive? I'm open to anything including converting it to a VM. Using NTFS on Windows 7 SP1.
If, for example, in the case of a sata drive, the original workstation use a standard Intel AHCI hard disk controller but the new workstation use a enhanced SATA 6Gb from marvel, then windows doesn't have the proper driver for this new controller and will fail to boot.
I'm helping a friend with his HP CP61-313US notebook computer. Somehow it's not booting from the hard drive. It tries to load Windows and then crashes giving me the black screen where you can choose safe mode, safer networking, etc.
I ordered recovery disks from HP and inserted disc one of the recovery package. It will not boot from the CD. I've gone into the bios options and set the CD drive as the first option. I've done this both from within the F10 bios settings and from the F9 boot order settings. I can hear the CD drive run but it keeps trying to boot from the hard drive.
Is there a way that I can copy this HP recovery disk onto a flash drive myself and try to boot from flash drive. I suppose there is a possibility that the DVD/CD drive is broken. My friend who owns the computer rarely used to drive.
I've determined that the DVD drive on this laptop is either bad or about to fail. I tried creating a Windows repair CD and was able to read the CD. It would give me the "Press any key to boot to CD or DVD" message which I was not getting with the HP factory restore discs. I put the HP factory restore discs in a different computer and tried copying them. I thought perhaps if my drive was about to fail there was something about the factory discs that it would not read but perhaps a copy freshly burned on a blank disk might read. It would almost boot. It would try and then get IO errors on the copied version of the disk. I came to the conclusion I could find other uses for an external DVD USB drive and since they were only $40 I went ahead and bought one. I'm now successfully doing the restore from the original HP recovery disks using the external DV
3a8082e126