cbapel

Members
  • Posts

    7
  • Joined

  • Last visited

Recent Profile Visitors

The recent visitors block is disabled and is not being shown to other users.

cbapel's Achievements

Noob

Noob (1/14)

0

Reputation

  1. The management tool sas3flash is for SLI branded controller, the Broadcom hba use StorCLI, and none of the firmware releases have a non-bios version that I could use. Unfortunately, the storcli64 /c0 erase bootserivce failed to run because: unsupported erase option. i can only conclude this is because it's an HBA without a BIOS, but why does it try to load a BIOS at boot 😣. Seems my adventure isn't ending so soon. I will try to upgrade Proxmox to the new release, something I was planning on doing only after I got the HBA working.
  2. I'll keep looking for solutions on the virtualization part, maybe that is really where the trouble starts. It's configuring the "ignore" or "delete" part I'm hoping for. Given the information I've found so far, it doesn't appear that the HBA controller has much of a BIOS. I've found a new command in the StorCli manual that I'll try later, but otherwise I haven't yet found a way erase or disable just the BIOS on the Broadcom card; it seems for LSI the IT mode is a recurring solution. Cheers storcli /c0 erase bootservices
  3. Thanks, it's a good question, but I don't have an easy way to run Unraid baremetal, so do I don't know. Realizing this issue could be vm related I was considering posting this under the VM sub but decided to post where the other HBA related posts are.
  4. Unraid is running as a guest vm in Promox. I've swapped from the onboard controller to a Broadcom HBA 9400-16i, I've successfully updated the HBA firmware using Broadcoms StorCli package for Unbuntu (Proxmox), passed through the HBA directly to Unraid, blacklisting the driver in Promox, and my Unraid main array is online and healthy. But, when Unraid boots, I get the following error: I've understood, from browsing other posts and tinkering with StorCli, that this particular controller should work fine with Unraid. For instance, when I run these commands in StorCli I get errors, that these commands don't work. /opt/MegaRAID/storcli/storcli64 /c0 show bios /opt/MegaRAID/storcli/storcli64 /c0 set bios state=off abs=off Also, in the MB BIOS the configuration options are not active for this controller, I can only display information, such as firmware, etc. I have the Proxmox boot order set to USB (Unraid) first, but for some reason when I start the VM Unraid tries to boot the HBA BIOS, fails, and patiently waits for me to press any key. Any ideas on how to get Unraid to boot normally? Many thanks
  5. Thanks for all the detailed responses, I've already learned a few things here. I like the ipmi workaround you found, and specifics about how Supermicro sets the speed at boot. I am also tempted to HA my OpnSense box as a result (do you just move the WAN cable when trouble starts?). I have a question on how you manage the hba if you don't mind. Right now I have the drives connected to the motherboard controller and I'm passing the devices (hdd) to Unraid as virtio, but I'm on the fence about passing through the hba controller to give Unraid direct access (pros and cons to each approach). Long story short, passing through the onboard AMD hba controller with Proxmox is tricky and I don't like the workarounds that can address the compatibility challenges. I'm thinking of getting the Broadcom hba you are using, but I'm unsure of how I will get it to work with the three Mini-SAS ports on my backpane. I noticed that your backpane also has three ports, how did you get around this problem? My current setup needs two cables CBL-SAST-0826 from the onboard Slimline-SAS (SFF-8654) x8 ports to the three Mini-SAS HD (SFF-8643) x4 on the backpane. If I went with the Broadcom hba, I would need a cable that splits the x8 into 4 x2, but I'm unaware such a cable exists, or whether Mini-SAS even comes in x2 flavors. Broadcom does have a x16 adapter eHBA 9620-16i from which I can run two cables, but it's around 1'000 USD and hard to find. Maybe I'm missing something obvious, but my first experience with SFF compatibility on an ASRock motherboard has made me paranoid and prone to over complicating. Cheers
  6. At idle around 160~170 watts and noise with the Standard fan profile is tolerable, keeping the hdd comfortably under 40 C and the flash below 60 C. Though, noise is less of a problem for me because I built a noise and dustproof case around my rack Link . My goal was never to have to worry about hdd storage capacity and Unraid delivers. At my fill rate and room to grow to 10x 18 T (w 2x for parity) drives I think I've got that covered unless I start running a media focused business. The tricky part was getting space for U.2 drives. I want everything software related (boot, vm, containers, etc) and zfs based storage to run on flash only. For zfs, this means I get all the nice features without the headache of performance turning and degradation as it fills up.
  7. Nice build! I've put together something similar, maybe I'll throw up a post. My approach is running Unraid as a guest on Proxmox and so far I'm happy. Here's a link to the post on reddit Link with pictures. 1x Case SilverStone RM22-312 1x PSU SilverStone GM800-2UG 1x MB Supermicro H12SSL-NT 1x CPU AMD 7443p 1x Heatsink Dynatron A38 8x RAM Kingston KSM32RD4/64HCR 64G (512 G) 1x PCIe U.2 Delock 90077 4x4 v4.0 bifurcation 2x PCIe M.2 Delock 90090 4x4 v4.0 bifurcation 1x LAN Intel X520-DA2 10Gbit SFP+ 3x Bracket 2.5" Delock 18271 4x Heatsink M.2 be quiet MC1 Pro 2x Cable Supermicro CBL-SAST-0826 2x Nvme M.2 Samsung PM9A3 1.9 T (Proxmox boot mirror) 2x Nvme U.2 Samsung PM9A3 3.8 T (Proxmox vm mirror) 2x Nvme M.2 Samsung 990 Pro 2 T (TrueNas zfs) 2x Nvme M.2 Samsung 998 Pro 1 T 2x Nvme M.2 Samsung 960 Evo 1 T (Unraid cache) 2x Optane Intel P4801x 100 G (initially planned as slog for zfs, but decided to run TrueNas nvme only) 1x HDD WD Ultrastar DC H560 20 T (Unraid parity) 4x HDD D Ultrastar DC H550 18 T (72 T) (Unraid pool)