Narvath

Members
  • Posts

    8
  • Joined

  • Last visited

Recent Profile Visitors

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

Narvath's Achievements

Noob

Noob (1/14)

1

Reputation

  1. My solution was to set the minimal RAM to about 5G and to change the iso installation but from sata to usb
  2. Done, it looks like basically every docker containers are dead or got their settings reset as I could not get their appdata folder backed up. Not the end of the world, simply annoying to set up everything back up. Thanks for the help, it's been very appreciated! Now I'll go set up the appdata backup plugin and look into a raid 1 cache pool to prevent that kind of loss from happening again. Thanks again
  3. Backup what is in the cache or everything on the array too?
  4. Ok, so it took quite a while to recieve the new RAM replacement but it's here now. Here is the new diagnostic with the new RAM (which passed MemTest). As of now, it seems like the network is unreachable (among some other things). And I'm clueless on what should be done next... tower-diagnostics-20230426-1123.zip
  5. Ok well, I was going to ask in what setting I should run it but in mere sefonds and I have 110+ errors... I'll try to test it in another slot juust in case but assuming thats really the ram, replace it and then what should I do for unraid to get out of read only? (and track which file was corrupted so that I can delete/replace it)
  6. Greetings, I noticed that my containers were not working anymore and hopped on the logs and sure enough, to my understanding, there seems to be something corrupted on the cache(?) due to and IO failure: Searched a bit and saw that for many people the issue wasn't really related to an actual IO failure and so, I'd like to know if I really sould look into the physical side of things or not. As always, the diagnostic zip is in the atttached files. Also, there isn't any important information on the server which is why there is no parity for the array and cache. Altough I might seriously consiter it if that could prevent such problems from happening again... tower-diagnostics-20230407-0959.zip
  7. Have you found the issue? I'm having the same thing...
  8. Finaly, just writing it87 worked since my auto detect didn't work either... But i end up with 6 temp readings that starts with it8792 and ends with either temp1, temp2 or temp3 (2 of each) and they all have different readings !_! is that a problem since i din't use auto detect? or is there simply 6 temp readings from different places of the mobo?