kernel-packages team mailing list archive

[Gerv <1338942@xxxxxxxxxxxxxxxxxx>]

penlavch: so, let me get this straight. This bug where my computer won't
boot from a particular SSD: you want me to boot the computer from a CD
and see if I can reproduce the bug? And if I do reproduce the bug where
my computer won't boot, you want me to run some software on this non-
booted computer in order to submit a problem report?

Have I got that right?

-- 
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1338942

Title:
  New 64-bit 14.04 install doesn't boot

Status in “linux” package in Ubuntu:
  Incomplete

Bug description:
  I have a Thinkpad X230 happily running 14.04 32-bit with full disk
  encryption. It was an upgrade from 13.10, which also (obviously) had
  full disk encryption. However, I have 12GB of RAM so I wanted to
  switch to 64-bit. I decided the safest way was to buy a new drive and
  install the 64-bit version to that, then migrate my data. So I bought
  a Crucial SSD, made a boot USB stick of 14.04 64-bit, fitted the SSD
  and started the install, again requesting full disk encryption.

  The install proceeds fine and precisely as expected, right up to
  "Reboot to use your new system". But then the system does not start.

  The first time I try and restart, immediately after install, I get the
  BIOS splash screen and the "black with a purple border" screen, but no
  "please enter your drive password". Instead, the fan starts whirring
  and the machine gets hot - it seems to be pegging the CPU. In case it
  was doing something like encrypting all the data, I left it overnight
  (the second time I tried the install), but when I came back 10 hours
  later, I was still at the "black with a purple border" screen,
  although the CPU seemed not to be working hard any more.

  If I try rebooting again, I can get a GRUB screen, but if I pick
  "Ubuntu", I get the purple border, and then "Kernel panic - not
  syncing - No init found." And that's the message I get on each
  subsequent boot attempt.

  I can boot the machine using my old 32-bit 14.04 disk (attached in a
  USB3 enclosure) and examine the internal drive. However, I don't know
  what to look for. Using the "Disks" tool, I can mount the boot
  partition - it seems to have all the right bits, but I'm no expert. I
  an also unlock the encrypted partition, although I can't work out how
  to mount it.

  So I'm happy to provide more info if people just tell me what to look
  for.

  I'll also try and install _without_ FDE and see if that's the factor
  which makes the difference.

  Gerv

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1338942/+subscriptions