# Access console not possible because root acccount is locked **URL:** \ **Category:** Support and Troubleshooting\ **Created:** [August 6, 2024, 4:21am UTC](https://community.umbrel.com/t/access-console-not-possible-because-root-acccount-is-locked/18689 "2024-08-06T04:21:31Z")\ **Posts on this page:** 3\ **Page:** 1
**Author:** ![cryptopath](https://yyz2.discourse-cdn.com/flex030/user_avatar/community.umbrel.com/cryptopath/32/5026_2.png) [@cryptopath](https://community.umbrel.com/u/cryptopath)\ **Post date:** [August 6, 2024, 4:21am UTC](https://community.umbrel.com/t/access-console-not-possible-because-root-acccount-is-locked/18689/1 "2024-08-06T04:21:31Z")
Cannot open access to console, the root account is locked??? I am putting the is on my mini pc? ---
**Author:** ![TCalache](https://avatars.discourse-cdn.com/v4/letter/t/df705f/32.png) [@TCalache](https://community.umbrel.com/u/TCalache)\ **Post date:** [August 16, 2024, 11:36am UTC](https://community.umbrel.com/t/access-console-not-possible-because-root-acccount-is-locked/18689/2 "2024-08-16T11:36:57Z")
I have the same error. And show "You are in emergency mode. After logging in, type “jounalctl -xb”… ---
**Author:** ![jfpoub](https://avatars.discourse-cdn.com/v4/letter/j/5f8ce5/32.png) [@jfpoub](https://community.umbrel.com/u/jfpoub)\ **Post date:** [January 4, 2026, 7:59pm UTC](https://community.umbrel.com/t/access-console-not-possible-because-root-acccount-is-locked/18689/3 "2026-01-04T19:59:15Z")
2 ways to resolv it : If your are on a PC : Boot on a live usb (for example Ubuntu), mount from it the /dev/sdaX of your Umbrel where /data resides and correct the bad /etc/fstab If you are inside a Umbrel VM (virtual machine) : if your first unbootable UmbrelOS (sda) is in a VM, stop the VM, add a disk of 32GB, install the iso of UmbrelOS (1.5 now) on the second disk not the first unbootable one (in order to keep the blockchain). Until the new UmbrelOS is installed on the second disk (sdb). Mount the /dev/sda3 (/data) of the first unbootable disk Change/correct the bad /etc/fstab Stop the VM Delete the new disk and verify if the first one is now booting after correcting its bad /etc/fstab