Jump to content

Jacrushar

Members
  • Content Count

    23
  • Joined

  • Last visited

Community Reputation

2 Neutral

About Jacrushar

  • Rank
    Member
  1. Oof, I remember setting up port forwarding on my router for my unraid server back when I was trying to set up a NextCloud docker. Ended up ditching it but forgot to remove that. Thanks!
  2. From the fix common problems plugin: /var/log is getting full (currently 80 % used) Either your server has an extremely long uptime, or your syslog could be potentially being spammed with error messages. A reboot of your server will at least temporarily solve this problem, but ideally you should seek assistance in the forums and post your Server has only been up for 32 days and just started getting this warning over the weekend. I attached the diagnostics zip file. Any assistance in understanding what the problem is would be greatly appreciated. hardi-unraid-diagnostics-20190904-0814.zip
  3. If I'm doing that, I might as well move it to the new case I guess? That's what the new case is for
  4. So I was about to move my entire unraid system into a new computer case and I read that it is a good idea to do a parity check before and after. My computer case arrived today so I started a parity check. Probably no more than 5 min in and my Parity drive is now disabled... This drive is just a few weeks old since I had a failure a few weeks ago and did a parity swap procedure with the new (larger than old parity) drive. I've attached my diagnostics zip file, anyone able to understand it able to confirm what went wrong? Should I go ahead and move the system to the new computer case anyways? If the drive is permanently broken, hopefully it is under warranty... Any help is appreciated.
  5. I see this post is old... but nobody seems to have responded to it. I had a similar issue where my VM with a GTX 970 passed through would BSOD with the error VIDEOS_CHEDULER_INTERNAL_ERROR as well. I found this page while searching for why. I fixed it by going into my motherboard bios and setting the integrated graphics (iGPU) to be the primary. I think the BSOD was being caused by the Unraid host OS trying to use the 970 at the same time as the VM was. By choosing the iGPU in the BIOS, the Unraid Host OS will use that one instead, freeing up the 970 for my VM. Hope this helps someone.
  6. I know this post is old... I have a VM with a GTX 970 passed through to it and I am wondering how one would set unraid to use the igpu when you boot it into gui mode?
  7. Ran the parity copy again last night and was able to start the array this morning to begin the data rebuild. So I guess everything is fine. Here is my diagnostics file. unraid-diagnostics-20180708-0837.zip
  8. Ok that makes sense. Thanks for clearing up my question about the zeroing of the parity drive. Sorry I didn't have much info, was in a hurry and heading out when I wrote the post and haven't gotten a chance to sit at the computer again since. I'll start the parity copy again when I do. Where do I get the diagnostics you're speaking of? Downloading the smart report for each drive or something?
  9. Hi, I had a drive failure and I'm replacing it with a new drive that is larger than the parity. I am following this procedure https://lime-technology.com/wiki/index.php/The_parity_swap_procedure I made it to step 13 where it copied the parity drive over to the new drive to make it become the new parity drive (ran all night). Then when trying to follow step 14 to start the array and start the rebuild process, nothing would happen. I would click start and the page would hang until I refreshed the page, which would bring me right back to the same page as if I never clicked the start button. I then clicked reboot but after waiting 10min for it to reboot with nothing else to do I just held the power button down to kill it and start it up again. Now the server is back up and it looks like I'll have to start the parity copy process all over again... I'm not sure if I should do that because step 13 implies that the parity disk was zero'd after it was completed... so if I copy again would I just be erasing my parity? Any ideas anyone? Should I just start the copy again and hope it starts up after it is finished this time?
  10. Sounds good. Well thank you very much for all your help Johnnie.black! You saved me a lot of headache.
  11. It looks like the drive rebuilt just fine, it mounted and everything and it also LOOKS like all my data is intact. Is there a way to be sure there is no corruption?
  12. Just finished performing your recommended steps johnnie.black. Looks like disk1 is rebuilding right now! Hopefully it all works out just fine. Once it is done rebuilding, how do I run the filesystem check you mentioned above? Thanks again for all your help.
  13. Thanks johnnie.black! I'll give this a shot when the new drive comes in hopefully in the next couple days here. Fingers crossed...