itimpi
-
Posts
19,815 -
Joined
-
Last visited
-
Days Won
54
Content Type
Profiles
Forums
Downloads
Store
Gallery
Bug Reports
Documentation
Landing
Report Comments posted by itimpi
-
-
Your USB key has been set to read-only. This could be because there is file system corruption or because the USB stick is starting to fail.
The USB stick can be checked by plugging it into a Windows PC and then letting Windows scan it and repair any errors.
if you decide it is failing and want to purchase a replacement USB stick then it is recommended that you get a USB2 version as they tend to me more reliable than USB3 and since Unraid runs from RAM after initial boot there is no measurable performance hit.
-
There have been reports for some time that some hardware configurations only boot in GUI mode. Not sure the cause has ever been identified. Most people just leave the system booting into GUI mode even if they never intend to use the GUI locally.
-
You probably also want to set the Minimum Free Space value for the share to be more than the largest file you expect to move to the share. This gets important as the disks fill up as it stops Unraid from selecting as a target for a new file any disk that has less than that amount of free space.
-
I have seen reports that some of the ISP provided routers seem to stop servicing the local LAN if internet connectivity is lost. I wonder if the router you were using suffered from this defect?
-
57 minutes ago, Frank76 said:
Last night I disabled the Direct IO, and rebooted, and woke up this morning to the same issue. It seems like my backups are too IO intensive for NFS to handle. I'm getting very close to downgrading, but I have lost the ability to go back to 6.5.x (at least easily). In the mean time I will disable my backups. Hopefully that will prevent my server from crashing again.
If you need to downgrade the manual method will still work. It is likely on;y the automatic downgrade via the GUI that is no longer possible.
-
I am not sure anyone knows the cause yet which makes it impossible to estimate a fix ETA.
-
I believe this is expected behavior (albeit not very intuitive) as it the most recent ‘Next’ release. Changing it to ‘stable’ would show the 6.6.0 release.
A number of other people have commented that the most recent release should always be shown as otherwise some people may not realise they should update and will remain on the last rc that predates the stable release.
-
When using SMB you use server/sharename (I.e. omit the /mnt/user part which is not visible at the Samba Level)
-
Have you tried booting your server in Safe Mode? If this eliminates the problem then you almost certainly have a plugin that is causing your problem.
-
The GUID that is being referred to is that of the current USB you are using. I suspect your problem is the second point listed. What brand/model of USB drive are you using? It may be one where the manufacturer is not giving each drive they make a unique GUID.
if you think it is something else then you may need to contact LimeTech support to get it resolved.
-
On 9/15/2018 at 5:45 PM, xorinzor said:
Yes, but if I click on the disk it isn't showing the live values from S.M.A.R.T. is it?
So if those values are stored / cached somewhere, then surely they can just be displayed in the dashboard semi-live without impacting the disk itself, this would fix the entire issue.
I think in this case you ARE seeing live values. If you take that action it is probably assumed that you are happy to take any performance hit the action might cause.
-
There can be a delay before the GUI is updated. What do you have under Settings->Disk Settings->Tunable (poll_attributes) ? The default value of 1800 means that the disks are only polled every 30 minutes. You may want a much smaller value - something like 300 (5 minutes) is what I use.
-
Upgrade from rc1 appears to have gone through without issue.
Well timed as I was just about to report the issue with dockers not updating!
-
8 hours ago, testdasi said:
Wow, does this mean the mover is not to be trusted until the bug is fixed? ?
This is one of those issues that while genuine is very hard to reproduce in practice. The timing window for hitting this error will be very narrow so probably not an issue for most people in typical usage.. Definitely will not be an issue if running mover at its default of early morning when nobody is likely to be using the server.
-
It is not a bug in unRAID but the way it is designed to work. The problem is that once the free space disk drops below the value then unRAID stops copying new files to the drive.
i think you are probably going to have to manually copy these very large files directly to the target disk (which bypasses the Minimum Free Space setting) or you are going to have to add a lot more disk space.
-
What value do you have for Minimum Free Space? It needs to be larger than the file you are trying to copy. That is the only way you will get mover to select the correct disk. The problem is that is not mover that selects the disk (and can thus take into account the file size) but the underlying unRAID disk handler.
-
Unfortunately that is not how unRAID currently works. If non of your disks have enough free space for the file then you have a problem as unRAID will never split a file across disks.
-
You need to have the Minimum Free Space value for the share to be larger than the largest file you will be copying. That stops a disk with less than that amount of free space from being selected as the target by mover.
-
I would it is time to update the minimum requirement for unRAID v6 to be 2GB?
-
1
-
-
@digitalfixerIf you are running any sort of adblocker, have you made sure that the unRAID server has been whitelisted? Adblockers are notorious for interfering with the correct functioning of the unRAID GUI.
6.6.3-- IE11 does not work.
in Stable Releases
Posted
That sounds like a reasonable approach. At least that way the users will know what the problem is rather than continually getting this raised as a support question.