Originally Posted by bmgoodman
Does Kickstart 52 download the OS from Tivo or copy the current OS to the alternate partitions? I tried the KS 52 several times on the drive already with no change in the boot loop. It sounds like the corruption is in the MFS database. I guess there's no going back. Thanks for the info.
Kickstart 52 unpacks the "slices" stored in MFS into the alternate root/kernel partitions. There is a CRC check, IIRC, so it should match exactly what was download from TiVo, or it will fail.
We might be able to sort out what is causing the reboot from a serial console log, but you'd have to get setup with a serial console cable. If this is a TiVoHD, that involves some additional hardware to convert TTL signal levels to RS232. On an S3, you need a special cable and will still need to open the case to attach it. More information on serial console cables is available over at DDB.
Another alternative would be to extract the logs via linux on a PC (e.g. mfstools/mfslive). How much is on disk depends on how far it is getting before the reboot. Is it getting to the "... just a few minutes more" screen? If so, there may be useful information in the on disk logs. Basically all the logs in subdirectory 'log' in partition 9 may be of interest.