smino Posted March 25, 2009 Share Posted March 25, 2009 ASUS P5NT WS (775) (See Specs below) Intel Core2 Duo E6850 Power: OCZ520ADJ Memory:OCZ Platinum 4GB PC2-6400 DDR2 2xPromise SATA300 TX4 4 Port SATA Controller Card PCI (Could easily add an 8 port Supermicro pci-X card for a total of 23 Drives... Drives: All Seagate 400GB, 750, 1TB, and a 200GB Maxtor for Cache (temporary) Case: Tsunami Dream Case (it's an ok case) Ambient Temperature is 22C in the house. parity ata-ST31000340AS_9QJ1VGNP 23°C 976,762,552 - 2,363,487 339,038 0 disk1 ata-ST31000340AS_5QJ036TR 26°C 976,762,552 93,194,240 2,167,189 106 0 disk2 ata-ST31000640AS_3QJ00AJF 28°C 976,762,552 290,135,592 8,485,371 66,318 0 disk3 ata-ST3750640AS_5QD046F9 32°C 732,574,552 555,133,104 183,369 2,185,084 0 disk4 ata-ST3750330AS_9QK0Q3JY 26°C 732,574,552 288,106,992 2,110,687 4,344 0 disk5 ata-ST3400832AS_3NF0T88Q 30°C 390,711,352 212,624,160 1,132,704 33 0 disk6 ata-ST31000340AS_9QJ1KE5W 27°C 976,762,552 329,884,860 2,519,143 2,548 0 disk7 ata-ST3750640AS_5QD03EHT 29°C 732,574,552 553,760,328 1,989,912 33 0 disk8 ata-ST3750640AS_5QD04LCF 34°C 732,574,552 405,054,348 3,469,122 223 0 disk9 ata-ST3750640AS_5QD0CZSP 30°C 732,574,552 608,623,200 2,061,159 33 0 cache ata-Maxtor_6B200M0_B413F2CH 32°C 195,360,952 5,250,460 200,213 246,993 0 Lots of room to add more drives on the controllers, no place left in the case! That Norco 4020 looks good. I tested for file corruption using MD5 Checksum with this software: http://www.exactfile.com 3/24/2009 23:35:09 Move From Local Drive to TOWER:\TestFile.x264.mkv 8513693882 bytes MD5: Before:d6029cc734c43b196e318d7c2cbfa953 After :d6029cc734c43b196e318d7c2cbfa953 MotherBoard Specs: CPU LGA775 socket for Intel® Core™2 Extreme/Core™2 Duo/Pentium® Extreme/Pentium® D/Pentium® 4/Celeron® D Processors Intel® Quad-core CPU Ready Compatible with Intel® 06/05B/05A processors Chipset NVIDIA® nForce® 680i LT SLI Front Side Bus 1333/1066/800/533 MHz Memory Dual channel memory architecture 4 x DIMM, max. 8GB, DDR2-800/667/533, non-ECC, unbuffered memory *When installing total memory of 4GB capacity or more, Windows 32-bit operation system may only recognize less than 3GB. Hence, a total installed memory of less than 3GB is recommended. Expansion Slots 3 x PCI Express x16 slot, support NVIDIA® SLI™ technology, at x8, x8, x16 or x16, x1, x16 speed 1 x PCI-X slot 2 x PCI Express x1 slot 1 x PCI 2.2 slot Storage South bridge supports: - 1 x Ultra DMA 133/100/66/33 - 6 x Serial ATA 3.0Gb/s - NVIDIA MediaShield™ RAID supports RAID 0, 1, 0+1, 5 and JBOD span cross Serial ATA drives - 1x eSATA 3Gb/s Silicon Image Sil3531 LAN NVIDIA built-in dual Gigabit MAC with external Marvell 88E1116 PHY Support NVIDIA DualNet® technology High Definition Audio RealTek ALC888 8-channel High Definition Audio CODEC Support Jack-Sensing, Multi-streaming and Jack-Retasking Coaxial, Optical S/PDIF out IEEE 1394a VIA6308S controller supports 2 x 1394a ports USB Max. 10 USB2.0/1.1 ports(6 ports at mid-board, 4 ports at back panel) Here is a pciture of the setup: I have the syslog since 27 FEb 2009 to 22 March 2009. I removed names of duplicate files in the syslog for security reasons and left a commment there stating so. The files are very descriptive. I noticed it says "Phoenix BIOS detected: BIOS may corrupt low RAM, working it around.", but my MD5 Checks out... Quote Link to comment
SSD Posted March 25, 2009 Share Posted March 25, 2009 This is a nice setup. You should add to the "Pimp my rig" thread! Temps look quite good for #drives vs # fans in the case. You syslog also looks good. If you haven't rebooted, if you could do ONE more parity check it would satisfy the level2 verification requirements. It looks like there are 12 drives mounted? You only list 11 so was just curious. Maybe one is a CDROM drive. I like that little 6 drive stack on the floor of the case. Is that part of the case or something you bought separately? How does it work? How easy is it to get access (i.e., replace) a drive inside or the portion of the motherboard underneath? I bult something similar (except its 10 drives tall), but getting it in and out is a bit of a PITA. I have to disconnect ALL the drives and remove the stack to change a drive or access the lower right corner of the motherboard. I'm wondering if there is something I could learn from this to improve my design. Thanks! Quote Link to comment
smino Posted March 25, 2009 Author Share Posted March 25, 2009 I drilled four holes to mount the floor one. That is actually my Cache drive, so if the heat get's to it, no big deal. I did notice the temperature go up a little with the case open. This is my current case. My next Case will probably be a 4020 or the Lian Cube (30 drive). I prefer the hot swap option of the 4020. Now if they came out with a cheap 4020(no hot swap), I would just grab it. I originally had an 800 Watt power supply in this rig, it went bad, and now that I see it is stable with a lower power cpu, I will stick to it. I have many drives to add. 11 drives, I might have miscounted! Too much port. Maybe I should add one more Drive to the floor! That would bring it up to 13! Hmm..... I guess the question is, with 2TB drives, how many drives do you need to connect? In Theory, this should do me just fine, but the "Tim the tool Man" gene says go for more! Grin. Let me fix the duplicate file errors, and then run another parity check. Maybe I should buy the SuperMicro PCI-X Card and replace my two PCI cards. I was tempted to try out raid zero for both Cache and Parity. I just need to find something that does the trick. Quote Link to comment
prostuff1 Posted March 25, 2009 Share Posted March 25, 2009 Thanks for taking the time to get the information together. I have added the board to the Hardware Compatibility Page with the appropriate links back to this thread. Quote Link to comment
smino Posted March 26, 2009 Author Share Posted March 26, 2009 I think I might have just jinxs myself. So I started the parity check, and the mover. I saw these errors. All drives are green right now. Just wondering if the error came up because the drives were powered down? See Attachment It seems fine now. I'll keep an eye on it. It might also be a lose cable, as I was playing around in there last week. I have not switched all my cables to locking cables yet, although I do have them in stock here. Quote Link to comment
SSD Posted March 26, 2009 Share Posted March 26, 2009 Sorry you had this hiccup. Maybe RobJ will take a look and see if he can figure out what happened with ata4. Parity checks are a good thing to do to make sure your drives are happy and stay healthy. Although you hate to find problems, it is better to find them than have them bite you in the butt later on! Quote Link to comment
RobJ Posted March 27, 2009 Share Posted March 27, 2009 The SATA spec allows for hot plugging SATA drives, under the right conditions, and if all 'parties' (drive, drivers, connectors, OS, etc) support it. Unfortunately, your drive appears to be trying to take advantage of this feature! It looks like it is being connected and disconnected rather rapidly, something you probably did not want, so obviously something is loose. This can happen more often when connected in a backplane, and not fully seated. I would suspect in your case, that you are right and either the power or data cable is loose, or some of the leads are not making firm continuous contact. As usually happens in this scenario, the speed is limited downward in order to improve the reliability of the communications. It did limit the SATA link speed down, and then restore it on reset to the full 3.0 Gbps, but never restored the UDMA mode back from UDMA/33, so drive performance will be VERY slow until reboot. Quote Link to comment
smino Posted March 27, 2009 Author Share Posted March 27, 2009 The Parity Check passed. I will post the syslog when I get a chance. I'll look into which cable is causing the problem as well. Thanks Guys... Quote Link to comment
smino Posted March 27, 2009 Author Share Posted March 27, 2009 Well all looks good. Here is the syslog. I only removed names of files moved my the mover. There is some overlap here from the previous syslog. I can run a third Parity Check this weekend and see if anything comes up. What else do I need to make this board approved? Mar 25 23:06:28 Tower kernel: ata4: EH in SWNCQ mode,QC:qc_active 0x1 sactive 0x1 Mar 25 23:06:28 Tower kernel: ata4: SWNCQ:qc_active 0x1 defer_bits 0x0 last_issue_tag 0x0 Mar 25 23:06:28 Tower kernel: dhfis 0x1 dmafis 0x1 sdbfis 0x0 Mar 25 23:06:28 Tower kernel: ata4: ATA_REG 0x40 ERR_REG 0x0 Mar 25 23:06:28 Tower kernel: ata4: tag : dhfis dmafis sdbfis sacitve Mar 25 23:06:28 Tower kernel: ata4: tag 0x0: 1 1 0 1 Mar 25 23:06:28 Tower kernel: ata4.00: exception Emask 0x10 SAct 0x1 SErr 0x1810000 action 0xe frozen Mar 25 23:06:28 Tower kernel: ata4.00: hot unplug Mar 25 23:06:28 Tower kernel: ata4: SError: { PHYRdyChg LinkSeq TrStaTrns } Mar 25 23:06:28 Tower kernel: ata4.00: cmd 60/f8:00:17:3b:18/03:00:00:00:00/40 tag 0 ncq 520192 in Mar 25 23:06:28 Tower kernel: res 40/00:00:17:3b:18/00:00:17:3b:18/40 Emask 0x10 (ATA bus error) Mar 25 23:06:28 Tower kernel: ata4.00: status: { DRDY } Mar 25 23:06:34 Tower kernel: ata4: link is slow to respond, please be patient (ready=0) Mar 25 23:06:38 Tower kernel: ata4: device not ready (errno=-16), forcing hardreset Mar 25 23:06:38 Tower kernel: ata4: soft resetting link Mar 25 23:06:40 Tower kernel: ata4: SATA link up 3.0 Gbps (SStatus 123 SControl 300) Mar 25 23:06:40 Tower kernel: ata4.00: configured for UDMA/33 Mar 25 23:06:40 Tower kernel: ata4: EH complete Mar 25 23:06:40 Tower kernel: sd 4:0:0:0: [sdc] 1465149168 512-byte hardware sectors (750156 MB) Mar 25 23:06:40 Tower kernel: sd 4:0:0:0: [sdc] Write Protect is off Mar 25 23:06:40 Tower kernel: sd 4:0:0:0: [sdc] Mode Sense: 00 3a 00 00 Mar 25 23:06:40 Tower kernel: sd 4:0:0:0: [sdc] Write cache: enabled, read cache: enabled, doesn't support DPO or FUA Mar 25 23:06:40 Tower emhttp: shcmd (985): /usr/local/sbin/mover 2>&1 | logger & Mar 25 23:06:40 Tower logger: mover started Mar 25 23:43:07 Tower emhttp: shcmd (986): cp /var/spool/cron/crontabs/root- /var/spool/cron/crontabs/root Mar 25 23:43:07 Tower emhttp: shcmd (987): echo '# Generated mover schedule:' >>/var/spool/cron/crontabs/root Mar 25 23:43:07 Tower emhttp: shcmd (988): echo '30 1 * * /usr/local/sbin/mover 2>&1 | logger' >>/var/spool/cron/crontabs/root Mar 25 23:43:07 Tower emhttp: shcmd (989): crontab /var/spool/cron/crontabs/root Mar 25 23:43:07 Tower emhttp: shcmd (990): cp /etc/exports- /etc/exports Mar 25 23:43:07 Tower emhttp: shcmd (991): killall -HUP smbd Mar 25 23:43:07 Tower emhttp: shcmd (992): /etc/rc.d/rc.nfsd restart >/dev/null Mar 25 23:43:26 Tower logger: `./TV/TV/discovery.science.eco.tech.zero.waste.pdtv.xvid-t33v33.avi' -> `/mnt/user0/./TV/TV/discovery.science.eco.tech.zero.waste.pdtv.xvid-t33v33.avi' Mar 25 23:43:26 Tower logger: removed `./TV/TV/discovery.science.eco.tech.zero.waste.pdtv.xvid-t33v33.avi' Mar 25 23:44:45 Tower logger: `./TV/TV/discovery.science.human.body.ultimate.machine.sensation.pdtv.xvid-t33v33.avi' -> `/mnt/user0/./TV/TV/discovery.science.human.body.ultimate.machine.sensation.pdtv.xvid-t33v33.avi' Mar 25 23:44:45 Tower logger: removed `./TV/TV/discovery.science.human.body.ultimate.machine.sensation.pdtv.xvid-t33v33.avi' Mar 25 23:45:37 Tower ntpd[1436]: time reset -0.186718 s Mar 25 23:45:52 Tower ntpd[1436]: synchronized to 199.60.16.218, stratum 3 Name of files moved has been removed.All were successfull moving from cache drive to final destination. Mar 26 03:02:33 Tower ntpd[1436]: time reset -0.146327 s Mar 26 03:02:55 Tower ntpd[1436]: synchronized to 199.60.16.218, stratum 3 Name of files moved has been removed.All were successfull moving from cache drive to final destination. Mar 26 07:52:52 Tower logger: Cannot stat file /proc/1985/fd/160: No such file or directory Name of files moved has been removed.All were successfull moving from cache drive to final destination.Mar 26 11:01:31 Tower logger: mover finished Mar 26 11:47:48 Tower emhttp: shcmd (994): /usr/sbin/hdparm -y /dev/sdk >/dev/null Mar 26 11:47:48 Tower emhttp: shcmd (995): /usr/sbin/hdparm -y /dev/sdh >/dev/null Mar 26 11:47:48 Tower emhttp: shcmd (996): /usr/sbin/hdparm -y /dev/sdc >/dev/null Mar 26 11:47:48 Tower emhttp: shcmd (997): /usr/sbin/hdparm -y /dev/sdi >/dev/null Mar 26 11:47:48 Tower emhttp: shcmd (998): /usr/sbin/hdparm -y /dev/sdl >/dev/null Mar 26 11:51:04 Tower kernel: md: sync done. time=46171sec rate=21155K/sec Mar 26 11:51:04 Tower kernel: md: recovery thread sync completion status: 0 Mar 26 12:02:48 Tower emhttp: shcmd (999): /usr/sbin/hdparm -y /dev/sdj >/dev/null Mar 26 12:37:48 Tower emhttp: shcmd (1000): /usr/sbin/hdparm -y /dev/sdb >/dev/null Mar 26 12:37:48 Tower emhttp: shcmd (1001): /usr/sbin/hdparm -y /dev/sda >/dev/null Mar 26 12:37:48 Tower emhttp: shcmd (1002): /usr/sbin/hdparm -y /dev/sde >/dev/null Mar 26 12:37:48 Tower emhttp: shcmd (1003): /usr/sbin/hdparm -y /dev/sdg >/dev/null Mar 26 17:23:49 Tower emhttp: Spinning up all drives... Mar 26 18:09:00 Tower emhttp: shcmd (1004): /usr/sbin/hdparm -y /dev/sdb >/dev/null Mar 26 18:09:00 Tower emhttp: shcmd (1005): /usr/sbin/hdparm -y /dev/sde >/dev/null Mar 26 18:10:49 Tower emhttp: shcmd (1006): /usr/sbin/hdparm -y /dev/sda >/dev/null Mar 26 18:10:49 Tower emhttp: shcmd (1007): /usr/sbin/hdparm -y /dev/sdk >/dev/null Mar 26 18:10:49 Tower emhttp: shcmd (1008): /usr/sbin/hdparm -y /dev/sdh >/dev/null Mar 26 18:10:49 Tower emhttp: shcmd (1009): /usr/sbin/hdparm -y /dev/sdg >/dev/null Mar 26 18:10:49 Tower emhttp: shcmd (1010): /usr/sbin/hdparm -y /dev/sdc >/dev/null Mar 26 18:10:49 Tower emhttp: shcmd (1011): /usr/sbin/hdparm -y /dev/sdi >/dev/null Mar 26 18:10:49 Tower emhttp: shcmd (1012): /usr/sbin/hdparm -y /dev/sdl >/dev/null Mar 26 18:25:49 Tower emhttp: shcmd (1013): /usr/sbin/hdparm -y /dev/sdj >/dev/null Mar 26 19:02:50 Tower emhttp: shcmd (1014): /usr/sbin/hdparm -y /dev/sda >/dev/null Mar 26 19:02:50 Tower emhttp: shcmd (1015): /usr/sbin/hdparm -y /dev/sde >/dev/null Mar 26 19:02:50 Tower emhttp: shcmd (1016): /usr/sbin/hdparm -y /dev/sdk >/dev/null Mar 26 23:50:50 Tower emhttp: shcmd (1017): /usr/sbin/hdparm -y /dev/sdb >/dev/null Mar 26 23:50:50 Tower emhttp: shcmd (1018): /usr/sbin/hdparm -y /dev/sda >/dev/null Mar 26 23:50:50 Tower emhttp: shcmd (1019): /usr/sbin/hdparm -y /dev/sdk >/dev/null Mar 26 23:51:50 Tower emhttp: shcmd (1020): /usr/sbin/hdparm -y /dev/sde >/dev/null Mar 26 23:51:50 Tower emhttp: shcmd (1021): /usr/sbin/hdparm -y /dev/sdh >/dev/null Mar 26 23:51:50 Tower emhttp: shcmd (1022): /usr/sbin/hdparm -y /dev/sdc >/dev/null Mar 27 02:31:51 Tower emhttp: shcmd (1023): /usr/sbin/hdparm -y /dev/sda >/dev/null Mar 27 02:32:51 Tower emhttp: shcmd (1024): /usr/sbin/hdparm -y /dev/sde >/dev/null Mar 27 02:32:51 Tower emhttp: shcmd (1025): /usr/sbin/hdparm -y /dev/sdk >/dev/null Mar 27 04:31:51 Tower emhttp: shcmd (1026): /usr/sbin/hdparm -y /dev/sda >/dev/null Mar 27 04:31:51 Tower emhttp: shcmd (1027): /usr/sbin/hdparm -y /dev/sde >/dev/null Mar 27 04:31:51 Tower emhttp: shcmd (1028): /usr/sbin/hdparm -y /dev/sdk >/dev/null Mar 27 04:31:51 Tower emhttp: shcmd (1029): /usr/sbin/hdparm -y /dev/sdh >/dev/null Mar 27 04:31:51 Tower emhttp: shcmd (1030): /usr/sbin/hdparm -y /dev/sdg >/dev/null Mar 27 04:31:51 Tower emhttp: shcmd (1031): /usr/sbin/hdparm -y /dev/sdc >/dev/null Mar 27 04:31:51 Tower emhttp: shcmd (1032): /usr/sbin/hdparm -y /dev/sdi >/dev/null Mar 27 04:31:51 Tower emhttp: shcmd (1033): /usr/sbin/hdparm -y /dev/sdl >/dev/null Mar 27 04:46:51 Tower emhttp: shcmd (1034): /usr/sbin/hdparm -y /dev/sdj >/dev/null Mar 27 05:57:52 Tower emhttp: shcmd (1035): /usr/sbin/hdparm -y /dev/sdl >/dev/null Mar 27 06:25:52 Tower emhttp: shcmd (1036): /usr/sbin/hdparm -y /dev/sda >/dev/null Mar 27 06:26:52 Tower emhttp: shcmd (1037): /usr/sbin/hdparm -y /dev/sdk >/dev/null Mar 27 06:27:52 Tower emhttp: shcmd (1038): /usr/sbin/hdparm -y /dev/sdi >/dev/null Mar 27 06:35:52 Tower emhttp: shcmd (1039): /usr/sbin/hdparm -y /dev/sdj >/dev/null Mar 27 07:28:52 Tower emhttp: shcmd (1040): /usr/sbin/hdparm -y /dev/sde >/dev/null Mar 27 07:28:52 Tower emhttp: shcmd (1041): /usr/sbin/hdparm -y /dev/sdk >/dev/null Mar 27 07:29:19 Tower emhttp: shcmd (1042): /usr/sbin/hdparm -y /dev/sdh >/dev/null Mar 27 07:29:19 Tower emhttp: shcmd (1043): /usr/sbin/hdparm -y /dev/sdg >/dev/null Mar 27 07:52:52 Tower emhttp: shcmd (1044): /usr/sbin/hdparm -y /dev/sdb >/dev/null Mar 27 07:53:52 Tower emhttp: shcmd (1045): /usr/sbin/hdparm -y /dev/sda >/dev/null Mar 27 07:57:52 Tower emhttp: shcmd (1046): /usr/sbin/hdparm -y /dev/sdi >/dev/null Quote Link to comment
smino Posted March 29, 2009 Author Share Posted March 29, 2009 The SATA spec allows for hot plugging SATA drives, under the right conditions, and if all 'parties' (drive, drivers, connectors, OS, etc) support it. Unfortunately, your drive appears to be trying to take advantage of this feature! It looks like it is being connected and disconnected rather rapidly, something you probably did not want, so obviously something is loose. This can happen more often when connected in a backplane, and not fully seated. I would suspect in your case, that you are right and either the power or data cable is loose, or some of the leads are not making firm continuous contact. As usually happens in this scenario, the speed is limited downward in order to improve the reliability of the communications. It did limit the SATA link speed down, and then restore it on reset to the full 3.0 Gbps, but never restored the UDMA mode back from UDMA/33, so drive performance will be VERY slow until reboot. Can you help me identify which drives are on ata4? I think I will shut it down and remove on pci sata 2 card for now. Cheers... Quote Link to comment
RobJ Posted March 30, 2009 Share Posted March 30, 2009 It is just the one drive sdc, but this syslog begins at the errors, does not include the boot and drive setup, so I can't be sure which drive sdc is. You can check the Devices tab to identify it. In the earlier syslog of March 22, sdc was Disk 7, a Seagate 750GB with serial ending in EHT. Quote Link to comment
smino Posted March 30, 2009 Author Share Posted March 30, 2009 OK, Thanks. I will swap that cable first. Quote Link to comment
smino Posted April 16, 2009 Author Share Posted April 16, 2009 It was the cable. I moved my entire rig over to a new box now. I ran out of hard drives to continue testing on this platform. It is a good size and platform, but me new build with the p5Q Deluxe/premium is much better. See post in MB section. End of Line. Quote Link to comment
smino Posted August 29, 2009 Author Share Posted August 29, 2009 Folks, stay away from the OCZ 800W eliteXtreme power supply. I am now on my second RMA!@! Still waiting to get my RMA back. I did not wait, and went out and bought a Corsair instead. The replacement will be a backup. Curious if anyone knows of good cheap Dual hotswapable power supply that would do the trick? Quote Link to comment
Recommended Posts
Join the conversation
You can post now and register later. If you have an account, sign in now to post with your account.
Note: Your post will require moderator approval before it will be visible.