F5F Stay Refreshed Software Operating Systems Ubuntu launches directly into the BusyBox command line.

Ubuntu launches directly into the BusyBox command line.

Ubuntu launches directly into the BusyBox command line.

_
_RacKe_
Junior Member
13
10-27-2016, 01:19 AM
#1
Hello. I've been using Ubuntu 16.04 for a few months. Recently, I faced issues with bootloaders while running Windows 10, OS X and Ubuntu 16.04 on my MacBook with 11.1 drivers. Today I restarted Ubuntu but couldn't launch apps via Dock, Launcher or Terminal. Downloads from Firefox indicated the disk was write-protected. During shutdown, the screen tore—upper and lower halves didn’t sync—and froze for minutes before forcing a shutdown. Now I’m stuck in the BusyBox terminal after selecting Ubuntu in Grub2. I have a boot-repair disk. Should that fix it or disrupt my current setup? (On OSX, reFind can install kernels or use Grub, both work similarly.)
_
_RacKe_
10-27-2016, 01:19 AM #1

Hello. I've been using Ubuntu 16.04 for a few months. Recently, I faced issues with bootloaders while running Windows 10, OS X and Ubuntu 16.04 on my MacBook with 11.1 drivers. Today I restarted Ubuntu but couldn't launch apps via Dock, Launcher or Terminal. Downloads from Firefox indicated the disk was write-protected. During shutdown, the screen tore—upper and lower halves didn’t sync—and froze for minutes before forcing a shutdown. Now I’m stuck in the BusyBox terminal after selecting Ubuntu in Grub2. I have a boot-repair disk. Should that fix it or disrupt my current setup? (On OSX, reFind can install kernels or use Grub, both work similarly.)

C
CheezBurgerzz
Member
202
10-28-2016, 04:26 AM
#2
can you format the text as the white background doesn't look good for me with white text
C
CheezBurgerzz
10-28-2016, 04:26 AM #2

can you format the text as the white background doesn't look good for me with white text

M
mat_fram
Posting Freak
776
10-28-2016, 09:40 AM
#3
You're welcome to give it a shot. If it doesn't work, you can reinstall it entirely.
M
mat_fram
10-28-2016, 09:40 AM #3

You're welcome to give it a shot. If it doesn't work, you can reinstall it entirely.

S
StyleTrick
Senior Member
744
10-31-2016, 02:55 AM
#4
I observed the boot process and noted that my Linux partition sda4 has filesystem errors. Running fsck completed with exit code 4, indicating issues that require manual attention. It suggests performing a live-disk boot followed by a manual fsck for resolution.
S
StyleTrick
10-31-2016, 02:55 AM #4

I observed the boot process and noted that my Linux partition sda4 has filesystem errors. Running fsck completed with exit code 4, indicating issues that require manual attention. It suggests performing a live-disk boot followed by a manual fsck for resolution.

C
cto976
Member
64
11-21-2016, 08:30 PM
#5
Corrected using a live CD with fsck.ext4 -v command for /dev/sda4
C
cto976
11-21-2016, 08:30 PM #5

Corrected using a live CD with fsck.ext4 -v command for /dev/sda4