Stuck in a ~30sec boot loop after grub, encrypted volumes

The name of the pictureThe name of the pictureThe name of the pictureClash Royale CLAN TAG#URR8PPP











up vote
0
down vote

favorite












I got my new laptop and I installed Debian 9 Testing alongside OEM'd Windows 10.



I did not encrypt the whole Debian partition, i managed to encrypt the /home and /swap only (not sure if reasonable, but I did it that way...).



Now, when I reach grub on startup and select Debian my system is stuck in a ~30 seconds boot loop where



(NCRYPT is my LVM volume name)



Volume group "NCRYPT" not found
Cannot process volume group NCRYPT


is printed over and over until



Gave up waiting for suspend/resume device


And then I'm able to insert my passphrase, decipher the encrypted partition, and reach the lightdm where i can log in the new session.



Checking out journalctl I found out that, at some point, this is printed:



ct 07 10:12:15 debian kernel: random: lvm: uninitialized urandom read (4 bytes read)
Oct 07 10:12:15 debian kernel: random: lvm: uninitialized urandom read (4 bytes read)
Oct 07 10:12:15 debian kernel: random: lvm: uninitialized urandom read (4 bytes read)
Oct 07 10:12:15 debian kernel: random: lvm: uninitialized urandom read (4 bytes read)
Oct 07 10:12:15 debian kernel: random: lvm: uninitialized urandom read (4 bytes read)
Oct 07 10:12:15 debian kernel: random: lvm: uninitialized urandom read (4 bytes read)
Oct 07 10:12:15 debian kernel: random: lvm: uninitialized urandom read (4 bytes read)
Oct 07 10:12:15 debian kernel: random: lvm: uninitialized urandom read (4 bytes read)


Grep-ing "NCRYPT" gives me:



pagano@debian:~$ sudo journalctl | grep NCRYPT
Oct 07 10:12:24 debian lvm[681]: 2 logical volume(s) in volume group "NCRYPT" now active
Oct 07 10:12:24 debian systemd[1]: Found device /dev/mapper/NCRYPT-swap.
Oct 07 10:12:24 debian systemd[1]: Found device /dev/mapper/NCRYPT-home.
Oct 07 10:12:24 debian systemd[1]: Activating swap /dev/mapper/NCRYPT-swap...
Oct 07 10:12:24 debian kernel: Adding 7811068k swap on /dev/mapper/NCRYPT-swap. Priority:-2 extents:1 across:7811068k SSFS
Oct 07 10:12:24 debian systemd[1]: Activated swap /dev/mapper/NCRYPT-swap.
Oct 07 10:12:24 debian lvm[697]: 2 logical volume(s) in volume group "NCRYPT" monitored
Oct 07 10:12:24 debian systemd[1]: Starting File System Check on /dev/mapper/NCRYPT-home...
Oct 07 10:12:24 debian systemd-fsck[700]: /dev/mapper/NCRYPT-home: clean, 10766/3530752 files, 1531219/14116864 blocks
Oct 07 10:12:24 debian systemd[1]: Started File System Check on /dev/mapper/NCRYPT-home.


This is the output of my /etc/fstab:



pagano@debian:~$ cat /etc/fstab 
# /etc/fstab: static file system information.
#
# Use 'blkid' to print the universally unique identifier for a
# device; this may be used with UUID= as a more robust way to name devices
# that works even if disks are added and removed. See fstab(5).
#
# <file system> <mount point> <type> <options> <dump> <pass>
# / was on /dev/nvme0n1p4 during installation
UUID=4b84cf4f-9124-408e-8047-ce57465d0cd9 / ext4 errors=remount-ro 0 1
# /boot/efi was on /dev/nvme0n1p1 during installation
UUID=C880-B670 /boot/efi vfat umask=0077 0 1
/dev/mapper/NCRYPT-home /home ext4 defaults 0 2
/dev/mapper/NCRYPT-swap none swap sw 0 0


This is the output of /etc/crypttab:



sudo cat /etc/crypttab 
nvme0n1p5_crypt UUID=24276de5-4748-4695-973c-600506de6068 none luks


... and these are blkid ...



sudo blkid -c /dev/null -o list
device fs_type label mount point UUID

/dev/nvme0n1
(in use)
/dev/nvme0n1p1
vfat SYSTEM /boot/efi C880-B670
/dev/nvme0n1p2
(not mounted)
/dev/nvme0n1p3
ntfs Windows (not mounted) 2CFC870DFC86D10E
/dev/nvme0n1p4
ext4 / 4b84cf4f-9124-408e-8047-ce57465d0cd9
/dev/nvme0n1p5
crypto_LUKS (in use) 24276de5-4748-4695-973c-600506de6068
/dev/mapper/nvme0n1p5_crypt
LVM2_member (in use) xjeWlz-bxzP-cjmp-Pxdd-3wSP-YUsg-TMpczg
/dev/mapper/NCRYPT-swap
swap [SWAP] 574eb521-71bf-44e5-9ceb-af8e34bd64a2
/dev/mapper/NCRYPT-home
ext4 /home 30fb1988-212c-4887-ba27-6d9fddc539cd


... and lsblk :



sudo lsblk -o name,uuid,mountpoint
NAME UUID MOUNTPOINT
nvme0n1
├─nvme0n1p1 C880-B670 /boot/efi
├─nvme0n1p2
├─nvme0n1p3 2CFC870DFC86D10E
├─nvme0n1p4 4b84cf4f-9124-408e-8047-ce57465d0cd9 /
└─nvme0n1p5 24276de5-4748-4695-973c-600506de6068
└─nvme0n1p5_crypt xjeWlz-bxzP-cjmp-Pxdd-3wSP-YUsg-TMpczg
├─NCRYPT-swap 574eb521-71bf-44e5-9ceb-af8e34bd64a2 [SWAP]
└─NCRYPT-home 30fb1988-212c-4887-ba27-6d9fddc539cd /home


What can I do to fix this behaviour?










share|improve this question









New contributor




ncryptn00b is a new contributor to this site. Take care in asking for clarification, commenting, and answering.
Check out our Code of Conduct.























    up vote
    0
    down vote

    favorite












    I got my new laptop and I installed Debian 9 Testing alongside OEM'd Windows 10.



    I did not encrypt the whole Debian partition, i managed to encrypt the /home and /swap only (not sure if reasonable, but I did it that way...).



    Now, when I reach grub on startup and select Debian my system is stuck in a ~30 seconds boot loop where



    (NCRYPT is my LVM volume name)



    Volume group "NCRYPT" not found
    Cannot process volume group NCRYPT


    is printed over and over until



    Gave up waiting for suspend/resume device


    And then I'm able to insert my passphrase, decipher the encrypted partition, and reach the lightdm where i can log in the new session.



    Checking out journalctl I found out that, at some point, this is printed:



    ct 07 10:12:15 debian kernel: random: lvm: uninitialized urandom read (4 bytes read)
    Oct 07 10:12:15 debian kernel: random: lvm: uninitialized urandom read (4 bytes read)
    Oct 07 10:12:15 debian kernel: random: lvm: uninitialized urandom read (4 bytes read)
    Oct 07 10:12:15 debian kernel: random: lvm: uninitialized urandom read (4 bytes read)
    Oct 07 10:12:15 debian kernel: random: lvm: uninitialized urandom read (4 bytes read)
    Oct 07 10:12:15 debian kernel: random: lvm: uninitialized urandom read (4 bytes read)
    Oct 07 10:12:15 debian kernel: random: lvm: uninitialized urandom read (4 bytes read)
    Oct 07 10:12:15 debian kernel: random: lvm: uninitialized urandom read (4 bytes read)


    Grep-ing "NCRYPT" gives me:



    pagano@debian:~$ sudo journalctl | grep NCRYPT
    Oct 07 10:12:24 debian lvm[681]: 2 logical volume(s) in volume group "NCRYPT" now active
    Oct 07 10:12:24 debian systemd[1]: Found device /dev/mapper/NCRYPT-swap.
    Oct 07 10:12:24 debian systemd[1]: Found device /dev/mapper/NCRYPT-home.
    Oct 07 10:12:24 debian systemd[1]: Activating swap /dev/mapper/NCRYPT-swap...
    Oct 07 10:12:24 debian kernel: Adding 7811068k swap on /dev/mapper/NCRYPT-swap. Priority:-2 extents:1 across:7811068k SSFS
    Oct 07 10:12:24 debian systemd[1]: Activated swap /dev/mapper/NCRYPT-swap.
    Oct 07 10:12:24 debian lvm[697]: 2 logical volume(s) in volume group "NCRYPT" monitored
    Oct 07 10:12:24 debian systemd[1]: Starting File System Check on /dev/mapper/NCRYPT-home...
    Oct 07 10:12:24 debian systemd-fsck[700]: /dev/mapper/NCRYPT-home: clean, 10766/3530752 files, 1531219/14116864 blocks
    Oct 07 10:12:24 debian systemd[1]: Started File System Check on /dev/mapper/NCRYPT-home.


    This is the output of my /etc/fstab:



    pagano@debian:~$ cat /etc/fstab 
    # /etc/fstab: static file system information.
    #
    # Use 'blkid' to print the universally unique identifier for a
    # device; this may be used with UUID= as a more robust way to name devices
    # that works even if disks are added and removed. See fstab(5).
    #
    # <file system> <mount point> <type> <options> <dump> <pass>
    # / was on /dev/nvme0n1p4 during installation
    UUID=4b84cf4f-9124-408e-8047-ce57465d0cd9 / ext4 errors=remount-ro 0 1
    # /boot/efi was on /dev/nvme0n1p1 during installation
    UUID=C880-B670 /boot/efi vfat umask=0077 0 1
    /dev/mapper/NCRYPT-home /home ext4 defaults 0 2
    /dev/mapper/NCRYPT-swap none swap sw 0 0


    This is the output of /etc/crypttab:



    sudo cat /etc/crypttab 
    nvme0n1p5_crypt UUID=24276de5-4748-4695-973c-600506de6068 none luks


    ... and these are blkid ...



    sudo blkid -c /dev/null -o list
    device fs_type label mount point UUID

    /dev/nvme0n1
    (in use)
    /dev/nvme0n1p1
    vfat SYSTEM /boot/efi C880-B670
    /dev/nvme0n1p2
    (not mounted)
    /dev/nvme0n1p3
    ntfs Windows (not mounted) 2CFC870DFC86D10E
    /dev/nvme0n1p4
    ext4 / 4b84cf4f-9124-408e-8047-ce57465d0cd9
    /dev/nvme0n1p5
    crypto_LUKS (in use) 24276de5-4748-4695-973c-600506de6068
    /dev/mapper/nvme0n1p5_crypt
    LVM2_member (in use) xjeWlz-bxzP-cjmp-Pxdd-3wSP-YUsg-TMpczg
    /dev/mapper/NCRYPT-swap
    swap [SWAP] 574eb521-71bf-44e5-9ceb-af8e34bd64a2
    /dev/mapper/NCRYPT-home
    ext4 /home 30fb1988-212c-4887-ba27-6d9fddc539cd


    ... and lsblk :



    sudo lsblk -o name,uuid,mountpoint
    NAME UUID MOUNTPOINT
    nvme0n1
    ├─nvme0n1p1 C880-B670 /boot/efi
    ├─nvme0n1p2
    ├─nvme0n1p3 2CFC870DFC86D10E
    ├─nvme0n1p4 4b84cf4f-9124-408e-8047-ce57465d0cd9 /
    └─nvme0n1p5 24276de5-4748-4695-973c-600506de6068
    └─nvme0n1p5_crypt xjeWlz-bxzP-cjmp-Pxdd-3wSP-YUsg-TMpczg
    ├─NCRYPT-swap 574eb521-71bf-44e5-9ceb-af8e34bd64a2 [SWAP]
    └─NCRYPT-home 30fb1988-212c-4887-ba27-6d9fddc539cd /home


    What can I do to fix this behaviour?










    share|improve this question









    New contributor




    ncryptn00b is a new contributor to this site. Take care in asking for clarification, commenting, and answering.
    Check out our Code of Conduct.





















      up vote
      0
      down vote

      favorite









      up vote
      0
      down vote

      favorite











      I got my new laptop and I installed Debian 9 Testing alongside OEM'd Windows 10.



      I did not encrypt the whole Debian partition, i managed to encrypt the /home and /swap only (not sure if reasonable, but I did it that way...).



      Now, when I reach grub on startup and select Debian my system is stuck in a ~30 seconds boot loop where



      (NCRYPT is my LVM volume name)



      Volume group "NCRYPT" not found
      Cannot process volume group NCRYPT


      is printed over and over until



      Gave up waiting for suspend/resume device


      And then I'm able to insert my passphrase, decipher the encrypted partition, and reach the lightdm where i can log in the new session.



      Checking out journalctl I found out that, at some point, this is printed:



      ct 07 10:12:15 debian kernel: random: lvm: uninitialized urandom read (4 bytes read)
      Oct 07 10:12:15 debian kernel: random: lvm: uninitialized urandom read (4 bytes read)
      Oct 07 10:12:15 debian kernel: random: lvm: uninitialized urandom read (4 bytes read)
      Oct 07 10:12:15 debian kernel: random: lvm: uninitialized urandom read (4 bytes read)
      Oct 07 10:12:15 debian kernel: random: lvm: uninitialized urandom read (4 bytes read)
      Oct 07 10:12:15 debian kernel: random: lvm: uninitialized urandom read (4 bytes read)
      Oct 07 10:12:15 debian kernel: random: lvm: uninitialized urandom read (4 bytes read)
      Oct 07 10:12:15 debian kernel: random: lvm: uninitialized urandom read (4 bytes read)


      Grep-ing "NCRYPT" gives me:



      pagano@debian:~$ sudo journalctl | grep NCRYPT
      Oct 07 10:12:24 debian lvm[681]: 2 logical volume(s) in volume group "NCRYPT" now active
      Oct 07 10:12:24 debian systemd[1]: Found device /dev/mapper/NCRYPT-swap.
      Oct 07 10:12:24 debian systemd[1]: Found device /dev/mapper/NCRYPT-home.
      Oct 07 10:12:24 debian systemd[1]: Activating swap /dev/mapper/NCRYPT-swap...
      Oct 07 10:12:24 debian kernel: Adding 7811068k swap on /dev/mapper/NCRYPT-swap. Priority:-2 extents:1 across:7811068k SSFS
      Oct 07 10:12:24 debian systemd[1]: Activated swap /dev/mapper/NCRYPT-swap.
      Oct 07 10:12:24 debian lvm[697]: 2 logical volume(s) in volume group "NCRYPT" monitored
      Oct 07 10:12:24 debian systemd[1]: Starting File System Check on /dev/mapper/NCRYPT-home...
      Oct 07 10:12:24 debian systemd-fsck[700]: /dev/mapper/NCRYPT-home: clean, 10766/3530752 files, 1531219/14116864 blocks
      Oct 07 10:12:24 debian systemd[1]: Started File System Check on /dev/mapper/NCRYPT-home.


      This is the output of my /etc/fstab:



      pagano@debian:~$ cat /etc/fstab 
      # /etc/fstab: static file system information.
      #
      # Use 'blkid' to print the universally unique identifier for a
      # device; this may be used with UUID= as a more robust way to name devices
      # that works even if disks are added and removed. See fstab(5).
      #
      # <file system> <mount point> <type> <options> <dump> <pass>
      # / was on /dev/nvme0n1p4 during installation
      UUID=4b84cf4f-9124-408e-8047-ce57465d0cd9 / ext4 errors=remount-ro 0 1
      # /boot/efi was on /dev/nvme0n1p1 during installation
      UUID=C880-B670 /boot/efi vfat umask=0077 0 1
      /dev/mapper/NCRYPT-home /home ext4 defaults 0 2
      /dev/mapper/NCRYPT-swap none swap sw 0 0


      This is the output of /etc/crypttab:



      sudo cat /etc/crypttab 
      nvme0n1p5_crypt UUID=24276de5-4748-4695-973c-600506de6068 none luks


      ... and these are blkid ...



      sudo blkid -c /dev/null -o list
      device fs_type label mount point UUID

      /dev/nvme0n1
      (in use)
      /dev/nvme0n1p1
      vfat SYSTEM /boot/efi C880-B670
      /dev/nvme0n1p2
      (not mounted)
      /dev/nvme0n1p3
      ntfs Windows (not mounted) 2CFC870DFC86D10E
      /dev/nvme0n1p4
      ext4 / 4b84cf4f-9124-408e-8047-ce57465d0cd9
      /dev/nvme0n1p5
      crypto_LUKS (in use) 24276de5-4748-4695-973c-600506de6068
      /dev/mapper/nvme0n1p5_crypt
      LVM2_member (in use) xjeWlz-bxzP-cjmp-Pxdd-3wSP-YUsg-TMpczg
      /dev/mapper/NCRYPT-swap
      swap [SWAP] 574eb521-71bf-44e5-9ceb-af8e34bd64a2
      /dev/mapper/NCRYPT-home
      ext4 /home 30fb1988-212c-4887-ba27-6d9fddc539cd


      ... and lsblk :



      sudo lsblk -o name,uuid,mountpoint
      NAME UUID MOUNTPOINT
      nvme0n1
      ├─nvme0n1p1 C880-B670 /boot/efi
      ├─nvme0n1p2
      ├─nvme0n1p3 2CFC870DFC86D10E
      ├─nvme0n1p4 4b84cf4f-9124-408e-8047-ce57465d0cd9 /
      └─nvme0n1p5 24276de5-4748-4695-973c-600506de6068
      └─nvme0n1p5_crypt xjeWlz-bxzP-cjmp-Pxdd-3wSP-YUsg-TMpczg
      ├─NCRYPT-swap 574eb521-71bf-44e5-9ceb-af8e34bd64a2 [SWAP]
      └─NCRYPT-home 30fb1988-212c-4887-ba27-6d9fddc539cd /home


      What can I do to fix this behaviour?










      share|improve this question









      New contributor




      ncryptn00b is a new contributor to this site. Take care in asking for clarification, commenting, and answering.
      Check out our Code of Conduct.











      I got my new laptop and I installed Debian 9 Testing alongside OEM'd Windows 10.



      I did not encrypt the whole Debian partition, i managed to encrypt the /home and /swap only (not sure if reasonable, but I did it that way...).



      Now, when I reach grub on startup and select Debian my system is stuck in a ~30 seconds boot loop where



      (NCRYPT is my LVM volume name)



      Volume group "NCRYPT" not found
      Cannot process volume group NCRYPT


      is printed over and over until



      Gave up waiting for suspend/resume device


      And then I'm able to insert my passphrase, decipher the encrypted partition, and reach the lightdm where i can log in the new session.



      Checking out journalctl I found out that, at some point, this is printed:



      ct 07 10:12:15 debian kernel: random: lvm: uninitialized urandom read (4 bytes read)
      Oct 07 10:12:15 debian kernel: random: lvm: uninitialized urandom read (4 bytes read)
      Oct 07 10:12:15 debian kernel: random: lvm: uninitialized urandom read (4 bytes read)
      Oct 07 10:12:15 debian kernel: random: lvm: uninitialized urandom read (4 bytes read)
      Oct 07 10:12:15 debian kernel: random: lvm: uninitialized urandom read (4 bytes read)
      Oct 07 10:12:15 debian kernel: random: lvm: uninitialized urandom read (4 bytes read)
      Oct 07 10:12:15 debian kernel: random: lvm: uninitialized urandom read (4 bytes read)
      Oct 07 10:12:15 debian kernel: random: lvm: uninitialized urandom read (4 bytes read)


      Grep-ing "NCRYPT" gives me:



      pagano@debian:~$ sudo journalctl | grep NCRYPT
      Oct 07 10:12:24 debian lvm[681]: 2 logical volume(s) in volume group "NCRYPT" now active
      Oct 07 10:12:24 debian systemd[1]: Found device /dev/mapper/NCRYPT-swap.
      Oct 07 10:12:24 debian systemd[1]: Found device /dev/mapper/NCRYPT-home.
      Oct 07 10:12:24 debian systemd[1]: Activating swap /dev/mapper/NCRYPT-swap...
      Oct 07 10:12:24 debian kernel: Adding 7811068k swap on /dev/mapper/NCRYPT-swap. Priority:-2 extents:1 across:7811068k SSFS
      Oct 07 10:12:24 debian systemd[1]: Activated swap /dev/mapper/NCRYPT-swap.
      Oct 07 10:12:24 debian lvm[697]: 2 logical volume(s) in volume group "NCRYPT" monitored
      Oct 07 10:12:24 debian systemd[1]: Starting File System Check on /dev/mapper/NCRYPT-home...
      Oct 07 10:12:24 debian systemd-fsck[700]: /dev/mapper/NCRYPT-home: clean, 10766/3530752 files, 1531219/14116864 blocks
      Oct 07 10:12:24 debian systemd[1]: Started File System Check on /dev/mapper/NCRYPT-home.


      This is the output of my /etc/fstab:



      pagano@debian:~$ cat /etc/fstab 
      # /etc/fstab: static file system information.
      #
      # Use 'blkid' to print the universally unique identifier for a
      # device; this may be used with UUID= as a more robust way to name devices
      # that works even if disks are added and removed. See fstab(5).
      #
      # <file system> <mount point> <type> <options> <dump> <pass>
      # / was on /dev/nvme0n1p4 during installation
      UUID=4b84cf4f-9124-408e-8047-ce57465d0cd9 / ext4 errors=remount-ro 0 1
      # /boot/efi was on /dev/nvme0n1p1 during installation
      UUID=C880-B670 /boot/efi vfat umask=0077 0 1
      /dev/mapper/NCRYPT-home /home ext4 defaults 0 2
      /dev/mapper/NCRYPT-swap none swap sw 0 0


      This is the output of /etc/crypttab:



      sudo cat /etc/crypttab 
      nvme0n1p5_crypt UUID=24276de5-4748-4695-973c-600506de6068 none luks


      ... and these are blkid ...



      sudo blkid -c /dev/null -o list
      device fs_type label mount point UUID

      /dev/nvme0n1
      (in use)
      /dev/nvme0n1p1
      vfat SYSTEM /boot/efi C880-B670
      /dev/nvme0n1p2
      (not mounted)
      /dev/nvme0n1p3
      ntfs Windows (not mounted) 2CFC870DFC86D10E
      /dev/nvme0n1p4
      ext4 / 4b84cf4f-9124-408e-8047-ce57465d0cd9
      /dev/nvme0n1p5
      crypto_LUKS (in use) 24276de5-4748-4695-973c-600506de6068
      /dev/mapper/nvme0n1p5_crypt
      LVM2_member (in use) xjeWlz-bxzP-cjmp-Pxdd-3wSP-YUsg-TMpczg
      /dev/mapper/NCRYPT-swap
      swap [SWAP] 574eb521-71bf-44e5-9ceb-af8e34bd64a2
      /dev/mapper/NCRYPT-home
      ext4 /home 30fb1988-212c-4887-ba27-6d9fddc539cd


      ... and lsblk :



      sudo lsblk -o name,uuid,mountpoint
      NAME UUID MOUNTPOINT
      nvme0n1
      ├─nvme0n1p1 C880-B670 /boot/efi
      ├─nvme0n1p2
      ├─nvme0n1p3 2CFC870DFC86D10E
      ├─nvme0n1p4 4b84cf4f-9124-408e-8047-ce57465d0cd9 /
      └─nvme0n1p5 24276de5-4748-4695-973c-600506de6068
      └─nvme0n1p5_crypt xjeWlz-bxzP-cjmp-Pxdd-3wSP-YUsg-TMpczg
      ├─NCRYPT-swap 574eb521-71bf-44e5-9ceb-af8e34bd64a2 [SWAP]
      └─NCRYPT-home 30fb1988-212c-4887-ba27-6d9fddc539cd /home


      What can I do to fix this behaviour?







      boot lvm luks loop-device volume






      share|improve this question









      New contributor




      ncryptn00b is a new contributor to this site. Take care in asking for clarification, commenting, and answering.
      Check out our Code of Conduct.











      share|improve this question









      New contributor




      ncryptn00b is a new contributor to this site. Take care in asking for clarification, commenting, and answering.
      Check out our Code of Conduct.









      share|improve this question




      share|improve this question








      edited yesterday









      Rui F Ribeiro

      37k1273117




      37k1273117






      New contributor




      ncryptn00b is a new contributor to this site. Take care in asking for clarification, commenting, and answering.
      Check out our Code of Conduct.









      asked yesterday









      ncryptn00b

      1




      1




      New contributor




      ncryptn00b is a new contributor to this site. Take care in asking for clarification, commenting, and answering.
      Check out our Code of Conduct.





      New contributor





      ncryptn00b is a new contributor to this site. Take care in asking for clarification, commenting, and answering.
      Check out our Code of Conduct.






      ncryptn00b is a new contributor to this site. Take care in asking for clarification, commenting, and answering.
      Check out our Code of Conduct.

























          active

          oldest

          votes











          Your Answer







          StackExchange.ready(function()
          var channelOptions =
          tags: "".split(" "),
          id: "106"
          ;
          initTagRenderer("".split(" "), "".split(" "), channelOptions);

          StackExchange.using("externalEditor", function()
          // Have to fire editor after snippets, if snippets enabled
          if (StackExchange.settings.snippets.snippetsEnabled)
          StackExchange.using("snippets", function()
          createEditor();
          );

          else
          createEditor();

          );

          function createEditor()
          StackExchange.prepareEditor(
          heartbeatType: 'answer',
          convertImagesToLinks: false,
          noModals: false,
          showLowRepImageUploadWarning: true,
          reputationToPostImages: null,
          bindNavPrevention: true,
          postfix: "",
          onDemand: true,
          discardSelector: ".discard-answer"
          ,immediatelyShowMarkdownHelp:true
          );



          );






          ncryptn00b is a new contributor. Be nice, and check out our Code of Conduct.









           

          draft saved


          draft discarded


















          StackExchange.ready(
          function ()
          StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2funix.stackexchange.com%2fquestions%2f473763%2fstuck-in-a-30sec-boot-loop-after-grub-encrypted-volumes%23new-answer', 'question_page');

          );

          Post as a guest



































          active

          oldest

          votes













          active

          oldest

          votes









          active

          oldest

          votes






          active

          oldest

          votes








          ncryptn00b is a new contributor. Be nice, and check out our Code of Conduct.









           

          draft saved


          draft discarded


















          ncryptn00b is a new contributor. Be nice, and check out our Code of Conduct.












          ncryptn00b is a new contributor. Be nice, and check out our Code of Conduct.











          ncryptn00b is a new contributor. Be nice, and check out our Code of Conduct.













           


          draft saved


          draft discarded














          StackExchange.ready(
          function ()
          StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2funix.stackexchange.com%2fquestions%2f473763%2fstuck-in-a-30sec-boot-loop-after-grub-encrypted-volumes%23new-answer', 'question_page');

          );

          Post as a guest













































































          Popular posts from this blog

          How to check contact read email or not when send email to Individual?

          Bahrain

          Postfix configuration issue with fips on centos 7; mailgun relay