For anyone with a separate /boot partition, when specifying your "root" at the GRUB prompt: set root=[*BOOT* partition] (example: set root=(hd0,gpt2)) linux [vmlinuz file] root=[*ROOT* partition] (example: linux */vmlinuz* root=/dev/sda3) Your vmlinuz file and initrd image are at the root of your boot partition. If you find this method confusing, here's an alternate method: kzbin.info/www/bejne/fHqkqa2weploick
@eggi91Ай бұрын
I only find initramfs files in the boot partition. Where can i find the initrd file?
@budthecyborg4575Ай бұрын
With Windows deleting everyone's bootloaders this must be a pretty popular video.
@jannikwinkler3544Ай бұрын
@@budthecyborg4575 thats how it is.
@carloscarbajal8233Ай бұрын
Thanks a bunch!!! One note for those who might get an error saying "bad shim signature" when trying to mount the root partition: linux [vmlinuz file] root=/dev/sdXY You need to disable Secure Boot in your BIOS. It got re-enabled for me after running a BIOS update on an MSI motherboard.
@h20andmore4 ай бұрын
Hello, thank you for the good work you are doing teaching about linux and all it's tools. I have been using linux on my laptop for 4 years, not the same distro mind you. I have had some GRUB2 failures (misshaps) which have made me cringe. Many times I have attempted to learn and understand chrooting and what steps are necessary for success. I did succeed once on ARCH following Chris Titus video but I messed it up the next time. I watched your video today on the alternate method which made a lot of sense. So, I indulged and also watched your video on using a live boot usb method. Came home from work, flashed a USB and followed all the steps I typed listening to your video. HOTDOG! It worked like a charm. I'm very happy to finally be able to not only be able to do it but know I can repeat it. Love your deliberate controlled speed of presentation. Clear pronunciation and keeping your hands out of the video, good job. The best part is you are concise! Thank you. I never subscribe to a channel, but you ask me to, so I did. I'll keep watching, friend.
@ditzytony5113Ай бұрын
For the ones that didn't figure it even after watching 1000+ videos on it, this was my situation: I have 2 drives that are of the same model both installed onto my pc. When I first downloaded Linux onto my drive, I accidentally chose the wrong one without ever knowing about it. How I ended up here was, I was messing with my computer and when I rebooted it, It would not boot so I had to go into grub. I followed dozens of video tutorials to try and fix it but to no avail. What I did next was, I physically opened my computer, removed the "second" drive from the second slot on the motherboard, and checked in the disk software using a bootable USB(you can also check in grub and in the terminal) and noticed that my "Main drive" was in the second slot on my motherboard. So this whole time I should have been repairing (hd1,gpt2) instead of (hd0,gpt2). This problem happened to me because like I said earlier, when I first installed Linux, I had installed it onto my "second" drive in the second slot in my motherboard. My recommendation is: Take out all your drives but leave one, check to see if that's the main drive(I found mine because my "second" drive had a partition in it, so by default, it had to be my "first" drive. Then follow this KZbin tutorial and you should be set. Edit: I have another problem. when I only have that one drive with linux installed, it boots and everything works fine. But when I add my additional drive to my computer, my computer crashes and I get sent to the grub menu again. hmm... strange. I followed the this repair grub tutorial again but it doesn't seem to work. I think I might go back to USB bootable drive to see if that "second" drive is mounted because if it is, I think it might be set to root partition and might be the reason why it keeps crashing. I'll keep you guys updated.
@poxel771928 күн бұрын
Thank you so much for the video! I dual boot Kubuntu and Windows 11 and for me reinstalling GRUB and rebooting was enough!
@BOUDAIRABaha3 ай бұрын
Excellent explanation! My problem started when i messed up my grub configuration files while working on the lfs project But thanks to you it wasnt a problem anymore! Thank you🙏
@ShadowZero2724 күн бұрын
great tutorial. the commands didn't work for my arch distribution however I was able to mix your approach with another persons and get it going. Using the UBUNTU live usb was what drove me here.
@5ov4-9428 күн бұрын
Thank you man! It's really helpful. When I wrote "sudo fdisk -l" I seen that my main linux path "/" was mounted as "EFI" 😂
@wadejbeckett3 ай бұрын
You have no idea how much I owe you for this video.
@tonystorckeАй бұрын
This video saved me when the others couldn't.
@alreaud7 ай бұрын
Excellent, thank you for your help. It's funny, my problem would have been resolved with "sudo update-grub", LOL! 🤷♂
@SilentKnightDeadlyKnightАй бұрын
This video is exactly what I needed. Thank you very much for this video.
@voidlicker515318 күн бұрын
MAY GOD BLESS YOU!!! IT FINALLY WORKED THANK YOU SO MUCH OH MY GODDDD THANK YOU SO MUCH FOR MAKING THIS VDIEO SHSJSJDHHDHDHD I CANT WAIT TO USE LINUX MINT!!!! For the beginners, my one was (hd1,gpt2) so my sda is sda2 That is what worked for me.
@blueboy462510 ай бұрын
Great way of showing how to fix the mess of complexity that is grub. 😂
@rezahp1436Ай бұрын
Oh thanks finally got fixed so helpful 🙏🏼
@maxmeyer748 ай бұрын
Thank you fixed my problem 😊
@Dviih10 ай бұрын
I’m not a grub hater but since I moved to systemd-boot I never had problems with bootloader and pretty much anything else since it used to be only grub to break sometimes
@dtcyhk8 ай бұрын
You are excellent !!
@SusanAmberBruce3 ай бұрын
It's ok but I found it didn't work for MX Linux on an M.2 drive, however I did manage to recover boot using a live MX from usb.
@kiddo20028 ай бұрын
Buddy i am stuck with Parrot OS installation on Live USB Please make a separate video on it
@DrewHowdenTech8 ай бұрын
This method should work on Parrot OS as well.
@kiddo20028 ай бұрын
@@DrewHowdenTech Not working Buddy
@DrewHowdenTech8 ай бұрын
Where are you having trouble?
@kiddo20028 ай бұрын
@@DrewHowdenTech Grub can't read files in USB But when i open usb in windows... every needed file is present there
@DrewHowdenTech8 ай бұрын
Are you having trouble with the Live USB itself? This video is meant to cover INSTALLED versions of Linux. If you are having trouble getting a live media to boot, I would suggest remaking it.
@westonmook72805 ай бұрын
It worked! TY sm my parrot home was acting up.
@old486whizz10 ай бұрын
So at 4:42, it would be far better just to do a couple of bind mounts, chroot into /mnt, then run the grub config/grub install command to get things to work on your reboot.. no need to muck about with anything else after
@DrewHowdenTech10 ай бұрын
You could also do that. I just wanted to show how to boot from the GRUB console (in case a user had only minor damage to their GRUB that didn't necessitate a full reinstall). As well, by the time I found that out, I had already tested this method and ensured that it works with all the major Linux distributions.
@marwanshamso15185 ай бұрын
Bro i really love you ❤❤ this worked for me ❤❤
@TreadOnThis25 күн бұрын
Getting "sudo: grub-install: command not found"
@DrewHowdenTech25 күн бұрын
Try the alternate method (linked in the pinned comment).
3 ай бұрын
thank you very much. All your videos are excellent (but your sound recording is not good). Have you produced a video on refind? I by now have waived Grub, which is whimsical and unreliable. Systemd-boot may be a good alternative, but it's too complicate to implement. Whereas refind is easy and quite efficient. I fail to understand why most distros cleave to Grub, while Refind seems no to be the default boot manager in any distro, AFAIK
@DrewHowdenTech3 ай бұрын
I've never covered rEFInd on this channel, but that would be a great idea for a future video. I think most distributions use GRUB because it's been the standard for basically forever, and it works on both UEFI and legacy systems--very important for Linux, since one of it's key features is the ability to run on old hardware.
3 ай бұрын
@@DrewHowdenTech for mbr drives lilo is much safer and efficient than grub. I've been a Slackware user, with lilo, for 26 years. In just 4 months with lubuntu, grub has failed me quite often, many more times than ever lilo did in 26 years. Following your quite useful instructions has not always sorted things out, which has necessitated reformatting the inner storage and reinstalling the OS again and again. All those mishaps have stopped upon going in for rEFInd
@woeangel2 ай бұрын
It works, really appreciate. I spent so much time on this issue. BTW you beat AI bro, the chatdpt-4o was able to solve the first half but never figure out the other half, you absolutely nailed it.
@JhonHo-e1k5 ай бұрын
Thank you, bro. That help me a lot!😊
@anksuczka2 ай бұрын
I reinstalled the grub but I still get booted to grub instead of going straight to Linux, when I try to update grub it says that efi catalog is missing
@DrewHowdenTech2 ай бұрын
After reinstalling GRUB, you need to run a few commands at the GRUB prompt, as described in this video.
@anksuczka2 ай бұрын
@@DrewHowdenTech i did everything you said and it works! It boots to Linux straight away!! Thanks!! 💜💚
@dejoneltahan19742 ай бұрын
i accidentaly deleted my efi partition and tried to fix it with chatgpt reinstalling grub but when i rebooted it just showed my the boot menu with no option to boot into linux
@DrewHowdenTech2 ай бұрын
Follow the instructions at 4:41.
@antiherosandwich8 ай бұрын
My problem is that my "boot/" is in my @/ subvolume, so it fails when i do your "linux /boot/vmlinuz" - is there are way to go about that?
@DrewHowdenTech8 ай бұрын
What is the output of “sudo fdisk -l”.
@antiherosandwich8 ай бұрын
@@DrewHowdenTech I'm using the second method since my screen only showed "Grub" - no the live environment.
@DrewHowdenTech8 ай бұрын
Okay, what’s the output of “ls”?
@antiherosandwich8 ай бұрын
@@DrewHowdenTech ls lists my partitions. My root partition is (hd1,gpt2). But when i do "ls (hd1,gpt2)/" ....it shows the folders of "@/ and @home/" - these 2 folders are my Fedora subvolumes... and the "boot/" folder is inside the "@/" for me, (unlike yours that is directly outside disk and can be accessed with "linux /boot/vmlinuz" - for me, i can't do that command because my boot is inside that @/ subvolume.
@DrewHowdenTech8 ай бұрын
Then you would set root to “(hd1,gpt2)/@/”.
@NolanKhalaf5 күн бұрын
I believe you’re the only one who will help me with the installation Debian 12 on a software raid 1 using my intel NUC6i7kyk. Grub error that can’t be installed & even if I install it manually still the system is not bootable.
@DrewHowdenTech4 күн бұрын
Do you see “grub” or “grub rescue” at the GRUB prompt?
@mime433110 ай бұрын
Ah, I wish I watched that about a month ago when my Fedora crashed.
@soundsandambientvideos3807 ай бұрын
How can you tell if you have a boot partition?
@DrewHowdenTech7 ай бұрын
Check the output of "sudo fdisk -l". See if you have a much smaller "Linux Filesystem" (that's about 512 MB to 2 GB in size). If you don't recall creating it for some other purpose, it's likely a boot partition. You can check this by mounting the partition, and looking at it's contents--either through the command line, or graphically, if your live media has a GUI.
@CARIMPORTGEORGIA7 күн бұрын
i accidently deleted my debian boot partition using fdisk from live linux usb how can i recover it? i'm not talking about (EFI fat32 partition) i want to recover boot partition because i cannot mount my debian PLEASE HELP ME THANKS
@DrewHowdenTech7 күн бұрын
If you deleted your entire /boot directory, you have more missing than just the GRUB bootloader. Unfortunately this video doesn’t cover such cases. Check out this Debian wiki article for instructions on how to install and use the boot-repair utility: wiki.debian.org/Boot-Repair
@lapiswolf2780Ай бұрын
I keep getting "error= failure reading sector 0x6bfb00 from 'hd1'." My main disc is usually labelled sda.
@DrewHowdenTechАй бұрын
This indicates your hard drive is failing. Hopefully you have a backup.
@luigiprovencher5 ай бұрын
Okay. So what are the commands if you have a separate boot partition like you would if you have installed LMDE6?
@DrewHowdenTech5 ай бұрын
When reinstalling GRUB, only difference is that, in addition to mounting your root and EFI System partitions, you also have to mount your boot partition at /mnt/boot (after mounting your root partition, but before mounting your EFI System Partition). When it comes to booting your system after reinstalling GRUB, here are the key differences: 1. "set root=[partition]" is your boot partition, not your root *"root=/dev/sdXY" in the "linux" command is still your root partition! 2. Your vmlinuz and initrd.img files are at the root of your boot partition (so you would use /vmlinuz or /initrd.img instead of /boot/vmlinuz or /boot/initrd.img)
@wonderful94926 ай бұрын
hi, that is an excellent video. one superficial comment, is watching the vid full screen, the shell commands put near the low edge of the video are obscured a bit by the KZbin video controls! I think it would be better to keep shell commands higher up in the video! I will watch the alternative method later, as I want to reconstruct a dual boot for win10 + win11 + Linux_mint, starting from a reformatted EFI partition. where I have watched another vid about doing the win10 + win11 loading, where I will do that first, then try to do the Linux mint loader. now one bit which puzzled me in this video here, is where he talks of a boot partition versus a root partition, where I am not 100% sure which I will have! the partition I wish to construct a triple boot loader for win10, win11, Mint, is called "EFI system partition" on GParted on Mint, and is about 100MB, where it is created when I install win10 or win11 to a brand new drive. but I then will reformat that to the same FAT32, and use bcdboot to make it a loader for each win OS partition. I tried this making it a loader for 4 windows installs, win10 + win11 on the same disk, and win10 + win11 from another disk. the plan then is to try and put a LInux boot loader to this also, which possibly loads as a different bootloader there is a little bit of confusion, so any clarification would be appreciated.
@DrewHowdenTech6 ай бұрын
Use the "sudo fdisk -l" command to figure out if you have a /boot partition. If you have a second "Linux Filesystem" that's about 512 MB to 4 GB in size, that's probably a /boot partition. If you're still unsure, mount your root partition, then do "ls /mnt/boot". If it doesn't output anything--meaning that your /boot directory is empty--you have a separate /boot partition.
@wonderful94926 ай бұрын
@@DrewHowdenTech thanks for the reply, I have made a note and will have to experiment a bit, I am going to install the cinammon edge Linux Mint, and I want to be able to reconfigure different ways. earlier when I installed Linux Mint 21.1 after installing win10 and win11 to a disk, the UEFI boot menu showed a windows loader, and a loader called Ubuntu, where if I booted with the windows loader, I just got the windows installs, although if I went through the links something like "change default OS", I eventually got to the ubuntu option from the windows options, on the linux side, if I booted from the Ubuntu bootloader, I got Linux Mate, and an option for windows where clicking that continues the boot to the windows loader with the windows installs. I was wondering where that ubuntu bootloader is situated? is it on a partition, or is it on the disk outside the partitions in some metalevel area of the sectors? I know that if I do a sector by sector copy, that everything works like the original disk, so everything is there at the sector level. now I got painted into a corner, and have been reinstalling everything from scratch, and from a video on Windows, I can reconstruct the windows loader from scratch, by loading the windows 10 installer, selecting repair, then troubleshoot and getting to the command prompt. from that if I run diskpart, then "list vol", the partition which appears on Linux GParted as "EFI system partition" at the left of the drive, which is about 100MB and FAT32, say it is volume 8, and say letter X isnt in use, and say the other windows OSes are on T: U: V: W: where I study on GParted earlier to be really sure what is where, including the commands so far and then further commands that is: diskpart list vol sel vol 8 assign letter=X exit C: format X: /fs:fat32 bcdboot T:\windows /s X: /f UEFI bcdboot U:\windows /s X: /f UEFI bcdboot V:\windows /s X: /f UEFI bcdboot W:\windows /s X: /f UEFI where I have reformatted the bootloader partition and then constructed it from scratch to load 4 windows OSes here, which can be on different disks, in my case 2 on the same disk as X: and 2 on another disk, if I reboot now with the loader for the disk with X, I get to a windows bootloader with W, V, U, T with the last one as the default OS. each windows install might use totally different drive letters, those are only meaningful for the session, not afterwards or before. if I now install Linux, this will probably extend the arrangement, where I might get an Ubuntu bootloader, and can either boot to that and then on to the above windows, or I can go via the windows loader of the disk of X, but the problem is if I want to rejig the windows bootloader later, the reformatting might get rid of the Ubuntu loader, so I need to be able to reconstruct a bootloader for Linux, last time I installed Linux Mint 21.1, but this time I will install cinammon edge, I dont know if this makes sense to you? right now I have 4 installs of windows, with win10 + win11 on one disk, and win10 + win11 on the other disk, the latter disk is scratch installs to experiment with, and I am going to install Cinammon edge to the latter disk, but as an experiment I want to redo the bootloader of the latter disk from scratch by the MO mentioned earlier for the windows side with 4 windows OSes like in the example above, and I then need a bootloader for cinammon edge, which is why I was watching your video, and I meanwhile watched your other video. Linux installs to whatever partition I select, but I think there must be other stuff going on for the bootloader, not sure where! also I dont know if I can give the linux volume for bcdboot above, or is that too optimistic? I think with your 2 videos, /mnt will be the partition I install Linux to, and the "EFI system volume" probably /mnt/boot/efi I noticed that in your vid here it says "os-prober will be executed to detect other OSes...." but in your alternative video, it says os-prober will not be executed to ....! so maybe the MO here is better, as it will deal with say windows OSes.
@DrewHowdenTech6 ай бұрын
I think you could include Linux in bcdboot. I would personally prefer to use GRUB. You may need to add the “GRUB_DISABLE_OS_PROBER=false” line to your /etc/default/grub file. If you selected the “install alongside” option when installing Linux, this should be done automatically.
@wonderful94926 ай бұрын
@@DrewHowdenTech ok, cool! will try that! apologies for the delay in replying, but I was doing major backups before the experiments, and then did the Linux Mint 21.3 cinammon edge install, the try without installing DVD takes a long time to load, redid it as BDR, and also took at least 15 mins! but on installing, it loads super fast. now I have taken photos of the partition structure before and after installing Cinammon edge from both GParted and the installer, as I dont know where to paste screengrabs to with Gparted and not sure if I can do screenshots during installation, so I go old school with a camera! where I started with a blank disk, and then installed win10 to the leftmost partition, where the installer puts 2 partitions automatically to the left of it, then installed win11, according to GParted I get partitions thus: EFI system partition fat32 100 MB boot,esp Microsoft reserved partition unknown filesystem 16MB msftres (=Microsoft reserved) Basic data partition ntfs 309.85GB 118.29GB used, msftdata (=Microsoft data)(64 bit win10 install) unlabelled ntfs 546MB 457.85MB used, hidden diag, according to the windows desktop this is a recovery partition Basic data partition ntfs 310.5GB, 62.25GB used, msftdata (64 bit win11 install) I now via the earlier diskpart, bcdboot, format instructions, reformat the EFI system partition, and reconstruct it as a new bootloader for these win10 + win11 installs, and also a further 2 from the other disk. I now go to install cinammon edge, which I think took about 54 minutes to do, with this I have to select a partition to install to, and also select "Device for boot loader installation" and this shows all disks and partitions as options, eg it will say have /dev/sda as well as /dev/sda1 /dev/sda2 etc. so I decided to play it safe and create a new partition for the boot loader which was 100MB, and 102400MB for the Linux install, both ext4 filesystem, and consecutive to the above list of partitions, I also have to give a mount point, guessing now I put a fictional /myboot for the boot loader which was /dev/nvme1n1p6 and a fictional /mylinux for the install partition which is /dev/nvme1n1p7 but the installer gives an error message "no root file system is defined", reading this from my photos! so I redid the install partition mount point as / and left the bootloader one as /myboot and then continued the installation, and no problem, and the PC's UEFI bootlist now has a boot loader called "ubuntu (M2_3 : Samsung SSD 990" (no closing bracket!) and if I select that, Linux Mint boots super fast in less than a minute from the grub menu. now I dont know if you can make sense of that, and whether my naming the bootloader partition as /myboot means I have to mount other than the /mnt or /mnt/boot/efi given in your vids? I have done a sector backup of the entire disk via dd and gzip, namely: sudo dd if=/dev/nvme1n1 | gzip -c >> /media/mint/somedrive/backup.gz so I can experiment without risk, the plan is to do the earlier diskpart and bcdboot etc things again, and to try the linux as a further option with bcdboot, but I dont know which partition I should give bcdboot? /myboot or / above? where you say you prefer to use GRUB, I would like to go bothways! I prefer the Linux shell, as it has all kinds of sneaky tricks eg treating disks and partitions as if they were files eg the dd command above, ie a grub loader and also a windows loader, just so I can deal with any circumstance, and also out of curiousity. on the GRUB side, if I reformat the EFI system partition again, and then put win10 + win11 + win10 + win11 + Linux, will the ubuntu loader be unaffected because I designated a partition /myboot for the boot loader? also if instead I had put a disk for the bootloader rather than a partition, eg say /dev/nvme1n1 for the bootloader, would reformatting the EFI system partition disrupt the ubuntu loader? as mentioned I am trying to understand things both ways, both from the Linux side, and from the Windows side, and from the Linux side the bootloader at the disk and also instead the bootloader at a partition. I am kind of winging it, guessing a lot and relying on error messages, and ultimately relying on a sector backup if things go to pot! some weeks ago experimenting, I put 2 Linux Mint 21.1 installs with bootloader at the disks, and noticed that the grub loader had both installs there to select from. now later on as an experiment I deleted one of those 2 installs, and noticed that the grub boot no longer worked, where I think I got a grub> menu, not sure if I photographed it. if I follow the MO in your video where there is more than one Linux install, will the GRUB menu show both the way it does if I install directly? if not, is there an MO to get both? would maybe the os-prober fish out all the Linux installs and put them on the reconstructed GRUB menu. apologies for asking so many questions!
@DrewHowdenTech6 ай бұрын
Linux always stores it's boot files in /boot. /myboot means nothing to Linux! So if you use /myboot as a mount point during installation, it will just leave that partition untouched, and place your boot files in /boot, on your root partition. Linux also stores boot files on your EFI System Partition (in addition to the /boot directory). It has to in order for it to be bootable on a UEFI system. So yes, reformatting your EFI System Partition will disrupt Ubuntu. If you install multiple Linux distributions the way I did in that video, yes, GRUB should should give you options for both distros as well as Windows.
@indonesiandef8 күн бұрын
update-grub did not help, it still boots to grub command line im at the part grub was installed correctly but not 100% solved
@DrewHowdenTech8 күн бұрын
What’s the output of “update-grub”? Are you running it after having booted into your Linux install via the GRUB command line?
@abinashdewri26826 ай бұрын
I have dual boot of windows and kali linux, and I'm not even able to open linux to do what u suggested. Whenever i select linux, grub enters rescue mode. But im able to open the windows partition. What should i do?
@DrewHowdenTech6 ай бұрын
You will need to use a Linux live media from here.
@j.schmidt6312 ай бұрын
I get the GRUB> when trying to install Nobara fresh install using a USB. How they heck to I get past this. Using a MSI 450m MB - 2400G CPU - 16GB DDR4 RAM.
@DrewHowdenTech2 ай бұрын
You’re having problems with the install USB, correct? If that’s the case, that would mean that the installation media is corrupt; Either because something went wrong while the USB was being flashed, or the ISO file itself is corrupt.
@cybernit37 ай бұрын
I installed Ubuntu 24.04 and I rebooted then only gets to GRUB Rescue screen. I tried to list the root directory grub> ls (hd1,gpt2) error: unknown filesystem I run Windows 11 on hd0 and Ubuntu on hd1. So, I tried booting into Windows 11..then switch to run Ubuntu... then stopped working; I think Microsoft Windows deliberately corrupts GRUB for Linux. From the GRUB Rescue I tried: set prefix = (hd1,gpt2)/boot/grub set root = (hd1,gpt2) insmod normal normal Ok, it doesn't boot up Ubuntu and just return to GRUB rescue prompt... grub> I just wanted to try out this new Ubuntu, and I am frustrated. Thanks if anyone can help...
@DrewHowdenTech7 ай бұрын
As stated in this video, if the prompt says “grub rescue” and not just “grub”, that means that your GRUB is broken beyond repair. In that case, you will need to reinstall GRUB entirely, using a live ISO (as shown in this video), THEN boot with the GRUB prompt. If you find this method confusing, read the pinned comment.
@cybernit37 ай бұрын
@@DrewHowdenTech Well this morning I saw your videos and tried this recent 2nd method by Tryout ubuntu then mount and then chroot. But I couldn't even mount my SSD gives me NTFS is invalid error. So I thought just try reinstall Ubuntu 24.04 LTS and it seems it works. The 1st time I installed Ubuntu I then booted into Windows 11 and used disk part which showed me very old partition list; I assume this is maybe why it corrupted the new ubuntu ssd. I also tried Windows Disk Management (newer one) and it showed the new Ubuntu paritions. That is maybe one reason Windows corrupted the SSD. Or when I select boot from the bias but didn't swap the Ubuntu and Windows SSDs boot priority. I tried doing some tests; just boot into Windows and Ubuntu, and doesn't seem to corrupt. I am also concerned if I do a Windows Update it might ruin the Ubuntu SSD. Thanks for teaching about chroot fix method, might come in handy in the future.
@mabyes8 ай бұрын
Hi, 😊 I followed from 4:41 , updated grub and after rebooting, the grub bash appeared. I didn't followed from 8:58 because you say: "if you are prompted to emergency mode" which is something I am not. I just went into the same window from 4:41 again. I tried reinstalling again but all that happens is that another partition is created with the same error. Do you have some advice or documentation that could kindly share, please? 🙏
@DrewHowdenTech8 ай бұрын
What’s the output of “sudo update-grub”?
@hoboshomevideo67442 ай бұрын
I have an error after grub> linux /boot/vmlinuz error: ../../grub-core/fs/fshelp.c:257:file ‘/boot/vmlinuz’ not found. and the same with the vmlinux I’m trying to bring back to life Fedora 36 after failed attempt to upgrade it to 37 version Could you please give any advice?
@DrewHowdenTech2 ай бұрын
What is the output of "ls /boot"?
@hoboshomevideo67442 ай бұрын
@@DrewHowdenTech it is ../ ../ efi/ vmlinuz-6.2.14-100.fc36.x86_64 extlinux/ grub2/ System.map-6.2.14-100…ect.; loader/vmlinuz-0-rescue-(bunch of letters and symbols)
@DrewHowdenTech2 ай бұрын
Your vmlinuz file is /boot/vmlinuz-6.2.14-100.fc36.x86_64.
@heathercummins97784 ай бұрын
I can’t find Grub at all only able to f12 menu, and system is crashed when try to boot to Ubuntu on that screen
@DrewHowdenTech4 ай бұрын
You will need to use a Linux install media to reinstall GRUB (using the instructions in this video).
@michaelk18602 ай бұрын
My efi partition is on a different drive than my linux filesystem partition. When i try to mount it i get mount: /mnt/boot/efi: mount point does not exist. Is there any way to fix this?
@DrewHowdenTech2 ай бұрын
You probably have a separate /boot partition. You need to mount that before you can mount your EFI System Partition.
@Hmmindividualguy3 ай бұрын
Asking for you input here.. When I find my (hd1,gpt1), and boot, it drops to BusyBox shell. My machine broke when I tried to time shift to an old version, I think I was using a different kernel. The ls (hd1,gpt1) looks good when I ls, all my files are in there, but I noticed a /timeshift at the end, that isn’t in your files. Any idea why that is? Any input on this would be great.. Thanks
@Hmmindividualguy3 ай бұрын
Correction, it’s (hd1,gpt2) In the time shift folder, is snapshots/ snapshots-boot/ snapshots-hourly/ weekly, etc
@DrewHowdenTech3 ай бұрын
Sounds like there is more missing than just your bootloader. Unfortunately, this tutorial won’t fix it.
@ShreyPatel355 ай бұрын
After writing /boot/vmlinuz goot two files then i tried vmlinuz-6.1.0-21-amd64 root=/dev/sda2 then give putput as bad shrim signature what to do now ..any suggestions
@DrewHowdenTech5 ай бұрын
Go to your BIOS settings and disable secure boot.
@jonathanedwardgoode7 ай бұрын
When I do ls (hd0, gpt5)/ (the partition that I installed the distro on) it just gives me, /efi , loader/ , *series_of_numbers_and_letters. Is there any advice you would recommend. I have a multiboot system with three linux distros, and I thought I could just switch a new one in for one of them, and then grub-update, but whenever I try to boot into it it just says "error: no such device, unknown file system, you need to load the kernel first"
@DrewHowdenTech7 ай бұрын
Looks like that's your boot partition. Do you have your vmlinuz and initrd.img files in here? If so, "set root=(hd0,gpt5)", then, when specifying your vmlinuz and initrd.img files, use /vmlinuz and /initrd.img, respectively. NOTE: Your "root" under "linux /vmlinuz root=/dev/sdXY" needs to be set to the root partition of the distro that you want to boot; NOT your boot partition.
@AllanNguyen-e4v4 ай бұрын
In my boot file, there is no "vmlinuz", so i'm not entirely sure where to go from there. I've read on some forums of people saying to install "boot repair"? Any inputs or thoughts on what I should do?
@DrewHowdenTech4 ай бұрын
What is the output of “ls /boot”?
@thisisjustplainstupi4 ай бұрын
@@DrewHowdenTechI have this exact problem. Been looking for a solution for months. My only output for “ls /boot” is “grub/”
@DrewHowdenTech3 ай бұрын
Do what the people on the forums are suggesting. You have more missing than just your GRUB bootloader.
@thisisjustplainstupi3 ай бұрын
@@DrewHowdenTech what are the people on forums suggesting? What forums are you referring to? I’ve tried boot repair and it doesn’t offer any suggestions or help. How do I search for this? After 2 months this is the closest video I’ve found similar to my problem. The gnu grub boot loader opens but can’t find Ubuntu to boot it even though it’s there. I’d rather not lose my files but it seeming that a a hard reinstall is the only option but I’m worried this will happen again after an update.
@DrewHowdenTech3 ай бұрын
I have another video in the info card at the beginning of this video that shows you how to install and use boot repair. By the way, for clarity, I was referring to the forums that you mentioned in your comment where people were suggesting to install boot repair.
@garrylaw267Ай бұрын
i have a sudo mout error it says its write protected when i try mount boot
@DrewHowdenTechАй бұрын
Are you sure you got the right partition? Check the “sudo fdisk -l” command again to ensure that you aren’t trying to mount a partition on your install USB.
@denimsahu77182 ай бұрын
I've a bit different problem - i didnt deleted grub or something but i just restarted my system and for some reason instead of getting grub machine directly booted into windows so then I checked my bios thinking maybe somehow windows boot manager is set to first in bios boot manager but there kali wasn't there and it just had windows boot manager so then I used f9 key to get into some menu which shows all the os I've on my system as well as network boot option and boot from efi I winet into efi and in there after selecting few more option I found grub.efi Or something like that and when clicked on it I got the grub but now how do I make grub appear every time I start my system like before instead of having to do this whole thing?
@DrewHowdenTech2 ай бұрын
Try running “sudo update-grub” from within your Linux.
@denimsahu77182 ай бұрын
@@DrewHowdenTech sorry I forgot to remove my comment from here, but yeah I'd run that and it alone didn't worked, but from gpt got this command sudo grub-install --target=x86_64-efi --efi-directory=/boot/efi --bootloader-id=grub --recheck Ran this and then ran sudo update-grub And it worked
@michaelcanino40782 ай бұрын
Really great video! I get this error message from Grub when I power up my computer...Error: invalid environment block. 452: out of range pointer: 0xcfff020 Aborted. Press any key to exit. When I press a key on the keyboard it will go and boot Ubuntu Jammy Jellyfish. It use to just load right in will some of what you presented fix this? Thanks for any info you can provide.
@DrewHowdenTech2 ай бұрын
Run "sudo update-grub" from within your Ubuntu, and paste the output here.
@michaelcanino40782 ай бұрын
canino@canino-GE60-2PL:~$ sudo update-grub [sudo] password for canino: Sourcing file `/etc/default/grub' Sourcing file `/etc/default/grub.d/init-select.cfg' Generating grub configuration file ... Found linux image: /boot/vmlinuz-6.8.0-45-generic Found initrd image: /boot/initrd.img-6.8.0-45-generic Found linux image: /boot/vmlinuz-6.8.0-40-generic Found initrd image: /boot/initrd.img-6.8.0-40-generic Found linux image: /boot/vmlinuz-6.5.0-35-generic Found initrd image: /boot/initrd.img-6.5.0-35-generic Found memtest86+ image: /boot/memtest86+.elf Found memtest86+ image: /boot/memtest86+.bin Warning: os-prober will not be executed to detect other bootable partitions. Systems on them will not be added to the GRUB boot configuration. Check GRUB_DISABLE_OS_PROBER documentation entry. done Here is the output. Hope it helps! Thanks!
@nadooalaa16758 ай бұрын
How can I know the root partition I tried something similar to yours but didn't work
@DrewHowdenTech8 ай бұрын
What is the output of "ls"?
@wiltzie758 ай бұрын
I can only boot to grub and I can successfully run set root=(partition) and when I get ls /. I see my drive. When I try to run linux /boot/vmlinuz I don't have anything in the /boot folder. Is there a way to fix this?
@DrewHowdenTech8 ай бұрын
If you boot folder is empty, that means that you probably have a separate /boot partition. Set your root to that partition. NOTE: "root=/dev/sdXY" (when specifying your vmlinuz file and root partition) still needs to be your actual root partition.
@SB-gs2yl3 ай бұрын
@@DrewHowdenTech bro this makes no sense after I set root I put in linux /boot/vmlinuz It says " error: file ' /boot/vmlinuz ' not found" You're the tech guy please respond with exactly how I'm supposed to write the line of code to boot (hd0,gpt2) Please don't explain it just write the correct line of code thank you.
@DrewHowdenTech3 ай бұрын
@@SB-gs2ylIf you have a separate boot partition, your vmlinuz and initrd images will be at the root of your boot partition. In that case, set your root to your boot partition with ‘set root=[boot partition]’. The following commands are: linux /vmlinuz root=[root partition] initrd /initrd.img
@yumerthmijail8378Ай бұрын
Thanks a lot.
@senritsujumpsuit60218 күн бұрын
I have spent a long time procrastinating an should stop since theirs some files I want to fix the paths for and without my main install playing most games is impossible lol
@abdorouiss52798 ай бұрын
I am running a dual bootable windows and ubuntu. Sometimes when I boot my system it gives me Grub so i had to reboot again again untill it runs. Is this method gonna work ? Thank you
@DrewHowdenTech8 ай бұрын
Do you get the GRUB menu with your Ubuntu and Windows options?
@abdorouiss52798 ай бұрын
Ubuntu
@DrewHowdenTech8 ай бұрын
Does your GRUB menu show a "Windows Boot Manager" entry?
@Elnasir3 ай бұрын
I will try it later. I lost GRUB for my truenas scale server
@geetchavan97495 ай бұрын
Hey it is showing that there is vmlinuz file not found what to do currently i am using ubuntu
@DrewHowdenTech5 ай бұрын
Are you sure you set the right partition as your "root?" What is the output of "ls /"?
@geetchavan97495 ай бұрын
@@DrewHowdenTech actually when I have installed ubuntu my laptop was glitching and some files haven't downloaded properly i think i need to reinstall it
@DrewHowdenTech5 ай бұрын
That’s probably it.
@sulaksana16265 ай бұрын
hi currently i am facing this problem but i use pop os can i use the same way and is pop os use vmlinuz too ?
@DrewHowdenTech5 ай бұрын
Pop!_OS doesn’t use GRUB, but instead something called systemd-boot, so I don’t think this method will work, but you can try it anyway.
@sulaksana16265 ай бұрын
@@DrewHowdenTech ohh, i use dual boot win and pop os, yesterday i switched to win via bios but then when i am back to pop os the gnu grub rescue appears, i want to try with initrd like your vid but the problem i don't know my linux kernel version and how to check linux kernel in the gnu grub rescue, i have try use tab auto complete but it's doesn't work
@DrewHowdenTech5 ай бұрын
If it says “grub rescue” and not just “grub”, you will need to reinstall GRUB using a Linux installation media.
@soap54203 ай бұрын
THANKS!!
@sumayaali6897 ай бұрын
When I do (hd0,gpt3)/ it says unknown filesystem
@DrewHowdenTech7 ай бұрын
What’s the output of “ls”?
@mateusrodriguez87042 ай бұрын
thx my friend
@Ruiz.Senior4 ай бұрын
I haven't de efi folder, should I create it?
@DrewHowdenTech4 ай бұрын
If you don’t have an EFI System partition, no.
@fakeflame86Ай бұрын
failed to update usb drivers on my laptop.
@DrewHowdenTech29 күн бұрын
What happened?
@Un_Pour_Tous2 ай бұрын
This did not work just loops me right back to "grub>"
@DrewHowdenTech2 ай бұрын
You have to run the commands shown at the GRUB prompt.
@nadooalaa16758 ай бұрын
When I try to enter linux /boot/vmlinuz it says that it is not found what should I do
@nadooalaa16758 ай бұрын
I am dual booting my device if that helps
@DrewHowdenTech8 ай бұрын
What is the output of "ls /"?
@nadooalaa16756 ай бұрын
The same as the video , i think i messed up in the sda3 part
@DrewHowdenTech6 ай бұрын
Does it show a "boot" directory?
@danlarch35607 ай бұрын
I followed all the steps and I still get put into a grub menu(no recovery mode). UUID is reset and still did nothing. Do you know what I have done wrong? OS is ubuntu.
@DrewHowdenTech7 ай бұрын
You have to follow the instructions to boot with the GRUB command line.
@danlarch35607 ай бұрын
@@DrewHowdenTech It was too far gone, I just wiped it completely, but thanks for the very helpful video!!
@Ashu-y2k5cАй бұрын
Linux /boot/vmlinuz is not showing any thing
@DrewHowdenTechАй бұрын
Press the tab key twice after typing “linux /boot/” to see the contents of the boot directory. Your vmlinuz file may have a different name, depending on your distribution.
@Acelestialerror28 күн бұрын
None of my partitions have root ? Not that I see
@DrewHowdenTech28 күн бұрын
Check for a partition labelled "Linux Filesystem." If there are multiple, it's probably the largest one.
@Acelestialerror27 күн бұрын
@DrewHowdenTech thank you for answering my question and sorry for the late answer only took now the time to fix my grub yesterday I tried a bunch of different stuff using a live image of Ubuntu I thought it didn't do anything but now I'm looking at grub gpt2 is showing root weirdly enough but still thanks for answering and thx for the great video
@comosaycomosah16 күн бұрын
This was super helpful finally back in amd feel like I can figure it out but I'm in a weird spot afraid to run grub-update now lol...used clonezilla to copy distro to new partition on new drive then copied the efi partition to new drive, realize that's messy now. Currently booted into "new" os but using original drives boot partition lol sos cant even explain it good. But not sure how to proceed I changed the uuid for the new os partition bc it was the same from cloning and boot partition still has same identical uuid for both boot partitions but the same command wouldnt work since it's not ext4 lol so yea if anyone has advice thatd be great I know I can get back here at least now edit:and update grub took me back to minimal grub bash
@DrewHowdenTech16 күн бұрын
Try the alternate method linked in the pinned comment.
@sianocelot6 ай бұрын
tysm
@texmex60836 ай бұрын
I did this and I got unknown filesystem
@texmex60836 ай бұрын
And it's a endeavorOS installation and dual booting on separate drives
@DrewHowdenTech6 ай бұрын
I would be curious to see how the drive and its partitions show up in GParted, but you may have a corrupted filesystem. It’s also possible that you simply selected the wrong partition. Run sudo fdisk -l again.
@MrBobWareham7 ай бұрын
If I could get into Linux Mint then I would not need to repair grub but that is the problem grub is damaged so I cant get in to repair!!
@DrewHowdenTech7 ай бұрын
You need to use a Linux install media to reinstall GRUB.
@neelchaudhary3223 ай бұрын
1:14 lol Something unexpected happened
@aastharawat04097 ай бұрын
I am stuck at black screen grub menu from 2 days straight after watching this tutorial. i hit the same command in ubuntu terminal ( sudo rm -rf /boot/grub , then (reboot) ) and in [ grub> linux /boot/vmlinuz ] , it is displaying [ error : file' /boot/vmlinuz' not found. ] .........I even tried [ grub> linux /boot/vmlinuz-linux]
@DrewHowdenTech7 ай бұрын
That part of the video was me BREAKING my GRUB, to illustrate what scenario this video was meant to cover. I specifically said "you don't want to do this" as I was running it (in my virtual machine, for what I hope are obvious reasons). At this point, as shown in this video, nothing you do on that screen will do much of anything--since you just deleted your bootloader--so you're gonna have to follow the instructions in this video to completely reinstall GRUB, starting at 1:53.
@Muhaiminul_coding_club5 ай бұрын
holllllllllllllll
@REZAZIMohamedabdessamed7 ай бұрын
My root partition is /dev/nvme0 In the last step, when I type "boot", the system tries to boot and it gives error: "Alert! /dev/nvme0 does not exist. Dropping to a shell!". In the given shell when I do ls /dev/, I can find my nvme0. What to do?
@DrewHowdenTech7 ай бұрын
Are you sure you have the right ROOT (not boot) partition? You can check this with a Linux install media using a partition manager (such as GParted) or the "sudo fdisk -l" command. REMEMBER: You are specifying a PARTITION, not a device.