itimpi

Moderators
  • Posts

    19353
  • Joined

  • Last visited

  • Days Won

    53

Everything posted by itimpi

  1. You should provide your system’s diagnostics so we can give sensible feedback. my guess is one of the drives is having problems but without diagnostics that is just a guess.
  2. mover has nothing to do with docker stopping. this will be because you have the following scheduled to run at 2:00 am Nov 5 02:00:01 UnMonkey CA Backup/Restore: ####################################### Nov 5 02:00:01 UnMonkey CA Backup/Restore: Community Applications appData Backup Nov 5 02:00:01 UnMonkey CA Backup/Restore: Applications will be unavailable during Nov 5 02:00:01 UnMonkey CA Backup/Restore: this process. They will automatically Nov 5 02:00:01 UnMonkey CA Backup/Restore: be restarted upon completion. Nov 5 02:00:01 UnMonkey CA Backup/Restore: #######################################
  3. The same is what I expect would have happened if you had stopped the array and then restarted it in Normal mode so that Unraid makes another attempt to mount the drive. The reboot should not be required.
  4. It is normally recommended to NOT leave it checked. With it checked then if any discrepancy is noticed between the data drives and the parity drive then the parity is automatically updated to match the data drives. The downside is that if you unknowingly have a data drive playing up this can end up corrupting parity which means if a data drive later fails you might have data corruption when you try and rebuild it. I normally recommend that you only do a correcting check from a parity check you start manually when you have some reason to think that parity might not be valid and have already corrected the issue that made you think parity might be invalid.
  5. This will have corrected 2 sector thought to be in error. The next check should then return 0 errors. It is recommended that the regular scheduled checks are set to be non-correcting so that you do not get a disk that is playing up corrupting parity. You normally only want correcting checks to be run manually after you have resolved any disk issues you think that you may have, or if you have reason to suspect parity may not be completely valid such as after an unclean shutdown.
  6. No - sounds like a faulty disk. You could try running an extended SMART test to confirm.
  7. As stated in the error message Windows will not allow you to log into the same server using 2 different sets of user credentials at the same time. a common workaround is to make one connection using the server’s name, and the other the server’s IP address. In such a case Windows does not realise they are both connections to the same server.
  8. It probably depended exactly when you looked at the speed At any point the speed is determined by the slowest drive currently active. With multiple drive sizes you will see it slowing down as a particular size of drive gets to its inner tracks, and then jumping up again when the build gets past the size of that drive and the next drive size becomes the limiting factor. This pattern can repeat for each drive size.
  9. The .page files are not really designed to work outside the Unraid GUI unless special action is taken in the PHP code to support this which if probably why you got the errors you mentioned. In particular the code to handle multi-language support can sometimes have unexpected side-effects. I was hoping that you might get useful error messages to help with debugging.
  10. A parity check does not even know about dockers so it will not be that stopping them but something else. for anyone to be able to give any sort of sensible suggestions as to why this is happening to you then you will need to provide your system’s diagnostics with the logs in them covering a period when this happens.
  11. I have made it clearer that the options listed are all OR selections so you only need to do one of them (although there is no damage caused if you try more than one of them).
  12. This was not present in the 6.9.2 release either although it is in 6.8.3! It just seems to be a wrapper that redirects to running the 'install' command.
  13. You could try running the .page file from the Unraid console via the php -f option so it executes within an Unraid context in case the php conflicts with something that Unraid adds as standard to .page files Also including a line reading error_reporting(E_ALL); // This option should only be enabled for testing purposes at the top of the file might provide additional information
  14. Did you see the post from Limetech that said: Maybe this is your issue because as far as I can see extraPutty has not been updated for some time.
  15. How are you ‘moving’ the files? It sounds like you may be encountering this issue?
  16. That is quite normal for the speed to go down as one moves towards the inner tracks. Drives spin at a constant speed, so because the outer tracks are physically longer they can hold more sectors and the resulting speed is higher.
  17. Once you have the 14TB drives in place and built with valid parity then you could follow the normal process of upgrading disk1 and disk2 to 14TB (with their data intact). When that completes you would have plenty of space to use unBalance (or a manual move process) to move data off the drives you want to remove and then shrink the array to the drives you want to keep. The relevant procedures are documented in the Storage Management section of the online documentation accessible via the ‘Manual’ link at the bottom of the GUI.
  18. Putting the original parity drives back is just going to result in the system rebuilding parity on those drives to match the data drives so as such will not affect data visibility. The diagnostics did not show the array started in normal mode so we could see if any data drives are not mounting (showing as unmountable) due to file system level corruption which would mean their contents would not show until the appropriate action is taken to repair the file system.
  19. No - the idea is to identify that you have a problem that you can investigate further. If the problem is a data drive then you do NOT want it to cause invalid corrections to be made to parity which could then prejudice recovery of that drive’s contents if is later replaced. I would only recommend having the option to correct parity set for a check which is initiated manually after you have decided that is the most appropriate action. Still not clear how data loss can result from building parity as that is only reading from the data drives.
  20. Having a folder with the name of the share (even if it is empty) will make UnRaid display like that. If you are sure the folder on the cache drive is empty then deleting it will correct that. I guess the real question is what you did that resulted in you having that folder on the cache in the first place?
  21. I am confused as writing parity should never affect the content of the data drives Perhaps if you post your system’s diagnostics zip file we might be able to get a better idea of what happened and the current state of the system. BTW: it is recommended that scheduled parity checks are set to be non-correcting - your description makes it sound as this is not how you have yours set?
  22. You don’t need to do #1 if you are going to do #2 as in that case the ‘mover’ application does the transfer of the file to the array.
  23. Since the UPC seems to be stirring up a lot of adverse reaction, maybe the easiest option is to set up a setting under either Settings->Identification or Settings->Management Access (whichever is deemed most appropriate) to remove the Login prompt from the top of the GUI? It can then be defaulted to Enabled until explicitly disabled by the user so new users see it is an option. That might also help with making it clearer that this is purely an optional feature
  24. Set the I thought the recovery action was implicit in the description but obviously I was wrong I have edited the entry and added the recovery action at the start of the bullet point workarounds.
  25. This link in the online documentation accessible via the ‘Manual’ link at the bottom of the GUI both explains what has happened and what you can do about it.