Problems in trying to restore tivoapp

[SithLord]

I'm trying to restore my original 6.3 tivoapp--it's stuck at the "almost there" screen after I attempted to patch the 30-second skip feature--but when I try the tivoapp restore, I get an error message telling me "the device is out of space."

I'm trying to fix this without having to pull the drive, since this is my father's HR10-250, and he has a LOT of unwatched recordings on it. Any suggestions?

[SithLord]

FWIW, here is what I get when I reboot...



Lo : 00000ae0
epc : 80123034 Tainted: P
Status: 90019403
Cause : 0000000c
8001e9fc 8001eac0 80022bb4 80022e8c 80024f3c 80123034 8006cba4 8006d91c
800584e8 80058744 80020908 80020f64 020d8a4c
020d8a4c (Bad trace)
/etc/rc.d/rc.sysinit: line -37: 111 Bus error /tvbin/TvLauncher
-StartProgram 0 mfsd
Scanning for phase2 repair scripts
Running boot Stage E_PreApplication scripts
Checking for database conversions
do_page_fault #3: sending signal 10 to convert-db(131)
$0 : 00000000 90019400 100d3ffc 100d3ffc 100d1d84 00000000 000002bc 000002bc
$8 : 0000003c 100d1fc4 100d1d44 7fff7fea 7fff7d28 0001ffff ffffffff 0001ffff
$16: 00000001 829d8f60 874919a0 00000000 10000000 00006012 87151f30 87151dc0
$24: ffffffff 00000080 87150000 87151c40 00000008 8006cba4
Hi : 00000000
Lo : 00000c00
epc : 80123034 Tainted: P
Status: 90019403
Cause : 0000000c
8001e9fc 8001eac0 80022bb4 80022e8c 80024f3c 80123034 8006cba4 8006d91c
800584e8 80058744 80020908 80020f64 020d8a4c
020d8a4c (Bad trace)
/etc/rc.d/rc.sysinit: line 4: 131 Bus error /tvbin/convert-db
No upgrade to load
Not upgrading software
Scanning for phase3 repair scripts
Running boot Stage F_ApplicationLaunch scripts
Starting Services.
do_page_fault #3: sending signal 10 to TvLauncher(134)
$0 : 00000000 90019400 100d3ffc 100d3ffc 100d1d84 00000000 000002bc 000002bc
$8 : 0000003c 100d1fc4 100d1d44 7fff7fea 7fff7d1c 0001ffff ffffffff 0001ffff
$16: 00000001 829d8d60 87491ca0 00000000 10000000 00006012 87151f30 87151dc0
$24: ffffffff 00000080 87150000 87151c40 00000008 8006cba4
Hi : 00000000
Lo : 00000d20
epc : 80123034 Tainted: P
Status: 90019403
Cause : 0000000c
8001e9fc 8001eac0 80022bb4 80022e8c 80024f3c 80123034 8006cba4 8006d91c
800584e8 80058744 80020908 80020f64 020d8a4c
020d8a4c (Bad trace)
/etc/rc.d/rc.sysinit: line -14: 134 Bus error TvLauncher -StartA
tBoot
Scanning for phase4 repair scripts
Running boot Stage G_PostApplication scripts
starting rc.sysinit.author
set environmental variables
starting telnet and ftp
starting serial bash
running fakecall
do_page_fault #3: sending signal 10 to fakecall.tcl(141)
$0 : 00000000 90019400 100d3ffc 100d3ffc 100d1d84 00000000 000002bc 000002bc
$8 : 0000003c 100d1fc4 100d1d44 7fff7fe6 7fff7cdc 0001ffff ffffffff 0001ffff
$16: 00000001 829d8e60 87479840 00000000 10000000 00006012 870b5f30 870b5dc0
$24: ffffffff 00000080 870b4000 870b5b58 00000008 8006cba4
Hi : 00000000
Lo : 00000cc0
epc : 80123034 Tainted: P
Status: 90019403
Cause : 0000000c
8001e9fc 8001eac0 80022bb4 80022e8c 80024f3c 80123034 8006cba4 8006d91c
800584e8 8006cab0 800584e8 80058744 80020908 80020f64 020d8a4c
020d8a4c (Bad trace)
/etc/rc.d/rc.sysinit.author: line 18: 141 Bus error fakecall.tcl





bash: no job control in this shell
bash-2.02#


EXT2-fs warning: mounting unchecked fs, running e2fsck is recommended
/etc/rc.d/rc.sysinit.author: cd: /var/hack/sbin: No such file or directory
/etc/rc.d/rc.sysinit.author: ./ncidd: No such file or directory
/etc/rc.d/rc.sysinit.author: cd: /var/hack/bin: No such file or directory
/etc/rc.d/rc.sysinit.author: ./tivocid: No such file or directory
do_page_fault #3: sending signal 10 to tivosh(150)
$0 : 00000000 90019400 100d3ffc 100d3ffc 100d1d84 00000000 000002bc 000002bc
$8 : 0000003c 100d1fc4 100d1d44 7fff7fee 7fff7cdc 0001ffff ffffffff 0001ffff
$16: 00000001 829d8d60 87479d40 00000000 10000000 00006012 87029f30 87029dc0
$24: ffffffff 00000080 87028000 87029c40 00000008 8006cba4
Hi : 00000000
Lo : 00000660
epc : 80123034 Tainted: P
Status: 90019403
Cause : 0000000c
8001e9fc 8001eac0 80022bb4 80022e8c 80024f3c 80123034 8006cba4 8006d91c
800584e8 80058744 80020908 80020f64 020d8a4c
020d8a4c (Bad trace)
/etc/rc.d/rc.sysinit.author: /enhancements/TWPrun.sh: No such file or directory
/etc/rc.d/rc.sysinit.author: line 53: 150 Bus error tivosh /enha
ncements/endpadplus.tcl 1 2 -seq -auto >>/dev/null
crond: /var/spool/cron/crontabs: No such file or directory
rc.sysinit is complete

[captain_video]

Since you obviously hacked your Tivo with the Zipper script I would recommend posting your question to either Gunnyman or rbautch over at the Tivo Community Forum. They have expressly stated that anyone using said script not come here looking for support, let alone even mention it here.

As for the tivoapp file, check and see how many copies of the file you have in the /tvbin directory. Your script may have made a backup of the original file, although this is unlikely since it doesn't support 6.3/6.3a, and you may have created additional backups when manually patching the file. The tivoapp file is pretty big and too many copies will use up whatever available space you have and not allow you to restore the original tivoapp file. You'll probably have to place the drive in your PC, delete the extraneous tivoapp files, and rename the original file.

[SithLord]

Ah, dummy me forgot about the Zipper allusions. My bad. :o

Got it back up and running. Thanks to cheer for a simple reminder! :p

[rfc]

Got it back up and running. Thanks to cheer for a simple reminder! :p

What was the reminder? Were you ever successful modifying Tivoapp?

[ScanMan]

Some general comments on my experience. The preferred method in patching tivoapp (as I have read it here) is:
mount -o remount,rw /
cd /tvbin
mv tivoapp tivoapp.orig
cp tivoapp.orig tivoapp
<apply patches to tivoapp>
mount -o remount,ro /
reboot

I have done similarly when restoring a tivoapp:
mount -o remount,rw /
cd /tvbin
mv tivoapp tivoapp.old
cp tivoapp.new tivoapp
mount -o remount,ro /
reboot
You should do it exactly like that....DO NOT try to delete "tivoapp.old" at this time since processes still may have that file locked and it will hang. Then you won't be able to mount "read-only" which is important before rebooting. If you don't, you'll have the situation described by SithLord above where your root partition appears full (>80%) but there are no extra tivoapp's laying around. Perplexing? Not really, you've got a bunch of lost inodes and should run e2fsck as follows:
e2fsck -y /dev/hdaXWhere 'X' is the correct root partition (either 4 or 7). And you should do this with the partition mounted READ ONLY. That should free up your space...did for me, been there, done that!:cool:

[rfc]

Given that doing this via telnet or the serial port may have the file in use, wouldn't it eliminate this problem all together to make the changes with the drive in a PC?

[ScanMan]

Given that doing this via telnet or the serial port may have the file in use, wouldn't it eliminate this problem all together to make the changes with the drive in a PC?Yes, doing this in the PC would eliminate the "locking" issues. It's just a PITA to pull drives. As long as I leave the tivoapp "copy" that I 'mv' alone until after reboot, I've had no problems. You just have to wait until after the reboot to safely delete it; at least that's been my experience...