-
Posts
160 -
Joined
-
Last visited
Content Type
Profiles
Forums
Downloads
Store
Gallery
Bug Reports
Documentation
Landing
Report Comments posted by Zer0Nin3r
-
-
I just noticed that this was happening to me now that I have upgraded to Unraid 6.9. It's a real bummer that we have to do a work around in the meantime.
My only hesitancy with this workaround is that I know I'll forget to remove the added code instructions once this resolves itself.
I just submitted a feedback/bug report from within Unraid's dashboard and linked back to this post in the bug report. Hopefully the Unraid team pushes out an official patch. 🤞🏼
- 2
-
On 10/4/2018 at 11:11 PM, bonienl said:
This is by design of the kernel. See also Help on the CPU pinning page.
Is there another way of wording the explanation that you quoted? I read the same thing under the help toggle when logged into the Web GUI, but for some reason it isn't clicking for me on how 'CPU Isolation works'.
-
5 hours ago, eschultz said:
That was a issue in 6.6.2 but should have been fixed in 6.6.3. Is that still broken for you?
The restart within Windows 10 is now fixed.
Ha. I literally just signed on to come back and update my post. Thank you for the speedy response @eschultz
-
On 11/5/2018 at 9:35 AM, drugdoctor said:
I used a hex editor as spaceinvaders suggested in his video and and I still get the error code 43.
When you were dumping the bios, were you trying to dump from slot 1? I understand that better chances of success are to be made when you move your primary GPU from slot one to a different slot, then dump the bios. Try that and report back to see if that solves the issue for you.
On 11/5/2018 at 3:25 PM, ks2016 said:- nvidia vga & audio + dumped bios
When you dumped the bios, did you find it helped to place the GPU you're trying to pass through in another slot other than Slot 1?
Are you doing single pass through, or do you have a secondary GPU for Unraid? This information will help other users.
===
I journaled extensively about my process in order to get GPU pass through without Error Code 43.
Also to be noted, I stopped using the Restart VM button in Unraid because it wasn't functioning properly; same when using Restart from inside the Windows 10 VM. Now I just use the shutdown method inside the VM. -
- I tried for the life of me on four USB sticks. The Lime Tech USB Creator v 1.5 wouldn't pick up the USB drive in step two. I tried attaching the sticks directly to the MacBook Air (2014 w/ High Sierra 10.13.6). Nothing.
-
Even tried Etcher since it works with zip files, but Etcher wouldn't work with the zip image file from LT.
- Would it free up resources from LimeTech to just have an ISO that can be flashed with Etcher instead of custom writing a USB creator software in house?
- Sticks were formatted to FAT32 labeled UNRAID.
- Even the manual creation using the script in terminal would recognize the drive but throw up some sort of error about the partition.
What worked:
- Using Disk Utility in Mac OS >> View >> Show All Devices >> Select the USB device >> Partition >> FAT32 >> Label it as UNRAID >> Ensure that Partition Map is set to Bootable
- Once the disk drive is formatted, then the script for the Manual Method worked as intended.
I would like to update the Wiki to reflect this; I would be happy to update the wiki with this little tidbit.
-
Also, can we get the Wiki updated in an official capacity? I'm finding it hard to navigate the manual/wiki in finding information that I need i.e., there is a lot of outdated information. -
Additionally, the backend for the unRAID forum isn't the greatest as the search isn't the best.- I'm finding that appending the search operator: site:forums.unraid.net in DuckDuckGo/Startpage/Google to your search works better at finding what you are looking for than using the forum's search.)
P.S. - After all that's been said and done, I was able to get unRAID going on a low profile SanDisk USB stick. Super cheap I might add.
Search of SMB shares not working (MacOS client)
-
-
-
-
-
in Prereleases
Posted · Edited by Zer0Nin3r
Do we have to input share specific folders? Would stopping at '/mnt/user/' allow the spotlight flag to be recursive?
This is what the default looks like: