Search results

Hey! First of all, it's really difficult to find a standard solution to a non-standard situation. As far as i understand, the issue lies in the fact that after the unexpected power-down event, the Fusion-Io card goes into a self-diagnose mode that may take like 15 minutes to finalise, while the...

Just letting everyone know that the guide has been updated: it comes with the latest drivers it is compatible with both Proxmox 5 and Proxmox 6 it has been optimised for a single copy-paste into the console Good luck and looking forward to your feedback!

From the console type: crontab -e In the editor, add the following line: 0 0 * * 7 shutdown -t 0 This is an example. In cron the first 5 digits is the schedule for when the command is executed and in the example above - it will shut the server down on midnight between Sat and Sun. You can read...

Glad it worked! :)

Autoshutdown is easily done via cron. But i'm pretty sure you cannot to autostart via OS. You probably need to look into wake-on-lan feature.

Yes, they can. And they work great.

Hey! All depends on the size of the containers and the purpose of the storage. If the backup won't be done on server storage, but rather on external NAS, it makes less sense to have WD Red drives in there. On the other hand, if you need plenty of storage space, it makes sense to have bigger...

This is not really a Proxmox issue and the best answer you'd get on Microsoft forums. The answer would be that using OEM keys or cheap eBay keys is same as having a pirated Windows copy. Obviously the Windows would be activated. Take care!

If i understand correctly, you're using a Freenas instance as storage, mount that storage in Proxmox and deploy VMs on it. Please correct me if i'm wrong. Here you need to take maaaany things into account: RED drives, AFAIR, are 5400RPM (if not RED pro), which makes them slow. RAID6 is also...

Hello! It seems that NFS storage cannot be accessed via the network. If you think that the storage works fine and it should work properly, check this topic: https://forum.proxmox.com/threads/mount-no-longer-works-in-proxmox-6-nfs-synology.56503/post-317022 As for the storages not being visible...

See if this solution would help you: https://forum.proxmox.com/threads/mount-no-longer-works-in-proxmox-6-nfs-synology.56503/post-317022 It seems there is a bug in Debian which affects the way NFS mounts are handled.

Is pfsense somehow responsible for the networking between the server and NAS?

Hey! Usually it's done via the server bios rather than OS. Check the BIOS settings and see what boot options you have. You may need to set wake-on-lan or something akin to that.

Hey! Don't want to freak you out, but are you sure the card is ok? I had one of the cards die on me and it may be the case that yours may have died or entered some recovery mode. Can you do fio-status -a?

Hey! This might help you: https://forum.proxmox.com/threads/unusually-slow-io-on-a-pcie-ssd.54833/

It's not the showmount; it's actually the rpcbind 1.2.5-0.3+deb10u1 at fault. On Ubuntu the issue does not appear. Even when using an Ubuntu container (that shares the kernel with Proxmox). I guess the best we can do is wait. Btw, if you're looking for a solution, there is a simpler approach...

Incremental backups would kind of defeat the concept of data redundancy, since a bit rot of one of the data clusters would nullify the whole set of incrementals. For incrementals there are the snapshots.

Not really. The backup is around 40% slower on the local array, but i'm not concerned about that at all, as it's still fine and quick enough. I was bottlenecking when doing the offsite backup and the bandwidth was already pushing the times higher than what's needed for the better compression. On...

Beautiful numbers across the board :D 17.25 GB of storage space saved out of 123.8 GB initially (14% improvement). Amazing!

I have a NAS exposed to web. Would it help you to have access to it for testing purposes? My best guess - it's a bug in Debian's implementation of rpcbind, but i may be wrong.