You are not logged in.

Pages: 1

#1 2009-09-13 18:40:39

monstermudder78
Member
Registered: 2008-05-18
Posts: 120

kernel (or pre-kernel?) filesystem error.

EDIT

Could a mod please move this to the kernel subforum?  I believe the problem to be kernel related.
So basically I have tried everything here to no avail.  I have gone so far as formatting the entire partition as NTFS with my XP install and then re-tried linux and I still get this error.  The error is present no matter what distro I try; arch, ubuntu, xubuntu wubi, everything.  This leads me to believe that the error is from the kernel or even before the kernel, if that is possible?  The error comes up instantly so I believe it must be noted in some type of log file somewhere, but not a log in the ordinary filesystem.  Any ideas?

/EDIT




So here is the story:  I was using firefox last night and tried to view an embedded video, in the middle of the video firefox froze.  I couldn't close firefox, or open any other programs, nor could I change VC's to kill any processes.  I shutdown the computer (Asus eee 1000HE) using the power button, then tried to power back up.  This is the error that came up as arch tried to load:

ata1.00: status: { DRDY ERR }
ata1.00: error: { UNC }
ata1.00: configured for UDMA/133
ata1: EH complete
ata1.00: exception Emask 0x0 SAct 0x0 SErr 0x0 action 0x0
ata1.00: BMDMA stat 0x24
ata1.00: cmd 25/00:08:a8:9e:a1/00:00:12:00:00/e0 tag 0 dma 4096 in
         res 51/40:00:af:9e:a1/40:00:12:00:00/00 Emask 0x9 (media error)

This error basically repeated itself 11tybillion times and then everything ended with a kernal panic.

After some googling and serious hair pulling/banging head on desk I booted up the live Arch usb and used 

fsck -c /dev/sda5

to find and 'repair' 11 blocks with errors that resulted in short reads(?).  (sda5 is my / partition and SEEMS to be the only one with a problem.)

After doing that I got the following error:

sd 0:0:0:0: [sda] 312581808 512-byte hardware sectors: (160 GB/149 GiB)
sd 0:0:0:0: [sda] Write Protect is off
sd 0:0:0:0: [sda] Mode Sense: 00 3a 00 00
sd 0:0:0:0: [sda] Write cache: enabled, read cache: enabled, doesn't support DPO or FUA
 sda: sda1 sda2 < sda5 sda6 sda7 > sda3 sda4
sd 0:0:0:0: [sda] Attached SCSI disk
ata1.00: exception Emask 0x0 SAct 0x0 SErr 0x0 action 0x0
ata1.00: BMDMA stat 0x24
ata1.00: cmd 25/00:08:a8:9e:a1/00:00:12:00:00/e0 tag 0 dma 4096 in
         res 51/40:00:af:9e:a1/40:00:12:00:00/00 Emask 0x9 (media error)
ata1.00: status: { DRDY ERR }
ata1.00: error: { UNC }
ata1.00: configured for UDMA/133
ata1: EH complete
ata1.00: exception Emask 0x0 SAct 0x0 SErr 0x0 action 0x0
ata1.00: BMDMA stat 0x24
ata1.00: cmd 25/00:08:a8:9e:a1/00:00:12:00:00/e0 tag 0 dma 4096 in
         res 51/40:00:af:9e:a1/40:00:12:00:00/00 Emask 0x9 (media error)
ata1.00: status: { DRDY ERR }
ata1.00: error: { UNC }
ata1.00: configured for UDMA/133
ata1: EH complete
ata1.00: exception Emask 0x0 SAct 0x0 SErr 0x0 action 0x0
ata1.00: BMDMA stat 0x24
ata1.00: cmd 25/00:08:a8:9e:a1/00:00:12:00:00/e0 tag 0 dma 4096 in
         res 51/40:00:af:9e:a1/40:00:12:00:00/00 Emask 0x9 (media error)
ata1.00: status: { DRDY ERR }
ata1.00: error: { UNC }
ata1.00: configured for UDMA/133
ata1: EH complete
ata1.00: exception Emask 0x0 SAct 0x0 SErr 0x0 action 0x0
ata1.00: BMDMA stat 0x24
ata1.00: cmd 25/00:08:a8:9e:a1/00:00:12:00:00/e0 tag 0 dma 4096 in
         res 51/40:00:af:9e:a1/40:00:12:00:00/00 Emask 0x9 (media error)
ata1.00: status: { DRDY ERR }
ata1.00: error: { UNC }
ata1.00: configured for UDMA/133
ata1: EH complete
ata1.00: exception Emask 0x0 SAct 0x0 SErr 0x0 action 0x0
ata1.00: BMDMA stat 0x24
ata1.00: cmd 25/00:08:a8:9e:a1/00:00:12:00:00/e0 tag 0 dma 4096 in
         res 51/40:00:af:9e:a1/40:00:12:00:00/00 Emask 0x9 (media error)
ata1.00: status: { DRDY ERR }
ata1.00: error: { UNC }
ata1.00: configured for UDMA/133
ata1: EH complete
ata1.00: exception Emask 0x0 SAct 0x0 SErr 0x0 action 0x0
ata1.00: BMDMA stat 0x24
ata1.00: cmd 25/00:08:a8:9e:a1/00:00:12:00:00/e0 tag 0 dma 4096 in
         res 51/40:00:af:9e:a1/40:00:12:00:00/00 Emask 0x9 (media error)
ata1.00: status: { DRDY ERR }
ata1.00: error: { UNC }
ata1.00: configured for UDMA/133
sd 0:0:0:0: [sda] Unhandled sense code
sd 0:0:0:0: [sda] Result: hostbyte=0x00 driverbyte=0x08
sd 0:0:0:0: [sda] Sense Key : 0x3 [current] [descriptor]
Descriptor sense data with sense descriptors (in hex):
        72 03 11 04 00 00 00 0c 00 0a 80 00 00 00 00 00 
        12 a1 9e af 
sd 0:0:0:0: [sda] ASC=0x11 ASCQ=0x4
end_request: I/O error, dev sda, sector 312581807
Buffer I/O error on device sda, logical block 39072725
ata1: EH complete
ata1.00: exception Emask 0x0 SAct 0x0 SErr 0x0 action 0x0
ata1.00: BMDMA stat 0x24
ata1.00: cmd 25/00:08:a8:9e:a1/00:00:12:00:00/e0 tag 0 dma 4096 in
         res 51/40:00:af:9e:a1/40:00:12:00:00/00 Emask 0x9 (media error)
ata1.00: status: { DRDY ERR }
ata1.00: error: { UNC }
ata1.00: configured for UDMA/133
ata1: EH complete
ata1.00: exception Emask 0x0 SAct 0x0 SErr 0x0 action 0x0
ata1.00: BMDMA stat 0x24
ata1.00: cmd 25/00:08:a8:9e:a1/00:00:12:00:00/e0 tag 0 dma 4096 in
         res 51/40:00:af:9e:a1/40:00:12:00:00/00 Emask 0x9 (media error)
ata1.00: status: { DRDY ERR }
ata1.00: error: { UNC }
ata1.00: configured for UDMA/133
ata1: EH complete
ata1.00: exception Emask 0x0 SAct 0x0 SErr 0x0 action 0x0
ata1.00: BMDMA stat 0x24
ata1.00: cmd 25/00:08:a8:9e:a1/00:00:12:00:00/e0 tag 0 dma 4096 in
         res 51/40:00:af:9e:a1/40:00:12:00:00/00 Emask 0x9 (media error)
ata1.00: status: { DRDY ERR }
ata1.00: error: { UNC }
ata1.00: configured for UDMA/133
ata1: EH complete
ata1.00: exception Emask 0x0 SAct 0x0 SErr 0x0 action 0x0
ata1.00: BMDMA stat 0x24
ata1.00: cmd 25/00:08:a8:9e:a1/00:00:12:00:00/e0 tag 0 dma 4096 in
         res 51/40:00:af:9e:a1/40:00:12:00:00/00 Emask 0x9 (media error)
ata1.00: status: { DRDY ERR }
ata1.00: error: { UNC }
ata1.00: configured for UDMA/133
ata1: EH complete
ata1.00: exception Emask 0x0 SAct 0x0 SErr 0x0 action 0x0
ata1.00: BMDMA stat 0x24
ata1.00: cmd 25/00:08:a8:9e:a1/00:00:12:00:00/e0 tag 0 dma 4096 in
         res 51/40:00:af:9e:a1/40:00:12:00:00/00 Emask 0x9 (media error)
ata1.00: status: { DRDY ERR }
ata1.00: error: { UNC }
ata1.00: configured for UDMA/133
ata1: EH complete
ata1.00: exception Emask 0x0 SAct 0x0 SErr 0x0 action 0x0
ata1.00: BMDMA stat 0x24
ata1.00: cmd 25/00:08:a8:9e:a1/00:00:12:00:00/e0 tag 0 dma 4096 in
         res 51/40:00:af:9e:a1/40:00:12:00:00/00 Emask 0x9 (media error)
ata1.00: status: { DRDY ERR }
ata1.00: error: { UNC }
ata1.00: configured for UDMA/133
sd 0:0:0:0: [sda] Unhandled sense code
sd 0:0:0:0: [sda] Result: hostbyte=0x00 driverbyte=0x08
sd 0:0:0:0: [sda] Sense Key : 0x3 [current] [descriptor]
Descriptor sense data with sense descriptors (in hex):
        72 03 11 04 00 00 00 0c 00 0a 80 00 00 00 00 00 
        12 a1 9e af 
sd 0:0:0:0: [sda] ASC=0x11 ASCQ=0x4
end_request: I/O error, dev sda, sector 312581807
Buffer I/O error on device sda, logical block 39072725
ata1: EH complete
ata1.00: exception Emask 0x0 SAct 0x0 SErr 0x0 action 0x0
ata1.00: BMDMA stat 0x24
ata1.00: cmd 25/00:08:a8:9e:a1/00:00:12:00:00/e0 tag 0 dma 4096 in
         res 51/40:00:af:9e:a1/40:00:12:00:00/00 Emask 0x9 (media error)
ata1.00: status: { DRDY ERR }
ata1.00: error: { UNC }
ata1.00: configured for UDMA/133
ata1: EH complete
ata1.00: exception Emask 0x0 SAct 0x0 SErr 0x0 action 0x0
ata1.00: BMDMA stat 0x24
ata1.00: cmd 25/00:08:a8:9e:a1/00:00:12:00:00/e0 tag 0 dma 4096 in
         res 51/40:00:af:9e:a1/40:00:12:00:00/00 Emask 0x9 (media error)
ata1.00: status: { DRDY ERR }
ata1.00: error: { UNC }
ata1.00: configured for UDMA/133
ata1: EH complete
ata1.00: exception Emask 0x0 SAct 0x0 SErr 0x0 action 0x0
ata1.00: BMDMA stat 0x24
ata1.00: cmd 25/00:08:a8:9e:a1/00:00:12:00:00/e0 tag 0 dma 4096 in
         res 51/40:00:af:9e:a1/40:00:12:00:00/00 Emask 0x9 (media error)
ata1.00: status: { DRDY ERR }
ata1.00: error: { UNC }
ata1.00: configured for UDMA/133
ata1: EH complete
ata1.00: exception Emask 0x0 SAct 0x0 SErr 0x0 action 0x0
ata1.00: BMDMA stat 0x24
ata1.00: cmd 25/00:08:a8:9e:a1/00:00:12:00:00/e0 tag 0 dma 4096 in
         res 51/40:00:af:9e:a1/40:00:12:00:00/00 Emask 0x9 (media error)
ata1.00: status: { DRDY ERR }
ata1.00: error: { UNC }
ata1.00: configured for UDMA/133
ata1: EH complete
ata1.00: exception Emask 0x0 SAct 0x0 SErr 0x0 action 0x0
ata1.00: BMDMA stat 0x24
ata1.00: cmd 25/00:08:a8:9e:a1/00:00:12:00:00/e0 tag 0 dma 4096 in
         res 51/40:00:af:9e:a1/40:00:12:00:00/00 Emask 0x9 (media error)
ata1.00: status: { DRDY ERR }
ata1.00: error: { UNC }
ata1.00: configured for UDMA/133
ata1: EH complete
ata1.00: exception Emask 0x0 SAct 0x0 SErr 0x0 action 0x0
ata1.00: BMDMA stat 0x24
ata1.00: cmd 25/00:08:a8:9e:a1/00:00:12:00:00/e0 tag 0 dma 4096 in
         res 51/40:00:af:9e:a1/40:00:12:00:00/00 Emask 0x9 (media error)
ata1.00: status: { DRDY ERR }
ata1.00: error: { UNC }
ata1.00: configured for UDMA/133
sd 0:0:0:0: [sda] Unhandled sense code
sd 0:0:0:0: [sda] Result: hostbyte=0x00 driverbyte=0x08
sd 0:0:0:0: [sda] Sense Key : 0x3 [current] [descriptor]
Descriptor sense data with sense descriptors (in hex):
        72 03 11 04 00 00 00 0c 00 0a 80 00 00 00 00 00 
        12 a1 9e af 
sd 0:0:0:0: [sda] ASC=0x11 ASCQ=0x4
end_request: I/O error, dev sda, sector 312581807
Buffer I/O error on device sda, logical block 39072725
ata1: EH complete
ata1.00: exception Emask 0x0 SAct 0x0 SErr 0x0 action 0x0
ata1.00: BMDMA stat 0x24
ata1.00: cmd 25/00:08:a8:9e:a1/00:00:12:00:00/e0 tag 0 dma 4096 in
         res 51/40:00:af:9e:a1/40:00:12:00:00/00 Emask 0x9 (media error)
ata1.00: status: { DRDY ERR }
ata1.00: error: { UNC }
ata1.00: configured for UDMA/133
ata1: EH complete
ata1.00: exception Emask 0x0 SAct 0x0 SErr 0x0 action 0x0
ata1.00: BMDMA stat 0x24
ata1.00: cmd 25/00:08:a8:9e:a1/00:00:12:00:00/e0 tag 0 dma 4096 in
         res 51/40:00:af:9e:a1/40:00:12:00:00/00 Emask 0x9 (media error)
ata1.00: status: { DRDY ERR }
ata1.00: error: { UNC }
ata1.00: configured for UDMA/133
ata1: EH complete
ata1.00: exception Emask 0x0 SAct 0x0 SErr 0x0 action 0x0
ata1.00: BMDMA stat 0x24
ata1.00: cmd 25/00:08:a8:9e:a1/00:00:12:00:00/e0 tag 0 dma 4096 in
         res 51/40:00:af:9e:a1/40:00:12:00:00/00 Emask 0x9 (media error)
ata1.00: status: { DRDY ERR }
ata1.00: error: { UNC }
ata1.00: configured for UDMA/133
ata1: EH complete
ata1.00: exception Emask 0x0 SAct 0x0 SErr 0x0 action 0x0
ata1.00: BMDMA stat 0x24
ata1.00: cmd 25/00:08:a8:9e:a1/00:00:12:00:00/e0 tag 0 dma 4096 in
         res 51/40:00:af:9e:a1/40:00:12:00:00/00 Emask 0x9 (media error)
ata1.00: status: { DRDY ERR }
ata1.00: error: { UNC }
ata1.00: configured for UDMA/133
ata1: EH complete
ata1.00: exception Emask 0x0 SAct 0x0 SErr 0x0 action 0x0
ata1.00: BMDMA stat 0x24
ata1.00: cmd 25/00:08:a8:9e:a1/00:00:12:00:00/e0 tag 0 dma 4096 in
         res 51/40:00:af:9e:a1/40:00:12:00:00/00 Emask 0x9 (media error)
ata1.00: status: { DRDY ERR }
ata1.00: error: { UNC }
ata1.00: configured for UDMA/133
ata1: EH complete
ata1.00: exception Emask 0x0 SAct 0x0 SErr 0x0 action 0x0
ata1.00: BMDMA stat 0x24
ata1.00: cmd 25/00:08:a8:9e:a1/00:00:12:00:00/e0 tag 0 dma 4096 in
         res 51/40:00:af:9e:a1/40:00:12:00:00/00 Emask 0x9 (media error)
ata1.00: status: { DRDY ERR }
ata1.00: error: { UNC }
ata1.00: configured for UDMA/133
sd 0:0:0:0: [sda] Unhandled sense code
sd 0:0:0:0: [sda] Result: hostbyte=0x00 driverbyte=0x08
sd 0:0:0:0: [sda] Sense Key : 0x3 [current] [descriptor]
Descriptor sense data with sense descriptors (in hex):
        72 03 11 04 00 00 00 0c 00 0a 80 00 00 00 00 00 
        12 a1 9e af 
sd 0:0:0:0: [sda] ASC=0x11 ASCQ=0x4
end_request: I/O error, dev sda, sector 312581807
Buffer I/O error on device sda, logical block 39072725
ata1: EH complete
ata1.00: exception Emask 0x0 SAct 0x0 SErr 0x0 action 0x0
ata1.00: BMDMA stat 0x24
ata1.00: cmd 25/00:08:a8:9e:a1/00:00:12:00:00/e0 tag 0 dma 4096 in
         res 51/40:00:af:9e:a1/40:00:12:00:00/00 Emask 0x9 (media error)
ata1.00: status: { DRDY ERR }
ata1.00: error: { UNC }
ata1.00: configured for UDMA/133
ata1: EH complete
ata1.00: exception Emask 0x0 SAct 0x0 SErr 0x0 action 0x0
ata1.00: BMDMA stat 0x24
ata1.00: cmd 25/00:08:a8:9e:a1/00:00:12:00:00/e0 tag 0 dma 4096 in
         res 51/40:00:af:9e:a1/40:00:12:00:00/00 Emask 0x9 (media error)
ata1.00: status: { DRDY ERR }
ata1.00: error: { UNC }
ata1.00: configured for UDMA/133
ata1: EH complete
ata1.00: exception Emask 0x0 SAct 0x0 SErr 0x0 action 0x0
ata1.00: BMDMA stat 0x24
ata1.00: cmd 25/00:08:a8:9e:a1/00:00:12:00:00/e0 tag 0 dma 4096 in
         res 51/40:00:af:9e:a1/40:00:12:00:00/00 Emask 0x9 (media error)
ata1.00: status: { DRDY ERR }
ata1.00: error: { UNC }
ata1.00: configured for UDMA/133
ata1: EH complete
ata1.00: exception Emask 0x0 SAct 0x0 SErr 0x0 action 0x0
ata1.00: BMDMA stat 0x24
ata1.00: cmd 25/00:08:a8:9e:a1/00:00:12:00:00/e0 tag 0 dma 4096 in
         res 51/40:00:af:9e:a1/40:00:12:00:00/00 Emask 0x9 (media error)
ata1.00: status: { DRDY ERR }
ata1.00: error: { UNC }
ata1.00: configured for UDMA/133
ata1: EH complete
ata1.00: exception Emask 0x0 SAct 0x0 SErr 0x0 action 0x0
ata1.00: BMDMA stat 0x24
ata1.00: cmd 25/00:08:a8:9e:a1/00:00:12:00:00/e0 tag 0 dma 4096 in
         res 51/40:00:af:9e:a1/40:00:12:00:00/00 Emask 0x9 (media error)
ata1.00: status: { DRDY ERR }
ata1.00: error: { UNC }
ata1.00: configured for UDMA/133
ata1: EH complete
ata1.00: exception Emask 0x0 SAct 0x0 SErr 0x0 action 0x0
ata1.00: BMDMA stat 0x24
ata1.00: cmd 25/00:08:a8:9e:a1/00:00:12:00:00/e0 tag 0 dma 4096 in
         res 51/40:00:af:9e:a1/40:00:12:00:00/00 Emask 0x9 (media error)
ata1.00: status: { DRDY ERR }
ata1.00: error: { UNC }
ata1.00: configured for UDMA/133
sd 0:0:0:0: [sda] Unhandled sense code
sd 0:0:0:0: [sda] Result: hostbyte=0x00 driverbyte=0x08
sd 0:0:0:0: [sda] Sense Key : 0x3 [current] [descriptor]
Descriptor sense data with sense descriptors (in hex):
        72 03 11 04 00 00 00 0c 00 0a 80 00 00 00 00 00 
        12 a1 9e af 
sd 0:0:0:0: [sda] ASC=0x11 ASCQ=0x4
end_request: I/O error, dev sda, sector 312581807
Buffer I/O error on device sda, logical block 39072725
ata1: EH complete
ata1.00: exception Emask 0x0 SAct 0x0 SErr 0x0 action 0x0
ata1.00: BMDMA stat 0x24
ata1.00: cmd 25/00:08:a8:9e:a1/00:00:12:00:00/e0 tag 0 dma 4096 in
         res 51/40:00:af:9e:a1/40:00:12:00:00/00 Emask 0x9 (media error)
ata1.00: status: { DRDY ERR }
ata1.00: error: { UNC }
ata1.00: configured for UDMA/133
ata1: EH complete
ata1.00: exception Emask 0x0 SAct 0x0 SErr 0x0 action 0x0
ata1.00: BMDMA stat 0x24
ata1.00: cmd 25/00:08:a8:9e:a1/00:00:12:00:00/e0 tag 0 dma 4096 in
         res 51/40:00:af:9e:a1/40:00:12:00:00/00 Emask 0x9 (media error)
ata1.00: status: { DRDY ERR }
ata1.00: error: { UNC }
ata1.00: configured for UDMA/133
ata1: EH complete
ata1.00: exception Emask 0x0 SAct 0x0 SErr 0x0 action 0x0
ata1.00: BMDMA stat 0x24
ata1.00: cmd 25/00:08:a8:9e:a1/00:00:12:00:00/e0 tag 0 dma 4096 in
         res 51/40:00:af:9e:a1/40:00:12:00:00/00 Emask 0x9 (media error)
ata1.00: status: { DRDY ERR }
ata1.00: error: { UNC }
ata1.00: configured for UDMA/133
ata1: EH complete
ata1.00: exception Emask 0x0 SAct 0x0 SErr 0x0 action 0x0
ata1.00: BMDMA stat 0x24
ata1.00: cmd 25/00:08:a8:9e:a1/00:00:12:00:00/e0 tag 0 dma 4096 in
         res 51/40:00:af:9e:a1/40:00:12:00:00/00 Emask 0x9 (media error)
ata1.00: status: { DRDY ERR }
ata1.00: error: { UNC }
ata1.00: configured for UDMA/133
ata1: EH complete
ata1.00: exception Emask 0x0 SAct 0x0 SErr 0x0 action 0x0
ata1.00: BMDMA stat 0x24
ata1.00: cmd 25/00:08:a8:9e:a1/00:00:12:00:00/e0 tag 0 dma 4096 in
         res 51/40:00:af:9e:a1/40:00:12:00:00/00 Emask 0x9 (media error)
ata1.00: status: { DRDY ERR }
ata1.00: error: { UNC }
ata1.00: configured for UDMA/133
ata1: EH complete
ata1.00: exception Emask 0x0 SAct 0x0 SErr 0x0 action 0x0
ata1.00: BMDMA stat 0x24
ata1.00: cmd 25/00:08:a8:9e:a1/00:00:12:00:00/e0 tag 0 dma 4096 in
         res 51/40:00:af:9e:a1/40:00:12:00:00/00 Emask 0x9 (media error)
ata1.00: status: { DRDY ERR }
ata1.00: error: { UNC }
ata1.00: configured for UDMA/133
sd 0:0:0:0: [sda] Unhandled sense code
sd 0:0:0:0: [sda] Result: hostbyte=0x00 driverbyte=0x08
sd 0:0:0:0: [sda] Sense Key : 0x3 [current] [descriptor]
Descriptor sense data with sense descriptors (in hex):
        72 03 11 04 00 00 00 0c 00 0a 80 00 00 00 00 00 
        12 a1 9e af 
sd 0:0:0:0: [sda] ASC=0x11 ASCQ=0x4
end_request: I/O error, dev sda, sector 312581807
Buffer I/O error on device sda, logical block 39072725
ata1: EH complete
ata1.00: exception Emask 0x0 SAct 0x0 SErr 0x0 action 0x0
ata1.00: BMDMA stat 0x24
ata1.00: cmd 25/00:08:a8:9e:a1/00:00:12:00:00/e0 tag 0 dma 4096 in
         res 51/40:00:af:9e:a1/40:00:12:00:00/00 Emask 0x9 (media error)
ata1.00: status: { DRDY ERR }
ata1.00: error: { UNC }
ata1.00: configured for UDMA/133
ata1: EH complete
ata1.00: exception Emask 0x0 SAct 0x0 SErr 0x0 action 0x0
ata1.00: BMDMA stat 0x24
ata1.00: cmd 25/00:08:a8:9e:a1/00:00:12:00:00/e0 tag 0 dma 4096 in
         res 51/40:00:af:9e:a1/40:00:12:00:00/00 Emask 0x9 (media error)
ata1.00: status: { DRDY ERR }
ata1.00: error: { UNC }
ata1.00: configured for UDMA/133
ata1: EH complete
ata1.00: exception Emask 0x0 SAct 0x0 SErr 0x0 action 0x0
ata1.00: BMDMA stat 0x24
ata1.00: cmd 25/00:08:a8:9e:a1/00:00:12:00:00/e0 tag 0 dma 4096 in
         res 51/40:00:af:9e:a1/40:00:12:00:00/00 Emask 0x9 (media error)
ata1.00: status: { DRDY ERR }
ata1.00: error: { UNC }
ata1.00: configured for UDMA/133
ata1: EH complete
ata1.00: exception Emask 0x0 SAct 0x0 SErr 0x0 action 0x0
ata1.00: BMDMA stat 0x24
ata1.00: cmd 25/00:08:a8:9e:a1/00:00:12:00:00/e0 tag 0 dma 4096 in
         res 51/40:00:af:9e:a1/40:00:12:00:00/00 Emask 0x9 (media error)
ata1.00: status: { DRDY ERR }
ata1.00: error: { UNC }
ata1.00: configured for UDMA/133
ata1: EH complete
ata1.00: exception Emask 0x0 SAct 0x0 SErr 0x0 action 0x0
ata1.00: BMDMA stat 0x24
ata1.00: cmd 25/00:08:a8:9e:a1/00:00:12:00:00/e0 tag 0 dma 4096 in
         res 51/40:00:af:9e:a1/40:00:12:00:00/00 Emask 0x9 (media error)
ata1.00: status: { DRDY ERR }
ata1.00: error: { UNC }
ata1.00: configured for UDMA/133
ata1: EH complete
ata1.00: exception Emask 0x0 SAct 0x0 SErr 0x0 action 0x0
ata1.00: BMDMA stat 0x24
ata1.00: cmd 25/00:08:a8:9e:a1/00:00:12:00:00/e0 tag 0 dma 4096 in
         res 51/40:00:af:9e:a1/40:00:12:00:00/00 Emask 0x9 (media error)
ata1.00: status: { DRDY ERR }
ata1.00: error: { UNC }
ata1.00: configured for UDMA/133
sd 0:0:0:0: [sda] Unhandled sense code
sd 0:0:0:0: [sda] Result: hostbyte=0x00 driverbyte=0x08
sd 0:0:0:0: [sda] Sense Key : 0x3 [current] [descriptor]
Descriptor sense data with sense descriptors (in hex):
        72 03 11 04 00 00 00 0c 00 0a 80 00 00 00 00 00 
        12 a1 9e af 
sd 0:0:0:0: [sda] ASC=0x11 ASCQ=0x4
end_request: I/O error, dev sda, sector 312581807
Buffer I/O error on device sda, logical block 39072725
ata1: EH complete
ata1.00: exception Emask 0x0 SAct 0x0 SErr 0x0 action 0x0
ata1.00: BMDMA stat 0x24
ata1.00: cmd 25/00:08:a8:9e:a1/00:00:12:00:00/e0 tag 0 dma 4096 in
         res 51/40:00:af:9e:a1/40:00:12:00:00/00 Emask 0x9 (media error)
ata1.00: status: { DRDY ERR }
ata1.00: error: { UNC }
ata1.00: configured for UDMA/133
ata1: EH complete
ata1.00: exception Emask 0x0 SAct 0x0 SErr 0x0 action 0x0
ata1.00: BMDMA stat 0x24
ata1.00: cmd 25/00:08:a8:9e:a1/00:00:12:00:00/e0 tag 0 dma 4096 in
         res 51/40:00:af:9e:a1/40:00:12:00:00/00 Emask 0x9 (media error)
ata1.00: status: { DRDY ERR }
ata1.00: error: { UNC }
ata1.00: configured for UDMA/133
ata1: EH complete
ata1.00: exception Emask 0x0 SAct 0x0 SErr 0x0 action 0x0
ata1.00: BMDMA stat 0x24
ata1.00: cmd 25/00:08:a8:9e:a1/00:00:12:00:00/e0 tag 0 dma 4096 in
         res 51/40:00:af:9e:a1/40:00:12:00:00/00 Emask 0x9 (media error)
ata1.00: status: { DRDY ERR }
ata1.00: error: { UNC }
ata1.00: configured for UDMA/133
ata1: EH complete
ata1.00: exception Emask 0x0 SAct 0x0 SErr 0x0 action 0x0
ata1.00: BMDMA stat 0x24
ata1.00: cmd 25/00:08:a8:9e:a1/00:00:12:00:00/e0 tag 0 dma 4096 in
         res 51/40:00:af:9e:a1/40:00:12:00:00/00 Emask 0x9 (media error)
ata1.00: status: { DRDY ERR }
ata1.00: error: { UNC }
ata1.00: configured for UDMA/133
ata1: EH complete
ata1.00: exception Emask 0x0 SAct 0x0 SErr 0x0 action 0x0
ata1.00: BMDMA stat 0x24
ata1.00: cmd 25/00:08:a8:9e:a1/00:00:12:00:00/e0 tag 0 dma 4096 in
         res 51/40:00:af:9e:a1/40:00:12:00:00/00 Emask 0x9 (media error)
ata1.00: status: { DRDY ERR }
ata1.00: error: { UNC }
ata1.00: configured for UDMA/133
ata1: EH complete
ata1.00: exception Emask 0x0 SAct 0x0 SErr 0x0 action 0x0
ata1.00: BMDMA stat 0x24
ata1.00: cmd 25/00:08:a8:9e:a1/00:00:12:00:00/e0 tag 0 dma 4096 in
         res 51/40:00:af:9e:a1/40:00:12:00:00/00 Emask 0x9 (media error)
ata1.00: status: { DRDY ERR }
ata1.00: error: { UNC }
ata1.00: configured for UDMA/133
sd 0:0:0:0: [sda] Unhandled sense code
sd 0:0:0:0: [sda] Result: hostbyte=0x00 driverbyte=0x08
sd 0:0:0:0: [sda] Sense Key : 0x3 [current] [descriptor]
Descriptor sense data with sense descriptors (in hex):
        72 03 11 04 00 00 00 0c 00 0a 80 00 00 00 00 00 
        12 a1 9e af 
sd 0:0:0:0: [sda] ASC=0x11 ASCQ=0x4
end_request: I/O error, dev sda, sector 312581807
Buffer I/O error on device sda, logical block 39072725
ata1: EH complete
ata1.00: exception Emask 0x0 SAct 0x0 SErr 0x0 action 0x0
ata1.00: BMDMA stat 0x24
ata1.00: cmd 25/00:08:a8:9e:a1/00:00:12:00:00/e0 tag 0 dma 4096 in
         res 51/40:00:af:9e:a1/40:00:12:00:00/00 Emask 0x9 (media error)
ata1.00: status: { DRDY ERR }
ata1.00: error: { UNC }
ata1.00: configured for UDMA/133
ata1: EH complete
ata1.00: exception Emask 0x0 SAct 0x0 SErr 0x0 action 0x0
ata1.00: BMDMA stat 0x24
ata1.00: cmd 25/00:08:a8:9e:a1/00:00:12:00:00/e0 tag 0 dma 4096 in
         res 51/40:00:af:9e:a1/40:00:12:00:00/00 Emask 0x9 (media error)
ata1.00: status: { DRDY ERR }
ata1.00: error: { UNC }
ata1.00: configured for UDMA/133
ata1: EH complete
ata1.00: exception Emask 0x0 SAct 0x0 SErr 0x0 action 0x0
ata1.00: BMDMA stat 0x24
ata1.00: cmd 25/00:08:a8:9e:a1/00:00:12:00:00/e0 tag 0 dma 4096 in
         res 51/40:00:af:9e:a1/40:00:12:00:00/00 Emask 0x9 (media error)
ata1.00: status: { DRDY ERR }
ata1.00: error: { UNC }
ata1.00: configured for UDMA/133
ata1: EH complete
ata1.00: exception Emask 0x0 SAct 0x0 SErr 0x0 action 0x0
ata1.00: BMDMA stat 0x24
ata1.00: cmd 25/00:08:a8:9e:a1/00:00:12:00:00/e0 tag 0 dma 4096 in
         res 51/40:00:af:9e:a1/40:00:12:00:00/00 Emask 0x9 (media error)
ata1.00: status: { DRDY ERR }
ata1.00: error: { UNC }
ata1.00: configured for UDMA/133
ata1: EH complete
ata1.00: exception Emask 0x0 SAct 0x0 SErr 0x0 action 0x0
ata1.00: BMDMA stat 0x24
ata1.00: cmd 25/00:08:a8:9e:a1/00:00:12:00:00/e0 tag 0 dma 4096 in
         res 51/40:00:af:9e:a1/40:00:12:00:00/00 Emask 0x9 (media error)
ata1.00: status: { DRDY ERR }
ata1.00: error: { UNC }
ata1.00: configured for UDMA/133
ata1: EH complete
ata1.00: exception Emask 0x0 SAct 0x0 SErr 0x0 action 0x0
ata1.00: BMDMA stat 0x24
ata1.00: cmd 25/00:08:a8:9e:a1/00:00:12:00:00/e0 tag 0 dma 4096 in
         res 51/40:00:af:9e:a1/40:00:12:00:00/00 Emask 0x9 (media error)
ata1.00: status: { DRDY ERR }
ata1.00: error: { UNC }
ata1.00: configured for UDMA/133
sd 0:0:0:0: [sda] Unhandled sense code
sd 0:0:0:0: [sda] Result: hostbyte=0x00 driverbyte=0x08
sd 0:0:0:0: [sda] Sense Key : 0x3 [current] [descriptor]
Descriptor sense data with sense descriptors (in hex):
        72 03 11 04 00 00 00 0c 00 0a 80 00 00 00 00 00 
        12 a1 9e af 
sd 0:0:0:0: [sda] ASC=0x11 ASCQ=0x4
end_request: I/O error, dev sda, sector 312581807
Buffer I/O error on device sda, logical block 39072725
ata1: EH complete
EXT4-fs: barriers enabled
EXT4-fs: delayed allocation enabled
EXT4-fs: file extents enabled
kjournald2 starting: pid 480, dev sda5:8, commit interval 5 seconds
EXT4-fs: mballoc enabled
EXT4-fs: mounted filesystem sda5 with ordered data mode

But then arch will continue booting, although it takes FOREVER for udev events, loading modules, etc.  Once arch is up and running it seems to be ok.

Now, I am hoping someone will walk in here and tell me I have missed something simple and it is an easy fix, but as of right now I can't figure out where to go from here.  Anyone have any ideas?

Last edited by monstermudder78 (2009-11-25 06:38:35)

Offline

#2 2009-09-13 18:47:51

kjon
Member
From: Temuco, Chile
Registered: 2008-04-16
Posts: 398

Re: kernel (or pre-kernel?) filesystem error.

to me, it looks that your harddrive passed by...

They say that if you play a Win cd backward you hear satanic messages. That's nothing! 'cause if you play it forwards, it installs windows.

Offline

#3 2009-09-14 04:20:31

jspaces
Member
From: Canada
Registered: 2009-04-16
Posts: 21

Re: kernel (or pre-kernel?) filesystem error.

I afraid that the hard drive has a physical defect (bad sector).
http://ata.wiki.kernel.org/index.php/Li … r_messages

ata1.00: error: { UNC }
UNC    Uncorrectable error - often due to bad sectors on the disk

If there is a loose particle in the hard drive enclosure then it will eventually cause more physical defects (bad sectors). Total failure is very probable. I recommend you backup all important data off as soon as possible before it occurs. I believe that replacement is the only solution, hopefully it is still under warranty.

Knowledge is a beam of light in which humans can only see the reflection.

Offline

#4 2009-09-14 04:33:48

Zack89
Member
Registered: 2008-09-24
Posts: 170

Re: kernel (or pre-kernel?) filesystem error.

May I offer a suggestion for the backup? There are a few applications available for absolute backup. I have experience with Partimage. It is included with SystemRescueCd, free to download. SysResCD is a GNU/Linux distro devoted to system recovery. Partimage can snapshot your hard drive, and compress it with either gzip or bzip2 compressioning. So you can image your entire partition (assuming it is still readable) and when you get a new drive just import the volume back onto the drive using partimage again. Other apps you can use I heard is.. rsync. It works like Mac OS X's time machine where it will do an absolute image backup first, then incremental changes as your volume changes. but im assuming rsync is only usable if the volume is currently locked an in use.. so try Partimage.

Registered User number: 496613. Show your Tux Pride!
http://counter.li.org

Offline

#5 2009-09-14 08:49:17

arunix
Member
From: /home/kurali
Registered: 2009-04-08
Posts: 93

Re: kernel (or pre-kernel?) filesystem error.

ata1.00: status: { DRDY ERR }
ata1.00: error: { UNC }
ata1.00: configured for UDMA/133
ata1: EH complete
ata1.00: exception Emask 0x0 SAct 0x0 SErr 0x0 action 0x0
ata1.00: BMDMA stat 0x24
ata1.00: cmd 25/00:08:a8:9e:a1/00:00:12:00:00/e0 tag 0 dma 4096 in
         res 51/40:00:af:9e:a1/40:00:12:00:00/00 Emask 0x9 (media error)

i have an experiance with this last month. all are recomend is right so as soon as possible be backup.just put live cd(arch) and login as root and give this command

e2fsck -vyf /dev/[partation]

after fixing the problem ur system will run fine but its not the parmanent  solution.

Minds are like parachutes. They only function when they are open.

Offline

#6 2009-09-15 04:29:56

monstermudder78
Member
Registered: 2008-05-18
Posts: 120

Re: kernel (or pre-kernel?) filesystem error.

First, thanks for the replies.  I am still trying to come up with a workable solution.

jspaces wrote:

I afraid that the hard drive has a physical defect (bad sector).
http://ata.wiki.kernel.org/index.php/Li … r_messages

ata1.00: error: { UNC }
UNC    Uncorrectable error - often due to bad sectors on the disk

If there is a loose particle in the hard drive enclosure then it will eventually cause more physical defects (bad sectors). Total failure is very probable. I recommend you backup all important data off as soon as possible before it occurs. I believe that replacement is the only solution, hopefully it is still under warranty.

I have already backed up my important files - did that very first from a live usb.  The drive is still under warranty, however Asus is giving me grief about having Linux on a drive that was shipped with XP mad

arunix:  That is what I had done with fsck -c /dev/sda5.  It 'fixed' the errors that were found, and I can boot now, I just get piles and piles of errors before Arch's initscripts are run.

All this is an even bigger headache due to this machine being a netbook and not having a cd/dvd drive neutral  But I am still trying...

Last edited by monstermudder78 (2009-09-15 04:30:44)

Offline

#7 2009-09-15 14:12:51

R00KIE
Forum Fellow
From: Between a computer and a chair
Registered: 2008-09-14
Posts: 4,734

Re: kernel (or pre-kernel?) filesystem error.

Then as root try

dd if=/dev/zero of=/dev/sda5 bs=10M

Mind you that this will erase everything in that partiton, filesystem included, if you get errors while writing then you're in trouble and better change the disk, if not then try

dd if=/dev/sda5 of=/dev/null bs=10M

and see if dd complains it can't read something, if all goes well then problem solved.

I've had a somewhat similar problem where the disk would always report an error when trying to read certain sectors, then sort of as a last resort I've nuked the partition with zeros and it is working fine now.

R00KIE
Tm90aGluZyB0byBzZWUgaGVyZSwgbW92ZSBhbG9uZy4K

Offline

#8 2009-09-18 02:22:20

monstermudder78
Member
Registered: 2008-05-18
Posts: 120

Re: kernel (or pre-kernel?) filesystem error.

R00KIE wrote:

Then as root try

dd if=/dev/zero of=/dev/sda5 bs=10M

Mind you that this will erase everything in that partiton, filesystem included, if you get errors while writing then you're in trouble and better change the disk, if not then try

dd if=/dev/sda5 of=/dev/null bs=10M

and see if dd complains it can't read something, if all goes well then problem solved.

I've had a somewhat similar problem where the disk would always report an error when trying to read certain sectors, then sort of as a last resort I've nuked the partition with zeros and it is working fine now.

Ok, when I tried dd if=/dev/zero of=/dev/sda5 bs=10M I didn't get any explicit errors, but the numbers at the end were off by 1 (I did this 2 days ago and I don't remember what exactly they said, but I took it to mean it wrote every file but one?).  All the files written were read without problem.  I then rebooted to the live usb and still got the same error on boot.

I then changed sda5 to reiser, and rebooted, still the same error on boot.  Finally, in desperation I changed all my partitions, including swap, to NTFS, hoping that linux wouldn't try and read them at all, and rebooted to the live usb - still the same error.  I am now completely out of ideas and am planning on replacing the HDD.  Anyone have any 'last resort' ideas to try before I pull the trigger and order a new drive?

Offline

#9 2009-09-18 10:19:03

feralert
Member
Registered: 2007-03-21
Posts: 12

Re: kernel (or pre-kernel?) filesystem error.

Hi monstermudder78,

Unfortunately i cant help with your problem, I just wanted to ask you a quick question, did you migrate your /dev/sda5 partition from ext3 to ext4 or did you format the partition as ext4 from the begining?

Thanks and good luck.

Offline

#10 2009-09-18 14:15:16

monstermudder78
Member
Registered: 2008-05-18
Posts: 120

Re: kernel (or pre-kernel?) filesystem error.

It was ext4 from the start.

Offline

#11 2009-09-18 16:07:33

rwd
Member
Registered: 2009-02-08
Posts: 664

Re: kernel (or pre-kernel?) filesystem error.

if you get bad sectors it is probable that your drive is dying so it will have more bad sectors soon. I'd say put in a ssd so you don't have to worry about dropping it on the floor.

Last edited by rwd (2009-09-18 17:06:01)

Offline

#12 2009-09-18 19:28:21

R00KIE
Forum Fellow
From: Between a computer and a chair
Registered: 2008-09-14
Posts: 4,734

Re: kernel (or pre-kernel?) filesystem error.

Just out of curiosity what is the output of

smartctl -A /dev/sda

you will need to install smartmontools, if the count of Reallocated_Sector_Ct (or similar), Reallocated_Event_Count, Current_Pending_Sector or Offline_Uncorrectable are not zero then that's sign of trouble and it means that most probably you need a new HD, if not then the problem may be something else.

R00KIE
Tm90aGluZyB0byBzZWUgaGVyZSwgbW92ZSBhbG9uZy4K

Offline

#13 2009-11-25 06:39:30

monstermudder78
Member
Registered: 2008-05-18
Posts: 120

Re: kernel (or pre-kernel?) filesystem error.

Could a mod please move this to the kernel subforum?  I believe the problem to be kernel related.

Offline

#14 2009-11-25 09:54:26

iphitus
Forum Fellow
From: Melbourne, Australia
Registered: 2004-10-09
Posts: 4,927

Re: kernel (or pre-kernel?) filesystem error.

Sure it's kernel?

The kernel makes it pretty clear that it's a hardware issue. R00KIE's right, have a look using smart and see what you can see.

I'd be getting a warranty return on the drive. Doesn't matter that it's Linux, it's a hardware defect - Linux does not void warranty.

James

Offline

#15 2009-11-25 16:42:12

monstermudder78
Member
Registered: 2008-05-18
Posts: 120

Re: kernel (or pre-kernel?) filesystem error.

iphitus wrote:

Sure it's kernel?
The kernel makes it pretty clear that it's a hardware issue. R00KIE's right, have a look using smart and see what you can see.
I'd be getting a warranty return on the drive. Doesn't matter that it's Linux, it's a hardware defect - Linux does not void warranty.
James

You are right, let me try and clarify.  I believe it to be an OLD hardware problem that was repaired, but the kernel has the error logged and will not let it go.  This error message comes up instantly, without there being time for any sort of drive check, so I believe it must be logged somewhere and not the result of a new check at each boot.

And no, I can't get it warrantied.  The machine shipped with XP and runs fine with XP.  Windows doesn't give an error even when using that partition.  I was told by Asus that since it works there is nothing they can do.  Also, on their website, it specifically says that installing any other operating system other than what shipped on the machine voids the warranty.  So, anyways, I would like to fix the problem and not replace the drive.

Offline

Pages: 1

Board footer

Powered by FluxBB