Check reviews that test writes over ~15 minutes. This kingston holds out the longest but then has a very low floor https://cdn.mos.cms.futurecdn.net/cqJ6pXctEd5BKJVLJN7TCD-1200-80.png

It’s a worst case senario for all drives though, and they will drop in throughtput. Caches run out, heat build up, power supply gets strained, it’s rough.

DRAM-less is fine for the deck. Playing games is mostly large reads and small writes for saves. When writing you’re likely downloading which is going to be the slowest link in the chain. As you saw with this external drive, it could write quickly for 30GB. Getting bigger for less money is gonna be worth it, especially with the limited physical size of a 2230.

The key metric is game load times, which don’t change much even for desktop systems on drives that read 400MB/s or 5GB/s. So don’t worry about it too much.

TLC flash and no DRAM will do that. 😢

Huh annoying. You can run zdb -C TheMass To get more info about the pool and the disks in it. Might list enough disk detail to give you confidence it’s using the layout you want.

For me identifying disks usually ends up being unplugging them one by one and checking which shows OFFLINE. Could be worth the trouble to know for sure its specifying and using the disks.

In any case a good time to setup a backup for anything you can’t replace.

I’m not familiar with ZFS on Linux, but what is 9173635512214770897 referencing? The command is usually zpool replace pool device [new_device] So if you physically swapped out the old disk and put in a new one, you only need to specify the new disk. If you leave the old one plugged it you list both (old one first).

I don’t know what best practice is for specifying disks to ZFS on Linux, but arch wiki suggests not using /dev/sdc, but the ID instead https://wiki.archlinux.org/title/ZFS#Identify_disks

Also you don’t need to offline the pool to replace a disk, you can keep using it as it resilvers.