Error no such device kernel

Arch Linux

You are not logged in.

#1 2016-03-21 17:18:18

Grub: error: no such device:

G’day mates! I’ve got a bit of trouble installing Arch, first to my laptop and then to a VM. The same trouble seems to haunt both attempts. Immediately after installation is finished, I reboot, and I select the first option in Grub, I’m greeted with a warning:

error: no such device: string-of-characters
Loading Linux core repo kernel.
error: no such partition.
Loading initial ramdisk.
error: you need to load the kernel first.
Press any key to continue.

after which it returns to the grub menu.

After a bit of online searching, it appeared that my fstab is not configured properly. So I booted up a live Arch install, mounted the / partition (sda1), and checked fstab. Sure enough, fstab is completely empty. This is a bit weird because I’m positive I ran

So I reformatted swap, made sure that sda1 was mounted in /mnt, and reran genfstab. It appeared to execute correctly, but «cat /mnt/etc/fstab» once again revealed an empty fstab.

At this point I think it would be best to ask for help. I’ve checked the permissions of /mnt/etc/fstab; it is indeed -rw-r—r— and owned by root. I’ve checked the arch iso (v. 2016.02.01) and the checksums are good too.

My entire installation script is at http://pastebin.com/XAavu1nz

Thanks for any help!
Fred

Last edited by Fred Barclay (2016-03-21 20:56:49)

Источник

Linux Mint Forums

Welcome to the Linux Mint forums!

[SOLVED] Grub error no such device and no such partition

[SOLVED] Grub error no such device and no such partition

Post by patrick.landry2 » Sat Jul 30, 2011 6:40 pm

I need help to figure out why I cannot boot into Windows XP

When I attempt to boot from the Grub menu I get:

ERROR: No Such Device
ERROR: No Such Partition

Press any key to continue

When I press any key it send me back to the Grub Menu

The system will boot into MintLinux 9 from the Grub menu without issue.
I have searched and searched the forums trying several fixes to no avail.

What I have tried:
From LiveCD — grub-install, update-grub — No Joy
From Mint 9 — grub-install, update-grub — No Joy
From Mint 9 — apt-get purge grub-common, apt-get install grub-pc, grub-install, update-grub — No Joy

My system:
AMD Phenom II 1100T
Asus Crosshair V Formula
nVidia GT 520
Seagate 320GB SATA HDD (sda)
Seagate 2TB SATA HDD (sdb)
LG BD Rewriter

Relevant Boot data:
Boot Info Script 0.60 from 17 May 2011

=> Grub2 (v1.97-1.98) 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 in partition 1 for /boot/grub.
=> No boot loader is installed in the MBR of /dev/sdb.

File system: ntfs
Boot sector type: Windows XP
Boot sector info: No errors found in the Boot Parameter Block.
Operating System: Windows XP
Boot files: /boot.ini /ntldr /NTDETECT.COM

File system: vfat
Boot sector type: Unknown
Boot sector info: No errors found in the Boot Parameter Block.
Operating System:
Boot files: /boot.ini /ntldr /NTDETECT.COM

File system: ext4
Boot sector type: —
Boot sector info:
Operating System: Linux Mint 9 Isadora
Boot files: /boot/grub/grub.cfg /etc/fstab /boot/grub/core.img

File system: swap
Boot sector type: —
Boot sector info:

File system: ext4
Boot sector type: —
Boot sector info:
Operating System:
Boot files:

Drive: sda _____________________________________________________________________

Disk /dev/sda: 320.1 GB, 320072933376 bytes
240 heads, 63 sectors/track, 41345 cylinders, total 625142448 sectors
Units = sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 512 bytes

Partition Boot Start Sector End Sector # of Sectors Id System

/dev/sda1 * 63 606,644,639 606,644,577 7 NTFS / exFAT / HPFS
/dev/sda2 606,644,640 625,136,399 18,491,760 c W95 FAT32 (LBA)

Drive: sdb _____________________________________________________________________

Disk /dev/sdb: 2000.4 GB, 2000398934016 bytes
255 heads, 63 sectors/track, 243201 cylinders, total 3907029168 sectors
Units = sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 512 bytes

Partition Boot Start Sector End Sector # of Sectors Id System

/dev/sdb1 1 3,907,029,167 3,907,029,167 ee GPT

GUID Partition Table detected.

Partition Start Sector End Sector # of Sectors System
/dev/sdb1 2,048 39,065,599 39,063,552 Data partition (Windows/Linux)
/dev/sdb2 39,065,600 54,691,839 15,626,240 Swap partition (Linux)
/dev/sdb3 54,691,840 3,907,026,943 3,852,335,104 Data partition (Windows/Linux)

«blkid» output: ________________________________________________________________

Device UUID TYPE LABEL

/dev/sda1 FE88DF3088DEE5E5 ntfs HP_PAVILION
/dev/sda2 4C85-50CF vfat HP_RECOVERY
/dev/sdb1 e1a23d21-f756-4de8-8862-6ec1a3ae851e ext4
/dev/sdb2 7332b096-709b-4c1c-ae33-e5ebc1409dd2 swap
/dev/sdb3 12b960d0-1954-4fb1-8af8-f381a92e3a58 ext4

Device Mount_Point Type Options

/dev/sdb1 / ext4 (rw,errors=remount-ro)
/dev/sdb3 /home ext4 (rw)

multi(0)disk(0)rdisk(0)partition(1)WINDOWS=»Windows XP Media Center Edition» /noexecute=optin /fastdetect /usepmtimer

C:CMDCONSBOOTSECT.DAT=»Microsoft Windows Recovery Console» /cmdcons

multi(0)disk(0)rdisk(0)partition(1)WINDOWS=»Microsoft Windows XP Professional» /fastdetect

C:CMDCONSBOOTSECT.DAT=»Microsoft Windows Recovery Console» /cmdcons

———————————————————————————
#
# DO NOT EDIT THIS FILE
#
# It is automatically generated by /usr/sbin/grub-mkconfig using templates
# from /etc/grub.d and settings from /etc/default/grub
#

### BEGIN /etc/grub.d/00_header ###
if [ -s $prefix/grubenv ]; then
load_env
fi
set default=»0″
if [ $ ]; then
set saved_entry=$save_env saved_entry
set prev_saved_entry=
save_env prev_saved_entry
set boot_once=true
fi

function savedefault <
if [ -z $ ]; then
saved_entry=$
save_env saved_entry
fi
>

function recordfail <
set recordfail=1
if [ -n $ ]; then if [ -z $ ]; then save_env recordfail; fi; fi
>
insmod ext2
set root='(hd1,1)’
search —no-floppy —fs-uuid —set e1a23d21-f756-4de8-8862-6ec1a3ae851e
if loadfont /usr/share/grub/unicode.pf2 ; then
set gfxmode=640×480
insmod gfxterm
insmod vbe
if terminal_output gfxterm ; then true ; else
# For backward compatibility with versions of terminal.mod that don’t
# understand terminal_output
terminal gfxterm
fi
fi
insmod ext2
set root='(hd1,1)’
search —no-floppy —fs-uuid —set e1a23d21-f756-4de8-8862-6ec1a3ae851e
set locale_dir=($root)/boot/grub/locale
set lang=en
insmod gettext
if [ $ = 1 ]; then
set timeout=-1
else
set timeout=10
fi
### END /etc/grub.d/00_header ###

### BEGIN /etc/grub.d/05_debian_theme ###
set menu_color_normal=white/black
set menu_color_highlight=black/light-gray
### END /etc/grub.d/05_debian_theme ###

### BEGIN /etc/grub.d/06_mint_theme ###
insmod ext2
set root='(hd1,1)’
search —no-floppy —fs-uuid —set e1a23d21-f756-4de8-8862-6ec1a3ae851e
insmod png
if background_image /boot/grub/linuxmint.png ; then
set color_normal=white/black
set color_highlight=white/light-gray
else
set menu_color_normal=white/black
set menu_color_highlight=white/light-gray
fi
### END /etc/grub.d/06_mint_theme ###

### BEGIN /etc/grub.d/10_linux ###
menuentry «Linux Mint 9, 2.6.32-21-generic (/dev/sdb1)» —class linuxmint —class gnu-linux —class gnu —class os <
recordfail
insmod ext2
set root='(hd1,1)’
search —no-floppy —fs-uuid —set e1a23d21-f756-4de8-8862-6ec1a3ae851e
linux /boot/vmlinuz-2.6.32-21-generic root=UUID=e1a23d21-f756-4de8-8862-6ec1a3ae851e ro quiet splash
initrd /boot/initrd.img-2.6.32-21-generic
>
menuentry «Linux Mint 9, 2.6.32-21-generic (/dev/sdb1) — recovery mode» —class linuxmint —class gnu-linux —class gnu —class os <
recordfail
insmod ext2
set root='(hd1,1)’
search —no-floppy —fs-uuid —set e1a23d21-f756-4de8-8862-6ec1a3ae851e
echo ‘Loading Linux 2.6.32-21-generic . ‘
linux /boot/vmlinuz-2.6.32-21-generic root=UUID=e1a23d21-f756-4de8-8862-6ec1a3ae851e ro single
echo ‘Loading initial ramdisk . ‘
initrd /boot/initrd.img-2.6.32-21-generic
>
### END /etc/grub.d/10_linux ###

### BEGIN /etc/grub.d/10_lupin ###
### END /etc/grub.d/10_lupin ###

### BEGIN /etc/grub.d/20_memtest86+ ###
menuentry «Memory test (memtest86+)» <
insmod ext2
set root='(hd1,1)’
search —no-floppy —fs-uuid —set e1a23d21-f756-4de8-8862-6ec1a3ae851e
linux16 /boot/memtest86+.bin
>
menuentry «Memory test (memtest86+, serial console 115200)» <
insmod ext2
set root='(hd1,1)’
search —no-floppy —fs-uuid —set e1a23d21-f756-4de8-8862-6ec1a3ae851e
linux16 /boot/memtest86+.bin console=ttyS0,115200n8
>
### END /etc/grub.d/20_memtest86+ ###

### BEGIN /etc/grub.d/30_os-prober ###
menuentry «Windows XP Media Center Edition (on /dev/sda1)» <
insmod ntfs
set root='(hd0,1)’
search —no-floppy —fs-uuid —set fe88df3088dee5e5
drivemap -s (hd0) $
chainloader +1
>
menuentry «Windows NT/2000/XP (on /dev/sda2)» <
insmod fat
set root='(hd0,2)’
search —no-floppy —fs-uuid —set 4c85-50cf
drivemap -s (hd0) $
chainloader +1
>
### END /etc/grub.d/30_os-prober ###

### BEGIN /etc/grub.d/40_custom ###
# This file provides an easy way to add custom menu entries. Simply type the
# menu entries you want to add after this comment. Be careful not to change
# the ‘exec tail’ line above.
### END /etc/grub.d/40_custom ###
———————————————————————————

———————————————————————————
# /etc/fstab: static file system information.
#
# Use ‘blkid -o value -s UUID’ to print the universally unique identifier
# for a device; this may be used with UUID= as a more robust way to name
# devices that works even if disks are added and removed. See fstab(5).
#
#

proc /proc proc nodev,noexec,nosuid 0 0
# / was on /dev/sdb1 during installation
UUID=e1a23d21-f756-4de8-8862-6ec1a3ae851e / ext4 errors=remount-ro 0 1
# /home was on /dev/sdb3 during installation
UUID=12b960d0-1954-4fb1-8af8-f381a92e3a58 /home ext4 defaults 0 2
# swap was on /dev/sdb2 during installation
UUID=7332b096-709b-4c1c-ae33-e5ebc1409dd2 none swap sw 0 0
———————————————————————————

Источник

Thread: no such device: error from boot but Nautilus sees it OK

Thread Tools

Display

no such device: error from boot but Nautilus sees it OK

I have an external usb disc which contains some operating systems and user data. Having tried various methods from this forum and google followed by update-grub etc. the boot menu shows the os details but gives the following error messages when selected:

The disc is mounted when logged in to the internal disc Maverick and I can access the files for read and write from there.

Here is the latest RESULTS.txt

It may be in a peculiar state after my abortive attempts to resolve this.

I shall be grateful for advice which enables me to boot into the external disc os(s).

Re: no such device: error from boot but Nautilus sees it OK

Re: no such device: error from boot but Nautilus sees it OK

I still don’t know why, but my new desktop has trouble with grub2 trying to boot a partition farther out on a 500 GB USB hard drive (which boots fine on different laptops from 2006), even though the desktop boots Ubuntu fine from the far end of its 1 TB internal drive. Although, the error I got in the past from grub rescue was: unknown filesystem (for ext3 or ext4). The desktop works fine booting Ubuntu on a partition closer to the beginning an identical 500 GB USB hd (or anywhere on 160 GB USB hd), but I don’t know where the cutoff point is that works. Note:

262.4GB: boot/grub/core.img
284.5GB: boot/grub/grub.cfg
222.7GB: boot/initrd.img-2.6.32-26-generic
222.9GB: boot/initrd.img-2.6.35-23-generic
262.4GB: boot/vmlinuz-2.6.32-26-generic
262.5GB: boot/vmlinuz-2.6.35-23-generic
222.9GB: initrd.img
222.7GB: initrd.img.old
262.5GB: vmlinuz
262.4GB: vmlinuz.old

Maybe it would help to have a separate /boot partition at the beginning of the drive. Was Maverick able to boot from USB before installing Natty?

But you also have older kernels than current kernels in Natty, so not sure if that is an issue. Although, I use 64-bit, so my current uname -a is: Linux natty-ssd 2.6.37-11-generic #25-Ubuntu SMP Tue Dec 21 23:42:56 UTC 2010 x86_64 GNU/Linux

I don’t have Natty on USB hard drive, but I did have Natty on 8 GB USB stick, and now have Kubuntu Natty regular install on that stick. I currently boot Natty from internal SSD with grub2 on that /dev/sdb as boot drive (Win7 & Maverick are on 1 TB hda).

Re: no such device: error from boot but Nautilus sees it OK

From what you’ve posted so far I assume you can boot the 10.10 on sda2, eh? If so the very first thing I’d do is boot into it and run:

Wait for it to say done and see what happens. If the Natty on sdb1 and 10.10 on sdb6 still fail to boot read on.

I see your drives are as follows:

Disk /dev/sda: 30.0 GB
Disk /dev/sdb: 320.1 GB

And the MBR’s are assigned as follows:

So the next thing I’d try is changing the hard drive boot order in BIOS and see if either sdb1 or sdb6 will boot.

If things are still a no-go on both sdb1 and sdb6 I’d like to see the output of:

I should also mention that you appear to have mixed grub2 and legacy grub files on Natty, but I’d not worry about that until we can get the 10.10 on sdb6 booting

Re: no such device: error from boot but Nautilus sees it OK

From what you’ve posted so far I assume you can boot the 10.10 on sda2, eh? If so the very first thing I’d do is boot into it and run:

Yes 10.10 on sda boots as did the sdb installs prior to the last two updates to 10.10 on sda. No change from sudo update-grub.

I see your drives are as follows:

Disk /dev/sda: 30.0 GB
Disk /dev/sdb: 320.1 GB

And the MBR’s are assigned as follows:

So the next thing I’d try is changing the hard drive boot order in BIOS and see if either sdb1 or sdb6 will boot.

The Acer is eight years old and only offers Hard Disk, CD/DVD, Floppy Disk and Networks boot options — it does not have a USB Disk option.

If things are still a no-go on both sdb1 and sdb6 I’d like to see the output of:

Since my first post I installed another 10.10 in sdb8 (10Gb of 90 Gb that I use for additional installs or attempted repairs) in the hope it might sort it for me but no change.

Re: no such device: error from boot but Nautilus sees it OK

Re: no such device: error from boot but Nautilus sees it OK

I am no expert regarding grub2, Linux or anything in particular

Perhaps a tenable temporary workaround could be to roll back the updates to grub2 and post a bug report ( https://help.ubuntu.com/community/Sy. kage%20version https://help.ubuntu.com/community/ReportingBugs — no doubt you knew exactly where these are )

I haven’t researched, I’m guessing that you can access it in nautilus because a module for the kernel that takes care of USB storage in older PCs, where the BIOS doesn’t take care of USB storage access, is being loaded as it ought and perhaps they’ve dropped similar functionality (ie., a similar module(/part of) grub2 has been dropped) rendering the loader blind to your USB storage till a kernel is up and running with it’s module — if I’m right then it will never boot off a USB device using that(/these) version(s) of grub2 in a PC that doesn’t ‘connect’ USB storage in BIOS(/low level).

Being accessible once a kernel is actually booted, ‘update-grub’ and similar utilities can ‘see’ the USB storage and so can happily have it/them listed in the boot menu but if grub2 has been treated/borked as I’ve guessed then it cannot ‘see’ them.

I decided to at least check the changelog for grub2 under 10.10 before posting it is attached, I found the odd entry that made me wonder if that was what borked it for you, but I didn’t come across an entry that made me think that my guess is right for sure.

(I have subscribed this thread)

Источник

Booted up today to Arch not booting up throwing an error
no such device 5c83b9da-5f18-43ee-b8a7-5d5447903851
not a recognised filesystem
install kernel first

I can boot into both my windows and ubuntu installations fine as they are on different partitions
Ubuntu’s disk manager does not recognise my Arch partition anymore, neither does gparted giving this error:

Unable to detect file system! Possible reasons are:
— The file system is damaged
— The file system is unknown to GParted
— There is no file system available (unformatted)
— The device entry /dev/sdb6 is missing

It doesn’t appear in blkid

/dev/sda1: LABEL="Recovery" UUID="5822982922980E5E" TYPE="ntfs" PARTLABEL="Basic data partition" PARTUUID="5ed65451-df91-4e17-a720-dd80de32f76f"
/dev/sda2: LABEL="ESP" UUID="069A-0918" TYPE="vfat" PARTLABEL="EFI system partition" PARTUUID="d4e30b30-c651-4f25-9603-45040a46f7f5"
/dev/sda4: LABEL="Windows" UUID="C2FE9FADFE9F986D" TYPE="ntfs" PARTLABEL="Basic data partition" PARTUUID="438aca20-6384-44cc-921e-8646c89eb796"
/dev/sda5: UUID="F4BCCFE8BCCFA408" TYPE="ntfs" PARTUUID="0c19aac4-14f0-4787-80d7-26683fe24258"
/dev/sdb1: LABEL="DATA" UUID="0A06A26906A2560B" TYPE="ntfs" PARTLABEL="Basic data partition" PARTUUID="49f6005c-3a12-4409-b215-8b0352b92613"
/dev/sdb2: UUID="9BA7-D923" TYPE="vfat" PARTLABEL="EFI System Partition" PARTUUID="b925aeb5-78c3-4808-8dde-150284cb6392"
/dev/sdb3: LABEL="Push Button Reset" UUID="3E5AA6115AA5C5CD" TYPE="ntfs" PARTLABEL="Basic data partition" PARTUUID="fbb2711c-9e64-4f5a-9be2-9c6a5f55d2c0"
/dev/sdb4: LABEL="Ubuntu" UUID="65252ca1-d422-406d-ac17-46cd76c295fb" TYPE="ext4" PARTUUID="e33fc388-bbaa-4823-b6fd-676734164cb5"
/dev/sdb5: UUID="f05c5de1-b50c-4903-879f-2449c7c44ecf" TYPE="swap" PARTUUID="72d77ad0-89e4-417b-a62f-996824568eda"

But if I sudo blkid the partition I get

/dev/sdb6: PTUUID="9e073b42" PTTYPE="dos" PARTUUID="4660abcc-8a51-4ccf-9e50-cef6f78f98b1"

fdisk -l also shows /dev/sdb6/ partition even with the correct filesytem type

Disk /dev/sdb: 931.5 GiB, 1000204886016 bytes, 1953525168 sectors
Units: sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 4096 bytes
I/O size (minimum/optimal): 4096 bytes / 4096 bytes
Disklabel type: gpt
Disk identifier: E5209390-E94B-463B-AB67-0C84217B6AC8

Device          Start        End    Sectors  Size Type
/dev/sdb1        2048 1757450695 1757448648  838G Microsoft basic data
/dev/sdb2  1829378048 1830426623    1048576  512M EFI System
/dev/sdb3  1927258112 1953523711   26265600 12.5G Windows recovery environment
/dev/sdb4  1830426624 1893859327   63432704 30.3G Linux filesystem
/dev/sdb5  1893859328 1927258111   33398784 15.9G Linux swap
/dev/sdb6  1757450696 1829378047   71927352 34.3G Linux filesystem

So it seems to all be there just not mounting correctly on initial boot, it is sitting behind a large NTFS partition which can causes issues but it was fine until suddenly.
Any suggestions? Thanks

Last edited by ButteryCrumpet (2018-01-16 15:22:48)

Sometime you may encounter error messages like Error: no such device: xxxxx-xxxx-xxxx-xxxx-xxxxx  right after powering up the PC.

Such problems are caused by misconfigured GRUB, unable to load any operating system.

Usually happens when you resize, rename or shrink the disk partitions. Or may be even if you transfer a perfectly working hard drive from one PC to another.

But there’s an easy solution to deal with such problems, and here we’ll discuss about it.

Why this is happening?

This grub no such device problem usually happens when the boot drive’s UUID is changed somehow.

Like if you convert a disk drive with MBR partition table to GPT partition table. Another reason of UUID change is if you resize, merge, shrink or extend the linux root partition.

Here GRUB is present as bootloader, but it can’t find the proper modules and configuration file due to changed partition UUID.

To fix this problem, you’ve to determine three things.

First which one is the linux root( / ) partition, second how the system is booted, i.e. in UEFI mode or in legacy BIOS mode.

Third, if it’s booted in UEFI mode, then which is the EFI system partition?

You can use the parted command to determine the ESP partition, which is a FAT32 filesystem of around 100MB.

sudo parted /dev/sda print

Now the actual steps to fix the error no such device problem.

1. Use the ls command on the grub rescue prompt to list all the partitions.
2. Then you can use the ls command again to check the contents of each partitions to be sure.

   ls (hd0,1)/

   The linux root partition will contain /bin , /boot, /lib etc. etc directories.

3. If you’re sure about the linux root partition, then type the commands listed below one by one. In my case, the partition is (hd0,msdos5) .

   set root=(hd0,5)
   set prefix=(hd0,5)/boot/grub
   insmod normal
   normal

4. Then you should be able to access the GRUB boot menu like before, select the linux distro and boot to it.
5. After booting, you must be asked to login to your user account.
6. Next login to the account and open up a terminal window.
7. Then determine if the system is booted with UEFI mode or legacy BIOS mode, use the one liner script below.

   [ -d /sys/firmware/efi ] && echo "UEFI boot" || echo "Legacy boot"

8. To reinstall GRUB for legacy BIOS use this command.

   sudo grub-install /dev/sda --target=i386-pc

9. To re install GRUB on a UEFI based system, use this.

   sudo mount /dev/sda2 /boot/efi     # mount the EFI system partition
   sudo grub-install /dev/sda --target=x86_64-efi --efi-directory=esp

10. If grub installation reports no problem, then update the GRUB configuration file.

    sudo update-grub

11. Finally reboot the PC or laptop to check the if it worked at all or not.

Also don’t just copy-paste the commands, your EFI system partition could be different, most probably /dev/sda1 .

Conclusion

It’s not a very well described tutorial to fix the grub rescue no such device issue. But I hope you’ve got basic the idea to deal with the error no such device issue.

First you need to boot linux somehow then reinstall the GRUB bootloader and update the GRUB configuration. Here’s the detailed GRUB rescue tutorial.

If you’ve any question or suggestion, leave comments below.

I am in the process of replacing Windows 10 on a Cambio 10.1 RCA tablet. I have Bliss OS 11.11 loaded onto it. I successfully got the OS to begin after installing it, but when I turn off the tablet or reboot it to start up Bliss OS 11.11 again it gives me a Shell command page. I don’t know what to do, so I just choose Shell> Exit.

Then it takes me to the OS boot page with Bliss-OS 11.11, Bliss-OS 11.11 (Gearlock Recovery Mode), Bliss 11.11 — old modprobe mode, etc. on its blue page with Enter: Boot Selection, E: Edit Selection and C: Grub Command at the top.

When I hit enter on Bliss-OS 11.11. I get this:

error: variable ‘root’ isn’t set.

error: no such device: /bliss-x86-11.11/kernel.

error: variable ‘root’ isn’t set.

error: you need to load the kernel first.

Then it takes me back to the list of Bliss OS types and I get no further.

I AM able to access Bliss-OS with the USB dongle and choosing Advanced Options hd0,msdos1 to boot from, but that takes me back to basically restarting the whole setup of the OS again entirely. Like I keep having to re-install it over and over and over again. Obviously this is not a work around.

Now look, I’m not a linux guy and I don’t really know how to do things from this type of operating system, but I’ve already spent 6 hours at least on trying to fix it myself. I googled. I went into Grub and tried to fix it myself. I looked up about a dozen guides for this, but none of it seems to apply to Bliss OS or even Android for that matter. Now I know my way around Grub to some degree and feel proud of myself for that, but nothing I’ve wasted hours on has helped. The Bliss OS docs page is down and the giant forum on XDA dedicated to it is no help either. All I can find is ElektrikJesus saying «Just look in the thread for the countless other people posting on it.» Yeah, that forum is 2,900+ posts and the question may be posted a bunch, but the solution much less so.

I’ve done my leg work, guys, and it failed me. Can you please just tell me how to fix this or direct me to what works?

Other useful info:
The partition that has the useful stuff appears to be on (hd0,msdos1), which I think is the USB dongle.

Using the Terminal Emulator on Bliss OS, the kernel name appears to be 4.19.122-android-x86_64-gb20240b1dfcf.

The file I downloaded from Bliss to begin this journey is Bliss-v11.12—OFFICIAL-20200925-0851_x86_64_k-k4.19.122-ax86-ga-rmi_m-p9.0-x86_dgc-p9.0-x86-crhd_gms.iso