crankbearing

I had another look at my server this morning, disk 7 is a user share as Music, set to fill-up, is used only for music. The disk is excluded from all other user shares. So the only activity is when I copy a new album from my desktop to that user share. All files, but 4 are showing zero bytes. I had this problem back in 2014 as well, and I found the thread, but I did not post details on how I repaired it. I will post a syslog when I get home this evening. This is disk 7 and I did notice in the log upon boot that ata7 showed sata link down on boot up. I am going to pick up a new sata cable and try that first. Only disk 7 is affected, none of my movie files or tv show files have a problem. All of my music files at least 95% of them are FLAC. thanks, Dave

Hi all, I went to use my hi-res audio via my voyage mpd server last night, and it would not connect. I finally gave up and loaded up volumio 2.505 on my rasberry PI this morning, and no matter what I use for advanced options in the smb/cifs share, I can only get the artist and album title to show up in the library, I do get one album to populate but only 4 songs off that album show up. I finally scrapped Volumio and loaded up a version of rune audio to try and got the same results. I have reset permissions, I have tried various advanced options in the share setting on either platform including vers=1.0 to 3.0. ro, rw, and pretty much everything else I could try. This Music share works fine on kodi via my nvidia shield. I am sure it's a permission issue! Any ideas would help! Thanks, Dave

HI, No, the files have been on this drive and setup as a user share since I built the server a year or so ago. Thanks, Dave

thanks for the reply, I pulled the flash and checked it and it was ok, I pulled the drive and ran a recovery on it and it found 945 files both flac and mp3's. nothing in order and no file names just the files but all the tag info seems in tact. So I cannot figure out why it would only affect music files and nothing else either on that disk 7 or any other disk. I am attaching a syslog I cannot see anything although it is from today I do not have one from the 26th, it jumps from the 22/06 to 29/06. I did run a file system check on that drive it is in the log I am attaching. Thanks, Dave syslog-2014-06-29.zip

Hey All, Not sure what's happened, I am on 5.04 never had any issue with my music files. I went to play some music the other night on my voyage MPD alix box, which has never given me a days problem no playback all album titles are present on the unraid share. Tried XBMC no playback then I loaded up volumio on my raspi all no luck, dug into it a little deeper this morning and I see now that all of my music files are zero bytes except for a couple albums out of 600+. They all say they were modified on June 26 at 8:02 pm. Strange thing I never touched the server. We did have a power outage but I have a smart 2200 ups and powerdown script runs on both my servers. None of my movies or tv shows were affected nor any data on my other unraid server. I looked at the log but nothing stands out to me. Not sure where to look but any advice would be great. Thanks, Dave

Hey All, 75 for the board chip and ram - chip is 64 bit capable as well. 15 each for the promise cards 60 each for the supermicro caddies I think I will give the coolermaster to my dad. all plus shipping, I have some interest on the supermicro's thanks, Dave

I tried moving ipmi to lan 1 and unraid on lan 2 and it was like a race it seemed that for every 5 rx packets it was dropping 1 or 2. switched back to ipmi on dedicated, lan1 disabled and unraid on lan 2 that is where I get the least amount of packets dropped I am not sure how this will react with teaming or bonding eventually. I updated the eeprom on both 82574 chips and tried with both drivers. Dave

I found a eeprom update for the 82574L chips and ram it on both of mine on my board with no change. with either stock or updated driver. still digging for a solution. I am thinking of moving ipmi to lan 1 and unraid to lan 2 to test some more. I am preclearing a 4tb right now so that will have to wait. rgds, Dave

Tom, are you working late . just got my 3rd key in the mail. thanks Tom. Now I'll not have any fun with x64 testing for a while, I am pre-clearing a 4tb red right now in the test setup.

cleaning up the server room today I have a few things I could get rid of. Asus P5EVM-DO with 4Gb ddr2-800 patriot memory 2 sticks and an core2 duo e7300 2.66GHz stock heatsink and fan (attached is a syslog for the board no drives but sata300 tx4 cards are running and Ethernet is connected.) 2 Promise tx4 300 cards. 1 coolermaster 4 in 3 chassis that I used while I was building the new server. 2 supermicro 5 in 3 cages, now that I am swapping to the 4220 I will not need them anymore. all items are in Ottawa Canada. Make an offer tested with Unraid 5.05 Rgds, Dave syslog-2014-02-01.txt

just ordered my third pro key. Thanks, Tom. I just picked up a data traveler micro 8gb I have had two pro keys 512kb data travelers in service since 4.33 if I recall with no issue. Cannot find those sandisk fits around here

here is a good read that I found for SM board owners - ftp://ftp.supermicro.com/CDR-NIC_1.30_for_Add-on_NIC_Cards/Intel/LAN/PROXGB/DOCS/LINUX/e1000.htm. I know it's for older Kernels but still may help in some cases, I did not know there were several e1K driver revs. rgds, Dave

your lan looks to be up in the syslog, but it is showing three missing hard drives Disk 1, 4, and 5. and it does say possible corruption on sda. I would back up your flash drive and check it for errors. do you still have the failed drive and when was your last parity check performed. IF you had valid parity when the drive failed then and only then would I remove the new drive re-install the failed drive in that slot. boot up the server and via webgui make sure all the drives are there and in the proper slots and green other than the failed drive. if that is all good start and stop the array then shutdown replace the bad drive boot up assign the new drive and let it rebuild and do a parity check following that. when it is up you can ping the server ip and see if it responds prior to doing any of the above. The array is not going to start in it's current state.

I'll look into this for 5.0.6 release. Would be good if it could be resolved - I'm sure that there must be some performance hit from the dropped packets. I agree, here is a LP thread I was following and comment 22 has a link to SF and what I thought that was the latest module. https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1018561 My machine is setup for testing right beside me and I have the network plugged into a 2nd 1GB switch and I am seeing a lot of idle activity even with all drives spun down. I saw 80K plus dropped errors on lan 1, so I disabled it and switched to lan 2 and it is much less 700-800 within 10-15 Minutes I copied about 50 gb of data in testing the backplanes and it has stayed around that number but my lan light on the case is pretty much on solid, I am not sure if ipmi heartbeat causing some of that but I would not think so since I have it set to dedicated port and not shared. Did you find my old comments on this subject? I found that if I added another Gb switch between unRAID and the rest of my network, the dropped packet count fell to near zero. yes I did read through that thread and as many others as I could find here and abroad, that is how my lan is setup. I have a 24 port switch in the rack that all of my servers as well as the distributed panel wiring runs into and then in my office I have a 2nd 8 port gb switch that I have 2 machines, my network printer and I am plugged into it for testing. this is after about 48 hours since I last rebooted the machine. eth0 Link encap:Ethernet HWaddr 00:25:90:ad:6c:95 inet addr:192.168.1.59 Bcast:192.168.1.255 Mask:255.255.255.0 UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1 RX packets:7811986 errors:0 dropped:2024 overruns:0 frame:0 TX packets:330295 errors:0 dropped:0 overruns:0 carrier:0 collisions:0 txqueuelen:1000 RX bytes:11805474817 (10.9 GiB) TX bytes:36832264 (35.1 MiB) Interrupt:19 Memory:df900000-df920000 lo Link encap:Local Loopback inet addr:127.0.0.1 Mask:255.0.0.0 UP LOOPBACK RUNNING MTU:65536 Metric:1 RX packets:10 errors:0 dropped:0 overruns:0 frame:0 TX packets:10 errors:0 dropped:0 overruns:0 carrier:0 collisions:0 txqueuelen:0 RX bytes:758 (758.0 B) TX bytes:758 (758.0 B) root@Tower:~# pete on another note, do you see any acpi (minor errors) in your syslog. I have one that I have trying to research although I can find several none of them have the same code as mine. Jan 30 07:23:43 Tower kernel: e1000e: Intel(R) PRO/1000 Network Driver - 2.2.14-k Jan 30 07:23:43 Tower kernel: e1000e: Copyright(c) 1999 - 2013 Intel Corporation. Jan 30 07:23:43 Tower kernel: e1000e 0000:02:00.0: Disabling ASPM L0s L1 Jan 30 07:23:43 Tower kernel: e1000e 0000:02:00.0: Interrupt Throttling Rate (ints/sec) set to dynamic conservative mode Jan 30 07:23:43 Tower kernel: e1000e 0000:02:00.0: irq 40 for MSI/MSI-X Jan 30 07:23:43 Tower kernel: e1000e 0000:02:00.0: irq 41 for MSI/MSI-X Jan 30 07:23:43 Tower kernel: e1000e 0000:02:00.0: irq 42 for MSI/MSI-X Jan 30 07:23:43 Tower kernel: ACPI Warning: 0x00000580-0x0000059f SystemIO conflicts with Region \_SB_.PCI0.SBUS.SMBI 1 (20130117/utaddress-251) Jan 30 07:23:43 Tower kernel: ACPI: If an ACPI driver is available for this device, you should use it instead of the native driver

I'll look into this for 5.0.6 release. Would be good if it could be resolved - I'm sure that there must be some performance hit from the dropped packets. I agree, here is a LP thread I was following and comment 22 has a link to SF and what I thought that was the latest module. https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1018561 My machine is setup for testing right beside me and I have the network plugged into a 2nd 1GB switch and I am seeing a lot of idle activity even with all drives spun down. I saw 80K plus dropped errors on lan 1, so I disabled it and switched to lan 2 and it is much less 700-800 within 10-15 Minutes I copied about 50 gb of data in testing the backplanes and it has stayed around that number but my lan light on the case is pretty much on solid, I am not sure if ipmi heartbeat causing some of that but I would not think so since I have it set to dedicated port and not shared. Dave

I just picked up a SM X9-scm-iif board with the same intel chipset dual lans. I disabled lan 1 and I am using lan 2 but I am noticing a lot of dropped RX packets in testing. I have read several of the posts here about it and as well there seems to be several bugs posted across the net with several workarounds. Tom, which e1000 driver are we currently using I noticed there is a 2.54 revision driver that a lot of bug posters have said seems to help. Anyone else seeing this on there intel based nics. Thanks, Dave

something like this! http://lime-technology.com/forum/index.php?topic=14695.0

320 at newegg.ca well that sucks I just got my X9-iif board. http://www.newegg.ca/Product/Product.aspx?Item=N82E16813182341 rgds, Dave

I decided to swap out my test psu with my old faithful antec 650w tru power and I ran two pre-clear cycles on the drive with no issues, then I loaded everything in the chassis and I am running a preclear right now as well as a parity check and so far so good. parity check running along a 95MB/s and preclear at 100 Mb/s plus. All off the motherboard ports and on the first backplane. If that passes I will start testing different backplane configurations. Hopefully I can get this all put away by the weekend. One thing I am still concerned with is rx packet drops on the e1000 I have ipmi on the dedicated port and set to dedicated in ipmiview, I disable lan1 and I am using lan 2 for unraid. The drops on lan 1 were very high, lan 2 is better but still seeing roughly 500-800+ drops after about 15 minutes. It seems like a known issue/bug after some goggle searching, latest report as of dec 2013. rgds, Dave

Hey All, NEW - Retail S/M X9SCM-iif board NEW - Intel 3220 cpu active stock psu NEW - Kingston 8gb 1333 ecc unbuffered (10 passes all OK) on bench not in chassis at this point (bench testing) I have been testing my new board all this week. ran memtest for a couple days with no issues. then added a 1TB test drive x 4 over a couple days. testing pre-clear (these are old drives just lying around for test reasons) on the drives and parity sync and a parity check this morning I added a 4th drive and set it to a 3 cycle write only pre-clear test when I got home the pre-clear was at 56% on the first cycle and it was frozen (but the system webgui was ok). I restarted a pre-clear on that drive single cycle write only and this is what I am seeing in the log after 44%. Jan 29 16:53:53 Tower in.telnetd[12208]: connect from 192.168.1.55 (192.168.1.55) (Routine) Jan 29 16:53:55 Tower login[12209]: ROOT LOGIN on '/dev/pts/0' from '192.168.1.55' (Logins) Jan 29 16:54:46 Tower kernel: sdb: sdb1 (Drive related) Jan 29 17:47:45 Tower kernel: ata3.00: exception Emask 0x10 SAct 0x7fffffff SErr 0x880100 action 0x6 frozen (Errors) Jan 29 17:47:45 Tower kernel: ata3.00: irq_stat 0x08000000, interface fatal error (Errors) Jan 29 17:47:45 Tower kernel: ata3: SError: { UnrecovData 10B8B LinkSeq } (Errors) Jan 29 17:47:45 Tower kernel: ata3.00: failed command: WRITE FPDMA QUEUED (Minor Issues) Jan 29 17:47:45 Tower kernel: ata3.00: cmd 61/00:00:50:4a:4a/04:00:29:00:00/40 tag 0 ncq 524288 out (Drive related) Jan 29 17:47:45 Tower kernel: res 40/00:5c:50:76:4a/00:00:29:00:00/40 Emask 0x10 (ATA bus error) (Errors) Jan 29 17:47:45 Tower kernel: ata3.00: status: { DRDY } (Drive related) Jan 29 17:47:45 Tower kernel: ata3.00: failed command: WRITE FPDMA QUEUED (Minor Issues) Jan 29 17:47:45 Tower kernel: ata3.00: cmd 61/00:08:50:4e:4a/04:00:29:00:00/40 tag 1 ncq 524288 out (Drive related) Jan 29 17:47:45 Tower kernel: res 40/00:5c:50:76:4a/00:00:29:00:00/40 Emask 0x10 (ATA bus error) (Errors) Jan 29 17:47:45 Tower kernel: ata3.00: status: { DRDY } (Drive related) Jan 29 17:47:45 Tower kernel: ata3.00: failed command: WRITE FPDMA QUEUED (Minor Issues) Jan 29 17:47:45 Tower kernel: ata3.00: cmd 61/00:10:50:52:4a/04:00:29:00:00/40 tag 2 ncq 524288 out (Drive related) Jan 29 17:47:45 Tower kernel: res 40/00:5c:50:76:4a/00:00:29:00:00/40 Emask 0x10 (ATA bus error) (Errors) Jan 29 17:47:45 Tower kernel: ata3.00: status: { DRDY } (Drive related) Jan 29 17:47:45 Tower kernel: ata3.00: failed command: WRITE FPDMA QUEUED (Minor Issues) Jan 29 17:47:45 Tower kernel: ata3.00: cmd 61/00:18:50:56:4a/04:00:29:00:00/40 tag 3 ncq 524288 out (Drive related) Jan 29 17:47:45 Tower kernel: res 40/00:5c:50:76:4a/00:00:29:00:00/40 Emask 0x10 (ATA bus error) (Errors) Jan 29 17:47:45 Tower kernel: ata3.00: status: { DRDY } (Drive related) Jan 29 17:47:45 Tower kernel: ata3.00: failed command: WRITE FPDMA QUEUED (Minor Issues) Jan 29 17:47:45 Tower kernel: ata3.00: cmd 61/00:20:50:5a:4a/04:00:29:00:00/40 tag 4 ncq 524288 out (Drive related) Jan 29 17:47:45 Tower kernel: res 40/00:5c:50:76:4a/00:00:29:00:00/40 Emask 0x10 (ATA bus error) (Errors) Jan 29 17:47:45 Tower kernel: ata3.00: status: { DRDY } (Drive related) Jan 29 17:47:45 Tower kernel: ata3.00: failed command: WRITE FPDMA QUEUED (Minor Issues) Jan 29 17:47:45 Tower kernel: ata3.00: cmd 61/00:28:50:5e:4a/04:00:29:00:00/40 tag 5 ncq 524288 out (Drive related) Jan 29 17:47:45 Tower kernel: res 40/00:5c:50:76:4a/00:00:29:00:00/40 Emask 0x10 (ATA bus error) (Errors) Jan 29 17:47:45 Tower kernel: ata3.00: status: { DRDY } (Drive related) Jan 29 17:47:45 Tower kernel: ata3.00: failed command: WRITE FPDMA QUEUED (Minor Issues) Jan 29 17:47:45 Tower kernel: ata3.00: cmd 61/00:30:50:62:4a/04:00:29:00:00/40 tag 6 ncq 524288 out (Drive related) Jan 29 17:47:45 Tower kernel: res 40/00:5c:50:76:4a/00:00:29:00:00/40 Emask 0x10 (ATA bus error) (Errors) Jan 29 17:47:45 Tower kernel: ata3.00: status: { DRDY } (Drive related) Jan 29 17:47:45 Tower kernel: ata3.00: failed command: WRITE FPDMA QUEUED (Minor Issues) Jan 29 17:47:45 Tower kernel: ata3.00: cmd 61/00:38:50:66:4a/04:00:29:00:00/40 tag 7 ncq 524288 out (Drive related) Jan 29 17:47:45 Tower kernel: res 40/00:5c:50:76:4a/00:00:29:00:00/40 Emask 0x10 (ATA bus error) (Errors) Jan 29 17:47:45 Tower kernel: ata3.00: status: { DRDY } (Drive related) Jan 29 17:47:45 Tower kernel: ata3.00: failed command: WRITE FPDMA QUEUED (Minor Issues) Jan 29 17:47:45 Tower kernel: ata3.00: cmd 61/00:40:50:6a:4a/04:00:29:00:00/40 tag 8 ncq 524288 out (Drive related) Jan 29 17:47:45 Tower kernel: res 40/00:5c:50:76:4a/00:00:29:00:00/40 Emask 0x10 (ATA bus error) (Errors) Jan 29 17:47:45 Tower kernel: ata3.00: status: { DRDY } (Drive related) Jan 29 17:47:45 Tower kernel: ata3.00: failed command: WRITE FPDMA QUEUED (Minor Issues) Jan 29 17:47:45 Tower kernel: ata3.00: cmd 61/00:48:50:6e:4a/04:00:29:00:00/40 tag 9 ncq 524288 out (Drive related) Jan 29 17:47:45 Tower kernel: res 40/00:5c:50:76:4a/00:00:29:00:00/40 Emask 0x10 (ATA bus error) (Errors) Jan 29 17:47:45 Tower kernel: ata3.00: status: { DRDY } (Drive related) Jan 29 17:47:45 Tower kernel: ata3.00: failed command: WRITE FPDMA QUEUED (Minor Issues) Jan 29 17:47:45 Tower kernel: ata3.00: cmd 61/00:50:50:72:4a/04:00:29:00:00/40 tag 10 ncq 524288 out (Drive related) Jan 29 17:47:45 Tower kernel: res 40/00:5c:50:76:4a/00:00:29:00:00/40 Emask 0x10 (ATA bus error) (Errors) Jan 29 17:47:45 Tower kernel: ata3.00: status: { DRDY } (Drive related) Jan 29 17:47:45 Tower kernel: ata3.00: failed command: WRITE FPDMA QUEUED (Minor Issues) Jan 29 17:47:45 Tower kernel: ata3.00: cmd 61/00:58:50:76:4a/04:00:29:00:00/40 tag 11 ncq 524288 out (Drive related) Jan 29 17:47:45 Tower kernel: res 40/00:5c:50:76:4a/00:00:29:00:00/40 Emask 0x10 (ATA bus error) (Errors) Jan 29 17:47:45 Tower kernel: ata3.00: status: { DRDY } (Drive related) Jan 29 17:47:45 Tower kernel: ata3.00: failed command: WRITE FPDMA QUEUED (Minor Issues) Jan 29 17:47:45 Tower kernel: ata3.00: cmd 61/00:60:50:7a:4a/04:00:29:00:00/40 tag 12 ncq 524288 out (Drive related) Jan 29 17:47:45 Tower kernel: res 40/00:5c:50:76:4a/00:00:29:00:00/40 Emask 0x10 (ATA bus error) (Errors) Jan 29 17:47:45 Tower kernel: ata3.00: status: { DRDY } (Drive related) Jan 29 17:47:45 Tower kernel: ata3.00: failed command: WRITE FPDMA QUEUED (Minor Issues) Jan 29 17:47:45 Tower kernel: ata3.00: cmd 61/00:68:50:02:4a/04:00:29:00:00/40 tag 13 ncq 524288 out (Drive related) Jan 29 17:47:45 Tower kernel: res 40/00:5c:50:76:4a/00:00:29:00:00/40 Emask 0x10 (ATA bus error) (Errors) Jan 29 17:47:45 Tower kernel: ata3.00: status: { DRDY } (Drive related) Jan 29 17:47:45 Tower kernel: ata3.00: failed command: WRITE FPDMA QUEUED (Minor Issues) Jan 29 17:47:45 Tower kernel: ata3.00: cmd 61/00:70:50:06:4a/04:00:29:00:00/40 tag 14 ncq 524288 out (Drive related) Jan 29 17:47:45 Tower kernel: res 40/00:5c:50:76:4a/00:00:29:00:00/40 Emask 0x10 (ATA bus error) (Errors) Jan 29 17:47:45 Tower kernel: ata3.00: status: { DRDY } (Drive related) Jan 29 17:47:45 Tower kernel: ata3.00: failed command: WRITE FPDMA QUEUED (Minor Issues) Jan 29 17:47:45 Tower kernel: ata3.00: cmd 61/00:78:50:0a:4a/04:00:29:00:00/40 tag 15 ncq 524288 out (Drive related) Jan 29 17:47:45 Tower kernel: res 40/00:5c:50:76:4a/00:00:29:00:00/40 Emask 0x10 (ATA bus error) (Errors) Jan 29 17:47:45 Tower kernel: ata3.00: status: { DRDY } (Drive related) Jan 29 17:47:45 Tower kernel: ata3.00: failed command: WRITE FPDMA QUEUED (Minor Issues) Jan 29 17:47:45 Tower kernel: ata3.00: cmd 61/00:80:50:0e:4a/04:00:29:00:00/40 tag 16 ncq 524288 out (Drive related) Jan 29 17:47:45 Tower kernel: res 40/00:5c:50:76:4a/00:00:29:00:00/40 Emask 0x10 (ATA bus error) (Errors) Jan 29 17:47:45 Tower kernel: ata3.00: status: { DRDY } (Drive related) Jan 29 17:47:45 Tower kernel: ata3.00: failed command: WRITE FPDMA QUEUED (Minor Issues) Jan 29 17:47:45 Tower kernel: ata3.00: cmd 61/00:88:50:12:4a/04:00:29:00:00/40 tag 17 ncq 524288 out (Drive related) Jan 29 17:47:45 Tower kernel: res 40/00:5c:50:76:4a/00:00:29:00:00/40 Emask 0x10 (ATA bus error) (Errors) Jan 29 17:47:45 Tower kernel: ata3.00: status: { DRDY } (Drive related) Jan 29 17:47:45 Tower kernel: ata3.00: failed command: WRITE FPDMA QUEUED (Minor Issues) Jan 29 17:47:45 Tower kernel: ata3.00: cmd 61/00:90:50:16:4a/04:00:29:00:00/40 tag 18 ncq 524288 out (Drive related) Jan 29 17:47:45 Tower kernel: res 40/00:5c:50:76:4a/00:00:29:00:00/40 Emask 0x10 (ATA bus error) (Errors) Jan 29 17:47:45 Tower kernel: ata3.00: status: { DRDY } (Drive related) Jan 29 17:47:45 Tower kernel: ata3.00: failed command: WRITE FPDMA QUEUED (Minor Issues) Jan 29 17:47:45 Tower kernel: ata3.00: cmd 61/00:98:50:1a:4a/04:00:29:00:00/40 tag 19 ncq 524288 out (Drive related) Jan 29 17:47:45 Tower kernel: res 40/00:5c:50:76:4a/00:00:29:00:00/40 Emask 0x10 (ATA bus error) (Errors) Jan 29 17:47:45 Tower kernel: ata3.00: status: { DRDY } (Drive related) Jan 29 17:47:45 Tower kernel: ata3.00: failed command: WRITE FPDMA QUEUED (Minor Issues) Jan 29 17:47:45 Tower kernel: ata3.00: cmd 61/00:a0:50:1e:4a/04:00:29:00:00/40 tag 20 ncq 524288 out (Drive related) Jan 29 17:47:45 Tower kernel: res 40/00:5c:50:76:4a/00:00:29:00:00/40 Emask 0x10 (ATA bus error) (Errors) Jan 29 17:47:45 Tower kernel: ata3.00: status: { DRDY } (Drive related) Jan 29 17:47:45 Tower kernel: ata3.00: failed command: WRITE FPDMA QUEUED (Minor Issues) Jan 29 17:47:45 Tower kernel: ata3.00: cmd 61/00:a8:50:22:4a/04:00:29:00:00/40 tag 21 ncq 524288 out (Drive related) Jan 29 17:47:45 Tower kernel: res 40/00:5c:50:76:4a/00:00:29:00:00/40 Emask 0x10 (ATA bus error) (Errors) Jan 29 17:47:45 Tower kernel: ata3.00: status: { DRDY } (Drive related) Jan 29 17:47:45 Tower kernel: ata3.00: failed command: WRITE FPDMA QUEUED (Minor Issues) Jan 29 17:47:45 Tower kernel: ata3.00: cmd 61/00:b0:50:26:4a/04:00:29:00:00/40 tag 22 ncq 524288 out (Drive related) Jan 29 17:47:45 Tower kernel: res 40/00:5c:50:76:4a/00:00:29:00:00/40 Emask 0x10 (ATA bus error) (Errors) Jan 29 17:47:45 Tower kernel: ata3.00: status: { DRDY } (Drive related) Jan 29 17:47:45 Tower kernel: ata3.00: failed command: WRITE FPDMA QUEUED (Minor Issues) Jan 29 17:47:45 Tower kernel: ata3.00: cmd 61/00:b8:50:2a:4a/04:00:29:00:00/40 tag 23 ncq 524288 out (Drive related) Jan 29 17:47:45 Tower kernel: res 40/00:5c:50:76:4a/00:00:29:00:00/40 Emask 0x10 (ATA bus error) (Errors) Jan 29 17:47:45 Tower kernel: ata3.00: status: { DRDY } (Drive related) Jan 29 17:47:45 Tower kernel: ata3.00: failed command: WRITE FPDMA QUEUED (Minor Issues) Jan 29 17:47:45 Tower kernel: ata3.00: cmd 61/00:c0:50:2e:4a/04:00:29:00:00/40 tag 24 ncq 524288 out (Drive related) Jan 29 17:47:45 Tower kernel: res 40/00:5c:50:76:4a/00:00:29:00:00/40 Emask 0x10 (ATA bus error) (Errors) Jan 29 17:47:45 Tower kernel: ata3.00: status: { DRDY } (Drive related) Jan 29 17:47:45 Tower kernel: ata3.00: failed command: WRITE FPDMA QUEUED (Minor Issues) Jan 29 17:47:45 Tower kernel: ata3.00: cmd 61/00:c8:50:32:4a/04:00:29:00:00/40 tag 25 ncq 524288 out (Drive related) Jan 29 17:47:45 Tower kernel: res 40/00:5c:50:76:4a/00:00:29:00:00/40 Emask 0x10 (ATA bus error) (Errors) Jan 29 17:47:45 Tower kernel: ata3.00: status: { DRDY } (Drive related) Jan 29 17:47:45 Tower kernel: ata3.00: failed command: WRITE FPDMA QUEUED (Minor Issues) Jan 29 17:47:45 Tower kernel: ata3.00: cmd 61/00:d0:50:36:4a/04:00:29:00:00/40 tag 26 ncq 524288 out (Drive related) Jan 29 17:47:45 Tower kernel: res 40/00:5c:50:76:4a/00:00:29:00:00/40 Emask 0x10 (ATA bus error) (Errors) Jan 29 17:47:45 Tower kernel: ata3.00: status: { DRDY } (Drive related) Jan 29 17:47:45 Tower kernel: ata3.00: failed command: WRITE FPDMA QUEUED (Minor Issues) Jan 29 17:47:45 Tower kernel: ata3.00: cmd 61/00:d8:50:3a:4a/04:00:29:00:00/40 tag 27 ncq 524288 out (Drive related) Jan 29 17:47:45 Tower kernel: res 40/00:5c:50:76:4a/00:00:29:00:00/40 Emask 0x10 (ATA bus error) (Errors) Jan 29 17:47:45 Tower kernel: ata3.00: status: { DRDY } (Drive related) Jan 29 17:47:45 Tower kernel: ata3.00: failed command: WRITE FPDMA QUEUED (Minor Issues) Jan 29 17:47:45 Tower kernel: ata3.00: cmd 61/00:e0:50:3e:4a/04:00:29:00:00/40 tag 28 ncq 524288 out (Drive related) Jan 29 17:47:45 Tower kernel: res 40/00:5c:50:76:4a/00:00:29:00:00/40 Emask 0x10 (ATA bus error) (Errors) Jan 29 17:47:45 Tower kernel: ata3.00: status: { DRDY } (Drive related) Jan 29 17:47:45 Tower kernel: ata3.00: failed command: WRITE FPDMA QUEUED (Minor Issues) Jan 29 17:47:45 Tower kernel: ata3.00: cmd 61/00:e8:50:42:4a/04:00:29:00:00/40 tag 29 ncq 524288 out (Drive related) Jan 29 17:47:45 Tower kernel: res 40/00:5c:50:76:4a/00:00:29:00:00/40 Emask 0x10 (ATA bus error) (Errors) Jan 29 17:47:45 Tower kernel: ata3.00: status: { DRDY } (Drive related) Jan 29 17:47:45 Tower kernel: ata3.00: failed command: WRITE FPDMA QUEUED (Minor Issues) Jan 29 17:47:45 Tower kernel: ata3.00: cmd 61/00:f0:50:46:4a/04:00:29:00:00/40 tag 30 ncq 524288 out (Drive related) Jan 29 17:47:45 Tower kernel: res 40/00:5c:50:76:4a/00:00:29:00:00/40 Emask 0x10 (ATA bus error) (Errors) Jan 29 17:47:45 Tower kernel: ata3.00: status: { DRDY } (Drive related) Jan 29 17:47:45 Tower kernel: ata3: hard resetting link (Minor Issues) Jan 29 17:47:50 Tower kernel: ata3: link is slow to respond, please be patient (ready=0) (Drive related) Jan 29 17:47:55 Tower kernel: ata3: COMRESET failed (errno=-16) (Minor Issues) Jan 29 17:47:55 Tower kernel: ata3: hard resetting link (Minor Issues) Jan 29 17:48:00 Tower kernel: ata3: link is slow to respond, please be patient (ready=0) (Drive related) Jan 29 17:48:05 Tower kernel: ata3: COMRESET failed (errno=-16) (Minor Issues) Jan 29 17:48:05 Tower kernel: ata3: hard resetting link (Minor Issues) Jan 29 17:48:05 Tower kernel: ata3: SATA link up 3.0 Gbps (SStatus 123 SControl 300) (Drive related) Jan 29 17:48:05 Tower kernel: ata3.00: ACPI cmd ef/10:06:00:00:00:00 (SET FEATURES) succeeded (Drive related) Jan 29 17:48:05 Tower kernel: ata3.00: ACPI cmd f5/00:00:00:00:00:00 (SECURITY FREEZE LOCK) filtered out (Drive related) Jan 29 17:48:05 Tower kernel: ata3.00: ACPI cmd b1/c1:00:00:00:00:00 (DEVICE CONFIGURATION OVERLAY) filtered out (Drive related) Jan 29 17:48:05 Tower kernel: ata3.00: ACPI cmd ef/10:06:00:00:00:00 (SET FEATURES) succeeded (Drive related) Jan 29 17:48:05 Tower kernel: ata3.00: ACPI cmd f5/00:00:00:00:00:00 (SECURITY FREEZE LOCK) filtered out (Drive related) Jan 29 17:48:05 Tower kernel: ata3.00: ACPI cmd b1/c1:00:00:00:00:00 (DEVICE CONFIGURATION OVERLAY) filtered out (Drive related) Jan 29 17:48:05 Tower kernel: ata3.00: configured for UDMA/133 (Drive related) Jan 29 17:48:05 Tower kernel: ata3: EH complete (Drive related) All 4 drives are running on the sata 3gbs port of the supermicro board nothing plugged into the 6Gbs port and no pci-e cards installed yet. This drive is a know good drive previously removed from my main server with no issues I only upgraded it at the time. I am wondering, do I have a flaky board? now is the time I would like to find out, I was about ready to load it in the new 4220 and start testing the backplanes of the case, but if the board is flaky I do not want to find other issue and start blaming the chassis. Thanks, Dave

Got the new board and I ended up with Kingston 8GB unbuffered ecc for a total of 16Gb. setup the board as a test bed to get familiar with it last night, ran memtest all night with no issues, did a wrote only pre-clear on three 1TB test drives so far so good. I ended up getting a 3220 for 100$ new on clearance so that is the cpu I will use. I have set ipmi to dedicated and disabled lan 1 as I was seeing several RX drops on 5.04 and on 5.05 using lan2 I am seeing drops as well but not as many as on lan1. kvm was a bit of a drag to get working ended up having to add the site in java configuration to finally get it working from either a browser IE or IPMIView. I will likely continue to test for the rest of the week and get some rack rails for the case and install and test on the weekend. I will update to a better ipmi cable when I put the server in the rack to test the RX drops. The board is 2.0A bios and I updated the ipmi firmware to 2.38 that was the other key to kvm working for me. rgds, Dave

Hey all, I have a new 4220 on the way and one thing I cannot seem to find is how the backplane connectors relate to what drive bays? Thanks, Dave

Thanks, I thought as much, I guess overclocking is not a big concern. Are you running your sas cards side by side in the x8 pci-e slots? Did you play with MDsync tuning at all on your system with the SAS cards? I read through that thread well glanced over it yesterday for a while. The 4220 also supports 2 2.5 drives above the hard drive cages if I wanted to add a cache drive, I do have a kingston 90Gb ssd sitting on the shelf doing nothing. rgds, Dave

Thanks for the replies, I ordered it all this morning will update, found a 1240v2 locally for 250$. Other then DOA is there anything I should be concerned about with an open box Xeon processor. Thanks, Dave

yes read that several times, thanks. My question is after rebuilding data on 2 new 3 TB drives and then replacing a parity drive and having that sync and parity check twice and no further errors on the drive in question - Is there really any problems with it.