Search results

Hey, drop here your /etc/network/interfaces file here

on pve host, please post the output of "fdisk -l" ans the return of cat /etc/fstab

Want to say /etc/fstab I think x')

ahahah xD it seems your renter have a rewriting of your vps. for bypass that, search how do install proxmox with a hosts line like: 127.0.1.1 pve.fqdn pve

Hey, how did you have initiated your disk?? you haven’t any gpt schemas on your vdisk

i'm 8.2.4 with a VM truenas with qemu 9 :)

hey, Can you be more explicit about your final goal ? Switching from baremetal to virtualized services is, alone, a long road, where you need to don't have problem with tests. Many backups are your key for fully enderstand your stuff manager withoutt risk of any loose of datas.

Truely enderstandable :) But passing through your disk more stable :) It's my actuel truenas configuration :)

Did you have declared your mountpoint with uuid partition ? If not, do that before all.

Hey, YEs, select for your virtual processor "host" configuration. In your "options" tab of your VM, uncheck "KVM virtualization".

Hey :) @crc-error-79, why passthrough your sata controller when you can passthrough your physical disks to your Nas VM?

You can passthrough your NIC cartd in your material virtual stuff VM. With that, you can "unload" the physical NIC of the hypervisor, and use it like physical stuff in your VM. Like that, you can create your VLANs without OVS and simply use it with the interface.vlan# network configuration...

TY for the tips !!!!! :O

hi, before all, try another usb port, idealy with another usb controller. If was on USB3 port, try it with usb2. Problem encountered before, with usb JBOD 4 hdd 18To each. Solved via forcing usb2 usage. ( sufficient for my use case, see if good for U :)

not sure about this approach. This gonna just add 12To to his stripped pool, without convert to mirror. @Por12 , you just have 2To of used data on this pool. The best way is to snapshot the dataset and save it (on a temporary stripped pool or in a file, destroy your zpool, and re-create it...

hi, Proxmox need some pre-configuration of your debian install before you can properly install on top of debian. Please follow the proxmox process install completly :) https://pve.proxmox.com/wiki/Install_Proxmox_VE_on_Debian_12_Bookworm

hey, try to update your bios. Proxmox kernels calls last virt libs, that need a good version of your bios

Hey, Many of you seem's to see problems after upgrade to newer kernel. Did you tried to upgrade BIOS/UEFI before posting here ? :) I'm in the intial post configuration, with more cuonsumer stuff than the inital tread autor. Problems that's you're experiencing was mines before uopgrade my bios...

Hey :) Haven't chirugical idea about your ethernet card Mellanox. But, for deeply test of this hardware, a crashtest solution can be: Create a VM(use Os of your choice) Before boot them, PCI Passthrough the medllanox NIC (comment her in interfaces file PRIORLY) See how she's detected in you...

small question about security section, but, if you wanna do that more deeply, can I suggest you to passthrough NIC to pfsense VM directly? That permit more flexibility about vlan configuration, without the use of OVS :)