hostinglinks.
PRACTICAL TECH, EXPLAINED

STORAGE HARDWARE

SSD vs HDD for a home server

Separate the small, frequently accessed application files from the large media collection. A mixed layout can suit a home server better than placing everything on one expensive type of storage.

Editorial update: 24 October 2026. The layout below is an invented planning example, not a benchmark or a tested configuration.

Start with what the software needs

Immich’s current requirements recommend a local SSD for PostgreSQL data and say not to place that database on a network share. Jellyfin distinguishes media storage from its own application files, recommending SSD storage for the latter. Those requirements do not mean every photograph or film must live on SSD.

Read the current Immich requirements and Jellyfin hardware guide before designing a particular installation.

A mixed-layout example

Assign roles before choosing drive capacities
RoleExample locationWhat to budget for
Operating system and applicationsLocal SSDUpdates, containers, logs and spare working space
Database and active indexesLocal SSDSoftware-specific storage and backup requirements
Bulk photos and mediaLarger HDD storageOriginal files, new additions and generated files
Independent recovery copiesSeparate backup destinationFiles, database exports, configuration and retained versions

Decide exactly which folders live in each place. Otherwise a database, transcode cache or container volume may end up on a small system drive unintentionally. Check the application’s path settings after deployment.

Capacity: leave room for growth

Suppose a made-up collection is 2 TB and grows by 300 GB a year. After three years it reaches 2.9 TB before thumbnails, versions, temporary work or backups. A nominal 3 TB destination would leave very little room. The appropriate size depends on those additional requirements and usable filesystem capacity, not just the current original-file total.

Use consistent units when comparing the collection and drive. A drive label, formatted capacity and application storage report may use different GB/GiB conventions. Mirroring or parity also changes usable capacity; our NAS capacity planner separates layout and reserve assumptions.

What actually feels slow?

Separate loading a large file from lots of small database operations. A slow library scan can involve CPU, storage, database or network limits. Check which resource is busy during the problem before assuming an SSD upgrade fixes it.

For a mini PC using external drives, check enclosure power, connection reliability and the recovery process after a disconnect. Keep application paths stable and avoid relying on one loose cable for the only copy of important files.

Test recovery before adding more data

  1. Identify which files, database data and configuration are needed to rebuild the service.
  2. Use the application’s documented backup method, including any consistency requirements.
  3. Restore a small test into a separate location and confirm the application can read it.
  4. Keep another copy away from a failure that could affect the server and its attached disks together.

A mirror may help after a disk fails, but it does not undo a mistaken deletion. A fast drive does not replace a recovery plan.