The cryptboot from kmille

cryptboot's People

Contributors

Stargazers

Watchers

cryptboot's Issues

Is there a way to fix OpROM problems?

Hello,

I was wondering if there is a way to use OpROMs that are signed with other certificates than my own without enrolling those certificates into my db.
Really more of a question now than an issue, but it at least is somewhat related :)
Feel free to close this anytime.

Couldn't find EFI System partition mountpoint '/boot/efi', check your /etc/fstab

I'm trying to cryptboot mount but get an error saying that couldn't find the EFI partition whereas I think it's already there.
Any ideas?

anarchy: ~ $ sudo fdisk -l /dev/nvme0n1
Disk /dev/nvme0n1: 465.76 GiB, 500107862016 bytes, 976773168 sectors
Disk model: Samsung SSD 970 EVO Plus 500GB          
Units: sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 512 bytes
I/O size (minimum/optimal): 512 bytes / 512 bytes
Disklabel type: gpt
Disk identifier: 0D9FA33F-C4BF-4489-B8B6-FACE938B59E9

Device           Start       End   Sectors   Size Type
/dev/nvme0n1p1    2048   1048576   1046529   511M EFI System
/dev/nvme0n1p2 2099200 976773134 974673935 464.8G Linux filesystem
/dev/nvme0n1p3 1050624   2099199   1048576   512M Linux swap

anarchy: ~ $ cat /etc/fstab
# Static information about the filesystems.
# See fstab(5) for details.

# <file system> <dir> <type> <options> <dump> <pass>
# /dev/nvme0n1p2
UUID=2fc91d0c-7e3c-464f-973c-2c8d54df3555 / ext4 rw,relatime 0 1

# /dev/nvme0n1p1
UUID=D48C-AAB1 /boot vfat rw,relatime,fmask=0022,dmask=0022,codepage=437,iocharset=ascii,shortname=mixed,utf8,errors=remount-ro 0 2

# /dev/nvme0n1p3
UUID=fb239ff2-171b-4b3c-9451-eb64826834d none swap defaults 0 0

Recommend Projects