Recent content by Psilospiral

zelenij - I can confirm that simply adding "iommu=pt" to /etc/default/grub like: GRUB_CMDLINE_LINUX_DEFAULT="quiet iommu=pt" and then sudo update-grub fixes the fusion-io kernel issue on my t630 when booting any kernel 5.15 or greater. Thank you! The README.md has now been updated to...

kromberg - No I am using the following files (as in the first post): iomemory-vsl-5.12.1 fio-common_3.2.16.1731-1.0_amd64.deb fio-firmware-fusion_3.2.16.20180821-1_all.deb fio-sysvinit_3.2.16.1731-1.0_all.deb fio-util_3.2.16.1731-1.0_amd64.deb What are you using and could you please provide a...

cali0028 - I experienced the same issue with my fusion-io scale 2 this morning. I was able to get my server back up and running fairly quickly though. From the GNU GRUB boot menu, select "Advanced options for Proxmox VE GNU/Linux" then "Proxmox VE GNU/Linux, with Linux 5.13.19-6-pve"... After...

Thank you again, Dominic!

Hello prolab: I tried several different CLI methods before I realized the PVE GUI method was the easiest and best solution for me. To mount a Turnkey Linux File Server CT within Proxmox: After creating the TKLFS CT, go to Datacenter>[node name]>[TKLFS CT]>Resources>Add>Mount Point. Mount...

Vladimir: Here is my fio-status -a root@r720xd1:~# fio-status -a Found 1 ioMemory device in this system Driver version: Driver not loaded Adapter: ioMono Fusion-io 1.65TB ioScale2, Product Number:F11-003-1T65-CS-0001, SN:1323G0577, FIO SN:1323G0577 ioDrive2 Adapter...

Hello again Vladimir! I hope you have been well in Moscow. I had a power outage recently and when rebooting, my Fusion IO 2 driver would not load. My temps are still under control at 60C, so I decided to run the following build/modprobe as you suggest in your tutorial, but received...

Greetings again Vladimir: Have you written/tested your guide for Fusion IO2 installation on PVE 6? I am happy to test with a spare fio card on my R720...

Thank you for posting this, RobFantini. Your post allowed me to quickly solve a problem. I ran into this same 'namespacing permission denied' issue that was noted in my systemctl logs while creating a CT for a Syncthing server. Simply checking Options>Features>Nesting:ON took care of the problem!

I ran into this exact situation after completing a fresh install of PVE 5.4 (that I just downloaded) while testing another Fusion-IO Scale2 card I picked up. After installing PVE 5.4, I had kernel pve-4.15.18-12 and received: Backing up initrd.img-4.15.18-12-pve to...

t.lamprecht: So after realizing I could not alter the ownership of the mounted directory from within the CT, I decided to try to mount a directory under the syncthing user home directory: root@syncthing ~# su - syncthing $ pwd /home/syncthing $ mkdir share $ ls -hAl total 36K -rw-r--r-- 1...

t.lamprecht: Thank you for the suggestion. FYI: In PVE webUI: Datacenter>101 (syncthing)>Options>Features, I have nesting=1, mount=nfs,cifs. Aso, Unprivileged container= No. From within TKL Syncthing CT (101) console: root@syncthing ~# id syncthing uid=999(syncthing) gid=999(syncthing)...

I am running PVE 5.4-11 on a r720xd configured with two containers. One is TKL File Server (100) which is configured with several cifs shares. Those shares are accessible and writable on numerous PCs on the LAN. I have TKL Syncthing (101) installed as the second container. I am attempting to...

THANK YOU for posting this. I have been having a similar "bear" of a time trying to mount a TKL File Server contatiner share in a TKL Syncthing container. I have read that Proxmox bind mount page about a dozen times, and it never dawned on me that I needed to mount the share to the PVE host...

Thank you for posting your solution. This quickly solved the same issue for me.