You are not logged in.

Pages: 1

#1 2009-11-30 23:14:30

jak3b
Member
Registered: 2006-03-28
Posts: 6

what happend?

In the last day or so I noticed the performance on my laptop went from being very snappy to almost totaly unuseable.Im running Arch on a Dell Inspiron 1300.No problems at all till now.I ran hdparm and this is the result:
sudo hdparm  -Tt /dev/sda

/dev/sda:
Timing cached reads:   444 MB in  2.00 seconds = 221.88 MB/sec
Timing buffered disk reads:    6 MB in  3.69 seconds =   1.62 MB/sec.

Crappola

I ran the smartctl tests and the drive is passing.
This started yesterday after a pacman -Syu.

other hdparm info:sudo hdparm  -I /dev/sda

/dev/sda:

ATA device, with non-removable media
    Model Number:       SAMSUNG MP0804H                         
    Serial Number:      S042J10A179782
    Firmware Revision:  UE200-16
Standards:
    Used: ATA/ATAPI-7 T13 1532D revision 0
    Supported: 7 6 5 4
Configuration:
    Logical        max    current
    cylinders    16383    16383
    heads        16    16
    sectors/track    63    63
    --
    CHS current addressable sectors:   16514064
    LBA    user addressable sectors:  156301488
    LBA48  user addressable sectors:  156301488
    Logical/Physical Sector size:           512 bytes
    device size with M = 1024*1024:       76319 MBytes
    device size with M = 1000*1000:       80026 MBytes (80 GB)
    cache/buffer size  = 8192 KBytes (type=DualPortCache)
Capabilities:
    LBA, IORDY(can be disabled)
    Standby timer values: spec'd by Standard, no device specific minimum
    R/W multiple sector transfer: Max = 16    Current = 8
    Advanced power management level: disabled
    Recommended acoustic management value: 254, current value: 128
    DMA: mdma0 mdma1 mdma2 udma0 udma1 *udma2 udma3 udma4 udma5
         Cycle time: min=120ns recommended=120ns
    PIO: pio0 pio1 pio2 pio3 pio4
         Cycle time: no flow control=120ns  IORDY flow control=120ns
Commands/features:
    Enabled    Supported:
       *    SMART feature set
            Security Mode feature set
       *    Power Management feature set
       *    Write cache
       *    Look-ahead
       *    Host Protected Area feature set
       *    WRITE_BUFFER command
       *    READ_BUFFER command
       *    DOWNLOAD_MICROCODE
            Advanced Power Management feature set
            SET_MAX security extension
       *    Automatic Acoustic Management feature set
       *    48-bit Address feature set
       *    Device Configuration Overlay feature set
       *    Mandatory FLUSH_CACHE
       *    FLUSH_CACHE_EXT
       *    SMART error logging
       *    SMART self-test
       *    IDLE_IMMEDIATE with UNLOAD
Security:
    Master password revision code = 65534
        supported
    not    enabled
    not    locked
        frozen
    not    expired: security count
        supported: enhanced erase
    88min for SECURITY ERASE UNIT. 88min for ENHANCED SECURITY ERASE UNIT.
HW reset results:
    CBLID- above Vih
    Device num = 0 determined by the jumper
Checksum: correct

Thanks

Offline

#2 2009-12-01 19:02:07

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

Re: what happend?

Get iotop from the repos and while you have your machine idling see if there is anything accessing your HD (either reading or writing).

Also get smartmontools and try smartctl -A /dev/sdx and check at the end if there are any pending sectors or offline uncorrectable.

R00KIE
Tm90aGluZyB0byBzZWUgaGVyZSwgbW92ZSBhbG9uZy4K

Offline

#3 2009-12-01 19:42:23

lilsirecho
Veteran
Registered: 2003-10-24
Posts: 5,000

Re: what happend?

Perhaps the cpu is throttling.....................

Prediction...This year will be a very odd year!
Hard work does not kill people but why risk it: Charlie Mccarthy
A man is not complete until he is married..then..he is finished.
When ALL is lost, what can be found? Even bytes get lonely for a little bit!     X-ray confirms Iam spineless!

Offline

#4 2010-01-12 01:55:43

jak3b
Member
Registered: 2006-03-28
Posts: 6

Re: what happend?

Hello All,
I reinstalled after I made this post and everything was fine.....up till today.heres the relevent output from dmesg:
HDA Intel 0000:00:1b.0: PCI INT A -> GSI 16 (level, low) -> IRQ 16
HDA Intel 0000:00:1b.0: setting latency timer to 64
input: HDA Intel Mic at Ext Left Jack as /devices/pci0000:00/0000:00:1b.0/sound/card0/input9
input: HDA Intel HP Out at Ext Left Jack as /devices/pci0000:00/0000:00:1b.0/sound/card0/input10
Adding 996020k swap on /dev/sda2.  Priority:-1 extents:1 across:996020k
ata1: drained 32768 bytes to clear DRQ.
ata1.00: exception Emask 0x0 SAct 0x0 SErr 0x0 action 0x6 frozen
ata1.00: BMDMA stat 0x65
ata1.00: failed command: READ DMA
ata1.00: cmd c8/00:08:52:55:ee/00:00:00:00:00/e2 tag 0 dma 4096 in
         res 59/40:08:52:55:ee/00:00:00:00:00/e2 Emask 0x2 (HSM violation)
ata1.00: status: { DRDY DRQ ERR }
ata1.00: error: { UNC }
ata1: soft resetting link
ata1.00: configured for UDMA/100
ata1.01: configured for UDMA/33
ata1: EH complete
ata1: drained 32768 bytes to clear DRQ.
ata1.00: exception Emask 0x0 SAct 0x0 SErr 0x0 action 0x6 frozen
ata1.00: BMDMA stat 0x65
ata1.00: failed command: READ DMA
ata1.00: cmd c8/00:08:52:55:ee/00:00:00:00:00/e2 tag 0 dma 4096 in
         res 59/40:08:52:55:ee/00:00:00:00:00/e2 Emask 0x2 (HSM violation)
ata1.00: status: { DRDY DRQ ERR }
ata1.00: error: { UNC }
ata1: soft resetting link
ata1.00: configured for UDMA/100
ata1.01: configured for UDMA/33
ata1: EH complete
ata1: drained 32768 bytes to clear DRQ.
ata1.00: exception Emask 0x0 SAct 0x0 SErr 0x0 action 0x6 frozen
ata1.00: BMDMA stat 0x65
ata1.00: failed command: READ DMA
ata1.00: cmd c8/00:08:52:55:ee/00:00:00:00:00/e2 tag 0 dma 4096 in
         res 59/40:08:52:55:ee/00:00:00:00:00/e2 Emask 0x2 (HSM violation)
ata1.00: status: { DRDY DRQ ERR }
ata1.00: error: { UNC }
ata1: soft resetting link
ata1.00: configured for UDMA/100
ata1.01: configured for UDMA/33
ata1: EH complete
ata1: drained 32768 bytes to clear DRQ.
ata1.00: limiting speed to UDMA/66:PIO4
ata1.00: exception Emask 0x0 SAct 0x0 SErr 0x0 action 0x6 frozen
ata1.00: BMDMA stat 0x65
ata1.00: failed command: READ DMA
ata1.00: cmd c8/00:08:52:55:ee/00:00:00:00:00/e2 tag 0 dma 4096 in
         res 59/40:08:52:55:ee/00:00:00:00:00/e2 Emask 0x2 (HSM violation)
ata1.00: status: { DRDY DRQ ERR }
ata1.00: error: { UNC }
ata1: soft resetting link
ata1.00: configured for UDMA/66
ata1.01: configured for UDMA/33
ata1: EH complete
ata1: drained 32768 bytes to clear DRQ.
ata1.00: exception Emask 0x0 SAct 0x0 SErr 0x0 action 0x6 frozen
ata1.00: BMDMA stat 0x65
ata1.00: failed command: READ DMA
ata1.00: cmd c8/00:08:52:55:ee/00:00:00:00:00/e2 tag 0 dma 4096 in
         res 59/40:08:52:55:ee/00:00:00:00:00/e2 Emask 0x2 (HSM violation)
ata1.00: status: { DRDY DRQ ERR }
ata1.00: error: { UNC }
ata1: soft resetting link
ata1.00: configured for UDMA/66
ata1.01: configured for UDMA/33
ata1: EH complete
ata1: drained 32768 bytes to clear DRQ.
ata1.00: limiting speed to UDMA/33:PIO4
ata1.00: exception Emask 0x0 SAct 0x0 SErr 0x0 action 0x6 frozen
ata1.00: BMDMA stat 0x65
ata1.00: failed command: READ DMA
ata1.00: cmd c8/00:08:52:55:ee/00:00:00:00:00/e2 tag 0 dma 4096 in
         res 59/40:08:52:55:ee/00:00:00:00:00/e2 Emask 0x2 (HSM violation)
ata1.00: status: { DRDY DRQ ERR }
ata1.00: error: { UNC }
ata1: soft resetting link
ata1.00: configured for UDMA/33
ata1.01: configured for UDMA/33
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
        02 ee 55 52
sd 0:0:0:0: [sda] ASC=0x11 ASCQ=0x4
sd 0:0:0:0: [sda] CDB: cdb[0]=0x28: 28 00 02 ee 55 52 00 00 08 00
end_request: I/O error, dev sda, sector 49173842
ata1: EH complete
ata1: drained 32768 bytes to clear DRQ.
ata1.00: exception Emask 0x0 SAct 0x0 SErr 0x0 action 0x6 frozen
ata1.00: BMDMA stat 0x65
ata1.00: failed command: READ DMA
ata1.00: cmd c8/00:08:52:55:ee/00:00:00:00:00/e2 tag 0 dma 4096 in
         res 59/40:08:52:55:ee/00:00:00:00:00/e2 Emask 0x2 (HSM violation)
ata1.00: status: { DRDY DRQ ERR }
ata1.00: error: { UNC }
ata1: soft resetting link
ata1.00: configured for UDMA/33
ata1.01: configured for UDMA/33
ata1: EH complete
ata1: drained 32768 bytes to clear DRQ.
ata1.00: exception Emask 0x0 SAct 0x0 SErr 0x0 action 0x6 frozen
ata1.00: BMDMA stat 0x65
ata1.00: failed command: READ DMA
ata1.00: cmd c8/00:08:52:55:ee/00:00:00:00:00/e2 tag 0 dma 4096 in
         res 59/40:08:52:55:ee/00:00:00:00:00/e2 Emask 0x2 (HSM violation)
ata1.00: status: { DRDY DRQ ERR }
ata1.00: error: { UNC }
ata1: soft resetting link
ata1.00: configured for UDMA/33
ata1.01: configured for UDMA/33
ata1: EH complete
ata1: drained 32768 bytes to clear DRQ.
ata1.00: exception Emask 0x0 SAct 0x0 SErr 0x0 action 0x6 frozen
ata1.00: BMDMA stat 0x65
ata1.00: failed command: READ DMA
ata1.00: cmd c8/00:08:52:55:ee/00:00:00:00:00/e2 tag 0 dma 4096 in
         res 59/40:08:52:55:ee/00:00:00:00:00/e2 Emask 0x2 (HSM violation)
ata1.00: status: { DRDY DRQ ERR }
ata1.00: error: { UNC }
ata1: soft resetting link
ata1.00: configured for UDMA/33
ata1.01: configured for UDMA/33
ata1: EH complete
ata1: drained 32768 bytes to clear DRQ.
ata1.00: exception Emask 0x0 SAct 0x0 SErr 0x0 action 0x6 frozen
ata1.00: BMDMA stat 0x65
ata1.00: failed command: READ DMA
ata1.00: cmd c8/00:08:52:55:ee/00:00:00:00:00/e2 tag 0 dma 4096 in
         res 59/40:08:52:55:ee/00:00:00:00:00/e2 Emask 0x2 (HSM violation)
ata1.00: status: { DRDY DRQ ERR }
ata1.00: error: { UNC }
ata1: soft resetting link
ata1.00: configured for UDMA/33
ata1.01: configured for UDMA/33
ata1: EH complete
ata1: drained 32768 bytes to clear DRQ.
ata1.00: limiting speed to PIO4
ata1.00: exception Emask 0x0 SAct 0x0 SErr 0x0 action 0x6 frozen
ata1.00: BMDMA stat 0x65
ata1.00: failed command: READ DMA
ata1.00: cmd c8/00:08:52:55:ee/00:00:00:00:00/e2 tag 0 dma 4096 in
         res 59/40:08:52:55:ee/00:00:00:00:00/e2 Emask 0x2 (HSM violation)
ata1.00: status: { DRDY DRQ ERR }
ata1.00: error: { UNC }
ata1: soft resetting link
ata1.00: configured for PIO4
ata1.01: configured for UDMA/33
ata1: EH complete
ata1: drained 32768 bytes to clear DRQ.
ata1.00: exception Emask 0x0 SAct 0x0 SErr 0x0 action 0x6 frozen
ata1.00: ST-ATA: BUSY|DRQ persists on ERR|DF, dev_stat 0x59
ata1.00: failed command: READ MULTIPLE
ata1.00: cmd c4/00:08:52:55:ee/00:00:00:00:00/e2 tag 0 pio 4096 in
         res 59/40:08:52:55:ee/00:00:00:00:00/e2 Emask 0x3 (HSM violation)
ata1.00: status: { DRDY DRQ ERR }
ata1.00: error: { UNC }
ata1: soft resetting link
ata1.00: configured for PIO4
ata1.01: configured for UDMA/33
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
        02 ee 55 52
sd 0:0:0:0: [sda] ASC=0x11 ASCQ=0x4
sd 0:0:0:0: [sda] CDB: cdb[0]=0x28: 28 00 02 ee 55 52 00 00 08 00
end_request: I/O error, dev sda, sector 49173842
ata1: EH complete

Some kind of DMA error I guess? Its a Dell Inspiron 1300 with a SAMSUNG SATA MP0804H 80 gig hd.
heres the hdparm results. buffered disk reads are useally 25-28 mb's a sec

/dev/sda:
Timing cached reads:   864 MB in  2.00 seconds = 431.84 MB/sec
Timing buffered disk reads:    8 MB in  3.53 seconds =   2.27 MB/sec

Thanks

Offline

#5 2010-01-12 14:59:27

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

Re: what happend?

That looks like a flaky cable/connection or may be something with the kernel/drive controller/drive not handling ncq properly, I know some drives have been blacklisted not to use ncq as it causes problems. If you search for 'Emask 0x2 (HSM violation)' you will get the picture.

Just out of curiosity, whats the output of 'smartctl -A /dev/sda' ?

R00KIE
Tm90aGluZyB0byBzZWUgaGVyZSwgbW92ZSBhbG9uZy4K

Offline

#6 2010-01-12 17:09:42

jak3b
Member
Registered: 2006-03-28
Posts: 6

Re: what happend?

Heres the output from smartctl -A /dev/sda;

smartctl version 5.38 [x86_64-unknown-linux-gnu] Copyright (C) 2002-8 Bruce Allen
Home page is http://smartmontools.sourceforge.net/

=== START OF READ SMART DATA SECTION ===
SMART Attributes Data Structure revision number: 16
Vendor Specific SMART Attributes with Thresholds:
ID# ATTRIBUTE_NAME          FLAG     VALUE WORST THRESH TYPE      UPDATED  WHEN_FAILED RAW_VALUE
  1 Raw_Read_Error_Rate     0x000f   100   097   051    Pre-fail  Always       -       0
  3 Spin_Up_Time            0x0007   100   100   025    Pre-fail  Always       -       3392
  4 Start_Stop_Count        0x0032   094   094   000    Old_age   Always       -       6621
  5 Reallocated_Sector_Ct   0x0033   100   100   011    Pre-fail  Always       -       0
  7 Seek_Error_Rate         0x000e   100   100   000    Old_age   Always       -       0
  8 Seek_Time_Performance   0x0024   100   100   000    Old_age   Offline      -       0
  9 Power_On_Hours          0x0032   099   099   000    Old_age   Always       -       741600
10 Spin_Retry_Count        0x0032   100   100   000    Old_age   Always       -       0
12 Power_Cycle_Count       0x0032   097   097   000    Old_age   Always       -       3487
191 G-Sense_Error_Rate      0x0012   098   098   000    Old_age   Always       -       22344
194 Temperature_Celsius     0x0022   184   094   000    Old_age   Always       -       18
195 Hardware_ECC_Recovered  0x001a   100   100   000    Old_age   Always       -       547429
196 Reallocated_Event_Count 0x0032   091   091   000    Old_age   Always       -       20
197 Current_Pending_Sector  0x0012   100   100   000    Old_age   Always       -       0
198 Offline_Uncorrectable   0x0030   100   100   000    Old_age   Offline      -       0
199 UDMA_CRC_Error_Count    0x003e   200   200   000    Old_age   Always       -       0
200 Multi_Zone_Error_Rate   0x000a   100   100   000    Old_age   Always       -       0
201 Soft_Read_Error_Rate    0x0012   100   100   000    Old_age   Always       -       0
223 Load_Retry_Count        0x0012   098   098   000    Old_age   Always       -       2431
225 Load_Cycle_Count        0x0012   003   003   000    Old_age   Always       -       989363
255 Unknown_Attribute       0x000a   100   100   000    Old_age   Always       -

Offline

#7 2010-01-12 17:26:38

joaca_rj
Member
From: Rio de Janeiro, Brazil
Registered: 2009-04-12
Posts: 76

Re: what happend?

225 Load_Cycle_Count        0x0012   003   003   000    Old_age   Always       -       989363

you have a pretty high value here... some say the hd lasts 'till 600000 ( according to the numerous posts about the problems with some hds power management )...

Offline

#8 2010-01-12 21:11:05

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

Re: what happend?

joaca_rj wrote:

225 Load_Cycle_Count        0x0012   003   003   000    Old_age   Always       -       989363

you have a pretty high value here... some say the hd lasts 'till 600000 ( according to the numerous posts about the problems with some hds power management )...

Yes thats true, some disks will do this if you don't set longer idle timeouts, the value of the attribute is really close to the threshold so I would take care of that too, but it doesn't seem to be the problem.

Most attributes have what seem to be normal values except "Reallocated_Event_Count". It seems there were some reallocation events, whatever that means for the manufacturer/disk in question, on the other hand there are no "Reallocated_Sector_Ct". The way reallocated sectors are counted varies from manufacturer to manufacturer so it's more like an indication of possible problems. "Current_Pending_Sector" and "Offline_Uncorrectable" are both zero so I guess that read errors can be excluded from possible causes of problems.

If it was working fine before then it may be caused by some regression in the kernel or like I said before a flaky cable or power supply. If it is a notebook disk, then you may want to unplug it and plug it again to make sure it is properly seated. No other ideas here except maybe issuing a full disk smart test and check for any problems.

R00KIE
Tm90aGluZyB0byBzZWUgaGVyZSwgbW92ZSBhbG9uZy4K

Offline

#9 2010-01-12 22:43:26

Cyrusm
Member
From: Bozeman, MT
Registered: 2007-11-15
Posts: 1,053

Re: what happend?

jak3b wrote:

Hello All,
I reinstalled after I made this post and everything was fine.....up till today.heres the relevent output from dmesg:

HDA Intel 0000:00:1b.0: PCI INT A -> GSI 16 (level, low) -> IRQ 16
HDA Intel 0000:00:1b.0: setting latency timer to 64
input: HDA Intel Mic at Ext Left Jack as /devices/pci0000:00/0000:00:1b.0/sound/card0/input9
input: HDA Intel HP Out at Ext Left Jack as /devices/pci0000:00/0000:00:1b.0/sound/card0/input10
Adding 996020k swap on /dev/sda2.  Priority:-1 extents:1 across:996020k 
ata1: drained 32768 bytes to clear DRQ.
ata1.00: exception Emask 0x0 SAct 0x0 SErr 0x0 action 0x6 frozen
ata1.00: BMDMA stat 0x65
ata1.00: failed command: READ DMA
ata1.00: cmd c8/00:08:52:55:ee/00:00:00:00:00/e2 tag 0 dma 4096 in
         res 59/40:08:52:55:ee/00:00:00:00:00/e2 Emask 0x2 (HSM violation)
ata1.00: status: { DRDY DRQ ERR }
ata1.00: error: { UNC }
ata1: soft resetting link
ata1.00: configured for UDMA/100
ata1.01: configured for UDMA/33
ata1: EH complete
ata1: drained 32768 bytes to clear DRQ.
ata1.00: exception Emask 0x0 SAct 0x0 SErr 0x0 action 0x6 frozen
ata1.00: BMDMA stat 0x65
ata1.00: failed command: READ DMA
ata1.00: cmd c8/00:08:52:55:ee/00:00:00:00:00/e2 tag 0 dma 4096 in
         res 59/40:08:52:55:ee/00:00:00:00:00/e2 Emask 0x2 (HSM violation)
ata1.00: status: { DRDY DRQ ERR }
ata1.00: error: { UNC }
ata1: soft resetting link
ata1.00: configured for UDMA/100
ata1.01: configured for UDMA/33
ata1: EH complete
ata1: drained 32768 bytes to clear DRQ.
ata1.00: exception Emask 0x0 SAct 0x0 SErr 0x0 action 0x6 frozen
ata1.00: BMDMA stat 0x65
ata1.00: failed command: READ DMA
ata1.00: cmd c8/00:08:52:55:ee/00:00:00:00:00/e2 tag 0 dma 4096 in
         res 59/40:08:52:55:ee/00:00:00:00:00/e2 Emask 0x2 (HSM violation)
ata1.00: status: { DRDY DRQ ERR }
ata1.00: error: { UNC }
ata1: soft resetting link
ata1.00: configured for UDMA/100
ata1.01: configured for UDMA/33
ata1: EH complete
ata1: drained 32768 bytes to clear DRQ.
ata1.00: limiting speed to UDMA/66:PIO4
ata1.00: exception Emask 0x0 SAct 0x0 SErr 0x0 action 0x6 frozen
ata1.00: BMDMA stat 0x65
ata1.00: failed command: READ DMA
ata1.00: cmd c8/00:08:52:55:ee/00:00:00:00:00/e2 tag 0 dma 4096 in
         res 59/40:08:52:55:ee/00:00:00:00:00/e2 Emask 0x2 (HSM violation)
ata1.00: status: { DRDY DRQ ERR }
ata1.00: error: { UNC }
ata1: soft resetting link
ata1.00: configured for UDMA/66
ata1.01: configured for UDMA/33
ata1: EH complete
ata1: drained 32768 bytes to clear DRQ.
ata1.00: exception Emask 0x0 SAct 0x0 SErr 0x0 action 0x6 frozen
ata1.00: BMDMA stat 0x65
ata1.00: failed command: READ DMA
ata1.00: cmd c8/00:08:52:55:ee/00:00:00:00:00/e2 tag 0 dma 4096 in
         res 59/40:08:52:55:ee/00:00:00:00:00/e2 Emask 0x2 (HSM violation)
ata1.00: status: { DRDY DRQ ERR }
ata1.00: error: { UNC }
ata1: soft resetting link
ata1.00: configured for UDMA/66
ata1.01: configured for UDMA/33
ata1: EH complete
ata1: drained 32768 bytes to clear DRQ.
ata1.00: limiting speed to UDMA/33:PIO4
ata1.00: exception Emask 0x0 SAct 0x0 SErr 0x0 action 0x6 frozen
ata1.00: BMDMA stat 0x65
ata1.00: failed command: READ DMA
ata1.00: cmd c8/00:08:52:55:ee/00:00:00:00:00/e2 tag 0 dma 4096 in
         res 59/40:08:52:55:ee/00:00:00:00:00/e2 Emask 0x2 (HSM violation)
ata1.00: status: { DRDY DRQ ERR }
ata1.00: error: { UNC }
ata1: soft resetting link
ata1.00: configured for UDMA/33
ata1.01: configured for UDMA/33
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 
        02 ee 55 52 
sd 0:0:0:0: [sda] ASC=0x11 ASCQ=0x4
sd 0:0:0:0: [sda] CDB: cdb[0]=0x28: 28 00 02 ee 55 52 00 00 08 00
end_request: I/O error, dev sda, sector 49173842
ata1: EH complete
ata1: drained 32768 bytes to clear DRQ.
ata1.00: exception Emask 0x0 SAct 0x0 SErr 0x0 action 0x6 frozen
ata1.00: BMDMA stat 0x65
ata1.00: failed command: READ DMA
ata1.00: cmd c8/00:08:52:55:ee/00:00:00:00:00/e2 tag 0 dma 4096 in
         res 59/40:08:52:55:ee/00:00:00:00:00/e2 Emask 0x2 (HSM violation)
ata1.00: status: { DRDY DRQ ERR }
ata1.00: error: { UNC }
ata1: soft resetting link
ata1.00: configured for UDMA/33
ata1.01: configured for UDMA/33
ata1: EH complete
ata1: drained 32768 bytes to clear DRQ.
ata1.00: exception Emask 0x0 SAct 0x0 SErr 0x0 action 0x6 frozen
ata1.00: BMDMA stat 0x65
ata1.00: failed command: READ DMA
ata1.00: cmd c8/00:08:52:55:ee/00:00:00:00:00/e2 tag 0 dma 4096 in
         res 59/40:08:52:55:ee/00:00:00:00:00/e2 Emask 0x2 (HSM violation)
ata1.00: status: { DRDY DRQ ERR }
ata1.00: error: { UNC }
ata1: soft resetting link
ata1.00: configured for UDMA/33
ata1.01: configured for UDMA/33
ata1: EH complete
ata1: drained 32768 bytes to clear DRQ.
ata1.00: exception Emask 0x0 SAct 0x0 SErr 0x0 action 0x6 frozen
ata1.00: BMDMA stat 0x65
ata1.00: failed command: READ DMA
ata1.00: cmd c8/00:08:52:55:ee/00:00:00:00:00/e2 tag 0 dma 4096 in
         res 59/40:08:52:55:ee/00:00:00:00:00/e2 Emask 0x2 (HSM violation)
ata1.00: status: { DRDY DRQ ERR }
ata1.00: error: { UNC }
ata1: soft resetting link
ata1.00: configured for UDMA/33
ata1.01: configured for UDMA/33
ata1: EH complete
ata1: drained 32768 bytes to clear DRQ.
ata1.00: exception Emask 0x0 SAct 0x0 SErr 0x0 action 0x6 frozen
ata1.00: BMDMA stat 0x65
ata1.00: failed command: READ DMA
ata1.00: cmd c8/00:08:52:55:ee/00:00:00:00:00/e2 tag 0 dma 4096 in
         res 59/40:08:52:55:ee/00:00:00:00:00/e2 Emask 0x2 (HSM violation)
ata1.00: status: { DRDY DRQ ERR }
ata1.00: error: { UNC }
ata1: soft resetting link
ata1.00: configured for UDMA/33
ata1.01: configured for UDMA/33
ata1: EH complete
ata1: drained 32768 bytes to clear DRQ.
ata1.00: limiting speed to PIO4
ata1.00: exception Emask 0x0 SAct 0x0 SErr 0x0 action 0x6 frozen
ata1.00: BMDMA stat 0x65
ata1.00: failed command: READ DMA
ata1.00: cmd c8/00:08:52:55:ee/00:00:00:00:00/e2 tag 0 dma 4096 in
         res 59/40:08:52:55:ee/00:00:00:00:00/e2 Emask 0x2 (HSM violation)
ata1.00: status: { DRDY DRQ ERR }
ata1.00: error: { UNC }
ata1: soft resetting link
ata1.00: configured for PIO4
ata1.01: configured for UDMA/33
ata1: EH complete
ata1: drained 32768 bytes to clear DRQ.
ata1.00: exception Emask 0x0 SAct 0x0 SErr 0x0 action 0x6 frozen
ata1.00: ST-ATA: BUSY|DRQ persists on ERR|DF, dev_stat 0x59
ata1.00: failed command: READ MULTIPLE
ata1.00: cmd c4/00:08:52:55:ee/00:00:00:00:00/e2 tag 0 pio 4096 in
         res 59/40:08:52:55:ee/00:00:00:00:00/e2 Emask 0x3 (HSM violation)
ata1.00: status: { DRDY DRQ ERR }
ata1.00: error: { UNC }
ata1: soft resetting link
ata1.00: configured for PIO4
ata1.01: configured for UDMA/33
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 
        02 ee 55 52 
sd 0:0:0:0: [sda] ASC=0x11 ASCQ=0x4
sd 0:0:0:0: [sda] CDB: cdb[0]=0x28: 28 00 02 ee 55 52 00 00 08 00
end_request: I/O error, dev sda, sector 49173842
ata1: EH complete

Some kind of DMA error I guess? Its a Dell Inspiron 1300 with a SAMSUNG SATA MP0804H 80 gig hd.
heres the hdparm results. buffered disk reads are useally 25-28 mb's a sec

/dev/sda:
Timing cached reads:   864 MB in  2.00 seconds = 431.84 MB/sec
Timing buffered disk reads:    8 MB in  3.53 seconds =   2.27 MB/sec

Thanks

TLDR.  please use the code tags

Hofstadter's Law:
           It always takes longer than you expect, even when you take into account Hofstadter's Law.

Offline

Pages: 1

Board footer

Powered by FluxBB