Dying TiVo?

Discussion in 'TiVo Series 1 - UK' started by ptruman, Sep 26, 2006.

  1. ptruman

    ptruman New Member

    190
    0
    Jan 8, 2003

    Advertisements

    Hi all,

    For the last couple of days, TiVo has randomly rebooted, or, this morning, just been "dead" - until a coldboot.

    Squizzing around in /var/logs - are there any specifics I could/should look for?

    Cheers!

    Mr P.
     
  2. blindlemon

    blindlemon tivoheaven.co.uk

    5,577
    0
    May 12, 2002
    Malmesbury, UK
    Look for references in the kernel or tverr logs to DMA errors or uncorrectable sector errors.

    If I were you I would be thinking about replacing that drive ASAP, as if it's failing then it will only be a matter of time before you lose a sector so critical your TiVo won't boot at all - and then you can pretty much say goodbye to everything on the drive :eek:
     
  3. ptruman

    ptruman New Member

    190
    0
    Jan 8, 2003
    I have seen something about DMA - but was on a remote console, so will check it in more detail later. It's a 250GB drive - can I do a straight clone using something like partition magic or the Tivo MFS tools?
     
  4. blindlemon

    blindlemon tivoheaven.co.uk

    5,577
    0
    May 12, 2002
    Malmesbury, UK
    If the drive isn't full then MFSTools wil be the fastest option as it only takes actual content as opposed to blindly copying sectors.

    If you have network access you can speed things up further by using my PurgeDeleted script first too so that only required recordings are copied. Be prepared for an overnight job though with a 250gb drive unless it's virtually empty - and if you have many bad sectors you might end up having to copy the whole drive with something like dd_rescue ...which can take up to two weeks :eek:
     

    Attached Files:

  5. ptruman

    ptruman New Member

    190
    0
    Jan 8, 2003

    Advertisements

    Well, heres the dumps from the last wibble this morning :

    KERNEL :

    Sep 26 03:11:22 (none) kernel: tcp_keepalive: call keepopen(0x8047b3c0)
    Sep 26 03:12:37 (none) kernel: tcp_keepalive: call keepopen(0x8047b3c0)
    Sep 26 03:13:52 (none) kernel: tcp_keepalive: call keepopen(0x8047b3c0)
    Sep 26 03:15:07 (none) kernel: tcp_keepalive: call keepopen(0x8047b3c0)
    Sep 26 03:15:37 (none) kernel: IDE: calling handler with dma_running, altstat=0x51
    Sep 26 03:15:37 (none) kernel: IDE: read command for sector 207607360 bailed with DMA running
    Sep 26 03:15:37 (none) kernel: hda: unexpected_intr: status=0x51 { DriveReady SeekComplete Error }
    Sep 26 03:15:37 (none) kernel: hda: unexpected_intr: error=0x40 { UncorrectableError }, secCnt=0, LBAsect=6280768
    Sep 26 03:15:37 (none) kernel: Stopping immediate on Ide
    Sep 26 03:15:37 (none) kernel: hda: tivo_dma_intr_direct: status=0x51 { DriveReady SeekComplete Error }
    Sep 26 03:15:37 (none) kernel: hda: tivo_dma_intr_direct: error=0x40 { UncorrectableError }, secCnt=0, LBAsect=6280768
    Sep 26 03:15:41 (none) kernel: hda: tivo_dma_intr_direct: status=0x51 { DriveReady SeekComplete Error }
    Sep 26 03:15:41 (none) kernel: hda: tivo_dma_intr_direct: error=0x40 { UncorrectableError }, secCnt=0, LBAsect=207607360
    Sep 26 03:15:41 (none) kernel: IDE: DMA in a strange state
    Sep 26 03:15:41 (none) kernel: FPGA callback with DMA not running - delayed interrupt?
    Sep 26 03:15:50 (none) kernel: IDE: tivo DMA engine aborted
    Sep 26 03:15:50 (none) kernel: hda: irq timeout: status=0x58 { DriveReady SeekComplete DataRequest }
    Sep 26 03:15:50 (none) kernel: hda: irq timeout: error=0x00 { }, secCnt=1, LBAsect=57823897
    Sep 26 03:15:50 (none) kernel: hda: disabled DMA
    Sep 26 03:15:50 (none) kernel: hda: ide-tivo re-enabled DMA
    Sep 26 03:15:51 (none) kernel: ide0: reset: success

    Whereupon it did bugger all till 3 mins past midnight, and seems to have rebooted itself.

    The next chunk is after it's cachecard init, and then it froze until the missus rebooted it this morning...

    Jan 1 00:03:14 (none) kernel: sys_readsectors: filp is NULL
    Jan 1 00:03:14 (none) kernel: cachectl: 512MB database detected
    Jan 1 00:03:14 (none) kernel: cachectl: Writing.... 0% .... 25% .... 50% .... 75% .... 100% cachectl:
    Jan 1 00:03:14 (none) kernel: cachectl: Verifying... 0% .... 25% .... 50% .... 75% .... 100% cachectl:
    Jan 1 00:03:14 (none) kernel: cachecard: zone[0] = 0:10 (512MB)
    Jan 1 00:03:14 (none) kernel: cachecard: zone[1] = 0:12 (0MB)
    Jan 1 00:03:14 (none) kernel: cachectl: Caching.... 0% .... 25% .... 50% .... 75% .... 100% cachectl:
    Jan 1 00:03:14 (none) kernel: Writing 401560 bytes to OSD at address 0
    Jan 1 00:03:14 (none) kernel: Update IR microcode using /sbin/irmicro.hex
    Jan 1 00:03:14 (none) kernel: Atmel part found, 2kB of program memory, AT90S2313
    Jan 1 00:03:14 (none) kernel: MicroVeriry: bad=0, GetFpaRegCnt=0, AndFpgaCnt=0, OrFpgaCnt=0
    Jan 1 00:03:14 (none) kernel: Device already programmed with this microcode
    Jan 1 00:03:14 (none) kernel: Starting update ...
    Jan 1 00:03:14 (none) kernel: Look for debug board ...
    Jan 1 00:03:14 (none) kernel: SIOCSIFHWADDR: Operation not supported by device
    Jan 1 00:03:14 (none) kernel: IP struct was not filled in!
    Jan 1 00:03:14 (none) kernel: sa is: 0x20000 0x0 0x7ffffcf4 0x7ffffd10
    Jan 1 00:03:14 (none) kernel: sa.sin_addr = 0x7ffffc58 a sockaddr is 16 bytes
    Jan 1 00:03:14 (none) kernel: SIOCSIFADDR: Operation not supported by device
    Jan 1 00:03:14 (none) kernel: eth0: unknown interface.
    Jan 1 00:03:14 (none) kernel: Setting TCP keepalive parameters...
    Jan 1 00:03:14 (none) kernel: Starting logging daemons...
    Jan 1 00:03:14 (none) kernel: Check for PROM update ...
    Jan 1 00:03:14 (none) kernel: Loading mixaud ...
    Jan 1 00:03:14 (none) kernel: Updating system clock UID=0
    Sep 26 08:26:19 (none) kernel: Time set to: Tue Sep 26 08:26:19 2006
    Sep 26 08:26:19 (none) kernel: Have a nice day.


    TVERR :

    Sep 26 03:15:51 (none) TvMomMpegSink[151]: Tmk Fatal Error: Thread TvMomMpegSink <151> died due to signal 11
    Sep 26 03:15:51 (none) TvMomMpegSink[151]: NIP 0x1b79b28 link 0x1b79a2c ctr 27618432
    Sep 26 03:15:51 (none) TvMomMpegSink[151]: R00 0x00008b63 R01 0x7fffee40 R02 0x00000100 R03 0x300164dc
    Sep 26 03:15:51 (none) TvMomMpegSink[151]: R04 0x45189b67 R05 0x00000005 R06 0x00000004 R07 0x00004000
    Sep 26 03:15:51 (none) TvMomMpegSink[151]: R08 0xa38643f2 R09 0x300164dc R10 0x00040000 R11 0x30321004
    Sep 26 03:15:51 (none) TvMomMpegSink[151]: R12 0xa3954600 R13 0x01da9208 R14 0x00000000 R15 0x00000000
    Sep 26 03:15:51 (none) TvMomMpegSink[151]: R16 0x018bf48c R17 0x00000000 R18 0xffffffff R19 0xffffffff
    Sep 26 03:15:51 (none) TvMomMpegSink[151]: R20 0x00000080 R21 0x01d40000 R22 0x01d40000 R23 0x00000cc0
    Sep 26 03:15:51 (none) TvMomMpegSink[151]: R24 0x000e8beb R25 0x000001c7 R26 0x7fffef28 R27 0x00000001



    Bloody drive is < 1 year old too! Bought it from someone on this forum (via eBay)
     
  6. blindlemon

    blindlemon tivoheaven.co.uk

    5,577
    0
    May 12, 2002
    Malmesbury, UK
    Unfortunately drives can die at any time and even the best makes do sometimes fail early.

    Try contacting the selller to see if there is a warranty if it's less than a year since your purchase.
     
  7. ptruman

    ptruman New Member

    190
    0
    Jan 8, 2003
    Too late, I've got a new Maxtor Maxline III 250GB drive.

    Can someone give me some idiot proof instructions for using MFS tools? I will remove all Windows drives from the PC first :)
     
  8. blindlemon

    blindlemon tivoheaven.co.uk

    5,577
    0
    May 12, 2002
    Malmesbury, UK
    You should still be able to get a replacement drive from the manufacturer :)

    For MFSTools the Bible is Hinsdale. Just use a LBA48-aware boot CD and run copykern after the restore to copy the kernel and initialise the bigger swap.
     
  9. ptruman

    ptruman New Member

    190
    0
    Jan 8, 2003
    I got my drive from Ashmeadboy on eBay - I think he's on the forum, but it's March 2005 I bought it, so over a year anyway :)

    I'll check Hinsdale later!
     
  10. blindlemon

    blindlemon tivoheaven.co.uk

    5,577
    0
    May 12, 2002
    Malmesbury, UK
    That's me, and as you have noticed the drive is now out of warranty from myself - but it will still be covered by Seagate's warranty, so you can send it back to them and get a bare replacement drive to use in your PC etc. :)
     

Share This Page

spam firewall

Advertisements