Resetting the server root password

Written by

Updated at July 7, 2025

The system automatically generates a root password during BareMetal server provisioning. You must save this password, as it will become inaccessible after server initialization.

If you have lost your BareMetal server root password, you can create a new one. The recovery method depends on your access level.

Tip

To paste clipboard text to the KVM console, use the Paste text here field in the upper right corner.

If you still have SSH key access to the server

If you do not have access to the server

If you still have root SSH access via the key specified during server setup, you can reset the root password without using Rescue CD:

Connect to the server over SSH:
```
ssh root@<server_public_IP_address>
```
To change the root password on the BareMetal server OS, run this command:
```
passwd root
```
At the system prompt, enter and confirm the new password:
```
New password:
Retype new password:
```
Result:
```
passwd: password updated successfully
```
Note

At this stage, you can also add a new SSH key, modify other server OS settings to ensure proper booting and network connectivity, and diagnose and troubleshoot errors.

If you do not have root SSH access to the server, reset the root password using the Rescue CD boot image: Proceed with the following steps in the KVM console.

To reset the root password or change other BareMetal server settings:

Start the server from the Rescue CD image.

In the main SystemRescue menu, select Boot SystemRescue using default options, press ENTER and wait for SystemRescue to load.

View information about server storage devices, including disks and their partitions:

fdisk -l

Result:

Disk /dev/sda: 838.36 GiB, 900185481216 bytes, 1758174768 sectors
Disk model: SAMSUNG MZ7GE900
Units: sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 512 bytes
I/0 size (minimum/optimal): 512 bytes / 512 bytes
Disklabel type: gpt
Disk identifier: D79F5407-DEEC-4A1D-983F-3AC5********

Device      Start      End         Sectors      Size  Type
/dev/sda1   2048       614399      612352       299M  BIOS boot
/dev/sda2   614400     21585919    20971520     10G   Linux filesystem
/dev/sda3   21585920   34168831    12582912     6G    Linux filesystem
/dev/sda4   34168832   1732861951  1698693120   810G  Linux filesystem


Disk /dev/sdb: 838.36 GiB, 900185481216 bytes, 1758174768 sectors
Disk model: SAMSUNG MZ7GE900
Units: sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 512 bytes
I/0 size (minimum/optimal): 512 bytes / 512 bytes
Disklabel type: gpt
Disk identifier: CDZACB4C-1618-4BAF-A6BB-D2B9********

Device      Start      End         Sectors      Size  Type
/dev/sdb1   2048       614399      612352       299M  BIOS boot
/dev/sdb2   614400     21585919    20971520     10G   Linux filesystem
/dev/sdb3   21585920   34168831    12582912     6G    Linux filesystem
/dev/sdb4   34168832   1732861951  1698693120   810G  Linux filesystem

Disk /dev/md127: 6 GiB, 6438256640 bytes, 12574720 sectors
Units: sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 512 bytes
I/0 size (minimum/optimal): 512 bytes / 512 bytes

Disk /dev/md126: 9.99 GiB, 10729029632 bytes, 20955136 sectors = 512 bytes
Units: sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 512 bytes
I/0 size (minimum/optimal): 512 bytes / 512 bytes

Disk /dev/md125: 809.88 GiB, 869596659712 bytes, 1698430976 sectors
Units: sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 512 bytes
I/0 size (minimum/optimal): 512 bytes / 512 bytes

Disk /dev/loop: 824.97 MiB, 865046528 bytes, 1689544 sectors
Units: sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 512 bytes
I/O size (minimum/optimal): 512 bytes / 512 bytes

In the example above, the fdisk utility displayed information about the /dev/sda and /dev/sdb physical disks, their partitions, and the partitions of the server’s RAID array: /dev/md127, /dev/md126, and /dev/md125.

The /dev/sda and /dev/sdb disks are configured in a RAID array, and the 809.88 GiB /dev/md125 partition contains the server OS root filesystem. This is the partition you need to mount.

Mount the partition with the BareMetal server OS root filesystem:
```
mount /dev/md125 /mnt
```
Create a new SystemRescue shell environment using the server OS’s previously mounted BareMetal filesystem:
```
chroot /mnt /bin/bash
```
To change the root password on the BareMetal server OS, run this command:
```
passwd root
```
At the system prompt, enter and confirm the new password:
```
New password:
Retype new password:
```
Result:
```
passwd: password updated successfully
```
Note

At this stage, you can also add a new SSH key, modify other server OS settings to ensure proper booting and network connectivity, and diagnose and troubleshoot errors.
After completing all required operations in the server’s filesystem, exit the recovery environment.
```
exit
```

Unmount the BareMetal server filesystem:

umount /dev/md125 /mnt

Result:

umount: /mnt: not mounted.

Disable the virtual CD drive in the KVM console:
1. Click the CD icon or select Media → Virtual Media Wizard... in the top menu of the KVM console window.
2. In the window that opens, click Disconnect under CD/DVD Media1.
3. Click Close.
Restart the server:
```
reboot
```

Resetting the server root password

See also

Was the article helpful?

Resetting the server root password

See alsoSee also

Was the article helpful?

See also