This issue has been plaguing me for months.  My unraid intermittently drops out either:

 

1.  I cannot mount my share; or

2.  My server mounts the top directory and when I select a subdirectory it hangs; or

3.  I cannot access the webgui.

 

I can go for weeks without issue and then....gone

 

My hardware is as follows (please note my signature below is another box):

 

Motherboard:    ECS| A885GM-A2 (V1.1) 880G AM3 R 

RAID Card:        SUPERMICRO AOC-SASLP-MV8

CPU:                AMD|SEM 145 2.8G AM3 RT 

Memory:          4G RENDITION RM25664BA1339 R

PSU:                Corsair TX750

Version:            5.0-rc5

 

I have changed cables, networks, and switches. No solution.  I can telnet into the box.

 

eth0      Link encap:Ethernet  HWaddr 10:78:d2:1e:82:53 

          inet addr:192.168.1.150  Bcast:192.168.1.255  Mask:255.255.255.0

          UP BROADCAST RUNNING MULTICAST  MTU:1500  Metric:1

          RX packets:728468305 errors:0 dropped:436 overruns:0 frame:0

          TX packets:615069952 errors:0 dropped:0 overruns:0 carrier:0

          collisions:0 txqueuelen:1000

          RX bytes:4036080318 (3.7 GiB)  TX bytes:158035913 (150.7 MiB)

          Interrupt:43 Base address:0x4000

 

Settings for eth0:

Supported ports: [ TP MII ]

Supported link modes:  10baseT/Half 10baseT/Full

                        100baseT/Half 100baseT/Full

                        1000baseT/Half 1000baseT/Full

Supports auto-negotiation: Yes

Advertised link modes:  10baseT/Half 10baseT/Full

                        100baseT/Half 100baseT/Full

                        1000baseT/Half 1000baseT/Full

Advertised pause frame use: Symmetric Receive-only

Advertised auto-negotiation: Yes

Link partner advertised link modes:  10baseT/Half 10baseT/Full

                                    100baseT/Half 100baseT/Full

                                    1000baseT/Full

Link partner advertised pause frame use: Symmetric Receive-only

Link partner advertised auto-negotiation: Yes

Speed: 1000Mb/s

Duplex: Full

Port: MII

PHYAD: 0

Transceiver: internal

Auto-negotiation: on

Supports Wake-on: pumbg

Wake-on: g

Current message level: 0x00000033 (51)

Link detected: yes

 

Am I now forced to an unsafe shut down and hope the issue disappears for a few more weeks?  If a syslog is required, how can I produce it without gui access?

 

 

See Include your VERSION and SYSTEM LOG for support issues  in my sig.

 

5.0- rc5

 

 

Linux 3.0.35-unRAID.

root@Tower:~# tail -f /var/log/syslog

May 29 19:09:32 Tower login[8638]: ROOT LOGIN  on '/dev/pts/0' from '192.168.1.10'

May 29 19:10:12 Tower in.telnetd[8652]: connect from 192.168.1.10 (192.168.1.10)

May 29 19:10:14 Tower login[8653]: invalid password for 'UNKNOWN'  on '/dev/pts/0' from '192.168.1.10'

May 29 19:10:16 Tower login[8653]: ROOT LOGIN  on '/dev/pts/0' from '192.168.1.10'

May 30 11:22:31 Tower in.telnetd[8746]: connect from 192.168.1.10 (192.168.1.10)

May 30 11:22:33 Tower login[8747]: invalid password for 'UNKNOWN'  on '/dev/pts/0' from '192.168.1.10'

May 30 11:22:35 Tower login[8747]: ROOT LOGIN  on '/dev/pts/0' from '192.168.1.10'

May 30 11:25:08 Tower in.telnetd[8761]: connect from 192.168.1.10 (192.168.1.10)

May 30 11:25:09 Tower login[8762]: invalid password for 'UNKNOWN'  on '/dev/pts/0' from '192.168.1.10'

May 30 11:25:11 Tower login[8762]: ROOT LOGIN  on '/dev/pts/0' from '192.168.1.10'

 

5.0- rc5

 

 

Linux 3.0.35-unRAID.

root@Tower:~# tail -f /var/log/syslog

May 29 19:09:32 Tower login[8638]: ROOT LOGIN  on '/dev/pts/0' from '192.168.1.10'

May 29 19:10:12 Tower in.telnetd[8652]: connect from 192.168.1.10 (192.168.1.10)

May 29 19:10:14 Tower login[8653]: invalid password for 'UNKNOWN'  on '/dev/pts/0' from '192.168.1.10'

May 29 19:10:16 Tower login[8653]: ROOT LOGIN  on '/dev/pts/0' from '192.168.1.10'

May 30 11:22:31 Tower in.telnetd[8746]: connect from 192.168.1.10 (192.168.1.10)

May 30 11:22:33 Tower login[8747]: invalid password for 'UNKNOWN'  on '/dev/pts/0' from '192.168.1.10'

May 30 11:22:35 Tower login[8747]: ROOT LOGIN  on '/dev/pts/0' from '192.168.1.10'

May 30 11:25:08 Tower in.telnetd[8761]: connect from 192.168.1.10 (192.168.1.10)

May 30 11:25:09 Tower login[8762]: invalid password for 'UNKNOWN'  on '/dev/pts/0' from '192.168.1.10'

May 30 11:25:11 Tower login[8762]: ROOT LOGIN  on '/dev/pts/0' from '192.168.1.10'

 

You'll need to leave this on until it crashes again. Or use a keyboard and display to copy the syslog to the flash drive after it crashes.

The above is as far as I can get through my telnet connection.

Leave the telnet connection open. The syslog will be saved in the terminal buffer.

Can I restart my server via the power button.  Telnet had been open for hours without any further activity in the terminal.

Are there no more entires in the syslog? The tail command should show all new entries in the syslog in real time. The telnet windows needs to be open during a crash in order to save the syslog. Or if you can access the server using an attached keyboard and display after it crashes then you can copy the syslog to the flash drive.

No more entires.  I shut down and upgraded to rc-12a and will try again after parity check and post telnet activity.