You also might try a known good power supply as well. You should definitely try the drive on another system if you can't do that, and/or try another drive with the current mother board. With the errors being different over time it could easily be nearly any component in the system. Symptoms are sometimes misleading, trouble shooting is difficult for most people, sometimes even for people who are usually good at it and experienced. Root causes are often obscured and failures can propagate in unforeseen ways even for the experienced. Testing suspect components in another system and/or substituting known good components into the failing system are the most useful for trouble shooting, but you have to remember what you've tested and what it suggested and recheck when it doesn't make sense.
-- “The whole world is watching! The whole world is watching!” Jun 18, 2020, 18:28 by [email protected]: > On Fri, Jun 19, 2020 at 8:48 AM Michael <> [email protected]> > wrote: > >> It started thus: >> >> Jun 18 17:52:45 asus kernel: ata1.00: exception Emask 0x0 SAct 0x2 SErr 0x0 >> action 0x6 frozen >> Jun 18 17:52:45 asus kernel: ata1.00: failed command: WRITE FPDMA QUEUED >> Jun 18 17:52:45 asus kernel: ata1.00: cmd >> 61/20:08:60:f1:90/00:00:02:00:00/40 >> tag 1 ncq dma 16384 out\x0a res 40/00:01:00:4f:c2/00:00:00:00:00/00 >> Emask 0x4 (timeout) >> <snip> >> > > What does smartctl -a /dev/sda report? > > Tried replacing the cable? >
