trurl

Put your flash in your PC and let it checkdisk.

So I did.

Your changelog is not clear about this As an additional request: The script should look for the readvz file in the same folder as the actual script is, for people who dont like their /boot/ to be filled The actual script it uses is up to you, since no script is included. You have to take care of that yourself.

Just thought I would comment on how useful this plugin is to me right now. I am currently in the process of upsizing parity and disk1 from 4TB to 6TB. Then I will reuse those 4TB disks to upsize disk4 and disk5, my last 3TB disks. Counting preclears for the new drives, and parity checks after each rebuild, this whole process will take well over a week. Thanks to this plugin, I can easily keep track of which drives are where as they get reassigned. I will wait until all the upgrades are done, then shutdown and remove the 3TB drives I won't be using in the array anymore, and put all the drives in their final positions. Only had to shutdown and open the case at the beginning, and will do it once again at the end.

You can resize in the GUI.

Here Not sure if the workaround is still needed or not. Maybe it was fixed in rc2.

The dockers autoupdate based on what is available to download from the Plex website: https://plex.tv/downloads/1/archive I'm a little confused here. Plex notified me in the interface - I hadn't visited the forum to find out about an update. And the archive page you've linked to has version 0.9.12.8, whereas the docker has version 0.9.12.4. Granted, it does say "Please install manually" and I can click that text do download 0.9.12.8..., but I have no idea what I should do with that file (if anything)...? Just restart your plex docker and it will get the latest version when the docker starts.

TL;DR - Do the faster and the original preclear scripts continue the post-read all the way to the end even if it has already read non-zero data? Longer story I just finished (finally, successfully) preclearing a 6TB WD Red with the faster preclear. All attempts were using the plugin but I don't think I would have had a different result if I had run the scripts from the command line. The 1st attempt, I did 1 complete cycle, and after it was finished, it said the disk passed, and the smart data was good, but the post-read had detected non-zero data. The 2nd attempt, I skipped the pre-read and just did the clear and post-read. Same result. The 3rd attempt, I just did the post-read, but with the original script. Same result. Then, I decided to change my connections a little since I had been using an eSATA enclosure on an expansion card, and my intent was to put the drive in as parity using a motherboard port. I didn't expect that to make any difference since I had precleared several drives like that in the past, just nothing larger than 4TB. And I don't think the connections did matter, because I discovered what I think may have been the actual problem. Before booting up after the changes, I did a memtest and discovered that 1 of my 2x8GB memory sticks was bad. I tested each of them separately in both slots and it was definitely that 1 stick. After removing that memory and just running with only 8GB RAM, I did the preclear again. This 4th attempt skipped the pre-read and just did the clear and post-read with the faster script. Success! But, see my question at the top.

Probably not related, but you have filesystem corruption on disk3Aug 8 12:12:32 Tower kernel: REISERFS error (device md3): reiserfs-2025 reiserfs_cache_bitmap_metadata: bitmap block 184385536 is corrupted: first bit must be 1 Aug 8 12:12:32 Tower kernel: REISERFS (device md3): Remounting filesystem read-only Aug 8 12:12:32 Tower kernel: REISERFS warning (device md3): clm-6006 reiserfs_dirty_inode: writing inode 1507 on readonly FS

Already have this one working. A panorama my wife took on the South Island of New Zealand.

I recently had an incident and while troubleshooting it I noticed a surprising "interaction" between Cache Dirs and Unassigned Devices. I have a couple of SMB mounts in Unassigned Devices, and when I went into Cache Dirs to change the includes or excludes I noticed that those SMB mounts are selectable. Does that mean cache dirs will scan those SMB mounts unless you specifically configure it to either exclude them on not include them?

Typedf and see what you have for available space in tmpfs. Well on my Media server, the available space in tmpfs is 128,476. On the Test Bed Server, the available space is 129297. However, both servers have been rebooted to get rid of the extra two buttons so the present available space number (on the Media server) is not really a good indicator of what it was when the plugin installation was being run. See here for some discussion and a fix for tmpfs allocation.

Typedf and see what you have for available space in tmpfs.

Have you enabled docker in Settings - Docker?

Working for me now, including confirmations. Do have this reported by JustinChase earlier though, using chrome. It does cause a horizontal scroll bar, so I can scroll right and see the whole thing, and the part I can see without scrolling is enough. Haven't tried from other computers or browsers so not sure if other screen resolutions would have this or not.

You must delete every file and folder in flac share before the GUI will let you delete the share. Very easy to do this in Midnight Commander. Just type mc

deleting the .cfg file will not help since unRAID will automatically create a user share for any folder at the top level of cache or array data disk. The folder must not be empty or the GUI would let you delete the share. Post the result of ls -al /mnt/user/flac

Thanks. CA should officially replace the repository system IMO.

Does this make your Docker Search plugin obsolete? If so, should we uninstall that before applying this update?

The normal sequence is that after pressing the button a popup windows appears (see picture) telling that preparations are taking place, once these are done the normal shutdown or reboot screen is shown. You are saying none of this happening? I had to reboot for a different issue and after startup the buttons are gone as expected since I had uninstalled the plugin. I like the addition of the context menu and feel like that somewhat addresses the concern I had regarding confirmation but I would still like confirmation added based on the confirmation settings. It is not that difficult for me to accidentally click something when using my touchscreen notebook. I haven't reinstalled the plugin yet because I'm not sure I want to have that accident. Also, I would like some more feedback about the progress of the "preparations" like we get on the Array Operations page. Having said all that I would like to thank you once again for your many contributions!

Edit container and click link to docker hub.

That doesn't seem right. I may not have as much media as many, but I do have about 1000 movies, several hundred TV episodes, and several thousand music files in my plex library. My plex appdata folder is just over 3GB.

I am getting different behavior with the latest system buttons. Instead of a context menu, I get an additional powerdown button added to the 2 buttons that were already there. This also causes all the buttons at the right to wrap to a line below. I haven't tried to push any of them. Also, when I tried to uninstall it seems to just go back to the 2 buttons instead of removing it completely. Tried clearing browser cache but didn't help. Using chrome.

When I look at mine, I see Logitech Media Server Version: 7.9.0 - 1431440256 Since I didn't do anything to make it update, I assume it just gets the latest version when it installs. You might try just restarting it, or if that doesn't work, reinstall it from your template.

Interesting question - I like and am also keen on this. I tried creating a volume mapping to /boot, but that didn't want to work (/boot doesn't even show up in the host path drop down). I created a soft link from /cache/boot to /boot (ln -s /cache/boot /boot). But this, to me at least, is quite a large security risk. It could inadvertently give access to the flash files where you don't want it, especially if /cache is shared. Another option that springs to mind... create a backup folder on either the cache or a disk / user drive. Don't export it and create a cron job to copy all files periodically. Or do this manually each time you upgrade or change anything (which is what I do - each time I upgrade I backup the entire flash drive to my windows file server which is subsequently backed up to CrashPlan anyhow ). UPDATE Seems you can do this: [*]Create a mapping in the advanced settings. I did /boot to /boot, and made it read only. [*]Open the CrashPlan client and click the Change button on the backup tab [*]Check the "show hidden files" checkbox in the client (I'm using the CrashPlan-client via RDP from the host). [*]Once you've done this, all sorts of wonderful folders spring to life. Including /boot. [*]Select it and ok away, presto it is backing up (238 files for 700 MB in my case) Currently backing up boot > bzroot (7.59% @ 2.6Mbps) Glad you were able to figure it out :-) Would you be able to explain where this advanced settings file is and what exactly I need to do to create this mapping? There is a slider in the upper right to enable advanced settings. Since this is about backing up the flash, you should be aware that unRAID stores the array configuration and start/stop status of the array in /boot/config/super.dat. This is important to know for 2 reasons. The most important reason is that you don't want to restore a backup with a different array configuration than you actually have. There was a user that made a backup of his flash, and after that, he upgraded his parity drive and used the old parity as a data drive. Later when trying to solve some problem, he restored his old flash backup. Unfortunately, this made unRAID think that his old parity (now containing data) was still the parity disk, and it began writing parity to it. Not good. The other reason is that if you make a backup of the flash with the array started, and you later restore that backup and boot, then unRAID will think that the array wasn't stopped before it was shutdown, and it will do a correcting parity check due to an unclean shutdown.