Looping booting with filessystem assert

[danhi]

I had shutdown my TiVo (S1) and when I tried to reboot it would cycle through booting, green screen of death (for a very short time) then boot again. So I took out the hard drives, reimaged from an image that I've used several times before, and now it loops booting, but never gets the GSOD. I put the disks back in the PC and looked at the log, and I get the following:

Filesystem assert blksize > 0 at fphysdisk.c line 156 in FsPhysDisk::FsPhysDisk (struct * FsInitParms *, const char *)

Not sure if that's perfect, since I had to write it down.

Anyway, it looks to me like somethings wrong with the disk after I restored it. Can anyone give me a clue as to what I might have done wrong, or if there's something wrong with the unit itself.

One thought I had (before I looked at the log) is that I've never replaced the CMOS battery, and I've had the unit since 2001. If the CMOS battery dies, does that create any serious problems? If so, how do you replace it. It looks like you'd have to take the motherboard out of the unit to get to the battery!

Any help would be greatly appreciated.

Dan

[eastwind]

Run diagnostics on the HD. Might be going bad. You can use destructive or non-destructive, but do a full scan.

ew

[danhi]

I ran the extended diagnostics on both drives, which passed with no errors, then went the extra step and actually wrote all zero's to the A drive. Then did the restore, looked at it and it looked fine, put them back in the TiVo and same problem.

Anything else I can try. I miss my TiVo?

Anyone know if a bad CMOS battery will create problems?

Dan

[danhi]

After reading through lots of posts in the forum, I found a couple that reference bad ribbon cables. So I replaced the ribbon cable, and voila! It went to the GSOD, then after a bit rebooted and all looks good.

How a ribbon cable can go bad, is quite beyond me, but I'm just happy that I'm (hopefully) on the road to recovery.

Dan