Jump to content

JorgeB

Moderators
  • Posts

    67,675
  • Joined

  • Last visited

  • Days Won

    707

Everything posted by JorgeB

  1. It does if you assign them to a pool, if you were talking about array devices no.
  2. Unraid has no problems with multiple LSI controllers, usually a board issue.
  3. If this is to/from the array it's normal due to parity, pool(s) should be much faster.
  4. Try a different cable/switch/port, while it links at 100Mbits you'll be limited to that.
  5. Do you mean they are using ntfs, or did you use a reiser or xfs reader for Windows?
  6. 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.
  7. It's not needed if you set power supply idle control correctly.
  8. 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.
  9. You can create a pool with all the devices, then select a raid level appropriate for the performance/redundancy you prefer.
  10. Do a new config, assign them all in the previous slots and check parity is already valid before array start.
  11. Start here: https://forums.unraid.net/topic/46802-faq-for-unraid-v6/?do=findComment&comment=819173
  12. 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.
  13. You should backup and reformat that device, there are some recovery options here if needed
  14. 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.
  15. 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/
  16. There will be the test result in the report.
  17. 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.
  18. You need at least one data device assigned in the array.
  19. Please post the diagnostics: Tools -> Diagnostics
  20. Other then using a different board that's your best bet.
  21. Disk is showing a pending sector and recent UNC @ LBA errors, run an extended SMART test.
  22. Jul 27 14:25:42 Area51 kernel: ixgbe 0000:04:00.1: failed to load because an unsupported SFP+ or QSFP module type was detected. Jul 27 14:25:42 Area51 kernel: ixgbe 0000:04:00.1: Reload the driver after installing a supported module.
  23. Disks 6 and 11 should be fixable if you run xfs_repair again without -n, the other two don't look so good, for disk5 you can check if the actual disk mounts.
  24. Didn't read everything , but the rebuilt disk2 will be mostly corrupt. if you still have the old one don't wipe it, is disk1 the old disk or was also replaced?
×
×
  • Create New...