Jump to content

JorgeB

Moderators
  • Posts

    67,572
  • Joined

  • Last visited

  • Days Won

    707

Everything posted by JorgeB

  1. It shouldn't, does anything change by itself in the LAN settings page after a reboot?
  2. Try deleting /config/vfio-pci.cg on the flashdrive.
  3. Still having flash drive issues, it's disconnecting and reconnecting with a different identifier, and when that happens Unraid can't find it.
  4. Disk looks OK, replace/swap cables to rule them out and rebuild on top (if the emulated disk is still mounting correctly).
  5. Another small issue, after approving a new user's first post and getting back to unread/all activity feed it still appears as unread, need to click on it again to be marked as read, this didn't happen before, it was marked as read after approving.
  6. If you're up and running you can just reconfigure the LAN as needed, gigabit NIC should be eth0, and 10GbE configured using a different subnet and with just the IP address.
  7. Test should take around 2 hours on that drive, try aborting with: smartctl -X /dev/sdf Then start another smartctl -t long /dev/sdf
  8. One thing would should do is to update the 16 port LSI firmware, might not be the problem but all p20 releases except the latest one (20.00.07.00) have known issues, if that doesn't help swap cables/slot with another disk. You can do the update using Unraid.
  9. Sorry, outside my wheelhouse, someone else might help, if notask in the thread linked above.
  10. Several ways of doing, important part is doing it regularly.
  11. Diags are with the array stopped, what filesystem are you suing for the array?
  12. Several issues, but first please reboot and post the complete diagnostics after array start.
  13. No, but look for a BIOS update and/or try a different release(with a different kernel).
  14. Diags after rebooting are not much help, you can try this.
  15. Jan 15 11:55:48 Tower root: umount: /mnt/cache: target is busy. Something still using cache, as for the unmountable disk no valid filesystem is being detected, you're sure it was formatted?
  16. Both "old" disks look fine, disk3 is practically new, you can just do a new config with both and the rest of the array and re-sync parity, obviously will lose any data on those disks written after they were replaced.
  17. Plex was as at the time the diags were grabbed, not sure what uses Java.
  18. Not really, but it looks LAN related, so try to simplify the network config as much as possible.
  19. I never used Plex, best to ask in the existing docker support thread.
  20. It's Plex: PID USER PR NI VIRT RES SHR S %CPU %MEM TIME+ COMMAND 10835 nobody 20 0 2776188 447956 15896 R 864.7 1.4 7:22.32 Plex Tran+
  21. IIRC that was caused by the GPU statistics plugin, or a related one.
  22. Yes, the one I mentioned above, or doing a new config with the old disks if they really are OK.
×
×
  • Create New...