Helmonder

Thanks !!

Is it possible to reconfigure emhttp to default to another port then 80 ? I have a lot of stuff running on the system and would to have a base mainpage to route to the different functions of the system, ofcourse I know I can also do that thru another port but I would prefer having my "overall main page" on port 80.

Thats exactly what it said... Human error is the easiest reason, maybe I have forgotten to set screen or I did it wrong... I'll test it out when I restart the preclear.

screen -r did not bring anything... weird... I'll have to try again, had to reboot.

Mmm... my telnetdaemon just died on me, preclear is running in SCREEN but I cannot get to it without telnet.. I started it up wit the parameter that prevents writing of info in the preclear results directory (also no email alerts), is there any way now for me to know if preclear is still running and what the results are when it is finished ? If not I will hook up a monitor and keyboard and check on console, but it is kind of a hassle, so if there is another way ? Maybe the end result will get written to the preclear results directory anyway ? EDIT: Just hooked up a monitor, seems like there is no SCREEN to reattach, therefor I will assume that preclear has terminated.. Can someone confirm that SCREEN is tied to the running telnetdaemon process and that therefor a SCREEN session will be lost when the telnetdaemon dies ?

Using mcafee saas.. happy with it, never any issues..

Most bioses have an option for "resume on powerloss". Whenever power is gone you can choose between "on / off / last state". If you put that on "on" and setup a cheap power/timer clock between pc and wall socket you can get what you want : 01:00 shut down array and power down system 01:30 cut power using the timer 06:00 restore power using timer On restore of power system will turn on abd boot into unraid. What is my major issue with this is that I allmost always have to do manual stuff to get the system to shudown without a parity check on restart.

Thanks !

A week or so ago I noticed that one of my drives (disk1) was showing sectors pending reallocation, the disk was also one of my oldest and has made over 20,000 hours. I figured a replace was in order, I have been running flawlessly with v5b14 and want to be ready for the future, a 3TB replacement was in order. I started a replacement caroussel: - Bought new 3TB Hitachi - Precleared 3TB with 3 cycles, flawless ! - Replaced 2TB parity (that was flawless) with 3TB - Precleared old parity 2TB 3 cycles, flawless ! - Replaced my "failing" disk1 with the old parity disk Everything worked as expected, no stress ! Then I started a 3 cycle preclear on the old disk1 fully expecting to have it "fail" on me. Results were as followed: ============================================================================ ** Changed attributes in files: /tmp/smart_start_sdd /tmp/smart_finish_sdd ATTRIBUTE NEW_VAL OLD_VAL FAILURE_THRESHOLD STATUS RAW_VALUE Temperature_Celsius = 117 125 0 ok 35 No SMART attributes are FAILING_NOW 4 sectors were pending re-allocation before the start of the preclear. 4 sectors were pending re-allocation after pre-read in cycle 1 of 3. 0 sectors were pending re-allocation after zero of disk in cycle 1 of 3. 0 sectors were pending re-allocation after post-read in cycle 1 of 3. 0 sectors were pending re-allocation after zero of disk in cycle 2 of 3. 1 sector was pending re-allocation after post-read in cycle 2 of 3. 0 sectors were pending re-allocation after zero of disk in cycle 3 of 3. 0 sectors are pending re-allocation at the end of the preclear, a change of -4 in the number of sectors pending re-allocation. 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. My question: Should I continue to use the old disk1 or should I retire it ? More then happy to add it to the array for extra space (though I do not really need it at the moment. What confuses me is that there are changes in re-allocation during the cycle but preclear states it has "passed". I thought that such "changing" behavious most likely pointed towards a disk going to fail ? Current SMART report: ID# ATTRIBUTE_NAME FLAG VALUE WORST THRESH TYPE UPDATED WHEN_FAILED RAW_VALUE 1 Raw_Read_Error_Rate 0x002f 200 200 051 Pre-fail Always - 75 3 Spin_Up_Time 0x0027 142 142 021 Pre-fail Always - 9875 4 Start_Stop_Count 0x0032 100 100 000 Old_age Always - 443 5 Reallocated_Sector_Ct 0x0033 200 200 140 Pre-fail Always - 0 7 Seek_Error_Rate 0x002e 200 200 000 Old_age Always - 0 9 Power_On_Hours 0x0032 072 072 000 Old_age Always - 21114 10 Spin_Retry_Count 0x0032 100 100 000 Old_age Always - 0 11 Calibration_Retry_Count 0x0032 100 253 000 Old_age Always - 0 12 Power_Cycle_Count 0x0032 100 100 000 Old_age Always - 86 192 Power-Off_Retract_Count 0x0032 200 200 000 Old_age Always - 40 193 Load_Cycle_Count 0x0032 107 107 000 Old_age Always - 281502 194 Temperature_Celsius 0x0022 116 090 000 Old_age Always - 36 196 Reallocated_Event_Count 0x0032 200 200 000 Old_age Always - 0 197 Current_Pending_Sector 0x0032 200 200 000 Old_age Always - 0 198 Offline_Uncorrectable 0x0030 200 200 000 Old_age Offline - 0 199 UDMA_CRC_Error_Count 0x0032 200 200 000 Old_age Always - 0 200 Multi_Zone_Error_Rate 0x0008 200 175 000 Old_age Offline - 0 SMART Error Log Version: 1 No Errors Logged SMART Self-test log structure revision number 1 Num Test_Description Status Remaining LifeTime(hours) LBA_of_first_error # 1 Short offline Completed: read failure 90% 20488 1470867921 # 2 Extended offline Completed: read failure 90% 20196 1470867921 # 3 Short offline Completed without error 00% 20124 - # 4 Short offline Completed without error 00% 20030 -

Reallocated sectors are not a good sign, I would not use this disk in your unraid system. The number is also quite high, some people would advise to do a few more preclear cycles on the disk to see if the system is stable with this amount of errors or deteriorates. Most however do agree in just not using these disks, in most cases this is a sign of a disk that is going to fail on the short term.

I am tempted to say no... I have spent some time browsing the forums on SMART results, what I have come to understand is that what your drive is doing could possibly be ok, but parts of the drive ARE failing so it comes down to wanting to take a risk... Looking at the prices of disks I would advise taking out this disk, using it for some other kind of storage (its not broken yet) and replace your unraid drive with a fresh one that comes out of multuple preclear cycles without any issues..

Looks good.

Interesting, but the preclear script does nothing that the unRAID array will do itself when calculating parity or re-constructing a failed drive. It reads and write to the failed disk. (exactly like a parity check/calc or disk re-construction, it reads/writes the entire disk) The preclear script does invoke the smartctl program on the drive hundreds/thousands of times on the drive. unRAID uses native system calls to do the same. That is the only significant difference. The hardware will likely cause you the same errors once you put the disk into service. I wish you luck but I have nothing to suspect anything other than a bad drive. I've seen drives stop responding before... It seems like this is a case of this. We'll soon see. As you said, unRAID is clearing your drive. I would, if I were you, once assigned, see if you can get through a manual parity check. Joe L. Hi, I did just that, all ok. Also SMART results are ok, with small and large test, no significant errors. The fact that you mention that the script does the same action but thru different calls sounds like the reason to me.. Also note that some other users had the exact same issue.. Disk is performing without an issue, I'll check back in a couple of weeks to confirm ! UPDATE: Disk got thrown out of the array, totally failed.. Checking it on a windows box with the correct western digital analysis tool also told me to contact tech support.. So drive was indeed kaput.. Preclearing the new drive resulted in a load of red errors again but only for a few minutes, after that it went on, drive has now been in for several days and is working beautifully (store gave me a new one right away).

I had some kind of serious issues using the preclear script, I am linking to the thread describing them: http://lime-technology.com/forum/index.php?topic=18896.0