Repeated issues with "no suitable storage found" when trying to send gcode to mk4 over LAN

[tverett]

Description of the bug

70-80% of the time since using 2.6 prusaslicer "I get a no suitable storage found at " message. Sometimes it will work if I retry and most of the time it won't. Nothing has changed with regard to my LAN, USB stick used in the MK4 etc other than upgrading from previous beta version of 2.6 to released 2.6 and MK4 is now running RC input shaping firmware. The MK4 recognizes the stick just fine and I can navigate the files on the stick without issue using the Mk4 menu/screen.

Project file & How to reproduce

Try to send any file to MK4 using prusalink setup on LAN.

Checklist of files included above

• [ ] Project file
• [X] Screenshot

Version of PrusaSlicer

2.6.0 Arm64 MAC

Operating system

Mac OS 12.4

Printer model

Prusa MK4 running 5.0.0RC firmware

[slicedbread]

I had this issue as well. I discovered this was because the printer had moved to a new IP address. My resolution was to just update the machine settings to target the new IP and I assigned the printer to have a static IP rather than a dynamic one.

If you're familiar with setting a static IP stop reading here, if you aren't here's a lil GPT generated tutorial:

Accessing Your Router Find your router's IP address:

This is typically 192.168.1.1, 192.168.0.1, or something similar. You can often find it in the router's manual or on the bottom of the router itself. If you can't find it, you can often find your router's IP address by running ipconfig (on Windows) or ifconfig or ip a (on Linux/Mac) in the command line and looking for the "Default Gateway" address. Log in to your router:

Open a web browser and enter the router's IP address into the address bar. Enter the username and password to log in. This information may also be in the router's manual or on the router itself if you haven't changed it from the default. The default is often something like "admin" for both fields. Setting a Static IP Navigate to the DHCP settings:

Once logged in, look for a section called "DHCP", "LAN Setup", "Network Settings", or something similar. Find the Address Reservation or Static Lease section:

Within the DHCP or LAN settings, look for an option to set a static IP, often called "Address Reservation", "DHCP Reservation", "Static Lease", or similar. Choose your device:

You'll need to identify the device for which you want to set a static IP. This can usually be done by looking at a list of connected devices and their current IP addresses and MAC addresses. You might need to check your device’s settings to find out its current IP or MAC address to identify it on the router. Enter the details:

Once you've identified the device, enter the IP address you want to assign to it. This should be within the local network's IP range (e.g., if your router's IP is 192.168.1.1, you might assign 192.168.1.100). Enter the MAC address of the device, which is a unique identifier for the network interface. Save the settings:

Once you've entered the IP and MAC addresses, save the settings. You might have to restart the router and the device for the changes to take effect.

[tverett]

Yeah my printer is already set with a static ip address at my router so that’s not my issue. The issue has gotten better in the latest prusaslicer with beta mk4 firmware but I still occasionally get the issue. There seems to be an issue with the printer not always properly mounting/seeing the usb drive. I’ve noticed that if I reset the printer with the thumb drive inserted it won’t see it after it powers up until I remove it and reinsert it. When it’s in this state I get this error consistently and the only remedy is reinserting the usb drive.

[ltpitt]

Same error here, using a prusa mini plus

[tverett]

This error now occurs every time i try to send a file to my printer which is running the latest firmware and I'm running the latest Prusa Slicer. I have a static IP address set already which hasn't changed since the day I installed my Prusa MK4. I've recently discovered that when this problem occurs if I open a terminal window and ping my mk4's IP address it will respond with no issues and then when I go back to prusaslicer i'm then able to send the file as expected. It's like Prusaslicer isn't properly checking the network for the presence of the Mk4 before it decides the printer is unreachable.

[jandebleser]

I had this issue too. Turns out the USB drive was corrupt. Reformatting the USB stick as FAT32 fixed the issue.

[JayKeyStk]

I've had this bug appearing every now and then, a quick restart have solved it. Up until yesterday. Could not upload anything to the printer, and could not ping my printer's IP address. No matter what I tried.

In my case, it was caused by setting the IP static!! gah! I bound the IP of both my Prusas yesterday, and I lost all connection to them. I've now unbound them both, and both are working again.

So if anyone else has ZenWIFI XT9 from Asus, this could be your issue :-/

[jbernalr]

This is happening to me as well. PrusaSlicer 2.8.1 MK3S+ (Firmware 3.14.0) IP Addresses checked Connection via PrusaLink (Browser) works

[jbernalr]

This is happening to me as well. PrusaSlicer 2.8.1 MK3S+ (Firmware 3.14.0) IP Addresses checked Connection via PrusaLink (Browser) works

I tracked down the problem down to operating system (macos) permissions. Older versions of PrusaSlicer (tested 2.6.0) would cause a OS prompt to ask for permissions for PrusaSlicer to search the network. After you authorise this, you would have access to your printer. Newer PrusaSlicer Versions dont cause the prompt to come up, thereby you need another way to authorize searching the net.