Jump to content

After months of being idle, ran many updates on Klipper/Voron. After reboot "emergency mode" stuff showed up.


DennisM

Recommended Posts

So yesterday I did all the updates necessary to start things up again with my 2.4r2, after months of sitting idle.

Rebooting gives me:

You are in emergency mode. After logging in, "journalctl -xb" to view
system logs, "systemctl reboot" to reboot, "systemctl default" or "exit" to boot into default mode.
Give root password for maintenance
(or press Control-D to continue):

Hmm. Doing the journalctl -xb and looking through it I do see this in there:

Feb 06 09:15:00 mainsailos systemd-fsck[139]: rootfs contains a file system with errors, check forced.
Feb 06 09:15:19 mainsailos systemd-fsck[139]: rootfs: Duplicate or bad block in use!
Feb 06 09:15:19 mainsailos systemd-fsck[139]: rootfs: Multiply-claimed block(s) in inode 43385: 451746
Feb 06 09:15:20 mainsailos systemd-fsck[139]: rootfs: Multiply-claimed block(s) in inode 134618: 451746
Feb 06 09:15:33 mainsailos systemd-fsck[139]: rootfs: (There are 2 inodes containing multiply-claimed blocks.)
Feb 06 09:15:33 mainsailos systemd-fsck[139]: rootfs: File ... (inode #43385, mod time Mon Apr  4 06:43:28 2022)
Feb 06 09:15:33 mainsailos systemd-fsck[139]:   has 1 multiply-claimed block(s), shared with 1 file(s):
Feb 06 09:15:33 mainsailos systemd-fsck[139]: rootfs:         /home/pi/klipper_logs/crowsnest.log (inode #134618, mod time Tue Feb  6 09:10:57 2024)
Feb 06 09:15:33 mainsailos systemd-fsck[139]: rootfs:
Feb 06 09:15:33 mainsailos systemd-fsck[139]: rootfs: UNEXPECTED INCONSISTENCY; RUN fsck MANUALLY.
Feb 06 09:15:33 mainsailos systemd-fsck[139]:         (i.e., without -a or -p options)
Feb 06 09:15:33 mainsailos systemd-fsck[139]: fsck failed with exit status 4.

I'm hoping this isn't a "bad SD card on a raspberry pi" situation. Anyway, I can't seem to run fsck at all as it says everything is mounted and can't run.

Anyone else come across this? I'd hate to pull the pi or try and boot from a USB linux boot setup, but maybe that's what's needed?

I'm thinking about pulling the SD card out and "cloning" it with BalenaEtcher to a new SD card, which maybe would ignore/fix/skip the bad blocks?

 

Thanks for any tips here,

 

Dennis

 

Link to comment
Share on other sites

I am a dos / windows guy. But this really looks like you have some bad blocks on your 'hard' drive. And has nothing to do with your klipper update.

I would suggest checking your hard drive for bad sectors and repair. I am sure linux has an equivalent... let me see... here is a good one you could follow: https://phoenixnap.com/kb/fsck-command-linux

Sure our dos chksdsk c : /F  is a bit easier...

I would first find out if you have any bad sectors on the SD card and fix it, before undertaking any other steps, like copying the sd card or reinstalling mainsail-os. 

Link to comment
Share on other sites

OK, so I pulled the SD card and mounted it via USB on another linux box. I ran fsck to fix all the errors (there were a lot, so I'm not hopeful the setup is still good).

But viola, the system starts up without any issues and even looks like it's ready to use via the Klipperscreen interface on the printer.

BUT the mainsail web UI isn't working. When I try to access it from my laptop, I get the "favicon" and Mainsail on the browser tab, but there is nothing on the screen. So it's not timing out or anything, just not displaying anything on the web page.

Sound familiar to anyone?

Also, nginx IS running on http port 80, so it's listening.

Link to comment
Share on other sites

You will probably find somewhere in the klipper/mainsail logs that one or other component is missing or not working. Probably due to the corrected errors on your sd card, certain files are corrupt or non-functioning.

If you think your sd card is good and you just had a corrupted system because you shut down wrongly, I will suggest to re-install klipper and the whole bit. KIUAH will be very helpfull to remove and reinstall everything quickly for you. Before doing so, do not forget to backup your configuration files and later place it in the correct place so you can run your system as if nothing has happened.

 

If the SD card is a cheap one, I would suggest re installing a new system.

 

 

  • Like 1
Link to comment
Share on other sites

Join the conversation

You can post now and register later. If you have an account, sign in now to post with your account.

Guest
Reply to this topic...

×   Pasted as rich text.   Paste as plain text instead

  Only 75 emoji are allowed.

×   Your link has been automatically embedded.   Display as a link instead

×   Your previous content has been restored.   Clear editor

×   You cannot paste images directly. Upload or insert images from URL.

×
×
  • Create New...