Asklemmy

43945 readers

493 users here now

A loosely moderated place to ask open-ended questions

If your post meets the following criteria, it's welcome here!

Open-ended question
Not offensive: at this point, we do not have the bandwidth to moderate overtly political discussions. Assume best intent and be excellent to each other.
Not regarding using or support for Lemmy: context, see the list of support communities and tools for finding communities below
Not ad nauseam inducing: please make sure it is a question that would be new to most members
An actual topic of discussion

Looking for support?

Looking for a community?

~Icon~ ~by~ ~@Double_A@discuss.tchncs.de~

founded 5 years ago

MODERATORS

150

submitted 10 months ago by oriond@lemmy.ml to c/asklemmy@lemmy.ml

136 comments fedilink hide all child comments

you are viewing a single comment's thread
view the rest of the comments

[–] user224@lemmy.sdf.org 14 points 10 months ago* (last edited 10 months ago)

I don't know about how exactly to do it, but I do have an idea or two.

Something that will reflash the firmware on as many devices as possible using garbage data. At least the UEFI.
Filling most of the drive space, leaving let's say 50MB, then overwriting those 50MB repeatedly to damage the hardware itself. I suppose you could do the same with RAM. If we're dealing with PMR/CMR HDD, then you should just be able to write to specific sectors without doing it by filling the rest.
If present, keep ejecting the DVD drive. Either the mechanism dies or someone accidentally bumps into the open tray and breaks it off.
Keep hard rebooting the laptop after some time. It may corrupt some data, and put the blame on hardware. The hard reboot can be done by echo b > /proc/sysrq-trigger This will need magic SysRq compiled into the kernel, and power off/reboot enabled. The latter can be done by enabling all magic SysRq functions echo 1 > /proc/sys/kernel/sysrq or just reboot/power off with "128".