Reboot and freeze

[bato]

My Hughes Dtivo just started to reboot and feeze.

I unpluged the unit for a minute, replug boot normal, get 100% then display channels and without telling anything reboot, everything is done again but this time it freezes and I lost telnet/bash.

I have the logs, but I didn't have the time to rz send them, which one is the right to debug? /var/log/kernel? I checked it a bit and the system want to remove a file in /var/tmp but it can't.

The drive was full (new recordings dumping old) but I just deleted some movies, so now there is some space available.

Any ideas? Thanks.

[bato]

Update: I chattr -i the file and in the reboot /var was rebuilt, so now my logs only include the info after it began the reboots and not before (this hard drive is working since last August).

After a couple reboots, it freezes again. The only thing I can find in /var/log/kernel is:


Jan 1 00:00:16 (none) kernel: Cannot find map file.
Jan 1 00:00:16 (none) kernel: Partition check:
Jan 1 00:00:16 (none) kernel: hda:hda: recal_intr: status=0xd0 { Busy }
Jan 1 00:00:16 (none) kernel: hda: recal_intr: error=0xd0 { BadSector UncorrectableError SectorIdNotFound }, secCnt=208, LBAsect=13684944
Jan 1 00:00:16 (none) kernel: hda: disabled DMA
Jan 1 00:00:16 (none) kernel: hda: ide-tivo re-enabled DMA
Jan 1 00:00:16 (none) kernel: RAMDISK: Couldn't find valid ramdisk image starting at 0.
Jan 1 00:00:16 (none) kernel: EXT2-fs warning: mounting unchecked fs, running e2fsck is recommended
Jan 1 00:00:16 (none) kernel: warning: can't open /var/mtab: No such file or directory
Jan 1 00:00:16 (none) kernel: umount: /initrd: not mounted
Jan 1 00:00:16 (none) kernel: ext2fs_check_if_mount: No such file or directory while determining whether /dev/hda9 is mounted.
Jan 1 00:00:16 (none) kernel: /dev/hda9 was not cleanly unmounted, check forced.
Jan 1 00:00:16 (none) kernel: ext2fs_check_if_mount: No such file or directory while determining whether /dev/hda9 is mounted.
Jan 1 00:00:16 (none) kernel: /dev/hda9: clean, 76/32768 files, 7068/131072 blocks
Jan 1 00:00:16 (none) kernel: /dev/hda9 is clean after pass 2
Jan 1 00:00:16 (none) kernel: Attempting to fix modem using: /tvlib/modem/patches/P2109-V90/ram/expect_script
Jan 1 00:00:16 (none) kernel: spawn /tvbin/modempatch /tvlib/modem/patches/P2109-V90/ram/Patch9-2-RAM.s37
Jan 1 00:00:17 (none) kernel: SIOCSIFHWADDR: Operation not supported by device
Jan 1 00:00:17 (none) kernel: IP struct was not filled in!
Jan 1 00:00:17 (none) kernel: SIOCSIFADDR: Operation not supported by device
Jan 1 00:00:17 (none) kernel: eth0: unknown interface.
Jan 3 09:41:22 (none) kernel: route.tivo forgot to specify route netmask.
Jan 3 09:41:23 (none) kernel: eth0: unknown interface.

and the last line

Jan 3 09:43:23 (none) kernel: ApgManager Transition from state EXPRESSION_EVALUATION to STEADY_STATE


after this is either a reboot or a complete freeze. Can this info help me point the problem?

[fixn278]

I can't be sure, as I have never really looked inside the Tivo logs before, but based on my PC knowledge, I would say your hard-disk is about to bite the dust.

The unrecoverable read error points me to your hard disk.

I would check it with whatever tool the disk manufacturer makes. Keep in mind, if you fix any errors you may need to reload the drive anyway.

Good luck

[bato]

Thanks, I was afraid of that.

Another look at the logs point me in that direction also, it wanted to remove all info in /var to clean it, but it say it can clean /var so it recreated it, writing blocks again.
Jan 1 00:00:35 (none) kernel: /dev/hda9: UNEXPECTED INCONSISTENCY; RUN fsck MANUALLY.
Jan 1 00:00:35 (none) kernel: ^I(i.e., without -a or -p options)
Jan 1 00:00:35 (none) kernel: Can't clean /dev/hda9 - rebuilding

I'll do the following steps:
- remove drive and mount the original 40GB to make sure is the drive
- try to make a backup with Hinsdale How to
- check the drive with manufacturer disk
- hope for the best, there are some recordings I want to keep but in the 5 or so minutes window I can't use tytool

oh, well, not the first drive that bite the dust and sure not the last.

OT: how well the Samsung 120gb 5400 work?

[fixn278]

Originally posted by bato

- hope for the best, there are some recordings I want to keep but in the 5 or so minutes window I can't use tytool



Maybe there's a spot on the empty portion of the drive that's giving you trouble and when it buffers to it, you crash.

Try tuning to music channels on both tuners as soon as it boots up. Maybe you'll get lucky and be able to extract your videos.

[bato]

Originally posted by fixn278
Maybe there's a spot on the empty portion of the drive that's giving you trouble and when it buffers to it, you crash.

Try tuning to music channels on both tuners as soon as it boots up. Maybe you'll get lucky and be able to extract your videos.

Tried tuning to music channels - reboot.
Tried changing to channel 90 and 91 (not available) - reboot.
Checked the logs and in tvlog I found the process of indexing, so I unplug both sat cables and reboot the tivo, now I watched a 30min show and now is at 30min from 2 hour movie and extracting with tytool at the same time.

So somewhere in the indexing area there is a problem, or maybe some data corrupt.

Do you think I can select delete program guide and todo list and this will fix my problem?

Any way, I'll try to watch some recordings and tytool others and then test some more. Too bad I can't record anything until I fix it.

Thanks a lot.

[A.C.]

bato,

I was looking at my log of a newly upgraded T60 and noticed the same message, BadSector UncorrectableError. What did you end up figuring out? So far, about a week, my system is stable. So I went back and looked at my old drive, which was also an upgrade I did, and the same error message is in that log too. Just a guess, but is your drive a WD120 GB? I'm starting to wonder if the problem isn't with the factory drive, and if the data of the factory drive on that sector might have been corrupt.

[nevdull]

I have now had two different WD80 drives end up with errors on LBAsect=13684944. which cause reboots.. Either the error is just giving a bogus LBA or WD has a firmware issue. My WD80's are Serial # WD-WMAA51143263 and WD-WMAA51096863.

Anyone else seeing this? Anyone see errors from LBAsect=13684944 with some other drive manufacturer?

=- nevdull