Proxmox and MSA SAS
- Thread starter popoche28
- Start date
PVE is a set of packages and custom Ubuntu kernel, using Debian as userland. In essence, you would be connected your SAS array to a Linux host. Hence the answer to your question - "yes in most cases, yes specifically for PVE distribution).
Blockbridge : Ultra low latency all-NVME shared storage for Proxmox - https://www.blockbridge.com/proxmox
Blockbridge : Ultra low latency all-NVME shared storage for Proxmox - https://www.blockbridge.com/proxmox
Yes. I have a deployment running. even with multipathing. its pretty much plug and play.
It's Linux so everything works out of the box or you have a really hard time to get it working. In this case the former is true, so plug & play. If you want to use Multipathing, you need to install ... just look at this.
Yes, it was only for multipath access if necessary.
So, how do you determine that it is not working? It's plug & play.
Years ago I had to deal with an MSA2050, in my old thread some multipath configs were posted, maybe they help you getting started.
Also used SAS controllers.
https://forum.proxmox.com/threads/pve-6-0-hpe-msa-2050-sas.57317/ (german though, but the config is probably most relevant part anyway)
Also used SAS controllers.
https://forum.proxmox.com/threads/pve-6-0-hpe-msa-2050-sas.57317/ (german though, but the config is probably most relevant part anyway)
Hi, I have a MSA2062
On my vSphere I see MegaRAID 12GSAS/PCIe Secure SAS39xx with lsi_mr3 driver
Last edited:
Thats the key. since this is a raid controller and not an HBA, you'd need to "map" the luns presented by your MSA to the host. map is in quotes because in order to do that, you'd need to make them a single disk raid volume. you can do so from the bios or using megacli.
This is less than ideal for many reasons. consider replacing it with an HBA (host bus adapter.)
Hello, you told that's pretty much plug and play. But not for me, I think. Could you explain it to me shortly?
Its a three step process:
1. create and map LUNs on your controller. if you need help with this step, its in your MSA user manual.
2. This part depends on whether you have dual connections to the controller- install multipath-tools and multipath-tools-boot. configure according to the documentation.
3. define the storage in pve, as described here: https://pve.proxmox.com/wiki/Storage. you'd follow the steps for iscsi or SAS (local), depending on your controller type. file system is LVM THICK (not thin). Make sure to specify the multipath device name, not the "sd" device.
If you have specific questions feel free to ask.
1. I've done it
2. I've installed multipath-tools and multipath-tools-boot and lsscsi shows such state:
Code:
[1:0:0:0] enclosu HPE MSA 2050 SAS V270 -
[1:0:0:1] disk HPE MSA 2050 SAS V270 /dev/sdd
[1:0:1:0] enclosu HPE MSA 2050 SAS V270 -
[1:0:1:1] disk HPE MSA 2050 SAS V270 /dev/sde3. I don't know what to do now. It's SAS not iSCSI, how to use it as block device? Proxmox shows 2 block devices but can't create volume group (no disks unused).
Last edited:
If you have configured multipath, please post the output of (in CODE tags):
Code:
multipath -llNormally, you would get a device there on which you can create your physical group and then the volume group with this physical volume
Its worth noting that to get full useful performance from this storage you really want TWO luns, since a lun can only have one active controller at a time. This obviously assumes you have two controllers.
So you're good to go? the rest of the instructions is pretty much the same as for any other local attached storage.