Search results

@Alwin - it is working on Ubuntu 19.10. Moreover, i can mount it manually via mount -t nfs on Proxmox. But when trying to use pvesm add nfs, it fails. If i understand correctly, it should be an alias for the mount command, am i right? It's totally weird why one works and the other one fails.

Same issue. NAS: Thecus N2800. Works perfectly with Proxmox 5, fails on Proxmox 6. The server with Proxmox 6 used to work fine with this NAS prior to upgrade (to cross off the hardware issues). Firewall is disabled.

Confirming the issue. I have the following setup: NAS connected to the router, which forwards the incoming traffic to NAS. I connect to the router via DDNS (no static ip). I have 2 servers: 1 running Proxmox 5 and one running Proxmox 6. Both ips of these servers are allowed to connect to NAS...

Confirming the issue. I have the following setup: NAS connected to the router, which forwards the incoming traffic to NAS. I connect to the router via DDNS (no static ip). I have 2 servers: 1 running Proxmox 5 and one running Proxmox 6. Both ips of these servers are allowed to connect to NAS...

Second generation (ioDrive2) ;)

Success! :D Thank you for the tip. Turns out that the answer was hidden in the diff of the lvm.conf i've posted earlier. The reason why it works on Proxmox 5 and not Proxmox 6 is a different approach for LVM activation. The activation in Proxmox 6 is based on global/event_activation=1, which...

@fabian I understand perfectly well that you've no time to waste on support requests arriving randomly, but I think it's a question that is important. So it happens that Fusion-IO drives are a really good alternative to expensive PCIe drives out there and up until recently i had no hope that...

Hey, @fabian It is indeed the case that LVM processes fire before the device is attached. What is strange - why does it not monitor for devices added later? Is it possible to make sure the device is attached before the LVM processes are triggered? What is the difference in how LVM works in...

@mira Is it possible to adjust the template so that a log record is issued so that i can check what is the execution order? Going through the logs of Proxmox 5 and 6 i notice that the Fusion-IO card is added more-or-less identically, so assume it's not the case. Moreover, the strange thing is...

Never had SX300/SX350/PX600 on my hands to test it. Still looking for one.

Hey! Simply install these drivers: https://github.com/snuf/iomemory-vsl/tree/5.1.28. Make sure you use specifically drivers from this branch (5.1.28). The only thing you will have to adjust is (assuming you've downloaded the drivers to /home/temp directory): cp -r...

@fabian, @mira Merry Christmas, guys! Was wondering if it's be possible to look into this issue when you're back from holidays. Thank you in advance!

Hey, @mira Any updates? Would it help if you had Proxmox backend access?

@mira can you please tell me the location where i can look for these files? Update: i've gone through lvm.conf and it seems to differ from Proxmox 5 to Proxmox 6. https://www.diffchecker.com/eR8AYa9v It seems to skip lvmetad in Proxmox 6. I've tried swapping lvm.conf from Proxmox 5 to Proxmox...

@mira this is a clean Proxmox 6 install. I've no idea how something can be missing. No idea how lvmetad config looks like. If it'd be easier, i can send you the Proxmox credentials. Again - this is a clean instance. No idea why it would not have services enabled.

@mira lvm2-monitor.service loaded active exited Monitoring of LVM2 mirrors, snapshots etc. using dmeventd or progress polling lvm2-lvmpolld.socket loaded active listening LVM2 poll daemon socket

@mira, maybe this will help. This is what i notice on Proxmox 5 instances: Dec 09 05:31:50 dc1 kernel: <6>fioinf ioDrive 0000:41:00.0: Found device fct0 (HP 1205GB MLC PCIe ioDrive2 for ProLiant Servers 0000:41:00.0) on pipeline 0 Dec 09 05:31:54 dc1 kernel: <6>fioinf HP 1205GB MLC PCIe ioDrive2...

To be honest, haven't noticed anything suspicious in the journal. In any case, can provide access to Proxmox. Here is the data below: pveversion -v proxmox-ve: 6.1-2 (running kernel: 5.3.13-1-pve) pve-manager: 6.1-3 (running version: 6.1-3/37248ce6) pve-kernel-5.3: 6.1-1 pve-kernel-helper...

Currently working on a solution to port ioDrive2 devices to Proxmox 6.1. The last issue to solve is the volume group activation after boot, mentioned here. If the issue is solved, the solution will be ready for testing in production environments. I guess we all want a piece of that Proxmox 6...

Hello! I experience a weird issue on Proxmox 6.1. I've added a storage as LVM-thin. The container storage was created on this storage. After the machine is rebooted, the storage showed as 0% usage and the container would not launch. After debugging this issue for quite some time I've noticed...