Search results

For me it was 2 failed drives that caused the timeout. I changed them and everything is fine now.

Had a similar problem, and the thing with me was that i had 2 failed drives, and it tried to read something from it, timeout, and the network did not come up. Changed them, and everything is fine now.

Great. I will test this. But for now it seems the problem i had was solved by updating the packages i was using in the container.

So i have just upgraded to proxmox 8.2, and i have a problem with a container. The problem is that the 6.8 kernel seems to cause a crash in some packages i use, and it seems that the previous kernel is ok (6.7). So is there a save way to use the kernel version ?

I think you should just run apt autoremove after everyupdate (at least when a new kernel shows up). I had this problem on one node, and not the other, because it seems that i did not run apt autoremove after the updates.

Yes, i think i will probably do a clean install with ubuntu server. I havent decided yet if it will be a vm or a lxc container. But i was wondering if there is a way to upgrade a CentOS 7 LXC container. So no dice ?

So i have a old CentOS 7 LXC in proxmox. Is there any way i could upgrade this to something newer like almalinux ? Has anyone tried this kind of thing before ? I would prefer to avoid having to create a new lxc\vm and migrate everything over to it !

Scratch that. I rebooted the node (after installing pbs on it), and it now shows up.

So i have installed pbs on top of proxmox, but it cannot detect my tape drive. If i run "proxmox-tape drive scan", i dont get anything. What could i check ?

I wont copy anything. The folder will stay in the same place, in cepfs, and i would just mount it to another ct\vm

So if i have a folder, that has backups from another pbs instance, i cannot just used in a new pbs instance ? I mean, cant i just point the second instance to the same directory ?

Hmm. I dont think this would be a problem. So the datastore would be in a directory in cephfs, so it would be available on the other nodes as well. So in the event of a complete failure of the node running pbs, i could install it on another node, point it to the same data store, and i could use...

Yes, i saw that, i also understand that its not recommended. But on this point. Is the recommendation related to the fact the if the node fails you cand access the backup ? Or some other problems ? Like package conflicts, etc ?

I would like to use in a vm in order to use proxmox backup server.

The plan was to use PBS as a container or vm, in inside it i would have access to all the backups (via ceph). I would then use the tape device to write backup to it.

Thanks for the reply. Yes, im aware that i could add another sas controller, and pass that to the VM. Im trying to see if there is a alternative solution to this. So yes, im using debian as its a proxmox host. I dont actually know what options i have on debian in order to use this tape drive...

So i have a tape drive, connected to LSI sas controller. The controller has 4 ports. 2 of them are used for some external enclosure, and 2 of them for this tape drive. So what i need to do is somehow pass the tape drive to a VM. I cannot pass the whole pci device because of the external...

Not yet. I mean we have done it directly in ceph (so no proxmox). Maybe in the future this will also be managed from proxmox.

No i did not use zfs at all. And the device the error is indeed used, but its a ceph cluster.

So that cmd returns: root@int2:~# zpool status -v no pools available And i only have these drives: I did not use zfs on this server. By the way. Im talking about proxmox, not PBS (i just saw i posted in the PBS section).