New HDD for Tivo

Forums › TiVo › New HDD for Tivo

1 | 2 | 3 | 4 | 5 | 6

858 posts

Ultimate Geek
+1 received by user: 53

Subscriber

Reply # 1904031 19-Nov-2017 14:20

TinMan55:

I had an idea - being that the Tivo was not recognising the additional space on the new drive, I restored to it from the truncated backup I had taken of the original drive using Winmfs, selecting the option to add the extra space. Now, firing up the Tivo on the big drive, the extra space is there (says 400hrs), but although all of my recorded programs appear to be there, some of them have only the title, and clicking on them says there is nothing recorded. I have to say that I suspected not "seeing" the extra space wasn't the only thing lacking, as the copy had carked about two-thirds through; i.e. not just at the final step. So it looks like my options at the moment are-

Keep the original 320GB drive installed (which is full) so I can watch the stuff on it, while recording new stuff on my second box.

or -

Just go with the new bigger drive and accept the fact that some of the recorded stuff is lost (a higher authority may rule on this!!)

or - try and figure out how to drive JMFS to successfully clone the drive fully.

If the drive is anyway faulty - your more likely to strike it while imaging the system with all your existing recordings - many applications have problems with drives with surface issues. ddrescue is probably the best application for coping a potentially faulty drive - it skips past bad sectors getting most of the data off first them coming back around to get the what it can from the bad areas of the drive.

If you feel comfortable here is a guide on using ddrescue with a Tivo:
http://www.logicsector.com/tivo/how-to-clone-your-failing-tivo-drive-with-ddrescue/

However instead of using the distribution mentioned in that guide I would use a spare USB Drive, and download http://www.system-rescue-cd.org/Installing-SystemRescueCd-on-a-USB-stick/ following the install instructions under C)

Alternatively I'm happy to do this for you at no charge - you would need to leave the original drive with me for a few days for ddrescue to run and do its thing.

TinMan55

43 posts

Geek
+1 received by user: 6

Subscriber

Reply # 1904110 19-Nov-2017 17:37

rphenix:

TinMan55:

I had an idea - being that the Tivo was not recognising the additional space on the new drive, I restored to it from the truncated backup I had taken of the original drive using Winmfs, selecting the option to add the extra space. Now, firing up the Tivo on the big drive, the extra space is there (says 400hrs), but although all of my recorded programs appear to be there, some of them have only the title, and clicking on them says there is nothing recorded. I have to say that I suspected not "seeing" the extra space wasn't the only thing lacking, as the copy had carked about two-thirds through; i.e. not just at the final step. So it looks like my options at the moment are-

Keep the original 320GB drive installed (which is full) so I can watch the stuff on it, while recording new stuff on my second box.

or -

Just go with the new bigger drive and accept the fact that some of the recorded stuff is lost (a higher authority may rule on this!!)

or - try and figure out how to drive JMFS to successfully clone the drive fully.

If the drive is anyway faulty - your more likely to strike it while imaging the system with all your existing recordings - many applications have problems with drives with surface issues. ddrescue is probably the best application for coping a potentially faulty drive - it skips past bad sectors getting most of the data off first them coming back around to get the what it can from the bad areas of the drive.

If you feel comfortable here is a guide on using ddrescue with a Tivo:
http://www.logicsector.com/tivo/how-to-clone-your-failing-tivo-drive-with-ddrescue/

However instead of using the distribution mentioned in that guide I would use a spare USB Drive, and download http://www.system-rescue-cd.org/Installing-SystemRescueCd-on-a-USB-stick/ following the install instructions under C)

Alternatively I'm happy to do this for you at no charge - you would need to leave the original drive with me for a few days for ddrescue to run and do its thing.

Hey thanks Robert - I'll have a look into this and see if I can knock the b*****d off myself; though will possibly end up taking you up on your kind offer. Right now I have both machines hooked up to the TV - one with an upgraded drive for recording, and one with a chock-full 320GB just for playback. Last night I explained to my wife how in order to watch the previously recorded stuff she could simply(!) switch the source on the TV and by flicking the little switch on the remote, control the second Tivo. I perceived some glazing of the eyes... probably in an attempt to stop them rolling!

gregmcc

1579 posts

Uber Geek
+1 received by user: 317

Lifetime subscriber

Reply # 1904150 19-Nov-2017 17:39

rphenix:

gregmcc:

Well, I've had a knock back on Tivo #4, knew there was a problem as before anything was done it wouldn't proceed past the "powering up" screen, most likely a hard drive failure, new drive fitted, same problem, ok 2nd possible fix - power supply - swapped from a known working Tivo, no go, ok maybe the HDD was corrupted, used this new drive in a known working tivo, got all the way thru to the start up menu but got error 51 which upon looking up seems normal when drives are swapped between tivo's.

So I know the HDD is good

Power supply is good

Where to now?

After the powering up screen does it just go to the grey screen or what happens? What is the status of the front of the Tivo after it fails to boot?

It just sits at "Welcome powering up"

There must be another problem as I got a good image from Spong, cloned that to a new HDD and same problem. So something else wrong with the motherboard, look like best to cut my losses with this Tivo and source a working unit to replace it

TinMan55

43 posts

Geek
+1 received by user: 6

Subscriber

Reply # 1904278 20-Nov-2017 06:39

rphenix:

However instead of using the distribution mentioned in that guide I would use a spare USB Drive, and download http://www.system-rescue-cd.org/Installing-SystemRescueCd-on-a-USB-stick/ following the install instructions under C)

Alternatively I'm happy to do this for you at no charge - you would need to leave the original drive with me for a few days for ddrescue to run and do its thing.

This link doesn't appear to be working?

rphenix

858 posts

Ultimate Geek
+1 received by user: 53

Subscriber

Reply # 1904619 20-Nov-2017 14:04

Try this

TinMan55

43 posts

Geek
+1 received by user: 6

Subscriber

Reply # 1904649 20-Nov-2017 14:43

rphenix:

Try this

All good - thanks.

minimoke

710 posts

Ultimate Geek
+1 received by user: 116

Reply # 1904839 20-Nov-2017 21:26

TinMan55:

Last night I explained to my wife how in order to watch the previously recorded stuff she could simply(!) switch the source on the TV and by flicking the little switch on the remote, control the second Tivo. I perceived some glazing of the eyes... probably in an attempt to stop them rolling!

I heard that someone is seeking $15b from the Callinan Institute to initiate a gene research programme into this common trait amongst only the female sex of the species. Money well spent I reckon.

This is essentially the same set up that I'm running. I've got the new empty hard drive recording all the new stuff. And a second TiVo with all the recorded stuff simply hooked to the TV - (no aerial or wifi connection). It runs well (except for trying to explain how the remote needs to work and switch tv between two sources and select one of two settings on the amp. Complicated stuff I know! The only issue I have found is that the remote works both Tivos so i reckon there is a risk if I delete something off one TiVo I may delete it off the other. It hasn't created a problem yet - but I am running this setup aware of the risk and consequently aim to get the recorded programmes viewed real quick. Then its off to my local chip installer fro an upgrade and I'll leave old hard drive as is and put the tivo back where it belongs

Skolink

1077 posts

Uber Geek
+1 received by user: 31

Reply # 1904966 21-Nov-2017 08:04

minimoke:

The only issue I have found is that the remote works both Tivos so i reckon there is a risk if I delete something off one TiVo I may delete it off the other.

Did you know TiVo remotes can be set with an ID?

http://www.oztivo.net/twiki/bin/view/IR/ControlTwoTiVosInSameRoom

https://support.tivo.com/articles/Features_Use/Controlling-2-TiVo-DVRs-with-1-Remote

TinMan55

43 posts

Geek
+1 received by user: 6

Subscriber

Reply # 1906651 23-Nov-2017 17:42

rphenix:

If you feel comfortable here is a guide on using ddrescue with a Tivo:
http://www.logicsector.com/tivo/how-to-clone-your-failing-tivo-drive-with-ddrescue/

However instead of using the distribution mentioned in that guide I would use a spare USB Drive, and download http://www.system-rescue-cd.org/Installing-SystemRescueCd-on-a-USB-stick/ following the install instructions under C)

Alternatively I'm happy to do this for you at no charge - you would need to leave the original drive with me for a few days for ddrescue to run and do its thing.

I was able to create the bootable USB stick and boot my laptop from it, but was not able to "see" the USB-connected Tivo drive or the upgrade drive. Entering the "hdparm -i /dev/sda" command showed the laptop's internal drive, but I couldn't establish the presence of the other drives. Any clues, or am I just pushing it uphill by trying to do this with USB-connected drives?

rphenix

858 posts

Ultimate Geek
+1 received by user: 53

Subscriber

Reply # 1906838 23-Nov-2017 22:42

I would expect the Tivo to be one of /dev/sda /dev/sdb /dev/sdc

Try plugging your USB connected Tivo drive into another port - perhaps a slower non USB3 port will be more likely to detect (usually black instead of blue on the usb port plastic).

In the example above its /dev/sdb for the Tivo drive.

You can try lsblk to show connected drives:

TinMan55

43 posts

Geek
+1 received by user: 6

Subscriber

Reply # 1906870 24-Nov-2017 06:27

Thanks - I'll have another fiddle...

TinMan55

43 posts

Geek
+1 received by user: 6

Subscriber

Reply # 1907841 26-Nov-2017 08:09

rphenix:

I would expect the Tivo to be one of /dev/sda /dev/sdb /dev/sdc

You can try lsblk to show connected drives:

OK lsblk appears to show everything, per this screenshot. sda = laptop HDD, sdb = Tivo HDD, sdc = USB boot stick, sdd = new HDD. Getting anything back using the hdparm command is still eluding me, though I guess that based upon what I'm seeing here, I should be OK to proceed with cloning sdb to sdd? And the correct command would be ddrescue -f -n /dev/sdb /dev/sdd tivo-rescue.log ?

TinMan55

43 posts

Geek
+1 received by user: 6

Subscriber

Reply # 1907843 26-Nov-2017 08:12

Sorry about the orientation of the image!

TinMan55

43 posts

Geek
+1 received by user: 6

Subscriber

Reply # 1908196 27-Nov-2017 00:05

Completed the cloning process successfully - took just over 14.5 hours. Hooked the new drive up to my Tivo and all my recordings appeared to be there - great! However the Tivo was not recognising the additional space on the 1TB drive - said 120hrs. So - I figured I'd restore from the truncated backup I'd taken off the original drive earlier to select access to the extra space. This worked, but though I now have the extra space, I'm back to square one with my recordings!!!

So am not sure what to do now? How to clone the original 320GB drive on to the new 1TB drive to keep all my recordings and also gain the extra space on the new drive???

Help.....?

TinMan55

43 posts

Geek
+1 received by user: 6

Subscriber

Reply # 1908213 27-Nov-2017 07:09

One thing which may be relevant is that I did not carry out the Kickstart 57 which is mentioned to be done following the cloning process. The instructions talked about pressing and holding Pause on the remote when yellow/amber lights start flashing irregularly. I didn't see this happen - just saw a yellow/amber light flash once. I waited for something more to happen, but it just went through and booted as normal so I worked on the assumption that it must have been OK. Maybe that singular flash was my cue to press and hold Pause?

It's a mystery why restoring from the truncated backup has taken me back to where I was after I had tried to copy the drive using Winmfs, as that backup was taken before I did anything else in the way of trying to copy.

I'm guessing I will now need to copy again using ddrescue - just another 14+ hrs - but then what?

1 | 2 | 3 | 4 | 5 | 6