flaggart

OK, so how do I shutdown safely and reboot?

Web interface stopped working.. Followed instructions to restart it.. root@BIGBOX:~# killall emhttp emhttp: no process found root@BIGBOX:~# nohup /usr/local/sbin/emhttp & [1] 2669 root@BIGBOX:~# nohup: ignoring input and appending output to ‘nohup.out’ But it is still not working. Any ideas? It seems to segfault very quickly. Mar 27 20:42:39 BIGBOX kernel: emhttp[4774]: segfault at 0 ip 00002acba9c50c3b sp 00007fffa41c2b48 error 4 in libc-2.17.so[2acba9b18000+1bf000] Mar 28 10:54:00 BIGBOX kernel: emhttp[722]: segfault at 0 ip 00002b45dcc3ed16 sp 00007fff8efa17b8 error 4 in libc-2.17.so[2b45dcb08000+1bf000] Mar 28 10:55:58 BIGBOX kernel: emhttp[2669]: segfault at 0 ip 00002b3547d8ed16 sp 00007fff6e7c1608 error 4 in libc-2.17.so[2b3547c58000+1bf000] Full log after restarting it: Mar 28 20:56:36 BIGBOX emhttp: unRAID System Management Utility version 6.0-beta14b Mar 28 20:56:36 BIGBOX emhttp: Copyright (C) 2005-2015, Lime Technology, Inc. Mar 28 20:56:36 BIGBOX emhttp: shcmd (1): mkdir -p /boot/config/plugins/dynamix Mar 28 20:56:36 BIGBOX emhttp: shcmd (2): mkdir -p /boot/config/shares Mar 28 20:56:36 BIGBOX emhttp: shcmd (4): :>/etc/samba/smb-shares.conf Mar 28 20:56:36 BIGBOX avahi-daemon[4841]: Files changed, reloading. Mar 28 20:56:36 BIGBOX emhttp: Restart SMB... Mar 28 20:56:36 BIGBOX emhttp: shcmd (5): killall -HUP smbd Mar 28 20:56:36 BIGBOX emhttp: shcmd (6): cp /etc/avahi/services/smb.service- /etc/avahi/services/smb.service Mar 28 20:56:36 BIGBOX avahi-daemon[4841]: Files changed, reloading. Mar 28 20:56:36 BIGBOX avahi-daemon[4841]: Service group file /services/smb.service changed, reloading. Mar 28 20:56:36 BIGBOX emhttp: shcmd (7): pidof rpc.mountd &> /dev/null Mar 28 20:56:36 BIGBOX emhttp: shcmd (: /etc/rc.d/rc.atalk status Mar 28 20:56:36 BIGBOX emhttp: startArray not found Mar 28 20:56:36 BIGBOX kernel: emhttp[3002]: segfault at 0 ip 00002b712baded16 sp 00007fffe7f05038 error 4 in libc-2.17.so[2b712b9a8000+1bf000] Mar 28 20:56:37 BIGBOX avahi-daemon[4841]: Service "BIGBOX" (/services/smb.service) successfully established.

Small, but not sure it is really needed in Node 804. The drives are above the PSU and there is a fair amount of space for cabling beneath them, behind the PSU.

Thanks, this has increased the speed by perhaps 50% which makes it slightly more bearable! Still nothing like the speed it should be however.

Here is the graph with 4x3TB on motherboard, 3x4TB and 5x2TB on Supermicro

Fine on LAN, dog slow outside

It seems that accessing guac from a proxy is much much slower (in fact I can't actually connect to a machine before it times out) so I have gone back to accessing it directly via port, which works fine. Do you have the same issue?

The speed did indeed jump from ~40MB/sec to ~95MB/sec (about 600MB/sec according to disk graph) after the 2TB drives had finished. However, I think this is more likely down to the fact that at this point in the operation, 4 drives are now on the motherboard SATA ports, and three drives including parity are on the Supermicro card. Either the 2TB drives are very slow at reading as you suggest, or the Supermicro card is the bottleneck, and the bottleneck is no longer a factor with only 3 active drives. I will perform individual speed tests on each drive when parity has completed, but my money is still on the Supermicro card. It still took 15 hours to complete the first 2TB of parity check and I think this is too much when the hardware should be capable of much quicker.

I have now moved the 4x3TB drives to motherboard, with the remainder on the Supermicro. Restarted parity and it is still maxing out at just under 512MB/sec according to disk stats graph, and ~40MB/sec "Estimated speed" on the Main tab. I'll post a full graph in an estimated 28 hours time (!)

This doesn't seem to indicate any bottleneck => you've only got 3 4TB drives, so you're getting about 117MB/s speeds for the final TB of your parity check. Seems about right for the final TB of a 4TB unit -- remember that at this point they're moving towards the innermost (slowest) cylinders. This is when the bottleneck had gone. The graph shows the bottleneck was at ~450MB/sec. With just the 4TB drives left there was no bottleneck. The Supermicro card should be able to provide up to 6 Gigabit per port, but it can't even do that _combined_ across all 8 drives!

Can you confirm what speed the card links at, and the maximum speeds the disk usage graph displays during parity?

I get what you are saying, but my expectation is that this card has a higher maximum throughput than 5 gigabit. It advertises that each of its 8 ports is "up to 6 gigabit" and is connected with a PCI-E 8x interface which is capable of much more than we are seeing. If 5 gigabit is the true maximum speed of this card then it is false advertising as not even a single drive can reach the maximum stated throughput. It would be like an ISP selling me a gigabit internet connection when their link further upstream is only 10mbit. I would appreciate if someone could confirm that the syslog is indicating it is linked at only 5 gigabit. Can someone with another PCI-E x8 card post what their card links at?

Hi all, Sorry to revive an old thread but I have the same issue with this card in unraid 6.0b14b and wondered if there is a definitive answer? http://lime-technology.com/forum/index.php?topic=38873.0

Hello, Sorry to revive this old thread but I have similar confusion with a newer model of this card and would appreciate advice. http://lime-technology.com/forum/index.php?topic=38873.0

I'm currently running a parity sync and the behaviour seems a little odd.. Initially sync was slow at 30-40MB/sec, but as the smaller 2TB drives finished, it increased.. and then increased again to 100-120MB/sec once the 3TB drives had finished and only the 4TB drives were left to complete. Up until the 3TB drives finished, the disk read stats graph indicated the total throughput was around 450MB/sec. When left with just the 4TB drives, the stats graph showed a drop to ~350MB/sec. 8 drives are connected to a Supermicro AOC-SAS2LP-MV8 in a PCIe 2.0 x8 slot which should be capable of 32 Gigabit/sec (e.g. 4GB/sec or 500MB/sec per drive). The remaining 4 drives are connected to SATA 3 6Gbit ports on an ASRock FM2A75M-ITX. The AOC-SAS2LP-MV8 reports it is linked at "5Gbps" during boot. Given PCI-e 8/10bit overheads this perhaps means "4Gbps" real world. I had assumed this must have meant GigaBYTE but is it in fact linked at only 5 Gigabit?? This would explain the bottleneck.. Syslog says: kernel: mvsas 0000:01:00.0: mvsas: PCI-E x8, Bandwidth Usage: 5.0 Gbps Obviously the system is not capable of reading data at more than 450MB/sec (just under 4gigabit per sec).. but my question is, why is this the case? Can anyone clarify what the "5.0 Gbps" in syslog refers to? Should the card be linking at a higher speed?

I have guacamole docker installed and listening on port 81. Here is my proxy-config.conf: <Location /guac> ProxyPass http://192.168.0.3:81 ProxyPassReverse http://192.168.0.3:81 </Location> It is then available from http://yourdomain.com/guac/'>http://yourdomain.com/guac/ Note that http://yourdomain.com/guac just loads a blank page

The web interface is what I am more interested in.. it is not a standard part of Quassel

Quassel (http://quassel-irc.org/) is a distributed IRC client - the quassel-core installs on a server and maintains connections to IRC servers, then quassel-client connects to it, so that you are always on IRC. This would be perfect for unRAID using docker! There is even a web based quassel-client - https://www.npmjs.com/package/quassel-webserver

Thanks. The problem was that I could not browse without a working mouse! It seems it it because I have a touchscreen monitor - https://groups.google.com/forum/#!topic/novnc/bOpKeuZCd7s Perhaps this patch could be included?

Hello, I have a few issues getting this to work 1) After creating a Windows VM for Server 2012, the installation does not detect any hard drives, so I can't install an OS 2) I cant control the VM using a mouse via VNC Here is the XML for the VM that was created: <domain type='kvm' id='2'> <name>test4</name> <uuid>affa8055-de6d-b2b6-3b86-0fba4593f540</uuid> <memory unit='KiB'>2097152</memory> <currentMemory unit='KiB'>1048576</currentMemory> <vcpu placement='static'>1</vcpu> <resource> <partition>/machine</partition> </resource> <os> <type arch='x86_64' machine='pc-i440fx-2.1'>hvm</type> <boot dev='cdrom'/> <boot dev='hd'/> </os> <features> <acpi/> <apic/> <hyperv> <relaxed state='on'/> <vapic state='on'/> <spinlocks state='on' retries='8191'/> </hyperv> </features> <clock offset='localtime'> <timer name='hypervclock' present='yes'/> <timer name='hpet' present='no'/> </clock> <on_poweroff>destroy</on_poweroff> <on_reboot>restart</on_reboot> <on_crash>restart</on_crash> <devices> <emulator>/usr/bin/qemu-system-x86_64</emulator> <disk type='file' device='disk'> <driver name='qemu' type='raw'/> <source file='/mnt/cache/vm/test4/test4.img'/> <backingStore/> <target dev='hda' bus='virtio'/> <alias name='virtio-disk0'/> <address type='pci' domain='0x0000' bus='0x00' slot='0x04' function='0x0'/> </disk> <disk type='file' device='cdrom'> <driver name='qemu' type='raw'/> <source file='/mnt/user/iso/apps/Microsoft.Windows.Server.2012.R2/servr2.iso'/> <backingStore/> <target dev='hdc' bus='ide'/> <readonly/> <alias name='ide0-1-0'/> <address type='drive' controller='0' bus='1' target='0' unit='0'/> </disk> <disk type='file' device='cdrom'> <driver name='qemu' type='raw'/> <source file='/mnt/cache/vm/virtio-win-0.1-100.iso'/> <backingStore/> <target dev='hdd' bus='ide'/> <readonly/> <alias name='ide0-1-1'/> <address type='drive' controller='0' bus='1' target='0' unit='1'/> </disk> <controller type='usb' index='0'> <alias name='usb0'/> <address type='pci' domain='0x0000' bus='0x00' slot='0x01' function='0x2'/> </controller> <controller type='pci' index='0' model='pci-root'> <alias name='pci.0'/> </controller> <controller type='ide' index='0'> <alias name='ide0'/> <address type='pci' domain='0x0000' bus='0x00' slot='0x01' function='0x1'/> </controller> <interface type='bridge'> <mac address='52:54:00:9f:30:be'/> <source bridge='br0'/> <target dev='vnet0'/> <model type='virtio'/> <alias name='net0'/> <address type='pci' domain='0x0000' bus='0x00' slot='0x03' function='0x0'/> </interface> <serial type='pty'> <source path='/dev/pts/0'/> <target port='0'/> <alias name='serial0'/> </serial> <console type='pty' tty='/dev/pts/0'> <source path='/dev/pts/0'/> <target type='serial' port='0'/> <alias name='serial0'/> </console> <input type='tablet' bus='usb'> <alias name='input0'/> </input> <input type='mouse' bus='ps2'/> <input type='keyboard' bus='ps2'/> <graphics type='vnc' port='5900' autoport='yes' websocket='5700' listen='0.0.0.0'> <listen type='address' address='0.0.0.0'/> </graphics> <video> <model type='vmvga' vram='16384' heads='1'/> <alias name='video0'/> <address type='pci' domain='0x0000' bus='0x00' slot='0x02' function='0x0'/> </video> <memballoon model='virtio'> <alias name='balloon0'/> <address type='pci' domain='0x0000' bus='0x00' slot='0x05' function='0x0'/> </memballoon> </devices> </domain>

Unfortunately the NewerTech G5 3-drive bay is a few mm too tall which means it will not fit in the main chamber beneath the controller card. So realistically all I can do is fit two more drives in the drive chamber using another OWC multimount - that would mean 13 data + parity + cache. Still not too shabby for such a tiny box!

root@BIGBOX:~# smartctl -a -A /dev/sdh smartctl 6.2 2013-07-26 r3841 [i686-linux-3.9.11p-unRAID] (local build) Copyright (C) 2002-13, Bruce Allen, Christian Franke, www.smartmontools.org === START OF INFORMATION SECTION === Model Family: Western Digital Caviar Green Device Model: WDC WD20EADS-00R6B0 Serial Number: WD-WCAVY1187400 LU WWN Device Id: 5 0014ee 2ae3ff9f8 Firmware Version: 01.00A01 User Capacity: 2,000,398,934,016 bytes [2.00 TB] Sector Size: 512 bytes logical/physical Device is: In smartctl database [for details use: -P show] ATA Version is: ATA8-ACS (minor revision not indicated) SATA Version is: SATA 2.6, 3.0 Gb/s Local Time is: Sun Mar 15 12:51:26 2015 GMT SMART support is: Available - device has SMART capability. SMART support is: Enabled === START OF READ SMART DATA SECTION === SMART overall-health self-assessment test result: PASSED General SMART Values: Offline data collection status: (0x84) Offline data collection activity was suspended by an interrupting command from host. Auto Offline Data Collection: Enabled. Self-test execution status: ( 0) The previous self-test routine completed without error or no self-test has ever been run. Total time to complete Offline data collection: (41580) seconds. Offline data collection capabilities: (0x7b) SMART execute Offline immediate. Auto Offline data collection on/off support. Suspend Offline collection upon new command. Offline surface scan supported. Self-test supported. Conveyance Self-test supported. Selective Self-test supported. SMART capabilities: (0x0003) Saves SMART data before entering power-saving mode. Supports SMART auto save timer. Error logging capability: (0x01) Error logging supported. General Purpose Logging supported. Short self-test routine recommended polling time: ( 2) minutes. Extended self-test routine recommended polling time: ( 473) minutes. Conveyance self-test routine recommended polling time: ( 5) minutes. SCT capabilities: (0x303f) SCT Status supported. SCT Error Recovery Control supported. SCT Feature Control supported. SCT Data Table supported. SMART Attributes Data Structure revision number: 16 Vendor Specific SMART Attributes with Thresholds: ID# ATTRIBUTE_NAME FLAG VALUE WORST THRESH TYPE UPDATED WHEN_FAILED RAW_VALUE 1 Raw_Read_Error_Rate 0x002f 200 200 051 Pre-fail Always - 0 3 Spin_Up_Time 0x0027 149 147 021 Pre-fail Always - 9508 4 Start_Stop_Count 0x0032 099 099 000 Old_age Always - 1637 5 Reallocated_Sector_Ct 0x0033 200 200 140 Pre-fail Always - 0 7 Seek_Error_Rate 0x002e 200 200 000 Old_age Always - 0 9 Power_On_Hours 0x0032 077 077 000 Old_age Always - 16822 10 Spin_Retry_Count 0x0032 100 100 000 Old_age Always - 0 11 Calibration_Retry_Count 0x0032 100 100 000 Old_age Always - 0 12 Power_Cycle_Count 0x0032 100 100 000 Old_age Always - 481 192 Power-Off_Retract_Count 0x0032 200 200 000 Old_age Always - 75 193 Load_Cycle_Count 0x0032 194 194 000 Old_age Always - 18501 194 Temperature_Celsius 0x0022 121 102 000 Old_age Always - 31 196 Reallocated_Event_Count 0x0032 200 200 000 Old_age Always - 0 197 Current_Pending_Sector 0x0032 200 200 000 Old_age Always - 0 198 Offline_Uncorrectable 0x0030 200 200 000 Old_age Offline - 0 199 UDMA_CRC_Error_Count 0x0032 200 200 000 Old_age Always - 0 200 Multi_Zone_Error_Rate 0x0008 200 200 000 Old_age Offline - 0 SMART Error Log Version: 1 No Errors Logged SMART Self-test log structure revision number 1 Num Test_Description Status Remaining LifeTime(hours) LBA_of_first_error # 1 Extended offline Completed without error 00% 16812 - # 2 Short offline Completed without error 00% 16800 - # 3 Short captive Completed without error 00% 24 - SMART Selective self-test log data structure revision number 1 SPAN MIN_LBA MAX_LBA CURRENT_TEST_STATUS 1 0 0 Not_testing 2 0 0 Not_testing 3 0 0 Not_testing 4 0 0 Not_testing 5 0 0 Not_testing Selective self-test flags (0x0): After scanning selected spans, do NOT read-scan remainder of disk. If Selective self-test is pending on power-up, resume after 0 minute delay.

I ran an extended SMART test from unRAID gui on drive 10. Not sure if there is a log for that, but the GUI reports no errors: Num Test Description Status Remaining LifeTime(hours) LBA of first error 1 Extended offline Completed without error 00% 16812 None 2 Short offline Completed without error 00% 16800 None 3 Short captive Completed without error 00% 24 None

The console log is verbatim. With regards to having removed the drive, connected to another PC etc, I think this step was totally unnecessary. I was unaware of the procedure to re-enable a disabled device. The drive red-balled at the exact same moment as I ran HDSentinal so it would be an amazing coincidence if a cable became loose! Data has finished rebuilding and all seems OK. Here is the syslog in case anyone is interested: Mar 13 21:34:00 BIGBOX in.telnetd[24059]: connect from 192.168.0.10 (192.168.0.10) Mar 13 21:34:03 BIGBOX login[24060]: ROOT LOGIN on '/dev/pts/0' from 'FRACTAL.home.net' Mar 13 21:34:53 BIGBOX s3_sleep: Disk activity detected. Reset all counters. /dev/sde drive state is: active/idle Mar 13 21:35:54 BIGBOX s3_sleep: Disk activity detected. Reset all counters. /dev/sde drive state is: active/idle Mar 13 21:36:58 BIGBOX s3_sleep: Disk activity detected. Reset all counters. /dev/sdb drive state is: active/idle /dev/sdc drive state is: active/idle /dev/sdd drive state is: active/idle /dev/sde drive state is: active/idle Mar 13 21:37:17 BIGBOX kernel: sd 2:0:1:0: command f7250600 timed out Mar 13 21:37:17 BIGBOX kernel: sas: Enter sas_scsi_recover_host busy: 1 failed: 1 Mar 13 21:37:17 BIGBOX kernel: sas: trying to find task 0xe2b1d900 Mar 13 21:37:17 BIGBOX kernel: sas: sas_scsi_find_task: aborting task 0xe2b1d900 Mar 13 21:37:17 BIGBOX kernel: sas: sas_scsi_find_task: task 0xe2b1d900 is aborted Mar 13 21:37:17 BIGBOX kernel: sas: sas_eh_handle_sas_errors: task 0xe2b1d900 is aborted Mar 13 21:37:17 BIGBOX kernel: sas: ata8: end_device-2:1: cmd error handler Mar 13 21:37:17 BIGBOX kernel: sas: ata7: end_device-2:0: dev error handler Mar 13 21:37:17 BIGBOX kernel: sas: ata8: end_device-2:1: dev error handler Mar 13 21:37:17 BIGBOX kernel: ata8.00: exception Emask 0x0 SAct 0x0 SErr 0x0 action 0x6 frozen Mar 13 21:37:17 BIGBOX kernel: ata8.00: failed command: SMART Mar 13 21:37:17 BIGBOX kernel: ata8.00: cmd b0/d8:00:01:4f:c2/00:00:00:00:00/00 tag 0 Mar 13 21:37:17 BIGBOX kernel: res 40/00:00:00:4f:c2/00:00:00:00:00/00 Emask 0x4 (timeout) Mar 13 21:37:17 BIGBOX kernel: ata8.00: status: { DRDY } Mar 13 21:37:17 BIGBOX kernel: ata8: hard resetting link Mar 13 21:37:17 BIGBOX kernel: sas: ata9: end_device-2:2: dev error handler Mar 13 21:37:17 BIGBOX kernel: sas: ata10: end_device-2:3: dev error handler Mar 13 21:37:17 BIGBOX kernel: sas: ata11: end_device-2:4: dev error handler Mar 13 21:37:17 BIGBOX kernel: sas: ata12: end_device-2:5: dev error handler Mar 13 21:37:17 BIGBOX kernel: sas: ata13: end_device-2:6: dev error handler Mar 13 21:37:17 BIGBOX kernel: sas: ata14: end_device-2:7: dev error handler Mar 13 21:37:17 BIGBOX kernel: sas: sas_form_port: phy1 belongs to port1 already(1)! Mar 13 21:37:19 BIGBOX kernel: drivers/scsi/mvsas/mv_sas.c 1527:mvs_I_T_nexus_reset for device[1]:rc= 0 Mar 13 21:37:25 BIGBOX kernel: ata8.00: qc timeout (cmd 0x27) Mar 13 21:37:25 BIGBOX kernel: ata8.00: failed to read native max address (err_mask=0x4) Mar 13 21:37:25 BIGBOX kernel: ata8.00: HPA support seems broken, skipping HPA handling Mar 13 21:37:25 BIGBOX kernel: ata8.00: revalidation failed (errno=-5) Mar 13 21:37:25 BIGBOX kernel: ata8: hard resetting link Mar 13 21:37:25 BIGBOX kernel: sas: sas_form_port: phy1 belongs to port1 already(1)! Mar 13 21:37:27 BIGBOX kernel: drivers/scsi/mvsas/mv_sas.c 1527:mvs_I_T_nexus_reset for device[1]:rc= 0 Mar 13 21:37:32 BIGBOX kernel: ata8.00: qc timeout (cmd 0xef) Mar 13 21:37:32 BIGBOX kernel: ata8.00: failed to set xfermode (err_mask=0x4) Mar 13 21:37:32 BIGBOX kernel: ata8.00: limiting speed to UDMA/133:PIO3 Mar 13 21:37:32 BIGBOX kernel: ata8: hard resetting link Mar 13 21:37:32 BIGBOX kernel: sas: sas_form_port: phy1 belongs to port1 already(1)! Mar 13 21:37:34 BIGBOX kernel: drivers/scsi/mvsas/mv_sas.c 1527:mvs_I_T_nexus_reset for device[1]:rc= 0 Mar 13 21:37:44 BIGBOX kernel: ata8.00: qc timeout (cmd 0xef) Mar 13 21:37:44 BIGBOX kernel: ata8.00: failed to set xfermode (err_mask=0x4) Mar 13 21:37:44 BIGBOX kernel: ata8.00: disabled Mar 13 21:37:44 BIGBOX kernel: ata8: hard resetting link Mar 13 21:37:45 BIGBOX kernel: sas: sas_form_port: phy1 belongs to port1 already(1)! Mar 13 21:37:47 BIGBOX kernel: drivers/scsi/mvsas/mv_sas.c 1527:mvs_I_T_nexus_reset for device[1]:rc= 0 Mar 13 21:37:47 BIGBOX kernel: ata8: EH complete Mar 13 21:37:47 BIGBOX kernel: sas: --- Exit sas_scsi_recover_host: busy: 0 failed: 0 tries: 1 Mar 13 21:37:47 BIGBOX kernel: sd 2:0:1:0: [sdh] READ CAPACITY(16) failed Mar 13 21:37:47 BIGBOX kernel: sd 2:0:1:0: [sdh] Mar 13 21:37:47 BIGBOX kernel: Result: hostbyte=0x04 driverbyte=0x00 Mar 13 21:37:47 BIGBOX kernel: sd 2:0:1:0: [sdh] Sense not available. Mar 13 21:37:47 BIGBOX kernel: sd 2:0:1:0: [sdh] READ CAPACITY failed Mar 13 21:37:47 BIGBOX kernel: sd 2:0:1:0: [sdh] Mar 13 21:37:47 BIGBOX kernel: Result: hostbyte=0x04 driverbyte=0x00 Mar 13 21:37:47 BIGBOX kernel: sd 2:0:1:0: [sdh] Sense not available. Mar 13 21:37:47 BIGBOX kernel: sd 2:0:1:0: [sdh] Truncating mode parameter data from 3330 to 512 bytes Mar 13 21:37:47 BIGBOX kernel: sd 2:0:1:0: [sdh] Got wrong page Mar 13 21:37:47 BIGBOX kernel: sd 2:0:1:0: [sdh] Assuming drive cache: write through Mar 13 21:37:47 BIGBOX kernel: sdh: detected capacity change from 2000398934016 to 0 Mar 13 21:37:48 BIGBOX kernel: program smartctl is using a deprecated SCSI ioctl, please convert it to SG_IO Mar 13 21:38:03 BIGBOX last message repeated 14 times Mar 13 21:38:10 BIGBOX s3_sleep: Disk activity detected. Reset all counters. /dev/sdb drive state is: active/idle /dev/sdc drive state is: active/idle /dev/sdd drive state is: active/idle /dev/sde drive state is: active/idle /dev/sdg drive state is: active/idle /dev/sdi drive state is: active/idle /dev/sdj drive state is: active/idle /dev/sdk drive state is: active/idle Mar 13 21:38:11 BIGBOX kernel: program smartctl is using a deprecated SCSI ioctl, please convert it to SG_IO Mar 13 21:38:56 BIGBOX last message repeated 32 times Mar 13 21:38:59 BIGBOX last message repeated 9 times Mar 13 21:39:11 BIGBOX s3_sleep: Disk activity detected. Reset all counters. /dev/sdb drive state is: active/idle /dev/sdc drive state is: active/idle /dev/sdd drive state is: active/idle /dev/sde drive state is: active/idle /dev/sdg drive state is: active/idle /dev/sdi drive state is: active/idle /dev/sdj drive state is: active/idle /dev/sdk drive state is: active/idle /dev/sdl drive state is: active/idle /dev/sdm drive state is: active/idle /dev/sdn drive state is: active/idle Mar 13 21:40:11 BIGBOX s3_sleep: Disk activity detected. Reset all counters. /dev/sdb drive state is: active/idle /dev/sdc drive state is: active/idle /dev/sdd drive state is: active/idle /dev/sde drive state is: active/idle /dev/sdg drive state is: active/idle /dev/sdi drive state is: active/idle /dev/sdj drive state is: active/idle /dev/sdk drive state is: active/idle /dev/sdl drive state is: active/idle /dev/sdm drive state is: active/idle /dev/sdn drive state is: active/idle Mar 13 21:41:11 BIGBOX s3_sleep: Disk activity detected. Reset all counters. /dev/sdb drive state is: active/idle /dev/sdc drive state is: active/idle /dev/sdd drive state is: active/idle /dev/sde drive state is: active/idle /dev/sdg drive state is: active/idle /dev/sdi drive state is: active/idle /dev/sdj drive state is: active/idle /dev/sdk drive state is: active/idle /dev/sdl drive state is: active/idle /dev/sdm drive state is: active/idle /dev/sdn drive state is: active/idle Mar 13 21:42:11 BIGBOX s3_sleep: Disk activity detected. Reset all counters. /dev/sdb drive state is: active/idle /dev/sdc drive state is: active/idle /dev/sdd drive state is: active/idle /dev/sde drive state is: active/idle /dev/sdg drive state is: active/idle /dev/sdi drive state is: active/idle /dev/sdj drive state is: active/idle /dev/sdk drive state is: active/idle /dev/sdl drive state is: active/idle /dev/sdm drive state is: active/idle /dev/sdn drive state is: active/idle Mar 13 21:43:11 BIGBOX s3_sleep: Disk activity detected. Reset all counters. /dev/sdb drive state is: active/idle /dev/sdc drive state is: active/idle /dev/sdd drive state is: active/idle /dev/sde drive state is: active/idle /dev/sdg drive state is: active/idle /dev/sdi drive state is: active/idle /dev/sdj drive state is: active/idle /dev/sdk drive state is: active/idle /dev/sdl drive state is: active/idle /dev/sdm drive state is: active/idle /dev/sdn drive state is: active/idle Mar 13 21:43:18 BIGBOX kernel: program smartctl is using a deprecated SCSI ioctl, please convert it to SG_IO Mar 13 21:43:23 BIGBOX last message repeated 46 times Mar 13 21:43:38 BIGBOX kernel: md: disk10 read error, sector=1871085816 Mar 13 21:43:39 BIGBOX kernel: md: disk10 write error, sector=1871085816 Mar 13 21:43:39 BIGBOX kernel: md: recovery thread woken up ... Mar 13 21:43:39 BIGBOX kernel: md: recovery thread has nothing to resync Mar 13 21:44:06 BIGBOX emhttp: shcmd (69): /usr/local/sbin/emhttp_event stopping_svcs Mar 13 21:44:06 BIGBOX kernel: mdcmd (88): nocheck Mar 13 21:44:06 BIGBOX kernel: md: nocheck_array: check not active

Did you try stopping the array, unassigning the bad drive, then restarting the array? After that shutdown and put in new drive, turn on and assign it?