Recent content by bzdigblig

There really isn't a whole lot to do on the UC3200 to set it up. The MPIO config on Proxmox is much more important.

The problem seems to be solved, but I didn't have much to do with it. The last update that Synology released for the UC3200 broke the non-transparent bridge linking the two controllers together, and this would cause the UC3200 to reboot itself regularly. Synology had to have one of their techs...

Those are my thoughts exactly. This config ain't rocket science. Even if was doing something crazy and causing an issue to happen, that should be my problem, not a problem with the storage device. Synology's been quite responsive overall, but getting into a real technical discussion seems...

Just wondering if anybody's got any ideas here. We've got a 3 node Proxmox cluster, with a Synology UC3200 as shared storage. The UC3200 has dual controllers in an active-active SAN configuration, so if one controller craps out, the workload won't be interrupted. The nodes and the UC3200 are all...

I appreciate your help. Thank you. There's just so many moving parts to this project, and for every thing that I know, there's like 15 things that I don't know, so there's a lot of learning as I go.

Thanks for the clarification. Am I to assume that my little experiment to try and create shared storage didn't actually damage anything then? And yes, the LVM is thick so no issues there.

If I had to guess, I'm going to assume it has something to do with my iSCSI/MPIO config, and the PV, VG and LVM created on top of that. /dev/mapper/HDDmpath0 or /dev/mapper/SSDmpath0 seem to be the block devices you're thinking of...I think those are the physical volumes. mpath0-VGSSD or...

I didn't create any LVM slice or anything. I just navigated to /dev/mpath0-VGSSD, saw that's where my VM files were, created a /sharedstorage folder there, then in the GUI, I went to Datacenter > Storage, and added a Directory for disk images and container templates, pointing to the...

Yes, the mpath storage is external storage, connecting to each node with multipath iSCSI connections. I didn't do a whole lot when trying to access this storage in the way I described...pretty much just tried it, saw it wasn't sharing in the way that I wanted, and reversed everything I did. The...

Setting NFS up locally on one of the nodes makes no sense if I'm trying to make this storage independent of a particular node, and externally makes no sense, since I'm trying to migrate stuff to our cluster, not off of it. Just to make sure I've got this straight...I already have storage that's...

As a final update, I never ended up figuring either the cause or solution to this. I just nuked all my network storage and started over. Not really an ideal solution in a production environment, but what can ya do..

I'm trying to figure out how to simply create a shared storage location so ISO or container templates can be accessed from any node in the cluster. I've got SSD (/dev/mpath0-VGSSD). and HDD (/dev/mpath0-VGHDD) storage added to the cluster...what do I need to do to actually use some of that...

Thank you. I appreciate your time and help. I'm sure I'll add more to this if/when I either solve it, or keep smashing my head against the wall.

That is correct. fdisk -l Disk /dev/sda: 446.63 GiB, 479559942144 bytes, 936640512 sectors Disk model: PERC H730P Mini Units: sectors of 1 * 512 = 512 bytes Sector size (logical/physical): 512 bytes / 4096 bytes I/O size (minimum/optimal): 4096 bytes / 4096 bytes Disklabel type: gpt Disk...

I appreciate your help. Still no joy though.. pvs PV VG Fmt Attr PSize PFree /dev/sda3 pve lvm2 a-- 446.12g 16.00g vgs VG #PV #LV #SN Attr VSize VFree pve 1 3 0 wz--n- 446.12g 16.00g lvs LV VG Attr LSize Pool Origin Data% Meta% Move Log...