BTRFS is smart enough to check for file errors in some situations under normal operations (I forget which, it’s been a while). When it finds issues, it puts it in read only to try and prevent things from going off of potentially corrupt data.

NTFS, which is what Windows usually uses, is a very “dumb” file system. It is merely a record of what files exist where, so if data corrupts, it will only throw NTFS off if it’s in the file index it stores itself. If it’s in the middle of your file, NTFS doesn’t know and doesn’t care and will just give you the wonky data.

Windows seemingly continuing to work is just a consequence of the “dumb” file system. It will take some critical file getting corrupted before Windows or some program will just crash. At least BTRFS is trying to tell you things are looking amiss and you should definitely back up anything important.

It depends on the exact nature of the failure. Controller errors are usually a complete failure. Media failure (magnetic spots on the disk or failed cells in ssd) are often sporadic and only impact data stored in those spots.

Regardless, drives rarely give you any warning. Look at any warning as a gift and get everything off and replace it ASAP.

its a configuration thing… sounds like maybe linux has detected the SMART errors and acted accordingly on its managed partition. windows is not making the same choice.

With the clicking etc it sounds like a mechanical failure?! A harddrive has several disks "platter"s stacked inside and multiple heads inside. They don’t necessarily all fail at the same time. Also sometimes there are just small areas affected that become inaccessible due to various reasons. They’ll probably grow at some point and you’re bound to loose more data. But if it’s an area of several consequtive blocks, it’ll show when you’re accessing those. And if your partitions and data are arranged serially, the next one might be physically stored where everything is still fine.