Error loading vmlinuz linux not found

This is my first time trying to install Arch.
  • Index
  • » Newbie Corner
  • » [SOLVED] Error loading vmlinuz-linux: not found

#1 2016-09-14 15:11:13

ThomasN
Member
Registered: 2016-02-03
Posts: 31

[SOLVED] Error loading vmlinuz-linux: not found

This is my first time trying to install Arch.

I tried following the instructions in the installation guide. I’m using systemd-boot on this Asus r209ha laptop.

However, when I try to boot into my installation, I get this:

Error loading vmlinuz-linux: not found

My first thought was that it was odd that there’s a instead of a / there, so I chrooted into my new system again and checked /boot/loader/entries/arch.conf. It is:

title       Arch Linux
linux      /vmlinuz-linux
initrd     /intel-ucode.img
initrd     /initramfs-linux.img
options  root=PARTUUID=410b225d-ea4b-4d72-9d8e-2c9db5a273dd rw

What am I doing wrong?

Last edited by ThomasN (2016-09-14 17:22:45)

#2 2016-09-14 15:20:32

ewaller
Administrator
From: Pasadena, CA
Registered: 2009-07-13
Posts: 19,013

Re: [SOLVED] Error loading vmlinuz-linux: not found

From the install media, mount your boot partition on /mnt and verify that vmlinuz-linux exists in the mount point.  ( ls -l /mnt )

When you chrooted into the system, are you sure that the boot partition was mounted on /boot  ?

Nothing is too wonderful to be true, if it be consistent with the laws of nature — Michael Faraday
Sometimes it is the people no one can imagine anything of who do the things no one can imagine. — Alan Turing
—
How to Ask Questions the Smart Way

#3 2016-09-14 15:33:53

ThomasN
Member
Registered: 2016-02-03
Posts: 31

Re: [SOLVED] Error loading vmlinuz-linux: not found

When mounting my boot partition on /mnt from the install media, ‘ls -l /mnt’ shows only the directories ‘EFI’ and ‘loader’ and the file ‘intel-ucode.img’.

When I chrooted, I mounted the boot partition on /boot using ‘mount /dev/mmcblk0p1 /boot’.

mmcblk0p1 is the EFI-partition I created earlier in the installation process.

#4 2016-09-14 15:37:45

poisonby
Member
Registered: 2016-08-20
Posts: 8

Re: [SOLVED] Error loading vmlinuz-linux: not found

ThomasN wrote:

When mounting my boot partition on /mnt from the install media, ‘ls -l /mnt’ shows only the directories ‘EFI’ and ‘loader’ and the file ‘intel-ucode.img’.

When I chrooted, I mounted the boot partition on /boot using ‘mount /dev/mmcblk0p1 /boot’.

mmcblk0p1 is the EFI-partition I created earlier in the installation process.

If you mounted your root partition to /mnt, then you should’ve mounted the boot partition to /mnt/boot, not /boot. What you should do is boot the live USB, mount your root partition to /mnt and your boot partition to /mnt/boot, chroot in and then:

And then make sure that vmlinuz-linux is present.

Transhumanist, amateur programmer and Linux enthusiast.

#5 2016-09-14 15:40:33

ewaller
Administrator
From: Pasadena, CA
Registered: 2009-07-13
Posts: 19,013

Re: [SOLVED] Error loading vmlinuz-linux: not found

Well, that is the problem.  The next question is, why is vmlinuz-linux missing?   if you unmount the boot partition, then mount the root partition on /mnt, look in /mnt/boot.  It should be empty.
I’m guessing you will find the missing kernel there.  If so, you can mount the boot partition somewhere (not /mnt/boot) and move the files.

Alternately, reestablish the chroot environment with the root partition on /mnt and the boot partition on /mnt/boot, and install the linux package.

Nothing is too wonderful to be true, if it be consistent with the laws of nature — Michael Faraday
Sometimes it is the people no one can imagine anything of who do the things no one can imagine. — Alan Turing
—
How to Ask Questions the Smart Way

#6 2016-09-14 15:41:40

ewaller
Administrator
From: Pasadena, CA
Registered: 2009-07-13
Posts: 19,013

Re: [SOLVED] Error loading vmlinuz-linux: not found

poisonby wrote:

If you mounted your root partition to /mnt, then you should’ve mounted the boot partition to /mnt/boot, not /boot.

Be aware that they are doing what I asked them to do for diagnostic purposes.

Nothing is too wonderful to be true, if it be consistent with the laws of nature — Michael Faraday
Sometimes it is the people no one can imagine anything of who do the things no one can imagine. — Alan Turing
—
How to Ask Questions the Smart Way

#7 2016-09-14 16:06:12

ThomasN
Member
Registered: 2016-02-03
Posts: 31

Re: [SOLVED] Error loading vmlinuz-linux: not found

Thanks a lot. The necessary files were indeed on the root partition, instead of the boot partition. Moving the files solved it. I have a working install!

#8 2016-09-14 16:30:33

jasonwryan
Anarchist
From: .nz
Registered: 2009-05-09
Posts: 30,379
Website

Re: [SOLVED] Error loading vmlinuz-linux: not found

Please remember to mark your thread as [Solved] by editing your first post and prepending it to the title.

Arch + dwm   •   Mercurial repos  •   Surfraw

Registered Linux User #482438

#9 2019-07-02 08:10:03

oxwivi
Member
Registered: 2019-07-01
Posts: 25

Re: [SOLVED] Error loading vmlinuz-linux: not found

By the way, is having two entries in the boot menu after installing systemd-boot normal? I’ve two entries on my HP laptop after installing bootctl, Linux Boot Manager and EFI HDD Device. I also can’t recall if the latter is HP firmware scanning for EFI devices either, but allow me to throw it out here.

Источник

Forum rules
Before you post please read how to get help. Topics in this forum are automatically closed 6 months after creation.

mmccarty

Level 1
Level 1
Posts: 12
Joined: Tue Apr 26, 2022 4:39 pm

[SOLVED]error:no such device | error:file vmlinuz not found

Hi all:

I thought I’d try Linux Mint on my new old PC that my Dad gave me after he went out and bought himself a new Mac. It has a new internal SSD drive divided into 2 partitions C: and D: with Windows 10 installed onto C:(/dev/sda — the Kingston). I installed Debian Bullseye onto the previously unused partition of D: and formatted it to ext4 and can dual boot into Windows or Debian Bullseye. This setup was working fine. I had his old hard drive (/dev/sdb type: USB vendor: Western Digital) laying around for which I bought a usb enclosure and it was this device that I wished to install Linux Mint onto hopefully being allowed to triple boot into the OS of my choice. Install seemed to go off fine but upon boot gave me several errors.

error1: no such device 9c7eb7c3-4a11-4042-b568-e6161b1ff05c
error2: file ‘/boot/vmlinuz-5.4.0-91-generic’ not found
error3: you need to load the kernel first

press any key

I can still boot into Windows or Debian Bullseye but not Linux Mint. Any help would be appreciated. It appeared to modify grub2 fine and added the new menu entries for Linux Mint. I can see all the devices in the grub command line but when I go to list the contents of the «/boot» on directory on /dev/sdb, it appears empty which explains error2. Error3 is easy enough once I resolve the other 2 errors. Why would grub2 not be able to «ls» the contents of the /boot directory and what is my no such device error1? I can’t figure out my device GUID. I have 2 swap devices on /dev/sda sda2 & sda3. Thanks for any help.

Regards,
Matthew

=============================================

Code: Select all

System:
  Kernel: 5.10.0-10-amd64 x86_64 bits: 64 compiler: gcc v: 10.2.1
  Desktop: GNOME 3.38.6 tk: GTK 3.24.24 wm: gnome-shell dm: GDM3
  Distro: Debian GNU/Linux 11 (bullseye)
Machine:
  Type: Desktop System: Gateway product: SX2840 v: SX2840 serial: <filter>
  Chassis: type: 3 v: SX2840 serial: <filter>
  Mobo: Gateway model: FIH57 serial: <filter> BIOS: American Megatrends
  v: P01-B3 date: 07/12/2010
CPU:
  Info: Dual Core model: Intel Core i3 530 bits: 64 type: MT MCP
  arch: Nehalem rev: 2 L2 cache: 4 MiB
  flags: lm nx pae sse sse2 sse3 sse4_1 sse4_2 ssse3 vmx bogomips: 23407
  Speed: 1502 MHz min/max: 1200/4133 MHz Core speeds (MHz): 1: 1502 2: 1537
  3: 1605 4: 1569
Graphics:
  Device-1: Intel Core Processor Integrated Graphics
  vendor: Acer Incorporated ALI driver: i915 v: kernel bus ID: 00:02.0
  chip ID: 8086:0042
  Display: wayland server: X.Org 1.20.11 compositor: gnome-shell driver:
  loaded: i915 note: n/a (using device driver) resolution: 1920x1080~60Hz
  s-dpi: 96
  OpenGL: renderer: Mesa DRI Intel HD Graphics (ILK) v: 2.1 Mesa 20.3.5
  direct render: Yes
Audio:
  Device-1: Intel 5 Series/3400 Series High Definition Audio
  vendor: Acer Incorporated ALI driver: snd_hda_intel v: kernel
  bus ID: 00:1b.0 chip ID: 8086:3b56
  Sound Server: ALSA v: k5.10.0-10-amd64
Network:
  Device-1: Intel 82578DC Gigabit Network vendor: Acer Incorporated ALI
  driver: e1000e v: kernel port: d880 bus ID: 00:19.0 chip ID: 8086:10f0
  IF: enp0s25 state: up speed: 1000 Mbps duplex: full mac: <filter>
Drives:
  Local Storage: total: 1.35 TiB used: 19.88 GiB (1.4%)
  ID-1: /dev/sda vendor: Kingston model: SV300S37A480G size: 447.13 GiB
  speed: 3.0 Gb/s serial: <filter> temp: 38 C
  ID-2: /dev/sdb type: USB vendor: Western Digital model: WD10 EADS-65P6B0
  size: 931.51 GiB serial: <filter>
Partition:
  ID-1: / size: 143.38 GiB used: 11.28 GiB (7.9%) fs: ext4 dev: /dev/sda4
Swap:
  ID-1: swap-1 type: partition size: 515 MiB used: 0 KiB (0.0%) priority: -2
  dev: /dev/sda2
  ID-2: swap-2 type: partition size: 516 MiB used: 0 KiB (0.0%) priority: -3
  dev: /dev/sda3
Sensors:
  System Temperatures: cpu: 29.0 C mobo: N/A
  Fan Speeds (RPM): N/A
Info:
  Processes: 229 Uptime: 1h 43m Memory: 5.61 GiB used: 1.76 GiB (31.5%)
  Init: systemd v: 247 runlevel: 5 Compilers: gcc: 10.2.1 alt: 10 Packages:
  apt: 2299 Shell: Bash v: 5.1.4 running in: gnome-terminal inxi: 3.3.01

===============================

Code: Select all

lsblk
NAME   MAJ:MIN RM   SIZE RO TYPE MOUNTPOINT
sda      8:0    0 447.1G  0 disk 
├─sda1   8:1    0 299.4G  0 part 
├─sda2   8:2    0   515M  0 part [SWAP]
├─sda3   8:3    0   516M  0 part [SWAP]
└─sda4   8:4    0 146.7G  0 part /
sdb      8:16   0 931.5G  0 disk 
├─sdb1   8:17   0   512M  0 part /media/mmccarty/70E8-B3EF
├─sdb2   8:18   0     1K  0 part 
└─sdb5   8:21   0   931G  0 part /media/mmccarty/90f6d996-04d5-46e2-8670-e588be0
sr0     11:0    1  1024M  0 rom

======================================

Code: Select all

sudo blkid
/dev/sda2: UUID="655b6cd0-29be-4854-9bb0-7b044414d745" TYPE="swap" PARTUUID="55295e62-02"
/dev/sda3: UUID="e30cd2cf-2b15-4f80-9ea8-45d849c46d20" TYPE="swap" PARTUUID="55295e62-03"
/dev/sda4: UUID="9c9fb8d6-283f-40f9-b978-843fda8c62bb" BLOCK_SIZE="4096" TYPE="ext4" PARTUUID="55295e62-04"
/dev/sdb1: UUID="70E8-B3EF" BLOCK_SIZE="512" TYPE="vfat" PARTUUID="af5028ba-01"
/dev/sdb5: UUID="90f6d996-04d5-46e2-8670-e588be06e45a" BLOCK_SIZE="4096" TYPE="ext4" PARTUUID="af5028ba-05"
/dev/sda1: PARTUUID="55295e62-01"

Last edited by LockBot on Wed Dec 28, 2022 7:16 am, edited 3 times in total.

Reason: Topic automatically closed 6 months after creation. New replies are no longer allowed.

mmccarty

Level 1
Level 1
Posts: 12
Joined: Tue Apr 26, 2022 4:39 pm

Re: error:no such device | error:file vmlinuz not found

Post

by mmccarty » Tue Apr 26, 2022 7:25 pm

Code: Select all

mmccarty@debianmbm5:/dev/disk/by-uuid$ ls -l
total 0
lrwxrwxrwx 1 root root 10 Apr 26 18:55 655b6cd0-29be-4854-9bb0-7b044414d745 -> ../../sda2
lrwxrwxrwx 1 root root 10 Apr 26 18:55 70E8-B3EF -> ../../sdb1
lrwxrwxrwx 1 root root 10 Apr 26 18:55 90f6d996-04d5-46e2-8670-e588be06e45a -> ../../sdb5
lrwxrwxrwx 1 root root 10 Apr 26 18:55 9c9fb8d6-283f-40f9-b978-843fda8c62bb -> ../../sda4
lrwxrwxrwx 1 root root 10 Apr 26 18:55 e30cd2cf-2b15-4f80-9ea8-45d849c46d20 -> ../../sda3
mmccarty@debianmbm5:/dev/disk/by-uuid$

mmccarty

Level 1
Level 1
Posts: 12
Joined: Tue Apr 26, 2022 4:39 pm

Re: error:no such device | error:file vmlinuz not found

Post

by mmccarty » Tue Apr 26, 2022 7:36 pm

Code: Select all

mmccarty@debianmbm5:/media/mmccarty/90f6d996-04d5-46e2-8670-e588be06e45a/boot$ ls -l
total 102384
-rw-r--r-- 1 root root   237884 Nov  5 12:02 config-5.4.0-91-generic
drwxr-xr-x 2 root root     4096 Apr 26 15:25 efi
drwxr-xr-x 4 root root     4096 Apr 26 15:45 grub
lrwxrwxrwx 1 root root       27 Apr 26 15:38 initrd.img -> initrd.img-5.4.0-91-generic
-rw-r--r-- 1 root root 88046949 Apr 26 15:40 initrd.img-5.4.0-91-generic
lrwxrwxrwx 1 root root       27 Apr 26 15:27 initrd.img.old -> initrd.img-5.4.0-91-generic
-rw------- 1 root root  4755132 Nov  5 12:02 System.map-5.4.0-91-generic
lrwxrwxrwx 1 root root       24 Apr 26 15:38 vmlinuz -> vmlinuz-5.4.0-91-generic
-rw-r--r-- 1 root root 11784448 Jan  4 10:00 vmlinuz-5.4.0-91-generic
mmccarty@debianmbm5:/media/mmccarty/90f6d996-04d5-46e2-8670-e588be06e45a/boot$ ^

senjoz

Level 5
Level 5
Posts: 726
Joined: Tue Jun 09, 2020 3:55 am
Location: Kamnik

Re: error:no such device | error:file vmlinuz not found

Post

by senjoz » Wed Apr 27, 2022 3:17 am

Welcome to the Linux Mint forums, mmccarty!

It looks like Grub is looking for a partition with UUID 9c7eb7c3-4a11-4042-b568-e6161b1ff05c but there is no partition with this UUID. Did you try running sudo update-grub when booted in Debian and with USB disk connected?

Regards, Jože

mmccarty

Level 1
Level 1
Posts: 12
Joined: Tue Apr 26, 2022 4:39 pm

Re: error:no such device | error:file vmlinuz not found

Post

by mmccarty » Wed Apr 27, 2022 5:48 am

Jože:

Yea. I think that that is the fix. Only to do it in a chroot environment with proc, dev, and sys mounted. Only thing is that I can’t figure out how it gets the bad UUID. I can’t believe that this is an uncommon use case. Running update-grub in my Bullseye Debian machine just updates grub on that machine which isn’t broken. It’s my Linux Mint boot machine that had the new install and now won’t boot. I’ll give chroot some more thought. https://www.suse.com/support/kb/doc/?id=000016034 is sort of helpful but not quite.

Regards,
Matthew

senjoz

Level 5
Level 5
Posts: 726
Joined: Tue Jun 09, 2020 3:55 am
Location: Kamnik

Re: error:no such device | error:file vmlinuz not found

Post

by senjoz » Wed Apr 27, 2022 6:11 am

I believe that chroot-ing is needed only when updating Grub on another installation. If you run sudo update-grub in Debian (without chroot-ing), Linux Mint on the USB disk should be detected and, after rebooting, you should have the boot option for Linux Mint in Debian’s Grub. What is the output of sudo os-prober with USB disk connected and without any chroot-ing?

Regards, Jože

EDIT:
If you wish to install/reinstall Grub to UDB disk, read this.

mmccarty

Level 1
Level 1
Posts: 12
Joined: Tue Apr 26, 2022 4:39 pm

Re: error:no such device | error:file vmlinuz not found

Post

by mmccarty » Wed Apr 27, 2022 7:17 am

Jože:

Code: Select all

/dev/sda1"Linux Mint 20.3 Una (20.3):LinuxMint:linux
/dev/sdb1:Windows 10:Windows:chain
/dev/sdb4:Debian GNU/Linux 11 (bullseye):Debian:linux

or maybe

Code: Select all

/dev/sda1:Windows 10:Windows:chain
/dev/sdb1:"Linux Mint 20.3 Una (20.3):LinuxMint:linux

Now, I’m really confused. Debian won’t boot but gives TIME error waiting for device /dev/disk/by-uuid/ce56958a-fb76-4377-a7df-7ae57a3374f9. I think I need to unplug usb, run update-grub to get my Debian back. Then plug in usb and update-grub again in Linux Mint rescue mode. Now I’m getting normal.mod not found. I’ve tinkered with it so much, I don’t know anymore. And grub not using set root=(hd1,4) instead of (hd1,msdos5) and not being able to list the contents of a boot directory for example. My dev ids are possibly changing doesn’t help the matter any.

I’ll try a few things without mucking around with the installer and let you know.

Regards,
Matthew

User avatar

Jo-con-Ël

Level 8
Level 8
Posts: 2298
Joined: Sun Jun 20, 2021 12:41 pm
Location: donde habita el olvido

Re: error:no such device | error:file vmlinuz not found

Post

by Jo-con-Ël » Thu Apr 28, 2022 5:41 am

@senjoz

OP did/does not put attention on your proposals and complicated things following other guides. :(

Now, OP needs to repair Wndows/Debian disk (BIOS) boot in first place and then see what went wrong with Mint installation on that USB disk (sdb). It looks like it was installed on UEFI mode (sdb1>would be EFI partition, there is an efi folder on Mint’s root /boot/,…) on a MBR disk (sdb2 will be extended partiion and sdb5, Mint’s root, a logical one inside). Reinstalling Mint from scratch on BIOS mode (ensuring Mint live USB boots on that mode) is not a bad option after all.

The recommended way to proceed, IMO, is booting LM Live USB and run Boot repair BootInfo summary option to post back url with report when offered. That summary report will provide all information needed to confirm what is the problem now and what was wrong on Mint installation.

Do not run Boot Repair Recommended repair option. It is not probable BR will solve the problem in that case.

Arrieritos semos y en el camino nos encontraremos.

mmccarty

Level 1
Level 1
Posts: 12
Joined: Tue Apr 26, 2022 4:39 pm

Re: error:no such device | error:file vmlinuz not found

Post

by mmccarty » Fri Apr 29, 2022 2:50 am

Hi all:

Thanks for all help and suggestions. I just gave up. Your right Boot repair didn’t help… I just decided to stick with Debian and did a reinstall of Debian which got my Debian back. I made my external usb the /home partition and mount. My new setup is running fine. However, I’m sure that I could reproduce the problem if you’d like for me too as I still have the same hardware setup just running Debian and Windows 10 only. However, os-prober doesn’t see my currently running OS of Debian but instead gives me just my Windows 10 installation. I don’t know why os-prober doesn’t see currently running OS as update-grub correctly gives me Debian and Windows 10 in my grub startup menu.

Code: Select all

mmccarty@debianmbm5:~$ sudo os-prober
[sudo] password for mmccarty: 
/dev/sda1:Windows 10:Windows:chain
mmccarty@debianmbm5:~$ uname -a
Linux debianmbm5 5.10.0-13-amd64 #1 SMP Debian 5.10.106-1 (2022-03-17) x86_64 GNU/Linux
mmccarty@debianmbm5:~$

Let me know if you want me to return to the installer and try again. I’m willing to lose my «/home» partition / directory on my Debian setup if you think that you could help me get Linux Mint up and running. I think I’m running EFI as my history shows:

Code: Select all

mmccarty@debianmbm5:~$ history | grep efi
   61  apt-get install grub-efi-amd64-bin
   62  sudo apt-get install grub-efi-amd64-bin
   66  sudo apt-get install --reinstall grub-efi
   68  file /boot/efi/EFI/debian/grubx64.efi
   75  ls efi*
   77  efibootmgr --verbose | grep debian
   78  efibootmgr --verbose 
   79  efibootmgr 
   82  sudo grub-install --target=x86_64-efi --efi-directory=$esp --bootloader-id=grub --recheck --debug
   85  sudo grub-install --target=x86_64-efi --efi-directory=$esp --bootloader-id=grub --recheck --debug
   91  efibootmgr
   92  apt install grub-efi-amd64-signed os-prober shim-signed
   93  sudo apt install grub-efi-amd64-signed os-prober shim-signed
  227  history | grep efi
mmccarty@debianmbm5:~$

if that helps you guys any. I don’t know what the difference between efi and bios is and just remember installing an EFI boot manager thingy that gives me a boot up option for Debian and Linux Mint before I even get to the grub menu. I just always select Debian at that point knowing I will get to the grub menu that then gives my the option of booting into Debian or Linux Mint. I somehow got rid of the «no such device» error and was stuck with Linux Mint telling me «/boot/grub/i386-pc/normal.mod» not found. I could list my devices in grub but whenever I went to list the contents of the boot directory on the Linux Mint device, it couldn’t «see» the files there hence the normal.mod not found error. That’s when I decided to forgo Linux Mint and just boot Debian or Windows 10. Let me know if you want me to try the BIOS mode install / repair or try to reproduce the original errors in apparently EFI mode. Sorry for creating so much confusion and making it harder than it should be. If you want me to proceed at this point, let me know. I like Linux Mint or did before. I still have a running version of Linux Mint on my debianmbm4 that never gave me any problems.

Code: Select all

mmccarty@debianmbm5:~$ more ./os-prober-debianmbm4.txt
mmccarty@debianmbm4:~$ sudo os-prober
[sudo] password for mmccarty: 
/dev/sda1@/efi/Microsoft/Boot/bootmgfw.efi:Windows Boot Manager:Windows:efi
/dev/sda5:Debian GNU/Linux 11 (bullseye):Debian:linux
/dev/sdb1:Debian GNU/Linux 11 (bullseye):Debian1:linux
/dev/sdb3:Ubuntu 20.04.3 LTS (20.04):Ubuntu:linux
/dev/sdd2:Linux Mint 20.1 Ulyssa (20.1):LinuxMint:linux
mmccarty@debianmbm4:~$ 
mmccarty@debianmbm5:~$

Thanks,
Matthew

mmccarty

Level 1
Level 1
Posts: 12
Joined: Tue Apr 26, 2022 4:39 pm

User avatar

Jo-con-Ël

Level 8
Level 8
Posts: 2298
Joined: Sun Jun 20, 2021 12:41 pm
Location: donde habita el olvido

Re: error:no such device | error:file vmlinuz not found

Post

by Jo-con-Ël » Fri Apr 29, 2022 3:04 pm

First:

mmccarty wrote: ↑

Fri Apr 29, 2022 2:50 am


However, os-prober doesn’t see my currently running OS of Debian but instead gives me just my Windows 10 installation. I don’t know why os-prober doesn’t see currently running OS as update-grub correctly gives me Debian and Windows 10 in my grub startup menu.

That is the way it works.

You can see on grub-cfg contents (cat /boot/grub/grub.cfg) Debian and Advanced option entries on GRUB menu are created by 10_linux when running sudo update-grub. 30_os-prober only creates entries for other systems when detected.

GRUB (os-prober) is able to detect other systems and then you can boot them from their GRUB menu entries, if those systems are installed in the same way/mode. Now, on that computer 30_os-prober executable creates a Windows entry and you can boot that entry w/o problems because it is installed also in BIOS legacy mode.

With the other computer (debianmbm4) you would never have problems ’cause all system are installed in UEFI mode.

For the rest

1)As per your first post you were trying dual/triple boot Windows/Debian and Mint on the other disk, so Mint needed to be installed in the same mode.

You have installed Windows and Debian in BIOS mode:

Mobo: Gateway model: FIH57 serial: <filter> BIOS: American Megatrends
v: P01-B3 date: 07/12/2010

I don’t know what happened for sure, maybe you just changed boot mode on BIOS setup, Linux Mint Live was booted on UEFI mode,…or a Mint installer bug (*) when installing on external disks, but it looks like Mint was installed in UEFI mode on a MBR disk.

When you tried to boot Mint USB disk, taken into account that Getaway computer’s firmware is too old (BIOS version dated on 2010) everything is possible. You didn’t mention an Ubuntu (Linux Mint UEFI) boot option in any case. Maybe it is not able to boot on UEFI mode from a MBR disk (if CSM was enabled or boot modewas set on UEFI +Legacy), or computer setup was on BIOS legacy only,… or Installer failed when installing (efi) loader.

After grub-update, even it was shown on Debian GRUB menu you were not able to boot that entry ’cause it was installed in UEFI mode.

You would be able to convert Mint installed on UEFI mode to BIOS legacy, and senjoz recommended you the right tutorial to install grub (bios) on Mint and loader on Mint disk’s MBR (i.e. Chroot or Purge-and-Reinstall in chroot methods but BIOS not UEFI). You also would be able to do it on from Debian but needed to be sure you mount Mint’s root partition (all the time you thought Mint was installed on first partition on but it was installed on fith partition on that disk) running sudo fdisk -l and then sudo mount /dev/sdx5 /mnt replacing /dev/sdx5 with the correct one….

Considering those codes on bash history you tried to convert Debian BIOS legacy install to UEFI. Finally you broke Windows/Debian disk boot.

2))Now if you want triple boot need to install Mint on BIOS legacy mode:

a)You need to be sure Linux Mint live USB is booted in BIOS legacy mode.

You can do that if you can select boot mode BIOS legacy (only) on BIOS setup but it will depend on that old firmware as I said.

You can try creating a Linux Live USB with Rufus or other tool, but Mint iso is Hybrid so can be booted both in UEFI or BIOS depending on computer setting.

You will be sure on booting linux Mint live as there are differences (screen with countdown only appears booting on BIOS mode and pressing a key to get GRUB menu it shows different options).

Even you can probe you have booted on BIOS mode once on Live session running inxi -SMxx from terminal if you find BIOS (see quoted) or UEFI[Legacy] on last line.

b)Then you can install Mint on that disk. Just make room for Mint (no need to remove Debian /home just resize) with Gparted, install with Something else.. option to create Mint root partition on that free space (of course do not create an EFI partition on it) and be sure you select that disk (not Windows/Debian one) to place loader.

b)Once installed you will be able to boot that USB disk from computer boot menu (tapping F12, Esc, F10 or F11 depending on computer as soon as power on PC). Mint GRUB menu will show Windows and Debian option, If it is not just run sudo update-grub on Mint session.

c)Also, booting with internal Windows/Debian disk GRUB menu wont show Mint option the first time after installing. You will need to run sudo update-grub on session Debian in order to detected Mint installed on the other disk.

The only problems you will have using that USB connected on that Getaway Computer will be because computer stop detecting USB disk or GRUB bug when booting external devices. You’d better use computer boot menu and choose USB disk whenever you want to boot it.

In other hand you have another computer with all systems installed on UEFI mode. If you are going to boot (single boot) that Mint USB HD on that computer, results will depend on computer settings. Mint USB hard disk wont be shown as a valid UEFi devices (it is not) but you can adjust UEFI settings in order to boot both UEFI and BIOS devices (boot mode UEFI+Legacy, UEFI+ CSM or enable Legacy boot or CSM depending on computer). Also Mint GRUB menu (on USB disk) wont detect systems installed in UEFI mode and it is good enough.

——————————
(*) One way to avoid that bug is installing w/o loader, launching installer from terminal with sh -c 'ubiquity -b gtk_ui'&. After installation is completed and before rebooting you need to install grub following link proposed by senjoz to install GRUB with chroot method but BIOS mode in any case.

Last edited by Jo-con-Ël on Sun May 01, 2022 9:46 am, edited 6 times in total.

Arrieritos semos y en el camino nos encontraremos.

User avatar

Jo-con-Ël

Level 8
Level 8
Posts: 2298
Joined: Sun Jun 20, 2021 12:41 pm
Location: donde habita el olvido

Re: [SOLVED]error:no such device | error:file vmlinuz not found

Post

by Jo-con-Ël » Sat Apr 30, 2022 4:55 am

mmccarty wrote: ↑

Sat Apr 30, 2022 1:35 am


I’m happily triple booting though I don’t know how I resolved the first error of «no such device». Thanks for all your help.

That error «no such device,.. you need to load kernel first» usually means boot mode (BIOS/UEFI/Secure boot) does not match installed system and/or device is not present/detected or can’t be accessed.

System on that disk (at least one time) was installed in UEFI mode and you were trying to boot on BIOS Legacy mode.

In your case, UUID partition mentioned on error was unknown and it was true there was not such UUID on sda or sdb disks. So GRUB on that disk’s MBR, if booting on BIOS mode, was pointing to a previous Mint’s root partition.

Also those changes on disk, from sda to sdb and viceversa you can see on fstabs, grub menu, parted… is/was a mess that happens when connecting/disconnecting internal disks (I thought you said it was a external).

Then you removed that first vfat partition (will never know its flags or content), removed the extended partition and created a new partition (Debian /home)…but you did not format that disk (you did not create a new partition table) so GRUB installed on its MBR was still pointing to wrong direction (i.e. first partition on that disk).

Grub2 (v2.00) is installed in the MBR of /dev/sda and looks at sector 1 of
the same hard drive for core.img. core.img is at this location and looks
for (,msdos1)/boot/grub.

Maybe you even did not try to boot that disk after repartitioning but (obviously there was no /boot/grub on Debian /home ) would end-up on a grub shell directly or after another error:no such UUID device.

You would be able to solve the problem before repartioning, as it is said on last post, installing grub (BIOS) on old Mint installation with chroot method.

In resume, now you would solved that problem If you have installed Mint on proper BIOS mode and (hope) installed GRUB loader on Mint disk (so re-wrote that MBR).Congrats. :D

Edited to remove «LM 20.3 does not install kernel 5.4.0-91 kernel…». It does. :oops:

Arrieritos semos y en el camino nos encontraremos.

Источник

Я и так понял, что там написано.

Ты не понял ничего. Ни того, что там, ни после.

оригинальное название образа «ubuntu-mate-18.04.5-desktop-i386», сокращено до «Ubuntu-Mate-18045-i386».

Лишний шанс ошибиться самому и запутать других.

заглядывал, для того, чтобы вытащить два файла vmlinuz и initrd.lz, положить их в папку Ubuntu18

Лишнее. loopback для того и монтирует, чтобы не вытаскивать из исо-образа, а найти в нем.

Получается, что на флешке надо создать папку casper и закинуть их туда

Лишнее. Выше написал почему. Хотя возможно и так, но тогда не нужен loopback.

как быть, когда будет несколько образов Linux (например: другие версии Ubuntu, Mint, Zorin) и каждый содержит папку casper?

Для того и loopback. Но возможно и «вытащить» *бунту из образа и поместить каждую в свой каталог.

initrd не содержит расширения .lz. Дописывал его вручную.

Опять, абсолютно не нужное действие, только вносящее дополнительную путаницу.
Чтобы не изобретать велосипед, можешь посмотреть здесь, как я делаю загрузочную флешку. Или здесь  взять код поновее.
 Что можно сделать с твоим кодом…

menuentry «Ubuntu-Mate-18045-i386» — заменить на «submenu», это даст возможность, в случае ошибки вернуться в меню груба.
set root=(hd0,1) — сработает только если флешка действительно окажется первым диском, заменить на «search».
linux (loop)/Ubuntu18/vmlinuz — это внутри образа, соответственно, путь должен быть «/casper…»
iso-scan/filename=/ISO/Ubuntu-Mate-18045-i386.iso — значение тоже, что в «isopath», можно заменить на него.
initrd (loop)/Ubuntu18/initrd.lz — аналогично ядру «/casper…», никаких «/Ubuntu18…» и если в образе у инитрд нет «.lz» то и здесь его лепить незачем.
С учетом этих исправлений:

submenu "Ubuntu-Mate-18045-i386" {
set isopath="/ISO/Ubuntu-Mate-18045-i386.iso"
set gfxpayload=keep
search -n -s -f "${isopath}"
loopback loop $isopath
linux (loop)/casper/vmlinuz iso-scan/filename=${isopath} boot=casper locale=ru_RU.UTF-8 splash --
initrd (loop)/casper/initrd.lz
}Не проверял, надеюсь что не наделал ошибок.

Исо-образ *бунту сделан по технологии «loopback-bootable». В нем есть еще одна задумка, позволяющая ничего не знать об ядре-инитрд.
Технология подразумевает, что в образе есть файл /boot/grub/loopback.cfg. Это конфиг груба именно для загрузки из исо-образа.
Достаточно после команды «loopback» добавить :

configfile /boot/grub/loopback.cfgВ моем коде сначала проверяется этот вариант. Если «loopback.cfg» не будет найден, то будет искать ядро-инитрд.

примерно такие же параметры написаны

Главное слово — примерно. Они годятся только для какого-то одного случая. Примеры я тебе уже привел.

Источник

Понравилась статья? Поделить с друзьями:
  • Error opening file for writing radeon software
  • Error loading vehicle
  • Error opening file for writing clownfish
  • Error opening file for writing amd radeon
  • Error loading use or uselsx module javacon