Jump to content

JorgeB

Moderators
  • Posts

    67,831
  • Joined

  • Last visited

  • Days Won

    708

Everything posted by JorgeB

  1. The GUI won't show device errors for pool members, see here for more info and better pool monitoring.
  2. Syslog posted it's not from the syslog server, it's the same from the diags, that one will only cover the last boot.
  3. Enable the syslog server and post that after a crash.
  4. Aug 5 23:01:33 NAS kernel: macvlan_broadcast+0x116/0x144 [macvlan] Aug 5 23:01:33 NAS kernel: macvlan_process_broadcast+0xc7/0x110 [macvlan] Macvlan call traces are usually the result of having dockers with a custom IP address and will end up crashing the server, switching to ipvlan should fix it (Settings -> Docker Settings -> Docker custom network type -> ipvlan (advanced view must be enable, top right)).
  5. As long as parity is valid and the server has no know issues, like bad RAM or frequent sync errors after a parity check, no reason to expect any issues with the rebuilt disk.
  6. Aug 6 22:50:16 Blastoise kernel: macvlan_broadcast+0x116/0x144 [macvlan] Aug 6 22:50:16 Blastoise kernel: macvlan_process_broadcast+0xc7/0x110 [macvlan] Macvlan call traces are usually the result of having dockers with a custom IP address and will end up crashing the server, switching to ipvlan should fix it (Settings -> Docker Settings -> Docker custom network type -> ipvlan (advanced view must be enable, top right)), or see below for more info.
  7. No need to have them, just loading the i915 driver can cause the problem, just blacklist the driver to prevent it from loading, you don't need to use a different GPU.
  8. Yes, this is usually a flash driver problem, you can first try to re-format the original flash drive (after making a backup), if that doesn't work try a different one.
  9. If the Synology share is mounted with UD you use the mount path, confirm is spelled correctly, post the output of df -h
  10. I still cannot see why cache is not being used, possibly some old setting that is conflicting or is not taking, I would suggest backing up flash drive, creating a new one, then restore only the things you need, like the key, disk assignments (super.dat), network config, etc, avoid restoring anything that relates to shares, then reconfigure them.
  11. Lots of data corruption detected by btrfs, also filesystem corruption on disk1, check filesystem on disk1, cache will need to be reformatted, copy everything you can manually, some recovery options here: https://forums.unraid.net/topic/46802-faq-for-unraid-v6/?do=findComment&comment=543490 P.S. did you ever run previous v6.10 releases other than v6.10.3?
  12. Looks more like a power problem, it's affecting multiple disks in different controllers, could also be SATA cables.
  13. Unassign all pool members, start array, stop array, re-assign all pool members, start array and you're done.
  14. Did you try a different browser? Like mentioned array appeared to have started correctly.
  15. Server appears to have started correctly, try closing and re-opening the browser, if the same reboot in safe mode.
  16. Don't see how that's possible, lets start with the basics, type this in the console: touch /mnt/user/Storage/cache_test Them post the output of: find /mnt -name cache_test
  17. I would first try recreating the flash drive, backup current one, recreate it using the USB tool or manually, restore the config folder, try again.
  18. Looks like a flash drive problem, Unraid cannot create the pool config folder/files: Aug 6 08:14:10 IronMike emhttpd: scandir: /boot/config/pools Not a directory
  19. Other than that not seeing anything relevant logged, could be this issue:
  20. Run a read test using the diskspeed docker to see if all disks are performing normally.
  21. There's no sdi in the diags posted, I assume you know parity is disabled?
×
×
  • Create New...