[SOLVED] UEFI no such device on slacks root partition.

after many hours of frustration. I finally got it to almost working using this (Crap) OS boot manager (BIOS) I ended up going to UEFI w/csm along with a wait state for selecting boot options.

If it selects the BIOS OS Boot Manager using that then it slips into Slackware grub with like it should. But if I remove the time out, then it goes into the BIOS Boot Manager and locks up , grub rescue>

error no such drive:
142d8df6-d0df-4518-b15d-138c36ec4863
unknown file system

that is

/dev/sdb2: UUID="142d8df6-d0df-4518-b15d-138c36ec4863" TYPE="ext4" PARTUUID="7b21e464-69ed-f045-8456-9fddfa655671"

which is Slacks root partition. so what THE &&& now????

Please provide output of this command:

lsblk -l -o name,fstype,uuid,partuuid

Originally Posted by Didier Spaier Please provide output of this command: lsblk -l -o name,fstype,uuid,partuuid

yeah thanks, so I work up this morning got to wondering about this issue, thinking about what more might it be. whittling it down to what haven't I tried yet? the only thing I could come up with is fast boot, which I've read about but it has never effect my laptop, always having it on.

So I got this ho 840 g2 with a good amount of options to pick from, and finally I decide to go UEFI everything, and this BIOS has that capability to go pure uefi. All of the OS'es are UEFI capable. but over a short period of time I find that I cannot use the UEFI w/o old school csm to help it.

so yeah , I turned off 'fast boot' and it is working. so with my moving things about like I did, and still not getting the desired results, and seeing that I was better off with the way I had it. well I just wasted a bunch of hours.


Okay I think I got somewhat screwed up I got the uefi install , then grub uefi installed too via slack docs. and in lue of trying to explain in detail because I do not even know how to put it all in to words ect...

$ lsblk -l -o name,fstype,uuid,partuuid
NAME FSTYPE UUID                                 PARTUUID
sda                                              
sda1 vfat   8798-C87B                            d0b1076d-0768-4088-808b-37440a968aed
sda2 ext4   606f650f-19a9-4b98-bf96-837c319bef1e b381e04c-4752-46b3-9c01-d3426beaa97c
sdb                                              
sdb1 ntfs   6367832D2FDF2B7B                     ec6c8425-0b24-4d98-8140-f5fe2a60fe3c
sdb2 ext4   142d8df6-d0df-4518-b15d-138c36ec4863 7b21e464-69ed-f045-8456-9fddfa655671
sdb3 ext4   187ce1c6-d61e-4ccf-9dfd-938b9d7730a1 8c2ebe74-bed9-0045-b654-9daa0c9e9002
sdb4 ext4   b352b8eb-967b-4922-827b-038a8cb17978 c28310d6-268b-4e49-a0f7-dc365f6ddd55
sdb5 vfat   BD41-11EE                            688a64ca-ffe4-11e9-a82f-480fcf2a5b40
sdb6 ufs    5dc19afcb78ff8a3                     688af616-ffe4-11e9-a82f-480fcf2a5b40
sdb7                                             688bfea4-ffe4-11e9-a82f-480fcf2a5b40
mmcblk0
                                                 
mmcblk0p1
     ext4   992d2614-392b-4a75-9221-b0de218f33bd d09b8eb7-01

first vfat is Windows, Linux fat32 efi, second is FreeBSD fat16 efi. AND, with FBSD own efibootmgr it shows slack, and windows, and itself, I changed the order to freebsd first but that is not working, that is what leads me to think it is that grub install thing I did that is booting my systems.

#grub-install --target=x86_64-efi --efi-directory=/boot/efi --bootloader-id=grub --recheck --debug
and
#grub-install --target=x86_64-efi /dev/sda

https://docs.slackware.com/howtos:sl...based_hardware

I do not think I even need that, I'd like to not use it, and use pure UEFI efibootmgr, but that might be me .. wishful thinking.

what is the output of

parted -l

First, grub won't work in Legacy mode as you have a GPT but no Bios Boot partition. For this reason, you can only boot in EFI mode if using grub.

Second, which software gives the error mentioned in your first post?

Third, please indicate us the content of /dev/sda1 and /dev/sdb5. Mount each of them one at a time, for instance as /mnt then type either "find /mnt" or "tree /mnt" and post the ouptut.

Fourth, download and copy to a small usb stick this ISO image: https://slint.fr/testing/grub/detect.iso
It will make a rescue boot disk that you can use to boot any of your installed systems until you completely solve this issue.

To coy it to the stick (I'll assume it's named /dev/sdc, adapt the name as need be, but check the device name carefully!):

cp detect.iso /dev/sdc

PS the ISO is very small (7.8M) but to avoid wasting the remaining free space on the USB stick, just use fdisk or cfdisk after having copied the ISO on it to create a third partition then put a file system in it.

OK this is where I am NOW at. fresh windows 10 install, fresh Slackware 14.2+ elilo, fresh FreeBSD install, all uefi. UEFI w/o csm windows 10 crashes, I have to enter boot selection then travel down and find the oses bootx64.efi file and select that to get anyone of these to boot into themselves.

NO efibootmgr install by me in anything. I did how ever install easyUEFI for windows and created list for slack, and freebsd to be added, made slack first to boot, and nhahaha NOPE that didn't work.

$  lsblk -l -o name,fstype,uuid,partuuid
NAME FSTYPE UUID                                 PARTUUID
sda                                              
sda1 vfat   FEB8-B7A6                            d0b1076d-0768-4088-808b-37440a968aed
sda2 ext4   606f650f-19a9-4b98-bf96-837c319bef1e b381e04c-4752-46b3-9c01-d3426beaa97c
sdb                                              
sdb1 ntfs   2739C9745025E0C4                     ec6c8425-0b24-4d98-8140-f5fe2a60fe3c
sdb2 ext4   915a2520-c27c-4fcd-9c99-5fc287e3e7f6 f8ee5869-f873-4971-aeda-989f4d35878c
sdb3 ext4   187ce1c6-d61e-4ccf-9dfd-938b9d7730a1 8c2ebe74-bed9-0045-b654-9daa0c9e9002
sdb4 ext4   b352b8eb-967b-4922-827b-038a8cb17978 c28310d6-268b-4e49-a0f7-dc365f6ddd55
sdb5                                             def8e6b9-8298-4b6b-b156-9a3086dc2593
sdb6 vfat   BD41-11EE                            21a6f531-020b-11ea-9449-480fcf2a5b40
sdb7 ufs    5dc53717271a8bf2                     21a72b67-020b-11ea-9449-480fcf2a5b40
sdb8                                             21a7b57f-020b-11ea-9449-480fcf2a5b40
mmcblk0
                                                 
mmcblk0p1
     ext4   992d2614-392b-4a75-9221-b0de218f33bd d09b8eb7-01

$ su
Password: 
bash-5.0# parted -l
Model: ATA Samsung SSD 860 (scsi)
Disk /dev/sda: 500GB
Sector size (logical/physical): 512B/512B
Partition Table: gpt
Disk Flags: 

Number  Start   End    Size   File system  Name  Flags
 1      1049kB  525MB  524MB  fat32              boot, esp
 2      525MB   500GB  500GB  ext4


Model: ATA CHN NGFFSA2242 2 (scsi)
Disk /dev/sdb: 256GB
Sector size (logical/physical): 512B/512B
Partition Table: gpt
Disk Flags: 

Number  Start   End     Size    File system  Name                          Flags
 1      1049kB  37.2GB  37.2GB  ntfs                                       msftdata
 2      37.2GB  64.0GB  26.7GB  ext4
 3      64.0GB  96.3GB  32.3GB  ext4
 4      96.3GB  186GB   89.8GB  ext4
 5      186GB   186GB   16.8MB               Microsoft reserved partition  msftres
 6      186GB   186GB   210MB   fat16                                      boot, esp
 7      186GB   253GB   66.4GB
 8      253GB   256GB   3403MB


Model: SD SS64G (sd/mmc)
Disk /dev/mmcblk0: 63.9GB
Sector size (logical/physical): 512B/512B
Partition Table: msdos
Disk Flags: 

Number  Start   End     Size    Type     File system  Flags
 1      1049kB  63.9GB  63.9GB  primary  ext4

bash-5.0# cp detect.iso /dev/sdc
cp: cannot stat 'detect.iso': No such file or directory

It looks like you forgot to download the ISO. Do this then:

wget https://slint.fr/testing/grub/detect.iso
cp detect.iso /dev/sdc

And you do not need to be root for these commands.

Originally Posted by Didier Spaier It looks like you forgot to download the ISO. Do this then: wget https://slint.fr/testing/grub/detect.iso cp detect.iso /dev/sdc And you do not need to be root for these commands.

sdc is empty unless I add a stick, am i suppose to add a stick or cp into la la land?

bash-5.0# ls /dev/sd*
/dev/sda   /dev/sda2  /dev/sdb1  /dev/sdb3  /dev/sdb5  /dev/sdb7
/dev/sda1  /dev/sdb   /dev/sdb2  /dev/sdb4  /dev/sdb6  /dev/sdb8

did I miss something, do I need to go back and review? ....

Originally Posted by Didier Spaier First, grub won't work in Legacy mode as you have a GPT but no Bios Boot partition. For this reason, you can only boot in EFI mode if using grub. Second, which software gives the error mentioned in your first post? Third, please indicate us the content of /dev/sda1 and /dev/sdb5. Mount each of them one at a time, for instance as /mnt then type either "find /mnt" or "tree /mnt" and post the ouptut. Fourth, download and copy to a small usb stick this ISO image: https://slint.fr/testing/grub/detect.iso It will make a rescue boot disk that you can use to boot any of your installed systems until you completely solve this issue. To coy it to the stick (I'll assume it's named /dev/sdc, adapt the name as need be, but check the device name carefully!): cp detect.iso /dev/sdc PS the ISO is very small (7.8M) but to avoid wasting the remaining free space on the USB stick, just use fdisk or cfdisk after having copied the ISO on it to create a third partition then put a file system in it.

sda1 vfat   FEB8-B7A6                            d0b1076d-0768-4088-808b-37440a968aed

that up there is EFI partition fat32 for windows, and linux OS'es

------------
bash-5.0# mount /dev/sda1 /mnt
bash-5.0# ls /mnt
EFI
bash-5.0# ls /mnt/EFI
Boot  Microsoft  Slackware

bash-5.0# umount /mnt
bash-5.0# mount /dev/sda5 /mnt
mount: /mnt: special device /dev/sda5 does not exist.
bash-5.0# mount /dev/sda6 /mnt
mount: /mnt: special device /dev/sda6 does not exist.
bash-5.0# mount /dev/sda7 /mnt
mount: /mnt: special device /dev/sda7 does not exist.
bash-5.0# mount /dev/sda8 /mnt
mount: /mnt: special device /dev/sda8 does not exist.

they are FreeBSD format it too has a fat16 efi because it cannot use fat32 so it makes its own fat16 efi.
------------------------------

tree

bash-5.0# mount /dev/sda1 /mnt
bash-5.0# tree /mnt
/mnt
└── EFI
    ├── Boot
    │** └── bootx64.efi
    ├── Microsoft
    │** ├── Boot
    │** │** ├── BCD
    │** │** ├── BCD.LOG
    │** │** ├── BCD.LOG1
    │** │** ├── BCD.LOG2
    │** │** ├── BOOTSTAT.DAT
    │** │** ├── Fonts
    │** │** │** ├── chs_boot.ttf
    │** │** │** ├── cht_boot.ttf
    │** │** │** ├── jpn_boot.ttf
    │** │** │** ├── kor_boot.ttf
    │** │** │** ├── malgun_boot.ttf
    │** │** │** ├── malgunn_boot.ttf
    │** │** │** ├── meiryo_boot.ttf
    │** │** │** ├── meiryon_boot.ttf
    │** │** │** ├── msjh_boot.ttf
    │** │** │** ├── msjhn_boot.ttf
    │** │** │** ├── msyh_boot.ttf
    │** │** │** ├── msyhn_boot.ttf
    │** │** │** ├── segmono_boot.ttf
    │** │** │** ├── segoe_slboot.ttf
    │** │** │** ├── segoen_slboot.ttf
    │** │** │** └── wgl4_boot.ttf
    │** │** ├── Resources
    │** │** │** ├── bootres.dll
    │** │** │** └── en-US
    │** │** │**     └── bootres.dll.mui
    │** │** ├── bg-BG
    │** │** │** ├── bootmgfw.efi.mui
    │** │** │** └── bootmgr.efi.mui
    │** │** ├── boot.stl
    │** │** ├── bootmgfw.efi
    │** │** ├── bootmgr.efi
    │** │** ├── cs-CZ
    │** │** │** ├── bootmgfw.efi.mui
    │** │** │** ├── bootmgr.efi.mui
    │** │** │** └── memtest.efi.mui
    │** │** ├── da-DK
    │** │** │** ├── bootmgfw.efi.mui
    │** │** │** ├── bootmgr.efi.mui
    │** │** │** └── memtest.efi.mui
    │** │** ├── de-DE
    │** │** │** ├── bootmgfw.efi.mui
    │** │** │** ├── bootmgr.efi.mui
    │** │** │** └── memtest.efi.mui
    │** │** ├── el-GR
    │** │** │** ├── bootmgfw.efi.mui
    │** │** │** ├── bootmgr.efi.mui
    │** │** │** └── memtest.efi.mui
    │** │** ├── en-GB
    │** │** │** ├── bootmgfw.efi.mui
    │** │** │** └── bootmgr.efi.mui
    │** │** ├── en-US
    │** │** │** ├── bootmgfw.efi.mui
    │** │** │** ├── bootmgr.efi.mui
    │** │** │** └── memtest.efi.mui
    │** │** ├── es-ES
    │** │** │** ├── bootmgfw.efi.mui
    │** │** │** ├── bootmgr.efi.mui
    │** │** │** └── memtest.efi.mui
    │** │** ├── es-MX
    │** │** │** ├── bootmgfw.efi.mui
    │** │** │** └── bootmgr.efi.mui
    │** │** ├── et-EE
    │** │** │** ├── bootmgfw.efi.mui
    │** │** │** └── bootmgr.efi.mui
    │** │** ├── fi-FI
    │** │** │** ├── bootmgfw.efi.mui
    │** │** │** ├── bootmgr.efi.mui
    │** │** │** └── memtest.efi.mui
    │** │** ├── fr-CA
    │** │** │** ├── bootmgfw.efi.mui
    │** │** │** └── bootmgr.efi.mui
    │** │** ├── fr-FR
    │** │** │** ├── bootmgfw.efi.mui
    │** │** │** ├── bootmgr.efi.mui
    │** │** │** └── memtest.efi.mui
    │** │** ├── hr-HR
    │** │** │** ├── bootmgfw.efi.mui
    │** │** │** └── bootmgr.efi.mui
    │** │** ├── hu-HU
    │** │** │** ├── bootmgfw.efi.mui
    │** │** │** ├── bootmgr.efi.mui
    │** │** │** └── memtest.efi.mui
    │** │** ├── it-IT
    │** │** │** ├── bootmgfw.efi.mui
    │** │** │** ├── bootmgr.efi.mui
    │** │** │** └── memtest.efi.mui
    │** │** ├── ja-JP
    │** │** │** ├── bootmgfw.efi.mui
    │** │** │** ├── bootmgr.efi.mui
    │** │** │** └── memtest.efi.mui
    │** │** ├── kd_02_10df.dll
    │** │** ├── kd_02_10ec.dll
    │** │** ├── kd_02_1137.dll
    │** │** ├── kd_02_14e4.dll
    │** │** ├── kd_02_15b3.dll
    │** │** ├── kd_02_1969.dll
    │** │** ├── kd_02_19a2.dll
    │** │** ├── kd_02_1af4.dll
    │** │** ├── kd_02_8086.dll
    │** │** ├── kd_07_1415.dll
    │** │** ├── kd_0C_8086.dll
    │** │** ├── kdstub.dll
    │** │** ├── ko-KR
    │** │** │** ├── bootmgfw.efi.mui
    │** │** │** ├── bootmgr.efi.mui
    │** │** │** └── memtest.efi.mui
    │** │** ├── lt-LT
    │** │** │** ├── bootmgfw.efi.mui
    │** │** │** └── bootmgr.efi.mui
    │** │** ├── lv-LV
    │** │** │** ├── bootmgfw.efi.mui
    │** │** │** └── bootmgr.efi.mui
    │** │** ├── memtest.efi
    │** │** ├── nb-NO
    │** │** │** ├── bootmgfw.efi.mui
    │** │** │** ├── bootmgr.efi.mui
    │** │** │** └── memtest.efi.mui
    │** │** ├── nl-NL
    │** │** │** ├── bootmgfw.efi.mui
    │** │** │** ├── bootmgr.efi.mui
    │** │** │** └── memtest.efi.mui
    │** │** ├── pl-PL
    │** │** │** ├── bootmgfw.efi.mui
    │** │** │** ├── bootmgr.efi.mui
    │** │** │** └── memtest.efi.mui
    │** │** ├── pt-BR
    │** │** │** ├── bootmgfw.efi.mui
    │** │** │** ├── bootmgr.efi.mui
    │** │** │** └── memtest.efi.mui
    │** │** ├── pt-PT
    │** │** │** ├── bootmgfw.efi.mui
    │** │** │** ├── bootmgr.efi.mui
    │** │** │** └── memtest.efi.mui
    │** │** ├── qps-ploc
    │** │** │** └── memtest.efi.mui
    │** │** ├── ro-RO
    │** │** │** ├── bootmgfw.efi.mui
    │** │** │** └── bootmgr.efi.mui
    │** │** ├── ru-RU
    │** │** │** ├── bootmgfw.efi.mui
    │** │** │** ├── bootmgr.efi.mui
    │** │** │** └── memtest.efi.mui
    │** │** ├── sk-SK
    │** │** │** ├── bootmgfw.efi.mui
    │** │** │** └── bootmgr.efi.mui
    │** │** ├── sl-SI
    │** │** │** ├── bootmgfw.efi.mui
    │** │** │** └── bootmgr.efi.mui
    │** │** ├── sr-Latn-RS
    │** │** │** ├── bootmgfw.efi.mui
    │** │** │** └── bootmgr.efi.mui
    │** │** ├── sv-SE
    │** │** │** ├── bootmgfw.efi.mui
    │** │** │** ├── bootmgr.efi.mui
    │** │** │** └── memtest.efi.mui
    │** │** ├── tr-TR
    │** │** │** ├── bootmgfw.efi.mui
    │** │** │** ├── bootmgr.efi.mui
    │** │** │** └── memtest.efi.mui
    │** │** ├── uk-UA
    │** │** │** ├── bootmgfw.efi.mui
    │** │** │** └── bootmgr.efi.mui
    │** │** ├── winsipolicy.p7b
    │** │** ├── zh-CN
    │** │** │** ├── bootmgfw.efi.mui
    │** │** │** ├── bootmgr.efi.mui
    │** │** │** └── memtest.efi.mui
    │** │** └── zh-TW
    │** │**     ├── bootmgfw.efi.mui
    │** │**     ├── bootmgr.efi.mui
    │** │**     └── memtest.efi.mui
    │** └── Recovery
    │**     ├── BCD
    │**     ├── BCD.LOG
    │**     ├── BCD.LOG1
    │**     └── BCD.LOG2
    └── Slackware
        ├── elilo.conf
        ├── elilo.efi
        ├── initrd.gz
        └── vmlinuz

45 directories, 142 files

I do not actaully need to boot stick, I can fanagle my BIOS for boot options to load the *.efi file to whatever I want to boot, this is just the BIOS OS BOOT MANAGER booting not what I need.

tough this was about when I had it using slacks grubx64.efi it was going into resuce grub> less I did it the round about way to get it, via by BIOS BOOT OPTIONS. then manually selecting the same file to boot.

Indeed you need to plug in an USB stick to write on it!
Also the second EFI partition is /dev/sdb6, so do this as I wrote:

mount /dev/sdb6 /mnt
tree /mnt

Originally Posted by Didier Spaier Indeed you need to plug in an USB stick to write on it! Also the second EFI partition is /dev/sdb6, so do this as I wrote: mount /dev/sdb6 /mnt tree /mnt

again that is FreeBSD efi partition fat16 /media/EFISYS/efi/boot/BOOTx64.efi and startup.nsh

I am in FreeBSD right now..

Then according to the EFI shell specification if every thing else fails then the EFI shell should execute the script starup.nsh. Please provide its content, for instance typing "cat /path/to/startup", replacing /path/to/ by the real path to this file.

anyways, I ended up having to reestablish my efi partition on the same drive because I wanted to, and reading this https://forums.freebsd.org/threads/c...on-uefi.68141/ link in here, saying the boot is default if the BIOS cannot find anything else to use it uses that bootx64.efi, I moved windows one out and put in grubx64.efi -> bootx64.efi so it defualts to grabing that and I get my linux grub efi menu ...

it is right back to how it was in the first place, and efibootmgr is useless on my system.