This is why it’s important to make backups. If, by any chance you printed your disk configuration before the gpt operation, you want to copy it into a notepad NOW. You can use that to try and recreate your original partition layout after converting the disk back to MBR. Chances are nothing is wiped, except for your disk configuration. No guarantees, though…

Whatever you do, don’t format anything, as that WILL overwrite your data.

You need some ansible love in your life!

I have my moments… 😉 Feel free to pm me if you need more advice.

I would copy the existing system onto a new system:

1. Update system to the latest packages
2. Create a new base system using the same distro
3. Check which packages are not on the new system, add them to your playbook
4. Install packages on new system
5. This will take some time. Run a find of all files and pass them to md5sum or sha512sum to get a list of files with their checksum. Compare the list from the old system to the new system.
6. Update your playbook with these findings. Template is probably the way to go, Lineinfile might be good as well, use copy if nothimg else works.
7. Check firewall settings and update your playbook.

Anyhow this will take some iterations, but while you have a copy of your ‘production’ system, you can test on your ‘test’ machine until you have the same functionality.

So… Europe? 160 ish?

I was kind of getting really desperate, as I usually, IMO, take good care of the machine. And usually I know hoe to solve issues. But in hindsight, and after checking timestamps, I do believe it is the slicer. When I updated it earlier this year I printed some figs, but couldn’t troubleshoot during to time constraints, and I parked it. So recently I picked up printing some more, but it didn’t connect immediately.

So yeah, I blame the slicer, and my lack of time.

Thanks for taking the time to reply.

I eventually ended up removing my slicer (Chitubox basic) and install the latest and greatest after cleaning up my profile. So literally starting anew.

Aside from changing te resin, I didn’t modify any other settings to begin with, so my config was rather vanilla.

After taking these steps (and cleaning the z-axis and replacing the nofep again) everything seems to be working fine now.

Cleaning the axis and a new nofep didn’t seem to do anything, so I think it was just a crappy version of the slicer.

Thanks for taking the time to reply.

I eventually ended up removing my slicer (Chitubox basic) and install the latest and greatest after cleaning up my profile. So literally starting anew.

Aside from changing te resin, I didn’t modify any other settings to begin with, so my config was rather vanilla.

After taking these steps (and cleaning the z-axis and replacing the nofep again) everything seems to be working fine now.

Cleaning the axis and a new nofep didn’t seem to do anything, so I think it was just a crappy version of the slicer.

Hey, I cleaned the z-axis: no change I replaced the nofep (again): no change I removed my old slicer (Chitubox Basic 1.9.5) and installed the latest (2.1). I cleaned up my profile, so it was vanilla config: what do you know: it seems to work now!

Still running some prints to monitor any changes, but it’s looking good!

Thank you for your time!

Thanks for taking the time to reply.

I eventually ended up removing my slicer (Chitubox basic) and install the latest and greatest after cleaning up my profile. So literally starting anew.

Aside from changing te resin, I didn’t modify any other settings to begin with, so my config was rather vanilla.

After taking these steps (and cleaning the z-axis and replacing the nofep again) everything seems to be working fine now.

Cleaning the axis and a new nofep didn’t seem to do anything, so I think it was just a crappy version of the slicer.

Thanks for taking the time to reply.

I eventually ended up removing my slicer (Chitubox basic) and install the latest and greatest after cleaning up my profile. So literally starting anew.

Aside from changing te resin, I didn’t modify any other settings to begin with, so my config was rather vanilla.

After taking these steps (and cleaning the z-axis and replacing the nofep again) everything seems to be working fine now.

Cleaning the axis and a new nofep didn’t seem to do anything, so I think it was just a crappy version of the slicer.

Thanks for taking the time to reply.

I eventually ended up removing my slicer (Chitubox basic) and install the latest and greatest after cleaning up my profile. So literally starting anew.

Aside from changing te resin, I didn’t modify any other settings to begin with, so my config was rather vanilla.

After taking these steps (and cleaning the z-axis and replacing the nofep again) everything seems to be working fine now.

Cleaning the axis and a new nofep didn’t seem to do anything, so I think it was just a crappy version of the slicer.

Well, it seems you might be right.

I installed the latest version of Chitubox Basic (2.1) and now it works just great.

Thank you very much, kind internet stranger!

The glass is half full, yeah? 😉

So you think is is maybe a software issue?

I’ll check if there are any known issues and possibly update my chitubox

I did select different settings for the other resin. I checked both in the app and on Epax’s website, and my settings are aligned

Thank you for your reply! I hadn’t thought of the mechanics!

I’ll check the screw and clean it.

Oh cool, implementing mediocre algorithms. What could possibly go wrong?

Yes, it is our entire airforce. Now send yours!

Ise kde, not gnome.