Search results

You might have deduced from the info I gave in OP that this isn't my first rodeo. Nevertheless, thank you for having added something which you might consider valuable to this thread.

That's what I was thinking, and that's why I had included lsblk output in my OP. I do have external backups of all clients, I'll just need to read up on backing up the host config files because that is going to be a pain to manually reconfigure from scratch. No way of adding the missing...

edit : solved, reinstalled the OS. The "how was this possible" remains. Hi all, I have an rpool, created at Proxmox installation time. Install was about 4 weeks ago from the Proxmox iso. The pool is a 2 disk mirror. After a powercut, the server won't boot, just stays on black screen with an...

I don't get it... 1. create the CIFS storage type, let's say device NAS, share Data 2. create a Directory type ?? what would be the path for this Directory so that backups go into //NAS/Data/Backups ?

I've made small changes to the Notification section of your script, using /usr/bin/pvemailforward makes it a bit more `standard` in proxmox , and added a tag (-t) for logger which helps finding messages in syslog. if [ "$problems" -ne 0 ]; then logger -t "zfs status notifier" "$emailSubject...

This does not work and throws errors in syslog : smtp_header_checks = pcre:/etc/postfix/smtp_header_checks . #for outgoing changes only "smtp". This works without errors : # for outgoing changes only "smtp". smtp_header_checks = pcre:/etc/postfix/smtp_header_checks

The custom From: should be # for outgoing changes only "smtp". smtp_header_checks = pcre:/etc/postfix/smtp_header_checks

Thank you to @t.lamprecht for pointing me/us in the right direction. A little experimentation showed me that adding post-up /sbin/ethtool -s enp2s0 wol g only to the vmbr0 interface is sufficient.

this seems to still be a thing ?

...move it over, being : root@pve2:/etc/pve# mv ./nodes/pve/lxc/203.conf ./lxc/203.conf After which the LXC should be present in the web interface.

Can I understand that the container doesn't show up on PVE2, because PVE (the originating node) is still in the cluster ? And, if for some reason (artificial or accidental) PVE disappears, then PVE2 _will_ offer up it's last known version of the replicated LXC ? Indeed the snapshot did...

Hello, I'm trying to get Replication working between 2 PVE nodes. (I also have a Raspberry Pi in the network configured as Qdevice.) After doing a replication, the LCX doesn't show up on the other PVE, see image : What am I missing ? This is the log output of my first attempt at...

Thank you for thanking :p ... aka thankception. Yes, it certainly was. Because I was able to cat /zfs-pool/subvol-104-disk-0/etc/debian_version. That would otherwise have thrown an error methinks? I can not be 100% certain, I think it appeared after. Because I did cp /etc/pve/lxc/104.conf...

Hi all, I force-stopped a non-responsive container, and now it won't start. Have searched for something similar, but the search-results don't apply to this case. Any input greatly appreciated !!

sorry, i neglected to mention in here that i did also move/rename the file /etc/zfs/zpool.cache as well as enabling the service.

i fully agree that the main problem resides between the chair & the keyboard. Still, enabling the service made the difference between containers starting at boot or not starting at boot.

hello everyone, having some kind of issue starting a LXC, I am having trouble analyzing the logs to pinpoint exactly what is happening here ? Any thoughts ? Mucho Gracias in advance ! lxc-start -n 103 -F -l DEBUG -o /tmp/lxc-103.log https://paste.ubuntu.com/p/P8sFVG2jQF/

I know that now...i didn't when I first created the pool, and the tutorial I was following didn't use long aliases for drives / partitions. On the bright side, the issue seems solved through help from the ZoL mailing list. fwiw, and for posterity, here's the thread ...

errr... given that i know that I put the zfs cache into a partition of the SSD , and given : root@pve:/etc/default# zpool history History for 'zfs-pool': 2018-10-10.16:41:27 zpool create -f -o ashift=12 zfs-pool raidz /dev/sda /dev/sdb /dev/sdc /dev/sdd cache /dev/sde5 log /dev/sde4 and...

but both must be related, surely ? Since doing "zfs mount -a" allows pve-container@100.service to start without errors.