JKY

Members
  • Posts

    15
  • Joined

  • Last visited

Everything posted by JKY

  1. Update for Googlers. I have a Gen2 Ryzen 2700ghz and I have hand clocked the RAM at 3200mhz. Everything has been working fine, it must have been that XMP profile. Thank you for the help.
  2. EDIT: I think its the XMP profile. I have two sticks of 8gb 3600mhz. I just set my BIOS to default which puts it back to 2100mhz. Had no issues in the past 4-5 hours. I set XMP profile when I tried to add a Windows Gaming VM, back when all the issues started. Looking around the forums, I can see other people have had issues with XMP. I will give it a few days and report back. - Regards.
  3. So, I did a parity correcting check, then a another parity check which found no errors. I then added the NVME cache back in and did yet another check. Everything was good. However last night 4-5 of my 8 cores were at 100% there system was slow. I tried to spin down the array and it would not let me, I tried to reboot via the UI and again it would not let me. Terminal sudo shutdown, didn't response... I had no idea what this was stuck on. If I hook a monitor up I can see it was doing a checksum... fine, I left it running all night. This morning it has spinlock on. I took some snaps on my phone camera and but I cant doing anything like scroll up to follow the output. The GUI will no longer loads from a browser, I have no idea what is going on... can anyone help advise? There is a lot of HEX but some of the lines of code include. TASK queued spin lock, list lru, inode iru list del, task work run do syscall 64 RIP RAP RAX RDX RBP R10 R13 /TASK
  4. Oh really? Thats going to take like 2-3 days.... But ok...
  5. At the start of last week, I upgraded the Unraid OS from 6.10.3 to 6.11.5. Other the next few days I did some extra tasks. I added a second cache pool with an NVME drive. I added a VM running Win10 with a GTX1060, which pointed to the NVME drive. I changed my RAM from the default 2100mhz to XMP native 3600mhz speeds. My parity check runs on the last Friday of every month and Saturday morning, my server was on but the UI was inaccessible. I rebooted and started to run the parity check. A few hours later, it had frozen up again. I another try and another crash, I noticed that you would see from the dashboard there was an issue, as after an hour a few cores would lock to 100% and the time left of the check would freeze. I read over the forums and saw someone had an issue kind of like this in the past. It was determined there was a hardware issue… so I started rolling back and trying a parity check after each step. As you can guess this took all weekend. Blew away VM, still crashed on parity check. Removed NMVE Cache pool, still crashed on parity check. Rolled back XMP, still crashed on parity check. Lastly… rolls back the OS. This seems to have worked, I have about three hours to go until it is complete. Anyway, it would seem as if the OS was the issue, but is there a way I check the points of failure? The parity check says there are 90 sync errors, I unticked the box to correct them because I don’t know what they are. Can untick correction by default?
  6. I thought that the disk with the least space would fill up first. I see now the order of the disks is key. Would it be easy to reorder the disks, or am in for a world of hurt?
  7. Thanks for the reply. I made the change to "Split Any Directory As Required", which is what I assume you mean by 'unlimited'. (on 6.9.2) Still going to the smaller drive. 🤔
  8. Thank you for yor help here. I want to fill up the disk with the least space. I changed the split level to: Manual Do Not Auot Split. Should that tecnialy do what I am lookingf for? Beucase, I just tried again and the files are still going to disk 2 and not disk 4 which is aprox 80% full and where I would actualy like the files to be.
  9. I see... I thought four levels would help keep files and subfolders together. Should I change it to one level? or have not split at all?
  10. I have a media share across two disks: Disk 2 at 3tb and Disk 4 at 6tb I have used unbalance to move everything from the 3tb drive to the 6tb drive which is now has 1tb of space left. I have set the share allocation method to fill-up and the minimum free space to 10gb (also tried 0kb) Whenever I add new content it goes to the 3tb disk, I have to use unbalance again to move a second time. I dont want move disks spinning than needed. This is something I looked into on this forum but didn’t find a clear answer. The help would seem to suggest 'Fill-Up' fills the disk with the least space, but it might also meand the disk that first in the array. ‘Fill-up Choose the lowest numbered disk that still has free space above the current Minimum free space setting.’ TLDR: Should new content not just go to disk 4? Is it an issue with the disk order?
  11. I started my Unraid server before Christmas. I have not done too much with it so far, it just runs PLEX. So I'd like to start over, from scratch and put in place some better practices I have since learnt. So what I'd like to be sure of... if I used the same USB drive I am using now, as its GUID has been logged... Would I run into any issues by rerunning the install tool onto this drive? - Thanks in advanced.
  12. Thank you! This fixed the issue for me, notably this bit: "Since mapped drives are user-centric, that Admin user context will not have the (same) drives, and you'll have to map them for that user context once the command window is open as Adminsitrator, e.g. by running net use <letter>: \\<server>\<share>. "
  13. Hello, I am new. I was told about UnRaid about two months ago. Just built a Ryzen 8 core PC with 24GB or RAM for gameing. So it was the perfect time to try UnRaid.... I was blown away! "One thing you like most about Unraid" The value it offers. With the use of VMs, Docker, Parity.... I can do so much stuff the I used to do across multiple computers. One thing you'd like to see added to the OS in 2020. Controls to snapshot or back up a VM or Docker configurations you got right. I messed up my gaming VMs XML and the easiest was out was to start the installer over.