I aim to run a destructive "badblocks" test from a LiveUSB, assumably via the commandline issue of:
to try to see whether this would solve the deal mentioned in the starter post. I have actually also recently run Bleachbit in a root mode and it deleted one or two large files too much, so I rather reinstall the system than wait until something bugs out in a least expected moment.
The thing with Bleachbit jinxes, I have seen and experienced it already somewhere back in the 2013/2014, when I was checking out on the Bionic Beaver. Expecting a regular WindowsOS style brief cleanup, I was surprised how each time the program showed more contents to get rid of. Giving it a go several times in a row, I found that I effectively wiped out most of my drive.
I am uncertain whether it was Bleachbit though or something else.
Code:
badblocks -wsvto try to see whether this would solve the deal mentioned in the starter post. I have actually also recently run Bleachbit in a root mode and it deleted one or two large files too much, so I rather reinstall the system than wait until something bugs out in a least expected moment.
The thing with Bleachbit jinxes, I have seen and experienced it already somewhere back in the 2013/2014, when I was checking out on the Bionic Beaver. Expecting a regular WindowsOS style brief cleanup, I was surprised how each time the program showed more contents to get rid of. Giving it a go several times in a row, I found that I effectively wiped out most of my drive.
I am uncertain whether it was Bleachbit though or something else.