I’m a couple weeks into learning HA and running my stuff on it and it’s gone… fairly well and pleased with the customisability of smart stuff.
I’m now trying to add a folder on my pc and shared it (windows 10) and trying to add that as a network storage backup option in HA ui. I am just getting the same error over and over no matter what I try.
2024-06-21 01:15:32.560 homeassistant systemd[1]: Requested transaction contradicts existing jobs: Transaction for mnt-data-supervisor-mounts-habackupfolder.mount/stop is destructive (mnt-data-supervisor-mounts-habackupfolder.mount has 'start' job queued, but 'stop' is included in transaction).
2024-06-21 01:16:32.703 homeassistant systemd[1]: mnt-data-supervisor-mounts-habackupfolder.mount: Mounting timed out. Terminating.
2024-06-21 01:16:32.705 homeassistant systemd[1]: mnt-data-supervisor-mounts-habackupfolder.mount: Mount process exited, code=killed, status=15/TERM
2024-06-21 01:16:32.705 homeassistant systemd[1]: mnt-data-supervisor-mounts-habackupfolder.mount: Failed with result 'timeout'.
2024-06-21 01:16:32.705 homeassistant systemd[1]: Failed to mount Supervisor nfs mount: habackupfolder.
I also tried enabling smb/cifs 1.0 in windows features but didn’t really understand what I meant to do with that. I tried using the same address for folder but added my m$ user pass but just same error anyway.
Check the firewall in Windows.
It can often have been set as default to block sharing of local drives.
Also be aware that folders located in your typical windows users directories (desktop, download, documents, pictures and so on) can be extra protected by Windows Security.
and you need to create homeassistant backups as it’s own share. such that you can access it via \\suze\homeassistantbackups
Also, I’m not sure what the permissions are on your folder that you are sharing but you don’t have any username/password configured. So if you don’t then that shared folder needs to be publicly read/write. If it’s not then you need to supply the appropriate username and password
I tried two things. Moved the folder to my usb drive and tried using my m$ credentials (or is there different user/pass I’m meant to set up somewhere?) in the username pass fields.
I then moved the folder to public documents and cleared the user pass fields and both have the same error below. Both times the folder is accessible via \suze\homeassistantbackups
Just verified on a lan pc that they can access \suze\homeassistantbackups too
thank you for persevering!
I do notice however that the time is wrong strangely, would this annoy the process? The time is correct in core log but host log shows 12hrs behind.
2024-06-21 20:10:02.910 homeassistant systemd[1]: Mounting Supervisor cifs mount: habs...
2024-06-21 20:10:02.913 homeassistant kernel: Use of the less secure dialect vers=1.0 is not recommended unless required for access to very old servers
2024-06-21 20:10:02.913 homeassistant kernel: CIFS: VFS: Use of the less secure dialect vers=1.0 is not recommended unless required for access to very old servers
2024-06-21 20:10:02.913 homeassistant kernel: CIFS: Attempting to mount //192.168.68.52/homeassistantbackups
2024-06-21 20:10:02.916 homeassistant mount[834771]: mount error: Server abruptly closed the connection.
2024-06-21 20:10:02.916 homeassistant mount[834771]: This can happen if the server does not support the SMB version you are trying to use.
2024-06-21 20:10:02.916 homeassistant mount[834771]: The default SMB version recently changed from SMB1 to SMB2.1 and above. Try mounting with vers=1.0.
2024-06-21 20:10:02.916 homeassistant mount[834771]: mount error(112): Host is down
2024-06-21 20:10:02.916 homeassistant mount[834771]: Refer to the mount.cifs(8) manual page (e.g. man mount.cifs) and kernel log messages (dmesg)
2024-06-21 20:10:02.916 homeassistant kernel: CIFS: VFS: cifs_mount failed w/return code = -112
2024-06-21 20:10:02.917 homeassistant systemd[1]: mnt-data-supervisor-mounts-habs.mount: Mount process exited, code=exited, status=32/n/a
2024-06-21 20:10:02.917 homeassistant systemd[1]: mnt-data-supervisor-mounts-habs.mount: Failed with result 'exit-code'.
2024-06-21 20:10:02.917 homeassistant systemd[1]: Failed to mount Supervisor cifs mount: habs.
2024-06-21 20:10:02.913 homeassistant kernel: CIFS: VFS: Use of the less secure dialect vers=1.0 is not recommended unless required for access to very old servers
2024-06-21 20:10:02.913 homeassistant kernel: CIFS: Attempting to mount //192.168.68.52/homeassistantbackups
it shows that home assistant saw the share and connected to it. but it looks like perhaps the versions of smb are different. ie, your windows is advertising smb version1 and home assistant is requiring smb2.1 perhaps? see this error:
The default SMB version recently changed from SMB1 to SMB2.1 and above. Try mounting with vers=1.0.
2024-06-21 20:10:02.916 homeassistant mount[834771]: mount error(112): Host is down
this might be an erroneous error that’s really caused by the time issue you noticed. or the time might be utc time…
but still… you got the share right and you got the permissions right… made progress in the right direction. sorry we didn’t get all the way there for you!
you should be using smb2 (or 2.1). the legacy 1.0 has some bad security issues. so the question is about getting your windows box to be 2.xx. windows 10 should be 2.xxx by default. mine is… but that’s what i would be pursuing.
That made sense, I followed some guide a few days ago which said to turn on smb 1 so I went back and undid that so now I suppose its using default of 2.x
Now I have a new error… lol
Seems my credentials are wrong so I don’t use my microsoft account. Honestly I don’t know why this is so difficult If I don’t use my m$ account what do I use or how can I make some username and pass that will work. I’ve got the everyone with read write applied if I have no credentials
Status code returned 0xc0000022 STATUS_ACCESS_DENIED
m$ account credentials
2024-06-21 22:52:42.410 homeassistant kernel: CIFS: Attempting to mount //192.168.68.52/homeassistantbackups
2024-06-21 22:52:42.414 homeassistant kernel: CIFS: Status code returned 0xc000006d STATUS_LOGON_FAILURE
2024-06-21 22:52:42.414 homeassistant kernel: CIFS: VFS: \\192.168.68.52 Send error in SessSetup = -13
2024-06-21 22:52:42.414 homeassistant kernel: CIFS: VFS: cifs_mount failed w/return code = -13
2024-06-21 22:52:42.415 homeassistant mount[841475]: mount error(13): Permission denied
2024-06-21 22:52:42.415 homeassistant mount[841475]: Refer to the mount.cifs(8) manual page (e.g. man mount.cifs) and kernel log messages (dmesg)
2024-06-21 22:52:42.417 homeassistant systemd[1]: mnt-data-supervisor-mounts-homeassistantbackups.mount: Mount process exited, code=exited, status=32/n/a
2024-06-21 22:52:42.417 homeassistant systemd[1]: mnt-data-supervisor-mounts-homeassistantbackups.mount: Failed with result 'exit-code'.
2024-06-21 22:52:42.417 homeassistant systemd[1]: Failed to mount Supervisor cifs mount: homeassistantbackups.
If I use nfs I get this (which I’m falling back to this wrong time thing, windows goes to crap when it’s time is wrong for updates activation etc, I wonder if it’s booing this because of the time)
ah! ok, now that makes sense why you were getting the smb mismatch. i was really wondering why you were getting smb1 on your windows10. that was turned off long ago.
for your windows10 machine machine, at least to test it, i would set the permissions on that folder to be your login. and then in the home assistant, put your username and login.
do you use a microsoft live.com account to log into your computer? if so, then for your username, you’ll need to use the same email address as you do for live.com and that same password.
i can’t answer you about nfs. i have never tried connecting via nfs. i’ve always used smb.
if it’s helpful, here’s an example that i have working:
i right clicked a folder. chose advanced sharing.
turned on "share this folder
save all of that. with this “advanced sharing” i don’t muck with who has what permissions.
the i went and verified that it shared from another machine. \\my_machine_name\downloads in my case here. i see that works. i remember what credentials i needed (which was my windows login info, but in my case i also set it for guest/no credentials required) and i then went and added that to home assistant:
Under advanced permissions I have full control for guest & everyone
2024-06-21 23:15:34.106 homeassistant systemd[1]: Mounting Supervisor nfs mount: homeassistantbackups...
2024-06-21 23:16:04.159 homeassistant systemd[1]: Requested transaction contradicts existing jobs: Transaction for mnt-data-supervisor-mounts-homeassistantbackups.mount/stop is destructive (mnt-data-supervisor-mounts-homeassistantbackups.mount has 'start' job queued, but 'stop' is included in transaction).
Adding guest permissions
2024-06-21 23:24:27.375 homeassistant systemd[1]: Mounting Supervisor nfs mount: homeassistantbackups...
2024-06-21 23:24:57.422 homeassistant systemd[1]: Requested transaction contradicts existing jobs: Transaction for mnt-data-supervisor-mounts-homeassistantbackups.mount/stop is destructive (mnt-data-supervisor-mounts-homeassistantbackups.mount has 'start' job queued, but 'stop' is included in transaction).
2024-06-21 23:25:57.453 homeassistant systemd[1]: mnt-data-supervisor-mounts-homeassistantbackups.mount: Mounting timed out. Terminating.
2024-06-21 23:25:57.454 homeassistant systemd[1]: mnt-data-supervisor-mounts-homeassistantbackups.mount: Mount process exited, code=killed, status=15/TERM
2024-06-21 23:25:57.455 homeassistant systemd[1]: mnt-data-supervisor-mounts-homeassistantbackups.mount: Failed with result 'timeout'.
2024-06-21 23:25:57.455 homeassistant systemd[1]: Failed to mount Supervisor nfs mount: homeassistantbackups.
After all this from my point of view permission wise this should work but doesn’t. I can only assume it’s the incorrect time spazzing it out.
Thank you for your help in this, the google drive backup addon works so I’ll just let this lie but leave it all here in case someone stumbles over it
If I don’t use my m$ account what do I use or how can I make some username and pass that will work. I’ve got the everyone with read write applied if I have no credentials
