Search results

  1. B

    virtio-win-0.1.262-1 Released

    Yes, you can install the drivers manually. Both during Windows setup and from within Windows. But if you're wanting all the drivers and services to be installed and functioning, the inability of the MSI-based installer to install everything is a bit of an issue.
  2. B

    virtio-win-0.1.262-1 Released

    Confirmed. Glad to see this thread. I have experienced the same. Neither an upgrade of an existing VM with previous install of virtio-win nor a fresh install of virtio-win-0.1.262 on a newly built Windows 11 VM succeeds.
  3. B

    ISOs uploaded to PVE via GUI became corrupted on cephfs. . .

    Hello! Thank you for the replies! Yes, this is a PVE-managed Ceph cluster. pveversion output follows. . . root@pve1:~# pveversion -v proxmox-ve: 8.2.0 (running kernel: 6.8.4-3-pve) pve-manager: 8.2.2 (running version: 8.2.2/9355359cd7afbae4) proxmox-kernel-helper: 8.1.0 pve-kernel-5.15...
  4. B

    ISOs uploaded to PVE via GUI became corrupted on cephfs. . .

    Located another corrupt ISO today. It was uploaded Feb 17, 2024. Can't say when the corruption occurred. But, given the findings above, I have no reason not to suspect that it happened after the file was uploaded and its checksum verified, like the other two. Having found this, I've now...
  5. B

    ISOs uploaded to PVE via GUI became corrupted on cephfs. . .

    We uploaded two ISOs on June 11 via the proxmox GUI and made use of the checksum matching feature while doing so. root@pve1:/var/log/pve/tasks# pvenode task list --type imgcopy...
  6. B

    Tape Backups Fail After Upgrade to PBS 3.2-4.

    Thank you, dcsapak. setuid bit set as you described. Tape backup job is now running.
  7. B

    Tape Backups Fail After Upgrade to PBS 3.2-4.

    Hello dcsapak, As requested: root@pbs2:~# ls -lh /usr/lib/x86_64-linux-gnu/proxmox-backup/* -rwxr-xr-x 1 root root 27M Jun 5 07:23 /usr/lib/x86_64-linux-gnu/proxmox-backup/proxmox-backup-api -rwxr-xr-x 1 root root 427K Jun 5 07:23...
  8. B

    Tape Backups Fail After Upgrade to PBS 3.2-4.

    can't even load a tape and format it. Get same "Error: this program needs to be run with setuid root" as above.
  9. B

    Tape Backups Fail After Upgrade to PBS 3.2-4.

    Tape backup jobs now fail since upgrading to pbs 3.2-4 last week: 2024-06-22T14:00:00-07:00: waiting for drive lock... 2024-06-22T14:00:00-07:00: Starting tape backup job 'pbs2-primary-140tb:pve-tapes:lto8:weekly-tape-backup' 2024-06-22T14:00:00-07:00: task triggered by schedule 'sat 14:00'...
  10. B

    proxmox-backup-server 3.2.4-1 tape jobs (format and write) fail

    Our first tape job since updating pbs last week is showing same: 2024-06-22T14:00:00-07:00: waiting for drive lock... 2024-06-22T14:00:00-07:00: Starting tape backup job 'pbs2-primary-140tb:pve-tapes:lto8:weekly-tape-backup' 2024-06-22T14:00:00-07:00: task triggered by schedule 'sat 14:00'...
  11. B

    [SOLVED] "unable to acquire lock" / "tried creating snapshot that's already in use"

    Thanks. Yes, I should have been more explicit. It's clearly the verify job conflicting. I'm just surprised that a snapshot that has already been synced across the previous night (and is now being verified) is being re-opened by the current sync job prior to syncing across the newer snapshot...
  12. B

    [SOLVED] "unable to acquire lock" / "tried creating snapshot that's already in use"

    Hi All, Is this expected behavior? PBS1 is our older pbs server that was removed to a remote site. Its sole function is to nightly reach out to our newer (PBS2) server and sync its datastore to itself. PBS1 then also runs its own verify jobs on the datastore it then holds. PBS1's sync log...
  13. B

    no catalog written to tape

    Well, I think we can call this a fluke or a test that went awry (perhaps due to the HBA issue that threw my processes (etc.) askew). I repeated my test scenario just now, using the last three weekends of written tapes as well as the original tape from the weekend where the catalog wasn't found...
  14. B

    no catalog written to tape

    One note: We had an hba that proved untrustworthy early on when we first imported the encryption key and did the intitial inventory. With the info provided above (thanks!) I now find myself focusing on this (which I had forgotten about). I now suspect things got into an odd state (the content...
  15. B

    no catalog written to tape

    Will do! In positive news, the manual re-cataloging succeeded overnight. It's an LTO8 tape so it took 11 hours. I'll follow up here as well if there's any further information to share (as well as bug report).
  16. B

    no catalog written to tape

    Odd. I can confirm that the backup job finished normally. I received the email from PBS stating the job was successfull and which tapes were used. I'm looking at it now (just to double-confirm). So, I guess it's a mystery and hopefully just a one-off fluke. I might be able to try to...
  17. B

    no catalog written to tape

    Hello All, I'm trying to be diligent in that I am currently simulating a "total loss" and trying to restore from our pbs tapes with only the tapes, our tape library, and a blanked server. I have installed pbs to the blanked server. I have connected the tape library and imported the tape...
  18. B

    Purchasing a Server Exclusively for PBS (hardware discussion)

    Well, it is a backup server, after all. We would still have the data on the live servers. And we backup to tape weekly. Given this, purchasing a second server seems extravagant. While safeguarding data is paramount, at some point, diminishing returns and budgets do matter. Apologies. I...
  19. B

    Purchasing a Server Exclusively for PBS (hardware discussion)

    Hi Fabian, Apologies for the huge delay in responding. Other things came up but we did finally get our new hardware and I'm getting ready to put pbs 3.0 on it. I'm jostling this thread awake again just in case others making a similar decision/purchase find it useful. We ended up with twelve...