TiVo Frozen - any suggestions?

Advertisements

You need to find the later version of smartctl for TiVo then.

 

Hi Ian,

Thanks for your reply. - I'll give that a go

Daniel

 

I've just uploaded it, and tried again, but just get the same.

Is there an easy way to see if it is picking up an old copy from another location ??

Thanks in advance,
Daniel

 

OK, I found another copy of smartctl and upgraded to the version on this thread.

When I try and run it I get the following error:

BUG IN DYNAMIC LINKER ld.so: dynamic-link.h: 46: elf_get_dynamic_info: Assertion
`! "bad dynamic tag"' failed!

I have tried downloading again and reuploading, but still get the same ??

Any ideas ?

Thanks again
Daniel

 

Advertisements

Where to get this please and how/where to install it?

 

I've managed to get the smartctl working on my Tivo.

The 'Reallocated_Sector_Ct' is showing as 1 on both by hda and hdb drives.

Does anyone know exactly what this means?? - Is this bad sectors ?

Thanks
Daniel

 

In my experience anything other than zero is bad news.....

This means the drive has detected a duff sector and assigned a new one to replace it (sometimes on same drive "cylinder" or sometimes at edge of disk). As I said before we have embedded PC systems that count anything other than zero as a failure and require a drive replacement, preferably sooner rather than later.

One of my TiVo drives had 'Reallocated_Sector_Ct' of 2 for ages (9 months) before, as would be expected, it suddenly got larger, TiVo rebooted/froze a couple of times then died as the disk expired.

Its a shame the TiVo version of SMARTCTL is not complete/full as it cannot retreive the full logs (smartctl -l selftest /dev/hda), so you could asertain how old the drive was when the error occured and base your disk replacement timescale upon if it is recent or old error.

Are your drives mounted on the bracket ? Reason I ask is one of our customers had an excessively high drive failure rate and this was traced to bolting the drive straight to the system chassis. Mount drive on a carrier plate/cradle bolted to chassis and suddenly, no failures.

 

The title to this thread sums it up. My TiVo is freezing every day. It doesn't respond to the remote and there is no tivoweb or telnet.

Ive already put in a new power supply to no avail and have downloaded and run smartctl. 'Reallocated_Sector_Ct' is showing 0, so I guess the disk is OK. It's a 250Gb Samsung and about 18 months old.

Does anyone have any suggestions as to what I could try next?

Thanks

 

Not necessarily.

The TiVo OS doesn't have the smarts to force the drive to reallocate bad sectors so your drive could be a mess!

I would pull the drive and check it with HUTIL. If it has bad sectors then it shoud be replaced. You can get a warranty replacement from www.rexo.co.uk in about a week as long as it is less than three years old

 

Thanks for that. I'll have a look at hutil and see what it comes up with.

BTW the disk was supplied as an upgrade from tivoheaven

 

If you would like me to handle the RMA and reconfigure it then just drop me an email or PM

 

Would you like to try my tale of woe?
My series 1 TIvo with 120G disk, Tivoweb, Endpad and Tystudio has been running beautifully for many years. It has now started freezing - usually on a Monday evening. It says it is recording, but does not respond to the remote in any way, and Tivoweb does not work. On reboot it continues to record as it should have been. The last bit of recorded program does seem to have a hole in it.The logs dont show anything that looks odd to me:

Everyone seems to blame the hard drive, so I tried smartctl. Again it all looked quite good:

Any other thoughts??

 

My Tivo has started freezing as described above as well ! ?
I deleted the last 10 hrs of progs & that did nothing, still freezing after a few hrs & OK on reboot for a few hrs.
Then deleted ~50hrs of progs - and it hasen't frozen for a few days now.

 

How very odd. My main TiVo hung while recording Monday as well, as well as hanging yesterday. Logs show nothing exciting.

Perhaps there's a bit of dodgy data from the daily call filtering through?