dada051

You don't have to wait if a drive fails. The failed drive is emulated until the array is fixed

right click on the docker, then "console", and you can do everything you did with the VM. But mine is just updated via docker update, and it's : Docker Tag 2021.10.1 Pi-hole v5.6 FTL v5.11 Web Interface v5.8

Don't know if it's already discussed, but I was not able to get websocket for Live Sync. I added a port mapping to 3012 in Swag (that is my reverse proxy) and it works

Just updated, great work! Thank you

Hi, thanks for your job. A little request maybe? Could it be possible to have a textbox to filter (on-the-fly) the list ? ----------------- In French (because I'm): Serait-il possible d'avoir un champ text permettant de filtrer à la volée les dockers qui ont un nom qui contient la valeur du champ ? Merci beaucoup pour le taf en tout cas

Is it possible to check the update of the docker in combinaison with the template date ? Too costly maybe.

Great. And the list, ordered by update date ?

Why not using unassigned disks for this use ?

+1 NUT native support will be great as it's more flexible and it's support is much better

I have deleted the old bitwardenrs template tio use the new vaultwarden one (but keeping appdata). I'm in 2.19 two. Don't know if it's a bug. After checking https://github.com/dani-garcia/vaultwarden/releases it's normal.

So you lost 500GB. I talking about cache pool, not the array.

You can use cache pool to create a RAID 1 with your 2 1TB disks. But you will be force to add only 1TB disks in this pool after if you want to add disk (and change to RAID 5 or 6). And I find "cache pool" not appropriate for HDD (and for the usage we do with)

Maybe arrays can be tagged as Required or not by the user (default with required), and maybe only for encrypted XFS. Or lot of checks may be required (mapped path used in dockers/VMs...)

I found another use case. One array with xfs, and another with Encrypted XFS. So we can start and use dockers/VM even after a reboot.

I want to create 2 arrays, one with 7200rpm disks, another with 5400rpm. So multiple arrays or at least dual array should be great!

As I said, maybe a change that I forgot.

Is it possible that the plugin can cause crash with "tired" usb flash drive, caused by the add of git. I've deleted the plugin because I've lost my array (not the data) multiple times since I've installed the plugin. No problem without the plugin.

Maybe I'm wrong or I forgot something that I've done, but I changed the "data dir' path in the photoprism docker settings and this morning, I found that it is set to the default one. One thing I am almost sure is that using /mnt/user/ instead of /mnt/cache seems to work well. But it should need more testing

I changed the path. But It has been reset after that change (maybe after the docker update, but I'm not sure). But I used to use /mnt/user/appdata path and it seems to work well.

So I have to rename my cache pool to avoid any problems later ?

Hello, by default, data dir path is bind to /mnt/cache/appdata/photoprism. I changed that but I don't know why, it was reseted. So It has created a new "cache" folder in /mnt because my cache pool are not named cache. It would be great to use /mnt/user/appdata/photoprism because it will use the right cache pool assigned to the "appdata" share

I think we always need th vBIOS, just, it's not necessary to modify it with an HEX editor to use it. But I'm not sure of what I say.

Why "Now if only AMD would make the same gesture... 😉" ? I didn't know that AMD locked the use of pass-through

I have the latest version (and did not change settings since a while) and it paused correctly my monthly parity check wxith a litlle mistake '%%" : [TOWER] Paused 9 hours ago Parity Check Tuning Correcting Parity Check (84.0%% completed)

It was more a joke than anything else. I understand your choice. Thanks for the fix