Search results

In the photo I can see exim4. Proxmox itself uses Postfix, not Exim. Is your system a standalone Proxmox or Proxmox on top of Debian?

You're right. Being in hurry, I misread the docs. I've got a thought to setup at 23:59 some simple cron job like ls /mnt/pve/barracuda to wake up your disk, but as you've written that you already have other job at 23:59 so the disk is already spinning at 00:00, I'm out of ideas :confused:.

cifs: barracuda path /mnt/pve/barracuda ... subdir /backups/docker ubuntu I wonder if this /backups/docker ubuntu shouldn't be escaped somehow? I mean the space inside. Maybe /backups/docker\ ubuntu or in quotation marks "/backups/docker ubuntu" ? Just guessing... Edit...

Thanks. Maybe the log of the backup job (without secrets, if any) in the SPOILER tags will give some trace...

Welcome! 1) Please post the definition of this storage. 2) The full command of the backup job. 3) Is the share actually mounted? 4) What is in /mnt/pve/barracuda ?

Are you, by chance, using a VLAN in Proxmox?

How, in detail, have you tried? What options? What was the output?

Possibly an IP address conflict. So I would start from checking IP addresses and routing.

Seems like some firewall is blocking the connections to port 8007. This must be fixed first :). Edit: Johannes S' remarks to let and use the connection in the opposite direction are correct.

Have you verified that this connection is let through? E.g. what does telnet 192.168.X.X 8007 return?

Are there any power-saving features enabled in the hardware setup? If yes, try disabling them. This is usually recommended. For instance I have found a report of similar issue which was caused most likely by ASPM [0]. I don't know if it can be disabled in the setup. If not, try to disable it in...

Disclaimer: I haven't tested this with real chunks! Using it is your risk ;) To answer your question: it depends whether you mean "chunks" as real chunks (files in directories) or directories themselves. For reference, my directories with chunks are in the directory /pool1/store1/.chunks In...

My Maybe because ....242 is not the correct beginning of a subnet. Have you tried e.g. https://www.calculator.net/ ?

I think you mean the smart idea described e.g. by @Cookiefamily in the thread "Copy backups to external drive" from year 2021 :) https://forum.proxmox.com/threads/copy-backups-to-external-drive.88791/post-389048

In Proxmox servers it's always recommended doing apt full-upgrade, not just apt upgrade. What happens if you execute it now?

You might not doing anything wrong :) . I wonder what is this above sdd disk sized 0 bytes... If these four disks are connected to that LSI card, I would check if the card has any "BIOS" / setup menu that can be entered into during the bootup of the server. And whether this fourth disk is...

I don't know Proxmenus, but I've found in its auto_post_install.sh that one of its "optimisations", khe-khe... is "Subscription banner removal". Tools which mess with the GUI often lead to problems like yours! I suggest you remove it and check if that helped. If not, repeat apt install...

And?... If it still doesn't work, another possible reason is: have you installed ANY tools / "improvements", unofficial software in your PVE host?

No, it isn't ;-(. THIS is in the CODE tags: root@proxomox:~# ls /dev/disk/by-id/ ata-WDC_WD5000AAKS-00YGA0_WD-WCAS83703777 nvme-INTEL_SSDPEKKW256G7_BTPY70130Q7M256D_1-part1 nvme-INTEL_SSDPEKKW256G7_BTPY70320X23256D-part3 And having lsblk output could help us to understand the issue...

This was one of my suspicions and that's why I asked for df -hT :) Yeah, one of Systemd "innovations" in the way devices are tried to be mounted during start of a machine... :p