Recent content by ghusson

Hello, could it be a disk read cache that is present on the source server but not on the destination server ? If you want to clear caches, you can refer to this link for example : https://linuxvox.com/blog/linux-cache-flush/

It is my 20 years of sysadmin and 16 years of Proxmox experience. I then used Claude to search around this possibility and it found 2 bugs report about it.

I am not sure if ti will work. Maybe read the github ? https://github.com/google-coral/edgetpu You could report your issue to the project as it is not linked to Proxmox.

What Claude says : Short answer: pulling the SSD out and putting it back, or attaching it as a secondary disk on another machine, does not change anything by itself. A disk only gets altered when a system writes to it. The main suspect is therefore the Clonezilla step, and two known mechanisms...

Ok I have an idea of what could be arriving here. Clonezilla classically reproduce disk structure and do things inside partitions. I didn't paid a close look but what could be happening here : - clonezilla reproduce LVM structure with same UUID - clonezilla begins to copy data but LVM...

Update is not allowed by google, read the error : E: Failed to fetch https://packages.cloud.google.com/apt/dists/coral-edgetpu-stable/InRelease 403 Forbidden [IP: 142.251.38.110 443]

"Forbidden [IP: 142.251.38.110 443]" seems to indicate that the repository reject you. Maybe because your IP was banned or more plausible that you need an authentication or a way to prove that you have the right to connect. Look at our product manual ? Maybe they have changed something ?

Hello, it is very strange. It shall not do that. Is it possible that the source disk has problem you didn't saw before ? Make a SMART test, look at %use, ... When you stopped the initial computer, was it a clean shutdown ?

Maybe a return of this command can help too : sudo lsof | grep ttyUSB

It seems to be a google repository problem. It doesn't allows you to download the catalog. I don't know anything about Google Coral. Recheck the connection procedure to the repo and verify your credentials ?

Hello, where did you sax that 0.1.271 is currently recommended for production use ? they are quite old... As said @bbgeek17 , latests stable are 0.1.302. Latests stable can always be downloaded from : https://fedorapeople.org/groups/virt/virtio-win/direct-downloads/stable-virtio/virtio-win.iso

Is nut on the dialout group ? cat /etc/group | grep nut if not (result = nut:x:119:), try to add it : adduser nut dialout It is just an idea.

Could it be a RAM overprovisioning issue ? Do you see OOM killer lines in the journal ?

You are right, old reflexes :-)

As an ugly solution you could use a VPN or L2 encapsulation as VXLAN over OSPF loopback IPs.