Can't Open Octoprint on Raspberry 4B+

That's still not the OctoPi version...

Whatever, for crying out loud people, I'm not looking for excuses and testimonials. I am looking for Help!!!!!!!! If you haven't got something Helpful to Submit, then Shut Up!!!!!!! For Christs Sake this is the Help Section, not the Testimonial Section of how Brilliant you seem to think you are!!!!!!!!!!!

I understand that you're frustrated but please watch your language.
We just want to help you and that reaction is not appropriate.

There is a difference between Octoprint - which is the printerserver and Octopi - which is the image Octoprint runs on.

I tried to help you in my first post, asking a question and suggesting further troubleshooting. You got OctoPi versions and OctoPrint versions confused, and even when it was explained to you just replied with a link to the release notes. All I wanted to know was what image did work and what did not. Seeing as you don't want that help, you won't get it.

I tell you what, all I am asking is how do I get the SD Card to Mount once it is finished burning the Octopi 0.18.0/Octoprint 1.2.2 img file with Raspberry Pi Imager, Win32 Imager or BalenaEtcher. I've been a A+ Computer Tech since 1996 and been using a computer since before Microsoft even existed back using an 8088 with a green screen and 32 kb of memory. So I don't need an explanation on HOW to run a computer.

interesting that some ppl, reaching a specific frustration level about something they have no clue about, turning into old-school computer "specialists" ...
I AM an IT specialist but I do not know everything. So if I'm moving my buttcheeks at new terrain, I better don't piss peaople off who are able to help.
So better watch what you say, and give the information the ppl need to help and do a strategic investigation about your problem.
Please downshift, and take a breath, and restart.
Thousands are using Octoprint and/or OctoPi. Thats two pair of shoes and there are different ways to support and to figure out the problem. At the end both do the same (remote your 3D printer) but the installation and configuration is not the same.
Nobody want you to teach how to use your PC but on your side something is going wrong, otherwise it would run like on our PC's or PI's .
I personally run that stuff on 4 of my PI's and printers. And its running flawless.
Yes, I ran into problems in the past, but please remember : This is not a payed support channel. All the ppl spent their free time to find a solution for you. For a problem you are NOT able to solve by yourself.
So please think about your reaction, and then lets start allover again.

Sorry about my bad english folks, but its not my first language.

So hopefully all are calm now. We are close to chrismas.

Regards
MAMEniac

1 Like

For once and for all, is there any work arounds to get Octoprint loaded onto an SD Card that will Mount Fat32????????????? That's all I want to know, I don't need to know if you or anyone else has managed to do it. Until my previous Raspberry Pi 3 B+ died due to a Brown Out. I had been running Octoprint daily for 3 years without any issues.

If no one can help me with a workaround or another option, then fine. I will break out my credit card and start using Astro again. I loved Octoprint because it was update regularly and worked flawlessly.

When you write an OctoPi image with any of the image writing tools, there are two partitions written to the SD card, one is FAT32, one is Linux (ext4). After writing the SD card, remove it and reinsert it. Most Operating Systems will then mount the FAT32 partition. Windows 10 (and earlier) may open a dialog to format the "unknown" partition, just answer no.

If it isn't working for you, I'm sorry. Without better input we don't have any better answers.

This is all I was looking for, When I try to burn the Octopi Image using Raspberry Pi Imager or one of the others available. I choose what it is that I am trying to burn an image of, and in this case it is Octopi from Other OS in Imager. I then click on Ctrl+Shft+x and enter Ender3.local followed by SSID and the Password. Then Time Zone and Nearest Location. I then choose the Drive and click on Write. It will write the image to the drive and then Verify. At the end of the verification I will always get a message stating that it couldn't verify because what was written doesn't correspond with what is there or at least something along those lines. I will then get a message that states that Raspberry Pi Imager Failed to Mount Fat32. There is no mention of Linux (ext4).
Is there not a 64Bit version available of Octoprint and could I not use Etcher or one of the others to burn a copy and mount it with a 64Bit solution.
I have been able to write Raspberry Pi OS without the slightest problem and Debian Linux without a problem either using Raspberry Pi Imager. It's only Octopi 0.18.2 that is giving me nightmares. My computer is running Windows 11 Professional and I have tried running the different Imaging software using every compatibility setting available.

I upgraded a system to Windows 11 Home and attempted to recreate your problem. I tried twice, once using the Raspberry Pi Imager to select the (stable) OctoPi image and once downloading the image from the OctoPrint web site.

In both cases, I did not get a verification error and after removing and reinserting the SD card, the boot partition showed up.

There is not a 64-bit version of OctoPi.

I finally gave up and just installed Octoprint for Window Server. Works perfectly and all I have to do now is get a USB-Cat 5 Adapter to connect my main PC and Ender 3 together. Thanks for trying, when a Level 3 Technician right from Microsoft Tech Support couldn't get a Verified output on an SD Card using remote access to my computer. I thought it had to do something with the official OctoPi 0.18.2 file itself available from within the Raspberry Pi Imager program.

1 Like

I have no problems with Balena Etcher ever since I turned off Norton Autoprotect during flashing.
Also try using a USB 2 ports instead of USB 3 for your card reader.

This topic was automatically closed 90 days after the last reply. New replies are no longer allowed.