PDA

View Full Version : S1 to S2 MFS-FTP Transfer Question...



DocTauri
10-14-2004, 09:50 AM
I have some movies that I recorded on my old T60, encryption off, that I mfs-ftp'd off to a server. I now have S2's and went to push the movie back. The transfer was fine, but when I went to play the movie, I get the bong sound, then the "no video signal" error. I previously was able to successfully push this movie to another S1 a year ago or so. Should this be working (S1 to S2 tranfer), and if so, is my recording salvagable or is it gone?

Thanks,
Doc

rc3105
10-16-2004, 05:53 AM
use cso_scout to clear the CommercialSkipOffset keys (after it's finished inserting) and bcc's util (http://www.dealdatabase.com/forum/showpost.php?p=170686&postcount=26) to fix the s1 -> s2 audio format problem

DocTauri
10-16-2004, 10:05 PM
Thanks for the pointer, it worked like a charm!

Doc

DocTauri
10-17-2004, 12:14 PM
Well, I guess I spoke too soon. In the process of reinserting, mfs_ftp threw an error (sorry, didn't capture it), I can recreate it later if need be, but it wasn't an error message, it was illegal operation. When that happened, it left a hanging mfs_stdinsert process open, so I had two of the shows in my Now Playing list. This actually happened twice, so I had three of them in the list, two with the recording icon.

I couldn't delete this from the Now Playing list, so tried from mfs_ftp, but after issuing the del command, the connection terminated. So, I rebooted the box and both items were gone. Figuring everything was OK, I moved on, and tried to HMO transfer a movie from another Tivo. The one I was having issues with then rebooted itself, and has been in a constant reboot cycle ever since. Powering UP -> Almost there -> the DirecTV screen -> Restart.

I've tried doing the emergency 57 and 58 mfs checks from the remote at boot, no luck. I pulled the drive from the unit, mounted in my pc and disabled rc.sysinit.author, no luck. I'm assuming this is an MFS thing, but I'm not as knowledgable with MFS as I'd like to be.

Does anyone have any suggestions (other than reimage ;))

Thanks,
Doc

rc3105
10-17-2004, 08:48 PM
rename rc.sysinit & create a basic one that just boots telnet & bash. then try

/tvbin/mfsassert -please
/tvbin/reboot

and

/tvbin/fsfix -splash -uncollide -rehash -salvage -reboot

DocTauri
10-18-2004, 12:07 AM
Thanks for the pointers, unfortunately, neither worked.

I first set my rc.sysinit.author for just telnet and bash, then a sleep 86400, so I could go interactive. No joy, still reboots on me. Next, I pulled the sleep and put in the mfsassert and reboot, the commands executed, but still no luck. Finally, I removed them and put in the fsfix. This too executed (I know because I have a date command before and after the command writing to a log file), again, no luck. Still the continual reboot.

Any idea what this could be?

Thanks,
Doc

rc3105
10-18-2004, 12:19 AM
I first set my rc.sysinit.author...
???


rename rc.sysinit...

;)

DocTauri
10-18-2004, 07:36 AM
Sorry, I thought you meant rc.sysinit.author, as ethernet apparently gets init'd in rc.sysinit (so telnet doesn't work if rc.sysinit is blown away and only contains bash and telnet). Or am I missing something?

So, I renamed rc.sysinit to rc.sysinit.original. In my rc.sysinit, I just launched bash and telnet, didn't work. Removed those lines, and did the mfsassert and reboot from above, waited for the Powering up screen to go away as system rebooted, put rc.sysinit.original back, didn't fix it. Replaced rc.sysinit with the single line fsfix from above, but that never appeared to work (splash screen didn't come up and never rebooted).

I don't know if this is important or not, but when it restarts itself, it's always at 26% on the DirecTV screen.

Thanks again,
Doc

rc3105
10-18-2004, 08:38 AM
ah, yah, that's kinda important

boot to serial bash without loading tivoapp & all


#!/bin/bash
# bare bones rc.sysinit
export PATH=.:./:/bin:/sbin:/tivobin:/tvbin:/etc/rc.d
export TERM=xterm
export PS1='\h:\w$ '

/bin/bash</dev/ttyS2&>/dev/ttyS2&

then try fsfix, mfsassert, etc

DocTauri
10-18-2004, 06:07 PM
Duh. Of course. Sorry to be dense.

Ok, mfsassert gave me this:

(dev):/tvbin$ mfsassert -please
TmkLogger: <134>Jan 2 00:02:15 AttachSharedMemoryFile[10]: Can't open key file
/var/tmp//Performance.mpkey for attach, errno 2

TmkLogger: <132>Jan 2 00:02:15 EvtMaster[10]: No EventSwitcher is active
TmkLogger: <131>Jan 2 00:02:15 TmkInit[10]: InitializeProgramOrDie failed: 0x190001

InitializeProgramOrDie failed: 0x190001

So I tried fsfix, which gave me:



(dev):/tvbin$ /tvbin/fsfix -splash -uncollide -rehash -salvage -reboot
Could not find supported OSD hardware
TmkLogger: <134>Jan 2 00:05:14 AttachSharedMemoryFile[11]: Can't open key file
/var/tmp//Performance.mpkey for attach, errno 2

TmkLogger: <132>Jan 2 00:05:14 CreateSharedMemoryFile[11]: Can't create key fil
e /var/tmp//fsmem.mpkey, error 2

Couldn't CreateSharedMemoryFile() /var/tmp//fsmem.mpkey -- check permissions
TmkLogger: <131>Jan 2 00:05:14 FsInit[11]: Unable to create new MFS heap fsmem
TmkLogger: <131>Jan 2 00:05:14 TmkInit[11]: InitializeProgramOrDie failed: 0x11
001

InitializeProgramOrDie failed: 0x11001

So I realized that hda9 wasn't mounted. I couldn't get / to remount as rw, so I did a mount -n /dev/hda9 /var and tried again, this time I got:



(dev):/var/tmp$ /tvbin/mfsassert -please
TmkLogger: <134>Jan 2 00:10:19 AttachSharedMemoryFile[26]: no segment for /var/
tmp//Performance.mpkey found, errno 2

TmkLogger: <132>Jan 2 00:10:19 EvtMaster[26]: No EventSwitcher is active
TmkLogger: <131>Jan 2 00:10:19 TmkInit[26]: InitializeProgramOrDie failed: 0x19
0001

InitializeProgramOrDie failed: 0x190001

and



(dev):/var/tmp$ /tvbin/fsfix -splash -uncollide -rehash -salvage -reboot
Could not find supported OSD hardware
TmkLogger: <134>Jan 2 00:10:54 AttachSharedMemoryFile[29]: no segment for /var/
tmp//Performance.mpkey found, errno 2

Tmk Assertion Failure: FsAllocateFunction, line 131 ()
TmkLogger: <129>Jan 2 00:10:54 TmkAssertionFailure[29]: (FsAllocateFunction, line 131 ())
TmkLogger: <129>Jan 2 00:10:54 fsfix[29]: Tmk Fatal Error: Thread fsfix <29> died due to signal -2
Tmk Fatal Error: Thread fsfix <29> died due to signal -2 f9c51c 100df1c 100e18c 100e1dc f56b28 400d18 108a0b0
TmkLogger: <129>Jan 2 00:10:55 fsfix[29]: Tmk Thread Backtrace: f9c51c 100df1c 100e18c 100e1dc f56b28 400d18 108a0b0
TmkLogger: <129>Jan 2 00:10:55 fsfix[29]: Tmk Fatal Error: Thread died due to signal -2
TmkLogger: <129>Jan 2 00:10:55 fsfix[29]: Invoking rule 834: rebooting system
TmkLogger: Restarting system.

Again, thanks for the help...
Doc

rc3105
10-18-2004, 10:46 PM
ah crum, been a while since I used those. probably need to initialize a few things like swapon & switcherstart before the mfs repair utils run properly

read through the original rc.sysinit for load order & syntax, then either run from bash or add 'em to the barebones rc.sysinit


you could try unhooking the sat inputs & running them from a normal telnet session, everything should be init'd properly

DocTauri
10-19-2004, 07:11 AM
I still haven't been successful getting mfsassert or fsfix to run, but I put the original rc.sysinit back and found that this is what's causing the reboot each time (extra lines added for reference w/in boot cycle, not the typos weren't there, gotta thank HyperTerm for that):

AddInputSection 1ectory: Hash tabl
AddInputSection 2ablished 4096 bin
TvMomMediaSwitchSource::DoSetup()ap partitionsbra module was s
NET
DTuneOpen calledAdding Swap: 130
DDLOpen called (priority -1)
DDLInitRead calledn module registe
/
TvMomMediaSwitchSource::DoSetup()em) readonl
DDLInitRead called
DDLRelease called
DDLOpen called
DDLInitRead called
bcmMpegVideoOpenPid()
Pvr - Adding Network Recording Proxy - Input Section
Helper Thread 200 (for 198) waking up
AddInputSection 3
Helper Thread 205 (for 199) waking up
oslink: 01 01 00 Access Card: Inserted Tuner[0]: Locked Tuner[1]:
Not Locked
ApgManager Transition from state INIT to ACQUIRE_MARKER
ProcessRemoteFilterChanged db=0 cur=0
ProcessRemoteFilterChanged db=0 cur=0
iptables: No chain/target/match by that name
Tmk Assertion Failure: setup, line 2768 ()
Tmk Fatal Error: Thread TvNvDataClient <212> died due to signal -2
bee248 be2524 b70418 b967a0 b6fef8 b8d874 b8d638 b4aec0 9f9848 b78330 b78ff8 b78
07c b79514 b76668 b7674c 1009d3c 10119dc 1011b34 b73528 b733d0 102aff4 1058814 S
canning for phase4 repair scripts
rc.sysinit is complete
Restarting system.

Thanks,
Doc

rc3105
10-19-2004, 08:10 AM
that's not a monte issue, stuck at 26-28% is a common problem even for unmodified units running the correct sw

unplug the sat cables & see if it'll at least boot, if so try fsfix from bash or telnet

search & do some reading in the the 2x% percent issue threads. incorrect sat config can cause that. sometimes just booting once w/o cables attached will fix the problem. if not, try running guided setup & the various fixes you'll come across

DocTauri
10-19-2004, 09:51 AM
Nope, w/o sat feeds produces the same errors as above. I'm surprised you even got that message, I realized it probably wasn't a monte issue, then edited the message about 10 min. later! In the edit above, I'm getting this via console w/an unmodified rc.sysinit (and no rc.sysinit.author) right before the reboot:

Tmk Assertion Failure: setup, line 2768 ()
Tmk Fatal Error: Thread TvNvDataClient <212> died due to signal -2
bee248 be2524 b70418 b967a0 b6fef8 b8d874 b8d638 b4aec0 9f9848 b78330 b78ff8 b7807c b79514 b76668 b7674c 1009d3c 10119dc 1011b34 b73528 b733d0 102aff4 1058814
Scanning for phase4 repair scripts
rc.sysinit is complete
Restarting system.