Daily call failing since moving ISP's to Optus

[eden]

Hi guys I recently just moved to Optus internet on Friday and have been having problems that were described earlier in this thread. I have 2 Tivo's and both I could telnet but only one I could gain access via tivoweb. All my daily calls were failing.

I have tried to follow your steps by changing the /etc/oztivo.conf and /etc/tclient.conf files however it does not seem to have fixed the problem.

Before when I did a Daily call it would say "Failed. Service unavailable" but now it says "Failed. No dial-in number chosen."

I did notice that in one of the steps I was asked to change something that didn't exist.

use an editor and edit /etc/tclient.conf: find and change the line starting with #127::65.49.60.197:80::: and change it to 127::65.49.60.197:9090::: then change the line with 127::127.0.0.1:8000::: to #127::127.0.0.1:8000:::


The bolded sequence of numbers is not in my /etc/tclient.conf file.
Below is what I have.


#
# This is the default port, it's values come from Addr.itcl not here
#
000:
# Dennis' Emulator
126::66.23.218.193:80:::
# This is for the server emulator on minnie. Trouble if your ISP blocks HTTP .9
#127::131.244.9.101:80:::

# This uses emuProxy2 to avoid problems with transparent proxy. Thanks Tim!
#127::127.0.0.1:8000:::



Does any of this make sense?

[eden]

Now my both tivo's are saying "Failed. No Dial-in number chosen."

[petestrash]

Eden,

Are your trying to fix a proxy issue, or the current DNS issue that has only been a problem since Friday?

At the moment your TiVo is not set to call anywhere which is why it is failing.

Just add the following 2 lines to the bottom of your /etc/tclient.conf file, then reboot and try again.


# Connect Via the www.oztivo.net emulator
127::65.49.60.197:9090:::

Peter.

[eden]

I tried those 2 lines however it still says "Failed. No dial-in number chosen."

[petestrash]

Are your trying to fix a proxy issue, or the current DNS issue that has only been a problem since Friday?

Can you show what is in your tclient.conf now, and any other file you have edited.

Peter.

[eden]

Here is my /etc/tclient.conf file

# Copyright (c) 2001 TiVo Inc.
#
# This file contains entries for each of the possible service
# instances supported. The fields are all ":": (colon) separated
# and are as follows with the folling meanings:
#
# label:phone_number:svr_addr:svr_port:ppp_user:ppp_ pass:radius_domain
#
# label This is a 3 character numeric field which must
# unique identify this entry (the /Setup field XXX
# will point to this). Note the value 911 is reserved
# to imply the Addr.itcl *_EMG_* fields. (i.e.
# emergency repair port). Note the value 000 is
# reserved to imply the Addr.itcl *_DEF_* fields
# (i.e. the default port).
# phone_number This is the full phone number to dial, minus any
# prefixes defined by the phone options screen
# svr_addr This is the Ip Address of the service to connect to
# svr_port This is the TCP port number of the service to
# connect to
# ppp_user This is the username to connect to the ppp modem
# ppp_pass This is the password to connect to the ppp modem
# radius_domain This is the radius domain to put after the generated username.
# If ppp_user is set then this will have no effect.

#
# This is the default port, it's values come from Addr.itcl not here
#
000:
# Dennis' Emulator
126::66.23.218.193:80:::
# This is for the server emulator on minnie. Trouble if your ISP blocks HTTP .9
#127::131.244.9.101:80:::

# This uses emuProxy2 to avoid problems with transparent proxy. Thanks Tim!
#127::127.0.0.1:8000:::
# Connect Via the www.oztivo.net emulator
127::65.49.60.197:9090:::




And below is the /etc/oztivo.conf from 1 tivo

OzTiVo menu configuration settings file
# Please do not edit this file
# Put the TiVo disk back in your PC to reconfigure
nic=TurboNet
ip=192.168.0.5
mac=00:0B:AD:10:10:10
hostname=
modem=0
pppondss=0
netmask=255.255.255.0
gateway=192.168.0.1
ssid=
wep=
wepkey=



and the /etc/oztivo.conf from my other tivo

# OzTiVo menu configuration settings file
# Please do not edit this file
# Run the nic_config_tivo tool to reconfigure
nic=TurboNet
ip=192.168.0.197
mac=00:0B:AD:84:19:38
timing=16
hostname=oztivo
emulator=65.49.60.197
emulatorport=9090
netmask=255.255.255.0
gateway=192.168.0.1
ssid=
wep=
wepkey=

[petestrash]

Eden, is your tclient.conf the same on both TiVo's?

From what you have shown the 2nd TiVo should work, but the first will not due to missing lines in oztivo.conf.

What version of software are both TiVo's running?

And I'll ask this question for the third time; Were you trying to fix a proxy issue, or the current DNS issue that has only been a problem since Friday?

Peter.

[eden]

Sorry, I was trying to fix what i think is a proxy issue. All of this started when I changed from telstra to optus, I could no longer make daily calls.

Tivo A is running with version 1.6 and it has the tclient.conf file i listed before and the oztivo.conf file that you said should be working properly

Tivo B is running with version 1.3 or 1.4 and it has the oztivo.conf file that is missing data and the the tclient.conf file I thought was similar but rechecked it and there is a small difference below.

Thanks



#
# This is the default port, it's values come from Addr.itcl not here
#
000:
# Dennis' Emulator
126::66.23.218.193:80:::
# This is for the server emulator on minnie. Trouble if your ISP blocks HTTP .9
#127::65.49.60.197:9090:::

# This uses emuProxy2 to avoid problems with transparent proxy. Thanks Tim!
#127::127.0.0.1:8000:::
# Connect Via the www.oztivo.net emulator
127::65.49.60.197:9090:::

[petestrash]

Your issues are not related to the problems that were discussed in the original thread, so I have stripped our posts and moved them to a new thread.

Since the 2nd TiVo is running 1.4 or earlier, the missing lines are ok as they are not used in that version.

It would be easier to work out the issues on one at a time.

Pick which the most important one and run these (http://www.oztivo.net/twiki/bin/view/Network/NetworkingHowto#Configuration_and_Diagnostics) tests to see how much connectivity it has and post the results here and tell us which TiVo it is from.

Peter.

[eden]

Below are the results of the tests for the Tivo with the version 1.5, I thought it was 1.4 cause that is what it says on the start up screen but when i double checked when telneting i found it to be 1.5-20051128.

[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:10:10:10
inet addr:192.168.0.5 Bcast:192.168.0.255 Mask:255.255.255.0
UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1
RX packets:10011 errors:0 dropped:0 overruns:0 frame:0
TX packets:539 errors:0 dropped:0 overruns:0 carrier:0 coll:0
Interrupt:29


[TiVo [p0] ~]# route
route_info, afname=inet, options=33
Kernel IP routing table
Destination Gateway Genmask Flags Metric Ref Use Iface
192.168.0.0 * 255.255.255.0 U 32767 0 0 eth0
default 192.168.0.1 0.0.0.0 UG 0 0 0 eth0



[TiVo [p0] ~]# ping -c 5 192.168.0.5
PING 192.168.0.5 (192.168.0.5): 56 data bytes
64 bytes from 192.168.0.5: icmp_seq=0 ttl=255 time=2.2 ms
64 bytes from 192.168.0.5: icmp_seq=1 ttl=255 time=0.7 ms
64 bytes from 192.168.0.5: icmp_seq=2 ttl=255 time=0.7 ms
64 bytes from 192.168.0.5: icmp_seq=3 ttl=255 time=0.8 ms
64 bytes from 192.168.0.5: icmp_seq=4 ttl=255 time=0.7 ms

--- 192.168.0.5 ping statistics ---
5 packets transmitted, 5 packets received, 0% packet loss
round-trip min/avg/max = 0.7/1.0/2.2 ms



[TiVo [p0] ~]# ping -c 5 65.49.60.197
PING 65.49.60.197 (65.49.60.197): 56 data bytes

--- 65.49.60.197 ping statistics ---
5 packets transmitted, 0 packets received, 100% packet loss



[TiVo [p0] ~]# wget http://65.49.60.197/index.html
--00:21:11-- http://65.49.60.197/index.html
=> `index.html'
Connecting to 65.49.60.197:80... failed: Connection timed out.
Retrying.

--00:24:20-- http://65.49.60.197/index.html
(try: 2) => `index.html'
Connecting to 65.49.60.197:80... failed: Connection timed out.
Retrying.

--00:27:29-- http://65.49.60.197/index.html
(try: 3) => `index.html'
Connecting to 65.49.60.197:80... failed: Connection timed out.
Retrying.


[TiVo [p0] ~]# dbget /State/PhoneConfig DialPrefix
,#401

[petestrash]

Ok, so it's not an ISP proxy issue. Your TiVo cannot connect to the Internet.

This is probably an issue in your router or firewall.

Peter.

[eden]

That's what I was afraid of. Which doesn't seem to make sense because I am accessing the internet though my wireless apple airport extreme and I can both telnet and tivoweb my tivo's through the same router.

Could the problem be the new optus modem which is the only new piece of hardware? How would I check? Should I call optus?

[petestrash]

Yes anything internal seems to work, but not external.

Did your routers address change when you got the new modem? maybe your gateway IP needs to be changed.

Peter.

[eden]

I pretty sure all of the IP addresses are right but i did have trouble at first because some were in the format 10.0.x.x or 10.1.x.x or 192.168.x.x.

I think I'm going to reinstall the modems and routers again and see how that goes.

Thanks for the help

[petestrash]

Are you using DHCP for your TiVo, or did you set a fixed IP address?

Peter.

[eden]

They both have fixed IP addresses

[petestrash]

Ok, then your gateway address may need to be changed in oztivo.conf as it sounds like it may have changed with your new router.

You need to change:
gateway=192.168.0.1

To whatever your new routers IP is. Or just change your routers IP to 192.168.0.1.

Peter.

[eden]

The gateway IP address is correct, so to is the IP subnet mask.

I did notice that when I just went in to my router's webpage in the LAN IP setup page there is an option for RIP (Routing Information Protocol) direction which is set to none. Below is the small description which is given for this...


RIP Direction: RIP (Routing Information Protocol, RFC1058 and RFC1389) allows a Router to exchange routing information with other Routers. The RIP Direction selection controls how the Router sends and receives RIP packets. Both is the default.
When set to Both or Out Only, the Router will broadcast its routing table periodically.
When set to Both or In Only, it will incorporate the RIP information that it receives.
When set to None, it will not send any RIP packets and will ignore any RIP packets received.
RIP Version: This controls the format and the broadcasting method of the RIP packets that the Router sends. (It recognizes both formats when receiving.) By default, this is set for RIP-1.
RIP-1 is universally supported. RIP-1 is probably adequate for most networks, unless you have an unusual network setup.
RIP-2 carries more information. Both RIP-2B and RIP-2M send the routing data in RIP-2 format.
RIP-2B uses subnet broadcasting.
RIP-2M uses multicasting. (See note below.)




Should I change the RIP Direction to both? or should this be ignored?

[petestrash]

RIP should not have anything to do with TiVo, unless you are running it though 2 routers. What are the physical connections from your TiVo to the phone line?

Can you confirm that your current router's address is 192.168.0.1 and also post the results from your TiVo for:
traceroute 65.49.60.197

Also when you tested ping before, you tested pinging the unit you were testing from. Try pinging the other TiVo and see if it works on your internal network at least.

Everything still seems to point to an issue using the new router. Does it have a firewall, that you may need to open to your TiVo's addresses?

Peter.

[eden]

My network involves the new optus netgear modem wireless router which is connected via Ethernet to my apple airport extreme base station. I've tried bypassing my airport extreme and connecting my tivos directly to the new modem/wireless router. The tivo we have recently been discussing with the ip address 192.168.0.5 connects to my network via a d-link dwl-810+ Ethernet to wireless bridge. My other TiVo with the ip address 192.168.0.197 is wired.

I can confirm that my optus router has the ip 192.168.0.10 and my airport extreme has 192.168.0.3

[petestrash]

According to the oztivo.conf file you posted, you show your gateway address as 192.168.0.1, not 192.168.0.10 as you have just said.

Is 192.168.0.10 a typo?

Peter.

[eden]

I'm pretty sure 192.168.0.10 is right. I checked it all last night before I posted by telneting and typing nic_config_TiVo which had the gateway as .10. I then check my modem and that is .10.

If my TiVo connects to my airport should the gateway be the airport or the modem?

[petestrash]

ok, posts #8 & #10 both show your gateway as 192.168.0.1. So double check your current /etc/oztivo.conf file.

Also please try the other 2 tests I suggested in post #19.

Peter.

[eden]

I double checked it and the gateway is 192.168.0.10 so I have tried those tests again and have tried to ping my other tivo. These are the results from the Tivo that connects to my modem with a wireless bridge.

In the webpage of my optus modem/wireless router there is also a section which shows the attached devices of which it shows up everything connected as normal.

[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:10 errors:0 dropped:0 overruns:0 frame:0
TX packets:10 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.5 Bcast:192.168.0.255 Mask:255.255.255.0
UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1
RX packets:1230 errors:0 dropped:0 overruns:0 frame:0
TX packets:494 errors:0 dropped:0 overruns:0 carrier:0 coll:0
Interrupt:29

[TiVo [p0] ~]# route
route_info, afname=inet, options=33
Kernel IP routing table
Destination Gateway Genmask Flags Metric Ref Use Iface
192.168.0.0 * 255.255.255.0 U 32767 0 0 eth0
default 192.168.0.10 0.0.0.0 UG 0 0 0 eth0


[TiVo [p0] ~]# ping -c 5 192.168.0.5
PING 192.168.0.5 (192.168.0.5): 56 data bytes
64 bytes from 192.168.0.5: icmp_seq=0 ttl=255 time=1.3 ms
64 bytes from 192.168.0.5: icmp_seq=1 ttl=255 time=0.9 ms
64 bytes from 192.168.0.5: icmp_seq=2 ttl=255 time=0.9 ms
64 bytes from 192.168.0.5: icmp_seq=3 ttl=255 time=1.9 ms
64 bytes from 192.168.0.5: icmp_seq=4 ttl=255 time=0.9 ms

--- 192.168.0.5 ping statistics ---
5 packets transmitted, 5 packets received, 0% packet loss
round-trip min/avg/max = 0.9/1.1/1.9 ms


[TiVo [p0] ~]# ping -c 5 192.168.0.197
PING 192.168.0.197 (192.168.0.197): 56 data bytes
64 bytes from 192.168.0.197: icmp_seq=0 ttl=255 time=17.7 ms
64 bytes from 192.168.0.197: icmp_seq=1 ttl=255 time=2.9 ms
64 bytes from 192.168.0.197: icmp_seq=2 ttl=255 time=2.9 ms
64 bytes from 192.168.0.197: icmp_seq=3 ttl=255 time=2.9 ms
64 bytes from 192.168.0.197: icmp_seq=4 ttl=255 time=3.7 ms

--- 192.168.0.197 ping statistics ---
5 packets transmitted, 5 packets received, 0% packet loss
round-trip min/avg/max = 2.9/6.0/17.7 ms


[TiVo [p0] ~]# ping -c 5 65.49.60.197
PING 65.49.60.197 (65.49.60.197): 56 data bytes
64 bytes from 65.49.60.197: icmp_seq=0 ttl=57 time=223.6 ms
64 bytes from 65.49.60.197: icmp_seq=1 ttl=57 time=239.0 ms
64 bytes from 65.49.60.197: icmp_seq=2 ttl=57 time=220.9 ms
64 bytes from 65.49.60.197: icmp_seq=3 ttl=57 time=238.7 ms
64 bytes from 65.49.60.197: icmp_seq=4 ttl=57 time=214.2 ms

--- 65.49.60.197 ping statistics ---
5 packets transmitted, 5 packets received, 0% packet loss
round-trip min/avg/max = 214.2/227.2/239.0 ms


[TiVo [p0] ~]# wget http://65.49.60.197
--21:47:36-- http://65.49.60.197/
=> `index.html'
Connecting to 65.49.60.197:80... connected.
HTTP request sent, awaiting response... 301 Moved Permanently
Location: http://www.oztivo.net/twiki/bin/view [following]
--21:47:36-- http://www.oztivo.net/twiki/bin/view
=> `view'
Resolving www.oztivo.net... failed: Host not found.

[petestrash]

Ok, your gateway now looks good, and your ping to 65.49.60.197 is also now working which was not before, and your wget now produces a different result.

There is a DNS error with the wget command.

Have you tried a daily call recently, it may now work anyway?

If it still fails try these two commands:
wget http://65.49.60.197/twiki/bin/view

wget http://www.google.com


Peter.

PS remind me which version is this TiVo running.

[petestrash]

Also please show what you now have in your /etc/tclient.conf & /etc/oztivo.conf files.

Peter.

[eden]

This tivo is running version 1.5

[TiVo [p0] ~]# wget http://65.49.60.197/twiki/bin/view
--11:06:25-- http://65.49.60.197/twiki/bin/view
=> `view'
Connecting to 65.49.60.197:80... connected.
HTTP request sent, awaiting response... 200 OK
Length: 20,672 [text/html]

0% [ ] 0 --.--K/s 0% [ ] 8,368 0.00B/s 0% [ ] 14,176 0.00G/s 0% [ ] 20,672 0.00G/s 0% [ ] 20,672 0.00G/s ETA 00:00

11:06:27 (0.00 GB/s) - `view' saved [20672/20672]



[TiVo [p0] ~]# wget http://www.google.com
--11:07:24-- http://www.google.com/
=> `index.html'
Resolving www.google.com... failed: Host not found.


# Copyright (c) 2001 TiVo Inc.
#
# This file contains entries for each of the possible service
# instances supported. The fields are all ":": (colon) separated
# and are as follows with the folling meanings:
#
# label:phone_number:svr_addr:svr_port:ppp_user:ppp_ pass:radius_domain
#
# label This is a 3 character numeric field which must
# unique identify this entry (the /Setup field XXX
# will point to this). Note the value 911 is reserved
# to imply the Addr.itcl *_EMG_* fields. (i.e.
# emergency repair port). Note the value 000 is
# reserved to imply the Addr.itcl *_DEF_* fields
# (i.e. the default port).
# phone_number This is the full phone number to dial, minus any
# prefixes defined by the phone options screen
# svr_addr This is the Ip Address of the service to connect to
# svr_port This is the TCP port number of the service to
# connect to
# ppp_user This is the username to connect to the ppp modem
# ppp_pass This is the password to connect to the ppp modem
# radius_domain This is the radius domain to put after the generated username.
# If ppp_user is set then this will have no effect.

#
# This is the default port, it's values come from Addr.itcl not here
#
000:
# Dennis' Emulator
126::66.23.218.193:80:::
# This is for the server emulator on minnie. Trouble if your ISP blocks HTTP .9
#127::65.49.60.197:9090:::

# This uses emuProxy2 to avoid problems with transparent proxy. Thanks Tim!
#127::127.0.0.1:8000:::
# Connect Via the www.oztivo.net emulator
127::65.49.60.197:9090:::




# OzTiVo menu configuration settings file
# Please do not edit this file
# Put the TiVo disk back in your PC to reconfigure
nic=TurboNet
ip=192.168.0.5
mac=00:0B:AD:10:10:10
hostname=
modem=0
pppondss=0
netmask=255.255.255.0
gateway=192.168.0.10
ssid=
wep=
wepkey=

[petestrash]

You are definitely having DNS issues, as you can't even resolve www.google.com.

Use the following commands:

rw
mv /etc/resolv.conf /etc/resolv.conf.old

Then use joe or vi to make a new file called /etc/resolv.conf and paste the following into it.

# Example resolv.conf file
nameserver 64.62.190.9 # linode.com
nameserver 202.12.144.10 # ns.telstra.com.au
nameserver 61.88.88.88 # ns.optus.net.au
nameserver 208.67.222.222 # ns.opendns.org

Once saved, Now type:

ro
reboot

And try a daily call again.

Peter.

[eden]

I did everything however when I did a daily call it only comes back as "Failed. No dial- in number chosen."

I then tried to do a wget test and these were the results

[TiVo [p0] ~]# wget http://65.49.60.197
--01:27:59-- http://65.49.60.197/
=> `index.html.1'
Connecting to 65.49.60.197:80... connected.
HTTP request sent, awaiting response... 301 Moved Permanently
Location: http://www.oztivo.net/twiki/bin/view [following]
--01:27:59-- http://www.oztivo.net/twiki/bin/view
=> `view.1'
Resolving www.oztivo.net... done.
Connecting to www.oztivo.net[65.49.60.197]:80... connected.
HTTP request sent, awaiting response... 200 OK
Length: 20,680 [text/html]

0% [ ] 0 --.--K/s 0% [ ] 8,368 0.00B/s 0% [ ] 14,176 0.00G/s 0% [ ] 20,680 0.00G/s 0% [ ] 20,680 0.00G/s ETA 00:00

01:28:01 (0.00 GB/s) - `view.1' saved [20680/20680]



[TiVo [p0] ~]# wget http://www.google.com
--01:27:18-- http://www.google.com/
=> `index.html'
Resolving www.google.com... done.
Connecting to www.google.com[74.125.19.103]:80... connected.
HTTP request sent, awaiting response... 302 Found
Location: http://www.google.com.au/ [following]
--01:27:19-- http://www.google.com.au/
=> `index.html'
Resolving www.google.com.au... done.
Connecting to www.google.com.au[74.125.19.104]:80... connected.
HTTP request sent, awaiting response... 200 OK
Length: unspecified [text/html]

[<=> ] 0 --.--K/s [ <=> ] 5,599 0.00B/s

01:27:20 (0.00 GB/s) - `index.html' saved [5599]



Thanks
Eden

[petestrash]

I don't know how so many things seem to have been wrong...

But the good news is that DNS is now working, bad news is I don't know why daily calls are still failing.

Could you please attach the tclient log from only your latest attempt (since the DNS worked), and hopefully it will point to the error you now have.

Peter.

[eden]

I cleared my tclient log and then did a daily call which failed.


[TiVo [p0] ~]# cat /var/log/tclient
Oct 15 19:16:22 (none) tcphonehome[145]: getting /State/GeneralConfig/Complete
Oct 15 19:16:22 (none) tcphonehome[145]: Setting MCP PhoneHome action: RUNNING
Oct 15 19:16:22 (none) tcphonehome[145]: pCommMempool empty
Oct 15 19:16:22 (none) tcphonehome[145]: useBackupTollFree is 0
Oct 15 19:16:22 (none) tcphonehome[145]: phonehome: received message. type = 30 subtype = 0
Oct 15 19:16:22 (none) tcphonehome[145]: creating CommGlobals
Oct 15 19:16:23 (none) tcphonehome[145]: created CommGlobals
Oct 15 19:16:23 (none) tcphonehome[145]: PerformCall, subtype=0 forceTollFree=0 automated=0
Oct 15 19:16:23 (none) tcphonehome[145]: GetPostalCodeVersion - /PostalCode/03000 ServerVersion=60
Oct 15 19:16:23 (none) tcphonehome[145]: debug: sumServerVersion=60
Oct 15 19:16:23 (none) tcphonehome[145]: setCallStatus called with: In Progress state 1
Oct 15 19:16:23 (none) tcphonehome[145]: LastCallAttempt at 1224060546
Oct 15 19:16:23 (none) tcphonehome[145]: setting call status to: In Progress
Oct 15 19:16:23 (none) tcphonehome[145]: setting call in progress to 1 (second successCount)
Oct 15 19:16:23 (none) tcphonehome[145]: Setting callActive to 1
Oct 15 19:16:23 (none) tcphonehome[145]: setting call attempt
Oct 15 19:16:23 (none) tcphonehome[145]: Error statting file /var/log/http: No such file or directory (errno=2)
Oct 15 19:16:23 (none) tcphonehome[145]: Error statting file /var/log/Ohttp: No such file or directory (errno=2)
Oct 15 19:16:23 (none) tcphonehome[145]: Calling TClient
Oct 15 19:16:23 (none) comm[145]: CallStatusReporter: Phase: Select_Phone, Status In Progress
Oct 15 19:16:23 (none) comm[145]: CallStatusReporter: sending message "EX|29"
Oct 15 19:16:24 (none) tcphonehome[145]: MakeDialConfig failed: 0xffff
Oct 15 19:16:24 (none) tcphonehome[145]: GetPostalCodeVersion - /PostalCode/03000 ServerVersion=60
Oct 15 19:16:24 (none) tcphonehome[145]: debug: sumServerVersion=60
Oct 15 19:16:24 (none) comm[145]: AT&V1&V2
Oct 15 19:16:24 (none) comm[145]: TERMINATION REASON.......... NONE
Oct 15 19:16:24 (none) comm[145]: LAST TX rate................ N/A
Oct 15 19:16:24 (none) comm[145]: HIGHEST TX rate............. 300 BPS
Oct 15 19:16:24 (none) comm[145]: LAST RX rate................ N/A
Oct 15 19:16:24 (none) comm[145]: HIGHEST RX rate............. 300 BPS
Oct 15 19:16:24 (none) comm[145]: PROTOCOL.................... N/A
Oct 15 19:16:24 (none) comm[145]: COMPRESSION................. N/A
Oct 15 19:16:24 (none) comm[145]: Line QUALITY................ 255
Oct 15 19:16:24 (none) comm[145]: Rx LEVEL.................... 215
Oct 15 19:16:24 (none) comm[145]: Highest Rx State............ 00
Oct 15 19:16:24 (none) comm[145]: Highest TX State............ 00
Oct 15 19:16:24 (none) comm[145]: EQM Sum..................... FFFF
Oct 15 19:16:24 (none) comm[145]: RBS Pattern................. FF
Oct 15 19:16:24 (none) comm[145]: Rate Drop................... FF
Oct 15 19:16:24 (none) comm[145]: Digital Loss................ None
Oct 15 19:16:24 (none) comm[145]: Local Rtrn Count............ 00
Oct 15 19:16:24 (none) comm[145]: Remote Rtrn Count........... 00
Oct 15 19:16:24 (none) comm[145]: BEGINaa255ab255ac0ad255ba255bb255bc0bd255ca255cb25 5cc255da255ea255eb255fa255fb255fc0ga255gb255ha255h b255hc0hd0he255hf255hg255hh255hi255hj255hk255hl255 hm255hn255ho255hp255hq255hr255hs255ia255ib255ic0ja 0jb0jc0jd0je0ka255kb255kc255kd255ke255kf255kg255kh 255ki255kj255kk255kl255km255kn255la0lb0lc255ld255m a0mb0mc0na255nb255oa255ob255oc255od255oe255of255og 255pa255pb0qa21qb0qc255ra255rb255rc255END
Oct 15 19:16:24 (none) comm[145]: OK
Oct 15 19:16:24 (none) comm[145]: ATZ
Oct 15 19:16:24 (none) comm[145]: OK
Oct 15 19:16:24 (none) comm[145]: CallStatusReporter: Phase: Select_Phone, Status Failed
Oct 15 19:16:24 (none) comm[145]: CallStatusReporter: sending message "EX|48"
Oct 15 19:16:24 (none) tcphonehome[145]: TClient failed: EX|48
Oct 15 19:16:24 (none) tcphonehome[145]: Sending dialup event, subtype 8, msg EX|48
Oct 15 19:16:24 (none) tcphonehome[145]: setCallStatus called with: Failed state 0
Oct 15 19:16:28 (none) tcphonehome[145]: LastCallAttempt at 1224098183
Oct 15 19:16:28 (none) tcphonehome[145]: setting call status to: Failed
Oct 15 19:16:28 (none) tcphonehome[145]: setting call in progress to 0 (second successCount)
Oct 15 19:16:28 (none) tcphonehome[145]: Setting callActive to 0
Oct 15 19:16:28 (none) comm[145]: CallStatusReporter: sending data changed event 20
Oct 15 19:16:28 (none) tcphonehome[145]: destroying CommGlobals!
Oct 15 19:16:28 (none) tcphonehome[145]: pCommMempool empty
Oct 15 19:16:35 (none) tcphonehome[145]: Setting MCP PhoneHome action: ENABLED

[petestrash]

It is still trying to dial via the inbuilt modem, which is failing.

It might just be easiest to upgrade your TiVo first, then I know you have the latest files, and then continue from there if we need you.

I am stretching my memory to try and remember how everything was done back in r1.5 and earlier.

follow this wiki (http://www.oztivo.net/twiki/bin/view/Howto/UpgradeOzTiVoImage#Upgrading_a_1_3_1_4_or_1_5_Imag e)to upgrade.

Peter.

[eden]

I upgraded to 1.6 and then updated to the new server cause I noticed in the oztivo.conf file a reference to the minnie server but the daily call still failed. So I cleared the tclient log tried and tried a daily call again. This is the tclient log that followed.

[TiVo [p0] ~]# cat /var/log/tclient
Oct 16 02:58:31 (none) tcphonehome[186]: getting /State/GeneralConfig/Complete
Oct 16 02:58:31 (none) tcphonehome[186]: Setting MCP PhoneHome action: RUNNING
Oct 16 02:58:31 (none) tcphonehome[186]: pCommMempool empty
Oct 16 02:58:31 (none) tcphonehome[186]: useBackupTollFree is 0
Oct 16 02:58:31 (none) tcphonehome[186]: phonehome: received message. type = 30 subtype = 0
Oct 16 02:58:31 (none) tcphonehome[186]: creating CommGlobals
Oct 16 02:58:32 (none) tcphonehome[186]: created CommGlobals
Oct 16 02:58:32 (none) tcphonehome[186]: PerformCall, subtype=0 forceTollFree=0 automated=0
Oct 16 02:58:32 (none) tcphonehome[186]: GetPostalCodeVersion - /PostalCode/03000 ServerVersion=60
Oct 16 02:58:32 (none) tcphonehome[186]: debug: sumServerVersion=60
Oct 16 02:58:32 (none) tcphonehome[186]: setCallStatus called with: In Progress state 1
Oct 16 02:58:32 (none) tcphonehome[186]: LastCallAttempt at 1224125511
Oct 16 02:58:32 (none) tcphonehome[186]: setting call status to: In Progress
Oct 16 02:58:32 (none) tcphonehome[186]: setting call in progress to 1 (second successCount)
Oct 16 02:58:32 (none) tcphonehome[186]: Setting callActive to 1
Oct 16 02:58:32 (none) tcphonehome[186]: setting call attempt
Oct 16 02:58:32 (none) tcphonehome[186]: Error statting file /var/log/http: No such file or directory (errno=2)
Oct 16 02:58:32 (none) tcphonehome[186]: Error statting file /var/log/Ohttp: No such file or directory (errno=2)
Oct 16 02:58:32 (none) tcphonehome[186]: Calling TClient
Oct 16 02:58:32 (none) comm[186]: CallStatusReporter: Phase: Select_Phone, Status In Progress
Oct 16 02:58:32 (none) comm[186]: CallStatusReporter: sending message "EX|29"
Oct 16 02:58:32 (none) tcphonehome[186]: MakeDialConfig failed: 0xffff
Oct 16 02:58:32 (none) tcphonehome[186]: GetPostalCodeVersion - /PostalCode/03000 ServerVersion=60
Oct 16 02:58:32 (none) tcphonehome[186]: debug: sumServerVersion=60
Oct 16 02:58:32 (none) comm[186]: AT&V1&V2
Oct 16 02:58:32 (none) comm[186]: TERMINATION REASON.......... NONE
Oct 16 02:58:32 (none) comm[186]: LAST TX rate................ N/A
Oct 16 02:58:32 (none) comm[186]: HIGHEST TX rate............. 300 BPS
Oct 16 02:58:32 (none) comm[186]: LAST RX rate................ N/A
Oct 16 02:58:32 (none) comm[186]: HIGHEST RX rate............. 300 BPS
Oct 16 02:58:32 (none) comm[186]: PROTOCOL.................... N/A
Oct 16 02:58:32 (none) comm[186]: COMPRESSION................. N/A
Oct 16 02:58:32 (none) comm[186]: Line QUALITY................ 255
Oct 16 02:58:32 (none) comm[186]: Rx LEVEL.................... 215
Oct 16 02:58:32 (none) comm[186]: Highest Rx State............ 00
Oct 16 02:58:32 (none) comm[186]: Highest TX State............ 00
Oct 16 02:58:32 (none) comm[186]: EQM Sum..................... FFFF
Oct 16 02:58:32 (none) comm[186]: RBS Pattern................. FF
Oct 16 02:58:32 (none) comm[186]: Rate Drop................... FF
Oct 16 02:58:32 (none) comm[186]: Digital Loss................ None
Oct 16 02:58:32 (none) comm[186]: Local Rtrn Count............ 00
Oct 16 02:58:32 (none) comm[186]: Remote Rtrn Count........... 00
Oct 16 02:58:32 (none) comm[186]: BEGINaa255ab255ac0ad255ba255bb255bc0bd255ca255cb25 5cc255da255ea255eb255fa255fb255fc0ga255gb255ha255h b255hc0hd0he255hf255hg255hh255hi255hj255hk255hl255 hm255hn255ho255hp255hq255hr255hs255ia255ib255ic0ja 0jb0jc0jd0je0ka255kb255kc255kd255ke255kf255kg255kh 255ki255kj255kk255kl255km255kn255la0lb0lc255ld255m a0mb0mc0na255nb255oa255ob255oc255od255oe255of255og 255pa255pb0qa21qb0qc255ra255rb255rc255END
Oct 16 02:58:32 (none) comm[186]: OK
Oct 16 02:58:33 (none) comm[186]: ATZ
Oct 16 02:58:33 (none) comm[186]: OK
Oct 16 02:58:33 (none) comm[186]: CallStatusReporter: Phase: Select_Phone, Status Failed
Oct 16 02:58:33 (none) comm[186]: CallStatusReporter: sending message "EX|48"
Oct 16 02:58:33 (none) tcphonehome[186]: TClient failed: EX|48
Oct 16 02:58:33 (none) tcphonehome[186]: Sending dialup event, subtype 8, msg EX|48
Oct 16 02:58:33 (none) tcphonehome[186]: setCallStatus called with: Failed state 0
Oct 16 02:58:33 (none) tcphonehome[186]: LastCallAttempt at 1224125912
Oct 16 02:58:33 (none) tcphonehome[186]: setting call status to: Failed
Oct 16 02:58:33 (none) tcphonehome[186]: setting call in progress to 0 (second successCount)
Oct 16 02:58:33 (none) tcphonehome[186]: Setting callActive to 0
Oct 16 02:58:33 (none) comm[186]: CallStatusReporter: sending data changed event 20
Oct 16 02:58:33 (none) tcphonehome[186]: destroying CommGlobals!
Oct 16 02:58:33 (none) tcphonehome[186]: pCommMempool empty
Oct 16 02:58:40 (none) tcphonehome[186]: Setting MCP PhoneHome action: ENABLED

[petestrash]

It's exactly the same.

After doing the upgrade did you run the update routine to bring you up to date with the current release?

If not do that, reboot, then if it still fails post your /etc/oztivo_version file and /etc/rc.d/rc.net files.

Peter.

[eden]

Yes I did bring it up to date. here are the files you wanted.


1.6.2-20081005



#!/bin/sh
# Install network kernel modules, set the IP address and gateway,
# or launch the DHCP client.
# $Revision: 1.6 $
#
###############################
# Send error mail including contents of /etc/oztivo.conf
neterr()
{
t="/tmp/err.$$"
syslog -t rc.net "ERROR: $1"
echo "The following error occurred as part of the network configuration:" >$t
echo >> $t
echo $1 >> $t
echo >> $t
echo "The network config file oztivo.conf has this:" >> $t
echo >> $t
cat /etc/oztivo.conf >> $t
sendtivomesg.tcl TiVo 'Network Config Error' < $t
rm -f $t
}

# Ensure that we have a network config file
if [ ! -f /etc/oztivo.conf ]; then
echo "Error: oztivo.conf is missing!" | \
sendtivomesg.tcl TiVo 'oztivo.conf Missing'
fi

# Load the appropriate module
case $nic in
TurboNet)
echo "Starting TurboNet"
# Fill in a timing value if there isn't one
if [ -z "$timing" ]; then timing=3; fi
/sbin/insmod -f /lib/modules/turbonet.o macaddr=$mac timing=$timing || \
neterr "turbonet.o module failed using mac=$mac"
export DYNAMIC_NET_DEV=eth0
;;
Cachecard)
echo "Starting Cachecard"
/sbin/insmod -f /lib/modules/turbonet2.o macaddr=$mac debuglevel=0 || \
neterr "turbonet2.o module failed using mac=$mac"
export DYNAMIC_NET_DEV=eth0
;;
AirNet)
echo "Starting AirNet"
if [ "$wep" = "None" ]; then
# No $wep, don't need to supply key
/sbin/insmod -f /lib/modules/airnet.o ssid=$ssid timing=6 || \
neterr "airnet.o with no key module failed using ssid=$ssid"
else
# need to supply a key to the kernel module
/sbin/insmod -f /lib/modules/airnet.o ssid=$ssid key=$wepkey timing=6||
neterr "airnet.o with key module failed using ssid=$ssid key=$wepkey
fi
export DYNAMIC_NET_DEV=eth0
;;
TiVoNet)
echo "Starting TiVoNet"
/sbin/insmod -f /lib/modules/8390tridge.o || neterr "8390tridge.o failed"
/sbin/insmod -f /lib/modules/tivone.o || neterr "tivone.o failed"
export DYNAMIC_NET_DEV=eth0
;;
PPPonDSS)
echo "Starting PPP over serial"
/etc/rc.d/rc.ppp &
export DYNAMIC_NET_DEV=ppp0
ip=None
;;
Modem) # Nothing to do for this one
ip=None
;;
*) neterr "Unknown network type $nic"
;;
esac

# Run ifconfig if the IP address is static, or use DHCP to get an IP address,
# or do nothing if we are using PPPonDSS or the internal Modem
case $ip in
DHCP)
mkdir -p /var/state/dhcp || neterr "Cannot mkdir /var/state/dhcp"
/sbin/dhclient -q eth0 2>/dev/null &
;;
None)
;;
*)
# Set up the IP address and default router
/sbin/ifconfig eth0 $ip netmask $netmask up || \
neterr "ifconfig failed using $ip netmask $netmask"
/sbin/route add default gw $gateway || \
neterr "route failed using default gw $gateway"
;;
esac

[petestrash]

I'm getting stuck now. I just don't know why it wants to call via the modem.

Try this again and list the results to make sure it hasn't changed:

dbget /State/PhoneConfig DialPrefix

And also try this to disable the modem:

rw
mv /dev/cua1 /dev/cua1.disabled
ro

Then reboot and try again.

Peter.

[eden]

The first line I put in gave me the result ,#401

After this I tried the next instruction and when I did the daily call it seemed to take a while when preparing call and then came back with the message UknownError.

Here is the tclient log.


Oct 17 09:07:16 (none) tcphonehome[149]: getting /State/GeneralConfig/Complete
Oct 17 09:07:17 (none) tcphonehome[149]: Setting MCP PhoneHome action: RUNNING
Oct 17 09:07:17 (none) tcphonehome[149]: pCommMempool empty
Oct 17 09:07:17 (none) tcphonehome[149]: useBackupTollFree is 1
Oct 17 09:07:17 (none) tcphonehome[149]: phonehome: received message. type = 30 subtype = 0
Oct 17 09:07:17 (none) tcphonehome[149]: creating CommGlobals
Oct 17 09:07:18 (none) tcphonehome[149]: created CommGlobals
Oct 17 09:07:18 (none) tcphonehome[149]: PerformCall, subtype=0 forceTollFree=0 automated=0
Oct 17 09:07:18 (none) tcphonehome[149]: GetPostalCodeVersion - /PostalCode/03000 ServerVersion=60
Oct 17 09:07:18 (none) tcphonehome[149]: debug: sumServerVersion=60
Oct 17 09:07:18 (none) comm[149]: ModemDescriptor::ModemDescriptor open returns -1
Oct 17 09:07:18 (none) comm[149]: ModemDevice::ModemDevice: tcgetattr() status = -1
Oct 17 09:07:18 (none) comm[149]: ModemDevice::ModemDevice tcflush() status = -1
Oct 17 09:07:18 (none) comm[149]: ModemDevice::ModemDevice tcsetattr() status = -1
Oct 17 09:07:18 (none) comm[149]: ModemDescriptor::~ModemDescriptor tcdrain() status -1
Oct 17 09:07:18 (none) comm[149]: ModemDescriptor::~ModemDescriptor close() status -1
Oct 17 09:07:18 (none) tcphonehome[149]: setCallStatus called with: In Progress state 1
Oct 17 09:07:18 (none) tcphonehome[149]: LastCallAttempt at 1224234212
Oct 17 09:07:18 (none) tcphonehome[149]: setting call status to: In Progress
Oct 17 09:07:18 (none) tcphonehome[149]: setting call in progress to 1 (second successCount)
Oct 17 09:07:18 (none) tcphonehome[149]: Setting callActive to 1
Oct 17 09:07:18 (none) tcphonehome[149]: setting call attempt
Oct 17 09:07:18 (none) tcphonehome[149]: Error statting file /var/log/http: No such file or directory (errno=2)
Oct 17 09:07:18 (none) tcphonehome[149]: Error statting file /var/log/Ohttp: No such file or directory (errno=2)
Oct 17 09:07:18 (none) tcphonehome[149]: Calling TClient
Oct 17 09:07:18 (none) comm[149]: CallStatusReporter: Phase: Select_Phone, Status In Progress
Oct 17 09:07:18 (none) comm[149]: CallStatusReporter: sending message "EX|29"
Oct 17 09:07:19 (none) tcphonehome[149]: MakeDialConfig failed: 0xffff
Oct 17 09:07:19 (none) tcphonehome[149]: GetPostalCodeVersion - /PostalCode/03000 ServerVersion=60
Oct 17 09:07:19 (none) tcphonehome[149]: debug: sumServerVersion=60
Oct 17 09:07:19 (none) comm[149]: ModemDescriptor::ModemDescriptor open returns -1
Oct 17 09:08:11 (none) tcphonehome[126]: TCphonehome active
Oct 17 09:08:11 (none) tcphonehome[149]: cleaning /Setup
Oct 17 09:08:11 (none) tcphonehome[149]: Fetching /SwSystemACTIVE/Name
Oct 17 09:08:11 (none) tcphonehome[149]: Last Call Status Was: 'In Progress' (size 11)
Oct 17 09:08:11 (none) tcphonehome[149]: Last Call Status Will Be: Failed
Oct 17 09:08:11 (none) tcphonehome[149]: setCallStatus called with: Failed state 0
Oct 17 09:08:11 (none) tcphonehome[149]: LastCallAttempt at 1224234438
Oct 17 09:08:11 (none) tcphonehome[149]: setting call status to: Failed
Oct 17 09:08:11 (none) tcphonehome[149]: setting call in progress to 0 (second successCount)
Oct 17 09:08:11 (none) tcphonehome[149]: setting CallStatusInfo to: 6
Oct 17 09:08:11 (none) tcphonehome[149]: Setting callActive to 0
Oct 17 09:08:12 (none) tcphonehome[149]: PhoneHome: statusValue = <0>, getResult = <0>
Oct 17 09:08:12 (none) tcphonehome[149]: /State/Avalanche LastStatus was <0> and getResult was <0>, changing to unknown
Oct 17 09:08:12 (none) tcphonehome[149]: finished cleaning /Setup
Oct 17 09:08:12 (none) tcphonehome[149]: About to execute: /sbin/ifconfig eth0 2>&1
Oct 17 09:08:12 (none) tcphonehome[149]: Command Output: eth0 Link encap:Ethernet HWaddr 00:0B:AD:10:10:10
Oct 17 09:08:12 (none) tcphonehome[149]: Command Output: inet addr:192.168.0.5 Bcast:192.168.0.255 Mask:255.255.255.0
Oct 17 09:08:12 (none) tcphonehome[149]: Command Output: UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1
Oct 17 09:08:12 (none) tcphonehome[149]: Command Output: RX packets:7 errors:0 dropped:0 overruns:0 frame:0
Oct 17 09:08:12 (none) tcphonehome[149]: Command Output: TX packets:0 errors:0 dropped:0 overruns:0 carrier:0 coll:0
Oct 17 09:08:12 (none) tcphonehome[149]: Command Output: Interrupt:29
Oct 17 09:08:12 (none) tcphonehome[149]: Command Output:
Oct 17 09:08:12 (none) tcphonehome[149]: Command succeeded
Oct 17 09:08:12 (none) tcphonehome[149]: NOT Using debug ethernet
Oct 17 09:08:12 (none) tcphonehome[149]: Error statting file /var/log/http: No such file or directory (errno=2)
Oct 17 09:08:12 (none) tcphonehome[149]: Error statting file /var/log/Ohttp: No such file or directory (errno=2)
Oct 17 09:08:12 (none) tcphonehome[149]: Timesync is within the past 5 days... all is well
Oct 17 09:08:12 (none) tcphonehome[149]: ReschedCall: reason = 7, secSinceLast = 0, numFails = 0
Oct 17 09:08:12 (none) tcphonehome[149]: Schedule call after failure
Oct 17 09:08:12 (none) tcphonehome[149]: setting next attempt at 1224237612 (Fri Oct 17 10:00:12 2008 )
Oct 17 09:08:12 (none) tcphonehome[149]: ReschedCall(7, 0) in 52 min
Oct 17 09:08:12 (none) PhoneAction[149]: PhoneAction 2 register complete timeout 3120
Oct 17 09:08:12 (none) PhoneAction[149]: Register Complete: Next call should happen at Fri Oct 17 10:00:12 2008
Oct 17 09:08:12 (none) tcphonehome[149]: called getTZ
Oct 17 09:08:12 (none) WatchdogAction[149]: WatchdogAction register complete

[petestrash]

Ok looking back through your posts you seem to have had virtually the same issue in June that you now have with this TiVo wanting to use the modem.

I have not seen a case like it.

I only have one area left that I want to explore. Can you please list what is on the screen when you go into tivowebplus MFS > State > PhoneConfig.

Peter.

[eden]

PhoneConfig 2276/10 {
Version = 19819
CallWaitingPrefix = {}
LocalAreaCode = 003
TollFreeNum = 0
DialInAreaCode = {}
DialInPrefix = {}
DialInNum = 1272240
LastDialInUpdateDate = 14155
InventoryFile = {}
LastSuccessCallSecInDay = 1223032181
LastSuccessPgdCallSecInDay = 1223032181
LastCallAttemptSecInDay = 1224264695
DialConfig = 127
DialPrefix = ,#401
LastCallStatus = Failed
CallStatusInfo = 6
NextCallAttemptSecInDay = 1224285481
IndexPath = /State/PhoneConfig
}

[petestrash]

Everything looks good.

One more thing to try in case there is some weird hidden character in DialPrefix:

dbsetx /State/PhoneConfig DialPrefix ',#401'

This will just set it to ,#401 again.

Reboot and try again.

If this does not work for you I'll post a message to the mailing list.

Peter.

[eden]

It is still showing UnknownError when i make a daily call.

The tivo is now rebooting itself quite frequently.

[petestrash]

Ok, I will post a message to the mailing list an see if someone else has some different suggestions.

Peter.

[eden]

thanks for the help.

Would I help if I just reinstalled the image. It doesn't bother me if I lose my shows.

[petestrash]

I assumed you would prefer not to do it.

I have already posted the message.

If you can wait a couple of days, someone might come up with something that we haven't tried.

Otherwise go ahead and start again.

Make sure you download the latest image, and update it after a reboot.

Peter.

[petestrash]

Nothing from the list request yet, but I did have another thought in the meantime.

It may be corruption of the MFS (database) which is not allowing it to read the value of DialPrefix correctly.

Try the command:
mfscheck -fix

This repairs any errors in the database. It takes quite a while to run, and from memory reboots automatically when done. If it doesn't, then just reboot when the prompt returns. If you see any errors listed, paste the details here.

Peter.

[eden]

It did take a while, for a second I thought well nothing is happening here and then...


[TiVo [p0] ~]# mfscheck -fix
Couldn't CreateSharedMemoryFile() /var/tmp//fsmem.mpkey -- check permissions
FsInit failed: 0x11001
[TiVo [p0] ~]#

[petestrash]

No worries, that error happens a lot.

Use these 2 commands:

rm /var/tmp//fsmem.mpkey
mfscheck -fix

Peter.

[eden]

It is still making the same error with mfscheck -fix.

[TiVo [p0] ~]# rm /var/tmp//fsmem.mpkey
[TiVo [p0] ~]# mfscheck -fix
Couldn't CreateSharedMemoryFile() /var/tmp//fsmem.mpkey -- check permissions
FsInit failed: 0x11001
[TiVo [p0] ~]#

[petestrash]

Okay, let's try a different route:

chmod 777 /var/tmp//fsmem.mpkey
rm /var/tmp//fsmem.mpkey
mfscheck -fix

Peter.

EDIT: For those that saw the original version of this post, the // in the rm line is correct.

[eden]

Same again.

[TiVo [p0] ~]# chmod 777 /var/tmp//fsmem.mpkey
[TiVo [p0] ~]# rm /var/tmp//fsmem.mpkey
[TiVo [p0] ~]# mfscheck -fix
Couldn't CreateSharedMemoryFile() /var/tmp//fsmem.mpkey -- check permissions
FsInit failed: 0x11001
[TiVo [p0] ~]#

[petestrash]

Ok, lets try

chmod 777 /var/tmp//fsmem.mpkey
ls -l /var/tmp//fsmem.mpkey

And take a note of the results.

Now we will try fixing the file system first with this command.

fsfix

It will take a while to run. Again take a note of any errors, and reboot when finished then try a daily call.

We will come back to mfscheck next.

Peter.

[eden]

As fsfix finishes and I guess it was happening with mfscheck -fix as well, the tivo seems to hang until it is rebooted. And then when I try to do a daily call the tivo automatically reboots and the daily call fails.

Here is what was telnetted.

[TiVo [p0] ~]# chmod 777 /var/tmp//fsmem.mpkey
[TiVo [p0] ~]# ls -l /var/tmp//fsmem.mpkey
-rwxrwxrwx 1 0 0 12 Oct 22 19:20 /var/tmp//fsmem.mpkey
[TiVo [p0] ~]# fsfix
Couldn't CreateSharedMemoryFile() /var/tmp//fsmem.mpkey -- check permissions
Error in FsInit: 0x11001

[petestrash]

Ok, that is just weird.

I'll put my hands up now, and accept defeat.

Go ahead and re-image as you offered a few days ago.

Peter.

[eden]

I have to wait till friday, I'll let you know how I go.

Thanks for your help. Very much appreciated.

[petestrash]

Actually since you are waiting till Friday, you could try this:

[TiVo [p0] ~]# chmod 777 /var/tmp//fsmem.mpkey
[TiVo [p0] ~]# rm /var/tmp//fsmem.mpkey
[TiVo [p0] ~]# fsfix

Peter

[eden]

Hi peter

the last commands you sent were no different so today I re-imaged both Tivo's.

Everything went well, re-imaging with 1.6.2-20080604 was successful. Then I went to do the guided setup and everything worked. It managed to make all the necessary calls. Then when I had to wait for the 4-8 hours I went and did the guided setup for my other tivo.

Everything also went perfectly (a first for me) but I guess I got too excited and right after the guided setup the tivo just reset itself.

Then when it reloads it froze on the Boot PROM screen. So I decided to leave it for a while but nothing happened. I then rebooted the tivo and when it started again it froze on the Maintenance Mode screen and every time I reboot it gets stuck in this position.

By now the first tivo has completed indexing so I reboot it to get out of maintenance mode and when it starts up it gets stuck on the Boot PROM screen. No amount of rebooting changes things.

I then did a bit of reading on other threads and I didn't like what I saw. I think there were three possible problems

1) Plugs not in place properly.

I checked this and still no improvement.

2) Tivo image corrupted or not installed properly.

No real biggy, I'm going to try and do it all over tomorrow.

3) HDD dead.

This one upset me cause the second tivo (the one which had the problem first) has a new seagate 254(?)GB drive. It shouldn't be dead.

Anyway I thought you might be interested to know how I'm going. I guess on the bright side the problem of not being able to do a daily call seems to be fixed by the re-imaging.

[Darren King]

3) HDD dead.

This is the most likely cause. Freezing at various points and/or not getting past the PROM boot screen is a sure sign of hard disk problems.


This one upset me cause the second tivo (the one which had the problem first) has a new seagate 254(?)GB drive. It shouldn't be dead.

There's no such thing as "shouldn't" as I've had a few that give up soon after purchase. It happens sometimes, and in no way unusual or limited to just Seagate hard disks. I would not be too upset because if it is a new hard disk then just follow the procedures on the Seagate website to get a warranty replacement as it will have a 5 year replacement warranty. The Seagate website will show you what you need to do to initiate a return and even allow you to print out the necessary paperwork and shipping labels.

Might also be a good idea while you are there to grab a copy of Seatools (get the CD bootable version) and check both your hard disks with this. Seatools will work even with old and/or non-Seagate hard disks fine.

[petestrash]

I agree with Darren, the only reason TiVo gets stuck on a boot screen is the hard drive is not being recognised or corrupt.

Follow Darrens advise about testing with Seatools.

Peter.

[eden]

Well I tested both HDD. The new one passed the short DST test so I re-imaged and have just finished the guided setup and everything seems ok, for now at least.

The old HDD failed the short DST test almost immediately. There was no reason given for the failure however Seatools did suggest I try the long test. I figured this HDD is quite old now hasn't been working properly recently and the short test failed that most likely so too will the long test.

I think it's out of warranty as it's the HDD that came with my Tivo and that is already a few years old that I'll just have to go buy a new one.

Thank you Peter and Darren for all your help.

[petestrash]

Good news, hopefully your problems are now solved.

Peter.

[Darren King]

Sounds good.

The old hard disk that failed the short test will be your problem with that TiVo so a new hard disk will fix it.

The other hard disk that passed the short test may be OK and glad to hear it is working, but if you have any further issues then my advice would be to run the full test as it does not take too long and tests all sectors on the hard disk. TiVo's don't like hard disks with any surface errors.