Michael_P

Run it from the docker's console Hint: ignore the dot slash and just run occ preview:generate-all -vvv

Why can't I put 10lbs of crap in a 5lb bag? Not enough room.

Edit the script for whatever you need, examples are provide in the script near the beginning marked ##Settings##. Add the script via the user scripts plugin and from there you can set triggers (array start, on specific unassigned device plugged in, etc.) Dunno about the others you mentioned or whether they're bettor or not, you asked if it was possible and it is

Yes, but it would be better just to not use the cache drive for the share while you're doing your copy

That's the rub, if it's just fill and read - there's no need to 'work' with the files so any space left over is simply wasted. 50GB over 24+ drives really adds up

This is wrong. There's no benefit in a write once read many use case to leave 20% of it's capacity un-used, where fragmentation isn't a thing. Fill'er up.

SMART is an internal test, so the cable wouldn't matter. If it fails SMART, it's dead Jim

'Disabled'

Yep

Word on the street is they're making their own NAS solution?

Post your diagnostics or it'd just be a WAG

They said already 8x 8TB Sabrent Rocket 4 Plus Pretty much best of the best

Forward the ports on your router or use a reverse proxy

Could try taping the 3.3v pin on the drive, or use a molex to sata power adapter that doesn't carry the 3.3v wire.

Make sure anything writing to disk in your docker container is mapped correctly to an actual disk/share or it'll write to the docker image instead

Is it a shucked drive?

Subsonic / Airsonic is my vote

I made my own using this style connector by adding them to unused SATA power cables that came with the PSU. Simple enough, and you can add as many as you need. https://www.moddiy.com/products/DIY-IDE-Molex-Power-EZ-Crimp-Connector-%2d-Black.html

Try to keep at max 4 per connector, avoid splitters (use crimped style connections, not molded, if you absolutely must) and definitely add another run to the PSU if at all possible. I've found Toshiba drives to be particularly sensitive to voltage sag when too many drives are on one connector

You need to switch from basic to advanced view Which will show you additional fields

Extra parameters line (in advanced settings for the docker container) --memory=4G That will limit the docker to 4GB before restarting the container (you can change to whatever you want to limit it to)

Plex can suck up a lot of RAM when doing its maintenance (very quickly), so best to limit all dockers to an amount well below your total free

Use Plex?

Jan 8 17:22:46 Plex kernel: pcieport 0000:00:03.1: AER: Multiple Corrected error received: 0000:00:00.0 Jan 8 17:22:46 Plex kernel: pcieport 0000:00:03.1: PCIe Bus Error: severity=Corrected, type=Data Link Layer, (Receiver ID) Jan 8 17:22:46 Plex kernel: pcieport 0000:00:03.1: device [1022:1453] error status/mask=00000040/00006000 Jan 8 17:22:46 Plex kernel: pcieport 0000:00:03.1: [ 6] BadTLP Jan 8 17:22:49 Plex kernel: pcieport 0000:00:03.1: AER: Multiple Corrected error received: 0000:00:00.0 Jan 8 17:22:49 Plex kernel: pcieport 0000:00:03.1: PCIe Bus Error: severity=Corrected, type=Data Link Layer, (Receiver ID) Jan 8 17:22:49 Plex kernel: pcieport 0000:00:03.1: device [1022:1453] error status/mask=00000040/00006000 Jan 8 17:22:49 Plex kernel: pcieport 0000:00:03.1: [ 6] BadTLP Jan 8 17:22:50 Plex kernel: pcieport 0000:00:03.1: AER: Multiple Corrected error received: 0000:00:00.0 Jan 8 17:22:50 Plex kernel: pcieport 0000:00:03.1: PCIe Bus Error: severity=Corrected, type=Data Link Layer, (Receiver ID) Jan 8 17:22:50 Plex kernel: pcieport 0000:00:03.1: device [1022:1453] error status/mask=00000040/00006000 Jan 8 17:22:50 Plex kernel: pcieport 0000:00:03.1: [ 6] BadTLP Guessing it's your 1070 reacting badly to ASPM, just a guess tho

Your video card is sh*t'n all over your log, too