0

I've got a new Supermicro SYS-1029U-TN12RV box with Intel VROC. Trying to install Ubuntu 20 LTS via a USB key. The distro I found is

https://releases.ubuntu.com/20.04.6/ubuntu-20.04.6-live-server-amd64.iso

but this installer doesn't see the VROC volumes, just the underlying disks.

There's a lot of past information about a separate HWE kernel/distro for this, e.g.,

Ubuntu 18.04.2 Server + Intel VROC Array on a Dell 7920

but I can't find a different distro for 20.

Help?

Improve this question
6
  • There is no Ubuntu 20 LTS or a version 20. Accurate info in your question is a must.
    – David
    Apr 6, 2023 at 16:56
  • I'm sorry if the several mentions of 20.04.6, including the download URL I used, weren't enough to avoid confusion. So let me try again: I'd like to install an LTS version of Ubuntu 20.04 server onto a VROC filesystem. The download link that is prominent on the Ubuntu site does not work for that - the installer doesn't see the VROC devices, just the underlying storage. Is there another installer that I can use, or some setting that I have missed? Thanks.
    – Chris Kantarjiev
    Apr 8, 2023 at 1:43
  • Did you try the legacy 20.04 server installer? This is suggested at support.hpe.com/hpesc/public/… . The legacy server installer is available at cdimage.ubuntu.com/ubuntu-legacy-server/releases/20.04/release . I believe the legacy server was discontinued after the 20.04.1 release and is not available for any newer releases.
    – Andrew Lowther
    Apr 10, 2023 at 22:17
  • Not yet. I tried the 18.04.2 legacy installer, based on information from the comment above, figuring I could upgrade in place. I was able to boot with an HWE kernel, yay. The installer noticed the VROC/md devices and asked if I wanted to activate them, yay. But they did not show up as devices that I could choose to install onto, boo.
    – Chris Kantarjiev
    Apr 12, 2023 at 2:09
  • This isn't really a solution, but a datapoint: I shoved a drive into a spare slot and installed there and booted. The VROC/md devices were ... sort of there. mdadm complained mdadm: No OROM/EFI properties for /dev/nvme2n1 and some googling around for that message led me to askubuntu.com/questions/1239082/… which actually helped - mdadm was able to assemble the devices and resync ... that they needed to resync makes me think that somehow the BIOS tool didn't really build them correctly in the first place. That's as far as I've gotten.
    – Chris Kantarjiev
    Apr 12, 2023 at 2:15

0

Reset to default

You must log in to answer this question.

Browse other questions tagged .