papnikol

Thanks for your prompt response, it works. It is difficult to follow all this stuff if you get out of touch for a few months. Does the same patch work on the bjp666 script? i.e. could i try sed -i -e "s/print \$9 /print \$8 /" -e "s/sfdisk -R /blockdev --rereadpt /" preclear_bjp.sh instead of sed -i -e "s/print \$9 /print \$8 /" -e "s/sfdisk -R /blockdev --rereadpt /" preclear_disk.sh ?

I tried using the JoeL or bjp666 preclear scripts since the webgui gfjardim script is currently not working. I get errors with both of them. Have they become obsolete for Unraid 6.5?

Hi. I run diskspeed for a controller that has 8 disks attached (attached file). The controller is an AOC-SASLp-MV8 (PCIe x4). Do those results indicate that the 4x PCIe lanes are saturated by the 4 first drives? Or could it be something else?

In network settings, try setting a static DNS addresses of 8.8.8.8 and 8.8.4.4 and try again thanks, that solved the problem, although I do not understand why Google's DNS is helping

Hi, I am tryin to install the plugin through the unRAID Plugin Manager I get the following: plugin: installing: https://raw.githubusercontent.com/theone11/serverlayout_plugin/master/serverlayout-package-2015.09.25.tar.gz plugin: downloading https://raw.githubusercontent.com/theone11/serverlayout_plugin/master/serverlayout-package-2015.09.25.tar.gz plugin: downloading: https://raw.githubusercontent.com/theone11/serverlayout_plugin/master/serverlayout-package-2015.09.25.tar.gz ... done Warning: simplexml_load_file(): /tmp/plugins/serverlayout-package-2015.09.25.tar.gz:1: parser error : Start tag expected, '<' not found in /usr/local/emhttp/plugins/dynamix.plugin.manager/scripts/plugin on line 193 Warning: simplexml_load_file(): ??V in /usr/local/emhttp/plugins/dynamix.plugin.manager/scripts/plugin on line 193 Warning: simplexml_load_file(): ^ in /usr/local/emhttp/plugins/dynamix.plugin.manager/scripts/plugin on line 193 plugin: xml parse error Can someone help?

Hi NAS I was wondering if you have found a solution. I seem to have a similar problem with you. After I used mc, my previously funtional cache_dirs command: cache_dirs -d 2 -m 3 -M 4 -w -F never stops. I even tried to decrease the depth but to no avail. I wonder if you have found a solution. PS: I have 2.5GB of ram (and 1.5 GB seem to be free) and i am using cache_dirs 1.6.5. i also get this: Executed find in 838.856452 seconds, weighted avg=841.972656 seconds, now sleeping 4 seconds which I know is normal but I thought it was supposed to start after cache_dirs has fully scanned my disks

thing is, most of the market wont do any kind of testing. unraid is a small niche of people who will do that but most common people wont test the hard drive. most shops that will sell you a custom pc wont do any testing either. Also, fixing the drives might cost but, in the long run, replacing them could cost more (although i guess they estimate that).

Looks good ya? Took a while Elapsed Time: 74:50:01 seems ok to me. but 3 days? it takes 25-30hrs for a 2TB WD EARS in my pc (and it is quite old, sata I - not that it makes any much difference) when nothing else is running

come to think of it now, isnt that supposed to be one of the seagate drives that cave to have their firmware update because of the "click of death" issue? If it came with the old firmware, that might be your problem. I hope you now understand how important and useful preclear is, Joe (just kidding)

larson might have a point. although i could not think of a practical solution, i have a possible conspiracy theory explanation: is it possible that this drive has been actually used before, returned and then sent again as new? that would explain your problems...

There generally seems to be a problem with EARS and unraid. i have noticed that many-many times in the forums. i, personally, had problems with 2 EARS drives (fresh from the box and jumpered). they would get stuck always at the same point of preclear. i tried unjumpering, i performed extensive smart and factory tests, i even tried SpinRite and they showed no errors. But they lock in unraid (at least in preclear). Obviously, i did not want to risk it so i RMA'd them....

i assume the system crashed so you had to restart. the drive wont be listed in the webgui anyways since it is not part of the array. you should be able to see it in Joe's unMenu or if you connect with telnet. if you still cannot see it there, i would guess, that the drive is either faulty or your sata cable should be resitted. to be sure, check if you can see it through the BIOS.

Joe, i hope you are not implying that you have created regular expressions to automatically answer to our posts. Even you cannot be THAT good?

this seems hardware related. Have you tried a memtest?

Hi Joe I was trying to preclear an EARS 2T and i got the same error i have had with the same type of disk some time ago: it stoped at a point during preread and when i try again to precleal i get the message: /boot/preclear_disk.sh: line 550: 1+( 2556951756)%() : syntax error: operand expected (error token is ") ") Would you happen to have an update as to why this error occurs? is it preclear-related or would i have had the same kind of problem if i had put it straight to the array? PS:I have two other 2Tb EARS HDDs that were precleared with no problems...

Userpaul, it seems your rig has created a lot of envy which 8 port sata cards are you using? I myself am using the saslp-mv8 and they get quite hot. so, i was wondering where you got those fans that fit underneath the saslp? UPDATE: i found some in amazon.co.uk ( i live in europe using keywords: pci + fan) http://www.amazon.co.uk/s/ref=nb_sb_noss?url=search-alias%3Daps&field-keywords=pci+fan&x=0&y=0 So i am just wondering if yours is silent? if yes i would rather buy the same type as yours than a fan about which i know nothing... I have the same cards as you I bought mine from the local Maplin store just up the road (impulse purchase). Whilst I was preclearing my HDD's I noticed that the saslp-mv8 cards got very very hot so I had a fan propped on the psu cooling them down. These are the fans. http://www.maplin.co.uk/Module.aspx?ModuleNo=28679 Both fans are controlled with the Skythe fan speed controller and I have a temp sensor on each card. The fans reduce the temps of the cards by around 20 C The advantage of having the fans managed by the Skythe controller is I can strike a balance between fan speed and noise level. I plan to install a small fan onto the heatsink and I am currently looking at kits to do that. thanx for the info unfortunately this creates more questions (at least to me): 1. the temp sensor is something that comes with the fan speed controller or something you bought separately? 2. i have never had a fan controller but i was thinking of buying one. How does it work? does it provide power straight to the fan thus working like a dimmer?

Userpaul, it seems your rig has created a lot of envy which 8 port sata cards are you using? I myself am using the saslp-mv8 and they get quite hot. so, i was wondering where you got those fans that fit underneath the saslp? UPDATE: i found some in amazon.co.uk ( i live in europe using keywords: pci + fan) http://www.amazon.co.uk/s/ref=nb_sb_noss?url=search-alias%3Daps&field-keywords=pci+fan&x=0&y=0 So i am just wondering if yours is silent? if yes i would rather buy the same type as yours than a fan about which i know nothing...

Yes, you can

@Tom899 & MvL: You can preclear up to 6 disk simultaneously (according to Joe, I myself have only tried 2 simultaneously). Also, whenever you use a remote connection to preclear, it would be very useful to use 'screen'. otherwise, if the remote session (e.g. putty) ends, your preclear will stop and you would have to start from scratch (I imagine it will be more annoying if it happens while preclearing many HDs simultaneously)

Hi, I bought an EARS 2TB few days ago and run preclear These were the results i got: root@Tower:~# screen -r 6946 = Step 1 of 10 - Copying zeros to first 2048k bytes DONE = Step 2 of 10 - Copying zeros to remainder of disk to clear it DONE = Step 3 of 10 - Disk is now cleared from MBR onward. DONE = Step 4 of 10 - Clearing MBR bytes for partition 2,3 & 4 DONE = Step 5 of 10 - Clearing MBR code area DONE = Step 6 of 10 - Setting MBR signature bytes DONE = Step 7 of 10 - Setting partition 1 to precleared state DONE = Step 8 of 10 - Notifying kernel we changed the partitioning DONE = Step 9 of 10 - Creating the /dev/disk/by* entries DONE = Step 10 of 10 - Testing if the clear has been successful. DONE = Disk Post-Clear-Read completed DONE Disk Temperature: 30C, Elapsed Time: 27:56:04 ============================================================================ == == Disk /dev/sdc has been successfully precleared == ============================================================================ S.M.A.R.T. error count differences detected after pre-clear note, some 'raw' values may change, but not be an indication of a problem 19,20c19,20 < Offline data collection status: (0x80) Offline data collection activity < was never started. --- > Offline data collection status: (0x84) Offline data collection activity > was suspended by an interrupting command from host. 54c54 < 1 Raw_Read_Error_Rate 0x002f 100 253 051 Pre-fail Always - 0 --- > 1 Raw_Read_Error_Rate 0x002f 200 200 051 Pre-fail Always - 0 58c58 < 7 Seek_Error_Rate 0x002e 100 253 000 Old_age Always - 0 --- > 7 Seek_Error_Rate 0x002e 200 200 000 Old_age Always - 0 63c63 < 193 Load_Cycle_Count 0x0032 200 200 000 Old_age Always - 11 --- > 193 Load_Cycle_Count 0x0032 200 200 000 Old_age Always - 12 67c67 < 199 UDMA_CRC_Error_Count 0x0032 200 253 000 Old_age Always - 0 --- > 199 UDMA_CRC_Error_Count 0x0032 200 200 000 Old_age Always - 0 ============================================================================ Having had some problems with an EARS few weeks ago i decided to run preclear a second time, just to be sure. I have been away for some time and when i came back i reconnected using screen. I guess preclear was over and i saw this screen: > Conveyance self-test routine > recommended polling time: ( 5) minutes. > SCT capabilities: (0x3035) SCT Status supported. > SCT Feature Control supported. > SCT Data Table supported. > > 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 0x002f 200 200 051 Pre-fail Always - 0 > 3 Spin_Up_Time 0x0027 253 253 021 Pre-fail Always - 1091 > 4 Start_Stop_Count 0x0032 100 100 000 Old_age Always - 10 > 5 Reallocated_Sector_Ct 0x0033 200 200 140 Pre-fail Always - 0 > 7 Seek_Error_Rate 0x002e 200 200 000 Old_age Always - 0 > 10 Spin_Retry_Count 0x0032 100 253 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 - 8 > 192 Power-Off_Retract_Count 0x0032 200 200 000 Old_age Always - 7 > 193 Load_Cycle_Count 0x0032 200 200 000 Old_age Always - 15 > 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 100 253 000 Old_age Offline - 0 > 199 UDMA_CRC_Error_Count 0x0032 200 200 000 Old_age Always - 0 > 200 Multi_Zone_Error_Rate 0x0008 100 253 000 Old_age Offline - 0 > > SMART Error Log Version: 1 > No Errors Logged > > 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. > ============================================================================ So, what does that mean? Could preclear, have stoped abruptly?

Thanks for the heads up. Brilliant, the F4204UI isn't supported yet. So what to do, send it back to Amazon, or wait and see if there is a solution... which could be a fair few months. From reading around it looks like it may well work, but isn't advised as a parity drive. And I need the space now. I would send it back since you can only use it as parity. Maybe get a refund from amazon and order a new drive right now...

as long as you dont start the array you will have no problem. Bear in mind that since you have a new 2tb drive and it is the largest, you have to use this for parity... also, i have heard that there are some problems with samsung HDs, so better check the forums for extra info, especially this: http://lime-technology.com/wiki/index.php?title=Hardware_Compatibility#Samsung

When the array is stopped, you can remove a disk from it from the devices tab in the unraid webgui. then you wont have any problem with precelear...

Joe, If you remember I had a problem with a disk not preclearing (with the jumper). I tried formatting it in windows with the jumper but it also failed. I am now formatting it in windows without the jumper. If the formatting works, should i use the jumper again and preclear it or there is no point to it? I can try it anyway but, since I need to RMA it within some time limits, I do not have the time...

Officially impressed/jealous