WHAT TO DO IF YOUR ROON DATABASE SIZE IS TOO BIG FOR RAM MODE OR FOR DRIVE SIZE

Roon Database can be huge.

This how-to can be applied in these cases:
1) Drive space is insufficient because you did not resize the ext4 partition after installation.
2) Ram size is not enough for booting in ram mode

1) Be sure that the ext4 partition is covering the full drive and the drive is at least 32 GB

An operation like this can be made from "outside" if you are booting normally or from "inside" if you are booting to ram.

* If you are booting in normal mode

1) Make a second USB stick with audiolinux lxqt installed
2) Boot from this new installation
3) Attach the original USB installation drive only when boot process is finished
4) Launch gparted, where you can resize the partition (please be sure that the original installation is un-mounted, you can do it eventually from gparted)

* If you are booting in ram mode

Lxqt version:
Use gparted as reported above

------------------------

Headless version:
First type (as root)
fdisk -l
to discover what is the address of your audiolinux ext4 partition.
For example, if the output is

Device       Start      End  Sectors  Size Type
/dev/sde1     2048  1001471   999424  488M EFI System
/dev/sde2  1001472 12265471 11264000  5.4G Linux filesystem

You can use /dev/sde in parted
Example:

[root@archlinux audiolinux]# parted /dev/sde
GNU Parted 3.2
Using /dev/sde
Welcome to GNU Parted! Type 'help' to view a list of commands.
(parted) print                                                          
Warning: Not all of the space available to /dev/sde appears to be used, you can fix the GPT to use all of the
space (an extra 58440158 blocks) or continue with the current setting?
Fix/Ignore? f                                                           
Model: SanDisk Ultra USB 3.0 (scsi)
Disk /dev/sde: 30.8GB
Sector size (logical/physical): 512B/512B
Partition Table: gpt
Disk Flags:

Number  Start   End     Size    File system  Name  Flags
 1      1049kB  25.9MB  24.9MB  fat16        EFI   legacy_boot, msftdata
 2      26.2MB  831MB   804MB   ext4         root

(parted) resizepart                                                     
Partition number? 2                                                     
End?  [831MB]? 100%                                                     
(parted) print                                                          
Model: SanDisk Ultra USB 3.0 (scsi)
Disk /dev/sde: 30.8GB
Sector size (logical/physical): 512B/512B
Partition Table: gpt
Disk Flags:

Number  Start   End     Size    File system  Name  Flags
 1      1049kB  25.9MB  24.9MB  fat16        EFI   legacy_boot, msftdata
 2      26.2MB  30.8GB  30.7GB  ext4         root

After typing quit to exit parted, disconnect and re-connect the USB stick if the output of
fdisk -l
does not show it
(after gparted command it happens sometime)
and  be sure is not mounted

Run
e2fsck -f /dev/sde2

Allocate the space in the extended partition:
resize2fs /dev/sde2

2) Upgrade your computer to 32 GB ram or store the Roon database on another drive.

The new drive (possibly formatted with ext4) must be mounted at boot editing /etc/fstab
See the guide here: http://www.audio-linux.com/html/mount.html

Please make this in normal mode (not ram mode). If you have enabled ram mode answer N to the boot prompt.

Now let's copy the Roon database folder to the new drive (in this example the drive is mounted to /media/linux1)

Open a root terminal and type
cp -R /var/roon/RoonServer/Database /media/linux1
... check that the copied files are in /media/linux1/Database, in case of a mistake in typing...
Once you have copied the files you must delete the original folder
rm -rf var/roon/RoonServer/Database
and link the new location to the old one
ln -s /media/linux1/Database /var/roon/RoonServer
Check that all is right with

ls -l /var/roon/RoonServer
you should have something like this:
lrwxrwxrwx 1 root root    21 Nov 20 11:21 Database -> /media/linux/Database

This way only the Roon database will be stored in the second HDD and this configuration will persists after a Roon update.

IMPORTANT: if you will use audiolinux as new Roon core installation, I suggest to rebuild the database from scratch. You will probably have to reconfigure your Roon endpoints.