SidebandSamurai

Well here is an update. I performed option number 4 (Check for firmware update). Seagate reported none available and one available under certificate. I downloaded the one under certificate as it was dated July of this year, and I have had the drives in storage since November 2012. The Firmware version shipped was CC43. The version I installed was CC29. I think this is a downgrade of the firmware, and I have no way to restore the firmware with shipped version as seagate does not provide the "updated" firmware. Currently I have started pre-clearing the CC29 hard drive on a different system. Its BIOS is also reporting 800 GB instead of 3TB. It seams I am just unlucky in finding a system that will show 3TB in the bios. From previous posts, I don't think this really the actual issue. It will take 24 hrs to re-preclear the drive. -- Sideband Samurai

All very good comments, thank you for the advice. 1. I did update the bios on the XW4300, it was on 1.06 and was updated to 1.12, but this did not fix the issue because the system still reports 800MB for a 3TB drive. 2. I started using a SiL3114 host adapter by Sabrent. Its a PCI to SATA HBA. when I restarted the pre-clear, it showed the same exact numbers as the mother board ports. Except it reported that a 3TB drive was attached. I did not allow the pre-clear to complete. 3. I will pre-clear this disk on a different system. If it works, then I will replace the existing parity drive with this 3TB disk. 4. I will check for firmware updates for my particular drive model and see if that fixes my problem. 5. I already have a 3TB drive that did not pass pre-clear running as a Parity. I put it in production with out knowing that I should not have. I have run 3 parity checks with no errors. I will be replacing this drive if number 3 is successful. I too would be interested in what JoeL has to say about the issue. Maybe the signature should be wiped out if the pre-clear is unsuccessful to prevent its installation. Although all that would do is just cause the array to not be mounted for 24 hours. but at least when you rant the -t you can see that its not ready to be put in production. Thanks again! Sideband Samurai

but why did the script return these errors, and that the disk had NOT been precleared successfully as seen below? ST3000DM001-1CH166 W1F12655 == Disk /dev/sde has NOT been precleared successfully == skip=151000 count=200 bs=8225280 returned 32768 instead of 00000 skip=161000 count=200 bs=8225280 returned 32768 instead of 00000 skip=171800 count=200 bs=8225280 returned 32768 instead of 00000 skip=179400 count=200 bs=8225280 returned 32768 instead of 00000 skip=183000 count=200 bs=8225280 returned 32768 instead of 00000 skip=187000 count=200 bs=8225280 returned 32768 instead of 00000 skip=193000 count=200 bs=8225280 returned 32768 instead of 00000 skip=220800 count=200 bs=8225280 returned 32768 instead of 00000 skip=289600 count=200 bs=8225280 returned 32768 instead of 00000 skip=326200 count=200 bs=8225280 returned 32768 instead of 00000

Darn! I am using an old hp xw4300 workstation. There is no new bios update that I can see (I am running the current version). My BIOS is reporting that the attached hard drive is 800GB not 3TB. The other 2TB drives actually show up as 2TB drives. So I am thinking that the 3TB hard drives though appear to be working, may actually not be absolutely happy. I have a PCI to sata HBA I can use to support the 3TB drives for now. At least I hope it supports 3TB drives. Its strange though, Unraid shows these as 3TB drives, and the drive I just put into production, which is a 3TB drive does not appear to be having any issues. I have checked the Parity twice with 0 errors. Should I be worried? If so, my plan would be to add the PCI to SATA HBA, attach the new drive tray to the HBA, then re-run a pre-clear to see if it clears ok. If it does then I can remove the existing parity, and re-add the re-tested 3TB drive that is on the PCI to SATA HBA, as the NEW parity drive, rebuild the parity, re-check the array to make sure I still get no errors. If everything goes well, do the same thing to the now to the existing 3TB parity and make it a data drive. What does everyone think? Any problems with this? I am not totally worried about performance right now. As I am in the process of building a whole new system these drives will go into. Just waiting on extra funds for the important parts (CPU and RAM). I just need more space so I can put my wife's Horror collection on the media server (some 60 DVDs). -- Sideband Samurai

Since this falls under the same subject, I wanted to ask about pre-clearing errors: I have pre-cleared my second 3TB drive, and received the following error: == ST3000DM001-1CH166 W1F12655 == Disk /dev/sde has NOT been precleared successfully == skip=151000 count=200 bs=8225280 returned 32768 instead of 00000 skip=161000 count=200 bs=8225280 returned 32768 instead of 00000 skip=171800 count=200 bs=8225280 returned 32768 instead of 00000 skip=179400 count=200 bs=8225280 returned 32768 instead of 00000 skip=183000 count=200 bs=8225280 returned 32768 instead of 00000 skip=187000 count=200 bs=8225280 returned 32768 instead of 00000 skip=193000 count=200 bs=8225280 returned 32768 instead of 00000 skip=220800 count=200 bs=8225280 returned 32768 instead of 00000 skip=289600 count=200 bs=8225280 returned 32768 instead of 00000 skip=326200 count=200 bs=8225280 returned 32768 instead of 00000 Is this a problem? Note the pre-clear script reports /dev/sde has NOT been precleared successfully. I saw this error before with the previous 3TB drive which is now the Parity drive. I just want to make sure everything is ok before proceeding. I am going to reboot the server to install the 5.0 release, then I will perform a parity check which as of the 30th of last month reported no errors with the new 3TB drive as a parity drive in place. for further information, here is the full pre-clear report: ================================================================== 1.13 = unRAID server Pre-Clear disk /dev/sde = cycle 2 of 2, partition start on sector 1 = = 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 - Verifying if the MBR is cleared. DONE = Disk Post-Clear-Read completed DONE Disk Temperature: 39C, Elapsed Time: 48:46:46 ========================================================================1.13 == ST3000DM001-1CH166 W1F12655 == Disk /dev/sde has NOT been precleared successfully == skip=151000 count=200 bs=8225280 returned 32768 instead of 00000 skip=161000 count=200 bs=8225280 returned 32768 instead of 00000 skip=171800 count=200 bs=8225280 returned 32768 instead of 00000 skip=179400 count=200 bs=8225280 returned 32768 instead of 00000 skip=183000 count=200 bs=8225280 returned 32768 instead of 00000 skip=187000 count=200 bs=8225280 returned 32768 instead of 00000 skip=193000 count=200 bs=8225280 returned 32768 instead of 00000 skip=220800 count=200 bs=8225280 returned 32768 instead of 00000 skip=289600 count=200 bs=8225280 returned 32768 instead of 00000 skip=326200 count=200 bs=8225280 returned 32768 instead of 00000 ============================================================================ ** Changed attributes in files: /tmp/smart_start_sde /tmp/smart_finish_sde ATTRIBUTE NEW_VAL OLD_VAL FAILURE_THRESHOLD STATUS RAW_VALUE Spin_Retry_Count = 100 100 97 near_thresh 0 End-to-End_Error = 100 100 99 near_thresh 0 High_Fly_Writes = 95 96 0 ok 5 Airflow_Temperature_Cel = 61 63 45 near_thresh 39 Temperature_Celsius = 39 37 0 ok 39 No SMART attributes are FAILING_NOW 0 sectors were pending re-allocation before the start of the preclear. 0 sectors were pending re-allocation after pre-read in cycle 1 of 2. 0 sectors were pending re-allocation after zero of disk in cycle 1 of 2. 0 sectors were pending re-allocation after post-read in cycle 1 of 2. 0 sectors were pending re-allocation after zero of disk in cycle 2 of 2. 0 sectors are pending re-allocation at the end of the preclear, the number of sectors pending re-allocation did not change. 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. Also the pre-clear test: root@DavyJones:/boot# preclear_disk -t /dev/sde Pre-Clear unRAID Disk /dev/sde ################################################################## 1.13 Device Model: ST3000DM001-1CH166 Serial Number: W1F12655 Firmware Version: CC43 User Capacity: 3,000,592,982,016 bytes Disk /dev/sde: 3000.6 GB, 3000592982016 bytes 255 heads, 63 sectors/track, 364801 cylinders, total 5860533168 sectors Units = sectors of 1 * 512 = 512 bytes Sector size (logical/physical): 512 bytes / 4096 bytes I/O size (minimum/optimal): 4096 bytes / 4096 bytes Disk identifier: 0x00000000 Device Boot Start End Blocks Id System /dev/sde1 1 4294967295 2147483647+ 0 Empty Partition 1 does not end on cylinder boundary. Partition 1 does not start on physical sector boundary. ######################################################################## ========================================================================1.13 == == DISK /dev/sde IS PRECLEARED with a GPT Protective MBR == ============================================================================ root@DavyJones:/boot# Your advice is greatly appreciated Sincerely, Sideband Samurai

Are you sure your version actually says 1.2 not 1.12?

but you did not answer my question. Why does the Preclear script tell me "Partition starting on Sector 63" and "it will not be 4k-aligned" and when the -A parameter is used it states "-A option elected, partition will start on sector 64" I am currently running RC-16 version of unraid, and Version 1.13 of the script. Thank you. Sideband Samurai

One quick question about the -A parameter. With out the -A parameter I get the following warning: ################################################################## 1.13 Device Model: ST3000DM001-1CH166 Serial Number: W1F12655 Firmware Version: CC43 User Capacity: 3,000,592,982,016 bytes Disk /dev/sde: 3000.6 GB, 3000592982016 bytes 255 heads, 63 sectors/track, 364801 cylinders, total 5860533168 sectors Units = sectors of 1 * 512 = 512 bytes Sector size (logical/physical): 512 bytes / 4096 bytes I/O size (minimum/optimal): 4096 bytes / 4096 bytes Disk identifier: 0x00000000 Device Boot Start End Blocks Id System /dev/sde1 1 4294967295 2147483647+ 0 Empty Partition 1 does not end on cylinder boundary. Partition 1 does not start on physical sector boundary. ######################################################################## invoked as ./preclear_disk /dev/sde ######################################################################## (partition starting on sector 63) (it will not be 4k-aligned) Are you absolutely sure you want to clear this drive? (Answer Yes to continue. Capital 'Y', lower case 'es'): As you can see, "Partition starting on Sector 63" and "it will not be 4k-aligned" but if I issue the -A command then you see the following: Pre-Clear unRAID Disk /dev/sde ################################################################## 1.13 Device Model: ST3000DM001-1CH166 Serial Number: W1F12655 Firmware Version: CC43 User Capacity: 3,000,592,982,016 bytes Disk /dev/sde: 3000.6 GB, 3000592982016 bytes 255 heads, 63 sectors/track, 364801 cylinders, total 5860533168 sectors Units = sectors of 1 * 512 = 512 bytes Sector size (logical/physical): 512 bytes / 4096 bytes I/O size (minimum/optimal): 4096 bytes / 4096 bytes Disk identifier: 0x00000000 Device Boot Start End Blocks Id System /dev/sde1 1 4294967295 2147483647+ 0 Empty Partition 1 does not end on cylinder boundary. Partition 1 does not start on physical sector boundary. ######################################################################## invoked as ./preclear_disk -A /dev/sde ######################################################################## (-A option elected, partition will start on sector 64) Are you absolutely sure you want to clear this drive? (Answer Yes to continue. Capital 'Y', lower case 'es'): In this example, you see "-A option elected, partition will start on sector 64" so according to your statement, with out issuing the -A (as its not required) the partition starts on 63 not 64, and is not 4K aligned as according to the script. but IF I specify the -A command it appears its 4K aligned and starting on 64. Could you clarify why the script is telling me this? This can be very confusing. I am running RC-16. Moving up to 5.0 release as soon as my drive is finished pre-clearing. Oh and remember "1:1 interleave on RLL drives" but I digress. Thank you for your advise, Sincerely, Sideband Samurai

GaryCase, Thanks for the confirmation and assurance. I am currently pre-clearing my second 3 TB drive. I am testing it for 5 cycles this time. Its funny, the bios shows the drive at a 800GB instead of a 3TB. Unraid shows the drive as 3TB though. I am not worried about it as this system was cobbled together to test the WAF (Wife Acceptance Factor). It went over very well, now I am in the process of getting new hardware and upgrading. Running short on space now, so that's why I am installing the 3TB drives. Sideband Samurai

In order to keep the drives temp under control, I purchased this at Frys for $17.00 Its not a permanent solution but it allows me to pre-clear disks with out taking the system covers off. Seems to work well so far. and here is the drive in action: ================================================================== 1.13 = unRAID server Pre-Clear disk /dev/sde = cycle 1 of 5, partition start on sector 1 = Disk Pre-Clear-Read completed DONE = Step 1 of 10 - Copying zeros to first 2048k bytes DONE = Step 2 of 10 - Copying zeros to remainder of disk to clear it = **** This will take a while... you can follow progress below: = = = = = = = = Disk Temperature: 43C, Elapsed Time: 10:41:29 320479+4 records in 320479+4 records out 672098189312 bytes (672 GB) copied, 3422.8 s, 196 MB/s Wrote 672,098,189,312 bytes out of 3,000,592,982,016 bytes (22% Done) As you can see the drive temp is down to around 43C instead of 50C so that is much cooler. This drive has been running for 10 hours. --Sideband Samurai

I have been using 5x since RC-8. It has been stable for me. I am currently on RC16, been too lazy to update to 5.0 final. I should just do it as its a simple copy and paste. Sideband Samurai

Well it looks like I have answered my own question. The values in my report are Normal ... with the exception of the temperature which was abnormally high because of how I had the hard drive installed. Seagate provides an excellent explenation of what Raw_Read_Error_Rate is and what is expected. This RAW_VALUE is normally high for this brand of drives. Here is a link to the article on Seagates Site: http://forums.seagate.com/t5/Desktop-HDD-Desktop-SSHD/Seagate-s-Seek-Error-Rate-Raw-Read-Error-Rate-and-Hardware-ECC/td-p/122382 So the drive is ready to become my parity drive. So I will install it tonight. Sincerely, Sideband Samurai

*bump* Does anybody have an answer to my questions? Thank you. Sideband Samurai

I have the following smart report for review. is this drive ok to use in production? root@DavyJones:/boot/preclear_reports# smartctl --all /dev/sdd smartctl 5.40 2010-10-16 r3189 [i486-slackware-linux-gnu] (local build) Copyright (C) 2002-10 by Bruce Allen, http://smartmontools.sourceforge.net === START OF INFORMATION SECTION === Device Model: ST3000DM001-1CH166 Serial Number: W1F1LWRA Firmware Version: CC24 User Capacity: 3,000,592,982,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 Sep 25 20:36:51 2013 PDT 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: (0x00) Offline data collection activity was never started. Auto Offline Data Collection: Disabled. 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: ( 89) seconds. Offline data collection capabilities: (0x73) SMART execute Offline immediate. Auto Offline data collection on/off support. Suspend Offline collection upon new command. No 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: ( 255) minutes. Conveyance self-test routine recommended polling time: ( 2) minutes. SCT capabilities: (0x3085) SCT Status supported. 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 118 100 006 Pre-fail Always - 199533168 3 Spin_Up_Time 0x0003 099 099 000 Pre-fail Always - 0 4 Start_Stop_Count 0x0032 100 100 020 Old_age Always - 2 5 Reallocated_Sector_Ct 0x0033 100 100 010 Pre-fail Always - 0 7 Seek_Error_Rate 0x000f 060 060 030 Pre-fail Always - 1071071 9 Power_On_Hours 0x0032 100 100 000 Old_age Always - 217 10 Spin_Retry_Count 0x0013 100 100 097 Pre-fail Always - 0 12 Power_Cycle_Count 0x0032 100 100 020 Old_age Always - 2 183 Runtime_Bad_Block 0x0032 100 100 000 Old_age Always - 0 184 End-to-End_Error 0x0032 100 100 099 Old_age Always - 0 187 Reported_Uncorrect 0x0032 100 100 000 Old_age Always - 0 188 Command_Timeout 0x0032 100 100 000 Old_age Always - 0 189 High_Fly_Writes 0x003a 100 100 000 Old_age Always - 0 190 Airflow_Temperature_Cel 0x0022 057 047 045 Old_age Always - 43 (Min/Max 26/53) 191 G-Sense_Error_Rate 0x0032 100 100 000 Old_age Always - 0 192 Power-Off_Retract_Count 0x0032 100 100 000 Old_age Always - 2 193 Load_Cycle_Count 0x0032 100 100 000 Old_age Always - 8 194 Temperature_Celsius 0x0022 043 053 000 Old_age Always - 43 (0 26 0 0) 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 240 Head_Flying_Hours 0x0000 100 253 000 Old_age Offline - 206781200466136 241 Total_LBAs_Written 0x0000 100 253 000 Old_age Offline - 64465865376 242 Total_LBAs_Read 0x0000 100 253 000 Old_age Offline - 136363348988 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. Thanks for your advice and help. Sincerely, Sideband Samurai

JoeL, I canceled it but after looking at my original OP, the report indicated that it had NOT been successfully pre-cleared. Have you seen anything like this? Also I did not get any report from the last 10 cycles so I don't know the health of the drive. Thanks for your fast response, Sideband Samurai

Hello, I am in the process of preclearing a disk. I accidentally set the count to 20, thinking I really wanted to test the heck out of this drive before putting it into production. Now that it has taken 7 days to reach 10 times, I am rethinking my strategy and am looking to cancel it after the 10th time. Do I have to wait for the remaining 10 cycles for me to see the reports and place this new drive into service? The reason I decided on an extended test was due to this report: ========================================================================1.13 == invoked as: ./preclear_disk -A /dev/sdd == == Disk /dev/sdd has NOT been successfully precleared == Postread detected un-expected non-zero bytes on disk== == Ran 1 cycle == == Using :Read block size = 8225280 Bytes == Last Cycle's Pre Read Time : 5:38:33 (147 MB/s) == Last Cycle's Zeroing time : 5:10:23 (161 MB/s) == Last Cycle's Post Read Time : 14:10:44 (58 MB/s) == Last Cycle's Total Time : 25:00:42 == == Total Elapsed Time 25:00:42 == == Disk Start Temperature: 33C == == Current Disk Temperature: -->49<--C, == ============================================================================ ** Changed attributes in files: /tmp/smart_start_sdd /tmp/smart_finish_sdd ATTRIBUTE NEW_VAL OLD_VAL FAILURE_THRESHOLD STATUS RAW_VALUE Raw_Read_Error_Rate = 114 100 6 ok 78450040 Spin_Retry_Count = 100 100 97 near_thresh 0 End-to-End_Error = 100 100 99 near_thresh 0 Airflow_Temperature_Cel = 51 67 45 near_thresh 49 Temperature_Celsius = 49 33 0 ok 49 No SMART attributes are FAILING_NOW 0 sectors were pending re-allocation before the start of the preclear. 0 sectors were pending re-allocation after pre-read in cycle 1 of 1. 0 sectors were pending re-allocation after zero of disk in cycle 1 of 1. 0 sectors are pending re-allocation at the end of the preclear, the number of sectors pending re-allocation did not change. 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. ============================================================================ Should I have been worried about the Spin_Retry_Count, End-toEnd_Error indicators. The AirFlow_Temperature_Cel indicator is just because its not mounted in the case yet. Can I cancel this and still have all my testing remain so that It does not take my array down for a day as it "reformats" the drive. This drive will be replacing a 2TB Parity Drive. Thanks for all your help. Sideband Samurai

From the Github page: If you want to download a later version of -latest than what you already have, then delete the two files first: cd /boot/plugins rm webGui-latest* wget --no-check-certificate https://github.com/limetech/webGui/raw/master/webGui-latest.plg installplg webGui-latest.plg Shut them off on the display tab on the Settings page... On the bottom right hand corner of the Main page. MikeJP Thank you for those instructions. This screams to be a script.

Hi Tom, should you add code to block access to IE7 and below? for example a windows that says IE8.0 or greater etc... -- Sideband Samurai IE users can just use chrome frame, you dont even need admin rights. Sadly though its being retired on Jan 2014. Anyways, rather than forcing that as short term solution we might just be better off doing something like showing a message to IE7 and older peeps: <!--[if lt IE 7]> <p class="browsehappy">You are using an <strong>outdated</strong> browser. Please <a href="http://browsehappy.com/">upgrade your browser</a> to improve your experience.</p> <![endif]--> +1 Great Idea!

How do you know if the new webgui was installed. I was running r2 of the new gui, and I just downloaded and installed the more recent version. I can still see the mountains even after rebooting the server. I ran installplg /boot/plugins/web-Gui-latest.plg and it seemed to install. the old web-Gui-r2.plg file is still in the folder as well as a new file called webGui-latest.txz Is there a webgui version I can check on the webinterface? -- Sideband Samurai

Hi Tom, should you add code to block access to IE7 and below? for example a windows that says IE8.0 or greater etc... -- Sideband Samurai

Triton, Pictures of the case the bakers rack and the dell rack, would be helpful. -Sideband Samurai

DiggsNC, Just curious, Why are you STILL running RC8a? Major bugs were squashed with the releases leading up to RC16C. You should be on RC16C to benefit from all the hard work the community put into that particular release. Sincerely, Sideband Samurai

Its already available, check your itunes store. -- Sideband Samurai

Hmmm. Release Candidate software as production software. As GreenLeaf themselves are using RC16C in production and have to support it. Either a dangerous president, or everyone running RC16C has release 5.0 already in their hands. Oh yea, and here is a post from Tom himself on July 10th. So there you have it. This would tell me that RC16-C is the 5.0 release. -- Sideband Samurai

I think the natives are restless because Tom has not posted on this release thread for a while. Since Tom has been silent, we don't know what he is doing to the code at this point. Maybe most of the critical bugs have been taken out, and now he is finalizing the new web interface and plugin system. Maybe there is another bug he is squashing and he is working hard to reproduce it. The point is we don't know and that's why the natives are restless. What I do know is that he is probably waiting to see what else comes up before moving on. This is not a oh my parity check ran successful and it was 850MB/s well it worked for me! Lets release it. There may be other problems Tom is looking into before he releases 5.0. Even if he is not doing ANYTHING. You have a working system with RC16-C. so IF nothing else changes, a "5.0" release will mean nothing as it will be the same as RC16-C. --Sideband Samurai