vicidial.org

Hi,

Been trying to install Vicidial on a blade server but keep having issues. The same Installer I download from the website works for Desktops or VMs but it keeps failing with this server.

Server specs:
Manufacturer: HP
Model: Proliant DL380 Gen 9
Processor Type: Intel® Xeon® CPU E5-2670 v3 @ 2.30Ghz
CPU Cores: 24 CPUs x 2.297GHz
Memory: 256GB DDR4
Storage: 2 x 200GB SSD
10 x 1TB HDD 7.2K RPM

It keeps booting emergency mode.



I tried running journalctl but not really sure what to look for. I posted a couple of screenshots. Any ideas or if someone can point me into the right direction, that would be great.

PS, do advise if there's more info I can send you.

Cheers,
Jet

Is this a new server? (Nice specs on it)

Did you create the raid array in the bios?

Installing with USB or CD?

Emergency mode usually indicates a hardware error. Test those you can. Take out those for which you have spares (like: Take out half the memory and hard drives if there are extras). Try to replace components until you get lucky. Remember this is just to find a dead component and you may end up re-installing once you find the dead item.

I don't know why it won't boot. We've had issues historically with HP servers just not installing correctly. It usually comes down to the RAID card they use.

In this case it looks like the USB key is not being found. How did you burn the ISO onto the USB Key? If you used something like unetbootin or something that attempts to modify an ISO and write it to a USB then that is likely your issue. The ISO is already USB enabled and just need to be written to the thumb drive.

I recommend using ImageUSB. You can download it here : https://www.osforensics.com/downloads/imageusb.zip

Just extract the zip file to a folder, then run ImageUSB. Once it opens up it should be pretty self explanatory.

Kumba wrote:It usually comes down to the RAID card they use.

Now that you mention it ... yep. In our case, though it wasn't always so much "which card" (although sometimes) as "where the boot sector was written". The OS would install, but then the BIOS couldn't find the boot list. We've even had this with non-RAID occasionally when an older OS was being installed over a previous partition from a later .iso, and just deleting the partitions properly with a newer .iso would often resolve the issue. If not, of course, just pop in a new HD and we're off to the races.