[einstein]

Full marks for initiative - but I provided a link to the recommended CD in the very post you have quoted!
TiVo drives are byteswapped, so to see the partitions listed at startup you need to boot in byteswapped mode.
Try the CD I linked to.

Edit: Doh! I knew I shouldn't have gone to make a cuppa in the middle of writing a post!

I downloaded the iso before you posted at 2.00am last night!, the iso i'm using is mfstools2.iso downloaded from http://mfstools.sourceforge.net/

Which is the recommended cdrom from the Hinsdale guide, I've just checked. Both cdroms are the same, just different links to the same place.

I didn't know, I had to boot in byteswap mode, I assumed the cdrom was setup by default!

Regards

Einstein

 

[blindlemon]

Sorry for staying up late...

That CD should be OK for a 40GB drive - and, no, you don't need to boot in byteswapped mode to make a backup, only if you want to view the partitions.

You do need to use -l32 though, and I would leave off the 6 if you have around 1.4GB free on your FAT drive, as the compression in MFSTools is buggy (and you can always zip the backup if you need to).

However, assuming the CD you're using is OK, then I would suspect that the problem may be caused by the problems you're experiencing with the drive. Can you get mfsinfo to give you any sensible output?

mfsinfo /dev/hdc

 

[blindlemon]

I found a company called "Pacelink" online but they are based in Co Fermanagh

Pacelink are the only company that do board-level repairs to UK TiVos AFAIK - but they can be very expensive so should be viewed as a last resort.

What is this "emergency reboot code 58" I read about on another thread? Might that help me?

The kickstart 58 is a way of getting the TiVo to check (and try to fix) the MFS filesystem under which the data is stored. The operation is similar to ScanDisk under Windows.

Kickstart 52 is more drastic as it forces the TiVo to reinstall the system software from the backup on the unused system partitions. This can sometimes fix more serious problems where system files have become corrupted - but if it goes wrong then you will need to re-image the drive.

The problem you describe could be caused by corruption in the system files, or it could be a motherboard isssue. I would try to eliminate all other options before sending the TiVo away for a m/b repair though as bills of £200+ are not uncommon.

 

[Kissxofxdeath]

Dear blindlemon
Thanks for the reply. Are you suggesting that I should try the kickstart options or are there other things I can try before I send it to Pacelink? Can I diagnose whether it is a software or m.b problem?
Many thanks. KoD

 

[blindlemon]

As I have loads of drives here I'd try replacing the drive first

However, as you don't have a spare drive to hand, try kickstart 57, 58 and 52 in that order. If none of them work then consider configuring or buying a replacement drive before sending the TiVo away to Pacelink.

At least if you configure a drive yourself (or buy a preconfigured drive from the right supplier) you can use it for something else or send it back for a refund if it doesn't fix your problem. If you send the TiVo to Pacelink you're looking at £35 + VAT + postage before you start - and it might still turn out to be just a drive problem.

 

[einstein]

Sorry for staying up late...

That CD should be OK for a 40GB drive - and, no, you don't need to boot in byteswapped mode to make a backup, only if you want to view the partitions.

You do need to use -l32 though, and I would leave off the 6 if you have around 1.4GB free on your FAT drive, as the compression in MFSTools is buggy (and you can always zip the backup if you need to).

However, assuming the CD you're using is OK, then I would suspect that the problem may be caused by the problems you're experiencing with the drive. Can you get mfsinfo to give you any sensible output?

mfsinfo /dev/hdc

No problems for staying up late, I came home late from work, needed to finish a server rebuild, and I've still had no tea yet!

It's just a shame that the MFSTOOLS swap option doesn't work as stated, this had me puzzled for a few minutes.! Worked it out and here goes:-

and here's the output of the Tivo HD (hdc), I can mount hdc4 & hdc7

when I use mfstools and I tried the "l" option -l32, it does the same, screenful of garbage, and hangs. Tomorrow night I'll drop the compression option and re-format the pc hard disk. I'm using FAT32, I shouldn't think that would cause a problem, as the drive is mounted under Linux. Not shown using the -l option in this photo.

I tried mfstools 1.1, and it does the same and reboots the pc.

I don't think this is the screensaver?

I'm really just trying to see, if is worth the spend on a new hard drive. I've three other Tivos, but I not opening them up, and damaging them! I've been there with compaq servers, swapping parts from server to server, and then I've ended up with two dead servers.

blindlemon: Thanks for your continued help, I'll try the msinfo command tomorrow evening, but I suspect it will show similiar output to the partition information at bootup? I'll include the l option, and turn-off compression.

PS you not drunk, some of these shots are out of focus, that's me the crap photographer, and I blame it on a new camera, which has more buttons than the Space Shuttle! (and if I put it in auto, it kills the PC screen with flash, and it could do with being on a tripod, and not handheld by an idiot!)

 

[Kissxofxdeath]

I tried kickstart 57 and the screen went blank and I got a "green screen of death" message saying that I should leave the TiVo connected for 24 hours and not touch it.

What should I do next?

KoD

 

[blindlemon]

Wait...

Normally the GSOD will complete in less than an hour. If it takes longer then that can be an indication that something more serious is wrong. However, it's not unknown for it to take many hours and then complete successfully - just don't unplug the TiVo while you're waiting.

 

[Kissxofxdeath]

Hi blindlemon.

Indeed as you said, it fixed itself in short order.

I have now tried kickstart 58 and 52 as well and none of them have worked.

Does that mean I need a new drive? And if so, can I get one with bigger memory thus hopefully killing two birds with one stone? And can I salvage any of the stuff on the original drive?

Thanks for all your help so far.

KoD

 

[blindlemon]

I have sent you a PM about replacement drives

However, I wouldn't want you to spend money on a new drive until you have tried a few more things. If you can see the input signal when you press "aux" then, as you say, it must be reaching the TiVo.

What options have you selected in Guided Setup? Have you selected the appropriate channels in "channels I receive"?

While watching "Live TV" (the blue screen) try typing the channel number - eg. 101 - and then typing it again. This should force the TiVo to switch from the RF (aerial) input to the AUX scart or vice-versa.

To test that the MPEG encoder is working, if you have an analogue TV aerial (even if the picture through a TV is crap) try, plugging that into the RF-In socket on the TiVo and then go through Guided Setup again choosing Aerial Only. If you can then see and pause a picture on "Live TV" the encoder is OK.

 

[einstein]

Sorry for staying up late...

That CD should be OK for a 40GB drive - and, no, you don't need to boot in byteswapped mode to make a backup, only if you want to view the partitions.

You do need to use -l32 though, and I would leave off the 6 if you have around 1.4GB free on your FAT drive, as the compression in MFSTools is buggy (and you can always zip the backup if you need to).

However, assuming the CD you're using is OK, then I would suspect that the problem may be caused by the problems you're experiencing with the drive. Can you get mfsinfo to give you any sensible output?

mfsinfo /dev/hdc

Thanks for your reply. I still couldn't get mfstools to work, without filling the screen with garbage, so after two other PCs which did the same, I've finally found an old Dual Pentium Pro motherboard which is working

mfstools info reports Standalone 39 hour tivo

I making a few backups to three different hard drives.

But I have discovered it is definately the hard drive, because in the final PC, I observed the same spin-up/power-up problem, the drive is lazy, a small tap with the end of the screwdriver and it span-up, so I'll back it up, get a new hard drive and restore the image.

any special switches I need to restore? Thanks for all your help.

Much appreciated.

 

[einstein]

I've purchased a Seagate 40GB drive today, cheaply from a local shop, to check if I can get this Tivo working, (I've got an arrangement with the shop, it's more of a loan drive) if I can I'll purchase a larger Seagate or Samsung drive.

I'm trying to restore the tivo.bak image and I get the error message First Target Drive Too Small, I've ssearched the forums, and found this is a common error, both drives are 40GB, but Linux reports them slightly differently.

Quantum Tivo drive - 40027
Seagate drive - 39956

I assume this is the problem, and the only thing I can do is find a larger hard drive!

I've even tried piping the out from mfsbackup to mfsrestore, but I get the same error message.

 

[blindlemon]

Yes, this is one of those unusual cases where an error message from software actually means what it says

You might as well just get a big drive now and be done with it. I would think the chance of it being anything other than a drive problem after all you've described is almost nil.

 

[einstein]

Yes, this is one of those unusual cases where an error message from software actually means what it says

You might as well just get a big drive now and be done with it. I would think the chance of it being anything other than a drive problem after all you've described is almost nil.

What still puzzles me is that I get no display from either SCART or RF from the TiVo after power is applied.

I think someone commented that, if the system board detects a drive spin-up, it displays the Welcome, Powering-Up please wait.

With all the working hard drives I have here, and I've tried 10, I don't get any visual indictation anymore that the system board is alive. Fan and Green LED are on.

Can you confirm this is correct?

Although signal on SCART does change, as if some signal is there on the output.

 

[blindlemon]

Normally if you put a working (but non-TiVo) drive into the TiVo then you will see the "Powering up..." message but it won't go any further than that. You do need to connect the IDE cable though - otherwise the drive will spin up but the screen will remain blank as the TiVo's BIOS can't detect anything connected.

 

[einstein]

Normally if you put a working (but non-TiVo) drive into the TiVo then you will see the "Powering up..." message but it won't go any further than that. You do need to connect the IDE cable though - otherwise the drive will spin up but the screen will remain blank as the TiVo's BIOS can't detect anything connected.

Yes, that's the worry, I've not seen any Powering Up.. message even when connecting the drive cable recently, after it reset three times.

My AV channel changes from no-signal (black) to TiVo gray background, but with no text! Apart from a White scan line at the very top of the screen only when I connect a hard drive.

No hard drive connected at power-up Black Screen no output.

Which makes me think the problem is more serious.

 

[blindlemon]

In that case the best thing to do, IMHO, would be to restore your image to a drive and see what happens.

And as a backup option, it might also be an idea to order a replacement PSU. They're so cheap it's worth having one around as a spare anyway.

No point worrying about busted motherboards until you have tried a working TiVo drive + new PSU in the machine....

 

[einstein]

I've noticed from observation that the TiVo has always had problems starting-up the TiVo hard disc when installed in the TiVo, the LED on the hard drive just blinks. Tivo success rate (1%). When it does start it displays Powering Up.. message, and then dies and restarts a three times, until the drive doesn't spin up.

The hard drive always starts most of the time when installed in a PC. (99%).

I decided to connect the Tivos hard drive to a PC's power supply connected to a pc motherboard to load it and turn the ATX psu on.

The Tivo hard drive spins up, Welcome. Powering-Up... Message, Almost There. A Few More Seconds Please... Tivo video and menu and a working Tivo.

I have a possible theroy, that maybe the TiVo hard drive is faulty, and drawing more current than the Tivo psu can maintain (this is a new psu) , and hence it cannot start-up the drive at power-on.

I think it's time to purchase that large hard drive. Thanks for all your help, any recommendations on hard drives, I was probably going to purchase a Seagate with a 5 year warranty.

PS This TiVo does not output a Powering Up.. message when connecting a non-Tivo drive.

 

[einstein]

Now, I've got the the Tivo up and running, I can see looking at the logs, that the Tivo drive is failing

Jan 8 19:04:17 (none) kernel: IDE: read command for sector 967710 bailed with DMA running
Jan 8 19:04:17 (none) kernel: hda: unexpected_intr: status=0x51 { DriveReady SeekComplete Error }
Jan 8 19:04:17 (none) kernel: hda: unexpected_intr: error=0x04 { DriveStatusError }, secCnt=1, LBAsect=967710
Jan 8 19:04:17 (none) kernel: Stopping immediate on Ide
Jan 8 19:04:17 (none) kernel: hda: tivo_dma_intr_direct: status=0x51 { DriveReady SeekComplete Error }
Jan 8 19:04:17 (none) kernel: hda: tivo_dma_intr_direct: error=0x04 { DriveStatusError }, secCnt=1, LBAsect=967710
Jan 8 19:04:20 (none) kernel: IDE: calling handler with dma_running, altstat=0x51
Jan 8 19:04:20 (none) kernel: IDE: read command for sector 1047038 bailed with DMA running
Jan 8 19:04:20 (none) kernel: hda: unexpected_intr: status=0x51 { DriveReady SeekComplete Error }
Jan 8 19:04:20 (none) kernel: hda: unexpected_intr: error=0x04 { DriveStatusError }, secCnt=1, LBAsect=1047038
Jan 8 19:04:20 (none) kernel: Stopping immediate on Ide
Jan 8 19:04:20 (none) kernel: hda: tivo_dma_intr_direct: status=0x51 { DriveReady SeekComplete Error }
Jan 8 19:04:20 (none) kernel: hda: tivo_dma_intr_direct: error=0x04 { DriveStatusError }, secCnt=1, LBAsect=1047038
Jan 8 19:04:26 (none) kernel: IDE: calling handler with dma_running, altstat=0x51
Jan 8 19:04:26 (none) kernel: IDE: read command for sector 1155734 bailed with DMA running
Jan 8 19:04:26 (none) kernel: hda: unexpected_intr: status=0x51 { DriveReady SeekComplete Error }
Jan 8 19:04:26 (none) kernel: hda: unexpected_intr: error=0x04 { DriveStatusError }, secCnt=1, LBAsect=1155734
Jan 8 19:04:26 (none) kernel: Stopping immediate on Ide
Jan 8 19:04:26 (none) kernel: hda: tivo_dma_intr_direct: status=0x51 { DriveReady SeekComplete Error }
Jan 8 19:04:26 (none) kernel: hda: tivo_dma_intr_direct: error=0x04 { DriveStatusError }, secCnt=1, LBAsect=1155734
Jan 8 19:04:30 (none) kernel: IDE: calling handler with dma_running, altstat=0x51
Jan 8 19:04:30 (none) kernel: IDE: read command for sector 950532 bailed with DMA running
Jan 8 19:04:30 (none) kernel: hda: unexpected_intr: status=0x51 { DriveReady SeekComplete Error }
Jan 8 19:04:30 (none) kernel: hda: unexpected_intr: error=0x04 { DriveStatusError }, secCnt=1, LBAsect=950532
Jan 8 19:04:30 (none) kernel: Stopping immediate on Ide
Jan 8 19:04:30 (none) kernel: hda: tivo_dma_intr_direct: status=0x51 { DriveReady SeekComplete Error }
Jan 8 19:04:30 (none) kernel: hda: tivo_dma_intr_direct: error=0x04 { DriveStatusError }, secCnt=1, LBAsect=950532
Jan 8 19:04:52 (none) kernel: IDE: calling handler with dma_running, altstat=0x51
Jan 8 19:04:52 (none) kernel: IDE: read command for sector 956262 bailed with DMA running
Jan 8 19:04:52 (none) kernel: hda: unexpected_intr: status=0x51 { DriveReady SeekComplete Error }
Jan 8 19:04:52 (none) kernel: hda: unexpected_intr: error=0x04 { DriveStatusError }, secCnt=1, LBAsect=956262
Jan 8 19:04:52 (none) kernel: Stopping immediate on Ide
Jan 8 19:04:52 (none) kernel: hda: tivo_dma_intr_direct: status=0x51 { DriveReady SeekComplete Error }
Jan 8 19:04:52 (none) kernel: hda: tivo_dma_intr_direct: error=0x04 { DriveStatusError }, secCnt=1, LBAsect=956262
Jan 8 19:04:56 (none) kernel: IDE: calling handler with dma_running, altstat=0x51
Jan 8 19:04:56 (none) kernel: IDE: read command for sector 1058628 bailed with DMA running
Jan 8 19:04:56 (none) kernel: hda: unexpected_intr: status=0x51 { DriveReady SeekComplete Error }
Jan 8 19:04:56 (none) kernel: hda: unexpected_intr: error=0x04 { DriveStatusError }, secCnt=1, LBAsect=1058628
Jan 8 19:04:56 (none) kernel: Stopping immediate on Ide
Jan 8 19:04:56 (none) kernel: hda: tivo_dma_intr_direct: status=0x51 { DriveReady SeekComplete Error }
Jan 8 19:04:56 (none) kernel: hda: tivo_dma_intr_direct: error=0x04 { DriveStatusError }, secCnt=1, LBAsect=1058628
Jan 8 19:05:00 (none) kernel: IDE: calling handler with dma_running, altstat=0x51
Jan 8 19:05:00 (none) kernel: IDE: read command for sector 951018 bailed with DMA running
Jan 8 19:05:00 (none) kernel: hda: unexpected_intr: status=0x51 { DriveReady SeekComplete Error }
Jan 8 19:05:00 (none) kernel: hda: unexpected_intr: error=0x04 { DriveStatusError }, secCnt=1, LBAsect=951018
Jan 8 19:05:00 (none) kernel: Stopping immediate on Ide
Jan 8 19:05:00 (none) kernel: hda: tivo_dma_intr_direct: status=0x51 { DriveReady SeekComplete Error }
Jan 8 19:05:00 (none) kernel: hda: tivo_dma_intr_direct: error=0x04 { DriveStatusError }, secCnt=1, LBAsect=951018
Jan 8 19:05:09 (none) kernel: IDE: calling handler with dma_running, altstat=0x51
Jan 8 19:05:09 (none) kernel: IDE: read command for sector 1138382 bailed with DMA running
Jan 8 19:05:09 (none) kernel: hda: unexpected_intr: status=0x51 { DriveReady SeekComplete Error }
Jan 8 19:05:09 (none) kernel: hda: unexpected_intr: error=0x04 { DriveStatusError }, secCnt=1, LBAsect=1138382
Jan 8 19:05:09 (none) kernel: Stopping immediate on Ide
Jan 8 19:05:09 (none) kernel: hda: tivo_dma_intr_direct: status=0x51 { DriveReady SeekComplete Error }
Jan 8 19:05:09 (none) kernel: hda: tivo_dma_intr_direct: error=0x04 { DriveStatusError }, secCnt=1, LBAsect=1138382
Jan 8 19:05:17 (none) kernel: IDE: calling handler with dma_running, altstat=0x51
Jan 8 19:05:17 (none) kernel: IDE: read command for sector 985376 bailed with DMA running
Jan 8 19:05:17 (none) kernel: hda: unexpected_intr: status=0x51 { DriveReady SeekComplete Error }
Jan 8 19:05:17 (none) kernel: hda: unexpected_intr: error=0x04 { DriveStatusError }, secCnt=1, LBAsect=985376
Jan 8 19:05:17 (none) kernel: Stopping immediate on Ide
Jan 8 19:05:17 (none) kernel: hda: tivo_dma_intr_direct: status=0x51 { DriveReady SeekComplete Error }
Jan 8 19:05:17 (none) kernel: hda: tivo_dma_intr_direct: error=0x04 { DriveStatusError }, secCnt=1, LBAsect=985376
Jan 8 19:07:40 (none) kernel: IDE: calling handler with dma_running, altstat=0x51
Jan 8 19:07:40 (none) kernel: IDE: read command for sector 1751222 bailed with DMA running
Jan 8 19:07:40 (none) kernel: hda: unexpected_intr: status=0x51 { DriveReady SeekComplete Error }
Jan 8 19:07:40 (none) kernel: hda: unexpected_intr: error=0x04 { DriveStatusError }, secCnt=1, LBAsect=1751222
Jan 8 19:07:40 (none) kernel: Stopping immediate on Ide
Jan 8 19:07:40 (none) kernel: hda: tivo_dma_intr_direct: status=0x51 { DriveReady SeekComplete Error }
Jan 8 19:07:40 (none) kernel: hda: tivo_dma_intr_direct: error=0x04 { DriveStatusError }, secCnt=1, LBAsect=1751222
Jan 8 19:20:51 (none) kernel: IDE: calling handler with dma_running, altstat=0x51
Jan 8 19:20:51 (none) kernel: tivo_dma_intr() called with DMA still running, abort it!
Jan 8 19:20:51 (none) kernel: hda: unexpected_intr: status=0x51 { DriveReady SeekComplete Error }
Jan 8 19:20:51 (none) kernel: hda: unexpected_intr: error=0x04 { DriveStatusError }, secCnt=8, LBAsect=190478
Jan 8 19:20:51 (none) kernel: Stopping immediate on Ide
Jan 8 19:20:51 (none) kernel: hda: tivo_dma_intr: status=0x51 { DriveReady SeekComplete Error }
Jan 8 19:20:51 (none) kernel: hda: tivo_dma_intr: error=0x04 { DriveStatusError }, secCnt=8, LBAsect=190478
Jan 8 19:32:11 (none) kernel: IDE: calling handler with dma_running, altstat=0x51
Jan 8 19:32:11 (none) kernel: tivo_dma_intr() called with DMA still running, abort it!
Jan 8 19:32:11 (none) kernel: hda: unexpected_intr: status=0x51 { DriveReady SeekComplete Error }
Jan 8 19:32:11 (none) kernel: hda: unexpected_intr: error=0x04 { DriveStatusError }, secCnt=2, LBAsect=689600
Jan 8 19:32:11 (none) kernel: Stopping immediate on Ide
Jan 8 19:32:11 (none) kernel: hda: tivo_dma_intr: status=0x51 { DriveReady SeekComplete Error }
Jan 8 19:32:11 (none) kernel: hda: tivo_dma_intr: error=0x04 { DriveStatusError }, secCnt=2, LBAsect=689600
Jan 8 19:35:01 (none) kernel: IDE: calling handler with dma_running, altstat=0x51
Jan 8 19:35:01 (none) kernel: IDE: read command for sector 1956742 bailed with DMA running
Jan 8 19:35:01 (none) kernel: hda: unexpected_intr: status=0x51 { DriveReady SeekComplete Error }
Jan 8 19:35:01 (none) kernel: hda: unexpected_intr: error=0x04 { DriveStatusError }, secCnt=16, LBAsect=1956742
Jan 8 19:35:01 (none) kernel: Stopping immediate on Ide
Jan 8 19:35:01 (none) kernel: hda: tivo_dma_intr_direct: status=0x51 { DriveReady SeekComplete Error }
Jan 8 19:35:01 (none) kernel: hda: tivo_dma_intr_direct: error=0x04 { DriveStatusError }, secCnt=16, LBAsect=1956742
Jan 8 19:34:46 (none) kernel: IDE: calling handler with dma_running, altstat=0x51
Jan 8 19:34:46 (none) kernel: IDE: read command for sector 1956742 bailed with DMA running
Jan 8 19:34:46 (none) kernel: hda: unexpected_intr: status=0x51 { DriveReady SeekComplete Error }
Jan 8 19:34:46 (none) kernel: hda: unexpected_intr: error=0x04 { DriveStatusError }, secCnt=16, LBAsect=1956742
Jan 8 19:34:46 (none) kernel: Stopping immediate on Ide
Jan 8 19:34:46 (none) kernel: hda: tivo_dma_intr_direct: status=0x51 { DriveReady SeekComplete Error }
Jan 8 19:34:46 (none) kernel: hda: tivo_dma_intr_direct: error=0x04 { DriveStatusError }, secCnt=16, LBAsect=1956742
Jan 8 19:34:54 (none) kernel: IDE: calling handler with dma_running, altstat=0x51
Jan 8 19:34:54 (none) kernel: IDE: read command for sector 1956742 bailed with DMA running
Jan 8 19:34:54 (none) kernel: hda: unexpected_intr: status=0x51 { DriveReady SeekComplete Error }
Jan 8 19:34:54 (none) kernel: hda: unexpected_intr: error=0x04 { DriveStatusError }, secCnt=16, LBAsect=1956742
Jan 8 19:34:54 (none) kernel: Stopping immediate on Ide
Jan 8 19:34:54 (none) kernel: hda: tivo_dma_intr_direct: status=0x51 { DriveReady SeekComplete Error }
Jan 8 19:34:54 (none) kernel: hda: tivo_dma_intr_direct: error=0x04 { DriveStatusError }, secCnt=16, LBAsect=1956742

So hopefully, a new drive will cure the fault.

 

[einstein]

Now, I've got the the Tivo up and running, I can see looking at the logs, that the Tivo drive is failing

<big snip?

So hopefully, a new drive will cure the fault.

and then after a call home to Tivo it did this:-

me thinks it's hard drive for certain now!