BigBadBeef
Active Member
I got 3 hard drives:
- M.2 prototype from 2015 with a 128GB capacity,
- Western Digital Black edition 2TB hard drive from 2014,
- 512GB SSD from 2020.
The M.2 contains pop!_os and utilizes the SSD for extended storage, while the 2TB HDD Contains windows.
Barring the details aside, lets just say I've kept them completely separated to the point that each contains their own bootloader and cannot see the other OS at all, with the exception that pop!_os can transfer files to and from the windows drive.
This has proven a wise course of action because my windows installation just wrecked itself. And I've done nothing, literally nothing! I couldn't have gotten any malware on whatsoever because I haven't even downloaded anything aside from the drivers from their official websites.
I used the windows installation for VR and nothing else, because I don't need it for anything else. I also have the habit of leaving my computer on 24/7. At nights, when I go to sleep, if I run Linux, the computer is dead quiet, not a beep.
But if I run windows, I just keep hearing the HDD crunching, the are fans spooling up and down, indicating sporadic processor activity, and all kinds of stuff.
Well, recently, one of it's standard nonsensical update shenanigans took place, and for some damn reason, windows decided that there is something wrong with the hard drive, forcing me to use its repair utility.
Well, the repair utility failed, the update failed, and the windows 10 installation is completely wrecked. it boots, but it takes forever, zero hard drive activity. But the drive is fine, I have drive health utilities active on linux that also monitor the windows disk, and other than some age related reports, the drives are completely healthy!
So yeah, windows 10 trashed itself, and now I'm stuck with salvaging data on mangled drive contents. THANK THE LAAAAAAWD didn't set up a single bootloader, who knows what that Microsoft garbage would have done to it.
It just further reinforces my animosity towards that proprietary cancer.
- M.2 prototype from 2015 with a 128GB capacity,
- Western Digital Black edition 2TB hard drive from 2014,
- 512GB SSD from 2020.
The M.2 contains pop!_os and utilizes the SSD for extended storage, while the 2TB HDD Contains windows.
Barring the details aside, lets just say I've kept them completely separated to the point that each contains their own bootloader and cannot see the other OS at all, with the exception that pop!_os can transfer files to and from the windows drive.
This has proven a wise course of action because my windows installation just wrecked itself. And I've done nothing, literally nothing! I couldn't have gotten any malware on whatsoever because I haven't even downloaded anything aside from the drivers from their official websites.
I used the windows installation for VR and nothing else, because I don't need it for anything else. I also have the habit of leaving my computer on 24/7. At nights, when I go to sleep, if I run Linux, the computer is dead quiet, not a beep.
But if I run windows, I just keep hearing the HDD crunching, the are fans spooling up and down, indicating sporadic processor activity, and all kinds of stuff.
Well, recently, one of it's standard nonsensical update shenanigans took place, and for some damn reason, windows decided that there is something wrong with the hard drive, forcing me to use its repair utility.
Well, the repair utility failed, the update failed, and the windows 10 installation is completely wrecked. it boots, but it takes forever, zero hard drive activity. But the drive is fine, I have drive health utilities active on linux that also monitor the windows disk, and other than some age related reports, the drives are completely healthy!
So yeah, windows 10 trashed itself, and now I'm stuck with salvaging data on mangled drive contents. THANK THE LAAAAAAWD didn't set up a single bootloader, who knows what that Microsoft garbage would have done to it.
It just further reinforces my animosity towards that proprietary cancer.