Hi,

 

Had a power out yesterday whilst I was at work, when I got home it was 'christmas treeing', i.e. all the drive lights flashing I guess it was checking parity. Anyway, now I can connect and login as root, but nothing I do lets me connect from a Windows browser window?

 

Any ideas?

 

Mark

 

PS It's been working fine for 18 months ..

Any ideas?

No, not really, since you did not post a syslog.

 

Instructions under "troubleshooting" in the wiki.

Any ideas?

No, not really, since you did not post a syslog.

 

Instructions under "troubleshooting" in the wiki.

Fair enough, was panicking a fair bit this morning before heading off to work that I'd lost my 12TB and the world was coming to an end etc.

 

I'll get the syslog when I get home tonight and be in calmer frame of mind.

syslog http://pastebin.com/nw6wMABZ

 

Just noticed I've posted in 4.3 when I'm running 4.5.1. Sorry 

 

 

syslog http://pastebin.com/nw6wMABZ

 

Just noticed I've posted in 4.3 when I'm running 4.5.1. Sorry 

 

 

Nothing looked unusual in the syslog... at least not at first glance.

Have you rebooted your router?

Have you rebooted the "master browser" on your LAN?

 

Joe L.

Thanks for the reply and yup, cold rebooted both. (Used this tool http://scottiestech.info/2009/02/14/how-to-determine-the-master-browser-in-a-windows-workgroup/) Nothing different.

 

One thing I noticed that seems odd, perhaps, is that ifconfig eth0 doesn't give me an IP address. Linux noob so may be nothing.

But you said earlier "Anyway, now I can connect and login as root"

 

From where were you logging in?  On the system console?  or via the LAN?

 

Joe L.

 

 

Via the system console. TOWER isn't visible on the LAN at all.

If Tower is not visible on the LAN Check:

 

That the unraid workgroup is the same as that of your Windows LAN

 

That you can ping the tower by IP address

 

That there are no firewalls on the machine trying to see the tower or that the firewall is allowing 80 and 8080 to pass.

 

If Tower is not visible on the LAN Check:

 

That the unraid workgroup is the same as that of your Windows LAN

 

That you can ping the tower by IP address

 

That there are no firewalls on the machine trying to see the tower or that the firewall is allowing 80 and 8080 to pass.

 

 

I'll check it all out when I get home, but it's been working for years in the same environment right up until the power cut the other day. Also nipped out at lunch and bought a new gigabit NIC just in case the motherboard NIC has somehow been fragged.

Right,

 

Had a good old read of the forums and tried all sorts of things I didn't really understand  then came across a post about the USE_DHCP setting and changed it to the following

 

USE_DHCP=no
IPADDR=192.168.2.110
NETMASK=255.255.255.0
DHCP_KEEPRESOLV=no

 

And BAM, all is good again!

 

Thanks for all your help once again.

That sort of implies that there is something wrong with whatever is serving as the DHCP server.  If other DHCP clients have no issues then all is well and it is/was some sort of a glitch with unraid's linux base. I do not use DHCP assigned address except for my little netbook.  Every other device on the LAN has a fixed IP.  A simple spreadsheet is all I use for manual management.  The netbook actually has both, a wireless and a wired connection with the wired taking precedence..

That sort of implies that there is something wrong with whatever is serving as the DHCP server.  If other DHCP clients have no issues then all is well and it is/was some sort of a glitch with unraid's linux base. I do not use DHCP assigned address except for my little netbook.  Every other device on the LAN has a fixed IP.  A simple spreadsheet is all I use for manual management.  The netbook actually has both, a wireless and a wired connection with the wired taking precedence..

 

That's the strange thing about it, I have two home built PC's, a ASRock 330 XBMC machine, Dell laptop, an XBOX360, a Wii and 2 iPhones that all connect to the network perfectly and only the unRAID box couldn't be seen.