# nodl stuck in unlock
Applies to:
nodl One (black, etched logo) with activated disk encryption and nodl Dojo (red, etched logo)
# Symptoms
After entering unlock password, your device stays on the "Device successfully unlocked, please wait for second stage" screen or goes back to the password input box.
# Cause
Sometimes, md
(the subsystem responsible for RAID) decides the device wasn't cleanly shut down and decides to go into read-only mode for safety. The file system might have also became inconsistent in the process.
Although nodl One doesn't have a second drive, it is RAID-ready so this can happen as well.
# Solution
First, ssh
into your nodl (opens new window) as rock.
After you're logged in, run the following commands:
sudo su -
to become permanently root.
service nodl-bootstrap stop
to stop the bootstrapping process.
cat /proc/mdstat
to check the status of the drives md0 and md1. If either or both of them in read-only
or auto-read-only
, run the following to force the drive(s) into readwrite
state:
mdadm --readwrite md0
mdadm --readwrite md1
Run cat /proc/mdstat
to verify that both drives are no longer in read-only
state and that it finished syncing. The output should look similar to the below:
Personalities : [raid1]
md1 : active raid1 sda3[0]
949273408 blocks super 1.2 [1/1] [U]
bitmap: 0/8 pages [0KB], 65536KB chunk
md0 : active raid1 sda1[0]
19479232 blocks super 1.2 [1/1] [U]
unused devices: <none>
Then unlock the encrypted partitions by running the following two commands and using the unlocking password:
cryptsetup open --type luks /dev/md0 root
cryptsetup open --type luks /dev/md1 opt
Then check the partitions for inconsistencies and auto-fix them by supplying the -y
argument to fsck
:
fsck -y /dev/mapper/root
fsck -y /dev/mapper/opt
Then start the bootstrapping process:
service nodl-bootstrap start
Now open the nodl's UI page and see if the issue went away!
If the issue isn’t solved, please contact support@nodl.it.