burtjr

1. You will not need the CBL-0068L the 16 pin connector will hook straight to the X8SIL-F 2. You will not need a 24pin extender 3. You will need a 8pin power extender something like this NZXT CB-8P 8-Pin Motherboard Power Extension Premium Cable (Black) 4. You will not need the 4 pin fan cables if you are not going to change fans right away. What you will need is at least a 1 to 2 split 3 pin fan cable to hook up the rear fans. Something like this Syba SY-CAB65007 3 Pin Female to 2 x 3 Pin Male Connectors Fan Power Extension Y Cable (7.75 Inches) The fans that come with it are pretty loud, but they are spinning at 3000-5000 rpm. If the server is in another room with the door shut you can't here it. I would wait on the fan change until you find out what temps your getting after you place it where it is going.

I'm talking about the 12V 8 pin cpu power connector on the C2SEE motherboard. The 12V 8 pin cpu power supply cable doesn't reach it. The question for other users with this motherboard is what solution are they using with this case? I have the X8SIL-F and had the same issue. Check the motherboard manual, I know mine states for the 8 pin connector. Since I will be adding cards in the future I wanted to ensure I had enough power going to the board. I got my extender cable for $8. Not worth taking the chance damaging anything over a few bucks. On a side note the rear fan cables were not long enough for the X8SIL, the fan headers are on the upper portion of the board. It looks as if at least one is on the upper portion of the C2SEE board.

keep an eye on craigslist. I use this web page so I get an email anytime there is a post in the computer section with the word rack in it. http://dostuffright.com/watch-craigslist-for-an-item Thanks for the tip flips, I haven't used craigs list much. I will lokk into the link a little. Have you gotten any spam from them?

Did they turn out to be long enough? Thanks good to know Yep they were long enough!

Did they turn out to be long enough?

Got my extention cables in today, finished the build. Fired up with no issues on first boot! In the middle of the parity check. The fans are loud, but my drive temps are currently between 24-26C, 14C lower than my last system. One of the main reasons I changed setups. I have only logged into the IPMI to look around, but looks pretty cool. Tomorrow I will straighten up the cables and play with the IPMI a little more. Now I need a rack, hopefully I can find one with fairly cheep shipping for X-Mas.

The ribbon cable was just long enough for the X8SIL-F. It is a 16 pin connector meant for Supermicro motherboards. If you plan on using a non-supermicro board you will require the cable mentioned above.

Started my build tonight. I went with the following: 1. Supermicro X8SIL-F MB ( I recieved rev 1.02 from Amazon) this case was supposedly designed for this board, but I had some set up issues a. 8 pin connector from the power supply is to short to reach the mother board power connector. I had to order an extension cable I went with this one http://www.amazon.com/gp/product/B0036ORCJY/ref=oss_product b. The rear fan cables are to short to reach all but one fan connector on the motherboard. I ended up ordering this http://www.amazon.com/gp/product/B002G1YNQS/ref=oss_product 2. I3-530 CPU 3. Supermicro SNK-P0046P Processor Heatsink (passive) 4. 4GB 1333MHZ DDR3 Ecc CL9 Dimm (KVR1333D3E9SK2/4G) Build quality seems excellent, but the stand offs do not match with this board perfectly. I had to put a plastic spacer in the hole around the sata ports, and the corner where the sata ports are has no mounting whole making the board slightly flimsy when plugging in the cables. Best bet is to support the board from underneath while plugging in the cables. I was unable to start her up as I am waiting on the cables to arrive. Did a parity check while I was at work in hopes of placing the drives after the build. Well I guess I can hold off until the weekend.

Found this in the tech support questions and answers Question: I have an SC932T-R760 chassis. There are other cables coming out from the power supply that are not labeled or documented. What are they? I really could use some output of some sort to indicate the status of the power modules. Answer: The cable with a black connector is for I2C and the other white connector is for Power Fault LED. If your motherboard has I2C and Power Fault header, then you can use it.

From what I have read this is the retail version of the EADS drive. It looks like the 2TB drives do have the advanced formatting, at least what I have read on their website. A way to check would be to register your drive with WD and see what you come up with.

Joe, completed the swap and the error followed the drive. I still need to look through the forum to reread about cluster errors and Unraid calling out as error after they have been fixed. If that is the case I may not even have a problem. Should I shift the drives back to the way they were or leave as is? Seems to me like it really doesn't matter as long as Unraid is functioning. Is this the case or am I off base here? Here is a cut and paste of a portion of the logs: Aug 29 18:37:08 Media kernel: e8 e0 88 af Aug 29 18:37:08 Media kernel: sd 2:0:0:0: [sdb] ASC=0x13 ASCQ=0x0 Aug 29 18:37:08 Media kernel: sd 2:0:0:0: [sdb] CDB: cdb[0]=0x28: 28 00 e8 e0 88 a8 00 00 08 00 Aug 29 18:37:08 Media kernel: end_request: I/O error, dev sdb, sector 3907029167 Aug 29 18:37:08 Media kernel: Buffer I/O error on device sdb, logical block 488378645 Aug 29 18:37:08 Media kernel: ata2: EH complete Burt

Thanks Joe, I will give that a try later today

The bad sectors are not being accessed. They've already been re-allocated. (and, there is nothing you can do to fix them anyway, other than writing to them, and that's when they are re-allocated, since only then does the disk know what should be in the sector, and if re-allocated they've already been written to.) How many disks do you have in your server? What specific model/brand power supply? Is it possible you are exceeding its capacity? have you a "Y" splitter in the power cable? Have you tried to switch the drive to a different connector on the disk controller (swap it with a drive that is working) to see if it is a disk controller issue, and not a disk drive issue? I remember reading somewhere on this site about unraid logging it as an error after it has been reallocated, I will take a look and reread that discussion. To answer your questions, 1. 4 disks 3 1.5T WDEARS, 1 2T WDEARS 2. Power supply I believe is a Speed (never heard of it) 650 watt. My son bought the computer on ebay, left for the military and I repurposed it into a server. Probably is a weak link 3. I haven't calculated, but I know I am not too close to it. 4. I have no Y splitters installed 5. I have not swapped the drive to a different spot, I will do that and let you know. Is there any precautions to switching the spot (I want to ensure unraid remembers which drive is which) I guess I can just do a search for that on the forum. Thanks for the help Joe Burt Joe L.

The only issue is that Unraid is still logging the error. Would fixing the bad clusters fix this read error? Burt Aug 29 08:40:59 Media kernel: ata1.00: exception Emask 0x0 SAct 0x0 SErr 0x0 action 0x0 Aug 29 08:40:59 Media kernel: ata1.00: BMDMA stat 0x4 Aug 29 08:40:59 Media kernel: ata1.00: failed command: READ DMA EXT Aug 29 08:40:59 Media kernel: ata1.00: cmd 25/00:08:a8:88:e0/00:00:e8:00:00/e0 tag 0 dma 4096 in Aug 29 08:40:59 Media kernel: res 51/01:00:af:88:e0/01:00:e8:00:00/e0 Emask 0x1 (device error) Aug 29 08:40:59 Media kernel: ata1.00: status: { DRDY ERR } Aug 29 08:40:59 Media kernel: ata1.00: configured for UDMA/33 Aug 29 08:40:59 Media kernel: sd 1:0:0:0: [sda] Unhandled sense code Aug 29 08:40:59 Media kernel: sd 1:0:0:0: [sda] Result: hostbyte=0x00 driverbyte=0x08 Aug 29 08:40:59 Media kernel: sd 1:0:0:0: [sda] Sense Key : 0x3 [current] [descriptor] Aug 29 08:40:59 Media kernel: Descriptor sense data with sense descriptors (in hex): Aug 29 08:40:59 Media kernel: 72 03 13 00 00 00 00 0c 00 0a 80 00 00 00 00 00 Aug 29 08:40:59 Media kernel: e8 e0 88 af Aug 29 08:40:59 Media kernel: sd 1:0:0:0: [sda] ASC=0x13 ASCQ=0x0 Aug 29 08:40:59 Media kernel: sd 1:0:0:0: [sda] CDB: cdb[0]=0x28: 28 00 e8 e0 88 a8 00 00 08 00 Aug 29 08:40:59 Media kernel: end_request: I/O error, dev sda, sector 3907029167 Aug 29 08:40:59 Media kernel: Buffer I/O error on device sda, logical block 488378645 Aug 29 08:40:59 Media kernel: ata1: EH complete

Here is the smart report from unmenu, I appreciate the help Statistics for /dev/sda 00S_WD-WCAVY2333185 smartctl -a -d ata /dev/sda smartctl version 5.38 [i486-slackware-linux-gnu] Copyright © 2002-8 Bruce Allen Home page is http://smartmontools.sourceforge.net/ === START OF INFORMATION SECTION === Device Model: WDC WD20EARS-00S8B1 Serial Number: WD-WCAVY2333185 Firmware Version: 80.00A80 User Capacity: 2,000,398,934,016 bytes Device is: Not in smartctl database [for details use: -P showall] ATA Version is: 8 ATA Standard is: Exact ATA specification draft version not indicated Local Time is: Sun Aug 29 08:15:14 2010 PDT 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: (40800) 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: ( 255) minutes. Conveyance self-test routine recommended polling time: ( 5) minutes. SCT capabilities: (0x3031) SCT Status 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 200 139 021 Pre-fail Always - 6966 4 Start_Stop_Count 0x0032 100 100 000 Old_age Always - 201 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 097 097 000 Old_age Always - 2743 10 Spin_Retry_Count 0x0032 100 100 000 Old_age Always - 0 11 Calibration_Retry_Count 0x0032 100 253 000 Old_age Always - 0 12 Power_Cycle_Count 0x0032 100 100 000 Old_age Always - 24 192 Power-Off_Retract_Count 0x0032 200 200 000 Old_age Always - 18 193 Load_Cycle_Count 0x0032 200 200 000 Old_age Always - 1079 194 Temperature_Celsius 0x0022 126 105 000 Old_age Always - 26 196 Reallocated_Event_Count 0x0032 200 200 000 Old_age Always - 0 197 Current_Pending_Sector 0x0032 200 200 000 Old_age Always - 1 198 Offline_Uncorrectable 0x0030 200 200 000 Old_age Offline - 1 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 No self-tests have been logged. [To run self-tests, use: smartctl -t] 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.

Thanks for the Help Joe, I tried the command you gave me through telnet, but came up with command not found. I am now attempting to get the smart report from unmenu.

Hi all, great site. Been coming here for about 6 months now, there is a lot of useful information. To my issue, today I was trying to access the web interface but could not get there. Ended up hooking up my monitor and keyboard to the server to see what was going on. I rebooted and it got stuck in a error loop on sda1 (WD20EARS). I did the following things: 1. Removed flash drive and checked for errors (ok) 2. Replaced SATA cable for sda1 (parity) I thought this fixed the issue because the system booted and I was able to get to the web interface. 3. Verified pins 7/8 are jumpered. 4. Checked the logs and here is what they look like: Aug 28 21:33:12 Media kernel: res 51/01:00:af:88:e0/01:00:e8:00:00/e0 Emask 0x1 (device error) Aug 28 21:33:12 Media kernel: ata1.00: status: { DRDY ERR } Aug 28 21:33:12 Media kernel: ata1.00: configured for UDMA/33 Aug 28 21:33:12 Media kernel: ata1: EH complete Aug 28 21:33:15 Media kernel: ata1.00: exception Emask 0x0 SAct 0x0 SErr 0x0 action 0x0 Aug 28 21:33:15 Media kernel: ata1.00: BMDMA stat 0x4 Aug 28 21:33:15 Media kernel: ata1.00: failed command: READ DMA EXT Aug 28 21:33:15 Media kernel: ata1.00: cmd 25/00:08:a8:88:e0/00:00:e8:00:00/e0 tag 0 dma 4096 in Aug 28 21:33:15 Media kernel: res 51/01:00:af:88:e0/01:00:e8:00:00/e0 Emask 0x1 (device error) Aug 28 21:33:15 Media kernel: ata1.00: status: { DRDY ERR } Aug 28 21:33:15 Media kernel: ata1.00: configured for UDMA/33 Aug 28 21:33:15 Media kernel: sd 1:0:0:0: [sda] Unhandled sense code Aug 28 21:33:15 Media kernel: sd 1:0:0:0: [sda] Result: hostbyte=0x00 driverbyte=0x08 Aug 28 21:33:15 Media kernel: sd 1:0:0:0: [sda] Sense Key : 0x3 [current] [descriptor] Aug 28 21:33:15 Media kernel: Descriptor sense data with sense descriptors (in hex): Aug 28 21:33:15 Media kernel: 72 03 13 00 00 00 00 0c 00 0a 80 00 00 00 00 00 Aug 28 21:33:15 Media kernel: e8 e0 88 af Aug 28 21:33:15 Media kernel: sd 1:0:0:0: [sda] ASC=0x13 ASCQ=0x0 Aug 28 21:33:15 Media kernel: sd 1:0:0:0: [sda] CDB: cdb[0]=0x28: 28 00 e8 e0 88 a8 00 00 08 00 Aug 28 21:33:15 Media kernel: end_request: I/O error, dev sda, sector 3907029167 Aug 28 21:33:15 Media kernel: Buffer I/O error on device sda, logical block 488378645 Aug 28 21:33:15 Media kernel: ata1: EH complete Aug 28 21:33:18 Media kernel: ata1.00: exception Emask 0x0 SAct 0x0 SErr 0x0 action 0x0 Aug 28 21:33:18 Media kernel: ata1.00: BMDMA stat 0x4 Aug 28 21:33:18 Media kernel: ata1.00: failed command: READ DMA EXT Aug 28 21:33:18 Media kernel: ata1.00: cmd 25/00:08:a8:88:e0/00:00:e8:00:00/e0 tag 0 dma 4096 in Aug 28 21:33:18 Media kernel: res 51/01:00:af:88:e0/01:00:e8:00:00/e0 Emask 0x1 (device error) Aug 28 21:33:18 Media kernel: ata1.00: status: { DRDY ERR } Aug 28 21:33:18 Media kernel: ata1.00: configured for UDMA/33 Aug 28 21:33:18 Media kernel: ata1: EH complete Aug 28 21:33:20 Media kernel: ata1.00: exception Emask 0x0 SAct 0x0 SErr 0x0 action 0x0 Aug 28 21:33:20 Media kernel: ata1.00: BMDMA stat 0x4 Aug 28 21:33:20 Media kernel: ata1.00: failed command: READ DMA EXT Aug 28 21:33:20 Media kernel: ata1.00: cmd 25/00:08:a8:88:e0/00:00:e8:00:00/e0 tag 0 dma 4096 in Aug 28 21:33:20 Media kernel: res 51/01:00:af:88:e0/01:00:e8:00:00/e0 Emask 0x1 (device error) Aug 28 21:33:20 Media kernel: ata1.00: status: { DRDY ERR } Aug 28 21:33:20 Media kernel: ata1.00: configured for UDMA/33 Aug 28 21:33:20 Media kernel: ata1: EH complete Aug 28 21:33:23 Media kernel: ata1.00: exception Emask 0x0 SAct 0x0 SErr 0x0 action 0x0 Aug 28 21:33:23 Media kernel: ata1.00: BMDMA stat 0x4 Aug 28 21:33:23 Media kernel: ata1.00: failed command: READ DMA EXT Aug 28 21:33:23 Media kernel: ata1.00: cmd 25/00:08:a8:88:e0/00:00:e8:00:00/e0 tag 0 dma 4096 in Aug 28 21:33:23 Media kernel: res 51/01:00:af:88:e0/01:00:e8:00:00/e0 Emask 0x1 (device error) Aug 28 21:33:23 Media kernel: ata1.00: status: { DRDY ERR } Aug 28 21:33:23 Media kernel: ata1.00: configured for UDMA/33 Aug 28 21:33:23 Media kernel: ata1: EH complete Aug 28 21:33:26 Media kernel: ata1.00: exception Emask 0x0 SAct 0x0 SErr 0x0 action 0x0 Aug 28 21:33:26 Media kernel: ata1.00: BMDMA stat 0x4 Aug 28 21:33:26 Media kernel: ata1.00: failed command: READ DMA EXT Aug 28 21:33:26 Media kernel: ata1.00: cmd 25/00:08:a8:88:e0/00:00:e8:00:00/e0 tag 0 dma 4096 in Aug 28 21:33:26 Media kernel: res 51/01:00:af:88:e0/01:00:e8:00:00/e0 Emask 0x1 (device error) Aug 28 21:33:26 Media kernel: ata1.00: status: { DRDY ERR } Aug 28 21:33:26 Media kernel: ata1.00: configured for UDMA/33 Aug 28 21:33:26 Media kernel: ata1: EH complete Aug 28 21:33:29 Media kernel: ata1.00: exception Emask 0x0 SAct 0x0 SErr 0x0 action 0x0 Aug 28 21:33:29 Media kernel: ata1.00: BMDMA stat 0x4 Aug 28 21:33:29 Media kernel: ata1.00: failed command: READ DMA EXT Aug 28 21:33:29 Media kernel: ata1.00: cmd 25/00:08:a8:88:e0/00:00:e8:00:00/e0 tag 0 dma 4096 in Aug 28 21:33:29 Media kernel: res 51/01:00:af:88:e0/01:00:e8:00:00/e0 Emask 0x1 (device error) Aug 28 21:33:29 Media kernel: ata1.00: status: { DRDY ERR } Aug 28 21:33:29 Media kernel: ata1.00: configured for UDMA/33 Aug 28 21:33:29 Media kernel: ata1: EH complete Aug 28 21:33:32 Media kernel: ata1.00: exception Emask 0x0 SAct 0x0 SErr 0x0 action 0x0 Aug 28 21:33:32 Media kernel: ata1.00: BMDMA stat 0x4 Aug 28 21:33:32 Media kernel: ata1.00: failed command: READ DMA EXT Aug 28 21:33:32 Media kernel: ata1.00: cmd 25/00:08:a8:88:e0/00:00:e8:00:00/e0 tag 0 dma 4096 in Aug 28 21:33:32 Media kernel: res 51/01:00:af:88:e0/01:00:e8:00:00/e0 Emask 0x1 (device error) Aug 28 21:33:32 Media kernel: ata1.00: status: { DRDY ERR } Aug 28 21:33:32 Media kernel: ata1.00: configured for UDMA/33 Aug 28 21:33:32 Media kernel: sd 1:0:0:0: [sda] Unhandled sense code Aug 28 21:33:32 Media kernel: sd 1:0:0:0: [sda] Result: hostbyte=0x00 driverbyte=0x08 Aug 28 21:33:32 Media kernel: sd 1:0:0:0: [sda] Sense Key : 0x3 [current] [descriptor] Aug 28 21:33:32 Media kernel: Descriptor sense data with sense descriptors (in hex): Aug 28 21:33:32 Media kernel: 72 03 13 00 00 00 00 0c 00 0a 80 00 00 00 00 00 Aug 28 21:33:32 Media kernel: e8 e0 88 af Aug 28 21:33:32 Media kernel: sd 1:0:0:0: [sda] ASC=0x13 ASCQ=0x0 Aug 28 21:33:32 Media kernel: sd 1:0:0:0: [sda] CDB: cdb[0]=0x28: 28 00 e8 e0 88 a8 00 00 08 00 Aug 28 21:33:32 Media kernel: end_request: I/O error, dev sda, sector 3907029167 Aug 28 21:33:32 Media kernel: Buffer I/O error on device sda, logical block 488378645 Aug 28 21:33:32 Media kernel: ata1: EH complete Aug 28 21:35:00 Media kernel: mdcmd (565): spinup 0 Aug 28 21:35:00 Media kernel: It looks to me like the drive is not working due to a bad sector? Is this an easy issue to fix, or is the drive starting to fail? I appreciate any help on this, I am not a big software guru, but I learn quick and can follow instructions very well.