Hey everyone,
I’ve finally decided to stop lurking and actually post. I’ve been building out a home lab over the last few months, and while it’s been a great learning experience, I’ve hit a bit of a wall with my storage expansion.
To give you some context on the setup: I’m currently running a refurbished ProLiant DL380P (Gen8). It’s not a speed demon by modern standards—it’s equipped with a single Hexa Core 2.0GHz Xeon —but for my needs, which are mostly local file backups and running a few lightweight VMs, it’s a total workhorse. I love the industrial build quality of these older servers; there’s something incredibly satisfying about the "clunk" of a drive tray sliding into place that you just don't get with consumer-grade plastic towers.
My personal insight from this journey is that enterprise gear is both a blessing and a curse. It's built to last forever, but it can be incredibly finicky when you try to mix and match different generations or brands. My current headache involves trying to daisy-chain an older VTrak series expansion chassis to the ProLiant via an external SAS HBA.
Specifically, I’m running into a point of failure regarding LUN mapping visibility. I can see the HBA is active in the ProLiant’s POST sequence, and the green lights on the expansion unit indicate that the drives are spinning up and healthy. However, once I get into the management interface, the server just refuses to acknowledge the logical drives I’ve configured on the storage array. It’s like they are speaking two different dialects of the same language.
I’ve tried swapping out the SFF-8088 cables and even tried a different PCIe slot on the DL380P, thinking it might be a lane-sharing issue with the Xeon's limited PCIe count on this specific low-clocked model, but no luck so far. I suspect there might be a firmware mismatch or perhaps a specific setting in the storage subsystem that I’m overlooking that’s preventing the "handshake" from completing.
Has anyone here had success bridging the gap between older HP rack gear and these dedicated storage subsystems? I'm curious if I need to hunt down a very specific driver version for an older OS, or if there’s a known compatibility quirk with the Gen8 backplanes and external arrays.
I’m starting to wonder if the 2.0GHz Xeon is actually struggling with the overhead of the management software, or if that’s just my frustration talking. Do you think the issue is more likely at the physical layer of the SAS controller, or should I be digging deeper into the subsystem’s internal configuration?
Looking forward to any advice you can spare!
