Search results

Thanks, that works

Hello, thanks for your response. I already have the entry in the fstab, and it mounts nicely without problems: //192.168.0.110/pihole_db /media/pihole_share/ cifs rw,vers=3.0,credentials=/root/.smbcredentials 0 0 However, I don't see any option to mount that in the container. Also, this makes...

Hello. I'm looking for a way to share a read-only samba across nodes. I tried to mount it on the UI but even if I just select it as container data it tries to create subfolders within the share, which is not permitted and not what I want. I want to mount a shamba share in the cluster, that at...

I know this is kind of an old thread, but I'm in this exact same situation, with a little difference: I have a cluster of 3 nodes, where one of the nodes is already on proxmox 7. Should I just update the other two from 5 to 6 then to 7 and finally all of them to 8?

Ok, thank you for your answer, gonna try that out. Then I don't know what the purpose of the HA group is, because in my case, there were two nodes available and still it chosen the only which was not on the group.

I did that already, and the CT still ends in the wrong node. Take a look at this screenshots:

Yes, I have to get into the console of the node, and then edit the file that says where the VMs are to put it in the right place. It is `/etc/pve`

Here is an screenshot of my current cluster state and the replication tasks. As you can see, replication is only done between nodes proxmox-2 and proxmox-3, which are the ones having ZFS storage.

Hello. I have a HA cluster with three nodes. I have replication between two nodes. Each of those two nodes have a zfs pool that is used for replication. I have replication rules setup between those two for HA. I have an older third node that does not have ZFS setup, so I don't use it as a...

Yes, that is exactly like that for me. I am using 6.2. As someone said on a previous comment, that not being default it's a joke

Nobody has an idea of why this could be happening? I feel very nervous not being able to manage the old snapshots from proxmox. All I can do is make new ones on the directory that is mounted on the same samba mount that I don't have access to

Well, it is hard to say. Since then I did some things that may have impacted it: - Moved all my backups to an external location, so I don't have any snapsot on the local storage anymore - Added two more nodes to the cluster, not sure if now it is load balancing some of the data (I don't think so)

Hello. This is still a problem for me. I don't know why I can write to a subfolder on the CIFS share mounted as a folder, but I can't write to the root to backup. This is the configuration of both on /etc/pve/storage.cfg cifs: Backup path /mnt/pve/Backup server nas.home share...

Thank you all for the responses! I will keep the OS on the mechanical disk and I'll keep an eye on the wearout. Is it enough to take a look at the wearout % on the disks list? Or should I run some specific test! I will also consider an 1U server with proper 120mm fans.

Wow, thank you very much for sharing your story. Indeed it is easy to go down the rabbit hole. I thought my mechanical keyboard addiction was expensive... until I discovered home lab. Dam it, each hobby is more expensive than the previous. My main limitation is that I want to keep everything on...

Ok, this is weird. I just created a directory inside the mounted CIFS and I was able to backup to that subdirectory. I don't understand why this works and backing up directly to the mounted CIFS share does not. I will really appreciate any explanation.

I just opened my newest node, the EliteDesk 800 G1 mini to find two nice surprises: It has a M2 slot. It is limited to Sata III but that will allow me to have two disks, which is very nice. I ordered a 500GB M2 module for a total of 1TB. Of course I don't plan to put both disks on raid, because...

Not sure if that is the same as I said (enabling it on all nodes at Datacenter level). Sho it is not required that the ZFS pool is named the same? I had the impression that it is needed.

Ok, I found what it's required. I have to go to the cluster/Datacenter and allow the ZFS pool on both nodes. Now it seems to work

Hello again. I just "suffered" the pool name not being able to be customised on the proxmox installation. I had to remove the ZFS pool from the cluster, remove the ZFS pool on the host and then delete all disk partitions. Now I have created a new pool named rpool, scheduled a replication and to...