Solved

Upgraded 12.1 with previously installed ISO for Veeam Hardened Repository?



Show first post

45 comments

Userlevel 7
Badge +21

anyone else reading this, if you hit “esc” too many times and you end up at GRUB command prompt, type “normal” to get to the proper screen. :)

Thanks for that little tip.  That is what I was having at first before I figured out the hit ESC once.  LOL

Very cool to know typing “normal” gets you to the menu. 👍🏼

Userlevel 3

anyone else reading this, if you hit “esc” too many times and you end up at GRUB command prompt, type “normal” to get to the proper screen. :)

Userlevel 7
Badge +21

Nevermind.  Mashing “esc” brought it up.

Yes, that is what I posted before you found out.  LOL 😂

Userlevel 3

Nevermind.  Mashing “esc” brought it up.

Userlevel 7
Badge +21

Chris.Childerhose - I don’t see GRUB when I boot up.  It immediately goes to a blue screen that says “Hardened Repository”

I had this issue too.  If you are using VMware (VM) then open the console - hit the ESC key on boot to get a boot menu for the VM - select the option “ubuntu” in the list and once you do hit the ESC key just ONCE (don’t continually press it - this does not work). This will then get you the GRUB menu.

Userlevel 3

Chris.Childerhose - I don’t see GRUB when I boot up.  It immediately goes to a blue screen that says “Hardened Repository”

Userlevel 7
Badge +21

While it looks like you can do stuff with SSH, etc. you cannot.  You need to follow the instructions I noted to go in to Single-User mode in order to update the VHR otherwise you cannot do anything.  Otherwise, you might as well redeploy it with the ISO file again and overwrite stuff.

Userlevel 7
Badge +19

Hmm...ok. Well, if your acct can make changes, you can create a new account by:
useradd -m <name-of-user> ; then add it to sudo: adduser <new-username> sudo 

The thing is though, since your VHR is already “working” (minus the upgrade part), you should already have a single-cred user you’re using. Search the passwd file to see if there is a “veeam user” in it (cat /etc/passwd).

Userlevel 3

coolsport00 - sorry, I mistyped.  It was “systemctl start ssh”

Userlevel 7
Badge +19

You can’t create an account without the ability to do admin tasks, which is only done via root or an account with sudo rights. systemctrl status enable? Status is still only a ‘monitoring’ cmd. It doesn’t change anything. 

Userlevel 7
Badge +21

@kmcdermott -- You need to go in to Single-User mode for the VHR and turn on SSH.  Once you do that you can update the VHR via the console and then reboot to go back in to hardened mode.  I had to do this recently for an upgrade in my homelab - have one more VHR to do but understand the process now.  Here is an article for Single-User mode - Ubuntu Linux Defense: Secure Boot & Single User Mode (veeam.com)

Userlevel 3

Just for giggles, I ran “systemctl start ssh without the sudo and that worked.  Interesting.

New problem, I need to figure out how to create a single-use credential. 

Userlevel 7
Badge +19

You can run systemctrl status sshd to see if SSH is running. You don’t need to admin credentials to check the status as you’re not modifying anything.

Userlevel 7
Badge +19

@kmcdermott the account you’re logged in with wasn’t given sudo rights then. Do you know the root account login credentials?

Userlevel 3

I only have the one account that I created when I made the repo.

If I run “sudo systemctl start ssh”, I get back the error that the user is “not allow to execute as root”.

If I try to run “usermod -a -G sudo user” I get “permission denied”. “cannot lock /etc/passwd”

 

 

Userlevel 7
Badge +19

To make administrative changes, you need to add “sudo” at the beginning of the command you’re trying to run. If the account your logged in with is not in the sudo group on the server, then it won’t work. You need to either login as root or login with an account with sudo permissions.

Userlevel 7
Badge +19

I don’t think think it’s the SSH service that’s the issue, but the user you’re using for VHR needs sudo rights re-added temporarily. If the acct you’re using to login with doesn’t have the ability to make “administrative” changes on the Linux server, you need to login with one that does.

Userlevel 7
Badge +19

Or, re-add the VHR user to sudo. After upgrade, you can remove it. I had to remember what was needed. We had discussed this in a previous thread several mos ago. You can review the post & thread comments here.

Userlevel 3

It won’t let me; it says I’m not allowed to.  I’m assuming because its harderned.

 

Userlevel 7
Badge +19

I believe you need to temporarily re-enable SSH on the VHR @kmcdermott . Have you tried that yet?

Comment