Ubuntu 17.10 no longer available for download due to LENOVO bios getting corrupted

ubuntu-17-download-disabledubuntu-17-download-disabled
Lenovo is a Chinese multinational technology company that is well known for LENOVO laptops, desktops and other IT equipment. The download of Ubuntu Linux 17.10 is currently discouraged due to an issue on specific Lenovo laptop models that are causing BIOS corruption or laptop bricking.

ADVERTISEMENT
find out your Linux distro name/release:
$ lsb_release -a
Sample outputs:

No LSB modules are available.
Distributor ID:	Ubuntu
Description:	Ubuntu 17.10
Release:	17.10
Codename:	artful

Linux kernel version:
$ uname -r
4.13.0-19-generic

You can use the dmidecode command to find out more about your bios and laptop too:
$ sudo dmidecode | more
$ sudo dmidecode -t 1

Sample outputs:

# dmidecode 3.1
Getting SMBIOS data from sysfs.
SMBIOS 2.7 present. Handle 0x000D, DMI type 1, 27 bytes
System Information Manufacturer: LENOVO Product Name: 2325YX3 Version: ThinkPad X230 Serial Number: xxxxxx UUID: 78E94B81-5244-11CB-BF24-zzzzzzzz Wake-up Type: Power Switch SKU Number: LENOVO_MT_2325 Family: ThinkPad X230

A note about other Linux distros

The bug seems to related to intel-spi-* drivers in the Linux kernel. So it is entirely possible that other Linux distro might be affected too. Check your Linux distribution mailing list or bug tracker for more info.

Bricking Linux based systems using rm

This reminds me of an older bug in BIOS. Back in 2016 many Linux based system were affected by another bug:

Deleting all files starting at the root (i.e. rm -rf /) is generally ill-advised; it is almost always a mistake of some sort. But, even if it is done intentionally, a permanently unbootable system—a brick—is not expected to be the result. The rm command can cause all of the Extensible Firmware Interface (EFI) variables to be cleared; due to some poorly implemented firmware in some systems, that can render the device permanently unable to even run the start-up firmware.

What should I do next?

You need to wait until Ubuntu release fix. Do not install Ubuntu 17.10 on affected devices. See the following links for more info:

Posted by Contributor