Grub-install error: disk 'crpytouuid/' not found

Clash Royale CLAN TAG#URR8PPP
up vote
0
down vote
favorite
I followed fdiblen's guide on Arch Linux Installation with a Fully encrypted disk and Btrfs filesystem that uses cryptsetup.
I'm at the bootloader stage where I'm trying to grub-install with these new lines in my /etc/default/grub
GRUB_ENABLE_CRYPTODISK=y
GRUB_CMDLINE_LINUX="cryptdevice=/dev/nvme0n1p3:crpytroot:allow-discards"
And while executing the line
grub-install --target=i386-pc /dev/nvme0n1
I got the error:
Grub-install: error: disk 'crpytouuid/0cebxxxxxxxxxxx' not found
I have tried goolging crpytouuid and strangely I didn't get any useful result.
I went to check my /dev/disk/by-uuid and saw that 0cebxxxxxxxxxxx is indeed the uuid of my third partition nvme0n1p3 (which is where / is).
So I did grub-install again but with --verbose and this is what I get:
As you can see in the screenshot grub-install logs that
/dev/mapper/cryptroot is not present.
so that can be where the problem is but doing ls /dev/mapper/cryptroot shows that /dev/mapper/cryptroot exists.
I also tried changing
GRUB_CMDLINE_LINUX="cryptdevice=/dev/nvme0n1p3:crpytroot:allow-discards"
to
GRUB_CMDLINE_LINUX="cryptdevice=/dev/disk/by-uuid/0cebxxxxxxxxxxx:crpytroot:allow-discards root=/dev/mapper/cryptroot"
and got the same error.
arch-linux system-installation grub disk-encryption cryptsetup
add a comment |Â
up vote
0
down vote
favorite
I followed fdiblen's guide on Arch Linux Installation with a Fully encrypted disk and Btrfs filesystem that uses cryptsetup.
I'm at the bootloader stage where I'm trying to grub-install with these new lines in my /etc/default/grub
GRUB_ENABLE_CRYPTODISK=y
GRUB_CMDLINE_LINUX="cryptdevice=/dev/nvme0n1p3:crpytroot:allow-discards"
And while executing the line
grub-install --target=i386-pc /dev/nvme0n1
I got the error:
Grub-install: error: disk 'crpytouuid/0cebxxxxxxxxxxx' not found
I have tried goolging crpytouuid and strangely I didn't get any useful result.
I went to check my /dev/disk/by-uuid and saw that 0cebxxxxxxxxxxx is indeed the uuid of my third partition nvme0n1p3 (which is where / is).
So I did grub-install again but with --verbose and this is what I get:
As you can see in the screenshot grub-install logs that
/dev/mapper/cryptroot is not present.
so that can be where the problem is but doing ls /dev/mapper/cryptroot shows that /dev/mapper/cryptroot exists.
I also tried changing
GRUB_CMDLINE_LINUX="cryptdevice=/dev/nvme0n1p3:crpytroot:allow-discards"
to
GRUB_CMDLINE_LINUX="cryptdevice=/dev/disk/by-uuid/0cebxxxxxxxxxxx:crpytroot:allow-discards root=/dev/mapper/cryptroot"
and got the same error.
arch-linux system-installation grub disk-encryption cryptsetup
Your cryptdevice is wrong: you want a space, not a:between the dm-name and the optionallow-discards.
â jasonwryan
May 9 at 23:30
@jasonwryan that doesn't solve a thing. still the same error.
â Archy Wilhes éÂÂä½Â
May 10 at 3:30
Well, it did solve the issue of your cryptdevice line being completely wrong... But you're welcome anyway.
â jasonwryan
May 10 at 6:12
@jasonwryan the parser will just ignore it anyway. it really doesn't change a thing here.
â Archy Wilhes éÂÂä½Â
May 10 at 23:06
@jasonwryan also can you send me a link to a doc that validate what you have said (i.e. showing that:is the wrong syntax.)? now that will be a lot more useful.
â Archy Wilhes éÂÂä½Â
May 10 at 23:17
add a comment |Â
up vote
0
down vote
favorite
up vote
0
down vote
favorite
I followed fdiblen's guide on Arch Linux Installation with a Fully encrypted disk and Btrfs filesystem that uses cryptsetup.
I'm at the bootloader stage where I'm trying to grub-install with these new lines in my /etc/default/grub
GRUB_ENABLE_CRYPTODISK=y
GRUB_CMDLINE_LINUX="cryptdevice=/dev/nvme0n1p3:crpytroot:allow-discards"
And while executing the line
grub-install --target=i386-pc /dev/nvme0n1
I got the error:
Grub-install: error: disk 'crpytouuid/0cebxxxxxxxxxxx' not found
I have tried goolging crpytouuid and strangely I didn't get any useful result.
I went to check my /dev/disk/by-uuid and saw that 0cebxxxxxxxxxxx is indeed the uuid of my third partition nvme0n1p3 (which is where / is).
So I did grub-install again but with --verbose and this is what I get:
As you can see in the screenshot grub-install logs that
/dev/mapper/cryptroot is not present.
so that can be where the problem is but doing ls /dev/mapper/cryptroot shows that /dev/mapper/cryptroot exists.
I also tried changing
GRUB_CMDLINE_LINUX="cryptdevice=/dev/nvme0n1p3:crpytroot:allow-discards"
to
GRUB_CMDLINE_LINUX="cryptdevice=/dev/disk/by-uuid/0cebxxxxxxxxxxx:crpytroot:allow-discards root=/dev/mapper/cryptroot"
and got the same error.
arch-linux system-installation grub disk-encryption cryptsetup
I followed fdiblen's guide on Arch Linux Installation with a Fully encrypted disk and Btrfs filesystem that uses cryptsetup.
I'm at the bootloader stage where I'm trying to grub-install with these new lines in my /etc/default/grub
GRUB_ENABLE_CRYPTODISK=y
GRUB_CMDLINE_LINUX="cryptdevice=/dev/nvme0n1p3:crpytroot:allow-discards"
And while executing the line
grub-install --target=i386-pc /dev/nvme0n1
I got the error:
Grub-install: error: disk 'crpytouuid/0cebxxxxxxxxxxx' not found
I have tried goolging crpytouuid and strangely I didn't get any useful result.
I went to check my /dev/disk/by-uuid and saw that 0cebxxxxxxxxxxx is indeed the uuid of my third partition nvme0n1p3 (which is where / is).
So I did grub-install again but with --verbose and this is what I get:
As you can see in the screenshot grub-install logs that
/dev/mapper/cryptroot is not present.
so that can be where the problem is but doing ls /dev/mapper/cryptroot shows that /dev/mapper/cryptroot exists.
I also tried changing
GRUB_CMDLINE_LINUX="cryptdevice=/dev/nvme0n1p3:crpytroot:allow-discards"
to
GRUB_CMDLINE_LINUX="cryptdevice=/dev/disk/by-uuid/0cebxxxxxxxxxxx:crpytroot:allow-discards root=/dev/mapper/cryptroot"
and got the same error.
arch-linux system-installation grub disk-encryption cryptsetup
asked May 9 at 22:43
Archy Wilhes éÂÂä½Â
1042
1042
Your cryptdevice is wrong: you want a space, not a:between the dm-name and the optionallow-discards.
â jasonwryan
May 9 at 23:30
@jasonwryan that doesn't solve a thing. still the same error.
â Archy Wilhes éÂÂä½Â
May 10 at 3:30
Well, it did solve the issue of your cryptdevice line being completely wrong... But you're welcome anyway.
â jasonwryan
May 10 at 6:12
@jasonwryan the parser will just ignore it anyway. it really doesn't change a thing here.
â Archy Wilhes éÂÂä½Â
May 10 at 23:06
@jasonwryan also can you send me a link to a doc that validate what you have said (i.e. showing that:is the wrong syntax.)? now that will be a lot more useful.
â Archy Wilhes éÂÂä½Â
May 10 at 23:17
add a comment |Â
Your cryptdevice is wrong: you want a space, not a:between the dm-name and the optionallow-discards.
â jasonwryan
May 9 at 23:30
@jasonwryan that doesn't solve a thing. still the same error.
â Archy Wilhes éÂÂä½Â
May 10 at 3:30
Well, it did solve the issue of your cryptdevice line being completely wrong... But you're welcome anyway.
â jasonwryan
May 10 at 6:12
@jasonwryan the parser will just ignore it anyway. it really doesn't change a thing here.
â Archy Wilhes éÂÂä½Â
May 10 at 23:06
@jasonwryan also can you send me a link to a doc that validate what you have said (i.e. showing that:is the wrong syntax.)? now that will be a lot more useful.
â Archy Wilhes éÂÂä½Â
May 10 at 23:17
Your cryptdevice is wrong: you want a space, not a
: between the dm-name and the option allow-discards.â jasonwryan
May 9 at 23:30
Your cryptdevice is wrong: you want a space, not a
: between the dm-name and the option allow-discards.â jasonwryan
May 9 at 23:30
@jasonwryan that doesn't solve a thing. still the same error.
â Archy Wilhes éÂÂä½Â
May 10 at 3:30
@jasonwryan that doesn't solve a thing. still the same error.
â Archy Wilhes éÂÂä½Â
May 10 at 3:30
Well, it did solve the issue of your cryptdevice line being completely wrong... But you're welcome anyway.
â jasonwryan
May 10 at 6:12
Well, it did solve the issue of your cryptdevice line being completely wrong... But you're welcome anyway.
â jasonwryan
May 10 at 6:12
@jasonwryan the parser will just ignore it anyway. it really doesn't change a thing here.
â Archy Wilhes éÂÂä½Â
May 10 at 23:06
@jasonwryan the parser will just ignore it anyway. it really doesn't change a thing here.
â Archy Wilhes éÂÂä½Â
May 10 at 23:06
@jasonwryan also can you send me a link to a doc that validate what you have said (i.e. showing that
: is the wrong syntax.)? now that will be a lot more useful.â Archy Wilhes éÂÂä½Â
May 10 at 23:17
@jasonwryan also can you send me a link to a doc that validate what you have said (i.e. showing that
: is the wrong syntax.)? now that will be a lot more useful.â Archy Wilhes éÂÂä½Â
May 10 at 23:17
add a comment |Â
active
oldest
votes
active
oldest
votes
active
oldest
votes
active
oldest
votes
active
oldest
votes
Sign up or log in
StackExchange.ready(function ()
StackExchange.helpers.onClickDraftSave('#login-link');
);
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
StackExchange.ready(
function ()
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2funix.stackexchange.com%2fquestions%2f442877%2fgrub-install-error-disk-crpytouuid-uuid-not-found%23new-answer', 'question_page');
);
Post as a guest
Sign up or log in
StackExchange.ready(function ()
StackExchange.helpers.onClickDraftSave('#login-link');
);
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Sign up or log in
StackExchange.ready(function ()
StackExchange.helpers.onClickDraftSave('#login-link');
);
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Sign up or log in
StackExchange.ready(function ()
StackExchange.helpers.onClickDraftSave('#login-link');
);
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Your cryptdevice is wrong: you want a space, not a
:between the dm-name and the optionallow-discards.â jasonwryan
May 9 at 23:30
@jasonwryan that doesn't solve a thing. still the same error.
â Archy Wilhes éÂÂä½Â
May 10 at 3:30
Well, it did solve the issue of your cryptdevice line being completely wrong... But you're welcome anyway.
â jasonwryan
May 10 at 6:12
@jasonwryan the parser will just ignore it anyway. it really doesn't change a thing here.
â Archy Wilhes éÂÂä½Â
May 10 at 23:06
@jasonwryan also can you send me a link to a doc that validate what you have said (i.e. showing that
:is the wrong syntax.)? now that will be a lot more useful.â Archy Wilhes éÂÂä½Â
May 10 at 23:17