itimpi

Moderators
  • Posts

    19353
  • Joined

  • Last visited

  • Days Won

    53

Everything posted by itimpi

  1. I assume that we will need to wait for a new Unraid release before this problem can be fixed. I have seen suggestions that 6.12.7 might be imminent. That would be expected if you have uninstalled the plugin as you mentioned earlier? That folder should always be there if the plugin is installed.
  2. If you have the Dynamix File Manager plugin installed then you can navigate to the plugins folder on the flash drive /boot/config/plugins/parity.check.tuning/ to get a file listing.
  3. Which disk is disabled/failed? Your diagnostics suggest it is parity2. If that is the case then you can stop array assign new 8TB drive to parity2 start array to rebuild parity2 The parity swap procedure is needed when it is data drive that has failed and you want to upgrade parity and re-use the old parity drive to replace the data drive as a single operation. In fact if the failing drive IS parity2 then you could replace parity1 with a 8TB drive at the same time as replacing parity2 and rebuild both parity drives simultaneously (keeping the old parity1 intact just in case something goes wrong with a data drive while rebuilding the parity drives).
  4. Not sure I understand the question - you just plug in two dummy flash drives and configure one of them as parity (making sure it is the larger one if they are not the same size).
  5. If you want to stop using a parity drive you can simply stop array; unassigned parity drive; restart array to commit change
  6. Did you run without -n (the no modify flag) ?
  7. It does - at the point the file is first opened and has 0 size. If the free space is below Minimum Free Space at that point another drive is chosen. Once the drive is chosen Unraid does not change its mind if the file subsequently does not fit - it gives an out of space error. That is why you want have to have a value for minimum free space that is larger than the biggest new file that might be written to the disk.
  8. If you btrfs that has built-in check summing for detecting bitrot.
  9. More often than not when a drive is disabled (because a write failed) it was due to an external factor and the drive is physically OK.
  10. If the CPU fan is OK perhaps the thermal paste needs renewing?
  11. Good - that helps when looking at diagnostics to look at issues regarding share settings.
  12. Did the old disk1 actually physically fail or simply get disabled and/or marked as unmountable?
  13. Sounds like you will need to Contact Support to sort out getting your licence transferred to a new flash drive.
  14. It seems that it would be a good idea to introduce buttons on the Main tab against individual drive for File System check and Format? The file system check button would probably just bring up same page you get when clicking on the drive name. Ideally the File System Check button would be omitted for a new disk that is all zeroes just added as in that case it does not make sense. i feel this would be helpful to users in giving guidance on what options make sense and reduce the chance of errors. Anyone see any downsides?
  15. Is the system actually shutting down rather than crashing and becoming unresponsive? If so this is almost certainly a hardware error with the most likely candidates being thermal (e.g. CPU overheating) or PSU struggling to provide sufficient power.
  16. Just a thought - if you install the Parity Check Tuning plugin then even if you do not use any of its features then new Parity History entries gets enhanced to say whether a check was correcting or not. This might help with troubleshooting?
  17. It is also worth noting that if you click on the orange icon for a drive on the Dashboard tab and select the Acknowledge option from the menu displayed Unraid will then only notify you again if the attribute changes. i suspect the reason you ‘think’ this is only an Unraid issue is that the other systems are not reporting CRC errors.
  18. Are you scheduled checks correcting or non-correcting? If correcting then you would expect no errors the next time you run a check. We do, however, recommend that scheduled checks are set non-correcting so that hardware playing up does not corrupt parity. That gives you a chance to correct any hardware issues while parity remains valid.
  19. The only reasons I can think of are: The system is having problems reading at least one of the drives do resets are slowing things down. the Disk controller is limiting throughput when all drives are active.
  20. Not sure why you want this as 0000 new drives it a lot less stress on the system. If you do it via the UD plugin then when you get around to adding it to the array it adds immediately so downtime is minimal. you might want to 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. The Unraid OS->Manual section in particular covers most features of the current Unraid release.. The process for handling drive failures is described here in the documentation. This handles both replacing failed drives and upgrading to larger drives. The only times New Config should come into play are: Completely resetting the array back to defaults Reducing the number of drives in the array. recovering from certain types of error scenario. This would normally be done after getting advice in the forum.
  21. There appear to be macvlan related crashes. As mentioned in the releases notes if you want to continue using macvlan for docker networking then you should disable bridging on eth0. The alternative is to switch docker to using ipvlan networking instead.
  22. The drive had dropped offline when the diagnostics were taken do there is no SMART report for it included.
  23. Quick SMART test does not test most of the disk - you need the extended version for that. Not sure why it is disconnecting though as the test runs internally to the drive and does not involve the host.
  24. I am sure that if only a way could be found that reliably reproduces it then it would quickly be fixed.