apandey

Typically, modern encryption is next to impossible to break unless the keys are compromised. If that was not the case, I would be hesitant to keep my money in banks which allow moving money online. I think your attempt to break encryption is wishful thinking unless this particular attack itself has a vulnerability. Maybe other security related forums will give you a better answer, this isn't an unraid question and people here may not be experts on what you are asking anyway

cp /mnt/user/"First Location"/"Rick And Morty (2013)"/* /mnt/user/"Second Location"/"Rick And Morty (2013)"/

Those seem like plug-ins that need updates, but cannot since the usb flash drive is broken

I see this in your syslog Mar 27 20:11:47 Tower kernel: i915 0000:00:02.0: Your graphics device 4c8b is not properly supported by the driver in this Mar 27 20:11:47 Tower kernel: kernel version. To force driver probe anyway, use i915.force_probe=4c8b Mar 27 20:11:47 Tower kernel: module parameter or CONFIG_DRM_I915_FORCE_PROBE=4c8b configuration option, Mar 27 20:11:47 Tower kernel: or (recommended) check for kernel updates. It's possible the later kernel in upcoming unraid 6.12 has support for 11th gen. You can wait for that or try the suggested kernel parameter

Haha, yes. My point was pre clearing should not succeed in this situation. Keen to see the result

You don't have to, as long as you have pointed to containers to /mnt/user/appdata, which is the share path. You just have to have the correct cache setup in respective share settings

Usually it's a good idea to keep system, appdata and domains on cache. You should stop docker and VM services before you move data, as open files cannot be moved

If you can successfully pre clear it without errors, I guess there is no need to RMA it then. That proves you can write to the whole disk ok 🤔

Maybe post diagnostics, would be good to see what happens on loading quicksync driver Intel graphics is enabled in BIOS I presume?

You can add a cache pool with ssd drive, then mark the appdata share as cache only. Then stop docker service and run mover and all appdata will be moved to cache drive. Your appdata needs to fit on your cache ssd You can add a 2nd ssd of same size to the pool if you want a raid1 redundebcy on your pool If running with a single ssd in cache pool, you can setup CA backup plugin to maintain a daily backup of cache on the array

Ah, interesting. I didn't know there is a JBOD mode

Not as a part of same pool. You can always use it as a separate single disk pool if you want different cache pools for different shares

No, but system stability is not guaranteed with xmp enabled Try running memtest86 with xmp enabled and see whether your system is stable

Multi device pools can only be btrfs raid, and you cannot mix drives of different sizes

Just to be clear When booting, use normal option (not gui). If that works, you will end up at unraid login prompt on attached monitor. There should be IP address just before that. You can login at the text prompt as root user and type in diagnostics after you log in. The zip will be saved to usb boot drive To access web ui, you will be going to http://unraid-IP from a browser on a computer on same network as unraid. I presume that is what you are trying. What do you see when you do so? Can you ping unraid IP on network?

Looks like it booted. Have you tried going to http://unraid-ip from a browser on another computer in your network? The IP would be shown right before the login prompt

I think you should first fix your flash drive. Those errors on sda probably mean your flash drive is broken, so settings changes or any updates cannot be written there

Where are you doing it. I also have a MX500 ssd, and I have pending sector warning disabled in disk settings For RC, you need to select Next channel instead of Stable channel in settings. That will offer the RC. Or Do you mean it's offered but you cannot upgrade because of incompatible plug-ins?

It is possible that mce logs something which may be a non-issue for AMD processors. The only mce logs I see in your logs are at processor initialization. It may be harmless Is there any adverse effect you see except for that error? To be safe, maybe you can run a long memtest86 session to rule out any cpu/mem issue

Log is maintained in ram, so it will be discarded on reboot. You still need to see if there is excessive logging from any plugin that might lead to same situation again over time. Do you still see those error messages flooding your syslog?

Let's go with yours in this case. I just want us to be 6.12 ready @Squidwhat is the go forward here? What needs to happen to put this in CA instead of the blocked version

I see sdb is a crucial ssd. Are those notifications SMART errors like these by any chance?

thanks @Squid, @itimpi, @SimonF - those pointers helped specifically, I was looking to take a stab at corsairpsu plugin since the current maintainer isn't free to update it for 6.12, but the real deal is that I wanted to learn something and get familiar with the system in general. This looked like a good opportunity For now, I just ran it on a NUC with a trial USB. For occasional dev effort (which is probably all I have time for right now), I guess trial would work, 12 USB a year isn't too expensive if all I am doing is booting occasionally for throwaway environments. If I get more serious, I can get a dedicated license later. The bigger issue is mimicking the hardware. In this case, I mocked the corsair API output to test, so I think it will depend on what I want I have something to show for this weekends attempt here, hope its useful:

@Fma965 / @giganode, I also have a seemingly working version here: https://raw.githubusercontent.com/ashishpandey/corsairpsu-unraid/master/corsairpsu.plg I have limited hardware to comprehensively test this, so if there is interest, can someone else try this and see if it works. All feedback welcome Happy to contribute my changes to another repo, or to let CA point to my repo. I will be happy to take contributions too going forward. I just want the plugin to not hot a dead end with 6.12

pool to pool cache isn't part of 6.12, but a later release might have it. see here