That’s a very reasonable question, and you’re not alone, many users notice similar behaviour at first.
In short, there isn’t really a “driver update” you can apply manually. ZimaOS already ships with the correct kernel and network/storage drivers for supported hardware, and updating them independently isn’t supported or recommended.
In most cases, slower read/write performance on ZimaOS comes from configuration and workload, not missing drivers. A few common things to keep in mind:
First, how the storage is formatted and used matters a lot. SSDs used in RAID, encryption, or certain filesystem layouts can trade performance for safety and compatibility. This can feel slower compared to a bare-metal NAS OS tuned purely for speed.
Second, how data is accessed makes a big difference. Transfers over SMB, Docker volume mounts, and apps running inside containers will always add some overhead compared to local disk benchmarks. If you are testing speed from another device over the network, the network path and protocol often become the bottleneck before the SSD does.
Third, background services and containers can impact I/O. Indexing, media scanning, backups, or multiple containers accessing the same disk at once can make reads and writes feel sluggish even on fast SSDs.
Fourth, network setup is often misunderstood. Even with dual 2.5G LAN ports, you won’t automatically get higher speeds unless link aggregation is correctly configured and supported by your switch and client. Otherwise, performance will be similar to a single link.
What you can do to improve things safely is:
- Make sure you’re on the latest stable ZimaOS release (which you already are with 1.5.3).
- Test disk speed locally versus over the network to identify where the slowdown actually is.
- Check whether heavy apps or background tasks are running during transfers.
- Keep expectations realistic: ZimaOS prioritizes stability, ease of use, and app compatibility over raw benchmark numbers.
So overall, this is unlikely to be a hardware or driver problem, and more about tuning, usage patterns, and understanding where the bottleneck is. If you can share where you notice the slowness most (local copy, SMB, specific apps), it becomes much easier for the community to give targeted advice.