Jump to content

JorgeB

Moderators
  • Posts

    67,416
  • Joined

  • Last visited

  • Days Won

    705

Everything posted by JorgeB

  1. Did you format the disks? You can also post the diagnostics: Tools -> Diagnostics
  2. Syslog only shows the last check, ideally we wanted to also see the previous ones, but for now you should cancel it and run an extended SMART test on disk8.
  3. Shouldn't make any different, but it won't hurt, and it should be on latest firmware anyway: 20.00.07.00
  4. Unrelated to previous issues, cache pool is completely full, note that the GUI can show wrong values when using different size devices.
  5. Please post the diagnostics: Tools -> Diagnostics
  6. There are checksum errors on the pool, and possibly because of that it's failing to remove the missing device, you can reboot to try again, if it still doesn't work best bet is to backup, re-format and restore the data.
  7. Disk4 is failing and needs to be replaced, and parity isn't 100% valid since there were read errors on disk4 during the sync.
  8. It does look like the cache pool was full, not so clear because of the missing device.
  9. This is usually controller related, i.e., some controllers do this, some don't.
  10. Disks will need to be formatted (any data there will be deleted), stop array, click each disk and set filesystem to "xfs - encrypted", you can also set default filesystem to the same for any future disks (Settings -> Disk Settings), then choose encryption passphrase to start the array and format the disks (parity will remain valid).
  11. Yes, if there's filesystem corruption it will also be on the emulated disk.
  12. Don't know what the error is about but it does confirm x4 link width: LnkSta: Speed 8GT/s (ok), Width x4 (downgraded) It's either a board issue or a bad HBA, do you have another board you can test with?
  13. Although there are no errors logged it's crashing while mounting disk10: Apr 7 18:46:13 Tower kernel: REISERFS (device md10): checking transaction log (md10) Apr 7 18:48:51 Tower kernel: microcode: microcode updated early to revision 0x2f, date = 2019-02-17 Check filesystem on disk10: https://wiki.unraid.net/Check_Disk_Filesystems#Checking_and_fixing_drives_in_the_webGui P.S. Reiserfs is not recommended for a long time.
  14. LSI BIOS doesn't usually show PCIe link width, at least don't remember seeing that, check with lspci to confirm. lspci -vv > /boot/lspci.txt Then upload the txt here.
  15. OK, then the diags don't help, try this: https://forums.unraid.net/topic/46802-faq-for-unraid-v6/?do=findComment&comment=781601
  16. Diags are before array start (or after a reboot).
  17. Everything looks normal, except it still balancing the pool to remove the missing disk, make sure it finishes. What does hosed mean? All can I can see in the logs is if the docker service is starting correctly, and it apparently it is.
  18. Unassign disk10, start the array, when it crashes see if you can download the diags on the console, by typing "diagnostics", then attach here.
  19. You should also disable NIC bonding, there are some reports it might sometimes cause issues on latest releases.
  20. Diags are after rebooting so we can't see what happened, but disk looks fine, suggest replacing/swapping cables to rule them out and rebuild.
  21. https://s3.amazonaws.com/dnld.lime-technology.com/next/unRAIDServer-6.9.0-beta1-x86_64.zip
  22. I see that now that you mentioned it, but it looks unrelated to cache, and a reboot will (should) fix it.
  23. The drivers are still there, and on v6.9 they load correctly without any errors, it just doesn't get an IP address, but if it works with v6.6 it suggests it's not just a NIC/connection problem, IMHO best bet would to get a different NIC, Intel preferred.
×
×
  • Create New...