My SV08 is one year old. My son was using it and was prompted to update orcaslicer, which he did. It was then stuck on a system rebooting. I used the USB to reinstall the Sovol_Update_Package-12-23.deb and got past the system rebooting problem. I went to reinstall the original software with the USB that came with the printer but the file is corrupted. I went to your website ( Firmware Download ) and found the file under SV08 USB files. That file is corrupted too. Some advice online says not to use newer versions of orcaslicer because of compatibility issues. I have tried a variety of orcaslicer versions but they all have some critical error. What “deb” file should I have used and which orcaslicer software version should i use? I use a Mac with a M chip. Thanks in advance…
Hi,
What operating system does your Mac use?
Because it seems to me that a deb package should be used with Debian.
I thought the USB only had Windows & Mac versions…
Linux versions are unstable.
The deb package was flashed to the SV08, not to my Mac. (Sequoia 15.6.1)
Yes, the USB that came with the unit has Win and Mac versions. The firmware update package I used from ‘Sovol 3d printer WIKI’ was uploaded to a clean FAT32 USB and placed in the SV08 to stop the endless system booting problem.
Ok, let me see if I got this straight…
Your son updated Orca Slicer…
Somehow that put the SV08 in a Boot Loop…
Then you re-installed the SV08 Firmware & fixed the Boot Loop issue…
Now, all you need is a version of Orca Slicer..??
Yes, and confirmation that the firmware update was the appropriate one would be much appreciated. 
The problem with the orcaslicer software is that i read (somewhere, officially sounding) not to update because sovol used some neutered version of the software. So I’ve been working under this assumption–that I just need the correct albeit outdated version. Ok, fine, but what software version should I use? None of the ones i tried have worked including the newest version. All have had issues but none have replicated the system rebooting problem. I’ve gone down many ‘rabbit holes’ trying to correct the issues with the various versions. I just want it to work like it did before. I would like a stable version of orcaslicer. Which version should i use??
Sovol like Creality & many others don’t update their version of Cura or Orca.
You should download the Official Orca Slicer and add the SV08 during setup.
Remove whatever version have installed first.
Once you have Orca installed, it will be safe to update without any problems.
Don’t install a Beta Version, install the Stable Version.
I really appreciate the help!
I removed my old version of Orca Slicer and installed the newest version (v2.3.1) from the link you provided. (Not sure if it is important but it didn’t ask me to add the SV08 during setup.) I tried a test print. It sliced it fine but when I asked it to upload and print, it generated a new error, any ideas?:
Error uploading to print host:
HTTP 500: {“error”: {“code”: 500, “message”: “Internal Server Error”, “traceback”: “Traceback (most recent
call last):\n\n File “/home/sovol/moonraker/moonraker/components/file_manager/file_manager.py”, line
958, in _process_uploaded_file\n shutil.move(\n\n File “/usr/lib/python3.9/shutil.py”, line 820, in move\n
copy_function(src, real_dst)\n\n File “/usr/lib/python3.9/shutil.py”, line 435, in copy2\n copyfile(src, dst,
follow_symlinks=follow_symlinks)\n\n File “/usr/lib/python3.9/shutil.py”, line 275, in copyfile\n
_fastcopy_sendfile(fsrc, fdst)\n\n File “/usr/lib/python3.9/shutil.py”, line 166, in _fastcopy_sendfile\n raise
err from None\n\n File “/usr/lib/python3.9/shutil.py”, line 152, in _fastcopy_sendfile\n sent =
os.sendfile(outfd, infd, offset, blocksize)\n\nOSError: [Errno 28] No space left on device:
‘/tmp/moonraker.upload-1211.mru’ → ‘/home/sovol/printer_data/gcodes/pinata collar 24 in
30_PLA_0.2_10m38s.gcode’\n\n\nDuring handling of the above exception, another exception
occurred:\n\n\nTraceback (most recent call last):\n\n File “/home/sovol/moonraker/moonraker/app.py”,
line 956, in post\n result = await self.file_manager.finalize_upload(form_args)\n\n File
“/home/sovol/moonraker/moonraker/components/file_manager/file_manager.py”, line 822, in
finalize_upload\n result = await self._finish_gcode_upload(upload_info)\n\n File
“/home/sovol/moonraker/moonraker/components/file_manager/file_manager.py”, line 896, in
_finish_gcode_upload\n finfo = await self._process_uploaded_file(upload_info)\n\n File
“/home/sovol/moonraker/moonraker/components/file_manager/file_manager.py”, line 964, in
_process_uploaded_file\n raise self.server.error(“Unable to save file”,
500)\n\nmoonraker.utils.ServerError: Unable to save file\n\n\nDuring handling of the above exception,
another exception occurred:\n\n\nTraceback (most recent call last):\n\n File
“/home/sovol/moonraker-env/lib/python3.9/site-packages/tornado/web.py”, line 1786, in _execute\n
result = await result\n\n File “/home/sovol/moonraker/moonraker/app.py”, line 958, in post\n raise
tornado.web.HTTPError(\n\ntornado.web.HTTPError: HTTP 500: Internal Server Error (Unable to save
file)\n”}}
It sounds like a bad installation.
Could you uninstall your OrcaSlicer, download the latest functional version (check the operating system), then, after installation, select the printer and filament appropriate for your model, restart the slice, and run your gcode on the printer?
I’m confused…
Your original post seems to refer to updating the printer FIRMWARE not Orca Slicer. Yes your son was using the web interface on the Device tab in Orca but the actual update was to the embedded Linux host built onto the SV08 mainboard.
Then suddenly you are worried about Orca versions. No version of Orca is going to work with a corrupted install of the printer operating system.
You will most likely need to obtain a USB EMMC adaptor and reflash your PRINTER to a working OS then worry about Orca Slicer.
Alternate source for EMMC tool:
I’m there with you
I thought the Firmware issue was fixed…
To be honest, I no longer understand why this is necessary.
Maybe it would be wise for @partimeprinter to explain it clearly.
The first error is a mainsail/fluidd error the rest are linux file system errors. All these are happening on the “host”.
Thanks for the help and sorry for any confusion. If I was an expert, I wouldn’t be here 
. Ok, I got some clarification from my son. In Orca Slicer, he got a pop up that indicated he needed to update. He followed the link to github and updated. Then, he tried to start a print and got an error 500 code (pic is below). He restarted the printer and it got stuck on the booting screen. That’s when I flashed the firmware and (apparently?) fixed the system rebooting problem.
The issue I currently have is I can’t upload a print. When I try, I get this error:
Error uploading to print host:
HTTP 500: {“error”: {“code”: 500, “message”: “Internal Server Error”, “traceback”: “Traceback (most recent
call last):\n\n File “/home/sovol/moonraker/moonraker/components/file_manager/file_manager.py”, line
958, in _process_uploaded_file\n shutil.move(\n\n File “/usr/lib/python3.9/shutil.py”, line 820, in move\n
copy_function(src, real_dst)\n\n File “/usr/lib/python3.9/shutil.py”, line 435, in copy2\n copyfile(src, dst,
follow_symlinks=follow_symlinks)\n\n File “/usr/lib/python3.9/shutil.py”, line 275, in copyfile\n
_fastcopy_sendfile(fsrc, fdst)\n\n File “/usr/lib/python3.9/shutil.py”, line 166, in _fastcopy_sendfile\n raise
err from None\n\n File “/usr/lib/python3.9/shutil.py”, line 152, in _fastcopy_sendfile\n sent =
os.sendfile(outfd, infd, offset, blocksize)\n\nOSError: [Errno 28] No space left on device:
‘/tmp/moonraker.upload-455.mru’ → ‘/home/sovol/printer_data/gcodes/pinata collar 24 in
30_PLA_0.2_10m34s.gcode’\n\n\nDuring handling of the above exception, another exception
occurred:\n\n\nTraceback (most recent call last):\n\n File “/home/sovol/moonraker/moonraker/app.py”,
line 956, in post\n result = await self.file_manager.finalize_upload(form_args)\n\n File
“/home/sovol/moonraker/moonraker/components/file_manager/file_manager.py”, line 822, in
finalize_upload\n result = await self._finish_gcode_upload(upload_info)\n\n File
“/home/sovol/moonraker/moonraker/components/file_manager/file_manager.py”, line 896, in
_finish_gcode_upload\n finfo = await self._process_uploaded_file(upload_info)\n\n File
“/home/sovol/moonraker/moonraker/components/file_manager/file_manager.py”, line 964, in
_process_uploaded_file\n raise self.server.error(“Unable to save file”,
500)\n\nmoonraker.utils.ServerError: Unable to save file\n\n\nDuring handling of the above exception,
another exception occurred:\n\n\nTraceback (most recent call last):\n\n File
“/home/sovol/moonraker-env/lib/python3.9/site-packages/tornado/web.py”, line 1786, in _execute\n
result = await result\n\n File “/home/sovol/moonraker/moonraker/app.py”, line 958, in post\n raise
tornado.web.HTTPError(\n\ntornado.web.HTTPError: HTTP 500: Internal Server Error (Unable to save
file)\n”}}
I don’t know what a mainsail/fluidd error is or the linux errors. Or how to fix it. Any ideas? I’m happy to clarify further if needed…
@partimeprinter The folks answering here are much more aware, but is the printers disk full? I don’t have a SV08 but I had a issue with my Sovol Zero where I ran out of disk space and if I recall the errors were similar “No Space left on device:” and happened when I tried to print. The fix was to clear out room in the gcodes folder.
To check: Again this is for a Sovol Zero I believe the SV08 should work the same.
Open your browser to the printers IP then select G-Code Files and review Free Disk space on the upper right side of the page.
If Orcaslicer is functional you can navigate to the same place using the Device page in Orcaslicer.
If the free space is really low you might have hit the same issue, and need to delete or download the files and delete?
Cheers,
-Mike
Trying to stay “high level” and not get too technical…
The embedded SBC (small board computer or loosely Pi) runs a custom version of Armbian. The image includes a preconfigured version of (Debian based) Linux.
Sovol releases firmware updates as .deb packages. The update package only contains files that have changed. In order to “'work” there must already be a functional OS on the SBC.
Your OS got corrupted. You did the logical thing and ran the .deb update. The update “fixed” things well enough to boot but didn’t repair all the damage. When Orca tries to send a file the file system on the SBC can not find the correct files and dumps a bunch of errors.
The only sure way to ensure the base OS is intact is to flash a new image onto the EMMC board plugged into your SV08 mainboard. Yor need to remove the EMMC board and mount it on the USB adaptor. Instructions (and videos) are on the WIKI.
Once the system boots that image THEN you can do the .deb update.
Are you sure OrcaSlicer logs on to the Internet?
@SV08_user yes, i did the test and confirmed it connects. Thank you!