dwoods99

COOLER MASTER GX 450W RS450-ACAAD3-US This is a deal on newegg.ca not .com and it expires Jan 31st. Price is regularly $60, now $45 CDN plus manufacturer $15 USD credit card, so effectively $15 for 450W High Efficiency Design

Just wait, no doubt it's because they will put out an Antec 1200 Two, like the ANtec 300 Too and Antec 900 Two, which have hardware support for USB 3.0 at the front. I love the Antec 900s (got 3) but you do need to flatten the 4 tabs to fit in the 5x3 cages. Once in they slide in and out no problem. I am now looking to replace 120mm fans for quieter ones.

I don't see mention of Startech's cages. I have 2 SATABAY5BK and was quite happy with them except I learned trayless is much easier for swapping, Temperature of fans is adjustable with L/M/H and I had no problems with them. Discontinued now. I also have a SBAY5BK (just been discontinued) which is trayless. Works great but no fan control. The two 3" fans are not enough and I found my drives going to 35-40C compared to 27-35C for other drives in the case. Even though they are both discontinued now, their website has no 5x3 replacement for them. EDIT: modified post to include links to the products.

I am unable to determine if this one is trayless, is it?

The difference is that I get out4= 00000 and out5= 00000, 0+0 records in & out, 0 bytes copied. I tried some commands and got a script error... root@Tower:/boot/config# ./preclear_disk.sh -v ./preclear_disk.sh version: .9.8 root@Tower:/boot/config# ./preclear_disk.sh -t /dev/sda Pre-Clear unRAID Disk ######################################################################## ######################################################################## ./preclear_disk.sh: line 825: [: too many arguments ============================================================================ == == Disk /dev/sda is NOT precleared == ============================================================================ I was running this pre-clear at the same time as other disks. Should I try again by itself? Is there a way to bypass *all* the tests? BTW, I did not jumper it because I am setting things up to get ready for 5.0b3 to support these WD Green drives. Yes, the drive has stopped responding. (and the script was not coded to deal with that very elegantly) Most people find they'll need to power cycle the drive to get it to respond again. Even after that, many have had to clear the first few sectors to get it to respond sanely after changing the jumper (or adding it after the drive has been used without it being installed) Basically, we've found it does not even respond to anything when locked up. Not even an fdisk -l /dev/sdb will get complete results until you power cycle. As far as skipping "tests" sorry... can't unless you don't want to clear the drive and ensure it is cleared. Joe L. I hate re-quoting long posts but this goes back 4-5 pages. Anyways, after rebooting I went into fdisk and removed the existing empty NTFS partition that I had previously created when I first got it. Now after 30+ hours with a preclear check (w/o jumper), it comes out just fine... ready to use.

I would search in this thread but 38 pages is too much and I haven't found a way for this forum to allow me to search in a specific thread. I started a preclear -c 3 on a drive but it's only nearing the end of the first cycle. Could I kill the script during the 2nd cycle in order to do a reboot, and then I can rerun preclear again? One more... If I have already run a full cycle, is it acceptabe to use the '-n' next time to speed things up?

Here's some results from a 1TB Seagate, not sure what to make of the "Raw_Read_Error_Rate" root@Tower:/tmp# diff smart_start2036 smart_finish2036 |more 54c54 < 1 Raw_Read_Error_Rate 0x000f 117 099 006 Pre-fail Always - 143105661 --- > 1 Raw_Read_Error_Rate 0x000f 114 099 006 Pre-fail Always - 78689498 58c58 < 7 Seek_Error_Rate 0x000f 075 060 030 Pre-fail Always - 36206913 --- > 7 Seek_Error_Rate 0x000f 075 060 030 Pre-fail Always - 36319190 And running smartctl --all /dev/sdd gives User Capacity: 1,000,204,886,016 bytes Device is: Not in smartctl database [for details use: -P showall] ATA Version is: 8 ATA Standard is: ATA-8-ACS revision 4 Local Time is: Wed Jan 5 00:26:03 2011 MST SMART support is: Available - device has SMART capability. SMART support is: Enabled ... SMART Attributes Data Structure revision number: 10 Vendor Specific SMART Attributes with Thresholds: ID# ATTRIBUTE_NAME FLAG VALUE WORST THRESH TYPE UPDATED WHEN_FAILED RAW_VALUE 1 Raw_Read_Error_Rate 0x000f 114 099 006 Pre-fail Always - 78711073 3 Spin_Up_Time 0x0003 100 100 000 Pre-fail Always - 0 4 Start_Stop_Count 0x0032 100 100 020 Old_age Always - 101 5 Reallocated_Sector_Ct 0x0033 095 095 036 Pre-fail Always - 216 7 Seek_Error_Rate 0x000f 075 060 030 Pre-fail Always - 36349186 9 Power_On_Hours 0x0032 089 089 000 Old_age Always - 9676 10 Spin_Retry_Count 0x0013 100 100 097 Pre-fail Always - 0 12 Power_Cycle_Count 0x0032 100 037 020 Old_age Always - 101 ... SMART Error Log Version: 1 No Errors Logged ... There are a lot of Raw_Read_Error_Rate however it went down?

Sure, post here or PM me with attachment.

Looks like you're right about that, 'fdisk -l' no longer shows sda. I'll reboot once the other drive is done with preclear'ing.

I am getting similar results (after 45 hours) like this on a WD Green 2TB drive (no jumpers) The difference is that I get out4= 00000 and out5= 00000, 0+0 records in & out, 0 bytes copied. I tried some commands and got a script error... root@Tower:/boot/config# ./preclear_disk.sh -v ./preclear_disk.sh version: .9.8 root@Tower:/boot/config# ./preclear_disk.sh -t /dev/sda Pre-Clear unRAID Disk ######################################################################## ######################################################################## ./preclear_disk.sh: line 825: [: too many arguments ============================================================================ == == Disk /dev/sda is NOT precleared == ============================================================================ I was running this pre-clear at the same time as other disks. Should I try again by itself? Is there a way to bypass *all* the tests? BTW, I did not jumper it because I am setting things up to get ready for 5.0b3 to support these WD Green drives.