I am in the same boat as several posters here. Something must be subtly corrupt with my Tablo database. I’ve got a hard drive full of 3,000 (!) recordings which Tablo sees and plays (and Tablo Ripper can rip) for about one-and-a-half recordings. The Tablo then crashes, the hard drive (independently powered) shuts down. I have to unplug the hard drive from the Tablo and reboot the Tablo, then re-connect the hard drive to get back up. Rinse and repeat.
I have successfully cloned the drive - same result. I have loaded both the original and the cloned hard drives onto a second, factory reset Tablo which then uploads the database from the hard drive. Same result with the fresh Tablo. I conclude the problem has to be subtle in the Tablo database or some even more obscure issue with whatever Tablo reviews on the hard drive. The second Tablo operates perfectly for weeks with a different, newly formatted (by the Tablo) hard drive, but always crashes if working with the original/cloned drive.
So the old hard drive contents (original or cloned) cannot be ripped for more than one or sometimes two programs at a time without disconnect and reboot. Pretty obviously, that process is not viable for 3,000 recordings (well, 2,090 or so after all my testing!).
So, I need some kind of program to pull and rip directly off the hard drive, bypassing the Tablo.
Incidentally, the recordings are on Tablo firmware .16, but seem readable by .18 and .20. Haven’t tried .22.
I can see the hard drive recordings and play them on both a Linux box and Windows 10 (using an EXT3/EXT4 reader - not using bash). But I don’t know any program that can read the Tablo segments per program and assemble them into one file in order, let alone maintain the metadata (series, program numbering, name, etc.). The need to convert to, e.g., MP4 could be handled separately if necessary. I’m not a scriptwriter, so I can’t write one.
Essentially what would be ideal would be if Tablo Ripper read the database not from the Tablo but the hard drive directly and operated on the hard drive through the host computer (if the hard drive was network mapped to the computer for access).
Anybody have any thoughts on a solution?