Hello, If there are really no drive bays, I'd look at a BOSS-S1 card for the R640. It takes two M.2 SATA drives in RAID 1 and is made exactly for booting. Even a small SSD on the internal USB port would last longer than microSD, Proxmox writes...
Technically yes, but you will not have a lot of fun with them and they will fail.
why a cluster when it will not be running 24/7? Makes no sense.
Install the OS on your raid disks and don't bother with microSD card install, problems and...
There are lots of small writes (e.g. to log files) and lots of filesystem flushes that really hurt your media's lifetime. Even seemingly benign operations can easily generate gigabytes worth of write operations. Fortunately, if you aren't running...
I just found this thread after putting together my own high availability solution for home assistant, zigbee, and z-wave. In case it helps: https://github.com/yuvaloren/ha_zradio
If this is managed by UCS Manager, I’d start with your Linux profile. Check that the boot policy can start the Proxmox ISO from virtual media and then boot the disk or SAN LUN you plan to install to. If that profile is assigned to another blade...
We’re developing this in the open because, once it reaches GA, we’ll submit it upstream as a full pull request. As a Ceph Foundation member and an employer of upstream maintainers, we’ve always merged our code upstream, and pushing upstream...
alexskysilk's RBD route is worth testing for that 8 TB SQL VM, but I'd keep the SQL log chain as the consistency mechanism: restore a crash-consistent RBD snapshot or replica as the base, start SQL, then apply native log backups. That avoids the...
Worth adding: after pulling the fixed package from oldstable-security and rebooting, check `uname -r` actually shows the newer 6.1.0-XX ABI rather than the old one, then undo whatever GRUB workaround was used (temporary default entry, pinned...
There wouldn't be much of a point if you don't know the actual origin of open connections since the community script by design pull further components from github. Maybe one of them updates their software that way? I never bothered to read the...
@Johannes S is correct, the traffic can also be generated by any of your VMs or LXCs. I mistakenly presumed that you have already excluded those by shutting them down.
Potential next steps are : a) shutdown VMs and LXCs, either one by one or all...
Since the whole host dies, try to capture logs off the box first: serial console or netconsole, plus pstore/ramoops if available. Then limit Immich and Jellyfin to one concurrent transcode and test. Also test CPU-only transcoding with the Arc...
So, this is a catch 20/20 issue, It's Debian changing named.service to use a Type=notify, and Proxmox VE 9.x including AppArmor 4.1 which has incomplete support and thus issues for this specific setup.
The ultimate "fix" is an override for named...
Hi @tillin9 , welcome to the forum.
It would be great if you could:
a) add your storage configuration (cat /etc/pve/storage.cfg) as text encoded with CODE tags
b) add output of "pvesm status" from source and destination nodes
c) present exact...
Have a test cluster with 3 nodes. 2 of the 3 have shared storage off an old SAS (IBM StorWiz) array. Running into an odd issue when trying to migrate a VM from then shared storage (which migrates fine between the 2 nodes with the shared storage)...
For testing the extension on Proxmox, click the noVNC console first so the keyboard input has focus; otherwise the synthetic keydown events may go nowhere. Also test shifted and special characters separately—sending keydown with `key` alone may...
I only used it once or twice, because you really don't need it if you do everything in the beginning "correctly" - after stumbling over repytr of course. I had the same learning curse as you have, but in the end the lessons to take away was...
Reporting the same issue. The same error was produced when trying to install 9.2.1, but the 8.4.1 installation was fine.
Update: solved my issue by adding intel_iommu=sp_off to the grub menu on 9.2.1 installation.
issue should be fixed by upstream now: https://tracker.debian.org/news/1824723/accepted-linux-61192-2-source-into-oldstable-security/
(did not test it explicitly)