Recent content by SoMoney

using the NVIDIA run scripts has been hit/miss with me. When I get to step7, I much rather goto NVIDIA's cuda page https://developer.nvidia.com/cuda-downloads, and select nvidia/cuda drivers for the OS I'm building.

!RESOLVED! Since I wasn't using Ceph pools and it was only the monitor that was broken(thank god) I decided to stop/disable and remove all the configs and hope the proxmox gui would rebuild the monitor for me when it saw it unconfigured... systemctl status ceph-mon.target systemctl stop...

Hey guys, was looking to upgrade my proxmox 6.4.1 server this weekend to 7 but it looks like it's having Difficulties with Ceph. 1. root@pve:~# pve6to7 = CHECKING VERSION INFORMATION FOR PVE PACKAGES = Checking for package updates.. PASS: all packages uptodate Checking proxmox-ve package...

I did something similar where I wanted a striped zfs volume but Proxmox does not allow you to do it from the storage menu since its a terribly risky setup. EXAMPLE putting two nvme disks together with the name "JBOD" root@pve:~# lsblk NAME MAJ:MIN RM SIZE RO TYPE MOUNTPOINT nvme0n1...

I had similar issue with when my NFS and Proxmox IP's changed From the QNAP Under "Edit Shared Folder Permission" Select the folder you are sharing to proxmox Select NFS Host Access Make sure you host/ip/network matched to what you are actually using.

Will do, FYI the error message for the user should indicate the "Write to NFS was unsuccessful". This would have focused my attention on the NFS read/write access, not only " '/mnt/pve/BIGNAS' does not exist " and saved me/us some time...

Hey, there you go! I had R/O permissions for my BIGNAS:/ISO volume and that worked originally. I Set BIGNAS:/ISO to read/write and that seems to have woken it up! Dont know why my QNAP decided to enforce all of a sudden... Maybe some weird bug with my QNAP but Im working again... Thanks!

No Adds, what happened to start this was my NAS had the wrong saved subnet mask and became unresponsive after a reboot. I since corrected the subnetting issue and can ping and telnet to the SMB port on the nas, but ProxMox can't seam to make changes to its r/o filesystem configs.. I'm Running...

I have an NFS Appliance called 'BIGNAS' that rebooted and came back up. Proxmox however doesn't appear to assume nfs volumes ever come back and has it listed "inactive" root@pve:~# pvesm status unable to activate storage 'BIGNAS' - directory '/mnt/pve/BIGNAS' does not exist or is unreachable...