Jump to content

JorgeB

Moderators
  • Posts

    67,600
  • Joined

  • Last visited

  • Days Won

    707

Everything posted by JorgeB

  1. It's normal for speed to decrease during a sync/check since disks are much faster in the outer tracks, but you're using a SATA port multiplier for 3 disks, this is bad for performance (and reliability), see here for a list of recommended controllers.
  2. Cache filesystem is corrupt, see here for some recovery options. Shares are not working because shfs segfaulted, rebooting should fix it.
  3. Diags are after rebooting so we can't see what happened, wait for the extended test to finish and if it passes and the emulated disk is mounting correctly rebuild on top.
  4. If you need to work with very small files and if possible for your use case you should use disk shares instead, user shares perform much worse with small files.
  5. Macvlan call traces are usually the result of having dockers with a custom IP address, more info below. You might also wait for 6.9.2, it might include a fix for this. https://forums.unraid.net/topic/70529-650-call-traces-when-assigning-ip-address-to-docker-containers/
  6. This suggests a hardware issue, like bad PSU, overheating CPU, etc.
  7. FAQ is still correct, but pool replacement is broken in v6.9.x:
  8. If there's still nothing logged it's not easy to diagnose remotely, you basically need to try and simply things as much as possible to try and find the culprit, e.g., do a new array with just one data disk for example and see if it starts (note that doing this will invalid pariyy, so it will need to be re-synced later).
  9. If it is the first time with the LSI it's likely not controller related, still important to try and find the cause, any unclean shutdowns?
  10. Also note that reiserfs is not recommended for v6, you should convert to XFS.
  11. Next step is starting the array in normal mode, filesystem should be fixed now.
  12. Assuming you have single parity you first need to complete the parity swap procedure, then upgrade disk3, parity swap procedure needs to be done from start to finish, any change you'll need to start over.
  13. Run a scrub on disk4, when it's done look at the syslog (tools - syslog) for the list of corrupt files.
  14. GUI SMART tests don't work with SAS devices, but you should see the attributes, tests for SAS devices need to be done manually.
  15. Plug is molex but it also comes with a molex to SATA adapter.
  16. If you can't find one on its own these kind of USB adapters come with one:
  17. You'd need to pass the SATA cable to the outside and use a 12V power supply for the disk, but it could work.
  18. You're better off using different hardware, NUC is not really a good base for a server, doesn't mean you can't use it, but expect issues.
  19. Good point, it won't, I assumed the disks were up.
  20. Should already be available, no idea what the problem is if it's working for the diags.
×
×
  • Create New...