Skip to main content
Solved

1-Touch Linux to Dell R730


Forum|alt.badge.img+1

I’m trying to do a 1-Touch restore to a Dell R730. I have an iso generated via create_1tchbootcd.sh. I then attached the iso via the attach media feature of the idrac for the server. It boots and gets to grub just fine. Immediately after grub is hangs on this message.

Trying to allocate 3315 pages for VMLINZ

[Linux-EFI, setup=0x10b4, size 0xcf2878]

 

Has anyone successfully booted a dell server via idrac virtual media with a 1-touch iso? Anyone know what might be going on here? The instructions say to use pxe but I’m trying to avoid that method.

Best answer by mfox

So the OS that was running on the host and being restored was UEFI? I assume so, since you created the ISO using the Single Stage method, but I certainly want to validate that the step was done for the correct reason.

The ISO you created and booted, was it generated using a -v n switch? if not, it would have defaulted to -v 1

…. what happens if you generate the Single Stage media again, this time use -v 2 option and then use that new media to boot. Is the condition the same? 

As Albert said, I recommend you do open a case should the alternative media suggested above still not boot.

 

Ref 1-Touch for Linux - Single Stage DVD (commvault.com)

View original
Did this answer your question?

6 replies

Forum|alt.badge.img+15

Hello @ThatGuyJ 

I have not run over those steps my self but i would recommend a support ticket to investiate this issue.

They will want to walk through your entire restore and backup process to make sure there are no reason for it to fail and a session is required to collect that kind of information. 

 

Kind regards

Albert Williams

 


Forum|alt.badge.img+5
  • Vaulter
  • 50 replies
  • Answer
  • August 20, 2024

So the OS that was running on the host and being restored was UEFI? I assume so, since you created the ISO using the Single Stage method, but I certainly want to validate that the step was done for the correct reason.

The ISO you created and booted, was it generated using a -v n switch? if not, it would have defaulted to -v 1

…. what happens if you generate the Single Stage media again, this time use -v 2 option and then use that new media to boot. Is the condition the same? 

As Albert said, I recommend you do open a case should the alternative media suggested above still not boot.

 

Ref 1-Touch for Linux - Single Stage DVD (commvault.com)


Forum|alt.badge.img+1
  • Author
  • Bit
  • 3 replies
  • August 21, 2024

Thank you both. Yes, the original host was UEFI. I tried the iso generation with “-v 2”. That generated iso does boot so now I’m in the 1-touch gui and working through the settings.

So to anybody else that is stumbling across this with similar issues, note the additional command flags above. I’ll chime back in with any other issues or important details that I encounter.


Forum|alt.badge.img+5
  • Vaulter
  • 50 replies
  • August 22, 2024
ThatGuyJ wrote:

Thank you both. Yes, the original host was UEFI. I tried the iso generation with “-v 2”. That generated iso does boot so now I’m in the 1-touch gui and working through the settings.

So to anybody else that is stumbling across this with similar issues, note the additional command flags above. I’ll chime back in with any other issues or important details that I encounter.

Great, by all means try the media defaulted to -v 1 during creation, but if it has problems, always try generating the -v 2 version to confirm it will address it. Seems to typically address it.


Forum|alt.badge.img+1
  • Author
  • Bit
  • 3 replies
  • August 23, 2024

Update: Ended up working with a commvault engineer since I still had issues doing the restore once booted into the iso. Here are some other issues I encountered. I was using my account to start the restore job, but we had 2fa turned on which was causing issues due to the pin being replaced before it was used for authentication. I didn’t have enough ports open in our firewall for Linux 1-touch. The doc linked above says you need 8111 and 8112, but the engineer said we needed 8114 as well, so we had to set up a 1-touch group and network config to use an alternate port that was already open. Due to the multiple failed restore attempts there was a _recovery entry in commvault that needed to be removed. I think I also had a setting or two in the interactive config that was slightly off. The interactive process is a bit clunky but I wanted to do it that way the first time so I better understand what is going on and what it takes to make it happen. Next time I’ll definitely let the system generate an xml. Hopefully this info helps someone...or myself when I forget all of this and find my own post about issues I’ve previously encountered.


Forum|alt.badge.img+15

Thanks for the update, really appreciate it when the story finish's. sometimes threads are just left open ended. Will help customers in the future!


Cookie policy

We use cookies to enhance and personalize your experience. If you accept you agree to our full cookie policy. Learn more about our cookies.

 
Cookie settings