Bug 749325 - Lenovo Thinkpads should be blacklisted to ms-dos labels
Lenovo Thinkpads should be blacklisted to ms-dos labels
Product: Fedora
Classification: Fedora
Component: anaconda (Show other bugs)
Unspecified Unspecified
unspecified Severity unspecified
: ---
: ---
Assigned To: David Lehman
Fedora Extras Quality Assurance
Depends On:
Blocks: F16Blocker/F16FinalBlocker
  Show dependency treegraph
Reported: 2011-10-26 14:03 EDT by Tom "spot" Callaway
Modified: 2012-04-15 03:32 EDT (History)
11 users (show)

See Also:
Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
Last Closed: 2011-10-29 02:42:29 EDT
Type: ---
Regression: ---
Mount Type: ---
Documentation: ---
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---

Attachments (Terms of Use)

  None (edit)
Description Tom "spot" Callaway 2011-10-26 14:03:51 EDT
For technical background, see https://bugzilla.redhat.com/show_bug.cgi?id=735733

But the summary is this: Most of the Lenovo Thinkpads in use will not boot after a Fedora 16 install with GPT disk label. They need the boring MSDOS disk labels. 735733 adds the "nogpt" flag, however, given the common use case of Lenovo Thinkpads and Fedora, we need to check the DMI for Lenovo and if found, default to the MSDOS disk labels in this case, without the need for any magic boot flags.
Comment 1 Adam Williamson 2011-10-26 14:05:59 EDT
fwiw, I personally am +1 blocker on this, we ought to blacklist thinkpads to ms-dos labels. it's just a much better situation to have, say, 50% of thinkpads using msdos disklabels when they don't really need to, than to have, say, 50% of thinkpads fail to boot after install. we don't know _exactly_ what that ratio is, but anything inside of 20/80 in either direction would give the same result, for me.
Comment 2 Adam Williamson 2011-10-26 14:14:56 EDT
oh, to avoid an obvious gotcha: any blacklist should only apply to *non*-EFI installs. obviously we'd still want to use gpt labels when doing an EFI install on a Thinkpad, I think...
Comment 3 Tom "spot" Callaway 2011-10-26 14:31:17 EDT
Docked Lenovo Thinkpad T500

[spot@pterodactyl ~]$ sudo dmidecode -s "chassis-manufacturer"
[spot@pterodactyl ~]$ sudo dmidecode -s "chassis-type"
Peripheral Chassis

Lenovo Thinkpad X220 Tablet (also in an ultradock, but dmidecode doesn't see that)

[spot@pandamotor ~]$ sudo dmidecode -s "chassis-manufacturer"
[spot@pandamotor ~]$ sudo dmidecode -s "chassis-type"
Comment 4 David Lehman 2011-10-26 14:58:04 EDT
To test this abomination, add the following to your boot or liveinst command line:


Let me know how it goes, of course.
Comment 5 Adam Williamson 2011-10-26 15:34:46 EDT
pjones confirmed this does indeed create msdos label on a thinkpad, and i confirmed it still creates gpt label on a VM, so looks good.
Comment 6 Adam Williamson 2011-10-26 15:37:45 EDT
note that a consequence of this fix will be that you won't be able to install to >2TB disks in Lenovo systems, I think, unless you use EFI or pre-format the drive and ensure anaconda doesn't re-format the whole thing.
Comment 7 Robyn Bergeron 2011-10-26 16:26:10 EDT
+1, blocker
Comment 8 Adam Williamson 2011-10-26 16:27:47 EDT
for those playing along at home with pocket protectors, the criterion here is "In most cases (see Blocker_Bug_FAQ), a system installed according to any of the above criteria (or the appropriate Beta or Final criteria, when applying this criterion to those releases) must boot to the 'firstboot' utility on the first boot after installation, without unintended user intervention, unless the user explicitly chooses to boot in non-graphical mode. This includes correctly accessing any encrypted partitions when the correct passphrase is supplied. The firstboot utility must be able to create a working user account" (Alpha). Affected systems boot to a black screen after install, not firstboot. =)
Comment 9 Adam Williamson 2011-10-26 16:36:54 EDT
we have devel +1 (spot), qa +1 (me), program manager +1 (rberge), that's good enough for government work. acceptedblocker.
Comment 10 Fedora Update System 2011-10-26 17:06:04 EDT
anaconda-16.24-1.fc16 has been submitted as an update for Fedora 16.
Comment 11 Adam Williamson 2011-10-28 14:59:59 EDT
Can someone with an affected system please just verify that this is fixed in TC3?


we're 99% sure it is, but just for the record. thanks!
Comment 12 Adam Williamson 2011-10-29 02:42:29 EDT
anaconda 16.24-2 (glibc rebuild) went stable, so CLOSING. We could still do with verification that this is fixed in TC3 or pending RC1. Thanks!

Fedora Bugzappers volunteer triage team
Comment 13 John L Magee 2011-10-29 20:19:58 EDT
works on Lenovo W510 if the drive is completely repartioned. Did not work when attempting to use existing F16 Beta partitions.
Comment 14 Adam Williamson 2011-10-29 20:33:35 EDT
yes, that would be expected. it's only going to change the disk label when completely reformatting the drive.

Fedora Bugzappers volunteer triage team
Comment 15 Charles R. Anderson 2011-10-31 10:20:00 EDT
Workaround confirmed on ThinkPad T520.

Note You need to log in before you can comment on or make changes to this bug.