phbigred

Members
 View Profile  See their activity

  • Posts

    265

  • Joined

  • Last visited

  • Days Won

    1

 Content Type 

Report Comments posted by phbigred

    Unraid OS version 6.8.0-rc4 available

    in Prereleases

    Posted · Edited by phbigred

    @limetechAny plans on putting in the fixes done by this person's recompile?

     

     

    This custom kernel fixes the VM VFIO bug with no GPU passthrough that @SpaceInvaderOne likely documented. This works for my MSI x370 sli plus with ryzen 3000 compatibility AGESA 1.0.0.3 ABBA code. 

     

    Also were there any NIC changes with this version 6.8 branch that would affect VM br0 passthrough? Noticing an issue with gateway routing for my VPN traffic. I have to put my entire server outside the VPN as I can't individually route now.

    Unraid OS version 6.8.0-rc1 available

    in Prereleases

    Posted

    8 minutes ago, Woodpusherghd said:

    Tried 6.8.0-RC1 and ran into a problem with my Windows 10 VM.  I have a wireless mouse and keyboard connected through a Logitech Unifying Receiver.  Under V6.7.2 when I booted unRaid into GUI mode I could use the mouse and keyboard.  When I started the Windows 10 VM (passing through an AMD 5450 GPU) the unifying receiver was also passed through and I could use the mouse and keyboard in the VM.  When I booted 6.8.0-RC1, the mouse and key board were not usable in the VM and when I tried to hot plug the receiver, I got an error messge that it was already being used by Qemu.  BTW, I have an additional video card that unRaid boots into and I can switch back and forth from unRaid and the VM using a hdmi switch.  In the case of v6.7.2, when the mouse and keyboard were usable in the VM, they were not usable in unRaid. In V6.8.0-RC1 the mouse and keyboard were usable in unRaid even after the VM booted.  It's as though V6.7.2 would release the mouse and keyboard to the VM while V6..8.0-RC1 doesn't.  Anyone else experience this problem?

    Saw something similar with mine. A simple VM restart fixed it and it only happened once.

    [6.7.0-rc5] Dashboard CPU erroneously stuck at 100%

    in Prereleases

    Posted

    44 minutes ago, presence06 said:

    If you're using Windows 10 and it's on 1903 version/Insider Edition, and you are remoting into it, once you disconnect it will peg 1 or 2 threads/cpu's.... I found this out and had to remove the Inside Edition from my VM and went back to the previous Version of Win10...  As of today it's still doing it even after the latest Insider update.

     

    If you remote in, DC and then remote back in, it will settle..but once you DC again it'll spike... something to do with the new background blur maybe in Win 10? not sure.

    This isn't VM related this is a general UI bug. I pin my CPUs and it happens to ones assigned to unraid outside of VM isolation.

    Unraid 6.7-rc6 unable to stop array.

    in Prereleases

    Posted

    2 hours ago, kizer said:

    Food for thought, but not knowing what the issue is as of yet.

     

    I always stop the Parity Check when I do a reboot if there was a glitch to cause the Reboot/Parity Check. I normally have to fix something or I know exactly what caused it. Then I proceed to doing what I need to do and then Start the Parity check.

     

    Do you have Dockers that might be reading/writing to the array that might of got stuck during a shutdown? I've had a problem with Dockers not shutting down and then glitching out my SSD or doing a Database Backup to one of my spinners and when it was forced down my machine came backup with a message saying it wanted to do a Parity Check.

     

    Now I shutdown all my Dockers manually every time to insure they are down before doing a reboot.

    It's a good point but this is new with the 6.7 branch for me. What you recommend is probably a good standard process to do in general. 

    Unraid 6.7-rc6 unable to stop array.

    in Prereleases

    Posted · Edited by phbigred

    Rebooted fine though ssh. Waiting for it to show up again. Triggered a parity check though. Any idea which process/task is causing this to trigger? Stinks having to reboot to stop my array to make a disk setting level adjustment. Especially when the btrfs is on one single cache drive and a drive that us in unassigned devices. Thoughts or ideas how to stop this from occuring? This issue is new in 6.7 branch for me.

    Unraid OS version 6.7.0-rc3 available

    in Prereleases

    Posted · Edited by phbigred

    11 hours ago, bonienl said:

    The display in your screenshot doesn't look right. Try the following

    • Start your system in safe mode (no plugins loaded)
    • When using adblocker or anti-virus then whitelist or exclude the GUI

    You were right, my system tripped a parity check after reboot. System is again responsive. Was throwing random 502 errors on the plug-in update page when this was all occuring. Snagged a diags too while occuring if you guys think it's helpful I'll post.

     

    I do use xfs encryption but I don't think it's related. I had 100MB/S access to my write access shares with cache and 60ish with straight array targets.

    Unraid OS version 6.7.0-rc3 available

    in Prereleases

    Posted · Edited by phbigred

    1268666509_Screenshot_20190213-0911032.thumb.png.46fdba8bd28ff0263b6958852444750b.png

    24 minutes ago, Frank1940 said:

    Not an issue here with my setup.  Please describe in greater detail what you experiencing.   What Protocol --SMB, NFS, etc.?  Are you talking about 'User access' or  'Security settings'?  ('User access' is the only one on my system that "read" vs "read-write" option.)

    SMB user access. It's not tied to one specific share either. All shares do a similar thing in RC3 for my setup. I hit apply and it just sits there. Tested on multiple browsers IE Edge Firefox Chrome and mobile Safari

     

    [6.7.0 RC1] Drives drop off Marvell controller

    in Prereleases

    Posted · Edited by phbigred

    Does pci-e nvme use marvel controllers? Having a similar situation with my WD black nvme. Kept dropping offline, updated my bios and magically it's back after 2 days. Quick snagged my vdisk.img off it in case it went belly up again. Only started occuring after the 6.7 upgrade.