Raident

I just upgraded to 7.3.1 and got presented with the new setup wizard. As I proceeded, I noticed that it had prefilled a lot of fields... with the wrong data that doesn't match my actual settings in 7.2. Then when I got to the final step, I got a "We couldn't verify current settings from the server. You can still continue, but setup will apply changes in best-effort mode." warning. Needless to say, this doesn't exactly inspire confidence. I ultimately ended up closing the setup wizard, but had I gone through and completed it, would it have screwed up my installation?

The UGREEN LED Driver plugin has a very minor bug. Steps to reproduce: Stop the array Pop out an HDD. The corresponding LED will turn red as expected. Push the HDD back in. Unraid detected that the HDD was back right away, but even after waiting ~10 mins the corresponding LED never turned back to white. This is a trivial matter since rebooting resolved the issue and hotswapping is uncommon to begin with, but I figure that it's better to report it than to not say anything.

I'm thinking of getting a 16GB Optane drive to use as a cache pool. These things are so useless that the AI boom has completely bypassed them, and consequently they can be obtained for dirt cheap. In theory, huge quantities of small files is Optane's best case scenario and also an HDD's worst case scenario, making this a match made in heaven. But can Unraid be configured so that files below a certain threshold (e.g. <1 MB) are written to the cache pool while files above that threshold are written straight to the array?

It seems that Core 0 can't be fully isolated... Now the P-core is idling for about 58-59 seconds per minute, but for some reason Unraid sends a huge burst of unknown activity to the P-core during the remaining 1-2 seconds. And judging by how CPU temps actually spike during that brief period, it doesn't seem to just be a phantom reading:

My NAS has a Pentium Gold 8505. This is Alder Lake 1P + 4E. For power and cooling reasons, I want to isolate/turn off the P-core and transform it into a pseudo-N100, but I've heard that isolating Core 0 (which is my P-core) is bad as that's where Unraid runs its core services...

It's clearly not CPU load - top is in agreement with Overall Load. It's not temperature either - sensors indicate that my CPU is running at ~43c.

Can you expand more on the data recovery aspect? I had thought that if I provide the encryption key to the technician working on the drive then it should be no more difficult than recovering data from an unencrypted drive, but perhaps that was naive of me? [Edit] To answer your question, I don't have a particularly strong reason for wanting encryption - it simply makes disposing of an old/dying/dead drive simple and hammer-free.

I'm in the process of setting up a new array, and I'm wondering if there's any reason to a) use a filesystem other than XFS and b) not use encryption

I'm trying to figure out the best way to move Unraid from an old (Nehalem-based) system to a brand new DXP4800 Plus, while simultaneously moving from Unraid 5 to 7. I'm thinking the cleanest way to do this would be to take the parity disk from the old system and format it as a data disk in the new system, then copy the data from disk 1 on the old system to the former parity disk, then move disk 1 from the old system to the new system and copy the data from disk 2 to disk 1, and repeat this process until all the disks are migrated and use the final data disk as the new parity disk, but before I do anything I figure it doesn't hurt to ask: is there a better migration strategy?

Wow, this is everything I was looking for, and then some! Thanks I'll try it out when I have time this weekend and let you know how it goes.