Separate names with a comma.
Discussion in 'TiVo Upgrade Center' started by ggieseke, Apr 13, 2013.
After complaining and escalating at Tivo, they agreed to submit a ticket to some other technical support group at Tivo and then I got an email saying that my box was ready to be updated. Indeed, I was able to connect and download the latest version.
I'm still experiencing freezing and rebooting though. And today I have a new problem: recordings that are mismatched and under the wrong folders. When I try to delete them, they wont delete (and sometimes trying that makes my box reboot). WD Diagnostics says my drive is fine, but maybe I will try a new drive.
You know, I think the problems on my Premiere started around the same time that I added a Roamio to my account. Think that could be related?
Well, I've seen plenty of evidence of hardware jealousy where you no sooner get a new piece of gear in the door than something else starts pitching fits and demanding special attention.
Great statement, hardware jealousy, never though of that problem that way.
Rebooting can often leave an error message in the logs, so I would look there.
I think this box deserves it's own thread, getting hard to put all the relevant history info together.
That works the other way too. You should have seen the look on my fully-loaded Arctic White C5 Corvette's face when I got sick of Chevy's BS and replaced it with a used Toyota from a salvage yard.
It's kinda like gremlins, but situation specific.
Helpful tips & explanations for all:
Use my trick of using 00000 zip code, Tiny TiVo as provider, run a C&DE on the updated image, pull the plug on the reboot once the C&DE operation has completed, which self-triggers a reboot (preferably before the KS [kickstart] window of opportunity, or before the "almost there" screen at the latest), make a backup of that, and upload it for distribution, or just use for yourself, if that's how you roll.
The 00000 zip code & Tiny TiVo provider trick only downloads one channel worth of empty guide data, keeping the new backup image small as can be, and saves time. A cablecard can be paired in this setup, but the channels can only be tested using "test channels using M-card" via DVR Diagnostics screens. This is just a FYI, for those who may use this trick for the many other uses I've found for it, like purging out corrupted data related to an existing zip and provider's guide data.
The reason for the C&DE with timed power-pull is to stop the drive from becoming married to the TSN of the board it is updated on, eliminating image recipients from having to repeat guided setup twice, with a C&DE between the two, to remove any existing host board TSN-to-drive marriage.
Once the software has reached a certain version number, the second screen of GS, where you select demo/home setup, has a "press enter for advanced options" option, which adds Installer Express mode to the choices, saving a big chunk of time, by only doing the absolute minimum GS needs to, leaving all the little personalized preferences to be set later through the menus.
If you want to see what software version is on a drive that boots into GS, without running it, press Info button on the very first GS screen (Select Country). It's at the bottom of the screen, when displayed.
EDIT/ADD: I had left out it is best that the only things connected, until done, are:
1. Power cord/supply.
2. Ethernet cable (or wireless, if you absolutely can't do RJ45 ethernet).
What absolutely should NOT be connected:
1. Coaxial cable for cable or antenna.
Why: If a video source is available, the TiVo will continuously process and buffer all tuners, making the resulting image larger for every zeroed-sector that is changed to in the process. A C&DE does not re-zero the sectors that get changed. Even though the buffer, per tuner, is 30 minutes, it still moves forward though more sectors for as long as the TiVo is on, and has a coax connection providing cable or antenna connectivity. For the cleanest and smallest backup image, this is a big deal.
I suppose (theoretically) somebody who insists on using MoCA, could just remove the cable/antenna input coax to the MoCA, and just use the coax for networking only.
I've been trying to create a 746/748 image that can be used with dvrBARS to restore on either a 3Tb or 4Tb drive. Check out this post #64 over at the DIY 4TB thread. Managed to get a 2Tb drive (WD Red) to the state where the final VHD is to be made. Tried using dvrBARS to backup the 2Tb drive (all three methods of backup), but it is hanging on scanning partition 9. Actually, the dvrBARS process is running the cpu around 50% constant, but the hard drive access stops after a few seconds. Waited about an hour on the Truncated method and still the same results. It would basically start the backup process like normal, but once it hits partition 9 it would read for a few seconds, than 'hang'. Any ideas what's the issue?
Btw, the 2Tb can copy via JMFS v1.05 to a 4Tb (than expand) just fine. It works great actually! Just need to figure out how to capture the VHD of the 2Tb.
This partition may be one of those that are huge, and would take a long while to complete.
I thought that too, but when I used it in an USB adapter the LED did not show any disk activity (read, or write). When i let it see for about 20 minutes, the drive had actually spun down (stopped).
I've had this happen too. I have a version of DVRBARS that skips the check for the drive being a TiVo drive, and it starts off promising, then the activity lights go out on my USB 3.0 docks. But, the program will complete, after hours of no LED activity, create a file around the size (I would guess) it should be, but the actual data inside the VHD only goes as far as the time the LEDs were showing activity...
I wrote it off as "it was worth a shot". What I was trying to do was create a VHD backup of some laptop drives, with the VHD files going to another drive. None of them completed properly.
The same docks have been used with the regular DVRBARS to backup and restore a great many TiVo drives. It's not a large-drive issue, since the laptop drives are only 500GB, 750GB, & 1TB, while the drive I formatted to NTFS to write the VHD files to was 2TB.
Could be some other problem. I just thought now was a good time to bring it up.
A Full backup should have worked unless there's something wrong with the drive or the connection to the computer. It doesn't go through the "scanning" process the read the ext2 and MFS file systems, it just reads bytes in a row. I have even used it to virtualize Windows drives.
Your first pic shows it scanning the /var partition. I only copy it to be nice to the hackers that have modified it on older models. If something is corrupted in the ext2 file system on that partition you can just zero those sectors with a hex editor.
Not sure what else to say. The code will always pop up an error message if any of the Windows API calls fail and it's littered with sanity checks, but something unexpected must have thrown it into a Hotel California loop.
My Premier just crashed. :-( Does anyone have an Image for a: Premiere xl4 (tcd758250) ? I will be restoring it to a 3tb drive. From what I have read in the thread I need to use hdparam.... Can someone send me the commands for that as well?
I would greatly appreciate it ..
If you use the 2TB XL4 image you can use the patched version of JMFS and go right to 4TB. No hdparm. The only caveat is that the image needs one of the later OS revisions for the OS to not bootloop on a drive greater than 2TB.
Sounds perfect. Where do I get the patched version of JMFS from as well as the newer image?
The patched version of JMFS is here.
Might see if ggieseke has an image that will not bootloop on large drives.
Hopefully he will see my posts, I can't PM do to my lack of posts even though I've been a member for 10 years..
The ultimate silent type.
And if you'd only posted once in each of those years, even just to let us know how you're doing, you'd be able to PM now.
After you answer this post, you'll only have 6 more to go.