Search results

on the screen the enp2s0 don't exist, so you can't add this card to the bridge. you only have enp1s0f0,enp1s0f1,enp1s0f2,enp1s0f3

I have replace my cluster of 3 x (Intel Apollo Lake N3450 8 Go ), with one N5105 with 32Go. So far i have no crash of the Hypervisor itself with stock kernel ( uptime 10 Hours), but i have perhaps one Vm ( container with bitwarden) with probably the same problem as bobbyrc. The VM crashed, and...

the conf : /etc/vzdump.conf tmpdir: i think you can see the path il the log of the backup job something like that: INFO: Upload config file '/var/tmp/vzdumptmp290473_175/etc/vzdump/pct.conf' i think the default tmpdir is /var/tmp , but you can change itin the /etc/vzdump.conf file

And the tempory folder like smecio said ??

Mdadm is the software raid. Do you have a raid over the iscsi disk? The iscsi lun is bootable? The network card is in the boot order in the bios? You use ipxe?

i have this running right now. Proxmox installation over a debian on boot on San ..Now piece of cake , you can directly install debian on isci Lun with the debian installer. for the record i use Pfsense for the the dhcp serveur / tftp / ipxe file..

Like l said it's my computer(workstation) @ home ...;) Whenever the method you use, giving the power to shutdown proxmox is a bit of risky

I use this command on my personal workstation on proxmox ( VM linux mint on passtrough ) : ssh -l root ip_du-promox- /usr/sbin/poweroff Works like a charm.

scp , can be a way if ssh is enable on the two container...

i have this when a try to dump my bios : root@n5105:/sys/devices/pci0000:00/0000:00:02.0# cat /sys/devices/pci0000\:00/0000\:00\:02.0/rom > /tmp/vbios.dump cat: '/sys/devices/pci0000:00/0000:00:02.0/rom': Erreur d'entrée/sortie any idea ?

Bonjour, i have the same problem. as you. Have you find a solution ?

do you add the module at the end of the command sensors-detect ? you should have something like this in /etc/modules : root@proxmoxsan:~# cat /etc/modules # /etc/modules: kernel modules to load at boot time. # # This file contains the names of kernel modules that should be loaded # at boot...

i try now with discard option on, and it's working again. thanks for the patch.

i think by default , the program mdadm isn't install by default . Perhaps it's a better idea to mount the disque on another pc, and copy the data via the network But you can install with apt-get install mdadm

I install the lastest pve update ans the qemu package of the test repository glusterfs storage to glusterfs storage create full clone of drive scsi2 (SSDinterne:170/vm-170-disk-2.qcow2) Formatting 'gluster://10.10.5.92/GlusterSSD/images/170/vm-170-disk-0.qcow2', fmt=qcow2 cluster_size=65536...

i try to pass the patch tonight

Il you have only 2 server for Glusterfs, if one server is down, or communication between the twoserver is down , you are in split Brain. for the split brain try this : gluster volume status you see something like this. You should have a "y" on every line root@p1:~# gluster volume status...

Thanks for the reply. I waiting for the patch.

Well it's not stable. The discard option is off . i was trying to remove the sbapshot before the update : May 06 23:00:16 p3 pvestatd[1312]: status update time (11.471 seconds) May 06 23:00:21 p3 pvedaemon[253908]: <root@pam> starting task...

well , without the discard option, i was able to update the VM, without any crash. with the discard option "on" i had this in the log : May 06 21:06:30 p3 pvestatd[1312]: status update time (11.371 seconds) May 06 21:06:42 p3 pvestatd[1312]: status update time (11.521 seconds) May 06...