May 17, 201214 yr EDIT: Replacing the PSU with a unit that has more amps on a single rail appears to have fixed my issues. I installed a Corsair CMPSU650TX. There's a single thread about this error and it didn't really address the error, so I'm asking for assistance. Eight disk array, wanted to add another 1TB disk. preclear rpt: ========================================================================1.13 == invoked as: ./preclear_disk.sh -A -c 2 /dev/sdb == WDC WD10EADS-11M2B2 WD-WMAV52389554 == Disk /dev/sdb has been successfully precleared == with a starting sector of 64 == Ran 2 cycles == == Using :Read block size = 8225280 Bytes == Last Cycle's Pre Read Time : 3:34:35 (77 MB/s) == Last Cycle's Zeroing time : 3:13:23 (86 MB/s) == Last Cycle's Post Read Time : 7:00:22 (39 MB/s) == Last Cycle's Total Time : 10:14:51 == == Total Elapsed Time 24:06:33 == == Disk Start Temperature: 27C == == Current Disk Temperature: 27C, == ============================================================================ ** Changed attributes in files: /tmp/smart_start_sdb /tmp/smart_finish_sdb ATTRIBUTE NEW_VAL OLD_VAL FAILURE_THRESHOLD STATUS RAW_VALUE Seek_Error_Rate = 100 200 0 ok 0 No SMART attributes are FAILING_NOW 0 sectors were pending re-allocation before the start of the preclear. 0 sectors were pending re-allocation after pre-read in cycle 1 of 2. 0 sectors were pending re-allocation after zero of disk in cycle 1 of 2. 0 sectors were pending re-allocation after post-read in cycle 1 of 2. 0 sectors were pending re-allocation after zero of disk in cycle 2 of 2. 0 sectors are pending re-allocation at the end of the preclear, the number of sectors pending re-allocation did not change. 0 sectors had been re-allocated before the start of the preclear. 0 sectors are re-allocated at the end of the preclear, the number of sectors re-allocated did not change. ============================================================================ When I assign the disk a slot and go back to the main page to bring the array online and format that new disk, all disks begin to mount, then I refresh the page and the same option to format is there. A loop, in other words. The disk is being added to the other port (SAS2) on the Supermicro AOC card. When I tried to add the disk to SAS1, it would red ball the 0223 disk. It was precleared on a different machine, if that matters. The odd.png image is something I've not noticed before. See syslog. 4.7 Pro addons: apcupsd, unmenu OS at time of building: 4.7 CPU: AMD Sempron 140 Motherboard: BIOSTAR A760G M2+ Micro ATX RAM: Kingston 2GB Case: AZZA Helios 910 Drive Cage(s): Icy Dock 5 in 3 Drive Cage(s): 2x SUPERMICRO CSE-M35T 5 in 3 Power Supply: Corsair CX500 v2 SATA Expansion Card(s): SUPERMICRO AOC-SASLP-MV8 PCI Express x4 SAS RAID Controller Cables: 18 inch Fans: Stock fans Flash Drive: 2GB SanDisk Cruzer Micro UPS: APC BE550G Back-UPS ES 8 Outlet 550VA 120V Parity Drive: 1tb WD FALS Data Drives: 3x 1tb WD FALS Data Drives: 4x Samsung F1 Spinpoint 1 TB Data Drives: 1tb Samsung F3 Spinpoint Total Drive Capacity: 7tb The new disk is a WD 10EADS I bought used. It has warranty valid through 2013-07. syslog-2012-05-17.txt
May 17, 201214 yr These errors seems to indicate it is not working too well: May 17 00:11:20 Other kernel: ata3: translated ATA stat/err 0x41/04 to SCSI SK/ASC/ASCQ 0xb/00/00 May 17 00:11:20 Other kernel: ata3: status=0x41 { DriveReady Error } Unless a cable has come loose, you might need to take advantage of the RMA.
May 17, 201214 yr Author These errors seems to indicate it is not working too well: May 17 00:11:20 Other kernel: ata3: translated ATA stat/err 0x41/04 to SCSI SK/ASC/ASCQ 0xb/00/00 May 17 00:11:20 Other kernel: ata3: status=0x41 { DriveReady Error } Unless a cable has come loose, you might need to take advantage of the RMA. It wasn't loose. I even tried another empty slot and found the same errors. Thanks, Joe.
May 17, 201214 yr Author I threw that offending disk into another unRAID server, and it is working fine. Which leads back to the cause for the errors in the first place. Now I'm thinking all the trouble I had with red balled disks, and running inticofig multiple times is all related to something else. I'm going to swap power supplies and see what happens. syslog is from the other server where the disk is functioning normally. syslog-2012-05-172.txt
May 17, 201214 yr Author Run check disk on the flash. reiserfsck --check /dev/sda where sda = flash disk?
May 18, 201214 yr Run check disk on the flash. reiserfsck --check /dev/sda where sda = flash disk? not exactly. Easiest for most is to move the flash disk to a windows PC and run chkdisk on it there. The flash drive does not have a reiser file system, therefore using reiserfsck on it would not be helpful. Joe L.
May 18, 201214 yr Author Switched from a Corsair 500CX v2 to a Corsair CMPSU650TX. +3.3V@25A, +5V@20A, +12V@34A, [email protected], [email protected] vs +3.3V@24A, +5V@30A, +12V@52A, [email protected], [email protected].
May 18, 201214 yr Author And no issues (thus far) adding another disk. I wonder if this CX500 v2 is hosed. It has the same output stats as the CX500 in my main server, which is running fourteen disks. Without a hiccup. :'( EDIT: I can see a light colored goo on top of one of the caps.
May 18, 201214 yr And no issues (thus far) adding another disk. I wonder if this CX500 v2 is hosed. It has the same output stats as the CX500 in my main server, which is running fourteen disks. Without a hiccup. :'( EDIT: I can see a light colored goo on top of one of the caps. The cream colored "goo" looks like glue to stabilize/hold the toroidal coil that is immediately adjacent (keep it from vibrating). It is not an indication of a failure.
May 18, 201214 yr And no issues (thus far) adding another disk. I wonder if this CX500 v2 is hosed. It has the same output stats as the CX500 in my main server, which is running fourteen disks. Without a hiccup. :'( EDIT: I can see a light colored goo on top of one of the caps. The cream colored "goo" looks like glue to stabilize/hold the toroidal coil that is immediately adjacent (keep it from vibrating). It is not an indication of a failure. On the other hand, if you are referring to the bottom of the capacitor, where there is some discoloration, and it almost looks like some bulging on the top of the capacitor, that could be an indication of a bad capacitor.
May 18, 201214 yr Author Moving back to SOLVED. It appears as though the PSU was my problem, even going back weeks and weeks to my previous issues.
Archived
This topic is now archived and is closed to further replies.