- Joined
- Aug 8, 2005
- Messages
- 100
- Reaction score
- 15
I am attempting to install Linux Mint 18.2 xfce on an Medion MD96630 laptop (CPU Intel 2-core 1.6 GHz and 4 GB of DDR2 RAM). I can't rely on booting into a USB live session to complete an interrupted installation and after automatic boot get a screen similar to that I have appended below.
From reading on the Internet I have been led to think I have a failing HDD or RAM. Has any Linux user here got any idea what I may conclude from the screen output which repeats on and on and eventually will end with a desktop-like display of a Linux Mint log-in screen which will not accept the user name and password I set initially.
Screen Image Output Text Follows:
[ 12.776641] sd 6:0:0:0: [sdb] No Caching mode page found
[ 12,776668] sd 6:0:0:0: [sdb] Assuming drive cache: write through
[ 62.444062] ata4,00: exception Emask 0x0 SAct 0x60000000 SErr 0x0action 0x6 frozen
[ 62.444085] ata4,00: failed command: READ FPDMA QUEUED
[ 62.444099] ata4.00: cmd 60/38E8:e8:40:00:00/00:00:00:00/40 tag 29 ncq dma 28672 in
[ 62.444099] res 40/00:00:00:00:00:00:00:00:00:00:00/00 Emask 0x4 (timeout)
[ 62.444118] ata4,00: status: { DRDY }
[ 62.444127] ata4,00: failed command: READ FPDMA QUEUED
[ 62.444139] ata4,00: cmd 60/90:f0:80:00:00/00:00:00:00:00/ tag 30 ncq dma 73728 in
[ 62.444139] res 40/00:00:00:00:00/00:00:00:00:00/00 Emask 0x4 (timeout)
[ 62.444156] ata4,.00: status: { DRDY }
[ 93.164052] ata4.00: exception Emask 0x0 SAct 0x2 SErr 0x0 action 0x6 frozen
[ 93,164073] ata4.00: failed command: READ FPDMA QUEUED
[ 93.164087] ata4,00: cmd 60/90:08:80:00:00/00:00:00:00:00/40 tag 1 ncq dma73728 in
[ 93.164087] res 40/00:00:00:00:00/00:00:00:00:00/00 Emask 0x4 (timeout)
[ 93.164106] ata4,00: status: { DRDY }
[ 123.884051] ata4,00: exception Emask 0x0 SAct 0x10000 SErr 0x0 action 0x6 frozen
[ 123.884072] ata4,00: failed command: READ FDMA QUEUED
[ 123.884086] ata4,00: cmd 60/90: 8O :80 :00:00/00:00:00:00:00/40 tag 16 ncq dma 73728 in
[ 123.889086] res 40/00:00:00:00:00/00:00:00:00:00/00 Emask 0x4 (timeout)
[ 123.884105] ata4.00: status: { DRDY }
[ 156.652066] ata4,00: exception Emask 0x0 SAct 0X40000000 SErr 0x0 action 0x6 frozen
[ 156.652090] ata4,00: failed command: READ FPDMA QUEUED
[ 156.652104] ata4,00: cmd 60/90:f0:80:00:00/00:00:00:00:00/40 tag 30 ncq dma73728 in
[ 156,652104] res 40/00:00:00:00:00/00:00:00:00:00/00 Emask 0x4 (timeout)
[ 156.652122] ata4.00: status: { DRDY }
[ 189.420040] ata,4.00: exception Emask 0x0 SAct 0x40000000 SErr 0x0 action 0x6 frozen
[ 189.420060] ata4,00: failed command READ DMA
[ 189.420073] ata4,00: cmd c8/00:90: 80 :00 :00/00:00 :00:00:00/e0 tag 13 dma 73728 in
[ 189.420073] res 40/00:00:00:00:00/00:00:00:00:00/00 Emask 0x4 (timeout)
[ 189.920091] ata4,00: status: { DRDY }
[ 220.140056] ata4,00: exception Emask 0xO SAct 0X0 SErr 0x0 action 0x6 frozen
[ 220.140078] ata4,00: failed command; READ DMA
[ 220.140091] ata4,00: cmd c8/00:90:80:00:00/00:00:00:00:00/e0 tag 13 dma 73728 in
[ 220,140091] res 40/00:00:00:00:00/00:00:00:00:00 Emask 0x4 (timeout)
[ 220,190110] ata4,00 status: { DRDY }
[ 220,509204] blk_update_request: I/0 error, dev sda, sector 128
From reading on the Internet I have been led to think I have a failing HDD or RAM. Has any Linux user here got any idea what I may conclude from the screen output which repeats on and on and eventually will end with a desktop-like display of a Linux Mint log-in screen which will not accept the user name and password I set initially.
Screen Image Output Text Follows:
[ 12.776641] sd 6:0:0:0: [sdb] No Caching mode page found
[ 12,776668] sd 6:0:0:0: [sdb] Assuming drive cache: write through
[ 62.444062] ata4,00: exception Emask 0x0 SAct 0x60000000 SErr 0x0action 0x6 frozen
[ 62.444085] ata4,00: failed command: READ FPDMA QUEUED
[ 62.444099] ata4.00: cmd 60/38E8:e8:40:00:00/00:00:00:00/40 tag 29 ncq dma 28672 in
[ 62.444099] res 40/00:00:00:00:00:00:00:00:00:00:00/00 Emask 0x4 (timeout)
[ 62.444118] ata4,00: status: { DRDY }
[ 62.444127] ata4,00: failed command: READ FPDMA QUEUED
[ 62.444139] ata4,00: cmd 60/90:f0:80:00:00/00:00:00:00:00/ tag 30 ncq dma 73728 in
[ 62.444139] res 40/00:00:00:00:00/00:00:00:00:00/00 Emask 0x4 (timeout)
[ 62.444156] ata4,.00: status: { DRDY }
[ 93.164052] ata4.00: exception Emask 0x0 SAct 0x2 SErr 0x0 action 0x6 frozen
[ 93,164073] ata4.00: failed command: READ FPDMA QUEUED
[ 93.164087] ata4,00: cmd 60/90:08:80:00:00/00:00:00:00:00/40 tag 1 ncq dma73728 in
[ 93.164087] res 40/00:00:00:00:00/00:00:00:00:00/00 Emask 0x4 (timeout)
[ 93.164106] ata4,00: status: { DRDY }
[ 123.884051] ata4,00: exception Emask 0x0 SAct 0x10000 SErr 0x0 action 0x6 frozen
[ 123.884072] ata4,00: failed command: READ FDMA QUEUED
[ 123.884086] ata4,00: cmd 60/90: 8O :80 :00:00/00:00:00:00:00/40 tag 16 ncq dma 73728 in
[ 123.889086] res 40/00:00:00:00:00/00:00:00:00:00/00 Emask 0x4 (timeout)
[ 123.884105] ata4.00: status: { DRDY }
[ 156.652066] ata4,00: exception Emask 0x0 SAct 0X40000000 SErr 0x0 action 0x6 frozen
[ 156.652090] ata4,00: failed command: READ FPDMA QUEUED
[ 156.652104] ata4,00: cmd 60/90:f0:80:00:00/00:00:00:00:00/40 tag 30 ncq dma73728 in
[ 156,652104] res 40/00:00:00:00:00/00:00:00:00:00/00 Emask 0x4 (timeout)
[ 156.652122] ata4.00: status: { DRDY }
[ 189.420040] ata,4.00: exception Emask 0x0 SAct 0x40000000 SErr 0x0 action 0x6 frozen
[ 189.420060] ata4,00: failed command READ DMA
[ 189.420073] ata4,00: cmd c8/00:90: 80 :00 :00/00:00 :00:00:00/e0 tag 13 dma 73728 in
[ 189.420073] res 40/00:00:00:00:00/00:00:00:00:00/00 Emask 0x4 (timeout)
[ 189.920091] ata4,00: status: { DRDY }
[ 220.140056] ata4,00: exception Emask 0xO SAct 0X0 SErr 0x0 action 0x6 frozen
[ 220.140078] ata4,00: failed command; READ DMA
[ 220.140091] ata4,00: cmd c8/00:90:80:00:00/00:00:00:00:00/e0 tag 13 dma 73728 in
[ 220,140091] res 40/00:00:00:00:00/00:00:00:00:00 Emask 0x4 (timeout)
[ 220,190110] ata4,00 status: { DRDY }
[ 220,509204] blk_update_request: I/0 error, dev sda, sector 128