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