Ripper from Hard-Drive connected directly to a PC

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?

Sorry, Nope :frowning: I gave up and just used the new drive.
The best way I can see it to work in Linux. The directory structure is something like :
/pvr\rec\364780\segs\00000.ts … 00001.ts … etc.
The “364780” folder contains all the segments for that individual show.
So, there are different “364780” folders for each show.
These .ts segments would have to be merged together.
Elsewhere on the drive are files that contain things like meta-data and thumbnails.
So, you would have to peer into some of these files to get an idea of what show is being looked at so you could give a name to the file you create when you do that merge.

Like I said, I gave up, sorry - Kurt

Trying to revive an old thread here.

I have the same issue. I unknowingly reset my Tablo to get it to recognize a new drive. Now I am unable to access 1.5TB of shows on the Tablo. All of the data is still on the old hard drive (also copied to new harddrive).

I am open to either a Windoesn’t or linux solution, and I am fairly comfortable in linux command line. I am not a coder, but am willing to give anything a shot.

My ultimate wish would be to have the recordings available to my Plex server.

Anyone with a solution?

I actually have something that works, but it’s :
) too klunky for the average user
) too lame for a sophisticated user.

It’s a .c program I wrote that looks for all the directories, then looks into the .meta file, then creates a name for a file that means something you can recognize.

You need to compile it with something like MinGW.

Anybody got a tool for this? My Tablo died and the new Tablo sadly isn’t restoring the HDD database as described in the Support Docs. I attached the drive to my PC, mounted the EXT4 filesystem, and can see all the files. I can easily peruse and even manually merge the TS files, but I’ve got hundreds of recordings and don’t have the time to go through each one manually. A tool that can at least scan and list all the recordings in some human legible manner would help a lot.

Unfortunately that doesn’t help me. I already know how to find and merge the recording segments. My issue is that I have 1000+ recordings with no way way to identify which ones are important.

If the drive has /db directory, the “backup” DB for the tablo… it’s in there. Supposedly tablo creates this, when ever? I know it does at reboots, and it’s unclear if/when it ever does randomly.

It, used to move your recordings form one tablo to another. (I found this to work, without trying while resetting tablos and swapping drives, if you don’t delete the db, it “restores” instead of resets)

If your device doesn’t restore as indicated, you may not even have a backed up DB. How ever if you do, and really really want to get the info. Unless you know how to query sqlite or parse exported data… 100s or 1000s of “important” (trusting a single device!?) is a PITA.

Look in the Recording table, objectType = recEpisode It looks like the key json is the same data tablo stores per recording, objectID is likely the “pvr” directory

Unfortunately my Tablo died randomly and after looking it seems to have not kept a backup DB directory on the drive as far as I can tell. Why a periodic backup of the DB wasn’t automatically made by the Tablo, I don’t know. I’ve been using the Tablo for 5 years and wasn’t expecting that the recording information wasn’t being stored on the drive with the recordings anymore.

This is a family DVR, so it wasn’t practical for me to automatically rip important recordings of my other family members since they often set things to record that they feel they might be interested in but probably won’t care about. So the end result is 1000+ recordings that I’d have to sift through in order to find what they’ve told me they actually care about.

Guess I might be SOL.

Might be worth trying a new power supply before you give up.

If you have one with similar specs you can see if that revives it before getting one:

I was pretty proud of the solution I came up with.
However, it relied on the existence of the file “meta.txt”
In recent versions of TabloTV, this file no longer exists.
TabloTV : can you please explain why you removed this file ?
Thanks, Kurt

did you try the search? If any/every one could figure it out, what do you thing technicians… well I’m sure they can still figure some things out. They still use a lot of open source code, but only offer a long since defunct link to any license agreement Opensource link referred to doesn’t exist

no response. link still 404

Borrowed a universal power supply from something else and it managed to get my old Tablo working enough to get the DB dumped to the HDD. Thanks for the tip.

I think I’ll keep the new Tablo anyway since the old Tablo is already 5 years old and I don’t feel like I can rely on it anymore. Plus the new one has Gigabit Ethernet and supposedly a better splitter and more sensitive tuners. Probably won’t make a huge difference, but it should cover me until ATSC3.0 actually takes off and Tablo makes a device for it.

I just wish Tablo would make a periodic backup of the DB to the HDD just in case the Tablo actually dies for some reason. Kinda dumb that recording metadata is kept solely in the internal memory. Even just a periodic backup can at least recover all but the most recent recordings and allow me to focus manual recovery on just the newest ones.

1 Like

I think that’s a very good idea about periodic database back up, and something Tablo should strongly consider adding to the near-term coding agenda. (I too have lost material this way, and would gladly have had it to pull off the hard drive.)

1 Like

I’m in the same boat. I tried my drive migration to a new Tablo and I stopped it after 5 hours LED pulsing. I tried again next day and didn’t precisely followed the procedure so I erased my database. Now my 3TB of recordings are not playable by neither of my 2 Tablos. I’m now looking for a way to copy/assemble the recordings in a Linux system by connecting the drive directly.

What does PITA mean?

PITA = Pain in the (posterior)

How did you erase the database and settings or your original aka old, tablo? They don’t go away with the drive, they’re stored internally on the tablo’s [technical term for nvram].

Although leaving it powered and/or connected to the internet will allow maintenance mode to occur and likely clean things up. :frowning:

I think I pressed the blue button once on the old Tablo. Then I disconnected the old Tablo and connected the new Tablo. I connected the usb drive before plugging the power cord to the new Tablo. The new Tablo started up quickly and the LED pulsates only for a minute or so. So I think the mistake I did was to press the blue button on the new Tablo and then disconnect the usb drive. Then when the new Tablo LED was solid blue I plugged the usb drive and again the LED pulsated for a minute or so. Then I disconnected the new tablo and connected the old tablo again (anything but the usb drive) and when the solid LED was there I plugged the usb drive. At this point, both the old and new tablo weren’t able to play my recordings but could all be seen. Yesterday I plugged my usb drive to a Windows desktop with ext2 (software to read/write ext partitions) and I could see that 3 DB_backup folders were there and one of them was before yesterday (before I had the problem). I tried to replace the DB file in the DB folder with the DB file that I thought was good but nothing changed. I can still see my recordings but not play them.
The weird thing is that I tried deleting some recordings from the Tablo interface and the free space in my drive got bigger. So that means my Tablo knows which metadata is related to which files. So I don’t understand why it can’t play the files…

So you tapped the button on the old, backed up the DB, as indicated in the instructions. Supposedly you should let the new one power up first, but I don’t think it will matter if the drive is attached first, when the new one powers up it started to read the drive… you tapped the button to backup the new/empty DB to the drive?

If your old tablo was not factory reset, it’s suppose to have all the DB data stored internally and has no real use for the /DB on the disk. It it only read by tablos brand new fresh out-of-box experience …or factory reset.

Why the internal DB on your old tablo is “gone” shouldn’t be directly connected to what’s up with the drive. Now if the other files related to the recordings… this may be a different issue.

It’s been many, many months since I’ve had my connected to a PC, I don’t believe /del is used and there were a couple of .dot files (hidden) never seen a /tmp. It’s unclear if those dates are last accessed or last modified. (never seen more than just a single /db, but I’ve never dug into regularly)