p.H wrote:but it seems that both errors happen at the same time, so I suspect that the bad sectors may be the initial cause. I have seen drives going completely offline when trying hard to read bad sectors.
Your words link together several issues that I have been experiencing.
The output of smartctl
indicates that the disk errors occurred on 28 Aug 2016, but I did not notice any problems until I upgraded from Wheezy to Stretch, two years later. smartctl
also indicates that there were bad sectors on both the / (root)
So I wonder if the bad sectors on / (root)
caused the "black screen of death"
issues that I had with Debian Stretch. I wonder if the drive was "going completely offline" just like you described.
It's too late to know now, because I reformatted the / (root)
partition when I installed Buster. The reinstall resolved the "black screen of death" issue, but now I am having trouble with the /home
partition, which I did not reformat.
p.H wrote:e2fsck detects and marks bad blocks only when run with the -c option.
I did not use that option when I ran the file system checks from a Live CD. Could that have been my mistake? Is that why I'm still having trouble with the /home
We'll find out soon enough! .
p.H wrote:KDE and systemd cannot be blamed for bad sectors. Neither a graphic card
Please excuse me. I was trying to summarize several posts in a handful of words.
I was just trying to say that several other people are seeing their partitions not unmount during shutdown. The issues that they experienced were similar, but they all pointed their fingers at different software packages, graphics cards, etc. I should have expressed that point more clearly.
I'm going to try e2fsck -c
and see what happens. Wish me luck!
Thanks again for your help! I will let you know what I find.