FreeMan

And... that didn't seem to have helped. I'm obviously setting something up incorrectly, but for the life of me, I'm not seeing the issue. I reinstalled CP, got it started and it filled up my docker.img file within minutes. Here is a screen shot of how I've got the drives mapped. where have I gone wrong?

Two questions: 1) The Piwigo page says things like a web server, MySQL and an FTP client are required. I presume that the docker installs all of those things 2) Since it says an FTP client is necessary, do I need to transfer my files from my unRAID server where they're already stored to a new location on the same server so that Piwigo knows about them, or can I just point Piwigo at them and have it scan an existing directory structure to find them? I don't want to have to store everything twice just to be able to display them.

Thanks. Took a minute to figure out which post "a few up" referred to, but I've got it. 20GB docker.img created, all other dockers reinstalled. I'm about to get CrashPlan reinstalled. Thanks for the help!

Another disk precleared with no issues. Big thanks to JoeL for the script and gfjardim for the plugin!

That does seem to be your issue, as it was mine. Learn from my mistake - uninstall the docker & reinstall it, don't try to change the cache mapping while it's running. Doesn't seem to work all that well.

You can do this on 6.2 What I suggest you do: Update to 6.2 when you can Then delete docker.img and recreate it. Then add all of your previous app via CA "previous apps" tab. OK, pre-clear finished, and 6.2 installed! So far, so good. Do I uninstall the dockers first, or just blow away the docker.img file? Also, I went with the default 10GB .img file, but it seems that 15-20GB is recommended. Can I create the new .img in a larger size & still get everything to install properly? It seems that I should be able to, but I just want to double check. Also - just noticed that there's an update to CA (9/17/2016) should I update that before reinstalling, or leave it on the current version (9/15/2016) for the fix, then update it? Does this mean that I should delete "docker.img" from disk, or does it mean I should go into Settings | Docker, disable docker, save it, then reenable it?

You probably want to run Windows Credential Manager to remove any cached credentials for the unRAID server. It is a not untypical Windows issue where it tries to use cached credentials that are not actually correct. Thank you, itimpi!!! I hit that yesterday (still on 6.1.9 - waiting on a pre-clear to finish before upgrading), and it was driving me nuts!

Clearly, I've made a mistake, and I only seem to have made it worse by trying to fix it. I installed the CP docker and everything worked great. I adopted my old backup (that was running on my Win machine for about 2 years) with about 1.4TB of data backed up to Code42's cloud. I followed their instructions to select my new locations and it was happily scanning along until I received 'Docker.img full' errors. Re-reading the OP and looking at the details of my install, I realized I had installed /config <-> /mnt/user/appdata/CrashPlan instead of /mnt/cache/appdata/CrashPlan. I stopped the docker, changed the mapping of /config and restarted the docker, confident that I had everything fixed. After a minute or two, I got a nice green pop-up telling me that my docker.img file use was back below 75% (it's at 30ish% right now). I'm on it, I've got this, no problem! I returned to the CrashPlan tab in Firefox, hit F5, and nothing. The No VPN page came up, but it wouldn't connect. I went to the docker tab in my unRAID management window, and I saw this: Great. What have I broken... Wait, that makes sense, there's a docker image on /mnt/user/appdata, and nothing's pointed at it - how do I delete the sucker? I clicked the disk icon, and got the 'Remove' option and clicked that, hit 'Just do it' I got the confirmation message: Fantastic, job done! I closed out the pop up, and there was that pesky orphaned image icon. OK, we'll go to the 'Dashboard' view, then back to 'Docker', and it'll be gone. Nope, no such luck. OK, maybe this will actually take a couple of minutes, let's go reinstall the docker in the mean time and everything will be great. I wandered off to the Community Applications tab, selected the 'Backups' department, clicked on the CrashPlan icon again, made sure to specify /config <-> /mnt/cache/appdata/CrashPlan, and hit Done. It went through its install routine, I headed over to the 'Docker' tab, and... yup, the orphan image icon is still there and there's no sign of the CrashPlan docker to be found. After several attempts to Remove the orphan, all with the same result, I attempted to install the docker to the original /config <-> /mnt/user/appdata/CrashPlan location in the hopes that unRAID would somehow reattach the docker to that orphan image so I could uninstall the docker correctly & get rid of it. That hasn't worked either. TL;DR - how the heck do I remove this orphan image and get your lovely CrashPlan docker to reinstall itself? I have the feeling I'll have to restart my backups, since it was at the very beginning of the process of reconciling things, but who knows, maybe CP will happily pick up where it left off. Either way, I don't care, I can wait a bit for all 1.4TB to push back to their servers, I just want to get this thing running again. As a side note, it might be nice to change the docker install config to default to having /config <-> /mnt/cache/... instead of /mnt/user/... since /mnt/cache is the recommended location for docker installs, and goobers like me tend to make mistakes and assume things when they're playing on the server late at night... A couple of additional points: [*]I'm at 85% of the pre-read of pass 2 of 2 on a preclear of a new drive, so rebooting the server (if necessary) will be postponed for a couple of days [*]As I was typing this up, unRAID 6.2 was released. See point 1. [*]My 975 GB of family photos are being copied to my solitary 1TB external drive, just in case, so until that finishes, see point 1.

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?

Installed the Community Applications plugin, then chose yours from there. Installed on Friday night. Sorry that wasn't clear.

Thanks for all your work! Now that I've finally upgraded to 6.x (yeah... I know...) I've got an odd (to me) issue. I installed your Subsonic docker, and couldn't for the life of me get Subsonic to see my media directories. (I've had a Subsonic license for years now.) After fiddling with it for a couple of days, I gave up and installed the Libresonic docker. I added a /Music mapping to the dock, and by the time I'd gotten the web page for Libresonic loaded (after fiddling around, browsing the Libsonic Git page, finding that it defaults to port 8080, then discovering that it's actually running on port 4040 on my machine), it had already cataloged all my music. I've since restarted the Libresonic with mappings for all my media files and my daughter is watching a soccer match from her dorm room now. The screen shot is of my Libresonic volume mappings, but they are the same as the ones I had for Subsonic. Any idea why one works and the other doesn't?

Thanks, RobJ! That's my second oldest drive. Guess I'll start keeping my eyes open for a good deal on a nice 4TB to replace it with, just to be safe

Running v5.0.6*, and I've started noticing some drive sounding noise coming from the server, so I took a look at some SMART reports. According to http://lime-technology.com/wiki/index.php?title=Troubleshooting#Obtaining_a_SMART_report, I really don't have anything to worry about because I'm not seeing any issues with Reallocated Sectors, Current Pending Sectors, Temperature, or UDMA CRC Error Count, but I do see a few items that have quite rather high error counts, and would like to get some expert opinion. Please see attached SMART reports and let me know if you think I've got anything to worry about. Thanks! FreeMan * Yes, I know the first thing I should do is upgrade. However, my backups stopped running for a while without me noticing, so I'm waiting for them to finish (CrashPlan - it'll be a few more days), and I want to be sure I have a clear plan before I start. I'm getting there, I promise! smarte.txt smartG.txt

=== 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!

I chose this because they are generally small video clips from the cell phone, and I was hoping to fill in smaller gaps on disks with minimal space. Guess I chose wrong. That, combined with the fact that a short video from the cell phone (at 1920x1080) is 1GB + doesn't really make it 'small'. I've increased the minimum size to 1GB, and I will probably switch fill methods, as well. I'll report back when the mover's had a chance to run, to see if it's worked OK. Thanks!

I've got several reports like this in my log file: Why would the mover be attempting to put files on a disk without enough space? Attached is a screen shot of the share setup, and there is currently 4.3TB of space available to the share.

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

Great tip, Weebo! And the results of my preclear: Preclear Successful ... Total time 81:00:40 ... Pre-Read time 14:59:36 (74 MB/s) ... Zeroing time 17:25:10 (63 MB/s) ... Post-Read time 15:32:50 (71 MB/s) That was a 2-pass on a 4TB HGST NAS drive. That's ~48 hours for the 2nd pass, but only about 33 hours for the first pass. Lots of varying use on the server over the last 3 days, so I guess that could be enough to account for the difference. Also, it's plugged into a slow card - I'll rearrange all my SATA connections when I rearrange the drives here in the next few days. Since that's the 2nd & 3rd run (the first failed just before the pre-read), and there have been 0 pending sectors the whole time, I think I'll call this one good!

I got an error on line 1182: read_speed=`/boot/readvz if=$1 bs=$units count=$bcount skip=$skip memcnt=50 2>>/tmp/postread_errors$disk_basename | awk '{ print $8,$9 }'` because it's hard coded to /boot Yes, I read the readme.txt indicating they both needed to be in /boot, but I didn't really think you meant it... Could you change the "`/boot/readvz" to "`./readvz" to allow the preclear_bjp.sh and readvz to be in the same directory, whatever it may be? I'd give it a shot, but it already took 32 hours to get through the first 9 steps, and I don't want to go through that again just to find that it won't work. I've moved readvz to /boot for now...

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?