-
Posts
19,716 -
Joined
-
Last visited
-
Days Won
54
Content Type
Profiles
Forums
Downloads
Store
Gallery
Bug Reports
Documentation
Landing
Report Comments posted by itimpi
-
-
It does not happen on my VM’s tab so I suspect there must be some other factor at play.
-
This is still the behaviour around pause/resume in that unRaid built-in reporting only gives figures for the last increment.
It might be worth mentioning that if the Parity Check Tuning plugin is installed it will give the correct information in Notifications raised by the plugin and will also update the Parity History information so it is correct for the whole run taking into account any pauses or resumes. It will do this even if you are not using its capability of running the operation in increments.
-
The only time I had such a problem it turned out to be on my Windows client side in that it’s network link failed under load.
-
7 hours ago, dimon said:
as @mgutt has mentioned, i have never used the Cache Pool.
After Upgrade from 6.8.x to 6.9.0 and then 6.9.1 I have problems with the increasing of rootfs partition.
because the docker instances used /mnt/cache for appdata
If you do not have a cache drive then you need to reconfigure them to not use ‘mnt/cache’. I do not see how that could have worked on any unRaid release with no cache drive present as if you do not have a cache drive that location is in RAM. In such a case you should use /mnt/user/appdata as that allows files to be on either the array or a cache drive.
-
@JokesOnYou77 If you spot any such discrepancies then please continue to point them out so they can be corrected.
it is worth pointing out that the help built into the GUI should always be considered the most authorative source as that will be created by whoever is involved in the implementation.
-
There are the detailed notes posted in the announcement thread for each release.
In addition there is the information here from the online documentation that can be accessed via the Manual link at the bottom of the unraid GUI.
-
1 minute ago, xrqp said:
Does this also apply to Unassigned Devices, with hot plugging a SATA spinning disk, and a USB spinning disk?
No - UD is hot-plug aware as long as your hardware supports it. That should always be true for USB devices and is normally true for SATA/SAS ones.
-
That is a browser issue that is typically fixed by clearing the browser’s cache.
- 1
-
You might still want to add appdata to the folders to be ignored as even with User Share scanning disabled the folder will still be found and scanned when the drive contains that folder is scanned.
-
Not sure that is a bug as you bypassed the GUI. The web GUI disk status is only updated at the interval set under Settings -> disk Settings -> Tunable (poll attributes) which defaults to 1800 seconds (30 minutes). I tend to reduce this value on my own system to something like 180 (3 minutes).
-
The 'find' command is almost certainly the Folder Caching (Cachedirs) plugin doing its initial scan since you have just rebooted.
You probably want the appdata share to be excluded as if you have something like Plex installed it can contain millions of files.
-
I have seen posts suggesting that the fuse implementation used to support unRaid User Shares can impose throughput limits so it is likely to be the reason you are capped at the sorts of speed you quote.
-
4 minutes ago, boomam said:
I saw that.
What's the advantage to doing that?
Not tried it myself so I do not really know. Have been waiting to see feedback from those who have tried it do get a feel.
-
1 minute ago, boomam said:
Or is there more for me to do?
You can (optionally) elect with the 6.9.0-rc2 release to not use an image file at all for docker containers and store the files directly on the target drive.
-
A pool HAS to use BTRFS if it includes (or will in the future include) more than 1 drive. If a pool is always going to be a single drive then XFS is more efficient and more resilient against crashes, but BTRFS has additional functionality.
-
When you give a container it’s own IP address then I think the host port setting is ignored and you can only use the port the container has configured. I could be wrong about that but that is my understanding.
- 1
-
1 hour ago, RealActorRob said:
Case-sensitive names is somewhat (to me) strangely under security settings for the Share.
Shares > 'Click Sharename' then it's there under SMB Security Settings.
it is a Samba specific issue, so if it is going to be settable at the share level that was probably as good a place as any to put the setting. -
3 minutes ago, shaunmccloud said:
Yes,
It does boot fine in safe mode. Do I just make a list of my plugins and install them one at a time until I find the one that causes the issue?
Unfortunately that is the only way to pin down the culprit.
you could try listing them here to see if anyone can point at a likely suspect.
-
The mover behaviour is what is expected if files end up on the wrong cache pool.
if using Krusader you would need to use copy/delete to avoid this behaviour. This is because of a quirk in the way the ‘move’ operation is handled by Krusader. If it thinks both source and target are on the same mount point (/mnt/user in this case) it first tries a simple rename (for speed) and only if that fails does a copy/delete operation. In this case the rename is working so the file is left on the same disk rather than moved to one that is part of the target user share.
if you do the move over the network then it should always do a copy/delete so give the expected behaviour.
-
How are you moving the files between the shares? Depending on the method used this might just be expected behaviour.
-
It could be worth running the appropriate make_bootable command for your OS from the USB stick (running as administrator) . I have see cases where the USB Creator tool seems to fail writing to the boot sector to make the flash drive bootable for some reason.
-
I do not believe there is code in place to update share settings if you rename a cache pool.
Whether this should be a bug or a feature request is a moot point.
-
If using a key file have you checked that there is no new line character at the end of the phrase? This seems to be the commonest error when trying to get a phrase into a key file.
I must admit I tend to steer clear of using any encryption (except on my test server) as if you ever get any file system level corruption there is a good chance that the data on the drive will end up being lost.
-
1 hour ago, SLNetworks said:
I simply installed apps from CA and specified which ports at installation I wanted it to use. It didn't apply the settings to the app at that stage or afterwards when going into the app settings.
I am afraid that still does not give me a set of steps I can use to try and replicate your problem.
I would suggest you need to do something like providing a screenshots of docker container settings you are setting that are not being applied.
6.9.2 VM section webUI glitch
in Stable Releases
Posted
No idea - the GUI is not something I know how to look into.