Error 422: Unprocessable Entity -> USB Stick lost formatting
 
Notifications
Clear all

Error 422: Unprocessable Entity -> USB Stick lost formatting  

  RSS
reox
 reox
(@reox)
Eminent Member
Error 422: Unprocessable Entity -> USB Stick lost formatting

Since a few weeks, I experience every now and then a problem when uploading GCode with PrusaSlicer via PrusaLink to my MINI currently with Firmware 6.2.4.

During the upload I get this error message:

When I look at the printer, I can see that there are no more files on the USB Stick, and when I plug it into a computer the partition table is wiped (actually I'm not sure what exactly happens - remember me to dump the device next time it happens...).

When I reformat the stick and run the upload again, everything works.

Is this behaviour likely a broken USB Stick or a problem with the firmware? I noticed that 6.2.4 was supposed to fix some issues with USB - maybe a regression?

Posted : 27/04/2025 4:23 pm
FoxRun3D
(@foxrun3d)
Illustrious Member
RE: Error 422: Unprocessable Entity -> USB Stick lost formatting

Sounds like a bad stick. I'll try a different one. 

Formerly known on this forum as @fuchsr -- until all hell broke loose with the forum software...

Posted : 27/04/2025 9:29 pm
Diem
 Diem
(@diem)
Illustrious Member

It's complaining about 'invalid' characters in the filename - not uncommon when switching storage between operating systems.  Some exotic unicode characters mimic controls codes - stick to simple alphanumerics without spaces or punctuation and you  should be OK.

More details here:  https://help.prusa3d.com/article/usb-not-detected-mini-mini_230441

Cheerio,

Posted : 27/04/2025 10:43 pm
reox
 reox
(@reox)
Eminent Member
Topic starter answered:
RE: Error 422: Unprocessable Entity -> USB Stick lost formatting

Sounds like a bad stick. I'll try a different one. 

I'll try deep-formatting it first - but yes, that would be the cheapest thing to try. Unfortunatley, I cannot trigger this bug reliably, thus it is very hard to tell if another stick really works.

 

It's complaining about 'invalid' characters in the filename - not uncommon when switching storage between operating systems.  Some exotic unicode characters mimic controls codes - stick to simple alphanumerics without spaces or punctuation and you  should be OK.

I don't think that's the case here. When this error occurs and I format the stick again, I can upload the same file from the same PrusaSlicer session without any problems. I leave the stick 100% of the time on the printer, because I always use PrusaLink. I think this error message is a symptom of the underlying problem and not the actual cause.

Posted : 28/04/2025 5:27 am
Share: