Search results

  1. K

    Problem Update Kernel 6.8.12-4-pve / No Boot

    Interesting. I've always read Proxmox was package compatible with Debian. Good to know it's not: I still think they are speaking of apt-get upgrade rather than apt upgrade breaking things, but I digress. Edit to add: But it will be if you use the correct apt dist-upgrade So what are you...
  2. K

    Problem Update Kernel 6.8.12-4-pve / No Boot

    apt upgrade would only break your system if the package dependencies were wrong, which could happen I suppose but is unlikely. Worst case you'd end up with a partially updated system. The behavior between apt upgrade and apt-get upgrade does not seem to be consistent. See: apt -s -V upgrade...
  3. K

    Problem Update Kernel 6.8.12-4-pve / No Boot

    apt upgrade / apt dist-upgrade is fine.
  4. K

    Migrate installed proxmox to new hardware - ZFS pools

    I've not come across a desktop board that supported UEFI but not CSM, so you should be fine as long as you set it correctly. Worst case I think so yes it will just fail to boot. I can't think of any reason it would hurt anything, but that doesn't mean one does not exist ;-)
  5. K

    Migrate installed proxmox to new hardware - ZFS pools

    You said you had 2 pools, I only see one in the screen shot but yes, it is using disk IDs. Going from Intel to AMD shouldn't cause issues outside of different platforms having different quirks you may need to work through, same as a new install. If the old system is not UEFI then you would need...
  6. K

    Migrate installed proxmox to new hardware - ZFS pools

    As long as: - The current kernel supports the new hardware - The ZFS pools are using disk IDs - The boot mode is the same (BIOS vs UEFI) - The disk controller is an HBA on the old and new servers * Anything else I'm overlooking ;-) You should be able to just move all the drives to the new...
  7. K

    Memory spikes win 2022 trying to defragment a 1TB disk

    This was solved in the thread linked to in post 6
  8. K

    Windows VM requires lots of ram to trim larger hard disks

    Apologies if this has been posted elsewhere, I could not find it. Describes the issue in detail and how to fix: https://www.alldiscoveries.com/how-to-fix-high-ram-usage-during-defrag-on-windows-server-virtualized-with-qemu/
  9. K

    [PSA] ZFS Silent Data Corruption

    From: https://github.com/openzfs/zfs/issues/15526#issuecomment-1826476737 robn commented: "@admnd I am 100% certain that zvols on Linux are not affected. On FreeBSD I'm 99% certain" I would love a 2nd opinion, but based on this it would appear zvols should be ok?
  10. K

    proxmox 7.0 (failed to prepare EFI)

    PowerEdge R510 The solution for me was to set the NVRAM clear jumper, power the server on, let it post, power it off, move the jumper back. It seems on some (Dell at least) servers, removing UEFI boot entries doesn't completely remove them, and the UEFI storage eventually fills up, which is...
  11. K

    Cron Schedule

    Ahhh ok, than you sir! I thought I was missing something ;-)
  12. K

    Cron Schedule

    Just did a fresh install of PVE. Going over the stock cron jobs I found this: In /etc/cron.d/zfsutils-linux # TRIM the first Sunday of every month. 24 0 1-7 * * root if [ $(date +\%w) -eq 0 ] && [ -x /usr/lib/zfs-linux/trim ]; then /usr/lib/zfs-linux/trim; fi Actually works out to the...