[Bug 1851239] [NEW] Open Suse locked down the bios of this computer.

[Herman Douglass Brown]

Public bug reported:

I installed Open Suse because I had used this OS previously. When I
pulled up the OS for the first time I noticed the OS had changed since
the last time I used it. (been on iPad for a while and wanted to go to
back to an OS I was previously familiar with. I found it had change and
decided to load Unbuntu Mate instead. I found out a 512GB Sata was not
recognized trying to install it. I was able to recover 442GB of that
drive. Puzzled, I just installed Open Mandriva on that. After two days,
I was not able to use the drive. The software kept saying there was no
drive to boot up to because an illegal transaction had taken place. I
went into the bios just to see if I could discern any changes, when I
did, a page came asking if I was going to keep the Opensuse OS, which
had captured the difference between the 442 and the original 512.

The only options was yes or no, I clicked on no because I was installing
the Mandriva OS. That's when the system locked up and I could not use
the F9 option to restore, nor would it let me install another OS from
installation CD or USB device. Now all that happens is the system does
not see a bootable device to pull up. I was more than most disappointed
that an Open Source OS would do this to an non OEM computer. I would
expect this from Windows or Apple, but not an Open Source platform. The
computer is one of the newer Intel NUCi7 system purchased on Amazon.
Because the system is considered broken, I can't get a refund from
Amazon and I can't install any other system and because I had installed
Mandriva over the original Suse OS, the system won't let me use any
thing on it and it can't no pull up the Suse OS anymore. I don't can't
even pull it up to send the requested files list below. I have no idea
what to do from here.

ProblemType: Bug
DistroRelease: Ubuntu 18.04
Package: ubiquity 18.04.14.12
ProcVersionSignature: Ubuntu 5.0.0-23.24~18.04.1-generic 5.0.15
Uname: Linux 5.0.0-23-generic x86_64
ApportVersion: 2.20.9-0ubuntu7.7
Architecture: amd64
CasperVersion: 1.394
Date: Mon Nov  4 02:49:15 2019
InstallCmdLine: BOOT_IMAGE=/casper/vmlinuz file=/cdrom/preseed/ubuntu-mate.seed boot=casper quiet splash ---
LiveMediaBuild: Ubuntu-MATE 18.04.3 LTS "Bionic Beaver" - Release amd64 (20190805)
SourcePackage: ubiquity
UpgradeStatus: No upgrade log present (probably fresh install)

** Affects: ubiquity (Ubuntu)
     Importance: Undecided
         Status: New


** Tags: amd64 apport-bug bionic ubiquity-18.04.14.12 ubuntu-mate

-- 
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/1851239

Title:
  Open Suse locked down the bios of this computer.

Status in ubiquity package in Ubuntu:
  New

Bug description:
  I installed Open Suse because I had used this OS previously. When I
  pulled up the OS for the first time I noticed the OS had changed since
  the last time I used it. (been on iPad for a while and wanted to go to
  back to an OS I was previously familiar with. I found it had change
  and decided to load Unbuntu Mate instead. I found out a 512GB Sata was
  not recognized trying to install it. I was able to recover 442GB of
  that drive. Puzzled, I just installed Open Mandriva on that. After two
  days, I was not able to use the drive. The software kept saying there
  was no drive to boot up to because an illegal transaction had taken
  place. I went into the bios just to see if I could discern any
  changes, when I did, a page came asking if I was going to keep the
  Opensuse OS, which had captured the difference between the 442 and the
  original 512.

  The only options was yes or no, I clicked on no because I was
  installing the Mandriva OS. That's when the system locked up and I
  could not use the F9 option to restore, nor would it let me install
  another OS from installation CD or USB device. Now all that happens is
  the system does not see a bootable device to pull up. I was more than
  most disappointed that an Open Source OS would do this to an non OEM
  computer. I would expect this from Windows or Apple, but not an Open
  Source platform. The computer is one of the newer Intel NUCi7 system
  purchased on Amazon. Because the system is considered broken, I can't
  get a refund from Amazon and I can't install any other system and
  because I had installed Mandriva over the original Suse OS, the system
  won't let me use any thing on it and it can't no pull up the Suse OS
  anymore. I don't can't even pull it up to send the requested files
  list below. I have no idea what to do from here.

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: ubiquity 18.04.14.12
  ProcVersionSignature: Ubuntu 5.0.0-23.24~18.04.1-generic 5.0.15
  Uname: Linux 5.0.0-23-generic x86_64
  ApportVersion: 2.20.9-0ubuntu7.7
  Architecture: amd64
  CasperVersion: 1.394
  Date: Mon Nov  4 02:49:15 2019
  InstallCmdLine: BOOT_IMAGE=/casper/vmlinuz file=/cdrom/preseed/ubuntu-mate.seed boot=casper quiet splash ---
  LiveMediaBuild: Ubuntu-MATE 18.04.3 LTS "Bionic Beaver" - Release amd64 (20190805)
  SourcePackage: ubiquity
  UpgradeStatus: No upgrade log present (probably fresh install)

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