Jump to content

JorgeB

Moderators
  • Posts

    67,416
  • Joined

  • Last visited

  • Days Won

    705

Everything posted by JorgeB

  1. It's normal during a btrfs balance.
  2. Pool mounted correctly and it's deleting the missing device, since currently it's a redundant pool with a single device missing all data should be there, and I'm not seeing any fs errors/issues.
  3. I meant stop all dockers before starting the array, then reboot, if it reboots normally then enable dockers one by one.
  4. Just add it, it will be cleared and then you can format it.
  5. Syslog on the diags is blank, reboot and try again.
  6. Best bet is to post on the UD support thread, and don't forget to attach the diagnostics.
  7. It's logged like a disk problem, but it dropped offline so there's no SMART, power cycle the server and post new diags (if you can't power cycle try a reboot but it might no be enough to bring the disk online).
  8. Please post the diagnostics: Tools -> Diagnostics
  9. Memtest won't detect ECC errors, since they are corrected, check the board's SEL (system even log), it might have more info on which is the problem DIMM.
  10. It's fine, but always run a non correcting check (unless sync errors are expected). Default profile is RAID1, so usable space will be the same, but it can be changed.
  11. You can just erase the BIOS, it's not needed for Unraid: https://forums.unraid.net/topic/12114-lsi-controller-fw-updates-irit-modes/?do=findComment&comment=632252
  12. Seems to be going normally, write speed to the array is close to 40MB/s, which is about right for default writing mode, and at those speeds it should move more than 100GB per hour, are most files similar sized media files or do you some time move smaller files? Smaller files can take much longer to copy/move. Also and just in case you're not familiar with it, if you enable turbo write mover should go much faster, at around 300/400GB per hour, at the expense of all drives spinning up.
  13. Like mentioned it has to exist, and it's present on the v6.9 diags posted
  14. There's nothing being written to the array or being read from cache, there's only small read activity on disk7.
  15. Don't see a reason for not working with v6.9, try deleting/renaming network.cfg (flash/config) then reboot.
  16. Start here: https://forums.unraid.net/topic/46802-faq-for-unraid-v6/?do=findComment&comment=819173
  17. -Tools -> New Config -> Retain current configuration: All -> Apply Then unassign the disk you want to remove (you can move the other data disks up a slot if you want), unassign old parity, assign new parity (or just assign new one if old one is already disconnected) and start array to begin parity sync.
  18. Likely a NIC driver issue, you could try v6.9-beta1 which includes a newer kernel, or use another NIC if available.
  19. Try this: https://forums.unraid.net/topic/46802-faq-for-unraid-v6/?do=findComment&comment=781601
  20. Disks look fine, and the errors happened on all five disks at the same time, which virtually rules out a disk problem, check all connections especially anything shared by those disks, like power cable, backplane region, etc, could also be a PSU issue, unlikely to be controller related since they are using two different controllers.
×
×
  • Create New...