gamer1pc

Members
  • Posts

    20
  • Joined

  • Last visited

Converted

  • Gender
    Undisclosed

Recent Profile Visitors

The recent visitors block is disabled and is not being shown to other users.

gamer1pc's Achievements

Noob

Noob (1/14)

1

Reputation

  1. Thank you so much for your reply, I really appreciate it. I will take a look at this plugin and limit the RAM on my VM
  2. This is the error: "Your server has run out of memory, and processes (potentially required) are being killed off. You should post your diagnostics and ask for assistance on the Unraid forums" I have included my diagnostics as well. If anyone could please let me know if my server is fine, it seems to be fine on RAM as well with only ~37% usage. xio-diagnostics-20230630-1101.zip
  3. I ran a scrub and came out with no errors found, should I checkmark "repair corrupted blocks"?
  4. I've also added these parameters to my flash configuration: nvme_core.default_ps_max_latency_us=0 pcie_aspm=off After reading around the forums and for some it fixed it but it hasn't for mine. I've attached and image of the errors and diagnostics as well. Any help is appreciated as I seem to not be able to find a solution around. xio-diagnostics-20220930-0628.zip
  5. @brimnac Thanks for the reply I'll give it a try
  6. Anyone know how I can add this to the config/command line c=LTC,mc=FIRO. I need it in order for the pool to convert my FIRO to LTC. Thanks in advanced for the help
  7. I was able to restore everything back to normal on wednesday and everything was fine on Thursday, but this Friday afternoon. Parity got disabled and other disks were put to grey status as the picture shows. I couldn't stop the array since it was stuck so I had to do a hard shutdown. Could it be just a coincidence and had bad luck or does the diagnostics show the same thing again? xio-diagnostics-20210205-1458.zip
  8. Well thinking I was fine, I had to stop the array and the other cache became corrupted as well as I started it up again. I have a question regarding the recovery options you linked. Do these have to be performed while the array is started in normal mode, maintenance mode or not have the array started? Thanks in advanced
  9. Yeah the second Cache 2 disk was a mirror of Cache disk so I just swap them. Thank you once again for explaining what happened
  10. Hi, I upgraded the OS to 6.9rc2 after the data rebuild. Then rebooted and started the array, and now the Cache disks are showing as "Unmountable: No file system", I have attached the diagnostics and a picture. Should I reboot again and see if they get mounted this time? xio-diagnostics-20210203-0716.zip
  11. I'm going to update to 6.9 to see if it resolves these problems then. Just need to wait for the parity data rebuild to finish. Thanks for the advice
  12. My parity disk became disabled and I started a parity check, but stopped it as I realized there's no point to it. I have a feeling it might be the sata cables or the sata controller on the motherboard as it happened to disk1 a day before and unraid hangs on "stopping array" for hours when I wanted to shutdown to inspect disk1. Which forced me to force shutdown the server. I have posted the diagnostics file before restarting. I really appreciate anyone who helps me figure this out. xio-diagnostics-20210201-1238.zip
  13. (SOLVED) I was able to test out the USB in the slots on the back instead of infront of the case and it worked. So my guess is that the driver wasn't loading for the USB controller on the front panel.
  14. It's a USB 3.0 stick and I've tried booting from either the USB 2.0 port and USB 3.0 port. I also made sure it's booting into legacy mode so it won't go into UEFI. I tried the command and only showed tmpfs. So I believe it should at least show disk 1, but like you said earlier it doesn't seem to mount it. It's really strange behavior.
  15. I tried it again and same thing, and like how it mentioned earlier that the USB does work on my other computer, I was even able to make the zip file and it saved on the flash drive. Could a setting on the BIOS be breaking it?