I actually have two issues.

 

Last night I shut down my server to attach new (shorter) sata cables to all drives.  Once done I rebooted and all looked fine.  Shortly afterwards I started copying data from my windows machine to a user share set to only use disk14 - this ran overnight. 

 

First issue: This morning I noticed disk7, disk14 and parity were all spinning while the rest had spun down.  Since the copy was still running I can understand why disk14 and parity were not spun down.  Disk7 is the mystery though.  There was no activity happening with this drive since the server was booted so I can't figure why it was still spinning.  Spindown time is set to 1 hour. 

 

Disk7 will spin down - it's spun down now.  (I stopped the copy and all drives have been inactive for more than an hour).  This one is puzzling me.  Is this possibly something to do with spinup groups?  I'm not sure I understand those yet.

 

Second issue:  Also this moring, while the copy was still taking place and all but the three drives were spun down I heard some brief additional activity from the drives.  I checked the syslog and noticed a bunch of errors.  I've seen these before (or at least ones that looked very similiar if memory server me) but there didn't seem to be any issues so I didn't dig into it.  Now I'd like to figure out what these are.  I found this especially curious since most drives were spun down at the time. 

 

Here is the content of my config/go file in case necessary:

#!/bin/bash
# Start the Management Utility
/usr/local/sbin/emhttp &
PATH=$PATH:/boot/custom/bin
echo "PATH=$PATH" >/root/.profile
cd /boot/packages && find . -name '*.auto_install' -type f -print | sort | xargs -n1 sh -c 
/boot/unmenu/uu
cache_dirs -w -e Pictures
nohup s3.sh &

 

Syslog is attached

Server config in sig

 

Thank you

syslog-2010-03-25.txt

Ok, I think the disk7 spindown issue was definitely related to spinup groups.  I found that it was in the same group as the parity drive.  I just turned off spinup groups as I don't think I need them.  We'll see how this goes.

 

I could still use some help with the syslog errors though

Mar 25 06:10:53 Ruprecht dhcpcd[1595]: sending DHCP_REQUEST for 10.101.1.1 to 10.101.1.30 
Mar 25 06:10:53 Ruprecht dhcpcd[1595]: dhcpIPaddrLeaseTime=86400 in DHCP server response. 
Mar 25 06:10:53 Ruprecht dhcpcd[1595]: dhcpT1value is missing in DHCP server response. Assuming 43200 sec 
Mar 25 06:10:53 Ruprecht dhcpcd[1595]: dhcpT2value is missing in DHCP server response. Assuming 75600 sec 
Mar 25 06:10:53 Ruprecht dhcpcd[1595]: DHCP_ACK received from ÿ (10.101.1.30) 
Mar 25 07:03:18 Ruprecht kernel: ata1: exception Emask 0x10 SAct 0x0 SErr 0x180000 action 0x6 frozen
Mar 25 07:03:18 Ruprecht kernel: ata1: edma_err_cause=00000020 pp_flags=00000000, SError=00180000
Mar 25 07:03:18 Ruprecht kernel: ata1: SError: { 10B8B Dispar }
Mar 25 07:03:18 Ruprecht kernel: ata1: hard resetting link
Mar 25 07:03:18 Ruprecht kernel: ata5: exception Emask 0x10 SAct 0x0 SErr 0x180000 action 0x6 frozen
Mar 25 07:03:18 Ruprecht kernel: ata5: edma_err_cause=00000020 pp_flags=00000000, SError=00180000
Mar 25 07:03:18 Ruprecht kernel: ata5: SError: { 10B8B Dispar }
Mar 25 07:03:18 Ruprecht kernel: ata5: hard resetting link
Mar 25 07:03:18 Ruprecht kernel: ata6: exception Emask 0x10 SAct 0x0 SErr 0x180000 action 0x6 frozen
Mar 25 07:03:18 Ruprecht kernel: ata6: edma_err_cause=00000020 pp_flags=00000000, SError=00180000
Mar 25 07:03:18 Ruprecht kernel: ata6: SError: { 10B8B Dispar }
Mar 25 07:03:18 Ruprecht kernel: ata6: hard resetting link
Mar 25 07:03:18 Ruprecht kernel: ata7: exception Emask 0x10 SAct 0x0 SErr 0x180000 action 0x6 frozen
Mar 25 07:03:18 Ruprecht kernel: ata7: edma_err_cause=00000020 pp_flags=00000000, SError=00180000
Mar 25 07:03:18 Ruprecht kernel: ata7: SError: { 10B8B Dispar }
Mar 25 07:03:18 Ruprecht kernel: ata7: hard resetting link
Mar 25 07:03:18 Ruprecht kernel: ata8: exception Emask 0x10 SAct 0x0 SErr 0x180000 action 0x6 frozen
Mar 25 07:03:18 Ruprecht kernel: ata8: edma_err_cause=00000020 pp_flags=00000000, SError=00180000
Mar 25 07:03:18 Ruprecht kernel: ata8: SError: { 10B8B Dispar }
Mar 25 07:03:18 Ruprecht kernel: ata8: hard resetting link
Mar 25 07:03:19 Ruprecht kernel: ata1: SATA link up 3.0 Gbps (SStatus 123 SControl 300)
Mar 25 07:03:19 Ruprecht kernel: ata5: SATA link up 3.0 Gbps (SStatus 123 SControl 300)
Mar 25 07:03:19 Ruprecht kernel: ata6: SATA link up 3.0 Gbps (SStatus 123 SControl 300)
Mar 25 07:03:19 Ruprecht kernel: ata7: SATA link up 3.0 Gbps (SStatus 123 SControl 300)
Mar 25 07:03:19 Ruprecht kernel: ata8: SATA link up 3.0 Gbps (SStatus 123 SControl 300)
Mar 25 07:03:19 Ruprecht kernel: ata6.00: configured for UDMA/133
Mar 25 07:03:19 Ruprecht kernel: ata6: EH complete
Mar 25 07:03:19 Ruprecht kernel: ata7.00: configured for UDMA/133
Mar 25 07:03:19 Ruprecht kernel: ata7: EH complete
Mar 25 07:03:19 Ruprecht kernel: ata8.00: configured for UDMA/133
Mar 25 07:03:19 Ruprecht kernel: ata8: EH complete
Mar 25 07:03:24 Ruprecht kernel: ata1.00: qc timeout (cmd 0x27)
Mar 25 07:03:24 Ruprecht kernel: ata1.00: failed to read native max address (err_mask=0x4)
Mar 25 07:03:24 Ruprecht kernel: ata1.00: HPA support seems broken, skipping HPA handling
Mar 25 07:03:24 Ruprecht kernel: ata1.00: revalidation failed (errno=-5)
Mar 25 07:03:24 Ruprecht kernel: ata1: hard resetting link
Mar 25 07:03:24 Ruprecht kernel: ata5.00: qc timeout (cmd 0x27)
Mar 25 07:03:24 Ruprecht kernel: ata5.00: failed to read native max address (err_mask=0x4)
Mar 25 07:03:24 Ruprecht kernel: ata5.00: HPA support seems broken, skipping HPA handling
Mar 25 07:03:24 Ruprecht kernel: ata5.00: revalidation failed (errno=-5)
Mar 25 07:03:24 Ruprecht kernel: ata5: hard resetting link
Mar 25 07:03:25 Ruprecht kernel: ata1: SATA link up 3.0 Gbps (SStatus 123 SControl 300)
Mar 25 07:03:25 Ruprecht kernel: ata5: SATA link up 3.0 Gbps (SStatus 123 SControl 300)
Mar 25 07:03:25 Ruprecht kernel: ata1.00: configured for UDMA/133
Mar 25 07:03:25 Ruprecht kernel: ata1: EH complete
Mar 25 07:03:25 Ruprecht kernel: ata5.00: configured for UDMA/133
Mar 25 07:03:25 Ruprecht kernel: ata5: EH complete
Mar 25 07:03:27 Ruprecht kernel: mdcmd (4801): spindown 1
Mar 25 07:03:28 Ruprecht kernel: mdcmd (4802): spindown 2