@lambdacalculus also "#HardwareRAID" only exist for garbage OSes like #Windows that don't have a proper #VolumeManager nor proper #filesystems!

@ezio Not sure if you saw my post on the matter but uh... avoid #RAID.

https://mastodon.top/@lispi314/110977299337341764

Software RAID isn't much better generally, it still (to its fault) relies on the hardware telling something is wrong.

That was only a sane assumption on specific hardware in the past, but relying on the firmware of the drives themselves? That was *never* a sane assumption.

#SoftRAID #HardwareRAID

LisPi (@[email protected])

So as I suspected but didn't quite remember, no, #RAID users weren't completely flippant or ignorant about #DataIntegrity & #bitrot in the past. And indeed it *was* handled properly by #hardware RAID of the time. That "handling it properly" part has been lost now though, along the usual regression of so many things. Modern RAID *doesn't* do anything to meaningfully ensure #integrity. It used to. Some video: https://youtu.be/l55GfAwa8RI #storage #redundancy #retrocomputing (sort of)

Mastodon.top

The #wikipedia page on #RAID would need some love, really.

To explain for instance that #hardwareRAID used strategies such as inline #EDAC appended to oversized sectors (512b vs 520b) so that #DataIntegrity could be assured regardless of the reliability or lack thereof from a given drive & its firmware.

It's a lot more recent that these features were dropped for the ever-so-idiotic "more speed lol" reasons.

#ErrorDetectionAndCorrection #ErrorDetection #Hardware #retrocomputing