prostuff1

my suggestion would be to run another preclear and see if it changes again, how much closer it gets to the threshold, and what that new number is.

preclear does not format anything, unRAID itself has to do the formatting. So long as it is the only drive showing unformatted you can click the format button.

Depends on the power supply but if you get a single rail PSU likes the ones described above then you will have to leave headroom for the motherboard and the like.

look here. The user reformatted the flash drive and reassigned all drives after booting 4.7 and everything worked for him.

I would run the slow drive through 2 more cycles. I run all my drives through 3 total cycles, but the slow one should be run again.

Let it complete and then figure it out. With three drives all going at the same time it might just be a fact that they are completing for resources.

you are running 5.0b4 and it had issues with the way disks were recognized. This was discussed ad nauseum in the announcements thread, and the main reason 5.0b5, etc change the way disks were discovered. If I had to guess at what happened, your computer restarted, disks were discovered in a different order, unRAID found the "new" disk in the old ones spot, and thought you were trying to upgrade it. Since it is an upgrade, preclear does not really matter for that drive. unRAID is coping over the data and everything else. Using preclear for an upgrade drive does nothing more than to torture test the drive. If this is not a test array please consider running 4.7 until the 5.0 betas have been tested by those with test arrays, or are experienced with linux/unRAID.

Both

No they are fine.

This setting is fine This should be AHCI This should be disabled

They have not carried servers for a while, but there homepage says there should be a server available in Q1 2011 for shipping. If you need one built Rajahal or myself are willing to build a server for you so long as you are in the united states. Just send us a private message if your interested.

Its fine, nothing to worry about. I just finished 3 cycles each on 2 drives and my results were almost identical.

My Dell test server does, but I don't have the case speaker hooked up to my production server to test. It is an interesting idea and I think one that I will mess with when I get some free time.

The above is normal. Those are all child processes of the cache_dirs script.

Do you have any IDE disks in your system? If not then that disk you just successfully cleared is presenting itself as IDE. There is more than likely a setting in your BIOS that is setting the ports that drive is on to emulate and IDE connection. Beside that the drive looks fine.

It would be simple enough to create one, you could probably do it!! The link above that you download the .tgz file at is really all you need. Take a look at he 'dmidecode' conf file and edit it as need be. There is really not a lot to it. If I get a chance to do it up quick I will, but I am busy with other things right now.

Check in your BIOS for settings related to IDE for the SATA chipset. you want to set the "mode" on the chipset to AHCI for best and native SATA performance.

I have one of the above cards in a system I am building for a client and it worked no problem. did not have to change a thing to get it to see the drives. I can add the drives to unRAID and everything works fine.

If your in the US try Monoprice

Try it with -i "TV Shows" or if that does not work try -i TV\ Shows

The User Contributed Wiki is editable by anyone. Feel free to create an account on the wiki site and edit to your hearts content. We update when and where we can, but it is just like any other documentation and can get out of date.

What do we always say... It's not a matter of if the drive will fail, it is a matter of when the drive will fail. I am a prefect example of this at the very moment. I had a 1.5TB Seagate I ran 3 preclear cycles on. The first changed some stuff so I ran one more. Nothing changed with this one, but I wanted to make sure that nothing else funky was going to happen so I ran one more preclear cycle. Nothing change between 2 and 3 so i added the drive to the array. Yesterday something happened with that drive and now it is going back for RMA.

Open the file in Windows with a text editor that is linux friendly. Notepad++ and EditPad Lite are two that are free and work well. Once you open the file there should be a menu option to "Convert to linux" or something along those lines.

Your wish is my command: root@TestTower:~# smartctl -a -d ata /dev/sda smartctl version 5.38 [i486-slackware-linux-gnu] Copyright (C) 2002-8 Bruce Allen Home page is http://smartmontools.sourceforge.net/ === START OF INFORMATION SECTION === Model Family: Western Digital Caviar SE Serial ATA family Device Model: WDC WD1200JD-75GBB0 Serial Number: WD-WMAET1372951 Firmware Version: 02.05D02 User Capacity: 120,000,000,000 bytes Device is: In smartctl database [for details use: -P show] ATA Version is: 6 ATA Standard is: Exact ATA specification draft version not indicated Local Time is: Mon Mar 8 10:40:48 2010 EST 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: FAILED! Drive failure expected in less than 24 hours. SAVE ALL DATA. See vendor-specific Attribute list for failed Attributes. 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: ( 121) The previous self-test completed having the read element of the test failed. Total time to complete Offline data collection: (3796) seconds. Offline data collection capabilities: (0x79) SMART execute Offline immediate. No Auto Offline data collection 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. No General Purpose Logging support. Short self-test routine recommended polling time: ( 2) minutes. Extended self-test routine recommended polling time: ( 53) minutes. Conveyance self-test routine recommended polling time: ( 5) minutes. 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 0x000b 001 001 051 Pre-fail Always FAILING_NOW 31473 3 Spin_Up_Time 0x0007 146 144 021 Pre-fail Always - 3241 4 Start_Stop_Count 0x0032 100 100 040 Old_age Always - 388 5 Reallocated_Sector_Ct 0x0033 187 187 140 Pre-fail Always - 195 7 Seek_Error_Rate 0x000b 200 200 051 Pre-fail Always - 0 9 Power_On_Hours 0x0032 060 060 000 Old_age Always - 29218 10 Spin_Retry_Count 0x0013 100 100 051 Pre-fail Always - 0 11 Calibration_Retry_Count 0x0013 100 100 051 Pre-fail Always - 0 12 Power_Cycle_Count 0x0032 100 100 000 Old_age Always - 387 194 Temperature_Celsius 0x0022 107 253 000 Old_age Always - 43 196 Reallocated_Event_Count 0x0032 178 178 000 Old_age Always - 22 197 Current_Pending_Sector 0x0012 165 165 000 Old_age Always - 695 198 Offline_Uncorrectable 0x0012 176 176 000 Old_age Always - 485 199 UDMA_CRC_Error_Count 0x000a 200 253 000 Old_age Always - 0 200 Multi_Zone_Error_Rate 0x0009 134 155 051 Pre-fail Offline - 2136 SMART Error Log Version: 1 ATA Error Count: 27583 (device log contains only the most recent five errors) CR = Command Register [HEX] FR = Features Register [HEX] SC = Sector Count Register [HEX] SN = Sector Number Register [HEX] CL = Cylinder Low Register [HEX] CH = Cylinder High Register [HEX] DH = Device/Head Register [HEX] DC = Device Command Register [HEX] ER = Error register [HEX] ST = Status register [HEX] Powered_Up_Time is measured from power on, and printed as DDd+hh:mm:SS.sss where DD=days, hh=hours, mm=minutes, SS=sec, and sss=millisec. It "wraps" after 49.710 days. Error 27583 occurred at disk power-on lifetime: 807 hours (33 days + 15 hours) When the command that caused the error occurred, the device was doing SMART Offline or Self-test. After command completion occurred, registers were: ER ST SC SN CL CH DH -- -- -- -- -- -- -- 40 51 08 01 00 00 e0 Error: Commands leading to the command that caused the error were: CR FR SC SN CL CH DH DC Powered_Up_Time Command/Feature_Name -- -- -- -- -- -- -- -- ---------------- -------------------- 00 00 c8 00 00 08 00 00 1d+09:48:57.450 NOP [Abort queued commands] 00 00 00 00 00 00 00 00 1d+09:48:57.450 NOP [Abort queued commands] 00 00 ef 00 00 45 00 00 1d+09:48:57.450 NOP [Abort queued commands] 00 00 00 00 00 00 00 00 1d+09:48:57.450 NOP [Abort queued commands] Error 27582 occurred at disk power-on lifetime: 803 hours (33 days + 11 hours) When the command that caused the error occurred, the device was active or idle. After command completion occurred, registers were: ER ST SC SN CL CH DH -- -- -- -- -- -- -- 40 51 08 ed 1d 4a e5 Error: Commands leading to the command that caused the error were: CR FR SC SN CL CH DH DC Powered_Up_Time Command/Feature_Name -- -- -- -- -- -- -- -- ---------------- -------------------- 00 00 c8 00 00 08 00 00 1d+05:40:44.100 NOP [Abort queued commands] 00 00 00 00 00 00 00 00 1d+05:40:44.100 NOP [Abort queued commands] 00 00 ef 00 00 44 00 00 1d+05:40:44.100 NOP [Abort queued commands] 00 00 00 00 00 00 00 00 1d+05:40:44.100 NOP [Abort queued commands] 00 00 c8 00 00 08 00 00 1d+05:40:44.100 NOP [Abort queued commands] Error 27581 occurred at disk power-on lifetime: 803 hours (33 days + 11 hours) When the command that caused the error occurred, the device was active or idle. After command completion occurred, registers were: ER ST SC SN CL CH DH -- -- -- -- -- -- -- 40 51 08 ed 1d 4a e5 Error: Commands leading to the command that caused the error were: CR FR SC SN CL CH DH DC Powered_Up_Time Command/Feature_Name -- -- -- -- -- -- -- -- ---------------- -------------------- 00 00 c8 00 00 08 00 00 1d+05:40:42.000 NOP [Abort queued commands] 00 00 00 00 00 00 00 00 1d+05:40:42.000 NOP [Abort queued commands] 00 00 ef 00 00 44 00 00 1d+05:40:42.000 NOP [Abort queued commands] 00 00 00 00 00 00 00 00 1d+05:40:42.000 NOP [Abort queued commands] 00 00 c8 00 00 08 00 00 1d+05:40:42.000 NOP [Abort queued commands] Error 27580 occurred at disk power-on lifetime: 803 hours (33 days + 11 hours) When the command that caused the error occurred, the device was active or idle. After command completion occurred, registers were: ER ST SC SN CL CH DH -- -- -- -- -- -- -- 40 51 08 ed 1d 4a e5 Error: Commands leading to the command that caused the error were: CR FR SC SN CL CH DH DC Powered_Up_Time Command/Feature_Name -- -- -- -- -- -- -- -- ---------------- -------------------- 00 00 c8 00 00 08 00 00 1d+05:40:39.850 NOP [Abort queued commands] 00 00 00 00 00 00 00 00 1d+05:40:39.850 NOP [Abort queued commands] 00 00 ef 00 00 44 00 00 1d+05:40:39.850 NOP [Abort queued commands] 00 00 27 00 00 00 00 00 1d+05:40:39.850 NOP [Abort queued commands] 05 00 4a 00 00 e8 1d 00 1d+05:40:39.850 [RESERVED] Error 27579 occurred at disk power-on lifetime: 803 hours (33 days + 11 hours) When the command that caused the error occurred, the device was active or idle. After command completion occurred, registers were: ER ST SC SN CL CH DH -- -- -- -- -- -- -- 40 51 08 ed 1d 4a e5 Error: Commands leading to the command that caused the error were: CR FR SC SN CL CH DH DC Powered_Up_Time Command/Feature_Name -- -- -- -- -- -- -- -- ---------------- -------------------- 00 00 c8 00 00 08 00 00 1d+05:40:37.750 NOP [Abort queued commands] 00 00 00 00 00 00 00 00 1d+05:40:37.750 NOP [Abort queued commands] 00 00 ef 00 00 44 00 00 1d+05:40:37.750 NOP [Abort queued commands] 00 00 00 00 00 00 00 00 1d+05:40:37.750 NOP [Abort queued commands] 00 00 c8 00 00 08 00 00 1d+05:40:37.750 NOP [Abort queued commands] SMART Self-test log structure revision number 1 Num Test_Description Status Remaining LifeTime(hours) LBA_of_first_error # 1 Extended offline Completed: read failure 90% 774 122951383 # 2 Short offline Completed without error 00% 430 - # 3 Short offline Completed without error 00% 0 - 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.

It's funny how it estimates its remaining lifetime to be 4 days. Call us back in four days, will you? It was close, and it may have lasted had I not tried to run prelcear on it. I had it running, and it was taking its good sweet time. The drive was so SOL that it was going on the 48 hour mark and was only done with 50% of the first step in preclear. I gave up on it and cancelled the preclear. I am going to take it apart tonight to see what is inside the drive.