# Problem with Azure serial console and root password

**URL:** <https://community.ipfire.org/t/problem-with-azure-serial-console-and-root-password/7063>\
**Category:** In The Cloud & Virtualized\
**Created:** [19 January 2022 19:48 UTC](https://community.ipfire.org/t/problem-with-azure-serial-console-and-root-password/7063 "2022-01-19T19:48:47Z")\
**Posts on this page:** 4\
**Page:** 1

<div class="post-metadata">

**Author:** ![mapstaeol](https://community.ipfire.org/user_avatar/community.ipfire.org/mapstaeol/32/8231_2.png) [@mapstaeol](https://community.ipfire.org/u/mapstaeol)\
**Post date:** [19 January 2022 19:48 UTC](https://community.ipfire.org/t/problem-with-azure-serial-console-and-root-password/7063/1 "2022-01-19T19:48:47Z")

</div>

Hi all,

I am trying to create a simple RED+GREEN firewall in Azure for labs.  
I successfully did long time ago with 2.23.x86\_64-full-core133, but now it seems impossible to get root access over serial console.  
I tried both the one that worked for me in the past (2.23) and latest 2.27, same result.

These are the steps I’m using:

- Create Hyper-V VM.
- Add line at the end of /etc/inittab for ttyS0, so Azure Serial Console connects fine. I didn’t need to do this step in the past.
- Upload VHD to storage account.
- Create a managed disk out of the VHD.
- Create a VM from the managed disk.

I can connect to the green interface from another VM and configure firewall.  
The problem is that when trying to log through serial console, the password for root is not accepted anymore, and returns “login incorrect”.

The same behavior occurs creating the VM with an unmanaged disk from the blob storage.

Any ideas?

---

<div class="post-metadata">

**Author:** ![mapstaeol](https://community.ipfire.org/user_avatar/community.ipfire.org/mapstaeol/32/8231_2.png) [@mapstaeol](https://community.ipfire.org/u/mapstaeol)\
**Post date:** [19 January 2022 20:45 UTC](https://community.ipfire.org/t/problem-with-azure-serial-console-and-root-password/7063/2 "2022-01-19T20:45:06Z")

</div>

Solved!  
I also had to add ttyS0 to /etc/securetty

Thanks!

---

<div class="post-metadata">

**Author:** ![arne\_f](https://community.ipfire.org/user_avatar/community.ipfire.org/arne_f/32/12760_2.png) [@arne\_f](https://community.ipfire.org/u/arne_f)\
**Post date:** [20 January 2022 08:10 UTC](https://community.ipfire.org/t/problem-with-azure-serial-console-and-root-password/7063/3 "2022-01-20T08:10:46Z")

</div>

Strange? Normal ttyS0 should be already in /etc/securetty in the IPFire image.

[https://git.ipfire.org/?p=ipfire-2.x.git;a=blob;f=config/etc/securetty;h=9a6a9fd30e841539a99fb191d3fa9b44f7ed5c26](https://git.ipfire.org/?p=ipfire-2.x.git;a=blob;f=config/etc/securetty;h=9a6a9fd30e841539a99fb191d3fa9b44f7ed5c26)

> [@mapstaeol](#):
>
> Add line at the end of /etc/inittab for ttyS0, so Azure Serial Console connects fine. I didn’t need to do this step in the past.

If you add console=ttyS0,[baudrate-config] to kernel cmdline at first boot this should auto added to all needed files. (grub,getty usw.)

---

<div class="post-metadata">

**Author:** ![mapstaeol](https://community.ipfire.org/user_avatar/community.ipfire.org/mapstaeol/32/8231_2.png) [@mapstaeol](https://community.ipfire.org/u/mapstaeol)\
**Post date:** [21 January 2022 15:56 UTC](https://community.ipfire.org/t/problem-with-azure-serial-console-and-root-password/7063/4 "2022-01-21T15:56:32Z")

</div>

For some reason, at least installing in Hyper-V in Windows 10 21H1 (build 1466), the console=ttyS0,115200 switch freezes the boot into black screen.  
Booting without any switch works fine and setup finishes, but /etc/securetty contains:  
 ![image](https://community.ipfire.org/uploads/default/original/2X/f/f4f596a9eb7a0b41e5738a9cfe8a7aaa3def9ddc.png)

PS: I was mostly needing serial console to reassign NICs when booting in Azure, but now IPFire is doing a great job configuring NICs in Azure, so not really needed unless for emergency access (i.e. locked out SSH/Web access).