molesza

Members
  • Posts

    178
  • Joined

  • Last visited

Converted

  • Gender
    Undisclosed

Recent Profile Visitors

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

molesza's Achievements

Apprentice

Apprentice (3/14)

0

Reputation

1

Community Answers

  1. Swapped out my SSD and all is working. Extended tests did not show any issues with that drive. I swapped the sata cable too, so that may have been it.
  2. I dont remember starting them. Before starting freshI had followed spaceinvaders guide to change my SSD drives to zfs. I changed all shares to move the files from cache to array drive. So maybe because those shares existed when I booted up for the first time docker and VM manager were automatically started? I have disabled them now.
  3. Got to 98% of the copy being done and now file transfer has stopped for about 20 minutes. Hmmm. At a loss
  4. I have my SSDs connected to an LSI hba from 2011. Wonder if that might be the problem. I am going to try and connect all drives to onboard.
  5. So i have been battling with terrible performance in unraid and after trying for hours i decided to just start with a fresh install. I made a backup of my unraid key and reinstalled unraid to the flash drive so I could start fresh. I started unraid up but cancelled the parity check to copy backup of my plex appdata back to the cache drive. I dont have critical files. I formatted my two SSD drives as zfs. 2 seperate pools. One for downloads and one for VMs and docker. I brought up the web terminal and started copying the plex appdata folder to the cache drive. The copying started off quickly copying a few thousand files every 5 seconds or so. Plex is full of small files. Thing is the copying pauses after about 10 seconds completely and I can see high IO wait and CPU usage. Surely copying from HDD to SSD shouldn't be a bottleneck. There is absolutely nothing else installed on this fresh install other than the community applications plugin so that I am ready to install plex after the copy. So I am beginning to think that I have a hardware issue. Does anyone have any suggestions? I will include my diagnostics. Really hope someone can help here. Thanks for taking the time to read. tower-diagnostics-20230627-2106.zip
  6. I swapped out the SSD to troubleshoot and this solved the problem. Not sure what caused it in the first place. I have moved away from btrfs as its only a single drive. Could this have been the issue? I am going to put the old ssd into another machine and check for any issues with the drive itself. With the new ssd in all is good!
  7. Thanks for the reply Squid. These orphaned images happen without me changing a thing. I only update from the docker tab.
  8. I forgot to mention the docker orphans. I will get random dockers that stop working and then I see that the image is orphaned on the docker page. I have to manually add the docker again to get it running. No idea why this is also happening.
  9. I am trying to work out why my system locks up every now and then. When this happens the CPU usage shows 100% on all 4 cores. This will continue for a few minutes and then the system comes back down to normal usage. My system Intel i5-6600k 16GB memory. I am only using 30% of the system memory. I'm pretty sure my i5-6600k is plenty for my use case. Only have a few docker containers running and not running any VMs I have attached my diagnostics. Tried looking through the logs but im not seeing anything. Hope someone can shed some light on this for me. Thanks tower-diagnostics-20230423-1922.zip
  10. Unraid did mention that it would rebuild parity when I did this but it only formatted the drives. Maybe I should run a parity check?
  11. OK all good! I let the array rebuild parity. Then I used Unbalance to move the data off of the drive that still had data on it. After this I stopped the array and set all the disks to "auto" on file system. Started the array and the 3 disks were waiting to be formatted. I went ahead and did this and now the drives are all mounting on xfs automatically. Thank you JorgeB !
  12. Much appreciated! I will do so after parity rebuild and report back.
  13. OK cool. How would I do that with the "dd" command please? Thanks
  14. It came back with a new UUID when i ran the command but it still didnt mount and the blkid command is attached. I have to go to the office now and I'm quite worried about losing data. I am going to mount forcing XFS on those three drives and let parity rebuild. I'm thinking once that is done I will: 1) transfer the data off all those drives 2) set filesystem back to auto 3) stop and start the array 4) format the unmountable drives This should do the trick right? I'm just worried about having no parity and a drive failing. Really Really appreciate your help so far.