jcofer555

i'd say you need to provide much more detail

i'd try removing the plugin, reboot unraid, and reinstall the plugin as a first attempt to fix

public beta is supposed to be within the month from what the newsletter mentioned

that's how the parity building process works. i'm not sure there is any way to avoid it. for why it has to be like that i don't know i just know that's how it is yes parity checks will take longer the bigger the parity drives are. it doesn't matter how much bigger they are than your data drives it's just based on the drive size of your parity drives. the size of the data drives do play a small part of how fast the parity building/checks go as the data drives are involved in the process but if say your parity is 10tb drive and your data drives are 4tb, 6tb, and 8tb, then all 3 drives will be involved until parity has checked up to 4tb then only 2 of the drives involved until the 6tb mark and then only the 1 drive until the 8tb mark and then only parity itself until it's done at 10tb

it should be pretty much the same if you do it either way. if you do it from unraid you can use the unassigned devices plugin to map an smb share from windows by which you'd share your external usb drive from within windows and then connect to it with the UD (unassigned devices) plugin and then you'd have access to those files from within unraid so really it's your choice there.

usually only shares that have appdata on them are set to exclude, i'd confirm there is no appdata on the share at all

q1) move should be fine, i've not personally had any issues with file names messing up with move compared to copy, although i'd suggest copy over move in case something goes wrong during the transfer then you still have the original data. you can install the dynamix file manager plugin to manage data from the unraid webui directly if you need that or install a container like krusader q2) windows capitalization doesn't really matter as you can reference the data by lower or upper case no matter what the actual filenames are set as, with linux case matters so Media and media are 2 completely different folders. the way you deal with this is really how you want things personally and then just point things correctly q3) you can/should use your current share and just point plex to the folders you are wanting the different libraries to be reading from. overall i think you are doing it the correct way and the way that most would do it

this is resolved in 6.13 beta

would be nice to have a keep only so many flash backups when using a seperate folder for the flash backup to go. also a way to not have the flash backup also go in the appdata backup path when you have it set to a seperate folder

having the WARN: Multi mapping detected! message in all my containers even though the paths are different. this is the newest version 2024.02.26

great thanks for the good work you do

it would be great if there was a select all button for the restore templates and restore containers part of the restore process @KluthR

it would be nice if we can re-order the servers in our connect page as right now it seems it's in the order you add them to connect.

parity 2 requires disks to be in the exact same order for parity to remain valid but yes he could have had parity remain valid but it would have been stuck in parity 2 slot adding those restrictions. also thankfully it's only a 6tb drive so parity will re-sync withing roughly 10 hours

with that it's ends up like this