Unable to Print GCode files

General Discussion
9

Post a new klippy.log, please.

TBH, I’m not sure how KIAUH would handle this. There are multiple files involved, all across the Linux system, that contain path information. It requires some in-depth Linux knowledge to check and backtrack all of them.
The safest approach would be:

  1. Backup your printer.cfg
  2. Provision a new SD card with a fresh Linux
  3. Update Linux and potentially fix the systemd bug as per Debian Bullseye Bug causing Klipper to no longer find the printer board
  4. Create a new user that you want to use for Klipper or use the default one (recommended)
  5. Use KIAUH to install everything, under the user that you want
  6. Restore your printer.cfg

Edit:

I hope you are aware that Linux is a case-sensitive operating system. So ~/Printer_Data/Gcodes and ~/printer_Data/gcodes are different paths

Edit 2:

[virtual_sdcard]
path: ~/printer_data/gcodes
on_error_gcode: CANCEL_PRINT

Your mainsail.cfg also includes a [virtual_sdcard] section. Working with includes is nice to keep things tidy but poses a high risk of creating unwanted effects. Klipper will take the last statement that it processes, i.e. in the sequence as given in the printer.cfg