itimpi
-
Posts
19668 -
Joined
-
Last visited
-
Days Won
54
Content Type
Profiles
Forums
Downloads
Store
Gallery
Bug Reports
Documentation
Landing
Posts posted by itimpi
-
-
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
-
-
19 minutes ago, Cressio said:
Looks like they’re actually moving now. I imagine/hope this is worthy of a bug report and not intended behavior?
Looks like you might be falling foul of the behaviour described in the Caution in this section of the online documentation accessible via the Manual link at the bottom of the Unraid GUI. Not sure there is much that can be done about it as it is a quirk of the way Linux handles move operations.
If you can configure the docker container to use Copy/Delete instead of 'move' then you would get the result you expected. The alternative is to set that share to have the 'downloads' pool as its primary storage.
-
3 minutes ago, apmiller said:
Are you able to reset my license? I did transfer from my license from the old server to this new server over the weekend and I'm currently ineligible to use different flash drive currently.
You will have to contact support as they are the only ones who can handle licence issues.
-
1 hour ago, Napoleon said:
This still sounds like the older versions will be left vulnerable in the future unless we pay more money for the new updated version?
Yes, but it is unreasonable to expect a small company like Limetech to continue to support obsolete versions of their software foreveri think the Limetech policy is significantly more generous than I have seen offered on many other products..
-
28 minutes ago, Napoleon said:
Am I missing something here?
It is not quite that simple.
You get any security updates that are available for the release you are on at the end of the years paid update period. What you do not get is security updates that are only available in future releases.
As an example Limetech says that if when your update support period expires you are on 7.0.x then you get all updates for the 7.0.x releases even though you have not taken out another years of updates support. While Limetech is working on and releasing the next release beyond your current one (i.e. 7.1.x releases) then they will (if possible apply patches to the 7.0.x releases. Once they start releasing the second release beyond yours (i.e. the 7.2.x releases) then the 7.0.x releases will no longer get any more updates.
At any point you can decide to take out another year of update support and then you the update to the release current at that time, and after another year the same principle as outlined above applies (which could be you being on a later release than you started the year on).
-
With high-water allocation then the relative size of disks can become relevant as the high-water cutover points are based on the largest drive but your screenshot does not show the sizes so we cannot see if the behaviour is what should be expected.
-
16 minutes ago, karash said:
I was able to reboot during the data rebuild and that brought the shares back online.
If you did tis before the rebuild completed then the rebuild would be started again from the beginning.
-
The end of both logs finishes with errors along the lines of:
Apr 22 08:33:48 Tower kernel: ata14.00: exception Emask 0x0 SAct 0x0 SErr 0x0 action 0x6 Apr 22 08:33:48 Tower kernel: ata14.00: irq_stat 0x40000001 Apr 22 08:33:48 Tower kernel: ata14.00: cmd a0/01:00:00:00:01/00:00:00:00:00/a0 tag 7 dma 16640 in Apr 22 08:33:48 Tower kernel: opcode=0x12 12 01 80 00 ff 00res 00/00:00:00:00:00/00:00:00:00:00/00 Emask 0x3 (HSM violation) Apr 22 08:33:48 Tower kernel: ata14: hard resetting linkNormally we would think these were power/sata cabling related but the fact it has occurred at the same point twice suggest it may really be a drive problem if ata14 is the new drive.
-
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.
I strong;y suspect that you have something incorrectly configured. It seems unlikely that mover will report files ‘exists’ when it does not so I suspect that you do not have things set up correctly to get the behaviour you want. -
You may find this section of the 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 useful in understanding what is happening and what actions to take.
-
Have you tried clicking on the orange icon for the drive on the Dashboard to see what error it is? If it is a CRC error then if you. Lick on the Acknowledge option Unraid will only notify you again if it increases.
CRC errors are connection related rather than a disk problem and would be triggering retries. They never reset to 0. Occasional CRC errors is not really something to worry about but if you get lots of them you should look into the power and SATA cabling to the drive as the most likely culprits.
-
You can use the procedure documented here in 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. The Unraid OS->Manual section in particular covers most features of the current Unraid release.
-
2 minutes ago, DeDude said:
Wow. Both drives are working in freakin Windows. Thats a statement. I dont know why Unraid is using Anti-Cheat/DRM techniques to identify a HDD - just do it with the volume ID maybe? Or would that be too easy? Gees, i dont wanna buy a new HDD just for this :'D
Never heard of 2 HDD drives really having the same serial number before. I feel there must be something that can be done, but no idea what. -
That is a clean looking check with no errors reported so I would expect all data to reappear after running the repair.
-
You just ran a check - not a repair. To do any repair you need to run without the -n option. If it asks for it you should add the -L option. After that the disk should mount when you restart the array in normal mode.
-
If you add a parity drove to an existing Unraid array then the sync is automatic when the array is next started. If this did not happen then that implies you did something other than the normal process for adding a parity drive. -
Another option would be to always boot into Unraid, and then run Linux as a VM under Unraid if you want both Unraid and Linux running simultaneously.
-
1
-
-
If the sever is simply rebooting rather than shutting itself down then this almost invariably indicates a hardware issue with the commonest being power or thermal type issues. If you get either of these then nothing will show up in the logs.
-
7 minutes ago, jul9000 said:
so maybe the old parity drive also only had power connection problems
Continual resets on a drive showing up in the syslog are typical symptoms of power/connection problems.
The simplest check is to run the Extended SMART test on the drive. That test is completely internal to the drive so If that passes then then the drive is normally OK. The only other likely cause would be insufficient power reaching the drive.
-
1
-
-
Unfortunately the syslog you posted (and the version automatically included when getting diagnostics) is the RAM version that starts afresh every time the system is booted. so we do not know what happened prior to the reboot. 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 preceded the reboot. 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.
When you say the system got a 'message' to terminate what do you mean? If you mean it started a tidy shutdown is there any chance someone/something (e.g. a cat) could have pressed on the power button to trigger a shutdown? If you simply mean it rebooted itself then this is normally a hardware issue of some kind.
-
The SMART test failing is never a good sign as it runs completely internally to the drive. The only external factor that springs to mind that could cause this is power issues.
If the drive cannot past the Extended (let alone the short) SMART test then we would normally think that it needs replacing.
Corrupted / Missing Flash Drive / Missing License Key
in General Support
Posted
Did you get an automated acknowledgement of your request?