Search results

I run apt dist-upgrade but get this error:

on that note, what is the upgrade process from 1.0 to 2.1 PBS?

maybe it was when it was in Beta, it was a known issue at one point. I'm on PVE 6.4 and PBS 1.0, Just don't want to jump too far too fast, thanks for info.

I know PBS was not 100% functional with 7.0, just wondering if that's fixed now.

I'm ordering a new server to add to my stack, its AMD EPYC dual 32C/64T processors and 1TB RAM in Dell 7525, anyone have a similar setup? Any issues? I do see where Proxmox Backup Server agents are not ready for the new Debian kernal, guess I'll wait a little longer, as I use the PBS.

ok, that makes sense.

Mine all say this:

welp, despite my lack of support licensing, i did add the enterprise repository as per above article, updated on one of the hosts and restarted all 22 VM's, and they all still have the same NIC. Maybe I had the wrong setting all along?

I'm on free version (no support contract) I can only use certain update repositories.

Update, the hardware has changed enough the VM's are now requiring Windows to be Re-Activated, this is ridiculous.

I see that what's happened, but I upgraded from 5.5 to 6.2 I didn't have to do this, not sure the update was thought through.

Every VM now has a "new" NIC installed and all my VM's were statically assigned IP addresses. I now have to log into every VM and reset the NIC's IP's ugh, why does this happen? VM environmant 6.3-4

Thanks.

Nobody seen this? or have a reason for the error constantly resending the emails?

I keep getting at 3am everyday this email about a drive that had a SMART issue. I replaced the drive (disk_08) and the emails just keep coming. How do i get rid of the emails? Subject: SMART error (FailedReadSmartErrorLog) detected on host: proxmox4 This message was generated by the smartd...

VE 6.2-15, PBS 1.0-1. Storage space used is 7% of 3.77TB.

I can run the backup job manually on only that one VM Template and still fails. I have other running VM's and another Template and those work fine. Right now no one is using the VM's so all hosts are more or less idle during the backups. I see nothing else in the logs to indicate anything going...

All other vm's on the back up schedule work every time, the below vm had never worked, I even migrated to another host with no change. Here's the error: 118: 2020-11-11 16:44:36 INFO: Starting Backup of VM 118 (qemu) 118: 2020-11-11 16:44:36 INFO: status = stopped 118: 2020-11-11 16:44:36...

the above does not fix it for me: root@proxmox4:~# zfs list -t snapshot NAME USED AVAIL REFER MOUNTPOINT RAIDZ/vm-200-disk-0@__migration__ 21.5G - 80.8G - root@proxmox4:~# zfs destroy rpool/data/RAIDZ/vm-200-disk-0@__migration__ cannot open...

ahh, now I can implement another and move forward, thanks!