ok, not sure where to start, nor where best to ask this, since although I thought i upgraded my unraid to v5 from the log all i can see is references to v3.

 

Its a HP proliant with 8 gig of ram and a 2tb hard drive

it is used for backups from my laptop, a plex movie server and a logitech music server

it's been running fine for the past year or so, then i go away for a week and find it doesn't respond via the unraid web management page (tower:8080)

at first i thought it was the ethernet that was dead, since it didn't appear on my router, i bought and installed a intel pcie card but still no luck, though it did access the intranet once, but all i did was power down with it.

with a monitor i can log in but my knowledge of what to do next is less than nothing so I don't know where to even start.

 

i have a few syslogs on the flash drive, here are a couple, one is the earliest one from last week when i first rebooted it and this is  what i got just now

 

am happy to rebuild it but am hoping that the hard drive is ok, otherwise it will be a total pita.

thanks in advance

mark

syslog-20141128-200833.zip

syslog_-20141201pm.zip

update, just checked the hard drive and looks like everything is there, phew, shall i just consider replacing the motherboard and ram and start over?

Your syslog has this for your version:

Dec  1 16:08:54 Tower emhttp: unRAID System Management Utility version 5.0-rc16c

 

tower:8080 is normally unMenu, not the default webGUI, which should be just tower or tower:80

 

There is also this

Dec  1 16:07:07 Tower kernel: FAT-fs (sda1): Volume was not properly unmounted. Some data may be corrupt. Please run fsck.

You might try plugging your flash into your PC and running checkdisk.

ah, unmenu rings a bell, but the server doesn't appear on the router (apart from the once), which seems to work just fine and identify everything else i plug into it

 

I just ran checkdisk via the pc and it says the drive is fine

 

forgot to mention, think we had a lightning strike last week , the tv had it's motherboard died last week too, so probably connected

 

thanks for looking at the logs already

hmm, with over a week with no reply, perhaps this wasn't  the best place to ask the question, if thats the case then can anyone point me in the right direction to ask what is almost definitely a hardware problem

Couple of questions:

 

- What happens when you hit http://tower , http://tower:80 or http://ip.address (whatever your router used to assign to your server)

- What happens if you log into the unRAID server console and type ping www.google.com or netstat?

 

Your network situation doesn't look healthy, lots of failed attempts to access files over the internet in your syslogs.

With a little further looking, I think that both Ethernet adapters are getting initialized:

 

Dec  1 16:07:07 Tower kernel: tg3 0000:03:00.0 eth0: Tigon3 [partno(BCM95723) rev 5784100] (PCI Express) MAC address a0:b3:cc:eb:07:a0
Dec  1 16:07:07 Tower kernel: tg3 0000:03:00.0 eth0: attached PHY is 5784 (10/100/1000Base-T Ethernet) (WireSpeed[1], EEE[0])
Dec  1 16:07:07 Tower kernel: tg3 0000:03:00.0 eth0: RXcsums[1] LinkChgREG[0] MIirq[0] ASF[0] TSOcap[1]
Dec  1 16:07:07 Tower kernel: tg3 0000:03:00.0 eth0: dma_rwctrl[76180000] dma_mask[64-bit]
Dec  1 16:07:07 Tower kernel: e1000e 0000:02:00.0 eth1: registered PHC clock
Dec  1 16:07:07 Tower kernel: e1000e 0000:02:00.0 eth1: (PCI Express:2.5GT/s:Width x1) 68:05:ca:2c:a1:f9
Dec  1 16:07:07 Tower kernel: e1000e 0000:02:00.0 eth1: Intel(R) PRO/1000 Network Connection
Dec  1 16:07:07 Tower kernel: e1000e 0000:02:00.0 eth1: MAC: 3, PHY: 8, PBA No: E46981-008

 

But things don't look good after that:

 

Dec  1 16:07:08 Tower logger: SIOCADDRT: Network is unreachable
...
Dec  1 16:07:10 Tower ntpd_intres[1048]: host name not found: pool.ntp.org
...
Dec  1 16:08:09 Tower logger:   /bin/bash /tmp/plugin-prepare ... No network communication !!!
...
Dec  1 16:08:19 Tower logger:  file /boot/config/plugins/plex/pms_48px.png: downloading from http://plex.spidisoft.de/pms_48px.png ... bad download, deleting

 

I'd do some isolation testing.  Pull the new card, and test more with the onboard Ethernet.  Then, go into your BIOS and turn off the onboard Ethernet and put in the new card.  I'd also play around with network cables and ports on your router.  It sounds like you have a problem with the network interface on your server but you need to isolate down to which one - Ethernet, cable, router port, etc.  It's a good idea to pull a syslog for each step.

looks like i have fixed it

well, got it working again anyway

 

i did the sensible thing, also as advised, pulled the board out and pushed and pulled everything to make sure it was all seated properly.

 

i then realised that at some stage when putting the tray in or out the new ethernet card had got pulled out, so carefully re installed that and put everything back together again, booted it up and voila, its all working fine again

 

all i can think of is that the on board ethernet died, perhaps the lightening strike?

 

now it seems to be working, is there any point in any more checking to try to work out why it seemed to die in the first place?

here is todays syslog, looks like there are a few errors in it, are they serious?

syslog-2014-12-09.txt

here are the lines that the syslog identifies as minor issues...

 

Dec  9 18:14:37 Tower kernel: xor: measuring software checksum speed (Minor Issues)

Dec  9 18:14:37 Tower kernel: acpi PNP0A08:00: ignoring host bridge window [mem 0x000d0000-0x000dffff] (conflicts with Adapter ROM [mem 0x000cf000-0x000d19ff]) (Minor Issues)

Dec  9 18:15:26 Tower avahi-daemon[2203]: WARNING: No NSS support for mDNS detected, consider installing nss-mdns! (Minor Issues)

Dec  9 18:17:22 Tower kernel: REISERFS (device md1): replayed 148 transactions in 22 seconds (Minor Issues)

Dec  9 18:17:34 Tower emhttp: shcmd (25): killall -HUP smbd (Minor Issues)

If you can now access the main console over the network I wouldn't worry about those messages (except the REISERFS one).  I would, though, do some precautionary work due to the rather bad uncontrolled shutdown that started the problem.  I.e., pull the USB stick and run a chkdsk on it.  Maybe run reiserfsck on the array drives, and run smart reports.  Finally, run a parity check and recheck smart.

did most of that, everything seems fine, phew