Jump to content

JorgeB

Moderators
  • Posts

    67,681
  • Joined

  • Last visited

  • Days Won

    707

Everything posted by JorgeB

  1. Usually not, try the controller in a different PCIe slot if available, if that doesn't help try a different controller.
  2. It can detect corruption if you btrfs, but it can't correct it since each data device is an individual filesystem without redundancy.
  3. That's strange, since Unraid is not finding a valid filesystem, something weird happened there, but in that case best to back them up using Windows and reformat.
  4. It does if you assign them to a pool, if you were talking about array devices no.
  5. Unraid has no problems with multiple LSI controllers, usually a board issue.
  6. If this is to/from the array it's normal due to parity, pool(s) should be much faster.
  7. Try a different cable/switch/port, while it links at 100Mbits you'll be limited to that.
  8. Do you mean they are using ntfs, or did you use a reiser or xfs reader for Windows?
  9. That's not normal, it should be around 6H as mentioned in the SMART report: Extended self-test routine recommended polling time: ( 389) minutes. Disk might have slow sector zones, that together with the other issues makes me think you should consider replacing it now.
  10. It's not needed if you set power supply idle control correctly.
  11. New config keeps all the data, just make sure to assign all devices as before, note also that depending on the raid controller used there's a small chance that the data devices are unmountable due to invalid partition layout, but data still won't be deleted, just don't format anything.
  12. You can create a pool with all the devices, then select a raid level appropriate for the performance/redundancy you prefer.
  13. Do a new config, assign them all in the previous slots and check parity is already valid before array start.
  14. Start here: https://forums.unraid.net/topic/46802-faq-for-unraid-v6/?do=findComment&comment=819173
  15. That doesn't matter. An it's not just filesystem corruption, no filesystem is being detected on those disks, which is very strange. Don't know what you mean, you are seeing the data from the disks that mount only, if that's everything you should have good.
  16. You should backup and reformat that device, there are some recovery options here if needed
  17. Cache device dropped offline: Jul 27 16:43:40 TardisDataCore kernel: sd 2:0:0:0: Device offlined - not ready after error recovery Check/replace cables and post new diags after array start.
  18. See if this applies to you: https://forums.unraid.net/topic/70529-650-call-traces-when-assigning-ip-address-to-docker-containers/ See also here: https://forums.unraid.net/bug-reports/stable-releases/690691-kernel-panic-due-to-netfilter-nf_nat_setup_info-docker-static-ip-macvlan-r1356/
  19. There will be the test result in the report.
  20. Docker image is corrupt, delete and re-create, VM service is disable in the diags posted, enable and post new diags if there are still problems.
  21. You need at least one data device assigned in the array.
  22. Please post the diagnostics: Tools -> Diagnostics
  23. Other then using a different board that's your best bet.
×
×
  • Create New...