12 minutes ago, FreeMan said:

Under Shares | Disk | Security.

That's right, I remember now, another tab in Shares. I just never use them myself. I always go to Midnight Commander if I want to work with the disks.

Just now, trurl said:

That's right, I remember now, another tab in Shares. I just never use them myself. I always go to Midnight Commander if I want to work with the disks.

 

I'm sure there's a setting in MC, but with the lengths of my paths & file names, MC just doesn't show enough for me to be sure I'm working with the right file sometimes.

I need an over/under window split instead of side-by-side.

 

5 minutes ago, FreeMan said:

I need an over/under window split instead of side-by-side.

Options - Layout.

1 hour ago, FreeMan said:

 

I'm sure there's a setting in MC, but with the lengths of my paths & file names, MC just doesn't show enough for me to be sure I'm working with the right file sometimes.

I need an over/under window split instead of side-by-side.

 

Also, you can usually drag the corner of the terminal window to expand it whichever way you want, and the contents will fill the new space instead of expanding the print. I know putty will do that. Combined with changing the layout, I'm pretty confident you should have very few files that would wrap.

 

Check out the dupeguru docker as well, it's very versatile when it comes to cleaning up this kind of mess.

1 hour ago, jonathanm said:

Also, you can usually drag the corner of the terminal window to expand it whichever way you want, and the contents will fill the new space instead of expanding the print. I know putty will do that

That's genius!

 

hangs head in shame for not having thought of that himself any time in the last... 6 years

 

Edited March 7, 20188 yr by FreeMan

How can I fix this?

 

 

Share Docker set to cache-only, but files / folders exist on the array

You should change the share's settings appropriately  or use the dolphin / krusader docker applications to move the offending files accordingly. Note that there are some valid use cases for a set up like this. In particular: THIS

 

The share is already configure as a cache only but it seems that the files are still in the array. How can I fix it? using "mc" in command line and moving the files, but where?

25 minutes ago, L0rdRaiden said:

The share is already configure as a cache only but it seems that the files are still in the array. How can I fix it? using "mc" in command line and moving the files, but where?

You would have to find the array disk the files/folders are on and move them to cache.

 

Alternatively, you could go to Settings - Docker and stop the service, change the Docker share to cache-prefer, run mover, then restart the service.

I have docker and VM shares configured as cache only, I have even exclude the disk, and the share show this message "Share is outside the list of designated disk"

then I click on mover time passes but the data is still in the disk.

 

I will try the other method but why the mover doesn't work?

2 minutes ago, L0rdRaiden said:

I will try the other method but why the mover doesn't work?

Mover can't move anything that's in use / open

1 minute ago, L0rdRaiden said:

I have docker and VM shares configured as cache only, I have even exclude the disk, and the share show this message "Share is outside the list of designated disk"

then I click on mover time passes but the data is still in the disk.

 

I will try the other method but why the mover doesn't work?

If a Share is set as cache only then files will never be moved from the array to the cache.    If you want this to happen then you need cache-prefer to be set.    Turning on the help in the GUI gives more detail on how the different settings work.

Just now, Squid said:

Mover can't move anything that's in use / open

The docker and VM add-ons where stopped, I will try disabling shared folders.

 

3 minutes ago, L0rdRaiden said:

I will try disabling shared folders.

What do you mean by this?

4 minutes ago, itimpi said:

If a Share is set as cache only then files will never be moved from the array to the cache.    If you want this to happen then you need cache-prefer to be set.    Turning on the help in the GUI gives more detail on how the different settings work.

 

 

Thanks, now is moving files, I was using cache only due to this message, maybe it should be changed.

 

 

Default docker appdata location is not a cache-only share

If the appdata share is not set to be cache-only, then the mover program will cause your docker applications to become inoperable when it runs (6.1.x). Under 6.2+, this setting should not affect the operation of the application, but it will definitely impact significantly the performance of the application. Fix it via

 

1 minute ago, trurl said:

What do you mean by this?

I have some shares, shared with NFS although I was not using another computer to access them

Edited March 9, 20188 yr by L0rdRaiden

I seem to be getting a spurious notification about "inotify-tools set to install"!   I cannot find what might be causing that as I do not have any reference to it that I can see in the nerd pack settings.   What is actually checked to cause this message to be output?.

4 hours ago, itimpi said:

I seem to be getting a spurious notification about "inotify-tools set to install"!   I cannot find what might be causing that as I do not have any reference to it that I can see in the nerd pack settings.   What is actually checked to cause this message to be output?.

/boot/config/plugins/NerdPack/NerdPack.cfg

 

A line beginning with "inotify-tools" set to be "yes"

 

Probably time to get rid of this test since inotify tools has been in unRaid since 6.3.0-rc6 and NerdPack was updated back then to not give you the option to install it.

Edited March 10, 20188 yr by Squid

54 minutes ago, Squid said:

/boot/config/plugins/NerdPack/NerdPack.cfg

 

A line beginning with "inotify-tools" set to be "yes"

 

Probably time to get rid of this test since inotify tools has been in unRaid since 6.3.0-rc6 and NerdPack was updated back then to not give you the option to install it.

I actually have no entry at all in that file for inotify-tools, let alone one set to “yes”!   I seem to remember removing it at around the time inotify was built into the standard unRAID release.

1 hour ago, itimpi said:

I actually have no entry at all in that file for inotify-tools, let alone one set to “yes”!   I seem to remember removing it at around the time inotify was built into the standard unRAID release.

Looking at the code, I don't see how it can fail.  Does it consistently give you the warning?  Can you post your nerdpack.cfg file?

1 hour ago, Squid said:

Looking at the code, I don't see how it can fail.  Does it consistently give you the warning?  Can you post your nerdpack.cfg file?

 

The issue appears to be consistent as far as I can see.  Attached is the requested file.

 

 

NerdPack.cfg

 

Mainly because my keyboard is worn out from replying "Uninstall Advanced Buttons", today's update features an "Update Assistant" which sits on the Tools Menu (next to Update OS)

 

This performs a couple of checks to see if you're going to have problems if you update your OS.  In otherwords, you run it before hitting Update OS

 

Problems it will catch:

• Plugins up to date
• Incompatible plugins with the updated unRaid OS
• At least 4G memory
• Any disabled disks present (doesn't actually hinder an update, but really something you'd be nuts not to take care of prior to an update)
• Cache drive partition starts on sector 64 (would catch all those "unmountable" cache drives after updating)
• Basic RW test to the flash drive
• Zenstates set up in the go file
• Any excess parameters on the emhttp line in the go file

Tests are not definitive, there may be valid use cases if there's a failure, but it will at least hopefully save me from buying another keyboard again  

 

EDIT: More tests coming...

Edited March 15, 20188 yr by Squid

3 minutes ago, Squid said:

but it will at least hopefully save me from buying another keyboard again  

Wishful thinking.

 

I bet you just get a bunch of questions about why the assistant is saying that Advanced Buttons isn’t compatible.

9 minutes ago, wgstarks said:

Wishful thinking.

 

I bet you just get a bunch of questions about why the assistant is saying that Advanced Buttons isn’t compatible.

And preclear plugin of course.

4 minutes ago, trurl said:

And preclear plugin of course.

And OpenVM tools, the older libvirt hot plug, etc.  Its not static, dynamically updated whenever you execute the script, and it bases it results not on the version of unRaid you're currently running, but what the version available is.  Will also adjust itself to whether you're on the stable or next branch of the OS.  Tested down to unRaid 6.3.5 as current version, but should work for users running 6.1.9+

Edited March 14, 20188 yr by Squid

Impressive, but what I meant is we will still get questions about preclear.

 

And everything else of course. I have seen lots of questions asking why they are getting a warning from FCP, and how do they fix it, when the warning actually already answers those questions.

I upgraded to 6.50. from 6.4.1 last night, and the upgrade went fine....

 

 

However, prior to that I noticed (IIRC) that Common Problems had an update that offered one new item, a script that offers a check list for upgrade compatibility (6.4.1 -> 6.5.0 for example), I thought it would be good to update and test it out prior to the upgrade.

 

Everything came back clean except for my cache drive, complaining that my SSD cache did not start on sector 64, with a link to a process of moving items to array, formatting, and moving back (on at least 6.4.0).

 

My SSD in a Samsung PM961 512 GB NVMe drive formatted as btrfs (originally formatted by unraid in 6.3.5). Up until now, coming from 6.3.5 to 6.4.0 to 6.4.1 I have had no issues with it not being detected, but I figured why not, this is pretty straight forward. So I followed the advice, and:

 

- Marked cache shares to move to array

- "moved"

- stopped array and changed to XFS for my cache, formatted, then changed back to btrfs and formatted

- started array

- ran script, still error 64

- stopped array

- unassigned cache

- started array

- performed upgrade

- added ssd back as cache, was picked up as btrfs

- did the same mark to xfs, format, mark as btrfs, format

- still sector 64

 

So with the above, is it really an error or issue here? I am only using unraid, to format/reformat (not UD) the SSD and is continually being flagged for not starting at sector 64, what gives?

 

 

 

 

 

 

 

 

 

 

Edited March 15, 20188 yr by cybrnook