Possible problem with MFS Tools or 3.1....I think...

[A.C.]

....but I'm not sure and I need some help. I just upgraded my T60 to a WD 120 SE, ( I know the extra cache probably means nothing, but hey..79 bux). After I got everything up and running I was looking around in the kernel log, and saw something that I thought was weird:

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

The line that bothers me is the one about a bad sector. So I started to do some checking. First I checked my old WD120 2 MB drive, and it had the same error. Then I checked my factory fresh drive that came with the T60. The factory drive's kernel log didn't have the bad sector error message. So then I thought I'd check both of my WD drives with the WD tools that ship with the drive, and no drive errors.

So I'm really confused and I'm wondering if anyone has any ideas. The only difference from the factory fresh drive and what I'm running now is new software and the use if mfstools to do the upgrade.

Can someone else who is using a WD120 check their kernel log and see if they have the message? Thanks

[A.C.]

Anyone who has an WD120 in their DTivo running tivoweb check their kernel log????

[nevdull]

Got WD80 running Xtreme 2.5.2 and have seen this same error on 2 different drives.

Both times WD's DLGDIAG for windows failed on the quick test telling me to return the drive but passed on the extended test.

Hmmm....

=- nevdull

[mozilla]

I have this exact same error with the EXACT same sector.

I had used a WD 120GB first. Worked fine for a couple of months. Then it started rebooting at which time I noticed the error.

I brought my old original Tivo 40GB drive out of storage, and made another backup of that drive. Installed that and expanded it to 200GB drive (which of course only recognized the 137GB limit).

I notice again, on the first boot that it has the EXACT same error with the EXACT same sector as listed here.

It seems to me there's a problem with the MFS tools.