Can't boot? BusyBox Prompt? How to fix HD corruption.
Posted: Mon Oct 14, 2024 6:39 am
I just wanted to alert you to an issue I had recently.
I had a misbehaving app I couldn't close.
So I hard rebooted the machine from the button(holding it down) and it corrupted the drive (well of course).
I've gotten away with this many times, but not this time.
On launch I was stuck at the BusyBox text only prompt and IIRC attempting to "exit" gave me this.
So I thought, what the fsck? I mean, what is fsch?
Well obviously it's a File System CHecker.
So the command you need to run to repair the drive is:
Obviously replace xxxxxxxxxxx with your drive partition name.
After issuing the command and typing "exit" the desktop should now boot up normally.
Your welcome.
I had a misbehaving app I couldn't close.
So I hard rebooted the machine from the button(holding it down) and it corrupted the drive (well of course).
I've gotten away with this many times, but not this time.
On launch I was stuck at the BusyBox text only prompt and IIRC attempting to "exit" gave me this.
Code: Select all
/dev/xxxxxxxxxxx cointains a file system with errors, check forced.
Inodes that were part of a corrupted orphan linked list found.
/dev/xxxxxxxxxxx : UNEXPECTED INCONSISTENCY; RUN fsck MANUALLY.
(i.e., without -a or -p options)
fsck exited with status code 4
The root filesystem on /dev/xxxxxxxxxxx requires a manual fsck
BusyBox v1.22.1 (Ubuntu 1:1.22.0-15ubuntu1) built-in shell (ash)
Enter 'help' for a list of built-in commands.
Well obviously it's a File System CHecker.
So the command you need to run to repair the drive is:
Code: Select all
fsck -y /dev/xxxxxxxxxxx
After issuing the command and typing "exit" the desktop should now boot up normally.
Your welcome.