Fatal error and ilo (nand) issues

[metsven]

Hi,

I am new to servers and IT in general. For a project I bought a dl380p g8 from an auction site. After initial start up, I decided to update firmware, also bios and updated the P420i card to hba mode. All went well. I installed a sata ssd (boot ubuntu) and nvme (m2 to pcie adapter) as extra storage, along side the 4x 1.2tb sas drives.

After this was all done, I restarted and booted to an usb with ubuntu. I got that installed. But I can't reboot to it.

After a few atempts of restarting and making sure the ssd was selected as drive, the issues started with embedded flash/sd card, nand read failure. I found a solution, which first worked.

I took out the ssd and nvme and retried to install ubuntu on one of the sas drives. And this time I did try to setup a logical drive (forgot that the first time). I selected 1 drive in raid 0, but got fatal error message after pressing F8. Second attempt was all 4 drives in raid 0, same issue.

So, now I have this fatal error when trying to setup the logical drive and the embedded flash/sd card nand error is back too. But the nand error message is sometimes different.

I called the local HPE support center, but the device is out of warrantry. What can I do to resolve the issues? Or does it need a new MB, like it is mentioned in the product support manual?

Thanks in advance for all the help/support!

Sven

[support_s]

System recommended content:

1. Advisory: (Revision) HPE Integrated Lights-Out 4 (iLO 4) - HPE Active Health System (AHS) Logs and HPE OneView Profiles May Be Unavailable Causing iLO Self-Test Error 8192, Embedded Media Manager and Other Errors

Please click on "Thumbs Up/Kudo" icon to give a "Kudo".

Thank you for being a HPE valuable community member.

[metsven]

Hi,

Thank you for that reply with link. Those steps I already have taken and was succesfull the first time. But now it seems it isn't working anymore after taking the step in the provided link.

Plus I am not sure that my second problem with the fatal error is linked to the nand issue.

Bye,

Sven

[Sham82]

Hello, 

Since you have already Followed the Document.

Still i would recommend to please try below step once again.

> Schedule downtime; AC power-cycle and repeat the NAND format.

If the issue reoccurs, you might have to go for system board replacement.

Regards
HPE

[metsven]

Thank you all for responding. Unfortunately the nand issue continues. So, it looks like I have to replace the MB.

Any thoughts on the second issue with the configuration, fatal error, while trying to setup the logical drive(s).

I tried 1 drive in raid 0 and also all drives in raid 0. And each time I got that error.

[pchops]

What is the fatal error that you are seeing? In your original post, you had stated:

... updated the P420i card to hba mode ...

When the P420i is set to HBA mode, the RAID functions are disabled and all drives are accessible directly from the host OS. If you set the P420i to HBA mode, you should be seeing a message like this during POST:

If you then try to configure a RAID volume using the ORCA (Option ROM Configuration for Arrays) utility (using F8 during POST), you will see a fatal error similar to:

This is expected when the P420i is in HBA mode. In other words, no hardware RAID configuation is possible, or even necessary -- the host OS should be able to directly access any drives connected to a P420i in HBA mode (unless there is a driver, or some other, issue).

[metsven]

Thank you for your reply. Which was very helpfull. But why was it then, when I installed ubuntu, that I couldn't have the server boot automatically to the drive which had the os installed on it. What am I overlooking?

[pchops]

There are a lot of possible reasons -- some that come to mind are:

• BIOS settings for "Standard Boot Order (IPL)" and/or "Boot Controller Order"
• possible differences between the way Ubuntu enumerates the target drive and the way the BIOS does
• boot loader (presumably GRUB) written to the wrong/different drive

What happens after the Ubuntu install completes and you reboot? Does it go straight to "Attempting Boot From NIC"?

[metsven]

Hi,

After installation and reboot, it goes to Attempting Boot From NIC and Attempting Boot From cd-rom. I did set the boot sequence to start with hdd

[pchops]

Can you get it to boot from the target drive by using the Boot Override Menu (F11 during POST) and selecting "One Time Boot to HDD"?

If not, I would boot the Ubuntu USB key again and see how it is enumerating the drives (ie, the SATA SSD versus the SAS drives, USB key, etc).

Also, what device did you specify (or which one did Ubuntu offer as a default) for the boot loader installation?

[metsven]

@pchops 

I have tried to press F11 and select "One Time Boot to HDD". But didn't work.

First I had it installed on a nvme, but found out you can't boot to that.

So, I added a sata ssd and installed the OS on there. Also didn't work.

Lastly, I tried to just install it onto one of the sas drives that came with the server and made sure the bootloader was installed onto that drive. But again, didn't want to boot from that drive.

[Sham82]

Hello, 

To Further assist you with you query.
we would request you to log a case with HPE support.

Regards
HPE

[metsven · Accepted solution]

Hi,

Thank you for the message. About the nand issue, it just continues. Which tells me, from the hpe support article about the issue, that I have to replace the motherboard. If I want to have it fixed. The other problem has been resolved by one of the responders. I was eventually able to install proxmox (I couldn't get ubuntu to boot from usb after installation).

Because the server is out of warranty, I decided to run it as is at the moment. Untill I find a motherboard replacement.

Thank you all for your support. With this I leave it as resolved.