Search results

Updates. The problem seems to be resolved, at least in part, if the matadata servers are stopped. I say "at least in part" because some OSDs still require one manual start. The system where I tested this solution is not the same but the Ceph versions are the same. pveversion -v proxmox-ve...

I'm afraid we're not understanding each other with the terminology. :) Probably not the correct one but for me: cartridge drive changer/library: where the cartridges are parked and available to be loaded into the drivers. Tape The TS4300 is something very similar to the previous...

With "PBS expect to use the full tape" do you mean the whole tape or the single cartridge? Also, can the file archiving activity be done with PBS or does it only take care of its own backups?

In the company we have a TS4300 that we currently use with Veeam. In addition to managing backups of a VMware environment, we use it to archive files that we consider no longer "hot" but we don't want to delete them. Since we are planning to switch everything to Proxmox, I would like to switch...

The problem was the SAS card. I tried with another, more recent, SAS card and managed to connect the Drivers and the Changer.

No! In reality the problem I reported is exactly this! It won't let me add new OSDs.

Any other suggestions?

Interesting! Maybe if I modify the configuration file I could do a direct restore. The problem with editing it is that it appears encrypted. Is there a way to change it?

So if you wanted to restore the machine on another server the storage names should be the same.

Restoring to a VM from WebGUI lets you choose only one storage for the restore. This is problematic given that very often if I have a VM with two disks on two different storage it's because I don't have the space I need on just one. So I couldn't do the restore. Is there a way, even in CLI, to...

Done, no improvements or changes.

ceph osd crush set-device-class hdd osd.0 osd.1 osd.2 Error EBUSY: osd.0 has already bound to class 'os', can not reset class to 'hdd'; use 'ceph osd crush rm-device-class <id>' to remove old class first So I run: ceph osd crush rm-device-class 0 ceph osd crush rm-device-class 1 ceph osd crush...

I delete the OSD by Stop -> Out -> Destroy, all in the WebGUI. How you do it?

ceph osd tree ID CLASS WEIGHT TYPE NAME STATUS REWEIGHT PRI-AFF -1 0.09357 root default -3 0.03119 host pve1 0 os 0.03119 osd.0 down 1.00000 1.00000 -5 0.03119 host pve2...

No. pveversion -v proxmox-ve: 8.1.0 (running kernel: 6.5.11-4-pve) pve-manager: 8.1.3 (running version: 8.1.3/b46aac3b42da5d15) proxmox-kernel-helper: 8.0.9 proxmox-kernel-6.5.11-4-pve-signed: 6.5.11-4 proxmox-kernel-6.5: 6.5.11-4 ceph: 18.2.2-pve1 ceph-fuse: 18.2.2-pve1 corosync: 3.1.7-pve3...

I'm trying to familiarize myself with problematic ceph situations. I can't find the solution to a situation that seems simple enough. The problem is this: Once I have inserted various OSDs I delete them, by Stop -> Out -> Destroy. Now I try to add them again. The problem is that the re-added...

Removed the comma, no improvement. cat /proc/cmdline: BOOT_IMAGE=/boot/vmlinuz-5.15.102-1-pve root=/dev/mapper/pbs-root ro quiet intremap=off

If you intend modify the file /etc/default/grub like this: # If you change this file, run 'update-grub' afterwards to update # /boot/grub/grub.cfg. # For full documentation of the options in this file, see: # info -f grub -n 'Simple configuration' GRUB_DEFAULT=0 GRUB_TIMEOUT=5...

Here the dmesg output.

I'm afraid the server (a ProLiant DL360p Gen8) doesn't have this option. :(