Jump to content

  • twitter
  • youtube

Welcome to UPES - Tech Community | Dehradun


Sign In 

Create Account
Welcome to UPES - Tech Community | Dehradun, like most online communities you must register to view or post in our community, but don't worry this is a simple free process that requires minimal information for you to signup. Be apart of UPES - Tech Community | Dehradun by signing in or creating an account.
  • Start new topics and reply to others
  • Subscribe to topics and forums to get email updates
  • Get your own profile page and make new friends
  • Send personal messages to other members.
  • Online chat support - 24/7 for your queries,engage with others.
 

Toggle %s About US

UPES - Tech Community helps the students to find study materials for different engineering specialties like mechanical, civil, electrical, computer science and electronics etc.The community is also sharing the year wise question papers of UPES, Dehradun and even comprised up with latest technology aspects, news, events, tutorials and various types of digital gadget reviews.

Photo

Running ‘rm -rf –no-preserve-root /’ Command In Linux Can Kill Some Laptops Permanently


No replies to this topic

#1 ilLuSion

ilLuSion

    Founder

  • Founder
  • 823 posts
  • 43 thanks
  • LocationDream World

Posted 26 May 2016 - 08:23 PM

In early January, a user posted on the Arch Linux forums telling how he bricked his own laptop after running a single ‘rm -rf –no-preserve-root /’  command. However, this command is known to erase the current Linux installation and nothing else. Well, this world isn’t a simple place and the Arch Linux forum user 9233 is a living example of the same.

 

To get rid of the Arch Linux installation on his MSI Notebook by avoiding simple reinstallation, he decided to run this command. Afterwards, when he tried to boot into the BIOS, it didn’t work.

On the Arch Linux forum, he writes:

“So today me and a friend ran “rm -rf –no-preserve-root /” on a MSI Notebook because we wanted to get rid of the pretty bloated Arch installation. Of course we could have just formatted  the root partition and reinstalled Arch. But instead we thought it would be fun seeing the GNOME installation die. We weren’t dumb enough to leave important partitions mounted. We unmounted everything except of root (/).”

Explaining the unfortunate outcome, he writes:

“But the unpleasant surprise came when we tried to boot into the BIOS afterwards:
It didn’t work. The screen stays off, the HDD LED turns on for a second but nothing else happens.”

It’s possible that the folder at /sys/firmware/efi/efivars/ was destroyed due to the command. This location stores the scripts and information used to boot the computer. If something happens to /sys/firmware/efi/efivars/ , the computer is hard bricked and it fails to turn on anymore.

At the moment, this issue is reported only in MSI laptops. However, in the comments following the original rant, one user complained about the same issue reported in his Lenovo machine.

Whatever the reason may be, losing your machine permanently is very frustrating. The fossBytes readers are advised to format their machines in case they want to erase a Linux installation.

— Arch Linux Forum





Reply to this topic



  


0 user(s) are reading this topic

0 members, 0 guests, 0 anonymous users



Discussion | Topics
Community Guidance
Useful Resources
Connect With Us

Copyright © 2018 UPES - Tech Community | Dehradun. All Rights Reserved.