Installing Root Lock by HeartSuite – Part 1
Overview: After running the install command, the machine reboots into the Root Lock by HeartSuite kernel.
Cloud users skip this step entirely. The Root Lock by HeartSuite kernel is pre-installed and on first boot the Dashboard confirms Phase 1 is complete. The Dashboard appears automatically on first boot.
Reboot into the Root Lock by HeartSuite kernel
The installer sets the Root Lock by HeartSuite kernel as the default boot target and reboots automatically. A 5-second countdown appears — press Ctrl+C to cancel if you need to inspect logs before rebooting.
After reboot, Root Lock by HeartSuite reads the startup and shutdown logs and adds those programs to the allowlist automatically. Continue with Installation Part 2.
If you are connected over SSH, your session drops when the reboot fires — this is expected. Reconnect after the system comes back. While setup is running, each SSH login shows a brief status line and drops you at a regular shell; the Dashboard appears once setup is complete. The serial console (virsh console, AWS/Azure/GCP serial console, IPMI SOL) shows the current setup step on every boot.
If an amber warning appears instead of the countdown, the installer could not set the GRUB default automatically. This occurs on Alpine Linux or when the GRUB configuration is missing. The warning includes instructions for opening a console session on your cloud provider (AWS, Azure, GCP, or DigitalOcean) or local VM before rebooting — then select the Root Lock by HeartSuite kernel from the GRUB menu manually.
If the system does not boot into HeartSuite
If the machine boots to the wrong kernel or hangs:
- Verify the installer completed without errors before the reboot fired.
- Reboot and select the Root Lock by HeartSuite kernel from the GRUB menu manually.
If the issue persists, contact HeartSuite support — we’re happy to help.
Feedback
Was this page helpful?
Glad to hear it! Please tell us how we can improve.
Sorry to hear that. Please tell us how we can improve.