Enabling Grub on Linux Mint 18.2 LUKS encrypted disk in dual-boot system
Clash Royale CLAN TAG#URR8PPP
up vote
0
down vote
favorite
I recently installed LUKS encrypted Linux Mint 18.2 onto an SSDD at the time of install the it was the only disk present. Then I reattached my Windows 7 disk which is also encrypted using veracrypt. The Linux Mint disk is the first in the boot order. So I tried to customize the and update the grub menu , using a method that worked for me on a unencrypted install of mint, by doing the following;
1) sudo nano /etc/grub.d/40_custom
adding then this;
menuentry "Next in Boot Sequence"
exit
Save and close.sud
2) sudo update-grub
After that I get this error message;
Generating grub configuration file ...
Warning: Setting GRUB_TIMEOUT to a non-zero value when GRUB_HIDDEN_TIMEOUT is set is no longer supported.
Found linux image: /boot/vmlinuz-4.8.0-53-generic
Found initrd image: /boot/initrd.img-4.8.0-53-generic
Found memtest86+ image: /memtest86+.elf
Found memtest86+ image: /memtest86+.bin
done
Does anyone know how to fix this or have any alternative booting strategies?
linux-mint dual-boot grub luks
asked Nov 12 '17 at 18:06
James Draper
1538
add a comment |Â
up vote
0
down vote
favorite
I recently installed LUKS encrypted Linux Mint 18.2 onto an SSDD at the time of install the it was the only disk present. Then I reattached my Windows 7 disk which is also encrypted using veracrypt. The Linux Mint disk is the first in the boot order. So I tried to customize the and update the grub menu , using a method that worked for me on a unencrypted install of mint, by doing the following;
1) sudo nano /etc/grub.d/40_custom
adding then this;
menuentry "Next in Boot Sequence"
exit
Save and close.sud
2) sudo update-grub
After that I get this error message;
Generating grub configuration file ...
Warning: Setting GRUB_TIMEOUT to a non-zero value when GRUB_HIDDEN_TIMEOUT is set is no longer supported.
Found linux image: /boot/vmlinuz-4.8.0-53-generic
Found initrd image: /boot/initrd.img-4.8.0-53-generic
Found memtest86+ image: /memtest86+.elf
Found memtest86+ image: /memtest86+.bin
done
Does anyone know how to fix this or have any alternative booting strategies?
linux-mint dual-boot grub luks
asked Nov 12 '17 at 18:06
James Draper
1538
That's not an error, it's a warning. Consider posting the final, generated Grub configuration.
– Emmanuel Rosa
Nov 14 '17 at 17:02
Sure what is the file path for that again?
– James Draper
Nov 14 '17 at 17:06
On MBR systems it's something like/boot/grub/grub.cfg.
– Emmanuel Rosa
Nov 14 '17 at 17:09
add a comment |Â
up vote
0
down vote
favorite
up vote
0
down vote
favorite
I recently installed LUKS encrypted Linux Mint 18.2 onto an SSDD at the time of install the it was the only disk present. Then I reattached my Windows 7 disk which is also encrypted using veracrypt. The Linux Mint disk is the first in the boot order. So I tried to customize the and update the grub menu , using a method that worked for me on a unencrypted install of mint, by doing the following;
1) sudo nano /etc/grub.d/40_custom
adding then this;
menuentry "Next in Boot Sequence"
exit
Save and close.sud
2) sudo update-grub
After that I get this error message;
Generating grub configuration file ...
Warning: Setting GRUB_TIMEOUT to a non-zero value when GRUB_HIDDEN_TIMEOUT is set is no longer supported.
Found linux image: /boot/vmlinuz-4.8.0-53-generic
Found initrd image: /boot/initrd.img-4.8.0-53-generic
Found memtest86+ image: /memtest86+.elf
Found memtest86+ image: /memtest86+.bin
done
Does anyone know how to fix this or have any alternative booting strategies?
linux-mint dual-boot grub luks
asked Nov 12 '17 at 18:06
James Draper
1538
I recently installed LUKS encrypted Linux Mint 18.2 onto an SSDD at the time of install the it was the only disk present. Then I reattached my Windows 7 disk which is also encrypted using veracrypt. The Linux Mint disk is the first in the boot order. So I tried to customize the and update the grub menu , using a method that worked for me on a unencrypted install of mint, by doing the following;
1) sudo nano /etc/grub.d/40_custom
adding then this;
menuentry "Next in Boot Sequence"
exit
Save and close.sud
2) sudo update-grub
After that I get this error message;
Generating grub configuration file ...
Warning: Setting GRUB_TIMEOUT to a non-zero value when GRUB_HIDDEN_TIMEOUT is set is no longer supported.
Found linux image: /boot/vmlinuz-4.8.0-53-generic
Found initrd image: /boot/initrd.img-4.8.0-53-generic
Found memtest86+ image: /memtest86+.elf
Found memtest86+ image: /memtest86+.bin
done
Does anyone know how to fix this or have any alternative booting strategies?
linux-mint dual-boot grub luks
asked Nov 12 '17 at 18:06
James Draper
1538
asked Nov 12 '17 at 18:06
James Draper
1538
asked Nov 12 '17 at 18:06
James Draper
1538
asked Nov 12 '17 at 18:06
James Draper
1538
1538
That's not an error, it's a warning. Consider posting the final, generated Grub configuration.
– Emmanuel Rosa
Nov 14 '17 at 17:02
Sure what is the file path for that again?
– James Draper
Nov 14 '17 at 17:06
On MBR systems it's something like/boot/grub/grub.cfg.
– Emmanuel Rosa
Nov 14 '17 at 17:09
add a comment |Â
That's not an error, it's a warning. Consider posting the final, generated Grub configuration.
– Emmanuel Rosa
Nov 14 '17 at 17:02
Sure what is the file path for that again?
– James Draper
Nov 14 '17 at 17:06
On MBR systems it's something like/boot/grub/grub.cfg.
– Emmanuel Rosa
Nov 14 '17 at 17:09
That's not an error, it's a warning. Consider posting the final, generated Grub configuration.
– Emmanuel Rosa
Nov 14 '17 at 17:02
That's not an error, it's a warning. Consider posting the final, generated Grub configuration.
– Emmanuel Rosa
Nov 14 '17 at 17:02
Sure what is the file path for that again?
– James Draper
Nov 14 '17 at 17:06
Sure what is the file path for that again?
– James Draper
Nov 14 '17 at 17:06
On MBR systems it's something like
/boot/grub/grub.cfg.– Emmanuel Rosa
Nov 14 '17 at 17:09
On MBR systems it's something like
/boot/grub/grub.cfg.– Emmanuel Rosa
Nov 14 '17 at 17:09
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%2f404086%2fenabling-grub-on-linux-mint-18-2-luks-encrypted-disk-in-dual-boot-system%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
That's not an error, it's a warning. Consider posting the final, generated Grub configuration.
– Emmanuel Rosa
Nov 14 '17 at 17:02
Sure what is the file path for that again?
– James Draper
Nov 14 '17 at 17:06
On MBR systems it's something like
/boot/grub/grub.cfg.– Emmanuel Rosa
Nov 14 '17 at 17:09