Search results

Hey, @Psilospiral and others! I haven't abandoned the thread, although I understand that updates are needed. My main concern at this moment is that regardless of the configs, flags and other tweaks my Windows 10 VM performance on Proxmox 7 is simply abysmal. I have 2 identical servers with the...

It may be the case that you're using ioDrive 1st gen card. Please check this list: https://docs.google.com/spreadsheets/d/e/2PACX-1vQMd40liekOCeftUYQx6GeofHgjU5SSDT-jHWid03JCfswQxHAhVee3rW-04baqKg1qN2fp7wEzuFm6/pubhtml

Hello, @Stefan_R Thank you for taking your time to address this. I guess a more detailed description of the situation is important, especially since downgrading Proxmox helped address the issue. The setup is the following - I am storing the VMs and CTs on a Fusion-Io PCIe SSD, added as a...

Looks like it's a dead card. It looks very similar to my dead ioDrive2. It may be the case that it's not formatted, but i doubt it. Sorry, mate...

Hello! I was wondering if Proxmox 7 has some architectural changes that need to be stored on VM and CT volumes. My situation is the following: I have VMs and CTs stored on a PCIe SSD and OS is stored on the disk raid I have reinstalled the OS entirely to Proxmox 7 and restored the conf files...

Interesting. Am i correct to assume that the drivers do load the drive every time and it's only the LVs that are not activated? What kind of storage are you using? Is it LVM thin? I assume we're in the same timezone, so drop me a message and i can connect remotely and have a look.

Hey! A couple of obvious questions: 1) what is the generation of the cards? Am i correct to assume it's the 2nd? 2) i see there are 2 cards installed. Have you tested with only one added? 3) has this setup worked in the past and stopped after the recent kernel update? 4) is the DKMS set up...

Just wanted to point out that i've tested this solution and it did NOT work in my case (NFSplugin timeout parameter). Cheers!

Glad it worked out for you! ;)

Hey! The obvious question - have you tried rebooting again? Does the problem persist? I had once a similar problem long ago due to the fact that the volume not being activated on boot. What do you see when you run lvscan -v? In my case the cause was related to the global/event_activation...

Glad to hear! :)

Hey! There is no need to add any records to the fstab. Storage.cfg should add the storage on OS boot. As for why it doesn't happen, can you please check the /etc/lvm/lvm.conf file and let me know what you have as value for global { event_activation }?

Glad it worked! ;)

Hey, maciek! As far as I remember, there is no way to output it as a disk for the OS, since the fusion-io cards are basically a RAID controller with several memory modules connected to it. View it more like a storage server. In order to make it usable within the Proxmox, I prefer creating an...

Hey! The most likely explanation is that you didn't go through with the DKMS installation for the iomemory-vsl module and most likely the kernel was updated between the reboots. Try checking this by running: ls /var/lib/initramfs-tools | sudo xargs -n1 /usr/lib/dkms/dkms_autoinstaller start If...

While this is a possible scenario, this is exactly why we exist as admins of the server. Whenever you update (we're talking mostly kernel here), you still have the previous kernel versions you can boot from in case something goes wrong. Moreover, it is never an ideal situation to jump blindly...

Sorry for the late reply. Yes, it is perfectly normal. As long as fio-status -a shows the drivers loaded - you are good to go.

You should definitely check LVM config. It might be.

Hey! Fusion-Io cards are not technically disks. Think of them as an external storage. The card itself has separate memory modules and a storage controller inside, so it's more like a RAID of SSDs. You won't see them in the disks tab, nor, most likely, there is no way to boot Proxmox from them...

The one in the initial message has been updated and can be used now.