Skip to content
View in the app

A better way to browse. Learn more.

Unraid

A full-screen app on your home screen with push notifications, badges and more.

To install this app on iOS and iPadOS
  1. Tap the Share icon in Safari
  2. Scroll the menu and tap Add to Home Screen.
  3. Tap Add in the top-right corner.
To install this app on Android
  1. Tap the 3-dot menu (⋮) in the top-right corner of the browser.
  2. Tap Add to Home screen or Install app.
  3. Confirm by tapping Install.

Server issues after lightning strike

Featured Replies

Hello,

Last week my neighbors house was struck by lightning, unfortunately my house has suffered some electrical side effects as well with some dead devices; tvs, ps3, etc.  My server is connected to a UPS, but I haven't been able to access it since the lightning storm.  Through various different fact finding missions, I find myself now attempting to boot a trial version of Unraid just to be sure it will boot!  Everything does seem to boot, but I'm still unable to access the server from the Web GUI.  My working theory is that the onboard NIC has died (my network switch the server was connected to died in the storm).  Can someone who is more familiar with Unraid logs have a look at the attached and see if you can confirm my theory?

 

Thanks in advance!

syslog.zip

Been ther, done that! Happened to me a few years back. I even lost individual ports on some switches.

Post the results of

ethtool eth0

and

ifconfig

  • Author

Thanks for the help!  The information you asked for is below.  I also forgot to mention that I have already verified the port on my router and cabling are good by connecting another computer to them which was able to get a connection to the internet.

 

ethtool eth0

Settings for eth0:
Supported ports: [ TP ]
Supported link modes:   10baseT/Half 10baseT/Full 
                        100baseT/Half 100baseT/Full 
                        1000baseT/Full 
Supports auto-negotiation: Yes
Advertised link modes:  10baseT/Half 10baseT/Full 
                        100baseT/Half 100baseT/Full 
                        1000baseT/Full 
Advertised pause frame use: No
Advertised auto-negotiation: Yes
Speed: 100Mb/s
Duplex: Half
Port: Twisted Pair
PHYAD: 0
Transceiver: internal
Auto-negotiation: on
MDI-X: Unknown
Supports Wake-on: pumbg
Wake-on: g
Current message level: 0x00000033 (51)
Link detected: no

 

ifconfig

eth0      Link encap:Ethernet  HWaddr 00:0c:76:ad:f9:18  
          UP BROADCAST MULTICAST  MTU:1500  Metric:1
          RX packets:0 errors:0 dropped:0 overruns:0 frame:0
          TX packets:0 errors:0 dropped:0 overruns:0 carrier:0
          collisions:0 txqueuelen:1000 
          RX bytes:0 (0.0 B)  TX bytes:0 (0.0 B)
          Interrupt:20 Base address:0xe300 

lo        Link encap:Local Loopback  
          inet addr:127.0.0.1  Mask:255.0.0.0
          UP LOOPBACK RUNNING  MTU:65536  Metric:1
          RX packets:8 errors:0 dropped:0 overruns:0 frame:0
          TX packets:8 errors:0 dropped:0 overruns:0 carrier:0
          collisions:0 txqueuelen:0 
          RX bytes:560 (560.0 B)  TX bytes:560 (560.0 B)

Been ther, done that! Happened to me a few years back. I even lost individual ports on some switches.

 

In my case the router got fried and also one port on the patch panel that connected the router to the

landline.

I wouldn't beleave it when the technician told me but he was right.

Then I was even more baffled when he described how he saw entire wall outlets/sockets popped out

and burnt after lightning strike.  :o

  • Author

Just closing the loop on this in case anyone finds this thread and is in a similar situation.  It did turn out to be the NIC that was the issue.  I bought a new NIC, installed it and disabled the onboard NIC.  After this it booted just fine and I'm able to access all drives and shares just like before the storm :).

Archived

This topic is now archived and is closed to further replies.

Account

Navigation

Search

Search

Configure browser push notifications

Chrome (Android)
  1. Tap the lock icon next to the address bar.
  2. Tap Permissions → Notifications.
  3. Adjust your preference.
Chrome (Desktop)
  1. Click the padlock icon in the address bar.
  2. Select Site settings.
  3. Find Notifications and adjust your preference.