By Mark Belanger
I'm new to the HPMSG8 world and so far I'm loving it. I have a stock Xeon with 16G of aftermarket memory with iLO patched to 2.70. Next up is adding a RAID card, so I can put my boot SSD on the onboard RAID. I picked up a LSI SAS9211-8i on Amazon, but am struggling to flash it to IT mode on the MicroServer. Is this even possible? Unfortunately, the only other system I have with PCI slots is 32-bit.
Any pointers would be greatly appreciated.
FYI, I have just installed Windows Server 2019 Standard (Desktop Experience) using the latest (WS2016) HP AMD chipset & VGA driver. Everything is recognised in Device Manager and stable.
I need to update the firmware on a HP Proliant Microserver Remote Access Card installed in my N40L.
Can someone please explain what I need to do to create a boot device that will update the firmware on the Remote Access Card?
I installed a BU50N Blu-ray 4K drive in my HPE ProLiant Gen8 MicroServer. Worked out well, I'm using PowerDVD13 -- I had to restart the "Machine" several times before it saw the ODD but "Machine" finally figured it out.
I hope this topic fits here just right.
So a few days ago, I moved my Microserver Gen8 to a friend's place and resetted it.
When we set it up with new disks, the raid-creation in OpenMediaVault (Debian 9.6) failed.
`smartctl` tests passed just fine though and vendor-tools also didn't report any drive errors.
- I start the Raid creation via `mdadm` and after a while (random blocks and times), it fails and the second disk seems to fail (e.g. sda and sdb are creating a raid, then sdb gets "kicked out" and reread as e.g. sdd, sometimes even with only a few GB of space instead of 3TB).
I tried attaching the second disk on ata2 and ata3, but it keeps failing. The one on ata1 works just fine though.
I tried different disks and vendors, but get the same results.
There are some errors in `dmesg`, but I don't know what they mean. I pasted them here: https://pastebin.com/raw/XASQJ6cy
What I did here: I stopped the raid to re-create it, but then didn't do anything for a while and the error still came up.
Can someone help me with this? (As a wild guess, I'd say that somethings wrong with the SATA connections at least on ata2 and ata3).
Thanks in advance