[Cannot Shutdown, hangs of Sync Filesystem]

Hi, I'm pretty new. This is my second thread, and I am still having similar problems from the first thread here.

 

I'll attache some recent Syslogs that are still getting numerous errors.

 

Biggest problems are recently when trying to restart or stop the array (I usually use the GUI, similar when running shutdown from telnet), it hands when saying "Sync Filesystem".  The the only way to restart the system is to hard power off the system and restart.  Then the Parity has to recheck, which takes about 7 hours to do, but doesn't find any errors.

 

This system is still in close to the factory set up shape, having only received this system about 3 weeks ago.  The only real customizations I've done are adding a few packages from unMenu, including Powerdown, Screen, and Mail. In the previous thread, Helmonder suggested rechecking the cabling to my parity drive, which is loaded as "ata1.00: ATA-9: ST4000DM000-1F2168,            Z302NTZJ, CC54, max UDMA/133".  There were no loose cables or anything, still in the factory shipped state

 

These I suspect are relevant error lines from the log:

Apr 15 14:59:05 Orcrist kernel: ata1.00: exception Emask 0x10 SAct 0x0 SErr 0x280100 action 0x6 frozen (Errors)
Apr 15 14:59:05 Orcrist kernel: ata1.00: irq_stat 0x08000000, interface fatal error (Errors)
Apr 15 14:59:05 Orcrist kernel: ata1: SError: { UnrecovData 10B8B BadCRC } (Errors)
Apr 15 14:59:05 Orcrist kernel:         res 50/00:00:df:5e:25/00:00:00:00:00/e0 Emask 0x10 (ATA bus error) (Errors)
Apr 15 15:00:08 Orcrist kernel: ata1.00: exception Emask 0x10 SAct 0x0 SErr 0x280100 action 0x6 frozen (Errors)
Apr 15 15:00:08 Orcrist kernel: ata1.00: irq_stat 0x08000000, interface fatal error (Errors)
Apr 15 15:00:08 Orcrist kernel: ata1: SError: { UnrecovData 10B8B BadCRC } (Errors)
Apr 15 15:00:08 Orcrist kernel:         res 50/00:00:7f:97:2e/00:00:01:00:00/e1 Emask 0x10 (ATA bus error) (Errors)
Apr 15 15:00:55 Orcrist kernel: ata1.00: exception Emask 0x10 SAct 0x0 SErr 0x280100 action 0x6 frozen (Errors)
Apr 15 15:00:55 Orcrist kernel: ata1.00: irq_stat 0x08000000, interface fatal error (Errors)
Apr 15 15:00:55 Orcrist kernel: ata1: SError: { UnrecovData 10B8B BadCRC } (Errors)
Apr 15 15:00:55 Orcrist kernel: ata1.00: exception Emask 0x10 SAct 0x0 SErr 0x280100 action 0x6 frozen (Errors)
Apr 15 15:00:55 Orcrist kernel: ata1.00: irq_stat 0x08000000, interface fatal error (Errors)
Apr 15 15:00:55 Orcrist kernel: ata1: SError: { UnrecovData 10B8B BadCRC } (Errors)
Apr 15 15:00:55 Orcrist kernel:         res 50/00:00:9f:bd:f2/00:00:01:00:00/e1 Emask 0x10 (ATA bus error) (Errors)
Apr 15 15:01:22 Orcrist kernel: ata1.00: exception Emask 0x10 SAct 0x0 SErr 0x280100 action 0x6 frozen (Errors)
Apr 15 15:01:22 Orcrist kernel: ata1.00: irq_stat 0x08000000, interface fatal error (Errors)
Apr 15 15:01:22 Orcrist kernel: ata1: SError: { UnrecovData 10B8B BadCRC } (Errors)
Apr 15 15:01:22 Orcrist kernel:         res 50/00:00:ff:3f:5f/00:00:02:00:00/e2 Emask 0x10 (ATA bus error) (Errors)

 

I'm very new to this, and not great at trouble shooting.  I'm still able to use the shares, though there are very sluggish at times.  Since I keep getting ATA1.00 errors, could this be a faulty drive?

 

syslog-2015-04-15.txt

[Newbie problems: Shares inaccessible and WebGUI not working]

In the syslog, it was referencing this:

Mar 31 17:07:52 Orcrist kernel: ata1.00: ATA-9: ST4000DM000-1F2168,             Z302NTZJ, CC54, max UDMA/133 (Drive related)

I spotted those error lines on ATA1.00.  Does the line mean that this drive is the ATA1.00 drive, which is serial number Z302NTZJ?  Z302NTZJ is my Parity drive.  I was wondering if the error references were to the Parity drive since it had to do a parity check after a reboot. Would that be a normal error message?

root@Orcrist:~# dmesg | grep ata1
ata1: SATA max UDMA/133 abar m2048@0xf7512000 port 0xf7512100 irq 36
ata1: SATA link up 3.0 Gbps (SStatus 123 SControl 300)
ata1.00: ATA-9: ST4000DM000-1F2168,             Z302NTZJ, CC54, max UDMA/133
ata1.00: 7814037168 sectors, multi 16: LBA48 NCQ (depth 31/32), AA
ata1.00: configured for UDMA/133

It looks like those 2 things do correlate, since the command above gave the same drive: Z302NTZJ.

 

It's worth mentioning that after the parity check, I rebooted the server, and there are no error messages in the syslog anymore.  I did take copies of multiple syslogs prior to the reboot.  So could those errors have just been references to the Parity error, since the drive referenced was the parity drive?

[Newbie problems: Shares inaccessible and WebGUI not working]

I must have really screwed something up here.  I just tried to copy to my media share.

 

-It takes a very long time to display the contents

-The transfer (from within windows via SMB shares (mapped)) fails, it did not even attempt it.  Just hangs when I copy and paste.

 

The WebGUI is still working, so I copied syslog from the UnMenu syslog page, I've attached the new one below.

 

I'm so sad.

 

-Edit: does it matter that a parity check is still going from the previous failure when I try to copy the new files.  Can you add files during a parity check?

syslog-2015-03-31.txt

[Newbie problems: Shares inaccessible and WebGUI not working]

So if the cache drive (512gb) is full during a copy, it won't simply copy directly to the regular drives?  Is that something that can be changed?

 

The telnet connection was working, though stopped before I could try to download the syslog.  A reset was done, and I have the syslog.  From what I've read, this is a different syslog. Sorry.

syslog-2015-03-31.txt

[Newbie problems: Shares inaccessible and WebGUI not working]

Hello.

 

I am very new, and you guys probably have heard many of my problems before.  I apologize in advance. I'm am both new to Unraid, and new to Linux environments.

 

I recently purchased a AVS-10/4 Server.  I had it preconfigured with 6 drives (parity plus 5).  Also it has 2x SSD cache drives, 32gb of ram.  I am not currently running any additional applications with it.  The only modifications that I made to the were ones in the Configuration Tutorial, specifically installing Unmenu and Screen, Configuring Mail and SSMTP.

 

I set my shares up as described in the Tutorial.  Then I transfered 12TB of movies/TV shows over.

 

I was ectatic.  Everything was working perfectly.  Very fast.  Responsive.  I was bragging to my friends.

 

Then, I probably screwed something up.

 

I took 3 older 4TB seagate drives (same models that were preconfigured by LimeTech when I ordered, ST4000DM000), and I ran 3 sessions of the preclear script on each drive.  I received no errors, and then added them into the array.  Still everything seemed to be working well.

 

Somewhere in here, occasionally the WebGUI becomes unresponsive (though it seems I can still Putty/Telnet in).  Also, occasionally, my shares seem to randomly go offline.  One additional error was that when transfering a few movie directories (about 50gb of files) to the media share (which has about 15 TB free), it says there is no space available for the transfer.

 

Since I'm so new, I'm not sure where to start and was hoping someone could point me in the right direction.

 

-Did I screw something up?  I added the drives according to the tutorial above

-Did I mis configure my shares somehow? since the SSDs run as cache, maybe they were full, and so I had not enough space there.  But why wouldn't it just right to the platter drives when the SSD was full?

Other?

 

Where can I start? I feel underqualified for this. Are there files that I can attach to this post that would help?