Search results

This person managed to install PVE on top of a QNAP. The base is debian. I'm sure it can be done the same way for PBS. https://old.reddit.com/r/qnap/comments/kf9632/why_is_this_not_a_thing/gg8ys3k/

I don't think anyone has said they cannot use proxmox 5.11 on NUC 11. The issue is purely the Proxmox graphical installer with the NUC 11 gfx card/driver. As long as you're using the latest proxmox ISO, all you need to do during the install is: Wait until an error about Chrony Press Alt + F3 to...

I just had the same thing...brand new PVE install...thought what the heck, after reading this, I'll ping my laptop IP from the shell of PVE. All of a sudden, the webui is working on my laptop...

I changed the storage server option to be IP based rather than hostname it fixed it. Cheers!

Hah..omg. https://isitdns.com/ You're right. This VM is the primary DNS. I have a failover backup DNS and the switchover happens automatically in < 10 seconds, but the snapshot and backup obviously pauses the VM and attempts to connect in a much faster time than that! You're a genius @dcsapak...

Thanks @dietmar but as mentioned its SPECIFICALLY only this one VM. If I immeditely go backup another VM to the same PBS target (i.e. with the same network conditions), no issues at all. I'm backing up 7 other VM's in total and it's a repeatable consistent error only on this one VM. Therefore...

Hi, I have a remote PBS and have it configured so PVE runs the backups. All other VM's, split across two PVE nodes, get backuped fine to this target. The one that won't back up reports: INFO: starting new backup job: vzdump 201 --mode snapshot --node proxmox1 --remove 0 --storage pbs-remote...

+1 to this issue! Will keep an eye on the bug.

Well I just dropped £600 on a new 2-bay NAS. I couldn't handle the r/w speeds of my 10 year old QNAP running on an ARM chip less powerful than my phone. At best it was doing 20mb/s transfers -_-. I'm still not seeing any corruption on it, but will test with my new NAS once it's up and running.

Thanks @guletz ! Thats excatly the sort of process I was thinking of doing, helpful to have it written out! So far with a 5GB file the checksum is fine/identical both sides, will wait a few hours and check again. Although I've had checksum issues with smaller PBS backups (~8GB) previously...

Trying to find the root cause of this. My QNAP doesn't run ZFS so cannot scrub it, but all the inbuilt RAID(5) tools, fsck and smart disk checkers report no issues. I've also been using it as a filestore and VM backup for a month or two without any issues (I've restored VM's from it multiple...

Getting Data blob has wrong CRC checksum errors again on larger backups :confused:

So still not sure why every backup was corrupt when my NAS reports 0 filestore errors. But fixed it - I had to remove the datastore config, then re-add it. For others doing this, I came across these issues: a) you cannot add storage to PBS with an existing PBS backup on it using the GUI or...

Fixed it - I had to remove the datastore config, then re-add it. For others doing this, I came across these issues: a) you cannot add storage to PBS with an existing PBS backup on it using the GUI or the command line tool (".chunks" - EEXIST: File exists" error). You can do it by manually...

I am having the same issue. I've tried turning opslock on/off on my NAS, I've confirmed lockd is running on the NAS host. I've also rebooted the NAS and unmounted/remounted the NFS share on the PBS VM, just in case. Still no dice.

I've read this might be to do with locking, but I've tried turning opslock on/off on my NAS, I've confirmed lockd is running on the NAS host. I've also rebooted the NAS and unmounted/remounted the NFS share on the PBS VM, just in case. Still no dice.

Thanks @dcsapak it's a good idea - to be honest my QNAP reports SMART as good, and a fsck doesn't show anything. I can't seem to find a RAID5 scrubbing option, its old QNAP but should still be there (will report back!). After running fsck I managed to get one backup stored and verified...

I'm having the same thing.. Installed PBS to test, added a NFS share, added the PBS to Proxmox as a storage target. Initiated a guest backup from within Proxmox. Switched to PBS and ran a verify: 2021-05-02T00:18:41+01:00: Starting datastore verify job 'zee-nfs:v-21eb29c4-30c6'...

I keep seeing these output to my proxmox console too: 78436.716999] zd0: p1 [78436.719978] zd16: p1 p2 p3 [78436.724023] zd32: p1 p2 [78436.732161] zd48: p1 p2 p3 p4 < p5 p6 > [78436.738724] zd64: p1 p3 Do I need to be concerned? Can't find anything else on Google about this apart from this post!

Welp, I ended up taking the ssd out and putting it in an older machine to install, then putting it back. Hoping I don't need to ever reinstall proxmox on this node... Edit: Take that back, networking is all messed up :/ Edit edit: kernel 5.11 fixed the issue. I guess NUC 11 hardware is new...