Recent content by Adam Talbot

root@RPi4-01-PVE:/etc/pve/lxc# cat 100.conf arch: arm64 hostname: RatOS memory: 2048 net0: name=eth0,bridge=vmbr0,hwaddr=9A:D9:50:59:6C:7D,ip=dhcp,type=veth ostype: debian rootfs: vmfs:100/subvol-100-disk-0.subvol,size=0T swap: 512 lxc.net.0.type: phys lxc.net.0.flags: down lxc.net.0.link: can0...

Way off the deep end here. Trying to figure out the Proxmox way to pass GPIO, and can0 (canbus nic 0) into an LXC container. Proxmox is running on a raspberry Pi 4. Can0 is comming in over the SPI (spi0.0) bus. Thanks

Off the deep end. Installing ProxMox on a Raspberry Pi to run a few LXC containers. Don't want ZFS. Don't need Ceph or qemu. Is there a clean way to 'apt install proxmox-ve --dont-install-zfs'? Or something to that effect?

Just figured I would document my saga of using BTRFS with Proxmox. This saga is over two years of experimentation and ripping out much of my hair. My system: Disks: 10X SSD's, Toshiba HG6 Enterprise class 512GB SSD's. CPU: Ryzen 7 3700X Motherboard: X470D4U RAM: 32GB DDR4 ECC Proxmox 6.1...

System just hard froze, with ZFS this time. Going to assume its a hardware problem.

Reinstalled 6.0... Problem still remains. Read through "https://forum.proxmox.com/threads/proxmox-with-zfs-or-btrfs.50962/". A lot of hear say and conjecture. No real data. Not interested in ZFS as it's lacking reflink support. I just enabled netconsole, and for that matter, serial...

Working under the assumption that I was having some bad interaction between BTRFS and VM's I pulled the VM storage (vmfs) off of the BTRFS volume. After a clean reboot system still hard hung with in 5m of btrfs scrub started.... I am running out of ideas. Might need to fall back to proxmox 6.0.

Not sure exactly whats going on here. I have 10X SSD's in a BTRFS RAID6 configuration. When ever I start a scrub, the whole system hard freezes. Like the blinking cursor stops blinking. I get no kernel panic, or anything to go on. PVE 6.0 did not have this problem. I have rebuilt this...