poopsie
-
Posts
62 -
Joined
-
Last visited
Content Type
Profiles
Forums
Downloads
Store
Gallery
Bug Reports
Documentation
Landing
Posts posted by poopsie
-
-
I wanted to see if this was an expected behavior or a bug before I submit a report. When I go to the VM Settings, even if I do not make any changes at all, I get the banner from that point forward as seen in the picture. It happens the second I click the VM Settings icon, like I said, without changing any of the settings at all. It is really annoying to look at a setting for something, and have to reboot the server to clear the banner. Thoughts?
-
Hey everyone,
I have UNRAID running with multiple VM's. I want one of those to have an HBA passed through to it.
I have two HBA (in IT mode) cards in the machine and they both have the same vendor ID, so I am unable to use append vfio-pci.ids= on the flash
The two cards are:
IOMMU group 18:[1000:0072] 04:00.0 Serial Attached SCSI controller: Broadcom / LSI SAS2008 PCI-Express Fusion-MPT SAS-2 [Falcon] (rev 03)
IOMMU group 53:[1000:0072] 42:00.0 Serial Attached SCSI controller: Broadcom / LSI SAS2008 PCI-Express Fusion-MPT SAS-2 [Falcon] (rev 03)
I have created the file /boot/config/vfio-pci.cfg.
Inside of that file I have:
BIND=0000:42:00:0
The output of LSPCI -V is
42:00.0 Serial Attached SCSI controller: Broadcom / LSI SAS2008 PCI-Express Fusion-MPT SAS-2 [Falcon] (rev 03)
Subsystem: Dell 6Gbps SAS HBA Adapter
Flags: bus master, fast devsel, latency 0, IRQ 53, NUMA node 1
I/O ports at 9c00
Memory at d0ff0000 (64-bit, non-prefetchable)
Memory at d0f80000 (64-bit, non-prefetchable)
Expansion ROM at d0000000 [disabled]
Capabilities: [50] Power Management version 3
Capabilities: [68] Express Endpoint, MSI 00
Capabilities: [d0] Vital Product Data
Capabilities: [a8] MSI: Enable- Count=1/1 Maskable- 64bit+
Capabilities: [c0] MSI-X: Enable+ Count=15 Masked-
Capabilities: [100] Advanced Error Reporting
Capabilities: [138] Power Budgeting <?>
Kernel driver in use: mpt3sas
Kernel modules: mpt3sasAfter a reboot, I am unable to see the HBA in the PCI devices when I go to edit the VM. Is there something else I need to to call that file during boot? Or did I create the vfio-pci.cfg wrong?
Thanks for the help!
SYSLOG has been attached from reboot
-
I actually moved it over to another server and it is working fine. It must have been some sort of hardware issue-
Thanks for the help
-
4 hours ago, jonathanm said:
Those two facts lead me to bad RAM. Has this new machine had at least 24 hours running memtest with a clean result? If it's using ECC RAM, I think you will need to create a boot USB with the new proprietary memtest program to get accurate results.
Perhaps as a test temporarily remove half the RAM and see if the symptoms change, swap with the removed set of RAM and repeat.
So I ran home and swapped out RAM from another machine. It did the same thing, no change. I had my old R710 laying around still that it was working on prior to the server move, so I pulled the RAM from that also. No change, same error. This one really has me stumped....
-
15 minutes ago, jonathanm said:
Those two facts lead me to bad RAM. Has this new machine had at least 24 hours running memtest with a clean result? If it's using ECC RAM, I think you will need to create a boot USB with the new proprietary memtest program to get accurate results.
Perhaps as a test temporarily remove half the RAM and see if the symptoms change, swap with the removed set of RAM and repeat.
I will give this a shot in a few hours and report back. Thank you!!!!
-
4 minutes ago, testdasi said:
This looks to be a rather idiosyncratic problem with Windows and not Unraid. That file looks to be some HBA controller driver according to Google so I would suggest you rebuild your install media and reinstall Windows from scratch.
So just an update on what I have tried. I have redownloaded Server 2016 and also Server 2012. They both are doing the exact same thing as you have seen above. I completed deleted my libvirt file and started over from scratch. I have pulled all my NIC cards, no change. I swapped my H310 HBA for an H200, no change. I have included more screenshots, as the file changes on every reboot. I tried creating the VM with just one core. Nothing is working, and I am getting a little nervous as this is a production machine. I appreciate any advice anyone is able to give-
-noVNC.thumb.jpg.0be8d92fe49e91e95de0ec48520137f5.jpg)
-noVNC.thumb.jpg.0962eb5cc94f6c2c8cffc17322f763a3.jpg)
-noVNC.thumb.jpg.dc76015647b5aee675eacd01be58a42d.jpg)
-
I am having the same problem right now, and really having a hell of a time. Did you figure this out at all?
-
-
I moved to a new server, an R720 vs an R710 like before. I moved all data over, and used the same USB, just created a new array. Now, I am unable to create a Server 2016 VM. Windows is no issue. It does install properly, and I go through everything to the desktop. Then, when I reboot, it fails and gives me the screen I added with the files. Then, if I make a change to the VM under edit, either moving to another NIC, or adding a virtual drive, whatever, it fires right up. Then, when I reboot, I get the same screen you see, again. Does anyone have any ideas as to what I am doing wrong??
Thanks!
<?xml version='1.0' encoding='UTF-8'?>
<domain type='kvm' id='36'>
<name>LabDC01</name>
<uuid>6a058db3-194f-a87c-89f4-901f80c72dc2</uuid>
<metadata>
<vmtemplate xmlns="unraid" name="Windows 10" icon="windows.png" os="windows10"/>
</metadata>
<memory unit='KiB'>4194304</memory>
<currentMemory unit='KiB'>4194304</currentMemory>
<memoryBacking>
<nosharepages/>
</memoryBacking>
<vcpu placement='static'>8</vcpu>
<cputune>
<vcpupin vcpu='0' cpuset='8'/>
<vcpupin vcpu='1' cpuset='20'/>
<vcpupin vcpu='2' cpuset='9'/>
<vcpupin vcpu='3' cpuset='21'/>
<vcpupin vcpu='4' cpuset='10'/>
<vcpupin vcpu='5' cpuset='22'/>
<vcpupin vcpu='6' cpuset='11'/>
<vcpupin vcpu='7' cpuset='23'/>
</cputune>
<resource>
<partition>/machine</partition>
</resource>
<os>
<type arch='x86_64' machine='pc-i440fx-3.1'>hvm</type>
</os>
<features>
<acpi/>
<apic/>
</features>
<cpu mode='host-passthrough' check='none'>
<topology sockets='1' cores='4' threads='2'/>
</cpu>
<clock offset='localtime'>
<timer name='rtc' tickpolicy='catchup'/>
<timer name='pit' tickpolicy='delay'/>
<timer name='hpet' present='no'/>
</clock>
<on_poweroff>destroy</on_poweroff>
<on_reboot>restart</on_reboot>
<on_crash>restart</on_crash>
<devices>
<emulator>/usr/local/sbin/qemu</emulator>
<disk type='file' device='disk'>
<driver name='qemu' type='raw' cache='writeback'/>
<source file='/mnt/user/VMs/LabDC01/vdisk1.img'/>
<backingStore/>
<target dev='hdc' bus='sata'/>
<boot order='1'/>
<alias name='sata0-0-2'/>
<address type='drive' controller='0' bus='0' target='0' unit='2'/>
</disk>
<controller type='pci' index='0' model='pci-root'>
<alias name='pci.0'/>
</controller>
<controller type='ide' index='0'>
<alias name='ide'/>
<address type='pci' domain='0x0000' bus='0x00' slot='0x01' function='0x1'/>
</controller>
<controller type='sata' index='0'>
<alias name='sata0'/>
<address type='pci' domain='0x0000' bus='0x00' slot='0x04' function='0x0'/>
</controller>
<controller type='virtio-serial' index='0'>
<alias name='virtio-serial0'/>
<address type='pci' domain='0x0000' bus='0x00' slot='0x05' function='0x0'/>
</controller>
<controller type='usb' index='0' model='ich9-ehci1'>
<alias name='usb'/>
<address type='pci' domain='0x0000' bus='0x00' slot='0x07' function='0x7'/>
</controller>
<controller type='usb' index='0' model='ich9-uhci1'>
<alias name='usb'/>
<master startport='0'/>
<address type='pci' domain='0x0000' bus='0x00' slot='0x07' function='0x0' multifunction='on'/>
</controller>
<controller type='usb' index='0' model='ich9-uhci2'>
<alias name='usb'/>
<master startport='2'/>
<address type='pci' domain='0x0000' bus='0x00' slot='0x07' function='0x1'/>
</controller>
<controller type='usb' index='0' model='ich9-uhci3'>
<alias name='usb'/>
<master startport='4'/>
<address type='pci' domain='0x0000' bus='0x00' slot='0x07' function='0x2'/>
</controller>
<interface type='bridge'>
<mac address='52:54:00:3c:c4:5d'/>
<source bridge='br0'/>
<target dev='vnet2'/>
<model type='virtio'/>
<alias name='net0'/>
<address type='pci' domain='0x0000' bus='0x00' slot='0x03' function='0x0'/>
</interface>
<serial type='pty'>
<source path='/dev/pts/2'/>
<target type='isa-serial' port='0'>
<model name='isa-serial'/>
</target>
<alias name='serial0'/>
</serial>
<console type='pty' tty='/dev/pts/2'>
<source path='/dev/pts/2'/>
<target type='serial' port='0'/>
<alias name='serial0'/>
</console>
<channel type='unix'>
<source mode='bind' path='/var/lib/libvirt/qemu/channel/target/domain-36-LabDC01/org.qemu.guest_agent.0'/>
<target type='virtio' name='org.qemu.guest_agent.0' state='disconnected'/>
<alias name='channel0'/>
<address type='virtio-serial' controller='0' bus='0' port='1'/>
</channel>
<input type='tablet' bus='usb'>
<alias name='input0'/>
<address type='usb' bus='0' port='1'/>
</input>
<input type='mouse' bus='ps2'>
<alias name='input1'/>
</input>
<input type='keyboard' bus='ps2'>
<alias name='input2'/>
</input>
<graphics type='vnc' port='5902' autoport='yes' websocket='5702' listen='0.0.0.0' keymap='en-us'>
<listen type='address' address='0.0.0.0'/>
</graphics>
<video>
<model type='qxl' ram='65536' vram='65536' vgamem='16384' heads='1' primary='yes'/>
<alias name='video0'/>
<address type='pci' domain='0x0000' bus='0x00' slot='0x02' function='0x0'/>
</video>
<memballoon model='virtio'>
<alias name='balloon0'/>
<address type='pci' domain='0x0000' bus='0x00' slot='0x06' function='0x0'/>
</memballoon>
</devices>
<seclabel type='dynamic' model='dac' relabel='yes'>
<label>+0:+100</label>
<imagelabel>+0:+100</imagelabel>
</seclabel>
</domain>
-noVNC.thumb.png.6c526b50923dc0ed42f3137e16346dd8.png)
-
I installed another instance of Server 2016, using the template. It installs, but reboot always fails to boot. I get a windows error about hardware changing. I think I narrowed it down to the HyperV tweaks. If I turn that off, it boots fine. But, when I reboot, it automatically turns it back on and I can't boot again without changing it to NO. Has anyone ever had this issue? I have two unraid boxes, and after upgrading to 6.7.0, they both do this now.
Thanks for any help! Here is the XML of it
<?xml version='1.0' encoding='UTF-8'?>
<domain type='kvm' id='27'>
<name>W10VM1</name>
<uuid>a7bdb834-b276-a940-09ef-771559fb13c7</uuid>
<metadata>
<vmtemplate xmlns="unraid" name="Windows Server 2016" icon="windows.png" os="windows2016"/>
</metadata>
<memory unit='KiB'>4194304</memory>
<currentMemory unit='KiB'>4194304</currentMemory>
<memoryBacking>
<nosharepages/>
</memoryBacking>
<vcpu placement='static'>8</vcpu>
<cputune>
<vcpupin vcpu='0' cpuset='4'/>
<vcpupin vcpu='1' cpuset='16'/>
<vcpupin vcpu='2' cpuset='5'/>
<vcpupin vcpu='3' cpuset='17'/>
<vcpupin vcpu='4' cpuset='6'/>
<vcpupin vcpu='5' cpuset='18'/>
<vcpupin vcpu='6' cpuset='7'/>
<vcpupin vcpu='7' cpuset='19'/>
</cputune>
<resource>
<partition>/machine</partition>
</resource>
<os>
<type arch='x86_64' machine='pc-i440fx-3.1'>hvm</type>
</os>
<features>
<acpi/>
<apic/>
</features>
<cpu mode='host-passthrough' check='none'>
<topology sockets='1' cores='4' threads='2'/>
</cpu>
<clock offset='localtime'>
<timer name='rtc' tickpolicy='catchup'/>
<timer name='pit' tickpolicy='delay'/>
<timer name='hpet' present='no'/>
</clock>
<on_poweroff>destroy</on_poweroff>
<on_reboot>restart</on_reboot>
<on_crash>restart</on_crash>
<devices>
<emulator>/usr/local/sbin/qemu</emulator>
<disk type='file' device='disk'>
<driver name='qemu' type='raw' cache='writeback'/>
<source file='/mnt/user/VMs/W10VM1/vdisk1.img'/>
<backingStore/>
<target dev='hdc' bus='sata'/>
<boot order='1'/>
<alias name='sata0-0-2'/>
<address type='drive' controller='0' bus='0' target='0' unit='2'/>
</disk>
<disk type='file' device='cdrom'>
<driver name='qemu' type='raw'/>
<source file='/mnt/user/Data/Software/Virtual_Machine_ISOs/Windows 10 - trial.iso'/>
<backingStore/>
<target dev='hda' bus='ide'/>
<readonly/>
<boot order='2'/>
<alias name='ide0-0-0'/>
<address type='drive' controller='0' bus='0' target='0' unit='0'/>
</disk>
<disk type='file' device='cdrom'>
<driver name='qemu' type='raw'/>
<source file='/mnt/user/Data/Software/Virtual_Machine_ISOs/virtio-win-0.1.160-1.iso'/>
<backingStore/>
<target dev='hdb' bus='ide'/>
<readonly/>
<alias name='ide0-0-1'/>
<address type='drive' controller='0' bus='0' target='0' unit='1'/>
</disk>
<controller type='usb' index='0' model='ich9-ehci1'>
<alias name='usb'/>
<address type='pci' domain='0x0000' bus='0x00' slot='0x07' function='0x7'/>
</controller>
<controller type='usb' index='0' model='ich9-uhci1'>
<alias name='usb'/>
<master startport='0'/>
<address type='pci' domain='0x0000' bus='0x00' slot='0x07' function='0x0' multifunction='on'/>
</controller>
<controller type='usb' index='0' model='ich9-uhci2'>
<alias name='usb'/>
<master startport='2'/>
<address type='pci' domain='0x0000' bus='0x00' slot='0x07' function='0x1'/>
</controller>
<controller type='usb' index='0' model='ich9-uhci3'>
<alias name='usb'/>
<master startport='4'/>
<address type='pci' domain='0x0000' bus='0x00' slot='0x07' function='0x2'/>
</controller>
<controller type='pci' index='0' model='pci-root'>
<alias name='pci.0'/>
</controller>
<controller type='ide' index='0'>
<alias name='ide'/>
<address type='pci' domain='0x0000' bus='0x00' slot='0x01' function='0x1'/>
</controller>
<controller type='sata' index='0'>
<alias name='sata0'/>
<address type='pci' domain='0x0000' bus='0x00' slot='0x04' function='0x0'/>
</controller>
<controller type='virtio-serial' index='0'>
<alias name='virtio-serial0'/>
<address type='pci' domain='0x0000' bus='0x00' slot='0x05' function='0x0'/>
</controller>
<interface type='bridge'>
<mac address='52:54:00:c0:5f:70'/>
<source bridge='br0'/>
<target dev='vnet1'/>
<model type='virtio'/>
<alias name='net0'/>
<address type='pci' domain='0x0000' bus='0x00' slot='0x03' function='0x0'/>
</interface>
<serial type='pty'>
<source path='/dev/pts/1'/>
<target type='isa-serial' port='0'>
<model name='isa-serial'/>
</target>
<alias name='serial0'/>
</serial>
<console type='pty' tty='/dev/pts/1'>
<source path='/dev/pts/1'/>
<target type='serial' port='0'/>
<alias name='serial0'/>
</console>
<channel type='unix'>
<source mode='bind' path='/var/lib/libvirt/qemu/channel/target/domain-27-W10VM1/org.qemu.guest_agent.0'/>
<target type='virtio' name='org.qemu.guest_agent.0' state='disconnected'/>
<alias name='channel0'/>
<address type='virtio-serial' controller='0' bus='0' port='1'/>
</channel>
<input type='tablet' bus='usb'>
<alias name='input0'/>
<address type='usb' bus='0' port='1'/>
</input>
<input type='mouse' bus='ps2'>
<alias name='input1'/>
</input>
<input type='keyboard' bus='ps2'>
<alias name='input2'/>
</input>
<graphics type='vnc' port='5901' autoport='yes' websocket='5701' listen='0.0.0.0' keymap='en-us'>
<listen type='address' address='0.0.0.0'/>
</graphics>
<video>
<model type='qxl' ram='65536' vram='65536' vgamem='16384' heads='1' primary='yes'/>
<alias name='video0'/>
<address type='pci' domain='0x0000' bus='0x00' slot='0x02' function='0x0'/>
</video>
<hostdev mode='subsystem' type='pci' managed='yes'>
<driver name='vfio'/>
<source>
<address domain='0x0000' bus='0x0c' slot='0x00' function='0x1'/>
</source>
<alias name='hostdev0'/>
<address type='pci' domain='0x0000' bus='0x00' slot='0x06' function='0x0'/>
</hostdev>
<memballoon model='none'/>
</devices>
<seclabel type='dynamic' model='dac' relabel='yes'>
<label>+0:+100</label>
<imagelabel>+0:+100</imagelabel>
</seclabel>
</domain> -
Yep! It was answered in my original post on the resilio forum - here you go!
-
24 minutes ago, Squid said:
unRaid itself saves all that info automatically if you change anything. /config/plugins/dockerMan/templates-user on the flash drive.
That is why you are the best Squid-Thanks!!
-
5 minutes ago, Squid said:
If you were using that drop down, then you were doing things wrong (I had it removed from the template screen if you got there from CA a number of unRaid versions ago)
The template, whether it was a new app, or one previously installed / already installed is already filled out accordingly, and always has been. If you chose something via the drop down, then you overrode what you just told CA to do in the first place.
Gotcha, so the next question then is how are those backed up? Is it on the flash drive? What I am wondering is if I delete a Docker, how will I know it will have all the information when I reinstall it 3 years from now?
-
I have searched, and must be missing something. When I install a docker item, it used to ask me what template I wanted to use in the edit screen. That is no longer there. Did it get removed or moved to some other place? Yes I do have Community Apps installed-
Thanks!!
-
I am not sure what I am doing wrong. When I have an SMB setup in UD, it works great. No issues. But, if the NAS I have it connected to is shut down, and UD can't find it, it freezes up unraid and will not clean shut down meaning a hard shut down. Is there a time out or does it just keep trying to connect indefinitely? Thanks!
-
1 minute ago, kizer said:
I have my machine to maximize parity checks meaning I have things scheduled on the Second and if I have anything scheduled and running with the User.Scripts Plugin I have them set to not run during a parity check. However I can't stop the family from watching videos via Plex when they want to.
Sure Fast Parity Checks are kinda cool, but lets face it if we stress out about our servers constantly then they are no longer fun.
You and John totally changed my mindset on that. Unraid will do what is has to do, just slower and still provide everything I need. Thanks!!
-
15 hours ago, John_M said:
Your parity check starts at midnight and at 02:00 Community Apps Backup and Restore stops your docker containers (cadvisor, CrashPlanPRO, Krusader, plex, resilio-sync), backs up their appdata and verifies the backup, then restarts the containers at 02:19. So you might want to schedule the backups to start earlier and the parity check to start later to avoid this clash.
The syslog is quiet for the rest of the morning. At 12:23 there's a burst of network activity from a docker (I'm not sure whether it's plex or resilio-sync). At 18:00 something creates a new user share called Downloads and there's more docker activity. At 22:19 there's a lot of docker activity for 10 minutes. At 22:40 disk3 spins down (it's your smallest so it's no longer needed by the parity check). The dockers are quiet now and your cache is rested, woken and rested again. Midnight passes and at 01:15 the parity check is complete. unRAID tries to connect to gmail to send you a confirmation email and fails. The remaining disks spin down at 01:30 and the system rests until being woken up at 02:00 again by Community Apps Backup and Restore.
It isn't possible to see what dockers are doing - reads/writes aren't logged - but the system seems to be working without any obvious errors. Of your dockers I'm familiar only with Krusader and plex. Krusader is a graphical file manager and basically does nothing unless you interact with it. Plex, on the other hand, runs all sorts of background processes under the guise of "the butler", scanning your media collection and downloading metadata, indexing and cross-referencing, in addition to it's obvious job of serving up media. I understand cadvisor monitors and gathers metric on other containers, while CrashPlan is a cloud backup/sync utility and resilio sync is a pee-to-peer sync tool, so I suppose these latter two are likely to be involved in accessing your array.
I hope this gives you a few clues.
Wow, that is an amazing report! Thanks!
13 hours ago, kizer said:I have my CA backup set for the 2nd of every month myself just to insure this doesn't happen.
I think between the two of you, I have decided to loosen up a few things on my dockers (Plex being one, not as much updating) and keeping everything running with a slower parity. John nailed it on the head, I would rather have a slower parity, but still have access to everything.
Thanks guys!!
-
2 hours ago, John_M said:
Tools -> Diagnostics. Post the zip file. Make sure you haven't rebooted since the problem showed up because rebooting discards the logs.
If it turns out that your dockers are accessing the array during the parity check maybe you ought to reschedule the latter. Normally people want to optimise their server with the services it provides in mind, rather than switching off services in order to speed up the parity check. If I want to watch a Plex movie during a parity check then it's much preferable for the parity check to be slowed down than for me to have to read a book instead due to Plex being unavailable!
No reboot since then-I appreciate you taking a look!!
-
4 hours ago, John_M said:
Presumably your dockers are accessing the array while the parity check is underway, but that's just a guess as you've provided no information to work with.
Whatever I need to provide to help I will. What exactly are you looking for?
-
Just as the title says, my parity check is really slow if I have dockers runnings. I have an R710, Dual Xeon x5570 with 5 drives (4 x 4TB, 1 x 2TB in Dual parity Config). This is my first parity check using the server, and the numbers were slow - Around 30MBs. I turned off all the dockers, and the numbers on each drive went up to 140MBs. The average CPU is 1%-3%, so that is not the issue. My transfer speeds are 115 MBs, so I don't think there is a bottleneck with the H200 card. My dockers that I am running are
Crashplan
Resilio
Plex
Krusader
No VM's on, 16GB of ECC RAM. Does anyone have any insight as to why this would be? Is there a script to turn off all dockers before starting and restarting them after parity check is done?
Thanks!!
-
Just now, josh.m83 said:
Oh wow, I was totally missing scrolling all the way down... Yes! - That video was super helpful. Thanks for sticking with me, hopefully this helps someone else in the future haha!
Awesome!
-
7 minutes ago, josh.m83 said:
Yeah, it expands, but I don't see "storage" anywhere to be found within, can't browse my unRAID array at all.
I made this quick video, see if your stuff looks like mine
-
1 minute ago, josh.m83 said:
Scratch that, the only thing I can see is the root... I need to figure out how to actually browse "storage" I can't actually see it in the interface for some reason.
As weird and easy as this sounds, and I say this from experience as I had the same issue when first installed. Have you clicked on the word "ROOT" to see if it expands? It doesn't look like it should, but it will.
-
3 minutes ago, josh.m83 said:
Yeah I have, I've got a bunch of containers setup and running. I'll try and replicate what I've done in other containers I guess. Just want to make sure I get the right config.
I've got default setup as described in SpaceInvader's videos for the unraid setup video 1-3.Good, then you will have no problems. I set my /mnt/user to the storage, then in CP I choose what I want to backup. The only other thing I found earlier in this thread is to recover the files back to original location, you need to go to advanced view in the docker settings. Then click edit next to storage, and change it to RW, instead of read only.
-noVNC.jpg.89617ecd30c589af989ddc8504fb0a1b.jpg)
-noVNC.jpg.9acdd8ac6897b30f05f3a395b842c6ea.jpg)
-noVNC.jpg.997becddb377c5daeae5e21a095d479e.jpg)
-noVNC.png.a898e82852755747518b56c657a05ad8.png)
VM Settings: A reboot is required to apply changes
in General Support
Posted
What is even more odd is I have created new USB's for 6.8.2, 6.8.3 and 6.9.0, and it does it on all of them. My old USB that had 6.8.3 did not do it. But when it died, I moved to this one and it does this now.