Search results

  1. F

    Kernel Panic, whole server crashes about every day

    hey, not my achievement, just took my time to search the webz. if you can afford to have another crashes for sake of testing, please, set your bios first to defaults and then _only_ set following options (or equivalents for your bios)...: SVM = enable (virtualization aka vt-d in intel world)...
  2. F

    Kernel Panic, whole server crashes about every day

    look kern.log if you have something like this: mce: [Hardware Error]: Machine check events logged mce: [Hardware Error]: CPU 15: Machine Check: 0 Bank 1: bc800800060c0859 mce: [Hardware Error]: TSC 0 ADDR 41576d480 MISC d012000000000000 IPID 100b000000000 mce: [Hardware Error]: PROCESSOR...
  3. F

    Kernel Panic, whole server crashes about every day

    My nodes with Ryzen 5800x, 5900x and 5950x crashed all the time (at least once per day, with or without load, even w/o a single VM/CT on them) with PVE 6.4 both kernels 5.4 and 5.11 and PVE 7.0. after disabled C6 state, all of them are now running rock solid since weeks. The troubleshooting was...
  4. F

    Kernel Panic, whole server crashes about every day

    Have you disabled C6 state in your bios/uefi? In my case this helped with Ryzen 5800X on a Gigabyte X570 board and Kingston ECC unbuffered RAM. For me it is the setting: Power idle control: Typical current idle. Could be different on your specific mainboard.
  5. F

    PBS tape backup - various questions

    Hello dear Proxmox-Team, i am still playing around with tape backup, currently with LTO-4, but even if i would invest considerable money into a LTO-8 (i would better put the money into a proxmox subscription), i would still hit the same questions, since the data amount is growing. - a quote...
  6. F

    Cloning a template to another host in the cluster

    ah, yes, right. if i remember correctly, migration between local storages was implemented in PVE6.2, but i don't know, if it was also implemented into the cloning process.
  7. F

    Cloning a template to another host in the cluster

    this is why it takes longer to clone a template to another host. the data is really transferred between the hosts/storages then. btw. you can't create a linked clone, only full clone in your storage setup.
  8. F

    Cloning a template to another host in the cluster

    You have a full cluster including Ceph or a pool wide shared storage? Or is it a PVE pool with local storages per host?
  9. F

    decode element status failed - failed to fill whole buffer

    for sure all thanks are to you and ofc. all in the proxmox team who do a lot of work for such amazing products :)
  10. F

    decode element status failed - failed to fill whole buffer

    i would like to add here, that HP/E has always and everywhere firmware issues (firmware issues are a common problem with any HP/E hardware, old or new). so i hope your efforts were not only useful for commodity hardware as mine (msl2024 + lto4), but will also have a positive impact on modern and...
  11. F

    decode element status failed - failed to fill whole buffer

    It works now perfectly! at least the previous "short" tasks like reload and clean drive. i will test everything (backup etc.) out and report later. Thank you Dominik! Edit: so far everything is good. first backup job is running since 22 hours, is at 45%, tape 9, speed is good. will take...
  12. F

    decode element status failed - failed to fill whole buffer

    i analyzed the returning data from library (sg_raw -r 64k /dev/tape/by-id/scsi-DEC80205XR B8 11 00 00 ff ff 00 ff ff ff 00 00 2>&1 | tee -a /root/test2.txt) in expected probability of repetition as the error/panic happens, the retuned data is full 64kB (65536 bytes). but all those extra bytes...
  13. F

    decode element status failed - failed to fill whole buffer

    compiled again from master branch, now pmtx does following:
  14. F

    decode element status failed - failed to fill whole buffer

    yes, sorry, something went wrong copy pasting. with mtx command no errors
  15. F

    decode element status failed - failed to fill whole buffer

    Thanks! no errors with mtx -f /dev/tape/by-id/scsi-DEC80205XR status
  16. F

    decode element status failed - failed to fill whole buffer

    yes, the package is installed. indeed, it looks like the tape library has some issues. if it would help, i can add your ssh keys and open it in the firewall. but the question is, is it worth to waste your time on that? for me this is not productive, just play to learn (and maybe for later use...
  17. F

    decode element status failed - failed to fill whole buffer

    the sg_raw commands return different, if issuing them multiple times. https://pastebin.pl/view/d61cb8c4
  18. F

    decode element status failed - failed to fill whole buffer

    # pmtx status --changer msl2024 using device /dev/tape/by-id/scsi-DEC80205XR Transport Element (Griper) 0: Empty Data Transfer Element (Drive) 0: Empty, Serial: HUE08455BM Storage Element 1: VolumeTag("PBS001L4") Storage Element 2: VolumeTag("PBS002L4") Storage Element 3...
  19. F

    decode element status failed - failed to fill whole buffer

    thanks! i suspected, that i was doing something wrong or have not fullfilled all needed dependencies. so i removed all rustc and dependencies which i installed previously, then recompiled exactly as in the documentation and build notes you posted above. still got same error. now i have seen...