Hi everyone,
I have an old spare notebook (hp pavilion 2120 el, 6Gb of ram, intel processor of 2° generation, 500 Gb of storage) and I would like to use it for a hybrid solution,i.e. a zorin installation and a server. I have checked with the forum of openmediavault, and this should possibile in double form. Install omv7 on usb stick and install zorin core 17.3 on the hd. I would then give 400 Gb for a data partition (ext4), which should be readable from the installed nas (debian-based). Alternatively, I should install first omv7, shrink it to 30 Gb, then install alongside zorin in sda2 of 70Gb, and leave the 400 Gb for the data in sda3. An external hd of 16 Tb will be provided for additional storage. Now my question is: how much space does actually a basic zorin installation require? Data would be stored in the data partition and in the external hd. Thanks a lot
There is no newer information about system requironments of Zorin 17.3. This is from july 2024. When you have 70 GB for Zorin, it is enough. I think Zorin 17.3 Core uses about 25 GB. When you install Zorin lite it needs a litte bit less.
`Minimum hardware specifications
These are the minimum hardware specifications required to install Zorin OS on a computer. If your computer doesn’t meet these requirements, you might not be able to run Zorin OS on it.
CPU: 1 GHz Dual Core – Intel/AMD 64-bit processor
RAM: 1½ GB
Storage: 15 GB (Core), 32 GB (Education), or 40 GB (Pro)
Display: 1024 × 768 resolution'
A base install doesn't take much but then you have to account for additional software that you want to install, and other things like personal files, backups, etc. In particular, you want to watch out for Flatpak and Snap packages which take a lot more space than the usual Debian package format.
You can get away with very little, but for the casual user I wouldn't go below the 100GB partition. Note that it's much easier to shrink a partition than it is to expand it; start with a generous margin to assess your needs over a reasonable period of time, and adjust as needed.
From the server perspective, keep in mind that long-running processes may produce a lot of logs that pile up over time. If there's a problem and the process misbehaves but tries to restart itself, it may end up in a endless loop that fills your drive with massive log files if you are not careful.