I’m going to have to give this a shot tonight, need to make a pfsense rule to allow the server to get out and then change its DNS. Regarding php, my current config is the following because I have over 64gigs of ram and went through great length to get Nextcloud to cache MORE into ram:

pm.max_requests = 50000 #set higher, the process is recyled after 50k calls to prevent memory leaks
pm.max_children = 1000
pm.start_servers = 60
pm.min_spare_servers = 30
pm.max_spare_servers = 120

So on your Nextcloud server you use an external DNS and it greatly sped up you nextcloud? Because I noticed a few years back mine got slow and I cannot figure out why. It was about the time I enforced pihole dns with pfsense. I might need to try this.

Do you know what it’s idle power usage is? I’m guessing below 10W?

+1 this is exactly my experience. My install must be 5-6 years old at this point and its on the rails. I’ve braved many php updates…

I noticed when they first spin up on boot they do some sub routine and they’re pretty loud and chatty. First time I heard it I was spooked but it worked fine and I just use it for backup so I just moved on. Once it’s on and in normal operation it’s like any other disk I’ve used over the decades. Nothing as loud as an old scsci disk or a quantum fireball.

It’s really boring, Debian 12: /dev/disk/by-uuid/8f041da5-6f7a-4ff5-befa-2d3cc61a382c { spindown_time = 241 write_cache = off }

I have an Exos x16 and x18 drive and they both spin down fine in Debian using hdparm. I use them for cold storage and they’re perfectly adequate.

I’ve been running the Joplin server for over a year with clients on four laptops and three phones and share notes with my wife and its wonderful. There are certainly quirks and sometimes sync issues but by and large I’m really happy with it. There seems to be one cluster of notes I have that always irritates a fresh client sync and it shows up at 50 conflicts but I work through it. Also my notebooks are huge and the first sync can take an hour. It’s a lot slower than I’d expect.

We are almost to the point where its the same cost for SSD. You can get an 8tb drive for $370 now and it won’t always be spinning and wasting 4-7W forever. For me, with high electricity costs, it was a no brainer to get a few of these and they will pay the difference within a year or two. I got them on sale for $320 each.

I think a full resync then re-index will go fine. My setup is different in that I sync everything through Nextcloud and run a script that looks for changes and triggers an indexing scan in photoprism. That being said I’ve absolutely mutilated some photo prism databases (migrating servers, different folder names with the same content) and run full indexing and never ended up with duplicates. It’s very good at stacking and cleaning up the same files in the DB so long as there aren’t actual duplicates in the original storage. But again it might take 3 or more full scans to find and purge duplicates.

I am far from a photo prism expert but I can safely say the indexing algorithm is weird and takes multiple runs to finish. Logically I would expect to run it once and it would do everything in one scan but I’ve found it takes sometimes 3 to 5 full scans to update and properly catch up to major changes. It’s almost like it acknowledges big changes and documents it but waits for multiple passes before committing it. Also it does a really good job when scanning to look or duplicate images and stacking/repointing to the valid file. I would advise running the indexing another 2 or 3 times if you are confident the 31k files are actually on storage and just not showing up on the database.