Recent content by jameswang

I made changes and created two datastores on PBS: osvms and mvms. But when I tried to add them under cluster storage, I got 'cannot find /datastore/osvms' even I gave correct admin right to the account. Do you know what I did wrong? I will try it again tomorrow. EDIT: as soon as I submitted...

Thank you for your fast response. I didn't expect you replied this fast and started to clone the VMs. This is a great idea and I am going to try it now.

How do you do that? I have a raw disk that is already mounted as /datastore/backups. When I tried to create a second datastore and point it to /datastore/backups, it won't allow me with file exist error. Thank you.

We use hardware RAID and zfs is not recommended.

We had same issue after adding more RAM in our 7.4-16 server. The above fixed it. Thank you.

Yes, please. We use fog for imaging our computer labs. We will be using PVE for a virtual computer lab soon.

Check if 'Sleep' is not set to 'Never'.

FYI, We had PVE hosts random reboots and they were caused by bad RAM modules.

FYI, I had same problem when tried to install Rocky 9 on PVE 7.2 (change CPU type to 'host' fixed it). I tried the same ISO on ESXi 5.5 and was able to install it.

Thank you bbgeek. I will go through the link and give it a try. I created a brand new VM in PVE and installed CentOS 7.9 on it. The X11 forwarding works. So it has to do with the new virtual hardware like you mentioned new NIC designation , change in drivers, or something similar. I did try...

Hello, We were a VMWare shop for over 15 years. Recently I migrated most of our VMs from ESXi into Proxmox 7.2 (new to proxmox). Initially we had server random crash issue. It was fixed by identifying a couple of failed ram modules. The two clustered Proxmox servers have been up and stable for...

Find out the filesystem type: file -s /dev/group1/vm-101-disk-0 or if it's symlinked, then file -L -s /dev/group1/vm-101-disk-0 Then mount it with 'mount -t the-filesystem-type /dev/group1/vm-101-disk-0 /mnt/fedora' --where the-filesystem-type is from the file type the 'file' command output...

Run 'lvdisplay', it'll give you details including LV Path. You can then mount it to your local filesystem (e.g. /mnt/) with the correct filesystem type.

I had a 7.2 server that crashed randomly, sometimes several times a day. I enabled kernel dump and finally caught the error: one of the memory modules was bad. Replaced the module with a new one and the server has been up for 41 days now without a crash. Not sure if it's your case but it might...

Thank you. Changed Win10 VM's sleep mode to 'Never' fixed it.