I am on version 4.3.3 right now and all has been running good until the last couple of weeks. I have random problems accessing the server. Sometimes I can browse the files but net get into the web gui. Some times even though I can get into the web gui I can still get into the UnMenu Web GUI. Other times file access will stop when I am browsing files then come back again. Some times telnet won't even work. No mater what I can always Ping the server so I don't think it is a network issue.

 

Guessing I am wondering if I should upgrade and to what version, or if I should try and sort this out first?

 

Attached a syslog. took a few trys to get UnMenu to come up to get it though.

This particular syslog is too recent, does not have all the errors that probably appeared in the previous session, so there is not much I can say for sure.  You definitely had problems, and were unable to shut it down correctly, so numerous transactions had to be replayed on Disk 6.

 

kernel: hdc: WDC WD1200JB-00EVA0, ATA DISK drive

kernel: hdc: host side 80-wire cable detection failed, limiting max speed to UDMA33

kernel: hdc: UDMA/33 mode selected

 

You have one drive with a bad IDE cable, needs to be replaced with a good 80-wire flat ribbon IDE cable.  Since there aren't any drive errors in this syslog, I can't say if it is this drive that is causing all or most of the problems, but at a minimum, it would certainly be slowing some operations way down.

 

If replacing the cable does not resolve the issues, try capturing the syslog when you know you are having major problems but before it crashes completely or becomes totally unresponsive.  You can also start a tail of the syslog on the monitor or in a Telnet session, to see the problems as they unfold.

tail -f --lines=200 /var/log/syslog

I have been having the problems all night and have not restarted it. Finally it all the sudden is working again so I captured the log quickly but it has no new entries at all, it the exact same as the one I posted earlier.

 

I will check the cable. Also is it normal for it to start a parity check when their is a power loss or you shut it down reseting it?

A power loss or a server crash or an improper shutdown are the occasions that are most likely to create parity errors, so yes, it is completely normal for the system to detect an unclean shutdown previously and begin a complete parity check.

OK, this just gets stranger.

 

I can seem to browse through the disks and files with windows explorer no problem. But I am trying to add a movie using My Movies, when it opens the browse window to select where the movie is stored I click on Network and the server show up in the list of network places. But when I try to get into the server it says Windows can not access. After that I can't browse through explorer or get into the web GUI, or telnet it. I can PING it though if that means anything.

 

After a couple minutes it comes back, new log attached

OK, this just gets stranger.

 

I can seem to browse through the disks and files with windows explorer no problem. But I am trying to add a movie using My Movies, when it opens the browse window to select where the movie is stored I click on Network and the server show up in the list of network places. But when I try to get into the server it says Windows can not access. After that I can't browse through explorer or get into the web GUI, or telnet it. I can PING it though if that means anything.

 

After a couple minutes it comes back, new log attached

You are being mis-lead by the successful ping.

You just happened to catch it while the network was up.

 

Your network connection is being lost and restored, and lost again.

Dec  9 21:19:43 Server ifplugd(eth0)[1762]: Link beat lost.

Dec  9 21:19:44 Server kernel: e100: eth0: e100_watchdog: link down

Dec  9 21:19:54 Server ifplugd(eth0)[1762]: Executing '/etc/ifplugd/ifplugd.action eth0 down'.

Dec  9 21:19:54 Server logger: /etc/rc.d/rc.inet1:  /sbin/ifconfig eth0 down

Dec  9 21:19:54 Server ifplugd(eth0)[1762]: Program executed successfully.

Dec  9 21:19:58 Server ifplugd(eth0)[1762]: Link beat detected.

Dec  9 21:19:58 Server kernel: e100: eth0: e100_watchdog: link up, 100Mbps, full-duplex

Dec  9 21:19:59 Server ifplugd(eth0)[1762]: Executing '/etc/ifplugd/ifplugd.action eth0 up'.

Dec  9 21:19:59 Server logger: /etc/rc.d/rc.inet1:  /sbin/ifconfig eth0 hw ether 00:E0:18:7B:40:90

Dec  9 21:19:59 Server logger: /etc/rc.d/rc.inet1:  /sbin/ifconfig eth0 192.168.77.100 broadcast 192.168.77.255 netmask 255.255.255.0

Dec  9 21:19:59 Server logger: /etc/rc.d/rc.inet1:  /sbin/route add default gw 192.168.77.1 metric 1

Dec  9 21:19:59 Server ifplugd(eth0)[1762]: Program executed successfully.

Dec  9 21:22:47 Server ifplugd(eth0)[1762]: Link beat lost.

Dec  9 21:22:48 Server kernel: e100: eth0: e100_watchdog: link down

Dec  9 21:22:49 Server ifplugd(eth0)[1762]: Link beat detected.

Dec  9 21:22:50 Server ifplugd(eth0)[1762]: Link beat lost.

Dec  9 21:22:57 Server ifplugd(eth0)[1762]: Link beat detected.

Dec  9 21:22:58 Server kernel: e100: eth0: e100_watchdog: link up, 100Mbps, full-duplex

You have a loose connection, a bad cable, or a bad router most likely.

Sorry I meant to tell you that that part of the log I unpluged the cable and pluged into a different network line totally to make sure it wasn't the line or port on the switch. I now have it pluged into where my printer normally is.

 

And I deffinately can ping it while I still can't get into the web interface.

Joe beat me!  And said basically the same thing I was going to say.  I'll add one comment.  If you can ping it, then the network is working, even though the host name may not be re-propagated yet.  I suspect that when you can ping it, you can also reach it through the IP address, by web page and Telnet.  Try that.

No it can not be reached by IP address, or name. I normally always pull it up by IP adress and never by name.

 

Right now this morning seems to be working fine. But I am pulling it up from work and not from my home PC, not that it should mater.

 

Checked the log thismorning and nothing new on it.

I was gone for the week end but have been working on this some more, it seems to have some thing to do with the My Movies program.

 

Any time I try and access the server from My Movies I get a "windows cannot access \\SERVER" error. MM is the only program having problems with the server. Also when this happens I can't access my server from anything for 3-5 minutes it is totally gone, no web gui or nothing. Have to close MM and wait then it will suddenly be back and fine. I can rip to and play from the server fine along with using other META programs with it fine it is just My Movies.

 

Nothing show up in the log either. It just seems like window looses the ability to see it. I can ping it from the run prompt and that work just fine.

 

Could some one please look at my last SYS Log. Last night I spun up all the drives which I assume is what the log entries are for DEC 14th @ 21:59. Then after that their is a bunch of stuff and I don't know if it means anything.

Google is your friend.  Nothing looks odd about the syslog other than the series of times were you unplugged the LAN cable.

 

 

Joe L.

And there was a moment when the drive could not be contacted, perhaps because it was spun down, but 10 seconds later, it was recovered without issue.

 

This would be handled better with a newer Linux kernel.  I really think it is time to upgrade to unRAID v4.5.

I will do the upgrade tonight I think. The problems I am having seem to have to do with My Movies and Windows, nothing with unraid. The only thing that I have changed with UnRaid is that I turned off user shares because I don't wan't to use them any more but I wouldn't that that should effect anything.

Ok I upgraded to 4.5 and it didn't help. Actually it seems to be getting worse now. I can't get into the UnRaid web GUI at all but I can get into the UnMenu GUI sometimes then all the sudden it will stop. You can get into browsing files once and a great while. I managed to get TELNET to work long enough to capture a SYSLOG, UnMenu didn't work long enough for me to copy one their. I also eliminated the Switch to make shure that wasn't the issue. Also fired up the laptop and it has the same problems accessing the server. Right now I can seem to TELNET in and browse files from both but can't get any web GUI from either.