PDA

View Full Version : var directory wiped...no connectivity


michaeljc70
12-15-2007, 06:29 PM
My hacked Dtivo no longer has network connectivity. I pulled the drive and hooked it to my PC and noticed the VAR directory was empty. I have no idea where to begin trying to get my network connectivity working again.

Everything else (hacks directory,rc.sysinit.author, etc) seems intact and the Tivo works just fine.

Thanks

Jamie
12-15-2007, 08:07 PM
Generally the way to debug network connectivity issues is from a serial console bash. So break out your serial cable and start looking around. Is the network adapter recognized? Was it assigned an IP? Can you ping out? Can you ping in? etc.

michaeljc70
12-16-2007, 01:24 PM
Generally the way to debug network connectivity issues is from a serial console bash. So break out your serial cable and start looking around. Is the network adapter recognized? Was it assigned an IP? Can you ping out? Can you ping in? etc.

It is not getting an IP, at least looking from my router. Since there is nothing in VAR, I can't look at the logs which is confusing me. I thought they were located in VAR.

I don't have a serial cable, but it looks like I may need to get one if can't debug by puling the drive.

angra
12-16-2007, 11:28 PM
my apologies if you know this already, but it's not clear from your post.

if you wish to pull the drive and look at the logs, you will need to mount partition 9.

Even if you are able to get what you need via pulled drive, you really are best off to have a serial cable if you plan to continue in this hobby. It will save you a lot of hassles and is occasionally the only way to really see what's going on.

michaeljc70
12-17-2007, 03:26 AM
my apologies if you know this already, but it's not clear from your post.

if you wish to pull the drive and look at the logs, you will need to mount partition 9.

Even if you are able to get what you need via pulled drive, you really are best off to have a serial cable if you plan to continue in this hobby. It will save you a lot of hassles and is occasionally the only way to really see what's going on.

I mounted partition 4 (failed), 7 and 9. On 7 there is nothing in the var directory. In 9, there is a log directory, but no log files (kernel, etc.).

I am wondering if it is a HD issue. Long story short, this started when I tried to install Hackman module and got a copy error while FTping it. It still won't let me delete those files (I removed TWP from my startup to eliminate that as a potential issue). I get an "input/output" error when trying to LS or RM those files. I ran WD diagnostics on the drive and it said there were "too many errors". As I said earlier, the Tivo works perfectly other than networking.

michaeljc70
12-17-2007, 02:08 PM
Stupidly, I have been doing this for a couple yrs and never had a serial cable (I thought). I plugged in my Philips Pronto remote cable and it worked perfectly! Anyway, here is what I see when my Tivo boots. I also attached my kernel log.

I am not sure where to look to see the USB port/networking aspect....

Jamie
12-17-2007, 03:06 PM
These lines in the kernel log indicate the usb ethernet device was found and the driver loaded:
Dec 17 17:54:40 (none) kernel: eth0: register usbnet usb-00:0d.2-2, ASIX AX88772 USB 2.0 Ethernet
Dec 17 17:54:40 (none) kernel: eth0: open: enable queueing (rx 73, tx 73) mtu 1500 ASIX framing
Next step is to ensure that it is configured with an IP address, netmask, gateway, etc. ifconfig eth0 should tell you that. Also, make sure you've turned off the iptables firewall.

IMO, the best way to setup your network settings is via the tivo network menus. Remove everything from your rc.sysinit.author that messes around with network settings, and let the tivo software do it all. On a dtivo, you need a tivoapp patch to enable the network settings menus.

michaeljc70
12-17-2007, 03:55 PM
It looks like the IP is fine....I don't see the gateway (192.168.1.1).

I guess I should have posted in the newbie area as I am clueless. When I searched for the tivoapp patch, it looks like it depends on which version you are running. I can't remember and a look in the logs and a search hasn't helped me determine which version I am running.....the System Info on the box says 6.2-01-2-381 but I have no idea if that is 6.2x or what. Since it looks like the IP is correct, do I even need to worry about this?

bash-2.02# ifconfig eth0
eth0 Link encap:Ethernet HWaddr 00:50:B6:00:80:83
inet addr:192.168.1.111 Bcast:192.168.1.255 Mask:255.255.255.0
UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1
RX packets:98 errors:0 dropped:0 overruns:0 frame:0
TX packets:21 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:100
RX bytes:4820 (4.7 Kb) TX bytes:2506 (2.4 Kb)

bash-2.02# ApgManager Transition from state FAST_LOAD to F

Jamie
12-17-2007, 05:00 PM
route will show you the gateway.

ipconfig indicates that you do have network connectivity. What makes you think you do not?

To repeat my debugging suggestions:

Can you ping in? Can you ping out? Do you have the iptables firewall turned off?

This is pretty basic networking stuff, and does belong in the newbie forum.

michaeljc70
12-17-2007, 06:06 PM
Route shows:
route_info, afname=inet, options=33
Kernel IP routing table
Destination Gateway Genmask Flags Metric Ref Use Iface

204.176.49.2 localhost.local 255.255.255.255 UGH 0 0 0 lo
192.168.1.0 * 255.255.255.0 U 0 0 0 eth0
204.176.49.0 localhost.local 255.255.255.0 UG 0 0 0 lo

It looks like the gateway is incorrect.

I cannot ping 192.168.1.111. I cannot ping out either. I looked at my router status and it shows attached devices. There are 4 known devices attached, but no Tivo.


I tried running iptables stop, but all I see is in the sbin directory and can see an iptables file, but I don't see an iptables command.

jt1134
12-17-2007, 06:25 PM
iptables -F . Or if you're running 6.2x you could just rename /etc/netfilter-enable.

michaeljc70
12-17-2007, 06:49 PM
iptables -F . Or if you're running 6.2x you could just rename /etc/netfilter-enable.

I actually saw that in a post in my searches and added it to near the top of my rc.sysinit.author. Still no networking.

ScanMan
12-17-2007, 09:22 PM
Route shows:
route_info, afname=inet, options=33
Kernel IP routing table
Destination Gateway Genmask Flags Metric Ref Use Iface

204.176.49.2 localhost.local 255.255.255.255 UGH 0 0 0 lo
192.168.1.0 * 255.255.255.0 U 0 0 0 eth0
204.176.49.0 localhost.local 255.255.255.0 UG 0 0 0 lo

It looks like the gateway is incorrect.

I cannot ping 192.168.1.111. I cannot ping out either. I looked at my router status and it shows attached devices. There are 4 known devices attached, but no Tivo.


I tried running iptables stop, but all I see is in the sbin directory and can see an iptables file, but I don't see an iptables command.

It looks like you don't have a default gateway; you could try to add one:
route add default gw 192.168.1.1 eth0You should be getting this from your router or an ifconfig/route statements in a startup file. Since you're not sure, you might want to post the contents of your 'rc.sysinit.author' file for review.

Jamie
12-17-2007, 11:04 PM
It looks like you don't have a default gateway; you could try to add one:
route add default gw 192.168.1.1 eth0You should be getting this from your router or an ifconfig/route statements in a startup file. Since you're not sure, you might want to post the contents of your 'rc.sysinit.author' file for review.Actually, a default route is unnecessary, unless you want to route to the outside world. He already has a subnet route.

In general, I advice against putting any network config commands in rc.sysinit.author with current software releases, unless you really know what you are doing and understand the interactions with the tivo software network configuration. It's much easier/more foolproof to setup your network settings in MFS using the tivo UI and let the tivo software do all the network configuration.

michaeljc70
12-18-2007, 01:33 AM
Actually, a default route is unnecessary, unless you want to route to the outside world. He already has a subnet route.

In general, I advice against putting any network config commands in rc.sysinit.author with current software releases, unless you really know what you are doing and understand the interactions with the tivo software network configuration. It's much easier/more foolproof to setup your network settings in MFS using the tivo UI and let the tivo software do all the network configuration.

It did work for 2 yrs with no network changes. but if this would be easier, I am willing to try it. I am unsure how to patch though to get the menus. My tvo says it is version 6.2-01-2-381. I am not sure how that relates to 6.2a, 6.2b, etc. to get the right patch.

I am also posting my rc.sysinit.sys here as suggested in the last post. I did recently comment out a few things for debugging (mfs_ftp, tivoweb).

ScanMan
12-18-2007, 01:01 PM
I am also posting my rc.sysinit.sys here as suggested in the last post. I did recently comment out a few things for debugging (mfs_ftp, tivoweb).The only thing I would say is put the 'iptables -F' line before the line that starts telnet (i.e., right after the export lines). Other than that, it looks fine.

Jamie
12-18-2007, 01:31 PM
It did work for 2 yrs with no network changes. but if this would be easier, I am willing to try it. I am unsure how to patch though to get the menus. My tvo says it is version 6.2-01-2-381. I am not sure how that relates to 6.2a, 6.2b, etc. to get the right patch.

I am also posting my rc.sysinit.sys here as suggested in the last post. I did recently comment out a few things for debugging (mfs_ftp, tivoweb).The obvious thing to ask is: if it worked for 2 years with no network changes, what changed that caused it not to work now?

You might want to consult with the author of your "hack it for me" script you used (supported on another site, IIRC) for help.

michaeljc70
12-18-2007, 01:39 PM
The obvious thing to ask is: if it worked for 2 years with no network changes, what changed that caused it not to work now?

You might want to consult with the author of your "hack it for me" script you used (supported on another site, IIRC) for help.

Long story short of what changed is I reinstalled TWP. It still worked fine. Then, I tried to install Hackman modules. When FTPing the files in, there were lots of errors. After rebooting, there was no connectivity. I couldn't delete the files or even ls them (input/output error). I eventually ran e2fsck and was able to delete the files and removed TWP from my startup.

I ran the Western Digital low level diagnostics on the drive. It said there are "too many errors". Even though the Tivo works fine, maybe the drive is on it's last legs? Maybe I should just watch everything and start with a fresh drive? Seems odd that everything works other than networking though....

If I do start from scratch at this point, what/who's method would your recommend? There seems to be 20 different guides/methods in the sticky section and many seem outdated. Can I just image my current drive to a new one or will I be at the same place I am now?

Jamie
12-18-2007, 08:07 PM
Long story short of what changed is I reinstalled TWP. It still worked fine. Then, I tried to install Hackman modules. When FTPing the files in, there were lots of errors. After rebooting, there was no connectivity. I couldn't delete the files or even ls them (input/output error). I eventually ran e2fsck and was able to delete the files and removed TWP from my startup.

I ran the Western Digital low level diagnostics on the drive. It said there are "too many errors". Even though the Tivo works fine, maybe the drive is on it's last legs? Maybe I should just watch everything and start with a fresh drive? Seems odd that everything works other than networking though....

If I do start from scratch at this point, what/who's method would your recommend? There seems to be 20 different guides/methods in the sticky section and many seem outdated. Can I just image my current drive to a new one or will I be at the same place I am now?If your drive is dying, I'd take care of that problem before worrying about networking. Odd that it could fail the WD diagnostic so badly but run mostly okay in your tivo. Makes me wonder if your IDE cable in the PC was flakey.

michaeljc70
12-19-2007, 11:17 AM
If your drive is dying, I'd take care of that problem before worrying about networking. Odd that it could fail the WD diagnostic so badly but run mostly okay in your tivo. Makes me wonder if your IDE cable in the PC was flakey.

Well, looking back, I did notice over the last 2-3 weeks my Now Playing list was very sluggish, sometimes taking 10 seconds to show the text after scrolling.

I bought a new drive (same size) and copied it over (using dd) to eliminate that. The tivo part works fine, but unfortunately, still no connectivity and I am back where I started.

Just to eliminate them, I tested the ethernet cable, router port and USB adapter and all are fine. BTW, the power light is on and the link light blinks when connected to the Tivo. Any other suggestions would be greatly appreciated.