December 26, 201015 yr I'm trying to get my 4224 up and running after migrating out of my CM Stacker case. It's been an interesting experience, learning valuable lessons like ALWAYS SCREW THE DRIVES TO THE TRAYS! That said, I have some issues. 1) In the CM Stacker I had my first 6 drives hooked to my MB. So I bought 2 of these: http://www.newegg.com/Product/Product.aspx?Item=N82E16816133033&Tpk=NORCO%20C-SFF8087-4S I had them hooked to ports 1-6 on my MB, with the two spares just hanging out for a better day. My MB doesn't see them anymore Shows zero connected SATA devices. So that's bad. 2) I moved the drives down in the case so that it was on the controller cards. The two cards see the 6 drives (4 on 1, two on another just to make sure the cards worked). But once I get past the part where it displays the detected drives it just hangs where it says press Ctrl-M or Space. If I wait too long hitting those two does nothing. Hitting ctrl-alt-del reboots. I've let it sit for 10 minutes at that screen with no progress. I can't get into the MB bios either because that doesn't come until after the SAS cards boot. Soooo... I seem to be stuck Any ideas on what I can do? I'm out of the water right now. I'm guessing the SAS cards are somehow stopping the MB from detecting the SATA drives, but why can't I get past that part
December 27, 201015 yr Author Apparently if I let it sit long enough it gets past the SAS screen and boots to unRaid. I was able to start the array again with the devices on the cards and am running a parity check right now. I am still very concerned that I can't see any hooked up to my MB slots. I need those 6 SATA slots
December 27, 201015 yr To confirm you are chasing down the right path did you remove the two MV8s and test hooking the drives to the mobo like you had them hooked up in the CM Stacker?
December 27, 201015 yr Author It's on my list to try today. I just wanted to be sure I could get the array up somehow. Question for anyone who knows, when you look at the row is Drive 0 on the left or right?
December 27, 201015 yr On my MSI H55M board, the bottom-most (nearest to the motherboard) slot closest to the power plug shows up as /dev/sda (SATA 1) in Slackware and the slot above it shows as /dev/sdb (SATA2). The next set of two slots next to it follow the same pattern, with bottom-most being /dev/sdc (SATA3) and slot above it shows as /dev/sdd (SATA4). Then the straight slot closest to the edge shows as /dev/sde (SATA5) and the straight slot further in shows as /dev/sdf (SATA6). I hope that description helps regardless of your motherboard orientation. Here's a picture I edited to label the sata connectors:
December 27, 201015 yr Author Right, thanks BRiT. I actually meant on the Norco case do the hard drive bays go L to R or R to L So is the leftmost bay 0 or 3 on a backplane.
December 28, 201015 yr Thanks. What does init13 do? It is a setting that can tell the motherboard that there are bootable drives attached. When that is set it can add drives to the available boot list. By disabling it those drives should not be added to that list. Another setting to consider is the the Interrupt 19 setting on some boards. I am setting up a Supermicro X8SIL board that has this setting. From my manual this setting probes all attached drives on expansion cards to see if they are bootable and will add them to them (even if they are not bootable) to the list to boot from. I turned both of these setting off and it has been working great for me.
December 29, 201015 yr Author Well, turning off init13 didn't cause the drives to appear. Sigh. So I am waiting for the preclears I have running to finish and then I will shut it down and pull the cards to try and confirm it is definately them interfering. Where would I find the Interrupt 19 setting? I still don't understand why it is sooooo slow to boot now too.
December 29, 201015 yr Author Crap. Came down this morning and found my system COMPLETELY hung. Could not access anything even from the console. Looks like running the 6 preclears froze it up somehow So then I rebooted, and now I've got the red ball on one of my drives. Grrrrrr! Things are not going my way. I can't see anything in the syslog to explain why I've got the red ball.
December 29, 201015 yr Crap. Came down this morning and found my system COMPLETELY hung. Could not access anything even from the console. Looks like running the 6 preclears froze it up somehow So then I rebooted, and now I've got the red ball on one of my drives. Grrrrrr! Things are not going my way. I can't see anything in the syslog to explain why I've got the red ball. if the system had hung and you had to reboot the syslog was lost. The system created a new one when you rebooted. The red ball is because a write to the drive failed more than likely. How much RAM do you have? I just set up a 4224 and Supermicro X8SIL with 8GB of RAM and had 6 preclear running at once. it worked just fine for me... but that might be because of the high amount of RAM.
December 29, 201015 yr Crap. Came down this morning and found my system COMPLETELY hung. Could not access anything even from the console. Looks like running the 6 preclears froze it up somehow So then I rebooted, and now I've got the red ball on one of my drives. Grrrrrr! Things are not going my way. I can't see anything in the syslog to explain why I've got the red ball. If a drive is "red" a write to it failed. The error messages affiliated with that failure were probably in the syslog that was lost when the machine had to be rebooted. The current syslog will not contain the error. You now need to determine why the "write" failed. It could be as simple as a loose cable, or as complicated as a power supply unable to keep up with clearing 6 disks plus those already in the array. (or, it could be a bad drive) In any case, can you get a SMART report from the failed drive? Joe L.
December 29, 201015 yr Author Yeah, I'll give that a go when I get home. PSU should be ok, it's a Corsair 650w with a nice strong 12v rail. I also noticed my drive temps got alot higher when I put the non-Green drives in it. I've got 4GB in, and I've run 6 drives at once before but I admit those were my first 6. This is also the first time I've tried preclear on those AOC SASLP cards. Maybe 6 at once was just too much. Not sure why any or all that would have impacted a drive in the array already.
December 29, 201015 yr Yeah, I'll give that a go when I get home. PSU should be ok, it's a Corsair 650w with a nice strong 12v rail. I also noticed my drive temps got alot higher when I put the non-Green drives in it. I've got 4GB in, and I've run 6 drives at once before but I admit those were my first 6. This is also the first time I've tried preclear on those AOC SASLP cards. Maybe 6 at once was just too much. Not sure why any or all that would have impacted a drive in the array already. The 650tx is a great power (if that is the one you have) The impact of additional drives could be in how the power cabling is configured. (all 12 drives off of a single connector would be too much for it) Other than that, should be no impact. You might have had an issue with memory, or as likely as not, a loose connection, or a cable you've accidentally loosened when installing the new drives, or loosened with the vibrations of the new drives being cleared.
December 29, 201015 yr Author Thanks, I'll crack it open and poke around. I am running the 6 backplanes off a single cable but multiple connectors on that cable. It is the 650tx.
December 29, 201015 yr Do you have BOTH molex connectors on each backplane in use on the 4224? If not I HIGHLY suggest doing that first. Even though the norco instructions say you only need to connect one of the molex connectors for power I have found that to be a little flacky. I actually loaded drives onto a single connector on purpose and it started misbehaving like crazy. Would give me random problems that were exactly what I was expecting after doing some reading.
December 29, 201015 yr Author Ahhh... no I don't. That's going to be a little problematic to hook both up. I think I need some more molex splitters, the PSU has a fairly limited supply. Or do they make SATA to molex adapters...
December 29, 201015 yr They do make Sata power to molex power adapters. I got mine from a local store called Microcenter. They are the exact same thing as these; though I don't think I paid that much for mine.
December 29, 201015 yr Author Yeah, just ordered a bunch from the egg. Never knew they made those, I've always seen the reverse. Should be here tomorrow.
December 31, 201015 yr Author Ok, attached the extra molex Booted up and kicked off a SMART test via UnMenu. Problem is, I admit I don't know where it gets put. I checked the syslog, nothing there. I checked the SMART history in unmenu and it said I don't have a smarthistory directory so I'm guessing something isn't set up right there. I do have a lot of the attached errors but my research here says those aren't a big deal. Dec 30 20:27:16 Tower ata_id[4692]: HDIO_GET_IDENTITY failed for '/dev/block/8:48' Dec 30 20:27:16 Tower ata_id[4709]: HDIO_GET_IDENTITY failed for '/dev/block/8:48' Dec 30 20:27:16 Tower ata_id[4728]: HDIO_GET_IDENTITY failed for '/dev/block/8:64' Dec 30 20:27:16 Tower ata_id[4744]: HDIO_GET_IDENTITY failed for '/dev/block/8:64' Dec 30 20:27:17 Tower ata_id[4764]: HDIO_GET_IDENTITY failed for '/dev/block/8:96'
December 31, 201015 yr Author Found the SMART report Looks like it's ok to me... smartctl -a -d ata /dev/sdf 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: SAMSUNG HD204UI Serial Number: S2HGJDWZ807151 Firmware Version: 1AQ10001 User Capacity: 2,000,398,934,016 bytes Device is: In smartctl database [for details use: -P show] ATA Version is: 8 ATA Standard is: Not recognized. Minor revision code: 0x28 Local Time is: Thu Dec 30 20:37:26 2010 EST ==> WARNING: May need -F samsung or -F samsung2 enabled; see manual for details. 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: (0x00) Offline data collection activity was never started. Auto Offline Data Collection: Disabled. 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: (20460) seconds. Offline data collection capabilities: (0x5b) SMART execute Offline immediate. Auto Offline data collection on/off support. Suspend Offline collection upon new command. Offline surface scan supported. Self-test supported. No 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. SCT capabilities: (0x003f) 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 100 100 051 Pre-fail Always - 4 2 Throughput_Performance 0x0026 252 252 000 Old_age Always - 0 3 Spin_Up_Time 0x0023 067 067 025 Pre-fail Always - 10003 4 Start_Stop_Count 0x0032 100 100 000 Old_age Always - 185 5 Reallocated_Sector_Ct 0x0033 252 252 010 Pre-fail Always - 0 7 Seek_Error_Rate 0x002e 252 252 051 Old_age Always - 0 8 Seek_Time_Performance 0x0024 252 252 015 Old_age Offline - 0 9 Power_On_Hours 0x0032 100 100 000 Old_age Always - 389 10 Spin_Retry_Count 0x0032 252 252 051 Old_age Always - 0 11 Calibration_Retry_Count 0x0032 252 252 000 Old_age Always - 0 12 Power_Cycle_Count 0x0032 100 100 000 Old_age Always - 13 181 Unknown_Attribute 0x0022 100 100 000 Old_age Always - 2793118 191 G-Sense_Error_Rate 0x0022 252 252 000 Old_age Always - 0 192 Power-Off_Retract_Count 0x0022 252 252 000 Old_age Always - 0 194 Temperature_Celsius 0x0002 064 063 000 Old_age Always - 30 (Lifetime Min/Max 17/38) 195 Hardware_ECC_Recovered 0x003a 100 100 000 Old_age Always - 0 196 Reallocated_Event_Count 0x0032 252 252 000 Old_age Always - 0 197 Current_Pending_Sector 0x0032 252 252 000 Old_age Always - 0 198 Offline_Uncorrectable 0x0030 252 252 000 Old_age Offline - 0 199 UDMA_CRC_Error_Count 0x0036 200 200 000 Old_age Always - 0 200 Multi_Zone_Error_Rate 0x002a 100 100 000 Old_age Always - 0 223 Load_Retry_Count 0x0032 252 252 000 Old_age Always - 0 225 Load_Cycle_Count 0x0032 100 100 000 Old_age Always - 188 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 Short offline Completed without error 00% 388 - # 2 Short offline Completed without error 00% 388 - SMART Selective Self-Test Log Data Structure Revision Number (0) should be 1 SMART Selective self-test log data structure revision number 0 Warning: ATA Specification requires selective self-test log data structure revision number = 1 SPAN MIN_LBA MAX_LBA CURRENT_TEST_STATUS 1 0 0 Completed [00% left] (0-65535) 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.
Archived
This topic is now archived and is closed to further replies.