Jump to content


  • Content Count

  • Joined

  • Last visited

  • Days Won


Everything posted by itimpi

  1. This will be a limitation of the USB external bay you are using. Many external bays DO present each drive with a unique ID to Unraid and so work fine. Having said that it is worth mentioning that is is not recommended that you have array drives connected via USB as USB connections tend to not be reliable enough for array drives. USB is typically used for removable drives that are only temporarily connected to an Unraid system (typically for back-up or data transfer purposes)
  2. The first step will be to post your system's diagnostics zip file (obtained via Tools -> Diagnostics) taken shortly after you have experienced the problem to see if we can spot something.
  3. You can but performance will be degraded if you do so until parity rebuild completes so you do not want to write any significant amount.
  4. The SMART information for that drive looks OK. At the moment UnRAID is emulating the drive - now that it is mounted do the contents look OK? The steps you outline will make UnRAID attempt to rebuild the contents of the emulated drive back onto the physical drive.
  5. From the SMART information I would say: Disk2 is probably fine. CRC errors are connection related and are typically related to the power/SATA cabling to the drive rather that the drive itself. Occasional errors are not really of concern but regular ones mean you should carefully check the cabling. The point to note is that the CRC errors count never gets reset, so if you click on the orange icon for the drive on the Dashboard and select the Acknowledge option Unraid will then only tell you about it again if it changes. disk3 looks as if it may be on the way out. It has lots of reallocated sectors and pending sectors. You could run the extended SMART test to confirm it is not well. the syslog in the diagnostics were taken just after a reboot so there is nothing to show what lead up to the current situation.
  6. According to that report only the ‘short’ SMART test has been run - but that failed anyway.
  7. With that many reallocated sectors I would expect them to accept a RMA regardless of the result of the Extended SMART test.
  8. Security enhancements in UnRAID means that files on the boot drive are not allowed to have execute permission. Script files therefore either needed to be preceded by the command name e.g. sh path-to-script-file or they need to be copied elsewhere and their execute bit set (typically using entries in the config/go file on the flash drive) before trying to use them. If they do not need to run as part of the boot sequence then the User Scripts plugin is another way to run them.
  9. This does not look too good: While reallocated sectors are not necessarily a problem as long as the numbers stays constant anything other that a small number is often a good indication that the drive's health may be suspect. You might want to run an extended SMART test on the drive to see how that goes.
  10. Are you sure you have the correct name for the mount point of the UD disk? (‘disk8’ is an unusual name). If you have got it wrong then that command will end up writing to RAM instead of the disk.
  11. I think you have mis-understood the purpose of `MacinaBox’. You only get the option to run the VNC viewer when you start your Mac VM. what the plugin does is generate the files that are required to run a Mac VM - it is not a VM in its own right.
  12. The drives have been disabled because a write to them failed, not necessarily because the drives have failed. Frequently the problem is not the drive itself having a problem but an external factor such as the SATA/Power cabling to the drive. Posting your system diagnostics zip file (obtained via Tools -> Diagnostics) might allow for some informed feedback on this.
  13. This is expected as the default for a cache pool is to set it up as the btrfs version of raid1 for redundancy . If you want to switch to a different profile then this can be done by clicking on the cache on the Main tab
  14. I am afraid not. I assume it is the partition type and the sector it starts on but that is just a guess.
  15. You can change the configuration dynamically with btrfs by clicking on the cache entry on the Main tab.
  16. The problem is likely to be that UnRAID expects a very specific partition layout and it sounds as if these drives partitions do not conform.
  17. The fastest way to copy on an initial setup is to not bother with the cache and without the parity drive assigned. You can then add the parity drive and set up how you want the cache drive to be used after this initial copy. Not having parity assigned means copies run significantly faster but your files are not yet protected so you have to decide if this suits you.
  18. The default,configuration for the cache is BTRFS version of raid1
  19. Nobody else seems to be having this problem so it sounds like it is something specific to your system. The issue is going to be to track down the cause. Providing any more information you can and a copy of your systems diagnostics zip file (obtained via Tools -> Diagnostics) might help with spotting something amiss.
  20. You do not need IOMMU to run Unraid in a VM The technique described here works fine without IOMMU being needed. It is what I use to run a VM for plugin development/testing.
  21. You have uncovered a bug in the code for pausing on drives over-heating and I will rectify this. When you have activated temperature related pause/resume then you will get a monitor task running every 5 minutes to check temperature - that is the "Monitor" log entry that is in your log. If temperature monitoring is not active then this task is not needed. so you get a lot less logged. The other resume/pause log entries are from the standard (not temperature related) pause/resume entries What is MEANT to happen is that the Monitor task will list the overheated drives (assuming debug logging is active) each time following the summary message and then pause the parity check that is running. It is this list + pause code that has the bug so that the pause is not taking place. I think the fact you have 19 "cool" phantom drives listed will be because you have 24 slots set on the Main tab (i.e. you have not reduced it to the number of drives you actually have). Can you confirm if this is the case? If so I need to add a check for slots allowed but not currently having a drive assigned to them to correct this count. If that is not the case then I need to do further investigation to determine why the drive count might be wrong in your case. I am in the middle of adding/testing multi-language support (ready for others to add translations to other languages) to the plugin so it will be at least a few days before I can release the fixes for the issues mentioned above. Hopefully this will not inconvenience you too much.
  22. Once a drive has been marked as ‘disabled’ with a red’s’ it always takes manual action to remove this status. You may find this section of the online documentation to be of help.
  23. What tests. Depending on what you actually did it may still be possible to get something off the drive.
  24. This could mess up docker containers that do not want those permissions. It is normally recommended to leave the permissions on appdata alone as far as possible, and if you do make changes limit them as much as is practical.
  25. itimpi

    Mover stuck

    Are you sure there are still files there? The 11.2GB sounds about right for the space used for the file system control structures.