!Screenshot
Issue: After a reboot, the boot process drops to the BusyBox shell and I end up at the Initramfs prompt:
Cause: 1. Unexpected powerloss and shock to the harddisk in a some way example charging a device while system being shutdown and causing bad superblock in system.
Solution:
Firstly, boot into a live CD or USB
Find out your partition number by using
Then, list all superblocks by using the command:
Replace "sda2" to your drive number
Now, to check and repair a Linux file system using alternate superblock # 32768:
The -y flag is used to skip all the Fix? questions and to answer them all with a yes automatically
Now try mounting the partition:
Now, try to browse the filesystem with the following commands:
If you are able to perform the above commands, you have most probably fixed your error.
Now, restart you computer and you should be able to boot normally.
(source)
#errors #Notes #fixes
Issue: After a reboot, the boot process drops to the BusyBox shell and I end up at the Initramfs prompt:
BusyBox v1.18.5 (Ubuntu 1:1.18.5-1ubuntu4) built-in shell (ash) Enter 'help' for a list of built-in commands. (initramfs)
Cause: 1. Unexpected powerloss and shock to the harddisk in a some way example charging a device while system being shutdown and causing bad superblock in system.
Solution:
Firstly, boot into a live CD or USB
Find out your partition number by using
sudo fdisk -l|grep Linux|grep -Ev 'swap'
Then, list all superblocks by using the command:
sudo dumpe2fs /dev/sda2 | grep superblock
Replace "sda2" to your drive number
Now, to check and repair a Linux file system using alternate superblock # 32768:
sudo fsck -b 32768 /dev/sda2 -y
The -y flag is used to skip all the Fix? questions and to answer them all with a yes automatically
Now try mounting the partition:
sudo mount /dev/sda2 /mnt
Now, try to browse the filesystem with the following commands:
cd /mnt mkdir test ls -l cp file /path/to/safe/location
If you are able to perform the above commands, you have most probably fixed your error.
Now, restart you computer and you should be able to boot normally.
(source)
#errors #Notes #fixes