yuelpl

Members
  • Posts

    31
  • Joined

  • Last visited

Everything posted by yuelpl

  1. The issue has been resolved. After repeatedly testing by replacing hardware, it was found that the problem was caused by poor heat dissipation of the P222 array card. Normal functionality has been restored after cleaning and other treatments.
  2. The diagnostic logs and syslog were downloaded after the issue reoccurred but before reboot the server. I have purchased new connection cables and a power supply, and I will try replacing them once they arrive on Sunday. If it still doesn't work, I will consider replacing the passthrough card for the array. However, I'm concerned that changing the P222 passthrough card to an LSI 9217 might result in data loss on the disks. Is that a possibility?
  3. I'm sorry, my English is not good, it's actually on the first page of this topic. After you asked me to 'get it, zip it, and post it‘.
  4. Hi, the error has occurred. I have uploaded new diagnostic logs and syslog in the reply, along with a description and images. Can you please help me analyze where the problem is? Thank you.
  5. But I don't know what other HBA cards besides P222 can be used with Gen8, and whether unraid has a recommended HBA card list?
  6. I have purchased a new cable and power supply, and I will replace them once it arrives
  7. Now I have paused the validation.Click the arrow in front of the disk to view its contents; it shows 'Invalid Path'. Strangely, it appears to be readable on the UI. After stopping the array, the disk shows as missing. Either the 9th or the 11th disk always have read error on one of them. In 5 verification attempts, they have never both experienced read errors at the same time. Once rebooted, the disk list appears to be normal, but I have to manually stop the verification to prevent the 9th and 11th disks from experiencing read errors again. Diagnostic logs and syslog have been uploaded above for your review. Thank you.
  8. It happen again😵 unraid-diagnostics-20240111-1544.zip syslog-10.0.0.10.zip
  9. OK, I will start a new verification and update this topic when the error occurs. Thank you
  10. Is that so? Then, should I reboot the server and wait for downloadable content to appear in the folder?
  11. Should I directly reboot next, or start a new verification and wait for the error to occur?
  12. Sorry, I have taken the screenshot again. I have set the logs to output to my cache disk. Please check if this setup is correct.
  13. if the settings are correct? If so, I will start the disk verification again and promptly download the diagnostic logs if there is an error.
  14. I have about 500GB of space left in my cache. Will doing this cause the cache to fill up and lead to Docker running abnormally?
  15. If that's not possible, do I only have the option to start the disk verification again and wait for the issue to occur, then download the diagnostic logs before rebooting?
  16. I setup local syslog server to "Enable",Is it possible to view the logs from the past few days after a reboot? If so, I will reboot the server now.
  17. Could it be that because I rebooted the server, the previous error diagnostics were lost?
  18. The cable is connected from the hard drive backplane through an 8087 to 8088 cable to the P222 on the Gen8.
  19. After the error, the read error count keeps accumulating, and many of my services become inaccessible. Therefore, I clicked 'Cancel' to stop the verification and restarted the array after rebooting, which restored normal operation of services like Docker. During a previous attempt, I also tried to directly stop the array, but the UI froze, and I ultimately had to resort to a hard power reset. The external disk cabinet has its own power supply, model: Sea Sonic 350W SS-350M1U, which is synchronized with the main server for power supply and power-off through a UPS.This power supply has been in use for less than 2 years.
  20. Disk array in the disk cabinet randomly drops disks during verification. However, the disk checks out fine, and the array starts normally after a reboot. Disks 9 and 11 are in an external disk cabinet. Even when I use a 'new configuration', these two disks randomly drop out during the synchronization process, their temperature cannot be measured, and read errors continue to accumulate. After the error occurs, I stop the array and then reboot. The faulty disks can automatically mount and the array starts, everything appears normal. The disks have been checked and no issues were found. I attempted to start the array and automatically sync three times. Each time, these two disks had issues, whereas the other disks not in the external disk cabinet did not encounter any problems. My server is a Gen8 ml310e v2, with a P222 serving as the HBA card connecting the internal hard drives and the external disk cabinet. I'm seeking advice on where the problem might be occurring. Thank you. unraid-diagnostics-20240111-1051.zip
  21. 昨晚在路由器上设置unraid经旁路由科学上网,docker可以更新,可以肯定是被墙了。