Hi, thanks for reading.

 

Although my server has been running for well over a year without problems (until recently), I'm still a noob at Unraid and not tremendously technical.

 

The current problem is that the server freezes about 30 minutes into rebuilding the parity drive (usually around 7% complete). At this point, it won't respond to anything, including not letting me type anything into the command line. I can't get to the syslog at that point, so I've attached the syslog that matches the screen grab.

 

I ran a memtest and found an error, which I was sure was the problem. But the current memory (1 stick of 512MB) tests fine - I'm sure it's not the memory. I'm also pretty sure the system is not overheating. If it came to it, I could change the processor (I have a spare lying around).

 

Is there any chance one of you kind folks could have a quick skim through the syslog attached and perhaps make some suggestions as to how I can get this server going again?

 

Many thanks,

 

Robbie

syslog.txt

Nothing in your syslog strikes me as out of the ordinary, but I'm no expert in that realm.

 

Here's a thought - install the Powerdown package (easy to do via the packages page if you already use unMenu).  This will automatically save a syslog to your flash drive whenever you press the power button on the server to shut it down.  Hopefully this will work to capture a syslog the next time your server freezes.

See this post by Tom on how to capture a system log for a crashing server.

 

http://lime-technology.com/forum/index.php?topic=9040.msg86637#msg86637

 

 

Thanks for the suggestions. I followed the link suggested by ohlwiler and got the following error as the system froze. After searching the forum, I noticed a few people with similar errors were being advised to check the SATA cabling and seating of the controller cards. After doing this, the server is now not seeing 2 of the SATA drives attached the PCI controller card! So I guess my first port of call is to replace the card and try again, I shall let you know how it goes.

 

Thanks for the help.

 

Robbie

Nov 24 02:23:44 Tower kernel: ata1: hard resetting link
Nov 24 02:23:44 Tower kernel: ata1: SATA link up 1.5 Gbps (SStatus 113 SControl
310)
Nov 24 02:23:44 Tower kernel: ata1.00: configured for UDMA/33
Nov 24 02:23:44 Tower kernel: ata1: EH complete
Nov 24 02:23:44 Tower kernel: sd 1:0:0:0: [sda] 1953525168 512-byte hardware sec
tors (1000205 MB)
Nov 24 02:23:44 Tower kernel: sd 1:0:0:0: [sda] Write Protect is off
Nov 24 02:23:44 Tower kernel: sd 1:0:0:0: [sda] Mode Sense: 00 3a 00 00
Nov 24 02:23:44 Tower kernel: sd 1:0:0:0: [sda] Write cache: enabled, read cache
: enabled, doesn't support DPO or FUA
Nov 24 02:23:45 Tower kernel: ata1.00: exception Emask 0x12 SAct 0x0 SErr 0x1380
500 action 0x6
Nov 24 02:23:45 Tower kernel: ata1.00: BMDMA stat 0x5
Nov 24 02:23:45 Tower kernel: ata1: SError: { UnrecovData Proto 10B8B Dispar Bad
CRC TrStaTrns }
Nov 24 02:23:45 Tower kernel: ata1.00: cmd 25/00:00:e7:fa:06/00:04:09:00:00/e0 t
ag 0 dma 524288 in
Nov 24 02:23:45 Tower kernel:          res 51/84:4f:98:fe:06/84:00:09:00:00/e0 E
mask 0x12 (ATA bus error)
Nov 24 02:23:45 Tower kernel: ata1.00: status: { DRDY ERR }
Nov 24 02:23:45 Tower kernel: ata1.00: error: { ICRC ABRT }
Nov 24 02:23:45 Tower kernel: ata1: hard resetting link

 

Thanks again for the help, the problem is now (almost) sorted.

 

It was indeed a failing SATA controller card. It completely died after my last post. A quick swap with a new card, and all is working again, parity sync complete.

 

However, I do have a new issue to do with accessing the tower through Windows Explorer on a particular PC. This was working ok before these problems, and I'm not too sure what is now different. I've read a good few threads on this forum and have followed some advice, but cannot explore the shares at all from the PC. Here's a quick summary of where I'm at right now:

 

- I can browse to \\tower\ through Explorer from other PCs on the network

- tower is on 192.168.2.107 and the webgui is accessible from the PC

- ifconfig on the tower gives me inet addr:192.168.2.107 Bcast:192.168.2.255 Mask:255.255.255.0

- ipconfig on the PC is IP:192.168.2.110 Subnet:255.255.255.0 Gateway:192.168.2.1

- ping 192.168.0.7 works fine from the PC

- ping tower works find from PC (I have manually added the address to the hosts file)

- Both tower and PC are in the same workgroup

- I've rebooted both several times

- Browsing to \\tower\ in Explorer times out with a Windows cannot find '\\tower\' error

 

Would it have something to do with DNS on the router or the PC? I'm not fully up to speed with networking yet, but learning fast!

 

Thanks once more.

 

Robbie