So my NAS is… let’s say “seasoned. It has been sitting in the “lab” quietly holding files for years, and as long as nobody asked it to do anything new, we got along great.
Then I asked it to do something new. I wanted it as backup storage for Proxmox, which I touched on in Building a Proxmox Home Lab: Lessons from Years of Breaking Things. This is the slightly longer version of that one paragraph. Hopefully it saves someone time. If not, that’s okay too.
Proxmox and SMB
Adding an SMB share to Proxmox should be a two-minute job. In the GUI it’s Datacenter > Storage > Add > SMB/CIFS, fill in the server, username and password, pick the share from the dropdown, done.
Mine was not a two-minute job.
After some digging (I mean Googling), the answer was pretty simple. The NAS was set to SMB1, and Proxmox doesn’t do SMB1. At all. The Proxmox storage docs list SMB 2.0 as the lowest version you can pick, and flat out say SMB1 is not supported due to security issues. So Proxmox wasn’t being difficult – it was being responsible. Annoying, but responsible.
Why SMB1 had to go anyway
Honestly, Proxmox did me a favor here. SMB1 is OLD, it’s deprecated, and Microsoft has been telling people to turn it off for years. The big reason is EternalBlue, the SMBv1 exploit that WannaCry used back in 2017 to tear through networks all over the world. If something on your network still speaks SMB1, that’s the door it was knocking on.
LAB isn’t Prod – but I still don’t want that door open.
What I changed
On the NAS: I went into the NAS settings and switched the SMB protocol from SMB1 to SMB2 to match what Proxmox needs. [FILL IN: where the setting lives in the NAS UI, and whether it’s labeled as a min/max protocol] [FILL IN: did the NAS offer SMB3? If so, why SMB2]
One thing worth a quick look before flipping it: anything else that still ONLY speaks SMB1 (old printers, scanners, ancient media players) is going to lose access once the NAS stops talking SMB1.
Test it before Proxmox gets involved. From one of the nodes, smbclient will tell you if the NAS is answering on SMB2 (if it’s not installed, apt install smbclient):
# smbclient -L //X.X.X.X -U labuser -m SMB2
If it lists your shares, you’re talking SMB2. If it errors out, the NAS change didn’t take, or the SMB service on the NAS may need a restart.
Adding the storage. Once the NAS was speaking SMB2, the GUI route works fine. I like the CLI for this one because I can pin the version:
# pvesm add cifs nas-backups --server X.X.X.X --share lab-backups --username labuser --smbversion 2.0 --content backup --password
# pvesm status
Leaving --password at the end with no value makes it prompt for the password, so it doesn’t end up sitting in your shell history. In pvesm status the new storage should show up as active. If it says inactive… back to the smbclient test.
Pin it, or let it negotiate. If you leave --smbversion out (or set it to default), Proxmox negotiates the highest SMB2+ version both sides support. Pinning 2.0 just makes it obvious what the NAS is doing. If the NAS ever learns SMB3, it’s a one-liner to bump it:
# pvesm set nas-backups --smbversion 3.0
Next up: Proxmox Backup Server
So with the NAS speaking a language from this decade, the next thing on the list is Proxmox Backup Server for the dedupe/incremental goodness. We’ll see how that goes.
Hope this helps someone searching Google for the same problems. Happy labbing!



