Search results

  1. G

    Can´t run my homemade script in PVE 9.0 but works fine on PVE 8.x

    Nobody will guess your script's content, where is sed command to adjust.
  2. G

    Taking app aware backups on veeam

    +1 , like other backup vendor which runs "within" guest.
  3. G

    Taking app aware backups on veeam

    Freeze/thaw invokes same VSS writers within Windows Guest, same as Veeam or others backups vendors. Just set VSS_BT_COPY into Registry , if chained/differentials SQL backups exist within Windows Guest, to prevent breaking the "LSN chain"...
  4. G

    Poor NFS Performance To TrueNAS Share

    :eek: Crucial BX500 are the slowest disks you can find, they writes data slower than HDD, except the first GBs, they use QLC flash. Running ZFS over these is the best to test the worst case. EDIT: I don't see network problem as iPerf show 9,3 Gbits/s for your 10Gb network as excepted.
  5. G

    Security of firewall rule to block LAN communication

    There isn't vulnerability in drop rules firewall, except human error configuration as always. Overriding this is not possible within VM/Guest.
  6. G

    Inaccesible boot device

    indeed. it's something else. I don't think it's boot manager as we can see Windows Boot Manager in #9 Weird thing is VirtIO SCSI Driver offline installation was successful in #11 (so screenshots of Log are pointless) where in #9 not. Try now detach/attach boot disk as scsi. By the way, it's...
  7. G

    Inaccesible boot device

    if works, edit title of your first post to SOLVED
  8. G

    Proxmox web UI memory leak - starts at 200MB, gradually increases to gigabytes

    try with Chromium based browser instead Firefox based or vice-versa.
  9. G

    Inaccesible boot device

    Check if drive contains Windows. Like dir c:\ /a Check log notepad X:\Windows\Logs\DISM\dism.log
  10. G

    Inaccesible boot device

    you need to assign letter yourself. it's Windows things : Within diskpart, select volume Number then assign letter
  11. G

    NTFS data corruption in windows VMs

    Try "Fleecing" PVE option backup https://pve.proxmox.com/pve-docs/chapter-vzdump.html#_vm_backup_fleecing or Try disabling VM backup to PBS for a day.
  12. G

    NTFS data corruption in windows VMs

    is after a backup to Proxmox Backup Server ? is Proxmox Backup Server located on LAN ?
  13. G

    Inaccesible boot device

    it's not mandatory. VirtIO SCSI driver cannot be "pre-installed", it's installed only within Windows running on PVE when a SCSI drive is present / attached. That's why the recommended way is boot once with sata, to post install VirtIO SCSI driver with a dummy temporary SCSI drive attached. You...
  14. G

    Inaccesible boot device

    if sata/ide cannot boot into Safemode, I would retry the "migration", how did you do ?
  15. G

    Inaccesible boot device

    You need to boot into Safemode, once, which re-enable standard ide or sata/ahci drivers.
  16. G

    NTFS data corruption in windows VMs

    Proxmox Backup Server used ? VirtIO scsi Controller Windows driver version ? double check version from Windows Device Manager, has to be v266+
  17. G

    dhcp Server issues

    https://forum.proxmox.com/threads/dhcp-server-issues.168876/post-786201 it's pointless. "interfaces" means content of /etc/network/interfaces and please copy/paste into CODE tags.