Differences

This shows you the differences between two versions of the page.

--- gcode_storage [2024/10/18 13:57] – [GCode storage] torte
+++ gcode_storage [2025/01/21 12:27] (current) – torte
@@ Line 1: / Line 1: @@
-===== Sovol KlipperScreen =====
+{{page>redirect#this_wiki_has_moved}}
-==== GCode storage ====
+https://torte71.github.io/InsideSovolKlipperScreen/gcode_storage.html
+{{page>redirect#section}}
+----
+===== Sovol KlipperScreen (Makerbase MKS KLIPAD50) =====
+==== Expand G-Code storage space ====
+Experienced Linux users: Scroll down to [[#for_the_linux_gurus|For the linux gurus]] for a short sum-up what is required.
+----
 Sovol's KlipperScreen uses an 8GB emmc card for storage, of which about 7GB are used by the system.
@@ Line 126: / Line 135: @@
 If everything is OK, power off the device, insert the usb-drive again and power it up.
 We are done.
+=== Things to keep in mind ===
+  * From now on, the automounter will ignore this specific drive (because it is managed by the system, the ''/etc/fstab'' file)
+  * All other usb-drives will be used by the automounter as before, i.e. they will be mounted as a subdirectories "USB" under the "gcodes" directory
+  * Only remove the usb-drive after shutting down the device
+  * If the usb-drive was not plugged in during boot, you will either have to mount it manually (''sudo mount /home/mks/printer_data/gcodes'') - or just reboot the device with the usb-drive plugged in.
+  * By default, you cannot access the files on the usb-drive by Windows. But there are several free programs that allow it (e.g. SysInternals LinuxReader or Ext2explore), just search the web for "windows ext4".
+=== For the linux gurus ===
+  * Set the partition type to "83 linux".
+  * Format the partition to "ext", e.g. ext4 (a filesystem with linux access rights is required).
+  * Make sure to unmount after each step (automounter is still active)
+  * In ''/etc/fstab'' use the parameters ''nofail,x-systemd.device-timeout=9'' to allow booting if that drive is not inserted
+  * Use the partitions UUID in ''/etc/fstab'', this makes the automounter ignore this drive
+  * Make the filesystem writable for users (''chown -R mks:mks <YOUR_MOUNTPOINT>'').
+=== A last tip ===
+When there is no usb-drive inserted, create a directory called "_NO_USB_MOUNTED_" (or whatever name you like) in the gcode directory. If the usb-drive is not inserted or broken, this directory will be visible and you know, that gcode files will not end up on the usb-drive, but on the internal file system.