After talking to a Dell technician, we discovered that the issue was related to the UEFI boot sequence (UEFI is essentially the new BIOS). Here are the instructions he sent me. Basically, the boot sequence should be changed to “Legacy” so that the boot sequence of the network, hard disk, CD / DVD drive can be changed to keep the network last. After that, the boot mode can be restored to UEFI Secure Boot On.
Hope this helps and you can fix it. ðŸ ™ ‚
I want to confirm if it is possible to connect to the machine via the network (NIC / LAN).
To work around the problem, I can suggest the following
(Choose boot order in old boot option):
1. Enter the one-time boot menu (F12)
2. Select “Change Boot Mode Settings” then select or “Secure Boot Legacy Boot”
3. Go to the one-time boot menu (F12) again and select “Enter Enter Setup”
4. Select Boot Tag and Legacy Boot should be selected.
5. Make sure the hard drive comes first. When a network appears, select it and select Disable.
Save Reconfigure and restart your computer.
6. When the problem is resolved, return to the EUFI Secure Boot Mode.
Show solution in original post
What if my computer starts normally with Windows?
After you have finished troubleshooting and the Windows operating system starts up normally on your computer, you should:
Run HP Assistant to update HP software and drivers.
Run Windows Update to update your operating system and software.
Run antivirus software to remove viruses.
First Try To Fix
We found the following links to the Azure documentation helpful:
- https://docs.microsoft.com/en-us/azure/virtual-machines/scripts/virtual-machines-linux-cli-sample-create-vm-from-snapshot?toc=/cli/module/ toc.json
Ok, step by step :
Submit a recovery virtual machine
What type of VM is it? I tried to create a default Ubuntu 18.04 LTS virtual machine. This is what you want – create a VM corresponding to the broken servers
Everything is fine, except that a connection is established to an existing hard drive. It looks like you won’t be able to connect to the hard drive unless you first move (disconnect) it from another computer.
Connect a copy of the hard disk of the virtual machine with the affected operating system to the backup virtual machine.
To make a copy, you can take a read-only snapshot of the disk and then create a new managed disk based on that snapshot.
The only hard drive you need a snapshot on is the operating system hard drive, not the data hard drive.
You can create a recovery virtual machine without a data disk, but only with an operating system disk, which will be created automatically.
Then you can add a snapshotto the operating system of the managed disk to the recovery virtual machine as a data disk.
Then you can connect to the recovery virtual machine and follow the steps above.
All steps went smoothly – we were able to copy and paste the exact messages
grub-install runs on a critical line. You should see:
root @ recoveryVM: / # grub-install / dev / sdcInstallation for PC platform i386.Installation completed. No bugs were reported.
Then log off and shut down the virtual machine.
You can then navigate to the failed virtual machine and select the Replace Operating System Disk option under the Hard Drives section of the virtual machine.
Mini Reddit thread explaining the required bindings: https://www.reddit.com/r/Ubuntu/comments/i0vlf0/repair_grub_boot_error_symbol_grub_calloc_not/