Orochimaru wrote:TorTorden wrote:Sounds like corrupted files.
I would wipe the install completely and start from scratch with a new install on the launcher.
But more importantly I would look into getting a new system drive asap.
If it's having issues it's not going to stop. And the next failure might be complete.
Drive already take care of. No more problems from that, using SSD and Raid0+1.
Next step is getting me back on the cockpit!
Thanks for the suggestion CMDR TorTorden o7
Sent from my LON-L29 using Tapatalk
Commodity firmware-Driver (aka Fake) RAID with consumer NAND SSD devices can be troublesome.
This is because they have huge DRAM write buffers (because NAND cell writes, especially 3-bit MLC aka TLC, are slow and error prone as piss, long story). Without enough capacitance, they aren't always flushed, leading to corruptions, if a system freezes or often -- as a result of the RAID abstraction -- the OS powering the hardware off, before the DRAM buffer is committed to the NAND cells.
Most of us who have a lot of embedded experience (including Embedded Windows, and understand how the overlay driver in Embedded NT works) have been warning about this for years. It never gets addressed by Intel-Microsoft, like the Linux kernel does.
_SIDE NOTE: there are some great dislikes of Samsung's EVO/PRO devices by Linux developers for a reason_
Until Intel gets serious about putting NVDRAM on the main board itself, used as the buffer for NAND (and platter for that matter), this will continue. In Intel's defense, the Windows NT kernel is really incapable of doing Device Mapping so you can have the OS use one device to buffer, cache and/or otherwise as backing/store for another.
Hence why, for Windows, I just get a simple 240-256GB (or 480-512GB) NAND device, and a pair of platters in RAID-1. A 192GB C: w/C:\Windows goes on the NAND (384GB w/C:\SteamSSD for larger), and then the RAID-1 platter w/D:\Program Files\Steam.
I then dual boot Linux, using 32GB on the NAND and 0.5TB of the RAID-1 platter, and DD (raw sector copy) the C: drive. That way, I'd Windows self-toasts, I just boot Linux and DD back the last C: drive image.
Sent from my FRD-L04 using Tapatalk