FreeMan

Display Settings - Dynamix color theme derp - that was about the only setting screen I didn't look at NerdPack sticky Thank you! working like a charm!

Thanks for your great work, bonienl! Having finally just migrated from 5.0.6, the new unRAID 6.1.9 looks very familiar, thanks to you! 2 questions: 1) How do I customize the GUI to get back to the darker interface I had under 5.x? 2) Do you have a recommendation for an easy install for perl for the System Temp plugin?

=== START OF INFORMATION SECTION === Model Family: Seagate Samsung Spinpoint F4 Device Model: ST320DM001 HD322GJ Serial Number: S2BJJ90C816980 LU WWN Device Id: 5 0004cf 208350c31 Firmware Version: 1AR10001 User Capacity: 320,072,933,376 bytes [320 GB] Sector Size: 512 bytes logical/physical Rotation Rate: 7200 rpm Form Factor: 3.5 inches Device is: In smartctl database [for details use: -P show] ATA Version is: ATA8-ACS T13/1699-D revision 6 SATA Version is: SATA 2.6, 3.0 Gb/s Local Time is: Mon May 18 19:42:23 2015 EDT SMART support is: Available - device has SMART capability. SMART support is: Enabled AAM feature is: Disabled APM feature is: Disabled Rd look-ahead is: Enabled Write cache is: Enabled ATA Security is: Disabled, frozen [sEC2] Wt Cache Reorder: Enabled It's been spinning for more than 2 years and was a cheapie that came with the 'bare bones' kit from Tiger Direct. Time for an upgrade so I'm throwing a shiny new SSD in there.

Hey all, been a while since I've stopped by. unRaid is just that good! This isn't even an unRaid issue, but I figure the folks here are pretty helpful, so I thought I'd post this: ID# ATTRIBUTE_NAME FLAGS VALUE WORST THRESH FAIL RAW_VALUE 1 Raw_Read_Error_Rate POSR-K 001 001 051 NOW 68478 2 Throughput_Performance -OS--K 252 252 000 - 0 3 Spin_Up_Time PO---K 083 074 025 - 5229 4 Start_Stop_Count -O--CK 100 100 000 - 53 5 Reallocated_Sector_Ct PO--CK 252 252 010 - 0 7 Seek_Error_Rate -OSR-K 252 252 051 - 0 8 Seek_Time_Performance --S--K 252 252 015 - 0 9 Power_On_Hours -O--CK 100 100 000 - 15210 10 Spin_Retry_Count -O--CK 252 252 051 - 0 11 Calibration_Retry_Count -O--CK 100 100 000 - 8 12 Power_Cycle_Count -O--CK 100 100 000 - 57 191 G-Sense_Error_Rate -O---K 099 099 000 - 10507 192 Power-Off_Retract_Count -O---K 252 252 000 - 0 194 Temperature_Celsius -O---- 063 058 000 - 37 (Min/Max 16/43) 195 Hardware_ECC_Recovered -O-RCK 100 100 000 - 0 196 Reallocated_Event_Count -O--CK 252 252 000 - 0 197 Current_Pending_Sector -O--CK 097 097 000 - 67 198 Offline_Uncorrectable ----CK 252 252 000 - 0 199 UDMA_CRC_Error_Count -OS-CK 200 200 000 - 0 200 Multi_Zone_Error_Rate -O-R-K 100 100 000 - 3019 223 Load_Retry_Count -O--CK 100 100 000 - 8 225 Load_Cycle_Count -O--CK 100 100 000 - 68 Device Error Count: 58753 (device log contains only the most recent 8 errors) That's the SMART output of my Windows 7 box system drive. I'm no expert, but I'm thinking that's looking pretty bad at this point. Thoughts? TIA!

There is an improved preclear script by bjp999. It speeds up the post read process. You can also skip the pre-read and post-read of the preclear process (check the --help for the specifics) to save time. However, those were added in for safety to help test out the drive to ensure it doesn't suffer from an early death once it's got your valuable info stored on it. It's a bit of a bother to run it and wait, but it's better than losing data. There's a discussion around here somewhere of how many times to run the preclear - some do 3 or 4 complete cycles.

It's not looking too good for the old drive - lots of pending re-allocations, and the numbers were growing after every cycle. Time to retire the old gal? preclear_rpt_JP2921HQ03M4KA_2015-01-01.txt

Kosti- When you preclear the drive, you can add it to the array "quickly" because all you do is stop the array (without powering down), assign the freshly precleared drive to the array, then restart the array. It will take unRAID just a couple of minutes to do its housekeeping, and you're back in business. If you don't preclear the drive, then you stop the array, assign the new drive to the array, restart the array, then wait hours and hours for unRAID to write zeros to every byte on the disk. During this time, your array is inaccessible, so you can't read from or write to it at all during that time. The "pre" clear process allows you to write the zeros to the new disk(s) while the array is still online, instead of doing it while it's offline. NOTE: both of these scenarios presume that you've powered down the machine and physically installed the drive.

I don't have results to ask about yet, but what I do have is on cycle 2 of 3: = Post-Read in progress: 69% complete. ( 696,254,464,000 of 1,000,204,886,016 bytes read ) 1.2 MB/s Disk Temperature: 32C, Elapsed Time: 39:53:56 Note 40 hours to run less than 2 complete passes on a 1 TB drive!!! Note the speed of 1.2 MB/s!!! I noticed that on pass 1, as well, and it was down into the KB/s range. Now, this is an older drive that spend a couple of years in a WinXP machine, then was migrated to my unRAID box as it was built, then started giving me lots and lots of errors. I've got all the data off of it and replaced the drive in the array a couple of days ago, then decided to re-run preclear to see if there were just some bad areas that could be mapped out or if it was really dead. Looks like it's really, really dead... I looked to see if there were any intermediate logs (after each cycle?) generated by preclear, but it doesn't look like it. Any thoughts? EDIT: I'm getting a fair number of issues being reported in the syslog (attached) EDIT 2: It actually seems to have hung. It's been about 2 hours and nothing has changed in my telnet session - byte count read and elapsed time haven't changed one bit. EDIT 3: Nope, it's moving. It's at 73% complete now, and has sped up to a blazing 6.1 MB/s syslog-2014.12.31.1116.txt

I just picked up a couple of refurb 300GB 10000RPM drives that I intend to use as system drives in my Windows machines, but since they're refurb & only have a 90 day warranty, I want to use preclear to give them a good workout. I've searched this thread, and it appears that preclear will work just fine on a drive mounted via a SATA->USB dock, but I'm getting an error root@NAS:/boot/Scripts# preclear_disk.sh -l ====================================1.15 Disks not assigned to the unRAID array (potential candidates for clearing) ======================================== /dev/sdn = usb-JMicron_USB_to_ATA_ATAPI_Bridge_152D203380B6-0:0 So the drive is recognized with no issues root@NAS:/boot/Scripts# preclear_disk.sh -c 10 /dev/sdn Sorry: Device /dev/sdn is not responding to an fdisk -l /dev/sdn command. You might try power-cycling it to see if it will start responding. This is an older 'dock' that I borrowed from a buddy. it's a Rosewill brand (from Newegg) and is actually just a power brick & connector and a USB-SATA cable, so there's nothing 'dockey' about it. I've got the drive sitting on its anti-static bag on top of the case, and it's recognized by unRAID as soon as I power it on, but preclear doesn't seem to like it. Any thoughts or suggestions?

I just upgraded my parity from a 3TB drive to a 4TB. The 4 precleared & parity has been rebuilt & checked just fine. I went to preclear the 3TB, and I get this output from preclear_disk.sh before starting the clear: root@NAS:/boot/scripts# preclear_disk.sh -n /dev/sdm Pre-Clear unRAID Disk /dev/sdm ################################################################## 1.15 Model Family: Western Digital Caviar Green (AF, SATA 6Gb/s) Device Model: WDC WD30EZRX-00D8PB0 Serial Number: WD-WMC4N0533589 LU WWN Device Id: 5 0014ee 603d7fd9c Firmware Version: 80.00A80 User Capacity: 3,000,592,982,016 bytes [3.00 TB] WARNING: GPT (GUID Partition Table) detected on '/dev/sdm'! The util fdisk doesn't support GPT. Use GNU Parted. Disk /dev/sdm: 3000.6 GB, 3000592982016 bytes 256 heads, 63 sectors/track, 363376 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/sdm1 1 4294967295 2147483647+ ee GPT Partition 1 does not start on physical sector boundary. ######################################################################## invoked as ./preclear_disk.sh -n /dev/sdm ######################################################################## (MBR 4k-aligned set. Partition will start on sector 64 for disks <= 2.2TB and sector 1 for disks > 2.2TB) Though I've upgraded my parity before (from 2 to 3TB), I don't recall seeing a message like this, though it may have been there. What concerns me is Partition 1 does not start on physical sector boundary. Is that an issue to worry about? I'm running unRaid v5.0.4. TIA FreeMan

Winner, winner, chicken dinner!!! Thanks Rob, that was the ticket. Despite wearing contacts, we all need 4 eyes. Thanks - don't know why I didn't think of that...

I'm running a Gigabyte F2A88XM-D3H mobo with an AMD A6 5400K CPU. I found this link http://ubuntuforums.org/showthread.php?t=2201555 and this one http://www.phoronix.com/forums/showthread.php?96788-Gigabyte-F2A88XM-D3H-AMD-A88X/page3 that both indicated that I needed to use modprobe it87 force_id=0x8728. Having done that, sensors now reports: k10temp-pci-00c3 Adapter: PCI adapter MB Temp: +9.4 C (high = +70.0 C) (crit = +80.0 C, hyst = +79.0 C) it8728-isa-0228 Adapter: ISA adapter in0: +1.00 V (min = +0.00 V, max = +3.06 V) in1: +1.49 V (min = +0.00 V, max = +3.06 V) in2: +2.02 V (min = +0.00 V, max = +3.06 V) in3: +2.02 V (min = +0.00 V, max = +3.06 V) in4: +2.00 V (min = +0.00 V, max = +3.06 V) in5: +2.22 V (min = +0.00 V, max = +3.06 V) in6: +2.22 V (min = +0.00 V, max = +3.06 V) 3VSB: +3.36 V (min = +0.00 V, max = +6.12 V) Vbat: +3.02 V fan1: 1917 RPM (min = 10 RPM) fan2: 0 RPM (min = 10 RPM) fan3: 0 RPM (min = 0 RPM) fan4: 0 RPM (min = 0 RPM) fan5: 0 RPM (min = 0 RPM) temp1: +29.0 C (low = +127.0 C, high = +127.0 C) sensor = thermistor temp2: -8.0 C (low = +127.0 C, high = +127.0 C) sensor = thermistor temp3: +30.0 C (low = +0.0 C, high = +60.0 C) sensor = Intel PECI intrusion0: ALARM I ended up with this in my sensors.conf: # sensor configuration chip "k10temp-*" #chip "it8728-isa-0028" label temp1 "MB Temp" label temp3 "CPU Temp" With the first "chip" line in effect, I get the somewhat ridiculously low reading in the single digits © as a temp being displayed in Dynamix. If I uncomment the 2nd "chip" line, instead, I get no readings showing up. The values from the it8728 chip seem to be accurate, or at least reasonable, how do I get them to display instead of the values from the k10temp chip? (As a side note, how do I get a nicely formatted word as a link, instead of displaying the full link? I know how to do <a href="url">text</a> in HTML, but how do I do it in BBCode?)

My guess is you received a drive with some problems, that had been 'repaired' by clearing the SMART tables, masking the problems, so the first test runs re-exposed the problems. The first 2 Preclears seemed to have dealt with most of them, and the third looks much better, but I'm not confident you've uncovered ALL of the marginal sectors yet. I'd run 2 or 3 more Preclears, and I'd only feel more confident if I had at least 2 passes with NO further changes, no more Current Pending sectors at any phase, no additional Uncorrectables, no additional Reallocated sectors. If interested and have time, you might also try a full badblocks run with the -w option. The other possibility is that it's a bad drive, and it's going to continue getting worse. I suspect that after another Preclear, you will either know it's bad or may decide that you aren't willing to trust the drive, even if it starts behaving, has clean reports. I would suggest keeping all the pre-clear SMART results, just in case Seagate questions why you want to return a drive they just shipped you. From what I've read around here, they don't normally question it, but returning a just shipped drive might raise an eyebrow somewhere. What's a few K of disk space for a few weeks, just to be on the safe side...

I've been having other issues with the box since upgrading from 4.7 to 5.0.4 and adding 2 drives, so I'll see if I can get those sorted before totally giving up on this drive. On the bright side, I picked up the drive locally at Fry's, so it shouldn't be an issue walking back in to return it as DOA. The drive was on sale for $100 - if it hadn't been just before Christmas, with lots o' cash already spent on presents, I'd have picked up several. EDIT: Seems that it was an issue with the SATA controller card I also purchased. The drive's fine, preclear has finished and parity is now syncing.

Thanks for your input, Gary & ProStuff! I ended up grabbing the ThermalTake PSU out of a dead machine I have sitting here, and the difference is like night and day! Interesting, since the CX series Corsairs are listed in the first couple of posts as recommended good PSUs. I'm not here to argue the point with you, since I'm the one asking for info, but is it worthwhile having a discussion amongst those who do know about whether those are good recommendations to leave up front there? If there are design issues, maybe it's time to update the recommendations...

The pre-read hung at 99%. I rummaged through the end of the syslog, and this is what I found: Dec 29 10:36:28 NAS kernel: sd 7:0:0:0: [sdg] CDB: Dec 29 10:36:28 NAS kernel: cdb[0]=0x88: 88 00 00 00 00 01 5d 50 78 00 00 00 00 08 00 00 Dec 29 10:36:28 NAS kernel: sd 7:0:0:0: [sdg] Unhandled error code Dec 29 10:36:28 NAS kernel: sd 7:0:0:0: [sdg] Dec 29 10:36:28 NAS kernel: Result: hostbyte=0x04 driverbyte=0x00 Dec 29 10:36:28 NAS kernel: sd 7:0:0:0: [sdg] CDB: Dec 29 10:36:28 NAS kernel: cdb[0]=0x88: 88 00 00 00 00 01 5d 50 78 00 00 00 00 08 00 00 Dec 29 10:36:28 NAS kernel: sd 7:0:0:0: [sdg] Unhandled error code Dec 29 10:36:28 NAS kernel: sd 7:0:0:0: [sdg] Dec 29 10:36:28 NAS kernel: Result: hostbyte=0x04 driverbyte=0x00 Dec 29 10:36:28 NAS kernel: sd 7:0:0:0: [sdg] CDB: Dec 29 10:36:28 NAS kernel: cdb[0]=0x88: 88 00 00 00 00 01 5d 50 78 00 00 00 00 08 00 00 Dec 29 10:36:28 NAS kernel: sd 7:0:0:0: [sdg] Unhandled error code Dec 29 10:36:28 NAS kernel: sd 7:0:0:0: [sdg] Dec 29 10:36:28 NAS kernel: Result: hostbyte=0x04 driverbyte=0x00 Dec 29 10:36:28 NAS kernel: sd 7:0:0:0: [sdg] CDB: Dec 29 10:36:28 NAS kernel: cdb[0]=0x88: 88 00 00 00 00 01 5d 50 78 00 00 00 00 08 00 00 Dec 29 10:36:28 NAS kernel: sd 7:0:0:0: [sdg] Unhandled error code Dec 29 10:36:28 NAS kernel: sd 7:0:0:0: [sdg] Dec 29 10:36:28 NAS kernel: Result: hostbyte=0x04 driverbyte=0x00 Dec 29 10:36:28 NAS kernel: sd 7:0:0:0: [sdg] CDB: Dec 29 10:36:28 NAS kernel: cdb[0]=0x88: 88 00 00 00 00 01 5d 50 78 00 00 00 00 08 00 00 Dec 29 10:36:28 NAS kernel: sd 7:0:0:0: [sdg] Unhandled error code Dec 29 10:36:28 NAS kernel: sd 7:0:0:0: [sdg] Dec 29 10:36:28 NAS kernel: Result: hostbyte=0x04 driverbyte=0x00 Dec 29 10:36:28 NAS kernel: sd 7:0:0:0: [sdg] CDB: Dec 29 10:36:28 NAS kernel: cdb[0]=0x88: 88 00 00 00 00 01 5d 50 78 00 00 00 00 08 00 00 There were a lot of lines like that, and the ones I checked were all the same. Can anyone interpret that for me? I'm not sure what it means beyond, 'not good'.

I've just purchased my first 3TB drive and updated from unRAID 4.7 to 5.0.4. I've updated to preclear_disk.sh v 1.14, and when I run it on my 3TB drive, it's hanging. The first try, I kicked it off in 2 seperate putty sessions, one for the 3TB and one for the new 1TB. They got to 7% and 26% completion on the first step (EDIT: Disk Pre-Read) in about 30 minutes, then for the next 30 minutes, the sessions didn't update at all - the percentage didn't increase and the timer never changed. I killed both with a ctrl-c, and attempted to kick off the preclear again, and it told me it couldn't access /dev/sdx for either drive. After rebooting the server (it did properly shut down & restart - it was still very responsive), I tried the same thing again, and it got to the same place. After a 2nd reboot (via the web interface), I kicked off the preclear on only the 3TB, and went to bed. When I got up in the morning, it had made it to 9% of the first phase (don't remember how long it had taken), but it hung there with the clock not counting up as I checked in on it for about 15 min. What logs would someone need to see to get an idea of what's going on? It's not putting anything into the /boot/preclear_reports directory. It's a brand-new, fresh from the box WD30EZRX drive. I've not confirmed that the drive is OK by putting it in another machine, but the fact that it has gotten to 2 different levels of completion leads me to believe that it may not be the disk itself failing/DOA. I'm currently trying the 1TB drive by itself to see if that will run to completion. I'm chasing several niggling little issues as I try to reconfigure everything that was working in 4.7 to get it function in 5.0.4 (SAB, CP, Sick, unMenu, preclear, UPS integration, etc). TIA EDIT: The 1TB drive is now up to 34% complete of the Disk Pre-Read step, so it, at least, seems functional EDIT 2: The 1TB finished its pre-clear and is now a part of the array and is formatting. On to the 3TB... EDIT 3: The 3TB drive seems to preclearing now, it's at 17% and counting.

Any suggestions for a very quiet, yet reasonably priced PSU for my desktop machine? I've got 2 drives in it now (one will be moving into my unRAID, once it's upgraded), and a low-end graphics card, so I don't need a lot of power, just quiet. I'm working from home full time now, and, honestly, starting to be a bit concerned about my hearing. This looks to be a pretty good price, and is listed as "quiet" but doesn't really say what quiet is. http://www.newegg.com/Product/Product.aspx?Item=N82E16817139049 Anyone have any thoughts or experience with this one, or a suggestion for something else? Thanks!

OK, I got the card and plugged it into my machine. The hardware recognizes it just fine, and I was able to get into the BIOS setup of the card, and it recognized the HD I'd attached. When I booted into unRAID (4.7) I could not see hide nor hare of the drive. Since I've got a machine made up of recycled parts (my son's old machine), I don't have a fancy KVM over IP solution for nice screen prints, so I did the next best thing. Pics attached linked. http://i324.photobucket.com/albums/k331/bdshepard/2013-01-16220945_zps6d9bafad.jpg http://i324.photobucket.com/albums/k331/bdshepard/2013-01-16220802_zps5d908ff8.jpg I pulled the card, and it's got 3 SiL 3112 chips on it to support the 6 SATA ports. http://i324.photobucket.com/albums/k331/bdshepard/2013-01-16222756_zps0746d4d4.jpg It looks like this controller chip will work with unRAID (http://lime-technology.com/forum/index.php?topic=17077.0) The card also has some jumpers, but any actual info about this card is hard to come by via the google. I went 6 pages in and couldn't find anything but for-sale, a few forum posts, and the LSI web site which doesn't seem to acknowledge the existence of this card. What other info might someone need to help solve the issue? EDIT: additional note - this is a PCIX card plugged into a PCI slot, and it appears that some of the extra connectors may be contacting a capacitor on the Mobo. I suppose that could be causing issues, but the machine boots, and I have no trouble getting into the card's BIOS, and the BIOS recognized a single drive that I'd plugged into it. http://i324.photobucket.com/albums/k331/bdshepard/2013-01-16225206_zpsede85577.jpg EDIT2: Found the LSI docs here: http://www.lsi.com/downloads/Public/Obsolete/Obsolete%20Common%20Files/sata150_ug.pdf and all the info they have on the board here: http://www.lsi.com/support/Pages/Download-Results.aspx?productcode=P00462&assettype=0&component=Storage%20Component&productfamily=Legacy%20RAID%20Controllers&productname=MegaRAID%20SATA%20150-4%20%28523%29

I can get one of these really cheap: http://www.ascendtech.us/lsi-ser523-rev-b2-raid-sata-controller_i_cntlsilogser523.aspx Anybody know if that will A) work with unRAID, B) be flashable (need to be flashed) as described in this post, C) be worth getting? I know it only supports SATA 1, so it will be slower, but most of my drives are SATA 1 at this point, so that won't matter much. I was unable to determine from the ad what chipset this has on it. Any help would be appreciated. FreeMan