Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Moonraker warnings found. Supplied path (/home/moonraker/gcode_files) for (gcodes) is invalid. Make sure that the path exists and is not the file system root. #37

Closed
Sail2019 opened this issue Sep 13, 2022 · 5 comments

Comments

@Sail2019
Copy link

No description provided.

@mkuf
Copy link
Owner

mkuf commented Sep 13, 2022

Please provide a Description to your issue.
Describe your exact setup and what you attempted to achieve.
Also run scripts/get-infos.sh and attach the generated archive to your response.

-Markus

@chvm-by
Copy link

chvm-by commented Sep 13, 2022

I have the same error in the interface on the web right after installation. I solved this problem by adding lines to the printer.cfg file:

[virtual_sdcard]
path: ./gcode

@mkuf
Copy link
Owner

mkuf commented Sep 15, 2022

[virtual_sdcard]
path: ./gcode

Thats not wrong, but it also does not really make sense.
The workingdir for the klipper image is /opt, where the gcode volume is mounted in /opt/gcode.
So it happens to work that you can specify the relative path ./gcode without getting an error.
The existing config sets the absolute path for the gcode directory. So in the end, the location is the same.

prind/config/printer.cfg

Lines 14 to 15 in 3f5b5ec

[virtual_sdcard]
path: /opt/gcode

I verified this in a local debugging stack and I do not get any Warnings in Moonraker or (in my case) Mainsail.
I'd be happy to get to the core of this issue, but I need more infos about your setup and the support archive that is generated by the above mentioned script.

-Markus

@mkuf
Copy link
Owner

mkuf commented Sep 21, 2022

Any Updates on this? @Sail2019

@mkuf
Copy link
Owner

mkuf commented Sep 27, 2022

Closing, as this is missing information for debugging.

@mkuf mkuf closed this as completed Sep 27, 2022
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

3 participants