PDA

View Full Version : Transfers Wont Complete



StevieC
31-07-2007, 08:27 AM
Hey Guys at my wits end here , I cant get any Recorded programs to finish transferring to my PC , Ive tried Ty Tools , Ty Server , TWP , changed my NIC to Failsafe , they start to transfer over fine , but get to a certain point and stop responding ,which stops access to the Tivo on the network , and I have to reboot to get access again , any Suggestions ?? , Its a Phillips Series one , with 250gb HDD thanks

Wibble
31-07-2007, 06:29 PM
Hey Guys at my wits end here , I cant get any Recorded programs to finish transferring to my PC , Ive tried Ty Tools , Ty Server , TWP , changed my NIC to Failsafe , they start to transfer over fine , but get to a certain point and stop responding ,which stops access to the Tivo on the network , and I have to reboot to get access again , any Suggestions ?? , Its a Phillips Series one , with 250gb HDD thanks

Check that there are not disk error in the logs.

Try putting the Tivo in standby so it's not recording (Green led off)

If using mfs_ftp make sure you are using a really dumb ftp client with only 1 allowed connection at a time.
Having 2 connections to the mfs_ftp server usually kills it.

StevieC
01-08-2007, 07:39 PM
Doesnt appear to be any Disk errors in the logs , also tried in stand by mode , still locks up , ive even tried mfs_ftp now , same problem it starts to Download ,but then the network access to the Tivo locks up , and i have to reboot , everything else still works fine , just no network access its driving me nuts :mad::mad::(

Wibble
01-08-2007, 07:53 PM
Doesnt appear to be any Disk errors in the logs , also tried in stand by mode , still locks up , ive even tried mfs_ftp now , same problem it starts to Download ,but then the network access to the Tivo locks up , and i have to reboot , everything else still works fine , just no network access its driving me nuts :mad::mad::(

It could be your network card/cabling is faulty. If you do an ifconfig is the count for errors,dropped,overruns etc all 0's for eth0?
Mine looks like this:
[TiVo [p0] ~]# ifconfig
lo Link encap:Local Loopback
inet addr:127.0.0.1 Bcast:127.255.255.255 Mask:255.0.0.0
UP BROADCAST LOOPBACK RUNNING MTU:3584 Metric:1
RX packets:7552 errors:0 dropped:0 overruns:0 frame:0
TX packets:7552 errors:0 dropped:0 overruns:0 carrier:0 coll:0

eth0 Link encap:Ethernet HWaddr 00:0B:AD:10:10:10
inet addr:192.168.0.40 Bcast:192.168.12.255 Mask:255.255.255.0
UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1
RX packets:3944562 errors:0 dropped:0 overruns:0 frame:0
TX packets:6470827 errors:0 dropped:0 overruns:0 carrier:0 coll:0
Interrupt:29

You could try this test:

ping -c 5000 -f -s 1500 192.168.0.1

where 192.168.0.1 is your PC or router.
This does a flood ping (ie ping as fast as it can)
With 1500 byte packets
And 5000 Packets.

It that kills it I would say it's an issue with the actual tivo network, not any apps.

StevieC
01-08-2007, 10:54 PM
thanks wibble this is what i get , my Rx Tx Packets are a lot lower than yours is that an issue ??

TiVo [p0] ~]# ifconfig
lo Link encap:Local Loopback
inet addr:127.0.0.1 Bcast:127.255.255.255 Mask:255.0.0.0
UP BROADCAST LOOPBACK RUNNING MTU:3584 Metric:1
RX packets:0 errors:0 dropped:0 overruns:0 frame:0
TX packets:0 errors:0 dropped:0 overruns:0 carrier:0 coll:0

eth0 Link encap:Ethernet HWaddr 00:0B:AD:29:60:52
inet addr:192.168.1.2 Bcast:192.168.1.255 Mask:255.255.255.0
UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1
RX packets:386 errors:0 dropped:0 overruns:0 frame:0
TX packets:93 errors:0 dropped:0 overruns:0 carrier:0 coll:0
Interrupt:29

Wibble
02-08-2007, 08:10 PM
thanks wibble this is what i get , my Rx Tx Packets are a lot lower than yours is that an issue ??


No, it just means mine has been running for a while.:)
All the other values are 0 which is good.

You might want to try the ifconfig after the ping and see if any error crop up.

The only other thing I can think of is to connect the serial cable and when the networking misbehaves to have a look at what ifconfig says and what's in the logs.