1. do_gro
2. get_si
3. ? page
4. …
5. Profit.

“Your TV has become a digital billboard.”

It’s been a digital billboard for at least 40 years of my life. Radio was no different, so be sure to drink your Ovaltine.

Have you never seen a commercial before? Cheap subsidized hardware? Bloatware loaded on phones? Bloatware on TVs? Games that require 5 mins of ad time? Google’s crippling of Chrome to break ad blockers? Unskippable ads on YouTube? Sponsored ad spots in YouTube videos? All the 3rd party logos on Smart TV boxes? Product placements in movies? Ad placements before the movie starts? The list goes on.

The entire entertainment industry is based around advertising. Every delivery platform is designed to show you ads first and entertainment second.

People have problems figuring that out?

This isn’t a new concept and it’s really stupid that Ars is presenting it that way.

If companies didn’t know this, then they are already out of business. If the viewers didn’t know this… well… I can’t help you.

It was on old 3.5" drives a long time ago, before anything fancy was ever built into the drives. It was in a seriously rough working environment anyway, so we saw a lot of failed drives. If strange experiments didn’t work to get the things working, mainly for lulz, the next option was to see if a sledge hammer would fix the problem. Funny thing… that never worked either.

I used to take failed drives while they were powered on and kinda snap them really with a fast twisting motion in an attempt to get the arm to move or get the platters spinning.

It never worked.

Did you get bad sectors? Weird things can absolutely happen but having sectors marked as bad is on the exceptional side of weird.

Maybe? Bad cables are a thing, so it’s something to be aware of. USB latency, in rare cases, can cause problems but not so much in this application.

I haven’t looked into the exact ways that bad sectors are detected, but it probably hasn’t changed too much over the years. Needless to say, info here is just approximate.

However, marking a sector as bad generally happens at the firmware/controller level. I am guessing that a write is quickly followed by a verification, and if the controller sees an error, it will just remap that particular sector. If HDDs use any kind of parity checks per sector, a write test may not be needed.

Tools like CHKDSK likely step through each sector manually and perform read tests, or just tells the controller to perform whatever test it does on each sector.

OS level interference or bad cables are unlikely to cause the controller to mark a sector as bad, is my point. Now, if bad data gets written to disk because of a bad cable, the controller shouldn’t care. It just sees data and writes data. (That would be rare as well, but possible.)

What you will see is latency. USB can be magnitudes slower than SATA. Buffers and wait states are causing this because of the speed differences. This latency isn’t going to cause physical problems though.

My overall point is that there are several independent software and firmware layers that need to be completely broken for a SATA drive to erroneously mark a sector as bad due to a slow conversion cable. Sure, it could happen and that is why we have software that can attempt to repair bad sectors.

An I beam trolley in your kitchen is awesome for those times you need a place for a chain to hoist the engine out of your car and then move that engine into your living room.

Also, when your floor is lava, you possibly have an escape route now.