I’m running a HP ProLiant DL20 server with 2 960GB SSD setup for an LVM in RAID 1. After running through the standard install successfully, I’m unable to boot to the installed OS. I checked my boot settings and confirmed Secure Boot is off. I can’t even get to the point to install GRUB on the second drive. Has anyone had issues like this?
Did you install Debian 12 then ran the FreePBX 17 shell installer ? Or did you use the ISO ? How about UEFI ? ISO + UEFI should just work out of the box for this sort of scenario.
After the install of Debian 12 I couldn’t even get to reboot into Debian, it’s like the system doesn’t see the OS. I ran through the setup without choosing UEFI. I found if I chose UEFI it would fail to install GRUB.
How old is your motherboard ? Is there a newer BIOS available ?
All the Sangoma hardware I’ve seen from the past decade or more supports UEFI.
Latest update as this is a brand new HPE server we just purchased.
It’s possible the drives are flapping – lower level race between which is a or b (0 or 1, primary or secondary, however the words may be.) So the BIOS says one disk is a and the kernel says it is b. Occasionally some manual GRUB install may be required, e.g., run both grub-install /dev/sda and grub-install /dev/sdb.
How can I run that when I can’t get to booting to the OS?
You might be able to boot from the installation media and then choose Rescue Mode from the GRUB menu. It’s a little tedious though. But if you establish a pattern, then those additional GRUB steps could be part of your steps while running the installer – just before the reboot, running the manual grub-install stuff. (Because sometimes the installer chooses different a & b disks than the installed OS does at first reboot.)
I rebooted into the installation media and ran through the rescue mode. I manually ran those commands to install grub on /root for the lvm setup in raid. I rebooted but it still failed. Any other ideas?
Where did you put the /boot partition ? Inside the LVM ? That’s harder. Another approach is making separate /boot on each disk – outside of LVM – when you set it up, then relying on separate scripts to sync contents later. (This is part of the approach with the ISO in UEFI mode for RAID.) Can you try the ISO and see if it just works ?
I kept root inside of the LVM as the guide states. I tried to run through again with choosing to install with UEFI and made the EFI partition inside of the LVM. But then grub failed to install with the “executing grub install dummy failed debian 12” error. I tried to execute shell without skipping the install and it failed to find the command so I shut down and decided to update the post. Should I proceed without grub and manually install within rescue mode?
First, boot != root
The root partition / is fine in LVM on top of RAID. What to leave out of LVM to make things a lot easier is the boot partition /boot. In non-UEFI, you could put boot on RAID; but for UEFI, keeping boot separate and outside of both RAID and LVM is probably better.
Understood! So I’ve made a /boot partition outside of the LVM and RAID on each drive. Is it fine to keep EFI inside of the LVM/RAID or should I move that out as well?
No, move it.
EFI has to load before LVM/RAID.
BTW the ISO does this work – any reason why that was a no go for you ?
When you say the ISO, do you mean the one here? Debian -- Debian “bookworm” Installation Information under netinstall?
No, the FreePBX 17 ISO – based on Debian 12 ISO – introduced here freepbx.org/sngfd12
I’ve actually been running the manual way, let me give this a go. I’m sorry I didn’t quite grasp where you were going with the ISO previously. I’ll format a USB drive and give this a run.
1 Like
Update: ISO worked to install but now I can’t run fwconsole commands on CLI or change the root password. During setup, I chose to leave the sangoma password as default and change after. I was able to successfully change this, however, I can’t seem to run fwconsole or change the root password. Any ideas? I did choose the basic installation with the PUB option with UEFI enabled for the RAID 1.
EDIT:
I also noticed that the RAID 1 isn’t using all of my drive. Would I need to manually adjust this or can this be set using an advanced install?
If you issue
sudo su
and enter the new sangoma password, do you get a root shell prompt? If so, you should be able to do what you need from there.
I was able to set the root user password with sudo passwd root but now this doesn’t allow login.