| 2019-12-29 01:48:58 |
Surfrock66 |
description |
I am attempting to install Ubuntu Server on a Dell Poweredge R710 server. There is a single RAID-5 volume group. This is a similar hardware configuration to other servers I have successfully deployed (with older releases, all are LTS). I am booting into Legacy mode, not UEFI.
I have downloaded the latest Ubuntu Server 19.10 installer as of 12/22/2019. When installing the OS using the default options in the GUI, the install completes "successfully" but immediately boots to GRUB rescue. When going through the installer choosing to update the installer as prompted, again the system boots to GRUB rescue. All partitioning is done accepting the defaults.
If I download the most up to date Ubuntu 18.04.3 LTS installer, the system installs and boots fine. Packages update and everything is peachy. If I upgrade to the latest release using do-release-upgrade, the upgrade "completes" successfully, but then immediately boots to GRUB rescue.
I can boot into a live environment and chroot into the system and it works fine. My installs, in testing, accept all defaults especially in terms of those related to partitioning.
I am not very experienced working in GRUB, so everything after this comes from these guides:
https://askubuntu.com/questions/232215/stuck-in-grub-rescue-mode
https://www.howtoforge.com/tutorial/repair-linux-boot-with-grub-rescue/
https://help.ubuntu.com/community/Grub2/Troubleshooting
When I ls, I get the following:
(hd0) (hd0,gpt2) (hd0,gpt1)
If I do "ls (hd0,gpt2)/" I get the contents of my root file system. Inside here, /boot and /boot/grub appear fully populated.
If I do "ls (hd0,gpt1)/" I get "Error, unknown file system".
When I do "set" I see the following relevant entries:
prefix=(hd0,gpt2)/boot/grub
root=hd0,gpt2
These appear to be correct. If I do the following, I can get the system to boot to initramfs prompt:
insmod normal
normal
insmod linux
linux /vmlinuz root=/dev/sda1 ro
initrd /initrd.img
boot
I have verified that the vmlinuz and initrd.img are there.
At this point as far as I can tell, something in the default configuration of Ubuntu Server 19.10 renders the OS un-bootable through GRUB. |
I am attempting to install Ubuntu Server on a Dell Poweredge R710 server. There is a single RAID-5 volume group. This is a similar hardware configuration to other servers I have successfully deployed (with older releases, all are LTS). I am booting into Legacy mode, not UEFI.
I have downloaded the latest Ubuntu Server 19.10 installer as of 12/22/2019. When installing the OS using the default options in the GUI, the install completes "successfully" but immediately boots to GRUB rescue. When going through the installer choosing to update the installer as prompted, again the system boots to GRUB rescue. All partitioning is done accepting the defaults.
If I download the most up to date Ubuntu 18.04.3 LTS installer, the system installs and boots fine. Packages update and everything is peachy. If I upgrade to the latest release using do-release-upgrade, the upgrade "completes" successfully, but then immediately boots to GRUB rescue.
I can boot into a live environment and chroot into the system and it works fine. My installs, in testing, accept all defaults especially in terms of those related to partitioning.
I am not very experienced working in GRUB, so everything after this comes from these guides:
https://askubuntu.com/questions/232215/stuck-in-grub-rescue-mode
https://www.howtoforge.com/tutorial/repair-linux-boot-with-grub-rescue/
https://help.ubuntu.com/community/Grub2/Troubleshooting
When I ls, I get the following:
(hd0) (hd0,gpt2) (hd0,gpt1)
If I do "ls (hd0,gpt2)/" I get the contents of my root file system. Inside here, /boot and /boot/grub appear fully populated.
If I do "ls (hd0,gpt1)/" I get "Error, unknown file system".
When I do "set" I see the following relevant entries:
prefix=(hd0,gpt2)/boot/grub
root=hd0,gpt2
These appear to be correct. If I do the following, I can get the system to boot to initramfs prompt but not the actual system:
insmod normal
normal
insmod linux
linux /vmlinuz root=/dev/sda1 ro
initrd /initrd.img
boot
I have verified that the vmlinuz and initrd.img are there.
At this point as far as I can tell, something in the default configuration of Ubuntu Server 19.10 renders the OS un-bootable through GRUB. |
|
