Recent content by fortechitsolutions

  1. F

    [SOLVED] Proxmox 8.3-1 cant detect disks with LSI MegaRaid

    Hi Just a followup on this thread, I was kicking away at this server recently, a few weeks ago tried to boot newer kernel after doing updates to proxmox 8.x.latest > so it is now proxmox 8.4.11 version and the latest kernel it has available is kernel 6-8-12-13 I believe so > it seemed to boot ok...
  2. F

    Q: weird problem after upgrade Prox7>8 / Boot newer kernel - "alert! /dev/mapper/pve-root does not exist" - not bootable

    Hi Everyone, I am just posting a followup on this thread from earlier in the year. Wanted to 'close the loop' on this topic I had work-around in place previously - just pinned older good-working kernel - was ok I did more updates this week, and had some available maintenance window over the...
  3. F

    Q: Aug-2025 new problem - Win10/11 VM Boot Drama / BSOD / Unbootable

    Hi, this is a bit open ended but I wanted to put a post in the forum in case anyone else bumps into this. I had my second proxmox server this week give me a similar bit of unhappy drama, which is very unusual. My solution in both cases ended up being "nuke the VM, restore from last good backup...
  4. F

    Live migration zero downtime

    yes, and note that HA is different - superset - from "pair of nodes in cluster" or even "three node in cluster". original question was asking about live migration. :-) anyhow. I agree, if doing a 2-node cluster you really do want to have a 3-node or a 3-node plus quorum-breaker-service on...
  5. F

    Live migration zero downtime

    I just wanted to chime in, I agree that 2 node cluster live-migration is possible, but having 3 nodes or a 3rd 'witness / QDevice' is nice if possible. But not mandatory. Tim
  6. F

    Q: weird problem after upgrade Prox7>8 / Boot newer kernel - "alert! /dev/mapper/pve-root does not exist" - not bootable

    Ok, thanks for added detail. This is 'weird' because - this setup is very (very) vanilla - stock proxmox ISO installer was used originally for deployment. It has been through a few in-place upgrades over a ~few years but nothing problematic with that normally. Hardware is ~plain (lenovo, stock...
  7. F

    Q: weird problem after upgrade Prox7>8 / Boot newer kernel - "alert! /dev/mapper/pve-root does not exist" - not bootable

    HI, thanks for suggestion. I had not tried the InstallerISO>Rescue option. In theory I can try that as an Edu piece. Might be good to see what it tells me. I am not super keen to do a reinstall 'just to see how it goes'. But it is indeed an option to try I suppose. I do have this proxmox...
  8. F

    Q: weird problem after upgrade Prox7>8 / Boot newer kernel - "alert! /dev/mapper/pve-root does not exist" - not bootable

    Footnote on the thread, I did a bit more dig in forum, and found this discussion which sounds very much maybe like the right thing possibly I need to chase. https://forum.proxmox.com/threads/proxmox-8-3-1-cant-detect-disks-with-lsi-megaraid.159858/ So I'll give that a go sometime - looks like...
  9. F

    Q: weird problem after upgrade Prox7>8 / Boot newer kernel - "alert! /dev/mapper/pve-root does not exist" - not bootable

    Hi, small fun question I wonder if anyone has any thoughts on. I've got a ~decent box at a client office - it is not latest hardware - was deployed as a 'refurb' lenovo tower server box, dual socket xeon, 96gb ram, megaraid hardware raid It was originally deployed as Proxmox v6 when that was...
  10. F

    Q: PBS and LXC container backup speeds

    Hi, thank you for this added info. I agree, it is not fast. (ie, ~>24 hours to do a full restore). I believe it is acceptable for the recovery time for this client. Drama for backup - I don't have enough free space local cache to do tempdir - suspend mode. So I am kind of stuck here with my...
  11. F

    Q: PBS and LXC container backup speeds

    arrgh, sorry chris. I am re-reading thread now and I see I had missed your one point. a few posts back. You are suggesting the job on Jan.26 ran successfully and fast, without metadata mode. And it took ~2 hours approx. And then I am trying to do metadata backup jobs since then. I was under the...
  12. F

    Q: PBS and LXC container backup speeds

    Hi Chris, thank you. So just to check and to clarify. 1) Right now my deployment model, is to setup a new PBS host any time I setup new related proxmox/cluster requirement. This gives me clean separation of resources (ie, disk, bandwidth, CPU-RAM) between any given Proxmox cluster and PBS that...
  13. F

    Q: PBS and LXC container backup speeds

    Apologies to those reading this / for my use of sloppy syntax in this thread, ie, I'm calling things here in this thread a "VM" when that means precisely a KVM VM and that is definitely not remotely what I am trying to talk about here. I am speaking only of "Container LXC based guests" and I was...
  14. F

    Q: PBS and LXC container backup speeds

    Hi Chris, I am still confused, for clarity. In this situation I have one proxmox cluster, one backup config panel for this cluster and three jobs exist therein. I have 7 proxmox node inside this cluster they all talk to the one PBS host there is no 'standalone proxmox host' which is outside...
  15. F

    Q: PBS and LXC container backup speeds

    Hi, here is view in PBS for VM101, not sure if this gives insight about anything. The jan-26-2025 is my last good backup, which is this snip view below. As I generated this snip, I also wonder - is there maybe a timeout on client site <> PBS Client <> talking to PBS server <> which allows it...