[Yandex Cloud documentation](../../../index.md) > [Yandex BareMetal](../../index.md) > [Step-by-step guides](../index.md) > Servers > Resetting a password on the server # Resetting the server root password The system automatically generates a root password during BareMetal server [provisioning](server-lease.md). 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. {% note tip %} To paste clipboard text to the KVM console, use the **Paste text here** field in the upper right corner. {% endnote %} {% list tabs %} - If you still have SSH key 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: 1. Connect to the server over SSH: ```bash ssh root@ ``` 1. To change the root password on the BareMetal server OS, run this command: ```bash passwd root ``` At the system prompt, enter and confirm the new password: ```bash New password: Retype new password: ``` Result: ```text passwd: password updated successfully ``` {% note info %} At this stage, you can also [add](add-new-ssh-key.md) a new SSH key, modify other server OS settings to ensure proper booting and network connectivity, and diagnose and troubleshoot errors. {% endnote %} - If you do not have access to the server 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](server-kvm.md). To reset the root password or change other BareMetal server settings: 1. [Start](rescue-boot.md#boot-up) 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. 1. View information about server storage devices, including disks and their partitions: ```bash fdisk -l ``` Result: ```text 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. 1. Mount the partition with the BareMetal server OS root filesystem: ```bash mount /dev/md125 /mnt ``` 1. Create a new SystemRescue shell environment using the server OS’s previously mounted BareMetal filesystem: ```bash chroot /mnt /bin/bash ``` 1. To change the root password on the BareMetal server OS, run this command: ```bash passwd root ``` At the system prompt, enter and confirm the new password: ```bash New password: Retype new password: ``` Result: ```text passwd: password updated successfully ``` {% note info %} At this stage, you can also [add](add-new-ssh-key.md) a new SSH key, modify other server OS settings to ensure proper booting and network connectivity, and diagnose and troubleshoot errors. {% endnote %} 1. After completing all required operations in the server’s filesystem, exit the recovery environment. ```bash exit ``` 1. Unmount the BareMetal server filesystem: ```bash umount /dev/md125 /mnt ``` Result: ```text umount: /mnt: not mounted. ``` 1. 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. 1. In the window that opens, click **Disconnect** under **CD/DVD Media1**. 1. Click **Close**. 1. Restart the server: ```bash reboot ``` {% endlist %} #### See also {#see-also} * [Using the Rescue CD diagnostics and recovery tools](rescue-boot.md) * [Adding a new SSH key for a user](add-new-ssh-key.md) * [Restoring the OS bootloader](restore-grub.md) * [Replacing a disk in a RAID array](switch-raid-member.md)