Jump to content

JorgeB

Moderators
  • Posts

    67,572
  • Joined

  • Last visited

  • Days Won

    707

Everything posted by JorgeB

  1. Yes, no difference if it's a thread you already posted or not, there was before.
  2. 9300-8i is IT mode only, and a good option, though SSD needs to support deterministic read after trim or it won't be trimmed.
  3. Before the update there was a different new content icon for threads you posted before both on the forum and on streams, now it doesn't appear on streams: Still OK in the normal forum view Not in any stream:
  4. See here: https://wiki.unraid.net/Troubleshooting#Re-enable_the_drive
  5. Macvlan call traces are usually the result of having dockers with a custom IP address, more info below:
  6. You can mount them and check SMART with the UD plugin, array should be stopped because of duplicate UUIDs.
  7. Disk3 appears to really be failing, best bet to recover as much data as possible would be to clone disk3 with ddrescue (to a disk of the same size), then use that to rebuild disk5, but there will always be some data loss on both disks. Is old disk5 completely dead?
  8. Seagate drives report this differently, I mentioned it should be 0 only WD drives. Run an extended SMART test on disk5, but it's likely past its prime.
  9. These should be ideally 0 on an healthy WD drive: ID# ATTRIBUTE_NAME FLAGS VALUE WORST THRESH FAIL RAW_VALUE 1 Raw_Read_Error_Rate POSR-K 200 200 051 - 65 200 Multi_Zone_Error_Rate ---R-- 200 200 000 - 2 And there also also UNC @ LBA errors in the report, keep monitoring those attributes, if they keep increasing there will likely be more error soon. Yes. AFAIK It will. It's past it because disk5 is only 1TB, so at the 1TB mark it ends checking it.
  10. Disk5 appears to be failing, you should run an extended SMART test, sync errors are likely the result of this: Jan 14 10:03:01 Server emhttpd: unclean shutdown detected As for the speed it could be disk related, but not disk5 since it's already past it, though parity is also showing some issues, but there also appears to be something else accessing the array, so stop all that first.
  11. Please post the complete diagnostics zip: Tools -> Diagnostics
  12. Assuming you didn't already start the array with the single device do this: If Docker/VM services are using the cache pool disable them, unassign all cache devices, start array to make Unraid "forget" current cache config, stop array, reassign all cache devices (there can't be an "All existing data on this device will be OVERWRITTEN when array is Started" warning for any cache device), re-enable Docker/VMs if needed, start array.
  13. There is no error counter but it will report any errors after it's done, be it rebuild errors or sync errors (or both together).
  14. Please use the existing plugin support thread: https://forums.unraid.net/topic/92462-unassigned-devices-managing-disk-drives-and-remote-shares-outside-of-the-unraid-array/
  15. That's is what is already being done, hence why parity2 is being read.
  16. Looks more like a connection problem, also problems with disk2, replace cables and post new diags.
  17. Just my yearly reminder that this is still happening.
  18. Since the diags are after a reboot we can't see what happened, but the disk looks healthy, would recommended replacing/swapping cables to rule them out and then rebuild on top.
  19. Some info here: https://forums.unraid.net/topic/46802-faq-for-unraid-v6/?do=findComment&comment=462135
×
×
  • Create New...