TV1 and TV2 - What happened to the rest?

[TimesOwn]

Hi
For some reason one of my Thomson TiVos has lost all channels, except for TV1 and TV2 in TWP running v1.3.1. It rebooted itself after awhile of running like this. A second one of much same configuration continues to run without this issue. What to do from here would be much appreciated! This is in Wellington.

[DJC]

What headends are the tivos on, if they are different lets check the data. Worst case a clear and delete of the guide on the bad unit should refresh things.

[TimesOwn]

Using postcode 02124. The funny thing is the channels are there when using the remote, just TWP not offering them anymore!
I also note this in /var/log/kernel/
Apr 19 13:26:21 (none) kernel: hda: drive_cmd: status=0x51 { DriveReady SeekComplete Error }
Apr 19 13:26:21 (none) kernel: hda: drive_cmd: error=0x04 { DriveStatusError }, secCnt=1, LBAsect=12734279
Apr 19 16:51:21 (none) kernel: hda: drive_cmd: status=0x51 { DriveReady SeekComplete Error }
Apr 19 16:51:21 (none) kernel: hda: drive_cmd: error=0x04 { DriveStatusError }, secCnt=1, LBAsect=12734271
Apr 19 17:07:08 (none) kernel: mediaswitch: returning 0 from standin tune after tuning to ch 0 with adjust 0
I did a Full Channel reload in TWP and that seems to have fixed it. Odd.

[slangnz]

Using postcode 02124. The funny thing is the channels are there when using the remote, just TWP not offering them anymore!
I also note this in /var/log/kernel/
Apr 19 13:26:21 (none) kernel: hda: drive_cmd: status=0x51 { DriveReady SeekComplete Error }
Apr 19 13:26:21 (none) kernel: hda: drive_cmd: error=0x04 { DriveStatusError }, secCnt=1, LBAsect=12734279
Apr 19 16:51:21 (none) kernel: hda: drive_cmd: status=0x51 { DriveReady SeekComplete Error }
Apr 19 16:51:21 (none) kernel: hda: drive_cmd: error=0x04 { DriveStatusError }, secCnt=1, LBAsect=12734271
Apr 19 17:07:08 (none) kernel: mediaswitch: returning 0 from standin tune after tuning to ch 0 with adjust 0
I did a Full Channel reload in TWP and that seems to have fixed it. Odd.

Dude, that sounds like a hard drive error to me....

Cheers -