Jump to content

JorgeB

Moderators
  • Posts

    67,616
  • Joined

  • Last visited

  • Days Won

    707

Everything posted by JorgeB

  1. Are those symlinks? IIRC there could be issues with those.
  2. What drive is that? Disk22 is SMR so degraded write performance is expected.
  3. It's difficult to say, if you have any spares of that, like a different PSU start with what you can test and rule out, you can also try with just two DIMMs at one time, to completely rule out the RAM.
  4. I'm really not a network guy, but always read you need different subnets for that, you can also add the server name with the 10GbE IP to the hosts file on the client computer, so you can access it by name still using 10GbE, that's what I do.
  5. If the disk was empty might as well reformat, but you can try to mount it with UD plugin and if it doesn't post the diags (key needs to be the same as other encrypted disks in the server).
  6. Does is still reboot frequently with the RAM running @ 2133 MT/s? If yes one thing you can try it to boot the server in safe mode with all docker/VMs disable, let it run as a basic NAS for a while, if it still crashes it's likely a hardware problem, if it doesn't start turning on the other services one by one.
  7. No valid filesystem is being detected, so there's serious damage to the superblock which may make recovery difficult, all your other disks are empty, was that the only disk with data?
  8. By default Unraid uses 20% free RAM for write cache, for all transfers, you can change that in the console or with this plugin:
  9. You need to put the 10GbE NIC on a different subnet (without gateway), then use that IP for 10GbE.
  10. Assign it to that slot and start the array.
  11. If it's the same disk use a different slot or swap with another disk and see where the problem follows.
  12. It shouldn't, are you using a different IP subnet for the 10GbE link?
  13. Looks more like an LSI driver issue, especially if doesn't happens with all the disk models, a future kernel may include a fix for that.
  14. There are various Nvidia and CPU related issues, looks more like a hardware problem, or current kernel doesn't Ike your hardware.
  15. No, but you could move all the data from the emulated disk to other disk(s) then remove it from the array.
  16. If the CPU supports the AES-NI instruction set you shouldn't notice any significant performance hit, and IIRC your CPU does.
  17. Please post the diagnostics: Tools -> Diagnostics
  18. Enable this and post that log after a crash, together with the complete diagnostics.
  19. If it's an option try that controller in a different server/board just to see if it initializes correctly.
  20. Lots of UDMA CRC errors on the disable disk, you should replace the SATA cable before rebuilding.
  21. Changed Status to Closed Changed Priority to Other
  22. RAM is running at 3600MT/s, max supported speed for you CPU with 4 dual rank DIMMs is 2667 MT/s, in any case this is general support issue, so please continue discussion here:
  23. reiserfsck --rebuild-sb /dev/sde1 Follow the instructions carefully, once it's done: reiserfsck --rebuild-tree /dev/sde1 This last one will take several hours.
×
×
  • Create New...