Hi Woodzy, note that android-androresolvd only makes sense in chroot-style environments -- you don't want it installed otherwise.
There's also a bunch of errors in your logs that look like they may be failing hardware:
199.316608] ata3.00: status: { DRDY ERR } [ 199.316611] ata3.00: error: { ABRT } [ 199.316616] ata3.00: failed command: WRITE FPDMA QUEUED [ 199.316626] ata3.00: cmd 61/08:a0:b0:55:0f/00:00:55:00:00/40 tag 20 ncq dma 4096 out res 41/04:00:00:00:00/04:00:00:00:00/00 Emask 0x1 (device error) [ 199.316631] ata3.00: status: { DRDY ERR } [ 199.316635] ata3.00: error: { ABRT } [ 199.316639] ata3.00: failed command: WRITE FPDMA QUEUED [ 199.316649] ata3.00: cmd 61/10:a8:08:51:0f/00:00:55:00:00/40 tag 21 ncq dma 8192 out res 41/04:00:00:00:00/04:00:00:00:00/00 Emask 0x1 (device error) [ 199.316655] ata3.00: status: { DRDY ERR }
Good luck
Hi Woodzy, note that android- androresolvd only makes sense in chroot-style environments -- you don't want it installed otherwise.
There's also a bunch of errors in your logs that look like they may be failing hardware:
199.316608] ata3.00: status: { DRDY ERR } b0:55:0f/ 00:00:55: 00:00/40 tag 20 ncq dma 4096 out
res 41/04:00: 00:00:00/ 04:00:00: 00:00/00 Emask 0x1 (device error) 08:51:0f/ 00:00:55: 00:00/40 tag 21 ncq dma 8192 out
res 41/04:00: 00:00:00/ 04:00:00: 00:00/00 Emask 0x1 (device error)
[ 199.316611] ata3.00: error: { ABRT }
[ 199.316616] ata3.00: failed command: WRITE FPDMA QUEUED
[ 199.316626] ata3.00: cmd 61/08:a0:
[ 199.316631] ata3.00: status: { DRDY ERR }
[ 199.316635] ata3.00: error: { ABRT }
[ 199.316639] ata3.00: failed command: WRITE FPDMA QUEUED
[ 199.316649] ata3.00: cmd 61/10:a8:
[ 199.316655] ata3.00: status: { DRDY ERR }
Good luck