"Your HDHomeRun DVR is ready to record" but no recordings

[dlparker]

I've just rebooted my dvr backend and the hdhomerun app on my mac shows "Your HDHomeRun DVR is ready to record" on the "Recorded" page. There are recordings but they're not showing up, and no new recordings are being made. The logs don't give me any clues.

Anyone have any ideas?

Thanks!

[signcarver]

What backend and how did you install it? Normally when one refers to it like that it will have its own log files that are easily viewable unlike when using a drive on a flex, scribe, servio.

If you followed the regular NAS install, that only autostarts after a reboot when installed to a WD nas so you would have to restart the dvr (for many probably easiest to just reinstall it there).

Occasionally updates on NAS's mess up permissions and the engine no longer can read or write to the directories. Also keep in mind everything should be on the same network (no vlans or different subnets). I have seen reboots of devices pick up rogue dns servers and end up on a different network.

[dlparker]

What backend and how did you install it? Normally when one refers to it like that it will have its own log files that are easily viewable unlike when using a drive on a flex, scribe, servio.

If you followed the regular NAS install, that only autostarts after a reboot when installed to a WD nas so you would have to restart the dvr (for many probably easiest to just reinstall it there).

Occasionally updates on NAS's mess up permissions and the engine no longer can read or write to the directories. Also keep in mind everything should be on the same network (no vlans or different subnets). I have seen reboots of devices pick up rogue dns servers and end up on a different network.

Woops. Left out a few details. I'm running it on a fedora 43 server. Installed it according to the instructions for manual installation on the silicondust website. I've got a crontab entry - "@reboot sh /HDHomeRun/hdhomerun_record start" - that I start it up with. I'd installed it first a few days ago on a different os and was using a startup script that I'd found online to enable it with systemctl, but when I reinstalled I couldn't find that script online. Like a real bonehead I didn't keep a backup copy.

One possible problem is that I'm copying a bunch of other files over to the /HDHomeRun directory so I can move them to another disk once I've repartioned that disk and installed a different filesystem (btrfs to ext4). There are thousands of files getting copied over. Once I've moved all those over to the other disk I'll know if that was a problem. Space isn't a problem - I've got over 300Gb available and another 20 or so to copy, so I'll still have over 200Gb.

After I've finished the file transfer process I'll reboot and see if that was the problem.

[signcarver]

Keep in mind when you start the engine and are not in rhe directory that contains the .conf file, you also must specify where the .conf file is (usually in the recording folder) such as


./HDHomeRun/hdhomerun_record start --conf /<path to recording folder>/hdhomerun.conf

Also keep in mind the "normal" linux install essentially has one download the linux engine which is a script that extracts the real engine for your platform (arm, x86,...) from itself to /tmp and then starts that file, many updates may mount /tmp as no-exec thus can't run the file from there... the solution if the engine doesn't start because of that is to copy that platform specific engine from /tmp to a place that it can execute from (such as the record folder) and execute that file rather than the regular hdhomerun_record (though some might call it that when they move/copy the file it is typically named something like hdhomerun_record_linux_x64