itimpi
-
Posts
20,026 -
Joined
-
Last visited
-
Days Won
55
Content Type
Profiles
Forums
Downloads
Store
Gallery
Bug Reports
Documentation
Landing
Posts posted by itimpi
-
-
Unraid only supports booting off the flash drive (and loading the OS into RAM. Not sure why you have to ‘interrupt’ the boot sequence - the flash drive should be set as the default boot drive in the BIOS to avoid this.
Have you read this section of the online documentation accessible via the ‘Manual’ link at the bottom of the GUI or the DOCS link at the top of each forum page. It covers transferring the licence to a new flash drive. -
I would definitely be worried about that on a new drive - particularily if the number is still increasing.
-
20 hours ago, JonathanM said:
maybe look into the tuning plugin?
That will not allow you to change the scheduling as Unraid is still responsible for starting the checks. However the standard scheduling can handle quarterly.
-
What you need is the parity swap procedure which is designed for exactly this scenario. It allows you to upgrade a parity drive to a larger one and then use the old parity drive to replace the failed data drive.
-
1
-
-
20 minutes ago, christobaass said:
Any ideas? Greatly appreciated! Thanks!
Are there any periods within the time spanned by the syslog in the diagnostics you posted that you know this occurred to help narrow the search criteria.
-
Just now, FrooFrooFluffyBunny said:
would i need to destroy the pool and create from scratch
This. You cannot do an ‘in place’ encryption.
-
2 hours ago, guyola said:
but they are in a unknown format...
The Linux ‘file’ command can be used to work out their likely content type which can be useful in working out what app can be used to open them for examination. There is no automated way to work out the original name. The reason a file gets put there in the first place (with the numeric name) is that the system was unable to work out what the name should be. It takes manual inspection of the contents.
-
47 minutes ago, weirdcrap said:
Are you saying that you disagree that it is a RAM issue? Or just that if I don't want to address the RAM issue simply recreating the docker.img file is easy?
No idea if it is a RAM issue or not! Just pointing out that it is very easy to get the docker.img file back into a known clean state. If you continue to get corruption then either the device holding it has a problem or you quite likely do have a RAM issue.
-
It is always easy to recreate the docker.img file if it gets corrupted and restore containers with settings intact via Apps->Previous Apps so, as long as the underlying XFS file system look OK, I would probably recommend doing that.
-
If you restart in normal mode then the drive should mount OK. Look for a lost+found folder where the repair process will put any files/folders it found for which it could not find the directory entry giving the correct name.
-
As long as you have the original drives intact after the rebuild then you can always check the data integrity at a later date.
-
1
-
-
You do not mention if the arrays have parity protection? If they do then you would have to use the New Config tool to add the drive and then rebuild parity. As far as I know there should be no ZFS compatibility issues.
I believe you could also add it as a single-drive pool directly.
I have not actually tried this myself so if you go that route would like confirmation I am right.
-
1
-
-
@mattiscg just to check the obvious, have you actually set any shares to be visible on the network (by default none of them are)? You did not post your system’s diagnostics zip file so we cannot look there to see.
-
8 hours ago, J05u said:
I should have data from syslog server, I will try to attach that now
Had a quick look there and nothing shows up to indicate the cause of your issue.
The last thing logged appears to be at just after 12:30 at night - do you by any chance have anything scheduled to start then?
-
The fact that drives are doing a parity sync should be irrelevant.
You do not mention what type of SMART error it is and since you did not post your system's diagnostics (which includes amongst other things SMART reports for your drives) we cannot look for ourselves to see if there appears to be genuine problem.
-
The syslog in the diagnostics is the RAM version that starts afresh every time the system is booted. You should enable the syslog server (probably with the option to Mirror to Flash set) to get a syslog that survives a reboot so we can see what leads up to a crash. The mirror to flash option is the easiest to set up (and if used the file is then automatically included in any diagnostics), but if you are worried about excessive wear on the flash drive you can put your server's address into the remote server field.
-
17 minutes ago, RBK-Serwer said:
If i make update for 59 $ I have updated life time but no vm and docker?
No - you DO get all Unraid features (including VMs and Docker) and keep your lifetime update status. All releases of Unraid are functionally equal, and the web site should make this clearer.
-
You have this in your syslog:
Apr 23 09:32:36 Tower root: Fix Common Problems: Error: Macvlan and Bridging foundso it appears you are using macvlan for docker networking. If using macvlan then for stability you need to disable bridging on eth0. The alternative is to use ipvlan for docker networking.
-
You could try installing the nVidia Drivers plugin. Whether it supports that card or not I have no idea.
-
18 hours ago, apmiller said:
Submitted reset request to support, now waiting on reply.
Did you get an automated acknowledgement of your request?
-
Do you have any drives showing as unmountable as if you have any files on those drives will not currently be available? You are likely to get better informed feedback if you attach your system’s diagnostics zip file to your next post in this thread. It is always a good idea when asking questions to supply your diagnostics so we can see details of your system, how you have things configured, and the current syslog.
-
59 minutes ago, Lien1454 said:
So would you say an ssd is more suitable?
That is what most people seem to use for pools although it is not mandated.
-
1
-
-
1 hour ago, Napoleon said:
Nice position untill they decide to introduce Unraid 7 and tell me my lifetime purchase is obsolete? Sounds like that is what's in the post
Except that Limetech has already explicitly said that they intend a Lifetime subscription to remain valid forever and they do not intend to do that behavior of a 'new' version' that you then have to pay for. Unraid 7 and Unraid 8 were given as examples of free upgrades for lifetime licences in the various podcasts on this subject.
-
36 minutes ago, Lien1454 said:
The Hard drive I have the docker image on never spins down. Is this normal?
Yes that drive will be kept spinning any time docker is running.
Most people tend to put the docker.img file onto a pool (cache) by configuring the 'system' share appropriately. This stops keeping the array drive spinning and also improves performance.
-
1
-
cant access my WebPanel
in General Support
Posted
You should be able to get the system's diagnostics zip file created via ssh. Posting that here might give us a chance to see what is going on.