Henry Thomas

Thanks Frank, I found the problem. I will also follow up on setting up a user.

poking around here, I only see I have 'root' as a defined user on the user tab. I did try to copy write security on the SHARES tab over on the column on the right for "write settings to" and that didn't help. I'm not even sure what my "Microsoft Windows login" user ID is to be honest. When I upgraded to Windows 11 I gave in to the stupid "Microsoft user" instead of continuing on with "Local User." I have resisted that for years and now regret the change. Anyway, with an email address of [email protected] my documents directory is telling me my user ID is volks (I think?)

I have several shares, all but one I can write to from Windows 11. The error is "you need permission to perform this action." I ran Docker Safe New Perms on the folder and received Processing '/mnt/disk1/TV' Processing '/mnt/disk2/TV' Processing '/mnt/disk3/TV' Processing '/mnt/disk4/DVR' Processing '/mnt/disk4/TV' Processing '/mnt/disk5/TV' Processing '/mnt/disk6/TV' Finished! But no change.

This is just a rant, I have to rant somewhere and my friends won't get it. I took my 8 drive (2 parity) server down to replace 1 data drive that is on life support. The 1 data drive has 196 re-allocated sectors. When I replaced that 1 drive, I could never get the RAID to start. Of course, I suspected loose cables ... after two hours of jiggling, replacing, rejiggling, firmly pushing, rebooting ... the unthinkable hit me. What if another drive refused to power up? And that's when it got interesting. TWO refuse to power up after a normal shutdown. No SMART errors. So now I have two replacement hard drives in, parity rebuilding (one of the two that refused to power up was a parity drive.) And the drive that's on life support is still in there. I'll have to replace it next (duh.) I can scarcely believe this happened. The odds are so rare it was last on my list of items to check .. and cost me about 3 hours of my Friday night

It's been stable overnight. I am ripping a bluray now and I swear it's faster than with the SSD unplugged. I'm theorizing I had two issues - one the edit to the "go" file. Lessons learned - read the release notes carefully. I always do but I think when I processed that I translated it into "optional" or something because I've never had to edit a file like that on an incremental upgrade - ever. Second issue - flaky SSD. Is the cache drive supposed to be THAT much faster than a non-cache drive? I'm not using a stopwatch but I'm not noticing much or any difference. Perhaps that's due to the drive being flaky - OR is it because Ryzen has faster throughput to the array? Any thoughts?

that's because I unplugged it because after the crashes it was always 'unmounted' so I suspected it as being a culprit (crashed once since I unplugged it.)

Anyone see a reason why I can't plug my SSD back in? Diagnostics in first post unRaid_Syslog

Fix Common Problems says "Your server has issued one more more call traces. This could be caused by a Kernel Issue, Bad Memory, etc. You should post your diagnostics" ok

DUH. I got it. It looks like an override in case the BIOS gets flipped but I'm up for anything. Booting .... It keeps kicking my cache drive off as "unmounted" so I've just physically disconnected it.

Yeah, c-states are off, but I skipped over that script edit. I have no idea how to get to that file. I installed notepad++ but that file isn't on the flash drive at least plugged into a windows laptop. Can I get to this file from a windows laptop from the server? I always get stuck here.

It was disabled because I was fiddling with VM. But I did hit 'default' button last night. I'll check that but I don't think that's going to be it. But I'll check / reboot right now.

Crashes in about 4 hours. 6.4.1 most recent version. One time it crashed, Parity Disk 2 was 'not assigned' but it did reassign. Yesterday it crashed, the cache drive SSD was unassigned. It did reassign. I do see CRC errors and I've tightened the cables but to no effect on crashing. unraid-diagnostics-20180215-1853.zip

USB is merely the sandisk used that holds unRaid. Only USB I'm passing through is keyboard/mouse on a combo Logitech htpc keyboard. --It's not really "usb sound stuttering" it's "all sound stuttering" not related to USB. Regardless, it's all hung on Error 43 now with USB:SANDISK as boot, instead of UEFI:SANDISK that was the prior setting.

I think I found it. I changed SANDISK from UEFI to USB. Error 43 gone. Until I went to use the sound. Sound didn't play, was very stuttering and videos playing at 1/2 speed. I did a reboot just wondering if there were some updates sitting around plus I had done some basic Kodi setup. Upon reboot the server completely locked up. So upon main reboot I completely disabled any device that said UEFI boot and made sure USB:SANDISK was the only option. Back into the VM, error 43

Thanks. is the trick to this renaming EFI on the USB to EFI- as I read here I'm not seeing anything in the BIOS to tell it to use Legacy I wonder if this ASRock TaiChi is UEFI only

I don't see 'boot type' in the bios. I found how to look at partitions from within WIndows but not Unraid. It's an ASRock Taichi. It definitely is UEFI when I go into BIOS to check. Since I can't find it, I don't know how to change it. I do see Boot Override and it says UEFI:SanDisk, Partion 1 which is my Unraid OS for sure.but there are no options to change it really. I see "Launch EFI SHell from filesystem device" but that gives me a Shell> that lists boot devices but it doesn't list UEFI or Legacy options

I am stuck on the infamous Error 43. I had the system working WITHOUT error 43 somehow yesterday but the entire server would crash. First I'd see a blue screen "internal video scheduler error" then during the dump the entire Unraid server would crash - and not reboot automatically. So I fiddled a little bit with reinstalling the driver, running the sfc command as admin cmd ... to no avail whatsoever. Then I'm back to Error 43. I have tried Hyper-V on and off, and I have tried SR-IOV on and off IOMMU of course is enabled. So today I tried a different version of the ROM. The entire server no longer crashes. I was had a perfectly working video card ... until Windows Activation triggered after a few reboots. Error 43 reappeared. I'm afraid to keep activating Windows because if I wind up changing BIOS and reinstalling Windows it looks like I'm using the same license over and over. I don't know what to do next This is a Ryzen 5 system / Nvidia 1050 Ti / ASRock Taichi 3.30 BIOS

I am stuck on the infamous Error 43. I had the system working WITHOUT error 43 somehow yesterday but the entire server would crash. First I'd see a blue screen "internal video scheduler error" then during the dump the entire Unraid server would crash - and not reboot automatically. So I fiddled a little bit with reinstalling the driver, running that sfc command as admin cmd ... to no avail whatsoever. Then I'm back to Error 43. I have tried Hyper-V on and off, and I have tried SR-IOV on and off IOMMU of course is enabled. I did dump a rom and am passing it through successfully (if I make a typo or whatever I just get a black screen as opposed to at least move around in WIndows.) I don't know what to do next This is a Ryzen 5 system with Nvidia 1050 Ti

I'm seriously considering Backblaze. I need to buy another hard drive for my backup server - but why should I do that and not just put it into the cloud? I'll get over my fear of putting my tax forms up there - but I do worry about blu-ray rips. Grey area. I own all of them, they're sitting in my file cabinet in the media room. But they're ripped. I'm a little more paranoid that someone is going to notice and cause me trouble.

The problem wound up being a BIOS battery that wasn't fully inserted so the setting wasn't saved. Gosh, so much time spent figuring that out, lol. Figure I'd post a response for anyone else wondering what's going on.

I did have a nice VM running with an Intel Kaby Lake, but that's over on another server. I thought a Ryzen 5 would be a great low-power VM CPU. But with Windows 10 no matter what I try I am getting Execution error unsupported configuration: Domain requires KVM, but it is not available. Check that virtualization is enabled in the host BIOS, and host configuration is setup to load the kvm modules. Now, info tells me this: HVM: Disabled IOMMU: Enabled I think I need a little push here...

With the complete lack of privacy on the internet any more with some of the recent administrative changes with ISPs and such, I'm really uncomfortable sending my entire life up to the cloud from tax documents to photos to videos to comic book database, bank records, etc. I desire to stay computer -> computer. You guys all fine and dandy with sending everything up to some server somewhere? Encrypted or not. Maybe I'm being paranoid and I'm willing to re-evaluate. Or do we just throw our hands up in the air and say there's no privacy any more with facial recognition once you walk outside your house and just not worry any more?

Usually less than 24 hours my server is locking up. I have 16GB in a Ryzen 5 1600 system / Taichi X370. I am in the process of backing up about 30TB through Crashplan to a Windows 10 server. I thought that memory settings may be the issue so I've increased allocated memory to 8GB. The LOG button only displays what's happened since the last boot. I don't know how to wade around through the various files to find the prior logs to see if there's a clue as to what may be causing the lockups. I can wade through my shared drives but getting to the other system files on the Flash drive or any other non-share drive is a skill I don't yet have.

Frustrating; restricts me from a lot of the functionality I wanted from an HTPC VM with new technology. It's a Kaby Lake with iGPU but I'm passing an Nvidia 1050 through for now until they fix the Kaby Lake display drivers Here's the XML. Hyper-V no or yes doesn't matter. <domain type='kvm'> <name>Windows 10</name> <uuid>80c35966-7e48-6323-aa06-be1d3ece4126</uuid> <description>W10VM</description> <metadata> <vmtemplate xmlns="unraid" name="Windows 10" icon="windows.png" os="windows10"/> </metadata> <memory unit='KiB'>8388608</memory> <currentMemory unit='KiB'>8388608</currentMemory> <memoryBacking> <nosharepages/> </memoryBacking> <vcpu placement='static'>2</vcpu> <cputune> <vcpupin vcpu='0' cpuset='0'/> <vcpupin vcpu='1' cpuset='1'/> </cputune> <os> <type arch='x86_64' machine='pc-i440fx-2.7'>hvm</type> <loader readonly='yes' type='pflash'>/usr/share/qemu/ovmf-x64/OVMF_CODE-pure-efi.fd</loader> <nvram>/etc/libvirt/qemu/nvram/80c35966-7e48-6323-aa06-be1d3ece4126_VARS-pure-efi.fd</nvram> </os> <features> <acpi/> <apic/> <hyperv> <relaxed state='on'/> <vapic state='on'/> <spinlocks state='on' retries='8191'/> <vendor_id state='on' value='none'/> </hyperv> </features> <cpu mode='host-passthrough'> <topology sockets='1' cores='2' threads='1'/> </cpu> <clock offset='localtime'> <timer name='hypervclock' present='yes'/> <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/domains/Windows 10/vdisk1.img'/> <target dev='hdc' bus='sata'/> <boot order='1'/> <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/isos/Windows.iso'/> <target dev='hda' bus='ide'/> <readonly/> <boot order='2'/> <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/isos/virtio-win-0.1.126-2.iso'/> <target dev='hdb' bus='ide'/> <readonly/> <address type='drive' controller='0' bus='0' target='0' unit='1'/> </disk> <controller type='usb' index='0' model='nec-xhci'> <address type='pci' domain='0x0000' bus='0x00' slot='0x07' function='0x0'/> </controller> <controller type='pci' index='0' model='pci-root'/> <controller type='ide' index='0'> <address type='pci' domain='0x0000' bus='0x00' slot='0x01' function='0x1'/> </controller> <controller type='sata' index='0'> <address type='pci' domain='0x0000' bus='0x00' slot='0x03' function='0x0'/> </controller> <controller type='virtio-serial' index='0'> <address type='pci' domain='0x0000' bus='0x00' slot='0x04' function='0x0'/> </controller> <interface type='bridge'> <mac address='52:54:00:1c:41:45'/> <source bridge='br0'/> <model type='virtio'/> <address type='pci' domain='0x0000' bus='0x00' slot='0x02' function='0x0'/> </interface> <serial type='pty'> <target port='0'/> </serial> <console type='pty'> <target type='serial' port='0'/> </console> <channel type='unix'> <target type='virtio' name='org.qemu.guest_agent.0'/> <address type='virtio-serial' controller='0' bus='0' port='1'/> </channel> <input type='mouse' bus='ps2'/> <input type='keyboard' bus='ps2'/> <hostdev mode='subsystem' type='pci' managed='yes'> <driver name='vfio'/> <source> <address domain='0x0000' bus='0x01' slot='0x00' function='0x0'/> </source> <rom file='/mnt/user/domains/VBIOS/GP107noheader.rom'/> <address type='pci' domain='0x0000' bus='0x00' slot='0x05' function='0x0'/> </hostdev> <hostdev mode='subsystem' type='pci' managed='yes'> <driver name='vfio'/> <source> <address domain='0x0000' bus='0x01' slot='0x00' function='0x1'/> </source> <address type='pci' domain='0x0000' bus='0x00' slot='0x06' function='0x0'/> </hostdev> <hostdev mode='subsystem' type='usb' managed='no'> <source> <vendor id='0x046d'/> <product id='0xc52b'/> </source> <address type='usb' bus='0' port='1'/> </hostdev> <hostdev mode='subsystem' type='usb' managed='no'> <source> <vendor id='0x8087'/> <product id='0x07dc'/> </source> <address type='usb' bus='0' port='2'/> </hostdev> <memballoon model='virtio'> <address type='pci' domain='0x0000' bus='0x00' slot='0x08' function='0x0'/> </memballoon> </devices> </domain>

I fixed it myself. I plugged the keyboard into a different USB port. I'm so smart. LOL.