blkid knows no NVME hard disks in rescue-shell

New features which should be implemented in Porteus; suggestions are welcome. All questions or problems with testing releases (alpha, beta, or rc) should go in their relevant thread here, rather than the Bug Reports section.
Post Reply
alubypass
White ninja
White ninja
Posts: 8
Joined: 12 Sep 2019, 14:01
Distribution: Porteus 5

blkid knows no NVME hard disks in rescue-shell

Post#1 by alubypass » 06 Mar 2020, 15:46

Hello,

I use the current version 5 of Porteus. I noticed something. When I start Porteus on a notebook with only one NVME hard disk, Porteus does not find the config file. In the rescue shell you can see that blkid does not return anything. But if you plug in a USB stick, it will be recognized by blkid. But a cat /proc/partions recognizes all partitions of the NVME and after a closer look I found out that the blkid is in the rescue shell from 2012 and therefore does not know any NVME. Also the version of blkid in the started porteus is newer than the version in the rescue shell. Would it be possible to provide a newer version of blkid or BusyBox in rescue shell ?

Thanks
alubypass

jssouza
DEV Team
DEV Team
Posts: 1165
Joined: 09 Jul 2015, 14:17
Distribution: Porteus x86 arm

blkid knows no NVME hard disks in rescue-shell

Post#2 by jssouza » 06 Mar 2020, 17:14

We have an initrd variant that we are testing which has busybox v1.31.1 and blkid linked to it, rather than a separate binary.

alubypass
White ninja
White ninja
Posts: 8
Joined: 12 Sep 2019, 14:01
Distribution: Porteus 5

blkid knows no NVME hard disks in rescue-shell

Post#3 by alubypass » 06 Mar 2020, 17:52

Hello jssouza, is it possible that I can get a link to the initrd ? I'd like to test it, if that's okay.

jssouza
DEV Team
DEV Team
Posts: 1165
Joined: 09 Jul 2015, 14:17
Distribution: Porteus x86 arm

blkid knows no NVME hard disks in rescue-shell

Post#4 by jssouza » 07 Mar 2020, 09:35

Here you go:
https://www.mediafire.com/file/iyeu9iby ... nt.xz/file
md5sum: 78e2b4f2ca0843eac9e01f6539738e49

Post Reply