jimwhite

Another thing to consider is the power supply design. Ideally you want a "single-rail" power supply, that is it has a single 12volt supply, not two or three. I had an OCZ 650 watt supply with two rails. One supplied the mother board, one supplied the peripheral (drive) cables. It supplied less current to the drives than an older single rail 430 watt supply. With the 650, all was well until I hit the button to spin-up all (10) drives from spin-down. The server would reboot! I've since replaced it with a Corsair 750w single rail supply, it happily will spin up 14 drives, and is >80% efficient from 20-100% load.

cool... thanks a lot Tom.... Go Buc's, Go Rays

Do you mean a separate partition on one of your data drives? If so, no. But, you can use the 'fdisk' command to manually create multiple partitions on your cache drive and unRAID will use partition 1 (so you have to have a partition 1). But you could then use other partitions on that drive for non-unRAID purposes. If you want to do this though, you have to also manually create the ReiserFS file system in partition 1 as well before assigning the drive as the Cache drive to prevent System Management utility from wanting to format it (which will also create a new partition table). Note this will work only with the Cache drive, not the parity/data drives. Make sense? okay, I've got this working now but, as usual, unintended consequences... can we have a radio button or something on the settings page to disable the cache drive from the "spindown" button on the main page? Also, if a process outside the array is using another partition on the "cache drive", is unraid smart enough to not automatically spin it down?

I was referring to fan speed threshold, not CPU temp.... are you running a "stock" heatsink/fan? Some aftermarket units spin down to below 900 rpm which is problamatic on some MB's, notably my AB9pro.... some BIOS' allow setting this to as low as 600 rpm, many don't...

the wah-wah speaker sound MIGHT be related to a CPU fan with faulty sensor or one that spins down too low for the bios' threshold...

ooooppppss..... I meant 1 hour

can we remove the spindown stuff now that Tom has reverted 4.4 back to the "good" logic? Also, we have times below 1 minute now with 4.4. Ref the spindown time, is a blank entry a "disable" ?

perfect sense and perfect answer

Tom, is there any way the Cache drive portion could be mod'd to allow mounting of a partition on a drive as cache instead of requiring the entire drive?

yes, my unraid has visibility to my cable router...

Looks like 4.4b2 broke the temperature readings in unmenu. Probably due to the Smartmontools update from 5.36 to 5.38 Edit... smartctl doesn't work at all.... the c++ library needs to be updated. Edit2... yup, loaded the cxxlibs-6.0.8-i486-4 pkg and all is well.... Tom, you need them for beta 3

sorry I didn't answer sooner... Weebotech helped me getting 5.38 installed, and yes, indeed it works fine

Now we just need a 64bit version Hmmmmm.... I wonder if it would work on SLAMD64

Thanx

Tom, can you update Smartcontrol in the next release? The current 5.36 does not run tests correctly on my Seagate 1 tb drives

Since this is a Seagate 1tb and even 4.4b1 uses ver 5.36 of Smartctl, I'm stuck.... it won't run tests on the Seagates.

One of my new Seagate 1 TB drives shows 8 Smart errors which seem to have occurred at about 90 hours. I have a suspicion it may have been a case of poor cabling to the drive, but cannot be sure. Can someone more knowledgeable take a look at the smart report below and comment? Statistics for /dev/sdk ST31000340AS_9QJ1BJB2 smartctl version 5.36 [i486-slackware-linux-gnu] Copyright (C) 2002-6 Bruce Allen Home page is http://smartmontools.sourceforge.net/ === START OF INFORMATION SECTION === Device Model: ST31000340AS Serial Number: 9QJ1BJB2 Firmware Version: SD15 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: Not recognized. Minor revision code: 0x29 Local Time is: Mon Sep 29 14:03:44 2008 GMT+4 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: (0x82) Offline data collection activity was completed without error. Auto Offline Data Collection: Enabled. 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: ( 625) seconds. Offline data collection capabilities: (0x7b) SMART execute Offline immediate. Auto Offline data collection on/off 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. General Purpose Logging supported. Short self-test routine recommended polling time: ( 1) minutes. Extended self-test routine recommended polling time: ( 232) minutes. Conveyance self-test routine recommended polling time: ( 2) minutes. 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 117 100 006 Pre-fail Always - 135301548 3 Spin_Up_Time 0x0003 091 089 000 Pre-fail Always - 0 4 Start_Stop_Count 0x0032 100 100 020 Old_age Always - 72 5 Reallocated_Sector_Ct 0x0033 100 100 036 Pre-fail Always - 84 7 Seek_Error_Rate 0x000f 066 060 030 Pre-fail Always - 4688826 9 Power_On_Hours 0x0032 100 100 000 Old_age Always - 727 10 Spin_Retry_Count 0x0013 100 100 097 Pre-fail Always - 2 12 Power_Cycle_Count 0x0032 100 037 020 Old_age Always - 47 184 Unknown_Attribute 0x0032 100 100 099 Old_age Always - 0 187 Unknown_Attribute 0x0032 092 092 000 Old_age Always - 8 188 Unknown_Attribute 0x0032 100 100 000 Old_age Always - 0 189 Unknown_Attribute 0x003a 100 100 000 Old_age Always - 0 190 Unknown_Attribute 0x0022 058 058 045 Old_age Always - 706215978 194 Temperature_Celsius 0x0022 042 042 000 Old_age Always - 42 (Lifetime Min/Max 0/23) 195 Hardware_ECC_Recovered 0x001a 037 030 000 Old_age Always - 135301548 197 Current_Pending_Sector 0x0012 100 100 000 Old_age Always - 0 198 Offline_Uncorrectable 0x0010 100 100 000 Old_age Offline - 0 199 UDMA_CRC_Error_Count 0x003e 200 200 000 Old_age Always - 0 SMART Error Log Version: 1 ATA Error Count: 8 (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 8 occurred at disk power-on lifetime: 95 hours (3 days + 23 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 00 ff ff ff 0f Commands leading to the command that caused the error were: CR FR SC SN CL CH DH DC Powered_Up_Time Command/Feature_Name -- -- -- -- -- -- -- -- ---------------- -------------------- 60 00 00 ff ff ff 4f 00 10:08:48.335 [RESERVED FOR SERIAL ATA] 60 00 00 ff ff ff 4f 00 10:08:48.335 [RESERVED FOR SERIAL ATA] 60 00 00 ff ff ff 4f 00 10:08:48.333 [RESERVED FOR SERIAL ATA] 27 00 00 00 00 00 e0 00 10:08:48.333 READ NATIVE MAX ADDRESS EXT ec 00 00 00 00 00 a0 00 10:08:48.332 IDENTIFY DEVICE Error 7 occurred at disk power-on lifetime: 95 hours (3 days + 23 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 00 ff ff ff 0f Commands leading to the command that caused the error were: CR FR SC SN CL CH DH DC Powered_Up_Time Command/Feature_Name -- -- -- -- -- -- -- -- ---------------- -------------------- 60 00 00 ff ff ff 4f 00 10:08:45.370 [RESERVED FOR SERIAL ATA] 60 00 00 ff ff ff 4f 00 10:08:45.370 [RESERVED FOR SERIAL ATA] 60 00 00 ff ff ff 4f 00 10:08:45.368 [RESERVED FOR SERIAL ATA] 27 00 00 00 00 00 e0 00 10:08:45.368 READ NATIVE MAX ADDRESS EXT ec 00 00 00 00 00 a0 00 10:08:45.366 IDENTIFY DEVICE Error 6 occurred at disk power-on lifetime: 95 hours (3 days + 23 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 00 ff ff ff 0f Commands leading to the command that caused the error were: CR FR SC SN CL CH DH DC Powered_Up_Time Command/Feature_Name -- -- -- -- -- -- -- -- ---------------- -------------------- 60 00 00 ff ff ff 4f 00 10:08:42.397 [RESERVED FOR SERIAL ATA] 60 00 00 ff ff ff 4f 00 10:08:42.396 [RESERVED FOR SERIAL ATA] 60 00 00 ff ff ff 4f 00 10:08:42.395 [RESERVED FOR SERIAL ATA] 27 00 00 00 00 00 e0 00 10:08:42.394 READ NATIVE MAX ADDRESS EXT ec 00 00 00 00 00 a0 00 10:08:42.393 IDENTIFY DEVICE Error 5 occurred at disk power-on lifetime: 95 hours (3 days + 23 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 00 ff ff ff 0f Commands leading to the command that caused the error were: CR FR SC SN CL CH DH DC Powered_Up_Time Command/Feature_Name -- -- -- -- -- -- -- -- ---------------- -------------------- 60 00 00 ff ff ff 4f 00 10:08:39.448 [RESERVED FOR SERIAL ATA] 60 00 00 ff ff ff 4f 00 10:08:38.382 [RESERVED FOR SERIAL ATA] 60 00 00 ff ff ff 4f 00 10:08:38.382 [RESERVED FOR SERIAL ATA] 60 00 00 ff ff ff 4f 00 10:08:38.380 [RESERVED FOR SERIAL ATA] 27 00 00 00 00 00 e0 00 10:08:38.379 READ NATIVE MAX ADDRESS EXT Error 4 occurred at disk power-on lifetime: 95 hours (3 days + 23 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 00 ff ff ff 0f Commands leading to the command that caused the error were: CR FR SC SN CL CH DH DC Powered_Up_Time Command/Feature_Name -- -- -- -- -- -- -- -- ---------------- -------------------- 60 00 00 ff ff ff 4f 00 10:08:35.458 [RESERVED FOR SERIAL ATA] 60 00 00 ff ff ff 4f 00 10:08:35.458 [RESERVED FOR SERIAL ATA] 60 00 00 ff ff ff 4f 00 10:08:35.456 [RESERVED FOR SERIAL ATA] 27 00 00 00 00 00 e0 00 10:08:35.456 READ NATIVE MAX ADDRESS EXT ec 00 00 00 00 00 a0 00 10:08:35.455 IDENTIFY DEVICE SMART Self-test log structure revision number 1 No self-tests have been logged. [To run self-tests, use: smartctl -t] 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.

Q6600 quad here.... boots without a hiccup, everything seems okay so far... as a plus, the "usual" Abit AB9pro ACPI errors in the syslog are conspicuous in their absence syslog attached

Kewel!!

As for creating VM's, go to http://easyvmx.com/.... easy on-line creation I'd like to see packages and support for Slim/Squeeze Server and a upnp server for music content....

Both good choices... go fer it !!!

You guys crack me up....

seems this thread has enough valuable info to be moved to the user customization thread, no?

Agreed, but get 2x2gb, not 4x1gb sticks so you have the 2 extra slots when you need them later

BTW, if you sign up for Microsoft Live! you get a 5gb "Skydrive" for free....