0

I have a dual boot Win7Pro/Ubuntu on an HP Probook 6550b. Everything worked fine until I did an upgrade to 16.04.

When trying to boot in Ubuntu I get this message :

BusyBox v1.21.1 (Ubuntu 1:1.21.0-1ubuntu1) built-in shell (ash)
Enter 'help' for a list of built-in commands
(initramfs)

I read somewhere on this forum that it could be caused by a bad filesystem, so I tried this:

sudo fdisk -l | grep Linux | grep -Ev 'swap'

But sudo fdisk -l gives this:

Disk /dev/sda: 320.1 GB, 320072933376 bytes
255 heads, 63 sectors/track, 38913 cylinders, total 625142448 sectors
Units = sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 512 bytes
I/O size (minimum/optimal): 512 bytes / 512 bytes
Disk identifier: 0x8c949010

   Device Boot      Start         End      Blocks   Id  System
/dev/sda1   *        2048      616447      307200    7  HPFS/NTFS/exFAT
/dev/sda2          616448   589486079   294434816    7  HPFS/NTFS/exFAT
/dev/sda3       589486080   620943359    15728640    7  HPFS/NTFS/exFAT
/dev/sda4       620943360   625127423     2092032    c  W95 FAT32 (LBA)

So, no Linux filesystem. I remembered Linux was installed from out of Windows, long time ago, something with wubi, see screenshot

Wubi screenshot

So, I cannot use this solution ? Boot drops to a (initramfs) prompts/busybox

Community
  • 1
bart
  • 3

2 Answers2

0

As we discussed... get into the GRUB menu by holding down the LEFT SHIFT key immediately after selecting Ubuntu from the Windows boot manager. Then select the prior kernel and see if it boots. If yes, do some backups! Then try the 16.04 upgrade again (with Wubi, if you like). If that fails again, just do a standard Ubuntu reinstall/upgrade using a Ubuntu LiveCD that you've burned to a DVD. Cheers, Al

heynnema
  • 73,649
0

I had same issue after upgrading (from Ubuntu udate manager) from Ubuntu 14.10 to Ubuntu 16.04.1. It worked fine, until rebooted.... The recovery menu and every option would go to busybox. So I booted into a live CD and ran sudo fsck /dev/sda1 from a terminal (with the HD in question NOT mounted) since that was the msg from busybox about sda1 needing manual fsck. But not sure for other busybox messages

Ronald Gaynor
  • 1