Jump to content

itimpi

Moderators
  • Posts

    20,126
  • Joined

  • Last visited

  • Days Won

    55

Everything posted by itimpi

  1. That looks as if no major corruption was found. You need to run without the -n option if you want anything to be fixed, and if it asks for it add the -L option. Restarting in normal mode should mean the drive then mounts OK. Look to see if you now have a lost+found folder - if not all data should be intact.
  2. The time is determined by the size of the largest parity drive. Typically around 2-3 hours per TB as long as your disk controllers are not throughput limited. With modern large drives you are likely to find the Parity Check Tuning plugin will help with minimising the impact on daily use of very long parity checks.
  3. This message has always occurred in all Unraid versions if the USB cannot be found at step 4 of the boot process (described here) but what is not clear is what has suddenly stopped the flash drive being found for some people. As far as I know this was not an issue for the many rc releases that preceded the ‘stable’ one. Not clear if this is a specific hardware combination causing this that nobody running an rc release happened to have, or if there is some last minute change since the last rc triggering it.
  4. This could be a problem - Unraid v6 requires a 64-bit capable system.
  5. No, Parity will be reflecting the current contents of the drive (including the lost+found folder). Parity has no knowledge of files - only disk sectors so in that sense it is not content aware. Parity is about protecting you against disk failure - it does not protect you from corruption at the file system level when the dixk has not failed. That is one reason that having parity protection is not a substitute for having backups outside the array.
  6. Unfortunately not. Files get put into the lost+found folder when the repair process was not able to find their directory entry to figure out their name (in which case they are given a random numeric name) or where they belong in the file system. It is often easier to restore from a backup (if you have one) rather than putting in the effort required to sort out the lost+found folder.
  7. Make sure that you make a backup of the flash drive with your current working setup in case you later get some unexpected behaviour.
  8. You can always use the procedure described here to handle the upgrade if you are not able to do it via the GUI.
  9. You could try this process to see if it helps
  10. The diagnostics can help us see both what activity is happening, and also how you have things configured that might cause activity. They are not just about errors
  11. It does not normally take very long (typically seconds to minutes) unless there is very severe corruption. The main determining factor is normally the number of files on the disk rather that the size of the disk. Why are you asking?
  12. Have you tried clearing cookies/cache in your browser (or using incognito mode).
  13. You are likely to get better informed feedback if you post your system’s diagnostics zip file.
  14. You might want to try the process documented here in the online documentations accessible via the ‘Manual’ link at the bottom of the GUI to see if that helps.
  15. Those are all different views of the same file so it looks if you only have 1 copy and it is physically on disk1.
  16. If this is working you can use the ‘diagnostics’ command to get a zip file generated in the ‘logs’ folder on the flash drive which you can then post to help us see what is going on.
  17. An upgrade is one time quite a bit of data is written to the flash drive so I guess it is the most likely time to trigger a flash drive failure. I have also noticed that after an upgrade there seems to be a higher than normal instance of getting read errors from the flash drive. Often simply rewriting the flash drive on a PC/Mac can fix such an issue if the flash drive has not really failed. I THINK a Mac has an option to check the flash - but quite where it is in Finder I am not sure.
  18. The procedure is covered here in the online documentations accessible via the ‘Manual’ link at the bottom of the GUI.
  19. You also have to consider what is the maximum clock speed the motherboard+CPU combination is rated to support which is frequently lower than what your RAM is capable off.
  20. The extended SMART test appears to have failed so the disk definitely needs replacing.
  21. I have not seen one that explicitly gives any changes since rc8 You could possibly compare the rc8 log to the latest stable one to look for changes.
  22. You should post your system's diagnostics zip file to get informed feedback.
  23. Regarding memtest - what did you mean by ‘it does nothing’. If you UEFI boot you need to use the version you can download from memtest86.org. if a fresh install boots then I would start by copying the .key file and the super.dat file across from the backup. This should at the very least enable you to get the system up and running while you look further at restoring settings. I think you could also safely copy the ‘shares’ and ‘pool’ folders from the config folder in the backup to keep your share and pool settings.
  24. I did not spot an obvious cause in the diagnostics. Things to try to narrow down the issue. See if it will boot in Safe Mode. If so you have a plugin causing an issue. Run memtest from the flash drive in case a RAM stick is going bad. Reformat the flash drive and see it will boot if you restore nothing from your backup. If so that could mean there is a problem in a config file from the backup.
  25. You are likely to get better informed feedback if you post your system’s diagnostics zip file. sounds as if there is file system corruption somewhere that is stopping mover from working. The diagnostics would allow us to see if this is the case.
×
×
  • Create New...