# Cannot boot /dev/mapper/rl-root does not exist **URL:** \ **Category:** Rocky Linux Help & Support\ **Created:** [October 7, 2024, 12:25pm UTC](https://forums.rockylinux.org/t/cannot-boot-dev-mapper-rl-root-does-not-exist/16097 "2024-10-07T12:25:33Z")\ **Posts on this page:** 8\ **Page:** 1
**Author:** ![netadmin](https://avatars.discourse-cdn.com/v4/letter/n/eada6e/32.png) [@netadmin](https://forums.rockylinux.org/u/netadmin)\ **Post date:** [October 7, 2024, 12:25pm UTC](https://forums.rockylinux.org/t/cannot-boot-dev-mapper-rl-root-does-not-exist/16097/1 "2024-10-07T12:25:33Z")
![image](https://us1.discourse-cdn.com/flex020/uploads/rockylinux/original/2X/f/fed91be3afb21d5da955504e6e1a2f81501d08c9.png) ---
**Author:** ![jlehtone](https://avatars.discourse-cdn.com/v4/letter/j/e9a140/32.png) [@jlehtone](https://forums.rockylinux.org/u/jlehtone)\ **Post date:** [October 7, 2024, 12:55pm UTC](https://forums.rockylinux.org/t/cannot-boot-dev-mapper-rl-root-does-not-exist/16097/2 "2024-10-07T12:55:06Z")
The kernel does attempt – according to instructions in initramfs – mount filesystem from LV “root” that is within VG “rl”. Looks like the LVM2 VG (and LVs within) have not been initialized. All of this is just resulting symptoms, not the initial error. Does the `/run/initramfs/rdsosreport.txt’ have the _first signs_ of failure? ---
**Author:** ![netadmin](https://avatars.discourse-cdn.com/v4/letter/n/eada6e/32.png) [@netadmin](https://forums.rockylinux.org/u/netadmin)\ **Post date:** [October 7, 2024, 1:28pm UTC](https://forums.rockylinux.org/t/cannot-boot-dev-mapper-rl-root-does-not-exist/16097/3 "2024-10-07T13:28:05Z")
![image](https://us1.discourse-cdn.com/flex020/uploads/rockylinux/original/2X/e/e4458d716e885d848aeed129b9b549ae89ef7831.png) Actually it started as per the above and then i removed the secure boot from the vm advanced options and started not loading at all. ---
**Author:** ![netadmin](https://avatars.discourse-cdn.com/v4/letter/n/eada6e/32.png) [@netadmin](https://forums.rockylinux.org/u/netadmin)\ **Post date:** [October 7, 2024, 1:28pm UTC](https://forums.rockylinux.org/t/cannot-boot-dev-mapper-rl-root-does-not-exist/16097/4 "2024-10-07T13:28:35Z")
![image](https://us1.discourse-cdn.com/flex020/uploads/rockylinux/original/2X/4/44f0958685e43f6171db2861fe322eccbe4fdf22.png) ---
**Author:** ![gerry666uk](https://avatars.discourse-cdn.com/v4/letter/g/dbc845/32.png) [@gerry666uk](https://forums.rockylinux.org/u/gerry666uk)\ **Post date:** [October 7, 2024, 6:46pm UTC](https://forums.rockylinux.org/t/cannot-boot-dev-mapper-rl-root-does-not-exist/16097/5 "2024-10-07T18:46:50Z")
> [@netadmin](#): > > i removed the secure boot from the vm advanced options Can you clarify the exact versions of the host, and the vm? The SBAT message, did you see this on the host or the guest? ---
**Author:** ![netadmin](https://avatars.discourse-cdn.com/v4/letter/n/eada6e/32.png) [@netadmin](https://forums.rockylinux.org/u/netadmin)\ **Post date:** [October 8, 2024, 2:55am UTC](https://forums.rockylinux.org/t/cannot-boot-dev-mapper-rl-root-does-not-exist/16097/6 "2024-10-08T02:55:07Z")
Yes sure … Host → VMware ESXi, 8.0.1, 21813344 VM → Rocky 8.7 The SBAT message appears on the guest. ---
**Author:** ![gerry666uk](https://avatars.discourse-cdn.com/v4/letter/g/dbc845/32.png) [@gerry666uk](https://forums.rockylinux.org/u/gerry666uk)\ **Post date:** [October 8, 2024, 6:56pm UTC](https://forums.rockylinux.org/t/cannot-boot-dev-mapper-rl-root-does-not-exist/16097/7 "2024-10-08T18:56:03Z")
Regarding where it says Rocky 8.7, it sounds a bit behind, did it have the Apr 2024 updates applied, new shim etc. If not, it could cause the SBAT failure. ---
**Author:** ![system](https://us1.discourse-cdn.com/flex020/uploads/rockylinux/original/1X/91b7219eec10e30013422e4df76c1d898711a5d5.svg) [@system](https://forums.rockylinux.org/u/system)\ **Post date:** [December 7, 2024, 6:56pm UTC](https://forums.rockylinux.org/t/cannot-boot-dev-mapper-rl-root-does-not-exist/16097/8 "2024-12-07T18:56:06Z")
This topic was automatically closed 60 days after the last reply. New replies are no longer allowed.