Fatal Error: Thread myworld <153> died due to signal -2

[tivoking]

My DiretTivo was runing fine for weeks but
while I was watching a recorded show it just did a reboot and now it just cycles thru "almost there.." then reboot.
It will get past the Cache Card startup writing, reading and caching til the almost there screen then it just reboots.
I runs long enough for me to telnet in but not long enough to do anything else.
I had to remove the harddrive and install it to my pc.
From the PC I checked out the log files.

The only hacks I have on this DTivo is the Tivoweb+.

Can any one figure out what wrong?
Last part of tverr and kernel log file are below.

Thanks


FROM tverr

Jul 21 22:55:29 (none) TmkAssertionFailure[173]: (Audit, line 31 ())
Jul 21 22:55:29 (none) myworld[173]: Tmk Fatal Error: Thread myworld <173> died due to signal -2
Jul 21 22:55:29 (none) myworld[173]: Tmk Thread Backtrace: 1b3b12c 1b39a10 1d33804 1d22998 1d2286c 1949ba0 1a92180 1a91be0

194c65c 1cc21b0 190afe0 1c26108 1c25898 1c24dd8 1c24a3c 1c24958 1c24c24 1c24594 190778c 1dfda1c 1dfdadc 1dfdb90 1c1f73c 1d66d5c

1800134
Jul 21 22:55:29 (none) myworld[173]: Tmk Fatal Error: Thread died due to signal -2
Jul 21 22:55:29 (none) myworld[173]: Invoking rule 834: rebooting system
Jul 21 22:59:30 (none) TmkAssertionFailure[152]: (Audit, line 31 ())
Jul 21 22:59:30 (none) myworld[152]: Tmk Fatal Error: Thread myworld <152> died due to signal -2
Jul 21 22:59:30 (none) myworld[152]: Tmk Thread Backtrace: 1b3b12c 1b39a10 1d33804 1d22998 1d2286c 1949ba0 1a92180 1a91be0

194c65c 1cc21b0 190afe0 1c26108 1c25898 1c24dd8 1c24a3c 1c24958 1c24c24 1c24594 190778c 1dfda1c 1dfdadc 1dfdb90 1c1f73c 1d66d5c

1800134
Jul 21 22:59:30 (none) myworld[152]: Tmk Fatal Error: Thread died due to signal -2
Jul 21 22:59:30 (none) myworld[152]: Invoking rule 834: rebooting system
Jul 21 23:03:30 (none) TmkAssertionFailure[152]: (Audit, line 31 ())
Jul 21 23:03:30 (none) myworld[152]: Tmk Fatal Error: Thread myworld <152> died due to signal -2
Jul 21 23:03:30 (none) myworld[152]: Tmk Thread Backtrace: 1b3b12c 1b39a10 1d33804 1d22998 1d2286c 1949ba0 1a92180 1a91be0

194c65c 1cc21b0 190afe0 1c26108 1c25898 1c24dd8 1c24a3c 1c24958 1c24c24 1c24594 190778c 1dfda1c 1dfdadc 1dfdb90 1c1f73c 1d66d5c

1800134
Jul 21 23:03:30 (none) myworld[152]: Tmk Fatal Error: Thread died due to signal -2
Jul 21 23:03:30 (none) myworld[152]: Invoking rule 834: rebooting system
Jul 21 23:07:31 (none) TmkAssertionFailure[153]: (Audit, line 31 ())
Jul 21 23:07:31 (none) myworld[153]: Tmk Fatal Error: Thread myworld <153> died due to signal -2
Jul 21 23:07:31 (none) myworld[153]: Tmk Thread Backtrace: 1b3b12c 1b39a10 1d33804 1d22998 1d2286c 1949ba0 1a92180 1a91be0

194c65c 1cc21b0 190afe0 1c26108 1c25898 1c24dd8 1c24a3c 1c24958 1c24c24 1c24594 190778c 1dfda1c 1dfdadc 1dfdb90 1c1f73c 1d66d5c

1800134
Jul 21 23:07:31 (none) myworld[153]: Tmk Fatal Error: Thread died due to signal -2
Jul 21 23:07:31 (none) myworld[153]: Invoking rule 834: rebooting system
******************************************************************************

FROM kernel

Jul 21 23:06:35 (none) kernel: Time set to: Fri Jul 21 23:06:35 2006
Jul 21 23:06:35 (none) kernel: Have a nice day.
Jul 21 23:06:35 (none) kernel: Configuring network...
Jul 21 23:06:35 (none) kernel: turbonet2: driver version 20050218
Jul 21 23:06:35 (none) kernel: turbonet2: using MAC address 00:0B:AD:68:A4:BF
Jul 21 23:06:35 (none) kernel: turbonet2: driver successfully installed
Jul 21 23:06:35 (none) kernel: turbonet2: driver successfully installed
Jul 21 23:06:35 (none) kernel: Checking for additional disk...
Jul 21 23:06:35 (none) kernel: Starting EventSwitcher...
Jul 21 23:06:36 (none) kernel: Not going to start Test service with NULL executable
Jul 21 23:06:36 (none) kernel: Not going to start Epg Manager (/tvbin/EpgManager isn't an existing executable)
Jul 21 23:06:36 (none) kernel: Not going to start thttpd (/tvbin/thttpd isn't an existing executable)
Jul 21 23:06:36 (none) kernel: Not going to start DmComponent (/tvbin/DmComponent isn't an existing executable)
Jul 21 23:06:36 (none) kernel: Not going to start IdlComponent (/tvbin/idl-component isn't an existing executable)
Jul 21 23:06:36 (none) kernel: Not going to start Falcon (/tvbin/falcon isn't an existing executable)
Jul 21 23:06:39 (none) kernel: turbonet2: link = 100Mbps full-duplex
Jul 21 23:06:39 (none) kernel: Start fan control...
Jul 21 23:06:39 (none) kernel: route forgot to specify route netmask.
Jul 21 23:06:39 (none) kernel: Couldn't open /dev/tivoconfig
Jul 21 23:06:39 (none) kernel: Terminal temp: 75
Jul 21 23:06:39 (none) kernel: Critical temp: 70
Jul 21 23:06:39 (none) kernel: Logging temp: 65
Jul 21 23:06:39 (none) kernel: Target temp: 48
Jul 21 23:06:40 (none) kernel: Scanning for phase2 repair scripts
Jul 21 23:06:41 (none) kernel: Can not check for Test Master
Jul 21 23:06:42 (none) kernel: Checking for database conversions...
Jul 21 23:06:44 (none) kernel: Checking new software installation
Jul 21 23:06:44 (none) kernel: SwSystem 3.5-01-1-011 is already active, nothing to do.
Jul 21 23:06:44 (none) kernel: Scanning for phase3 repair scripts
Jul 21 23:06:44 (none) kernel: Starting Services.
Jul 21 23:06:44 (none) kernel: Scanning for phase4 repair scripts
Jul 21 23:06:45 (none) kernel: /etc/rc.d/rc.sysinit.author: /var/hack/tivoftpd.ppc: No such file or directory
Jul 21 23:06:45 (none) kernel: /etc/rc.d/rc.sysinit.author: /var/local/tivoweb-tcl/tivoweb#: No such file or directory
Jul 21 23:06:45 (none) kernel: rc.sysinit is complete
Jul 21 23:06:45 (none) kernel: MCP startup complete
Jul 21 23:06:49 (none) kernel: ApgLogFrequency( 0 sec )
Jul 21 23:06:49 (none) kernel: Finished creating ApgDriverFrameIter
Jul 21 23:06:49 (none) kernel: Using a smartSorter!
Jul 21 23:06:49 (none) kernel: Creating ApgReader
Jul 21 23:07:12 (none) kernel: oslink: 21270 jiffies since heartbeat
Jul 21 23:07:12 (none) kernel: oslink: 21270 jiffies since heartbeat
Jul 21 23:07:31 (none) kernel: Tmk Assertion Failure:
Jul 21 23:07:31 (none) kernel: Audit, line 31 ()
Jul 21 23:07:31 (none) kernel: Tmk Fatal Error: Thread myworld <153> died due to signal -2

[Narf54321]

You'll find that myworld, tivosh, huxley and many other tivo-specific "programs" are really all built into the main tivoapp file.

You should probably start by checking/replacing the /tvbin/tivoapp file and then moving outwards to check possible hardware causes, like maybe the cachecard RAM.

[ciper]

Going out on a limb - would it make sense to switch the boot partition so that it starts from the old OS to rule out any software problems?

[tivoking]

How do I change the boot partition?

[mikey]

SwSystem 3.5-01-1-011 is already active, nothing to do.
As you're at 3.5 I would not recommend flipping the bootpage. IIRC there ARE mfs Changes and that it would be a bad idea. Try an emergency reinstall (http://www.dealdatabase.com/forum/showpost.php?p=255309&postcount=5)
might also try fsfix.
When you get it running its a good idea to dd a stable hacked image to the inactive partition. After that flipping the bootpage is a safe and fast means of recovery.
Mikey

[newbie]

Do a search, I had a similar problem that was solved by doing a clear thumbs data and progam/guide data. I didn't have to delete my programs.

Someone posted a script (clear.tcl?) so you only need telenet access for the few seconds it takes to run the script.

http://www.dealdatabase.com/forum/showpost.php?p=186138&postcount=2

Make sure you don't run the option that deletes your programs.

[PortlandPaw]

Its a good idea to dd a stable hacked image to the inactive partition.
Mikey
What's the appropriate dd command to copy the active partition to the inactive partition? I think I know, but I'd hate to make a mistake and I can't find it in a search.

And can this operation be done from the bash prompt or must the drive be connected to a PC?

[ScanMan]

What's the appropriate dd command to copy the active partition to the inactive partition?First determine the active pair with "bootpage -p"
Let's assume root=/dev/hda4; the 3/4 pair are active. So then:

dd if=/dev/hda3 of=/dev/hda6
dd if=/dev/hda4 of=/dev/hda7

1st one does the kernel, 2nd does the root filesystem. To switch to the alternate, you would need to write new bootpage parameters; for example:

bootpage -P "root=/dev/hda7 upgradesoftware=false" /dev/hda

You would probably want to mirror whatever displayed from "bootpage -p"

Next flip your bootpage

bootpage -f /dev/hda

reboot

And can this operation be done from the bash prompt or must the drive be connected to a PC?Yes, it can be done from bash.

[mikey]

What's the appropriate dd command to copy the active partition to the inactive partition? I think I know, but I'd hate to make a mistake and I can't find it in a search.

And can this operation be done from the bash prompt or must the drive be connected to a PC?
From bash. Preferebly telnet. I rarely use serial, but I start it on line 10 of rc.sysinit. A consequnce of starting it so early is tcl scripts, per Bubbaj, crash the tivo, but it has saved me from pulling the drive on more than 1 ocassion.

From the bash prompt

df <enter>

/dev/hda4 126911 25196 95162 21% /

/dev/hda9 126911 60702 59656 50% /var

This tells us /dev/hda4 is the active partition. It could also be /dev/hda7

so

dd if=dev/hda4 of=dev/hda7 bs=1024

and find the boot page with



bootpage -q /dev/hda

yields root=/dev/hda4 runideturbo=false

change with

bootpage -P "root=/dev/hda7 runideturbo=false" /dev/hda


you probably should copy the kernel over too. Find it with bootpage -b /dev/hda
mine is 3 so I would use
dd if=dev/hda3 of=dev/hda6 bs=1
if you get 6 use
dd if=dev/hda6 of=dev/hda3 bs=1024


and finally on after mounting the new partition in a folder named /7

joe /7/etc/fstab

change /dev/hda4 to /dev/hda7.

As always have a backup handy.
You really should have a backup handy because an inadvertent paste and enter will in all probablity nuke, as in pull the drive and perform a restore from a backup, your tivo.
You've been warned.
You have now been warned twice.
Mikey.

Thanks to Bubbaj, Riley, and Alphwolf. I just collected this information. It is posted in bits and pieces here at DD.

[PortlandPaw]

You've done me a real service and I hope to many others here! Thank you for taking the time to document this rather simple backup system.

[ScanMan]

Don't you have to swap (flip) the bootpage to boot from /dev/hda6?

If you check it as indicated with "bootpage -b" I think you'll see it's still 3. And if you boot from 3 with "root=/dev/hda7", it's not gonna work...well, it might but not as intended.

[mikey]

Don't you have to swap (flip) the bootpage to boot from /dev/hda6?

If you check it as indicated with "bootpage -b" I think you'll see it's still 3. And if you boot from 3 with "root=/dev/hda7", it's not gonna work...well, it might but not as intended.
That sounds reasonable. I'll try it tonight when I get home.
I just pasted some notes I had from a year or so ago. I wrote/collected them after inadvertently nuking the wifes FULL 500gb tivo. :eek:

That led me think of how to QUICKLY recover without restoring or pulling the drive.

bootpage -f /dev/hda

haven't seen this one. does it filp from 3 to 6 and vise versa.

[ScanMan]

bootpage -f /dev/hdaDoes it flip from 3 to 6 and vise versa.Exactly; you could also do it in two steps:

bootpage -B 6 /dev/hda
bootpage -A 3 /dev/hdaHere (http://www.courtesan.com/tivo/bootpage.html) is a good page with bootpage options if you haven't seen it already.

[tivoking]

Can the the instruction from the last few post be done with the drive connected to the PC?.
I have my drive connected to the PC and I can view/edit any of the etc/rc.d script files so it would be nice if I can do it from the PC then drop the drive back in the DTivo.

[mikey]

@ ScanMan You are correct about it not changing the boot kernel. However, the tivo was recording when got back to it before I could test bootpage -f /dev/hda
I don't believe mine has any shows scheduled for tonight so I'll try it this evening.

[mikey]

Can the the instruction from the last few post be done with the drive connected to the PC?.
I have my drive connected to the PC and I can view/edit any of the etc/rc.d script files so it would be nice if I can do it from the PC then drop the drive back in the DTivo.
The dd commands for copying partitions can be adjusted to whichever drive for example /dev/hdx easily. bootpage can be to, but I'll have to do several searches before trying it.

[ScanMan]

Yes, the bootpage can be done from the PC but depending on what boot disk/cd you are using, you might want to use this (http://www.dealdatabase.com/forum/showthread.php?t=39244) version of bootpage - which is the most recent/reliable AFAIK.

[PortlandPaw]

ScanMan, a clarification please -- I take it that alldeadhomiez's bootpage is just for use on the PC and that the native TiVo bootpage is OK the way it is (no "off-by-one on kernel partitions," for example) and doesn't need to be replaced.

Correct?

[ScanMan]

I take it that alldeadhomiez's bootpage is just for use on the PC and that the native TiVo bootpage is OK the way it is (no "off-by-one on kernel partitions," for example) and doesn't need to be replaced. Correct?Yes, that is correct; ADH's bootpage is for x86 linux. There are no "off-by-one" problems with native bootpage binaries compiled for PPC (S1) and MIPS (S2).

[tivoking]

I found the old Dtivo drive and put it back in the SAT-t60.
I powered it up and it ran fine, I even got the tivo menus with a meassage stating it hasn't call home in 1396 days.
Now I know the Dtivo SAT-t60 is OK. I need to get a new image or fix the image on the present Dtivo drive ( the old drive I'll keep as back up).
I tried swaping the boot/kernel partitions, I also copied the the present partitons to their backup and change the boot partition ang got the same error. How do I force a tivo scan/fix on the active partition in the tivo? Is there a way on the PC to setup a scan so when I plug it back in the tivo it with redownload software and repair itself?

[PortlandPaw]

I don't know for sure, but it sounds like you have a minimum amount of hacking done to your unit. I think the easiest way to get back up and running is to use Steve Jenkins guide to make a backup of your good drive to your PC and then load that image onto your ailing drive(s).

Before doing this, run the drive manufacturer's diagnostics on the drive(s) to fix any bad sectors. If a lot are found, consider junking it. Using mfstools will wipe the drive(s) and put your fresh image on it.

Then you just have to load whatever hacks (tivoftp, telnet TivoWeb, etc) that you want. Of course, you'll lose any recordings you have on the old drive, but at this point that may be unavoidable unless you have a very large drive on your PC and can backup everything to that.

Take a look at the hackman ReadMe (see my sig) -- I put a section in there about how to set up a TiVo so that you'd (almost) always have ftp and bash access in the event of malfunctions.

Good luck!

p.s. Just to consolidate things and make it easier for others in the future, I put the dd information from this thread into a "how to" which I successfully tested and posted here (http://www.dealdatabase.com/forum/showpost.php?p=260537&postcount=53)

[tivoking]

You may be right but the image on the original drive is over 3.5 year that put the version at 2.0x. The "bad" drive is not realy bad, at least as far as the Linux OS, I think just the Tivoapp has a bad/corrupt file. Is there a way can I just force the it to re-download the latest image?

[PortlandPaw]

You can try this technique (http://69.28.82.116/pe/action/forums/displaypost?postID=10112421) to force a download. Then you could save that image to disk as a backup in addition to keeping the original drive as a further backup.

[tivoking]

I tried that link, Item 52 was the only one that did something.
It showed the splash screen with the Tivo logo and the fact it was updating the software. But after it rebooted it was still stuck in the reboot loop.
I did try the other option 56, 57 and 58 but nothing happen I think it reboot before these commans are launched. The only one that did somthing was 52.
There might be a hardware fault that the 3.5 software does like but the 2.0 does'nt care.
Can I copy the 2.0 from my backup drive onto the 3.5 drive?

[PortlandPaw]

You might try cleaning the parlex cable between the power supply and the motherboard. It looks (on mine) like a 2" piece of white tape and simply plugs into connectors on the two boards. Use a pencil eraser to clean it and then re-seat it, maybe in the reverse direction from where it was. I had a DTivo doing the same thing, and cleaning this cable fixed it. <fingers crossed>

[tivoking]

I cleaned both end of that parlax cable but samoething.
Is there a way to force a GSOD/fsfix so the Dtivo will to fix the image?
Mabe something I could put into the startup script via the PC or something I could type in on the shell promt before it reboots? I think I have 5 to 10 seconds of active shell access before the reboot occusrs.

[PortlandPaw]

I've been experimenting with swapping the active partitions and this is something you might try. Since I don't know what will happen it's risky. The following command will flip the bootpage and (maybe) boot the machine from the other set of partitions:
bootpage -f /dev/hda
I think I would try this only if I'm ready to give up and re-image the drive.

Before you do this, do "bootpage -p /dev/hda" to see what partition is active. That way you can check if it really flipped when you reboot.

[PortlandPaw]

In reviewing this whole thread, I think maybe this is the best route:
1. Put your current drive in your PC and copy off your hacks directory
2. Make a backup of your original drive to your PC
3. Re-image your current drive using that image
4. Plug in a phone line, fire it up, and let the TiVo mothership update it
5. Re-hack it, i.e. put your old hacks back in

Maybe as a last ditch effort, after doing the hack backup (step 1), try flipping the partitions as I described above.

[tivoking]

I took your suggestion, I made a new backup of the original tivo drive, re-imaged my current drive and the let tivo phone home. It wasn't as bad as I thought, it took it less the two hours for it to update from 2.5 to 3.0.
Then the next day it updated to the latest 3.5. Now it's back up and runing, I'll am going to wait a week for things to settle before I add the tivoweb+ hack.
Thanks

[JoshFink]

My DiretTivo was runing fine for weeks but
while I was watching a recorded show it just did a reboot and now it just cycles thru "almost there.." then reboot.
It will get past the Cache Card startup writing, reading and caching til the almost there screen then it just reboots.
I runs long enough for me to telnet in but not long enough to do anything else.
I had to remove the harddrive and install it to my pc.
From the PC I checked out the log files.

The only hacks I have on this DTivo is the Tivoweb+.

Can any one figure out what wrong?
Last part of tverr and kernel log file are below.

Thanks


FROM tverr

Jul 21 22:55:29 (none) TmkAssertionFailure[173]: (Audit, line 31 ())
Jul 21 22:55:29 (none) myworld[173]: Tmk Fatal Error: Thread myworld <173> died due to signal -2
Jul 21 22:55:29 (none) myworld[173]: Tmk Thread Backtrace: 1b3b12c 1b39a10 1d33804 1d22998 1d2286c 1949ba0 1a92180 1a91be0

194c65c 1cc21b0 190afe0 1c26108 1c25898 1c24dd8 1c24a3c 1c24958 1c24c24 1c24594 190778c 1dfda1c 1dfdadc 1dfdb90 1c1f73c 1d66d5c

1800134
Jul 21 22:55:29 (none) myworld[173]: Tmk Fatal Error: Thread died due to signal -2
Jul 21 22:55:29 (none) myworld[173]: Invoking rule 834: rebooting system
Jul 21 22:59:30 (none) TmkAssertionFailure[152]: (Audit, line 31 ())
Jul 21 22:59:30 (none) myworld[152]: Tmk Fatal Error: Thread myworld <152> died due to signal -2
Jul 21 22:59:30 (none) myworld[152]: Tmk Thread Backtrace: 1b3b12c 1b39a10 1d33804 1d22998 1d2286c 1949ba0 1a92180 1a91be0

194c65c 1cc21b0 190afe0 1c26108 1c25898 1c24dd8 1c24a3c 1c24958 1c24c24 1c24594 190778c 1dfda1c 1dfdadc 1dfdb90 1c1f73c 1d66d5c

1800134
Jul 21 22:59:30 (none) myworld[152]: Tmk Fatal Error: Thread died due to signal -2
Jul 21 22:59:30 (none) myworld[152]: Invoking rule 834: rebooting system
Jul 21 23:03:30 (none) TmkAssertionFailure[152]: (Audit, line 31 ())
Jul 21 23:03:30 (none) myworld[152]: Tmk Fatal Error: Thread myworld <152> died due to signal -2
Jul 21 23:03:30 (none) myworld[152]: Tmk Thread Backtrace: 1b3b12c 1b39a10 1d33804 1d22998 1d2286c 1949ba0 1a92180 1a91be0

194c65c 1cc21b0 190afe0 1c26108 1c25898 1c24dd8 1c24a3c 1c24958 1c24c24 1c24594 190778c 1dfda1c 1dfdadc 1dfdb90 1c1f73c 1d66d5c

1800134
Jul 21 23:03:30 (none) myworld[152]: Tmk Fatal Error: Thread died due to signal -2
Jul 21 23:03:30 (none) myworld[152]: Invoking rule 834: rebooting system
Jul 21 23:07:31 (none) TmkAssertionFailure[153]: (Audit, line 31 ())
Jul 21 23:07:31 (none) myworld[153]: Tmk Fatal Error: Thread myworld <153> died due to signal -2
Jul 21 23:07:31 (none) myworld[153]: Tmk Thread Backtrace: 1b3b12c 1b39a10 1d33804 1d22998 1d2286c 1949ba0 1a92180 1a91be0

194c65c 1cc21b0 190afe0 1c26108 1c25898 1c24dd8 1c24a3c 1c24958 1c24c24 1c24594 190778c 1dfda1c 1dfdadc 1dfdb90 1c1f73c 1d66d5c

1800134
Jul 21 23:07:31 (none) myworld[153]: Tmk Fatal Error: Thread died due to signal -2
Jul 21 23:07:31 (none) myworld[153]: Invoking rule 834: rebooting system
******************************************************************************

FROM kernel

Jul 21 23:06:35 (none) kernel: Time set to: Fri Jul 21 23:06:35 2006
Jul 21 23:06:35 (none) kernel: Have a nice day.
Jul 21 23:06:35 (none) kernel: Configuring network...
Jul 21 23:06:35 (none) kernel: turbonet2: driver version 20050218
Jul 21 23:06:35 (none) kernel: turbonet2: using MAC address 00:0B:AD:68:A4:BF
Jul 21 23:06:35 (none) kernel: turbonet2: driver successfully installed
Jul 21 23:06:35 (none) kernel: turbonet2: driver successfully installed
Jul 21 23:06:35 (none) kernel: Checking for additional disk...
Jul 21 23:06:35 (none) kernel: Starting EventSwitcher...
Jul 21 23:06:36 (none) kernel: Not going to start Test service with NULL executable
Jul 21 23:06:36 (none) kernel: Not going to start Epg Manager (/tvbin/EpgManager isn't an existing executable)
Jul 21 23:06:36 (none) kernel: Not going to start thttpd (/tvbin/thttpd isn't an existing executable)
Jul 21 23:06:36 (none) kernel: Not going to start DmComponent (/tvbin/DmComponent isn't an existing executable)
Jul 21 23:06:36 (none) kernel: Not going to start IdlComponent (/tvbin/idl-component isn't an existing executable)
Jul 21 23:06:36 (none) kernel: Not going to start Falcon (/tvbin/falcon isn't an existing executable)
Jul 21 23:06:39 (none) kernel: turbonet2: link = 100Mbps full-duplex
Jul 21 23:06:39 (none) kernel: Start fan control...
Jul 21 23:06:39 (none) kernel: route forgot to specify route netmask.
Jul 21 23:06:39 (none) kernel: Couldn't open /dev/tivoconfig
Jul 21 23:06:39 (none) kernel: Terminal temp: 75
Jul 21 23:06:39 (none) kernel: Critical temp: 70
Jul 21 23:06:39 (none) kernel: Logging temp: 65
Jul 21 23:06:39 (none) kernel: Target temp: 48
Jul 21 23:06:40 (none) kernel: Scanning for phase2 repair scripts
Jul 21 23:06:41 (none) kernel: Can not check for Test Master
Jul 21 23:06:42 (none) kernel: Checking for database conversions...
Jul 21 23:06:44 (none) kernel: Checking new software installation
Jul 21 23:06:44 (none) kernel: SwSystem 3.5-01-1-011 is already active, nothing to do.
Jul 21 23:06:44 (none) kernel: Scanning for phase3 repair scripts
Jul 21 23:06:44 (none) kernel: Starting Services.
Jul 21 23:06:44 (none) kernel: Scanning for phase4 repair scripts
Jul 21 23:06:45 (none) kernel: /etc/rc.d/rc.sysinit.author: /var/hack/tivoftpd.ppc: No such file or directory
Jul 21 23:06:45 (none) kernel: /etc/rc.d/rc.sysinit.author: /var/local/tivoweb-tcl/tivoweb#: No such file or directory
Jul 21 23:06:45 (none) kernel: rc.sysinit is complete
Jul 21 23:06:45 (none) kernel: MCP startup complete
Jul 21 23:06:49 (none) kernel: ApgLogFrequency( 0 sec )
Jul 21 23:06:49 (none) kernel: Finished creating ApgDriverFrameIter
Jul 21 23:06:49 (none) kernel: Using a smartSorter!
Jul 21 23:06:49 (none) kernel: Creating ApgReader
Jul 21 23:07:12 (none) kernel: oslink: 21270 jiffies since heartbeat
Jul 21 23:07:12 (none) kernel: oslink: 21270 jiffies since heartbeat
Jul 21 23:07:31 (none) kernel: Tmk Assertion Failure:
Jul 21 23:07:31 (none) kernel: Audit, line 31 ()
Jul 21 23:07:31 (none) kernel: Tmk Fatal Error: Thread myworld <153> died due to signal -2

All of a sudden I'm getting this EXACT same thing on my T60

[mikey]

clear and delete your season passes. mine did the same thing a week or two ago.
from your logs var has been rebuilt so you mighy consider editing your startup file to exclude your hacks that were on var.
you would probably want to run "e2fsck -y /dev/hda9" until it comes back as clean.
mikey

[JoshFink]

Thanks..

How do I delete the season passes from the PC? I can't boot into the machine the tivo at all without it rebooting.

I already edited the startup file and all my hacks are commented out.

Thanks

Josh

[mikey]

IIRC search portlandpaw and clear and delete. I'm fairly sure its been posted in the last few months. if you don't find it and your are going to reimage anyway
mfsassert -please
or you can always try
http://alt.org/wiki/index.php/TivoDiagnostics
the kickstart remote codes.
mikey

[newbie]

Thanks..

How do I delete the season passes from the PC? I can't boot into the machine the tivo at all without it rebooting.

I already edited the startup file and all my hacks are commented out.

Thanks

Josh

I posted a link to a clear script. I'm not sure if you can run it in a PC but I had enough time to run it before my unit rebooted.