Mcu 'mcu': Unable to connect after emergency stop

General Discussion
1

Basic Information:

Printer Model: voron 2.4
MCU / Printerboard: monster8
klippy.log

Fill out above information and in all cases attach your klippy.log file. Pasting your printer.cfg is not needed
Be sure to check our Knowledge Base and in particular this and this post

Describe your issue:

It was working perfectly fine till i pressed emergnecy stop.
I checked ‘ls -l /dev/serial/by-id/’
and its giving me this error
ls: cannot access ‘/dev/serial/by-id/’: No such file or directory

I dont know what is wrong.
does emergency stop did something to my printer?
its not recognizing the printer.
I changed usb cable and port and reflashed the firmware by make menuconfig

please help
klippy.log (755.0 KB)

2

First, for the sake of whatever gods: Is it so damned difficult to follow the directions and provide a klippy.log? Do the directions need to be in red and blinking, or what is the issue?

Second, check if you are affected by: Debian Bullseye Bug causing Klipper to no longer find the printer board

3

sry forgot
i just updated it

4

Issue a sudo service klipper restart followed by a firmware restart via the webinterface, due to mcu.error: Can not update MCU 'BTT_CAN' config as it is shutdown
Apart from this, nothing special in this log you provided.