I am using a QNAP NAS for DVR storage with a Flex 4K. I had to reboot the NAS recently due to firmware update. And I just find HDHR lost the storage link and can't find any way to recover from it.
The Recorded tab says "Your HDHomeRun DVR wasn't found"
Tasks tab still list upcoming recordings.
My guess is a power toggle on the device is required? Can this be automatically reconnected?
Lost DVR after NAS reboot
-
signcarver
- Expert
- Posts: 11511
- Joined: Wed Jan 24, 2007 1:04 am
- Device ID: 10A05954 10802091 131B34B7 13231F92 1070A18E 1073ED6F 15300C36
- x 26
Re: Lost DVR after NAS reboot
How did you install it... the "official" NAS install way only restarts successfully after a reboot when its a WD NAS not qnap... Most using a qnap or virtually any other NAS would use one of the other install methods, depending on model, I would probably suggest the docker install but some qnap models don't properly support docker. Last I checked if you don't have docker the other unofficial qnap package works (for the qnap package see viewtopic.php?t=31745 or for the docker version see viewtopic.php?t=73757 )
The nice thing about the packages rather than the NAS install is that on restart they will also upgrade the engine to the latest version if needed. To me the hard part is that there can be some permissions and settings issues to figure out if you had previously used the NAS install method... I have heard some have actually found it easier to move the recordings to the "new" default location but it shouldn't be that difficult to upgrade the permissions properly and have it use the same location, but sometimes learning "locations" when one upgrades can take a bit of getting used to as the path to the folder may be different.
The nice thing about the packages rather than the NAS install is that on restart they will also upgrade the engine to the latest version if needed. To me the hard part is that there can be some permissions and settings issues to figure out if you had previously used the NAS install method... I have heard some have actually found it easier to move the recordings to the "new" default location but it shouldn't be that difficult to upgrade the permissions properly and have it use the same location, but sometimes learning "locations" when one upgrades can take a bit of getting used to as the path to the folder may be different.
Re: Lost DVR after NAS reboot
I am not sure what you mean. I installed the QNAP DVR storage using the official guide: https://info.hdhomerun.com/info/dvr:nas:qnap And I want to stick to the official supported install for as much as possible.
It's been running fine. But the 4K Flex doesn't reconnect to the NAS after the NAS rebooted. And there's no way to force it to.
It's been running fine. But the 4K Flex doesn't reconnect to the NAS after the NAS rebooted. And there's no way to force it to.
-
signcarver
- Expert
- Posts: 11511
- Joined: Wed Jan 24, 2007 1:04 am
- Device ID: 10A05954 10802091 131B34B7 13231F92 1070A18E 1073ED6F 15300C36
- x 26
Re: Lost DVR after NAS reboot
And it says right there the problem you had. Keep in mind the packages I mentioned get and run the official engine it just installs it in a way that actually works better for that environment rather than a generic linux environment (though docker is getting to be a more "universal" method on a nas),
If you wish to continue using the method mentioned there just do such and install again any time your nas had to reboot (the share is already made). Occasionally after a firmware update the nas may have changed some things that the traditional dvr nas install won't work with.
There are usually ways to put a script on your nas to start the engine on restarts (i think on the qnap it was modifying autorun.sh which may be in a different partition you need to mount to edit) but I have seen such appear to work correctly and then fail on some after if the nas does a firmware update (so often i will often not auto update firmware but suggest if you do that to make sure you manually keep it up to date), there are also some that the firmware essentially always kills such startup after reboot as they extract the system to ram on each boot rather than relying on drive to hold such system configuration. But these methods can vary between the various nas models (even with the same brand) and firmware versions which is why there aren't universal instructions for doing such (though if you post your model someone might chime in how for your nas) and probably the most universal now is to just use the docker version (if the nas supports such) as typically a nas will always support starting docker containers on reboot (though sometimes after firmware upgrades I've seen docker or othee manager may need to be reinstalled but may pick things right up after that)
If you wish to continue using the method mentioned there just do such and install again any time your nas had to reboot (the share is already made). Occasionally after a firmware update the nas may have changed some things that the traditional dvr nas install won't work with.
There are usually ways to put a script on your nas to start the engine on restarts (i think on the qnap it was modifying autorun.sh which may be in a different partition you need to mount to edit) but I have seen such appear to work correctly and then fail on some after if the nas does a firmware update (so often i will often not auto update firmware but suggest if you do that to make sure you manually keep it up to date), there are also some that the firmware essentially always kills such startup after reboot as they extract the system to ram on each boot rather than relying on drive to hold such system configuration. But these methods can vary between the various nas models (even with the same brand) and firmware versions which is why there aren't universal instructions for doing such (though if you post your model someone might chime in how for your nas) and probably the most universal now is to just use the docker version (if the nas supports such) as typically a nas will always support starting docker containers on reboot (though sometimes after firmware upgrades I've seen docker or othee manager may need to be reinstalled but may pick things right up after that)