[Bug 1467346] Re: Partition tool of 15.04 install script bricked SSD, conflict between UEFI/Legacy boot might be a factor...

[Brian Murray]

** Package changed: ubuntu => ubiquity (Ubuntu)

** Tags added: vivid

-- 
You received this bug notification because you are a member of Ubuntu
Foundations Bugs, which is subscribed to ubiquity in Ubuntu.
https://bugs.launchpad.net/bugs/1467346

Title:
  Partition tool of 15.04 install script bricked SSD, conflict between
  UEFI/Legacy boot might be a factor...

Status in Ubiquity:
  New
Status in ubiquity package in Ubuntu:
  New

Bug description:
  So, I don't fully understand the differences between 'legacy' boot and
  'efi/uefi' boot modes, but what I do know is that I had my bios set to
  'legacy' boot by default, it seems.

  I was running windows 8.1 on my Dell E6530.

  I tried to install ubuntu 15.04.

  In the boot menu, I had to select to boot off of the USB in UEFI mode.

  I tried to create a partition using the install script's tool for
  doing so.

  I had 80gb out of 240gb free. I tried to reduce the 240gb partition
  down to 200gb, and make the remaining 40gb into an ext4 partition.

  I initially got a pop up telling me that it seemed my other OS was not
  a UEFI installed OS, so I may have trouble with grub or something. I
  hit 'back', I think, and got some I/O errors. I hit ignore, as several
  alert windows popped up notifying me of I/O errors.

  I don't remember all the details of what is next. I think I tried to
  do it again, and then clicked skip this time, or something, and then
  got several I/O errors popping up, one after another.

  Finally, I got an alert that install had failed.

  When I restarted my computer, it was gone. No ability to boot into
  windows.

  Go ahead and liveboot into ubuntu, figuring it's just a matter of
  restoring the original partitions.

  Talk through it with a guy on IRC. Powercycle. He confirms with me
  that it isn't a faulty SATA port through a series of steps.

  Note that when I do the liveboot, I see the verbose booting read 'ata
  error -=16' repeatedly or something... That's the closest I get to
  seeing the computer even try to identify it.

  A lot of people seem to scoff initially, saying you can't brick a
  drive this way. But some bug somewhere caused something. The idea of a
  random drive failure at just the moment I started doing a partition
  seems very unlikely.

  This is an OCZ ARC 100 240gb. I purchased it a few months ago new. It
  has served me well and flawlessly until this moment.

  And it was $100, and I am very sad to be lacking it.

  Luckily, most of my files were kept on an external drive; still, it
  had all of my software, and many, many hours of work in its own right.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubiquity/+bug/1467346/+subscriptions