I did the swap, Christmas telly impending, and it turned out the recordings were not decrypted. Did the custom encryption key but it would not work. Missed the post above that someone suggested fix flash packages then found it and did it. It now works wonderfully. I have made a note of the new/old custom key.
-
The forum software that supports hummy.tv has been upgraded to XenForo 2.3!
Please bear with us as we continue to tweak things, and feel free to post any questions, issues or suggestions in the upgrade thread.
Problem. Have an old faulty T2 with 2TB drive. Also have a new working T2 with no HDD
- Thread starter SemiRamis
- Start date
confabulator
Member
So following up from the above, I have a dead Fox T2 and a replacement T2 set up with CF installed and ready. The HDD in the dead one needs to transfer over as it's 2TB and my replacement box only has 500GB, it also has recordings I'd like to retain. It is though, mainly, not decrypted.
So my plan is:
Posting this as a sense check I case I've missed a flaw.
So my plan is:
- Switch the old HDD into the new T2
- Change the encryption key in the webif to match my old T2 which made the recordings on that HDD
- Decrypt the whole drive via the webif, by either folder by folder manual decryption or setting recursive for the whole thing, so recordings play whatever the key.
- Once it's all decrypted change the encryption key on webif back to the native one for the replacement T2 (as the key from the old T2 will be redundant), so that any new recordings that aren't decrypted would play even without the CF installed.
Posting this as a sense check I case I've missed a flaw.
Black Hole
May contain traces of nut
No, you've got that correct.
You need the auto-unprotect package installed if you ever record HiDef, and then just set recursive auto-decrypt on Mt Video. Then leave it turned on for a few days. Job done, no manual intervention required. And leave recursive decrypt set, to avoid the same problem in the future.
You may as well use a key of all 0s, which is also more efficient to decrypt. Unless you actually want to have a hard-to-guess key, or when preparing for resale, there's no reason to use the native key.
You can save all the keys used in your setup (different machines at different times) and then CF decryption should use the first valid key for each encrypted file (after trying the default). But there is no WebIf UI for this: you have to add the keys to
You can save all the keys used in your setup (different machines at different times) and then CF decryption should use the first valid key for each encrypted file (after trying the default). But there is no WebIf UI for this: you have to add the keys to
/mod/etc/keys.
Black Hole
May contain traces of nut
That's what I do, but...
(a now-cured bug in stripts)
Not relevant to hardware decryption, but may be of interest to HD-FOX users (lacking hardware decryption unless running in HDR mode; but does anyone do that now?).
I didn't know that, but again irrelevant unless you rely on stripts for decryption.
The reason I recommend not running on a custom key unnecessarily is simply the chance that the unit might revert to the native key if the CF broke (because of a file system wobbly, for example). But I have a HD-FOX in a multi-unit network, so the arguments are different and having a consistent key on all units is a worthwhile convenience.
confabulator
Member
Yeah, auto unprotect is compulsory on every unit, I just didn't mention it specifically as for me it's part of "installed and ready". I do intend to have recursive decrypt on which would make most of this moot, but I intended that in the past too and for some reason it stopped happening leaving me here. Probably something I did I guess, but I don't know how, and so having the recordings in the native key if they end up remaining encrypted seems logical to me.
Black Hole
May contain traces of nut
Perhaps content sharing got turned off (it happens). It can be enforced by the bootsettings package.
Just a note for anyone enabling "recursive decrypt" on their whole media library (especially for the first time):
If you have the "undelete" package installed, you will have a "Create backup files in dustbin for decrypt and shrink?" option in WebIF >> Settings >> Auto-Processing Settings. If this is enabled, the original of every decrypted file will be moved to the "webif_autodecrypt" folder in the dustbin (by default at /media/My Video /[Deleted Items]), rather than being deleted.
If this happens, and your files that need decrypting are using more disk space than you have free, your box will run out of disk space before the process completes.
If you have the "undelete" package installed, you will have a "Create backup files in dustbin for decrypt and shrink?" option in WebIF >> Settings >> Auto-Processing Settings. If this is enabled, the original of every decrypted file will be moved to the "webif_autodecrypt" folder in the dustbin (by default at /media/My Video /[Deleted Items]), rather than being deleted.
If this happens, and your files that need decrypting are using more disk space than you have free, your box will run out of disk space before the process completes.
antipodean
Active Member
Yep, and the solution is to just delete the [deleted items] folder, and let it restart where it left off. You may need to do this several times (depending how much free space you have) before it has completely decrypted the drive.
Black Hole
May contain traces of nut
Or simply remove the undelete package temporarily.
In my multi-user, trigger happy household, it's saved the day (and an argument) many times...I've had this happen too confabulator, it's a proper pain sometimes..
Thank you for the beautifully simple solution Black Hole..
