HA keeping my NAS awake - WHY?

Hi all,

So I’ve recently acquired an NAS box for testing purposes (if important I can later add make and model), and to play with the backup function on HA. (I’m running HA OS on RasPi4, if that’s important)

Let’s start with the question- why is HA pinging my NAS drive every few minutes thus not allowing it to go into sleep mode? Can this be changed somehow or is it hardcoded in the system?

So I’ve set up this NAS box with a single sata HDD in, to test some things and also test HA backup system. There’s a single shared folder on the disk, it’s mapped in my computer and (later) also in HA network storage in CIFS mode. (I generally don’t have a need for NAS, my desktop is currently also doubling as media server/shared folder for all users)

Before it was added to HA, even if computer that it was mapped on was running, NAS disk would normally go into sleep mode, and be awaken by Windows every now and then. Fine.

First thing that I’ve noticed, after adding this drive to HA network storage, is that NAS wouldn’t go in sleep mode any more. As sleep time is set to 10mins of inactivity, it means that HA’s “pinging it” in a lesser interval and so keeping it awake. Disk is in HA network storage mapped only as backup, and automatic backup is set 1x week in “system optimal” time.
As I said, since I don’t currently need NAS, disk inside isn’t a proper NAS disk but a regular one (with fewer running hours per year before dying).

So, to repeat the question, if network disk in HA is marked as backup only, and there’s no backup planned for several days, why is HA constantly pinging the state of my network storage disk and not allowing it to get to sleep state? Is this behaviour on purpose, or is it a bug? How can I tell it to just leave this disk the F alone when it has no business with it?

Thank you to all who made it this far, and a special thank you to anyone with even a half-decent reply. :slight_smile:

//RANT: So to reduce the running hours, I’ve even set my NAS to go into sleep mode every evening and wake every morning, but HA within just a few minutes of this sleep reports an error “Network storage device failed”. Why?? It has no need of that disk for the next 3 days. :angry://

2 Likes

Thanks, voted! :crossed_fingers:

really HA backup is a bit overated. all it does is copy config folder which is not special or difficult.

You can create an automation that rysync config folder to your NAS every xx days.
With that you wont have need to mount folder and can just use command line integration.

I don’t need a NAS backup, I’m currently just testing the option to see if it’s beneficial. For years now I have used .bat file that I manually run every once in a while that does just that, copies config folder.

Just out of curiosity, can you post how your backup automation looks like? If I ever decide to automate it myself. Do you use bash or what? Cause my batch file is made of Windows commands mostly, for which I probably need to find Linux alternatives.
Thanks!

I manually backup data yearly.

My HA data effectively hasn’t changed and I don’t care about db data.

HA command line integration allows you to run script or command Yes, it would be a basic command like

rsync -aP /config [email protected]/backupfolder

And must add that to an automation

Thank you.
Mine is a bit more complicated, as I (manually) keep last 3 versions, but it also comes down to one copy command.
Maybe I’ll try to integrate something similar, until they fix the external storage pinging issue.
Cheers!

I have just remembered why I’m doing this via .bat file and not from automation - I’m too stoopid to understand how to use command line integration, even now I’ve spent 2hrs looking at it and am nowhere closer :rofl: I remembered that I can’t use rsync from bash file as it doesn’t work, but I was never able to understand and use command line, it’s just above my mental capacity apparently. I’ll stick to my .bat file until issue from the topic is resolved. :upside_down_face:

1 Like

I was searching forever and found your post… disabled this sh*t and went back to SambaBackup.

I would gladly use this feature, if it’s functionality wasn’t “broken” in this way. I’m still on manual backup.