You are not logged in.
Pages: 1
I have an Alienware 7700 Laptop, its a bit more like a desktop... with a P4 processor, etc..
I've noticed from time to time that the hard drive seemed slow, but I never thought it that much out of the ordinary (I can't say for sure if its always been this way or if this is a recent problem).
Recently I did a hdparm -t /dev/sda and got about 4.5 mb/s. I've since noticed that after a pm-suspend, this is the speed it performs at. However, if I reboot, I get:
anubis@Thorin ~/ $ sudo hdparm -t /dev/sda
/dev/sda:
Timing buffered disk reads: 84 MB in 3.04 seconds = 27.65 MB/sec
Then if I pm-suspend it goes back to 4.5 mb/s. The simple solution would seem to simply not pm-suspend, but I had a new problem last night.
anubis@Thorin ~/ $ cp amtrak1.vob /media/disk/Videos/Home_Videos/
cp: reading `amtrak1.vob': Input/output error
The drive began copying the file more and more slowly, and after this copy failed, I received this speed:
anubis@Thorin ~/ $ sudo hdparm -t /dev/sda
/dev/sda:
Timing buffered disk reads: 4 MB in 3.53 seconds = 1.13 MB/sec
My external hard drive works fine at
anubis@Thorin ~/ $ sudo hdparm -t /dev/sdb
/dev/sdb:
Timing buffered disk reads: 100 MB in 3.03 seconds = 33.00 MB/sec
I don't think it has anything to do with it, but I recently converted the internal laptop hard disk's /root and /home to ext4
sudo hdparm -I /dev/sda
/dev/sda:
ATA device, with non-removable media
Model Number: SAMSUNG MP0603H
Serial Number: S03ZJ10Y628227
Firmware Revision: UD100-14
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: 117304992
LBA48 user addressable sectors: 117304992
Logical/Physical Sector size: 512 bytes
device size with M = 1024*1024: 57277 MBytes
device size with M = 1000*1000: 60060 MBytes (60 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 = ?
Advanced power management level: disabled
Recommended acoustic management value: 254, current value: 0
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
not frozen
not expired: security count
supported: enhanced erase
66min for SECURITY ERASE UNIT. 66min for ENHANCED SECURITY ERASE UNIT.
HW reset results:
CBLID- above Vih
Device num = 0 determined by the jumper
dmesg
ata5.00: exception Emask 0x0 SAct 0x0 SErr 0x0 action 0x6
ata5.00: port_status 0x20280000
ata5.00: cmd c8/00:00:4e:a0:c7/00:00:00:00:00/e5 tag 0 dma 131072 in
res 59/40:1b:33:a1:c7/00:00:00:00:00/e5 Emask 0x3 (HSM violation)
ata5.00: status: { DRDY DRQ ERR }
ata5.00: error: { UNC }
ata5: soft resetting link
ata5.00: configured for UDMA/100
ata5: EH complete
ata5.00: exception Emask 0x0 SAct 0x0 SErr 0x0 action 0x6
ata5.00: port_status 0x20280000
ata5.00: cmd c8/00:00:4e:a0:c7/00:00:00:00:00/e5 tag 0 dma 131072 in
res 59/40:1b:33:a1:c7/00:00:00:00:00/e5 Emask 0x3 (HSM violation)
ata5.00: status: { DRDY DRQ ERR }
ata5.00: error: { UNC }
ata5: soft resetting link
ata5.00: configured for UDMA/100
ata5: EH complete
ata5.00: exception Emask 0x0 SAct 0x0 SErr 0x0 action 0x6
ata5.00: port_status 0x20280000
ata5.00: cmd c8/00:00:4e:a0:c7/00:00:00:00:00/e5 tag 0 dma 131072 in
res 59/40:1b:33:a1:c7/00:00:00:00:00/e5 Emask 0x3 (HSM violation)
ata5.00: status: { DRDY DRQ ERR }
ata5.00: error: { UNC }
ata5: soft resetting link
ata5.00: configured for UDMA/100
ata5: EH complete
ata5.00: limiting speed to UDMA/66:PIO4
ata5.00: exception Emask 0x0 SAct 0x0 SErr 0x0 action 0x6
ata5.00: port_status 0x20280000
ata5.00: cmd c8/00:00:4e:a0:c7/00:00:00:00:00/e5 tag 0 dma 131072 in
res 59/40:1b:33:a1:c7/00:00:00:00:00/e5 Emask 0x3 (HSM violation)
ata5.00: status: { DRDY DRQ ERR }
ata5.00: error: { UNC }
ata5: soft resetting link
ata5.00: configured for UDMA/66
ata5: EH complete
ata5.00: exception Emask 0x0 SAct 0x0 SErr 0x0 action 0x6
ata5.00: port_status 0x20280000
ata5.00: cmd c8/00:00:4e:a0:c7/00:00:00:00:00/e5 tag 0 dma 131072 in
res 59/40:1b:33:a1:c7/00:00:00:00:00/e5 Emask 0x3 (HSM violation)
ata5.00: status: { DRDY DRQ ERR }
ata5.00: error: { UNC }
ata5: soft resetting link
ata5.00: configured for UDMA/66
ata5: EH complete
ata5.00: limiting speed to UDMA/33:PIO4
ata5.00: exception Emask 0x0 SAct 0x0 SErr 0x0 action 0x6
ata5.00: port_status 0x20280000
ata5.00: cmd c8/00:00:4e:a0:c7/00:00:00:00:00/e5 tag 0 dma 131072 in
res 59/40:1b:33:a1:c7/00:00:00:00:00/e5 Emask 0x3 (HSM violation)
ata5.00: status: { DRDY DRQ ERR }
ata5.00: error: { UNC }
ata5: soft resetting link
ata5.00: configured for UDMA/33
sd 4:0:0:0: [sda] Unhandled sense code
sd 4:0:0:0: [sda] Result: hostbyte=0x00 driverbyte=0x08
sd 4: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
05 c7 a1 33
sd 4:0:0:0: [sda] ASC=0x11 ASCQ=0x4
end_request: I/O error, dev sda, sector 96969011
ata5: EH complete
ata5.00: exception Emask 0x0 SAct 0x0 SErr 0x0 action 0x6
ata5.00: port_status 0x20280000
ata5.00: cmd c8/00:08:2e:a1:c7/00:00:00:00:00/e5 tag 0 dma 4096 in
res 59/40:03:33:a1:c7/00:00:00:00:00/e5 Emask 0x3 (HSM violation)
ata5.00: status: { DRDY DRQ ERR }
ata5.00: error: { UNC }
ata5: soft resetting link
ata5.00: configured for UDMA/33
ata5: EH complete
ata5.00: exception Emask 0x0 SAct 0x0 SErr 0x0 action 0x6
ata5.00: port_status 0x20280000
ata5.00: cmd c8/00:08:2e:a1:c7/00:00:00:00:00/e5 tag 0 dma 4096 in
res 59/40:03:33:a1:c7/00:00:00:00:00/e5 Emask 0x3 (HSM violation)
ata5.00: status: { DRDY DRQ ERR }
ata5.00: error: { UNC }
ata5: soft resetting link
ata5.00: configured for UDMA/33
ata5: EH complete
ata5.00: exception Emask 0x0 SAct 0x0 SErr 0x0 action 0x6
ata5.00: port_status 0x20280000
ata5.00: cmd c8/00:08:2e:a1:c7/00:00:00:00:00/e5 tag 0 dma 4096 in
res 59/40:03:33:a1:c7/00:00:00:00:00/e5 Emask 0x3 (HSM violation)
ata5.00: status: { DRDY DRQ ERR }
ata5.00: error: { UNC }
ata5: soft resetting link
ata5.00: configured for UDMA/33
ata5: EH complete
ata5.00: exception Emask 0x0 SAct 0x0 SErr 0x0 action 0x6
ata5.00: port_status 0x20280000
ata5.00: cmd c8/00:08:2e:a1:c7/00:00:00:00:00/e5 tag 0 dma 4096 in
res 59/40:03:33:a1:c7/00:00:00:00:00/e5 Emask 0x3 (HSM violation)
ata5.00: status: { DRDY DRQ ERR }
ata5.00: error: { UNC }
ata5: soft resetting link
ata5.00: configured for UDMA/33
ata5: EH complete
ata5.00: limiting speed to PIO4
ata5.00: exception Emask 0x0 SAct 0x0 SErr 0x0 action 0x6
ata5.00: port_status 0x20280000
ata5.00: cmd c8/00:08:2e:a1:c7/00:00:00:00:00/e5 tag 0 dma 4096 in
res 59/40:03:33:a1:c7/00:00:00:00:00/e5 Emask 0x3 (HSM violation)
ata5.00: status: { DRDY DRQ ERR }
ata5.00: error: { UNC }
ata5: soft resetting link
ata5.00: configured for PIO4
ata5: EH complete
ata5.00: exception Emask 0x0 SAct 0x0 SErr 0x0 action 0x6 frozen
ata5.00: ST-ATA: BUSY|DRQ persists on ERR|DF, dev_stat 0x59
ata5.00: cmd 20/00:08:2e:a1:c7/00:00:00:00:00/e5 tag 0 pio 4096 in
res 59/40:03:33:a1:c7/00:00:00:00:00/e5 Emask 0x3 (HSM violation)
ata5.00: status: { DRDY DRQ ERR }
ata5.00: error: { UNC }
ata5: soft resetting link
ata5.00: configured for PIO4
sd 4:0:0:0: [sda] Unhandled sense code
sd 4:0:0:0: [sda] Result: hostbyte=0x00 driverbyte=0x08
sd 4: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
05 c7 a1 33
sd 4:0:0:0: [sda] ASC=0x11 ASCQ=0x4
end_request: I/O error, dev sda, sector 96969011
ata5: EH complete
ata5.00: exception Emask 0x0 SAct 0x0 SErr 0x0 action 0x6 frozen
ata5.00: ST-ATA: BUSY|DRQ persists on ERR|DF, dev_stat 0x59
ata5.00: cmd 20/00:08:2e:a1:c7/00:00:00:00:00/e5 tag 0 pio 4096 in
res 59/40:03:33:a1:c7/00:00:00:00:00/e5 Emask 0x3 (HSM violation)
ata5.00: status: { DRDY DRQ ERR }
ata5.00: error: { UNC }
ata5: soft resetting link
ata5.00: configured for PIO4
ata5: EH complete
ata5.00: exception Emask 0x0 SAct 0x0 SErr 0x0 action 0x6 frozen
ata5.00: ST-ATA: BUSY|DRQ persists on ERR|DF, dev_stat 0x59
ata5.00: cmd 20/00:08:2e:a1:c7/00:00:00:00:00/e5 tag 0 pio 4096 in
res 59/40:03:33:a1:c7/00:00:00:00:00/e5 Emask 0x3 (HSM violation)
ata5.00: status: { DRDY DRQ ERR }
ata5.00: error: { UNC }
ata5: soft resetting link
ata5.00: configured for PIO4
ata5: EH complete
ata5.00: limiting speed to PIO3
ata5.00: exception Emask 0x0 SAct 0x0 SErr 0x0 action 0x6 frozen
ata5.00: ST-ATA: BUSY|DRQ persists on ERR|DF, dev_stat 0x59
ata5.00: cmd 20/00:08:2e:a1:c7/00:00:00:00:00/e5 tag 0 pio 4096 in
res 59/40:03:33:a1:c7/00:00:00:00:00/e5 Emask 0x3 (HSM violation)
ata5.00: status: { DRDY DRQ ERR }
ata5.00: error: { UNC }
ata5: soft resetting link
ata5.00: configured for PIO3
ata5: EH complete
ata5.00: exception Emask 0x0 SAct 0x0 SErr 0x0 action 0x6 frozen
ata5.00: ST-ATA: BUSY|DRQ persists on ERR|DF, dev_stat 0x59
ata5.00: cmd 20/00:08:2e:a1:c7/00:00:00:00:00/e5 tag 0 pio 4096 in
res 59/40:03:33:a1:c7/00:00:00:00:00/e5 Emask 0x3 (HSM violation)
ata5.00: status: { DRDY DRQ ERR }
ata5.00: error: { UNC }
ata5: soft resetting link
ata5.00: configured for PIO3
ata5: EH complete
ata5.00: limiting speed to PIO0
ata5.00: exception Emask 0x0 SAct 0x0 SErr 0x0 action 0x6 frozen
ata5.00: ST-ATA: BUSY|DRQ persists on ERR|DF, dev_stat 0x59
ata5.00: cmd 20/00:08:2e:a1:c7/00:00:00:00:00/e5 tag 0 pio 4096 in
res 59/40:03:33:a1:c7/00:00:00:00:00/e5 Emask 0x3 (HSM violation)
ata5.00: status: { DRDY DRQ ERR }
ata5.00: error: { UNC }
ata5: soft resetting link
ata5.00: configured for PIO0
ata5: EH complete
ata5.00: exception Emask 0x0 SAct 0x0 SErr 0x0 action 0x6 frozen
ata5.00: ST-ATA: BUSY|DRQ persists on ERR|DF, dev_stat 0x59
ata5.00: cmd 20/00:08:2e:a1:c7/00:00:00:00:00/e5 tag 0 pio 4096 in
res 59/40:03:33:a1:c7/00:00:00:00:00/e5 Emask 0x3 (HSM violation)
ata5.00: status: { DRDY DRQ ERR }
ata5.00: error: { UNC }
ata5: soft resetting link
ata5.00: configured for PIO0
sd 4:0:0:0: [sda] Unhandled sense code
sd 4:0:0:0: [sda] Result: hostbyte=0x00 driverbyte=0x08
sd 4: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
05 c7 a1 33
sd 4:0:0:0: [sda] ASC=0x11 ASCQ=0x4
end_request: I/O error, dev sda, sector 96969011
ata5: EH complete
ata1.00: exception Emask 0x0 SAct 0x0 SErr 0x0 action 0x6 frozen
ata1.00: cmd a0/00:00:00:00:00/00:00:00:00:00/a0 tag 0
cdb 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
res 51/20:03:00:00:00/00:00:00:00:00/a0 Emask 0x3 (HSM violation)
ata1.00: status: { DRDY ERR }
ata1: soft resetting link
ata1.00: configured for UDMA/33
ata1: EH complete
Could the problem be a driver/kernel issue? Or the hard drive itself? or BIOS? I'm completely mystified by extremely slow performance when I try to copy that 2.7 gb file or pm-suspend.
Any society that would give up a little liberty to gain a little security will deserve neither and lose both.
-Benjamin Franklin
The reasonable man adapts himself to the world; the unreasonable one persists in trying to adapt the world to himself. Therefore all progress depends on the unreasonable man.
-George Bernard Shaw
Offline
Perhaps it is not receiving udma status...seems it is running at 66 mode.
Try setting dma with hdparm on that drive.
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
Perhaps it is a power problem.
The external drive is probably externally powered and the laptop drive internally powered.
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
Perhaps you need to defrag the ext4 partition(s). This function is part of the ext4 system.
http://linuxpoison.blogspot.com/2008/05 … -ext4.html
Last edited by lilsirecho (2009-10-28 01:24:07)
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
I've considered defragging it, but that doesn't explain the dma mode problem...
Before trying to copy the file or suspend:
anubis@Thorin ~/ $ sudo hdparm -t -T /dev/sda
Password:
/dev/sda:
Timing cached reads: 1486 MB in 2.00 seconds = 742.58 MB/sec
Timing buffered disk reads: 84 MB in 3.01 seconds = 27.86 MB/sec
anubis@Thorin ~/ $ sudo hdparm -i /dev/sda
/dev/sda:
Model=SAMSUNG MP0603H, FwRev=UD100-14, SerialNo=S03ZJ10Y628227
Config={ HardSect NotMFM HdSw>15uSec Fixed DTR>10Mbs }
RawCHS=16383/16/63, TrkSize=34902, SectSize=554, ECCbytes=4
BuffType=DualPortCache, BuffSize=8192kB, MaxMultSect=16, MultSect=off
CurCHS=16383/16/63, CurSects=16514064, LBA=yes, LBAsects=117304992
IORDY=on/off, tPIO={min:120,w/IORDY:120}, tDMA={min:120,rec:120}
PIO modes: pio0 pio1 pio2 pio3 pio4
DMA modes: mdma0 mdma1 mdma2
UDMA modes: udma0 udma1 udma2 udma3 udma4 *udma5
AdvancedPM=yes: disabled (255) WriteCache=enabled
Drive conforms to: ATA/ATAPI-7 T13 1532D revision 0: ATA/ATAPI-1,2,3,4,5,6,7
* signifies the current active mode
anubis@Thorin ~/ $ cp amtrak1.vob /media/disk/Videos/Home_Videos/
cp: reading `amtrak1.vob': Input/output error
Afterward:
anubis@Thorin ~/ $ sudo hdparm -t -T /dev/sda
/dev/sda:
Timing cached reads: 130 MB in 2.00 seconds = 64.96 MB/sec
Timing buffered disk reads: 4 MB in 3.65 seconds = 1.10 MB/sec
anubis@Thorin ~/ $ sudo hdparm -i /dev/sda
/dev/sda:
Model=SAMSUNG MP0603H, FwRev=UD100-14, SerialNo=S03ZJ10Y628227
Config={ HardSect NotMFM HdSw>15uSec Fixed DTR>10Mbs }
RawCHS=16383/16/63, TrkSize=34902, SectSize=554, ECCbytes=4
BuffType=DualPortCache, BuffSize=8192kB, MaxMultSect=16, MultSect=off
CurCHS=16383/16/63, CurSects=16514064, LBA=yes, LBAsects=117304992
IORDY=on/off, tPIO={min:120,w/IORDY:120}, tDMA={min:120,rec:120}
PIO modes: pio0 pio1 pio2 pio3 pio4
DMA modes: mdma0 mdma1 mdma2
UDMA modes: udma0 udma1 *udma2 udma3 udma4 udma5
AdvancedPM=yes: disabled (255) WriteCache=enabled
Drive conforms to: ATA/ATAPI-7 T13 1532D revision 0: ATA/ATAPI-1,2,3,4,5,6,7
* signifies the current active mode
So, it looks like its switching from udma5 to udma2 for some reason...
I'm not sure how to set it back to udma5, guess i'll try resetting bios or something, and defragging the partitions
Edit: and yes, the external has its own power, but the internal drive seems to operate for a long time at 28ish mb/s, it only seems to lower after a pm-suspend or cping that larger file... so i don't know what kind of power problem it could be
Last edited by 1LordAnubis (2009-10-28 01:35:05)
Any society that would give up a little liberty to gain a little security will deserve neither and lose both.
-Benjamin Franklin
The reasonable man adapts himself to the world; the unreasonable one persists in trying to adapt the world to himself. Therefore all progress depends on the unreasonable man.
-George Bernard Shaw
Offline
Perhaps the longish file run affects the cpu temp causing it to throttle....high cpu useage.
The reversion in DMA is quirky...suggests some problem in libata like we once had.............
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
Hmm, I just checked before and after a pm-suspend
after a pm-suspend I get
anubis@Thorin ~/ $ sudo hdparm -t -T /dev/sda
/dev/sda:
Timing cached reads: 1248 MB in 2.00 seconds = 623.48 MB/sec
Timing buffered disk reads: 14 MB in 3.19 seconds = 4.40 MB/sec
anubis@Thorin ~/ $ sudo hdparm -i /dev/sda
/dev/sda:
Model=SAMSUNG MP0603H, FwRev=UD100-14, SerialNo=S03ZJ10Y628227
Config={ HardSect NotMFM HdSw>15uSec Fixed DTR>10Mbs }
RawCHS=16383/16/63, TrkSize=34902, SectSize=554, ECCbytes=4
BuffType=DualPortCache, BuffSize=8192kB, MaxMultSect=16, MultSect=off
CurCHS=16383/16/63, CurSects=16514064, LBA=yes, LBAsects=117304992
IORDY=on/off, tPIO={min:120,w/IORDY:120}, tDMA={min:120,rec:120}
PIO modes: pio0 pio1 pio2 pio3 pio4
DMA modes: mdma0 mdma1 mdma2
UDMA modes: udma0 udma1 udma2 udma3 udma4 *udma5
AdvancedPM=yes: disabled (255) WriteCache=enabled
Drive conforms to: ATA/ATAPI-7 T13 1532D revision 0: ATA/ATAPI-1,2,3,4,5,6,7
* signifies the current active mode
So yeah, it stayed in the same udma mode, but i lost a lot of speed....
I checked the bios, and it says that IDE drive is set to mode 2... However, the BIOS doesn't seem to let me change any settings on the drive...
Edit: the temperature of my cpu is not the problem, I did a render that ran my cpu at 100% for a long time, with no trouble, this only yields a ~30% cpu load, which is about the normal cpu temp.... aka no throttling
Last edited by 1LordAnubis (2009-10-28 01:55:27)
Any society that would give up a little liberty to gain a little security will deserve neither and lose both.
-Benjamin Franklin
The reasonable man adapts himself to the world; the unreasonable one persists in trying to adapt the world to himself. Therefore all progress depends on the unreasonable man.
-George Bernard Shaw
Offline
Anyone know how to defrag ext4? I found a script here.. http://ck.kolivas.org/apps/defrag/defrag-0.06/defrag
Any society that would give up a little liberty to gain a little security will deserve neither and lose both.
-Benjamin Franklin
The reasonable man adapts himself to the world; the unreasonable one persists in trying to adapt the world to himself. Therefore all progress depends on the unreasonable man.
-George Bernard Shaw
Offline
Bios usually permits setting to max DMA for the drive.
Perhaps....the drive is not fully connected, accounting for the discrepant dma levels.
My last gasp!
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
you might have a dead or dying drive. a few years ago i had an alienware laptop, which was suffering from the hdd [loadcycle hdd killer problem]. point is, linux was not doing a good job preventing the laptop hdd's from parking or spinning down too much, and the drives aged a lot faster than designed because linux was basically parking them [correct me if i have the technical facts wrong]. at any rate, my hdd died on the laptop, followed by the laptop itself dying (unrelated).
[edit] found a link for the issue i'm talking about, i wasnt that far off
http://ubuntudemon.wordpress.com/2007/1 … -affected/
the key command is
sudo smartctl -a /dev/sda | grep Load_Cycle_Count
if it's too high, or increases daily by more than 90, that's bad.
but that was my experience, this may be unrelated, it just sounded so much like my experience when you said alienware, hdd not working well.
Last edited by toxygen (2009-10-28 02:19:16)
"I know what you're thinking, 'cause right now I'm thinking the same thing. Actually, I've been thinking it ever since I got here:
Why oh why didn't I take the BLUE pill?"
Offline
This BIOS won't let me change the DMA settings; its a phoenix bios, and it says to contact the system administrator or something...
Anyway, I tried a new test... I copied another file (4.3 gb) from sdb to sda ~/Desktop, and then copied that back to sdb, and there were no problems... the drive was operating normally...
So perhaps when I copied the file the first time it was actually corrupt for some reason? .. I'm still not sure why the drive changes modes when it encounters this problem... and why it slows down when I pm-suspend, but large transfers seem to be working.
Perhaps you were correct when assuming the high temperature; I encoded a .vob file for about 2 hours at ~100% cpu, perhaps that caused the drive to slow down/corrupt? or perhaps I should defrag ext4?... guess I need to redo the video and see what happens.
Any society that would give up a little liberty to gain a little security will deserve neither and lose both.
-Benjamin Franklin
The reasonable man adapts himself to the world; the unreasonable one persists in trying to adapt the world to himself. Therefore all progress depends on the unreasonable man.
-George Bernard Shaw
Offline
you might have a dead or dying drive. a few years ago i had an alienware laptop, which was suffering from the hdd [loadcycle hdd killer problem]. point is, linux was not doing a good job preventing the laptop hdd's from parking or spinning down too much, and the drives aged a lot faster than designed because linux was basically parking them [correct me if i have the technical facts wrong]. at any rate, my hdd died on the laptop, followed by the laptop itself dying (unrelated).
[edit] found a link for the issue i'm talking about, i wasnt that far off
http://ubuntudemon.wordpress.com/2007/1 … -affected/the key command is
sudo smartctl -a /dev/sda | grep Load_Cycle_Countif it's too high, or increases daily by more than 90, that's bad.
but that was my experience, this may be unrelated, it just sounded so much like my experience when you said alienware, hdd not working well.
Thats actually here in the arch wiki:
http://wiki.archlinux.org/index.php/Lap … wn_problem
I have it set to 255 (power management disabled)
Although, it took me awhile before I did this, so maybe the Alienware hard drive is doomed anyway. From what I've heard, linux does what the manufacturer does by default, which makes the hard drive spin down a little too often for good longevity... windows does something else by default... and on linux its up to you to do something else by default.
Anyway:
anubis@Thorin ~/ $ sudo smartctl -a /dev/sda | grep Load_Cycle_Count
225 Load_Cycle_Count 0x0012 039 039 000 Old_age Always - 626045
Any society that would give up a little liberty to gain a little security will deserve neither and lose both.
-Benjamin Franklin
The reasonable man adapts himself to the world; the unreasonable one persists in trying to adapt the world to himself. Therefore all progress depends on the unreasonable man.
-George Bernard Shaw
Offline
Hmm...
anubis@Thorin ~/ $ sudo smartctl -H /dev/sda
Password:
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 overall-health self-assessment test result: PASSED
anubis@Thorin ~/ $ sudo smartctl -l error /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 Error Log Version: 1
ATA Error Count: 60 (device log contains only the most recent five errors)
CR = Command Register [HEX]
FR = Features Register [HEX]
SC = Sector Count Register [HEX]
SN = Sector Number Register [HEX]
CL = Cylinder Low Register [HEX]
CH = Cylinder High Register [HEX]
DH = Device/Head Register [HEX]
DC = Device Command Register [HEX]
ER = Error register [HEX]
ST = Status register [HEX]
Powered_Up_Time is measured from power on, and printed as
DDd+hh:mm:SS.sss where DD=days, hh=hours, mm=minutes,
SS=sec, and sss=millisec. It "wraps" after 49.710 days.
Error 60 occurred at disk power-on lifetime: 2989 hours (124 days + 13 hours)
When the command that caused the error occurred, the device was active or idle.
After command completion occurred, registers were:
ER ST SC SN CL CH DH
-- -- -- -- -- -- --
40 51 08 2e a1 c7 e5 Error: UNC at LBA = 0x05c7a12e = 96969006
Commands leading to the command that caused the error were:
CR FR SC SN CL CH DH DC Powered_Up_Time Command/Feature_Name
-- -- -- -- -- -- -- -- ---------------- --------------------
20 00 08 2e a1 c7 e5 00 03:38:10.563 READ SECTOR(S)
ec 00 00 00 00 00 a0 00 03:38:10.563 IDENTIFY DEVICE
ef 03 08 00 00 00 a0 00 03:38:10.563 SET FEATURES [Set transfer mode]
ec 00 00 00 00 00 a0 00 03:38:10.563 IDENTIFY DEVICE
00 00 01 01 00 00 a0 00 03:38:10.438 NOP [Abort queued commands]
Error 59 occurred at disk power-on lifetime: 2989 hours (124 days + 13 hours)
When the command that caused the error occurred, the device was active or idle.
After command completion occurred, registers were:
ER ST SC SN CL CH DH
-- -- -- -- -- -- --
40 51 08 2e a1 c7 e5 Error: UNC at LBA = 0x05c7a12e = 96969006
Commands leading to the command that caused the error were:
CR FR SC SN CL CH DH DC Powered_Up_Time Command/Feature_Name
-- -- -- -- -- -- -- -- ---------------- --------------------
20 00 08 2e a1 c7 e5 00 03:38:09.000 READ SECTOR(S)
ec 00 00 00 00 00 a0 00 03:38:09.000 IDENTIFY DEVICE
ef 03 0b 00 00 00 a0 00 03:38:09.000 SET FEATURES [Set transfer mode]
ec 00 00 00 00 00 a0 00 03:38:09.000 IDENTIFY DEVICE
00 00 01 01 00 00 a0 00 03:38:08.875 NOP [Abort queued commands]
Error 58 occurred at disk power-on lifetime: 2989 hours (124 days + 13 hours)
When the command that caused the error occurred, the device was active or idle.
After command completion occurred, registers were:
ER ST SC SN CL CH DH
-- -- -- -- -- -- --
40 51 08 2e a1 c7 e5 Error: UNC at LBA = 0x05c7a12e = 96969006
Commands leading to the command that caused the error were:
CR FR SC SN CL CH DH DC Powered_Up_Time Command/Feature_Name
-- -- -- -- -- -- -- -- ---------------- --------------------
20 00 08 2e a1 c7 e5 00 03:38:07.438 READ SECTOR(S)
ec 00 00 00 00 00 a0 00 03:38:07.438 IDENTIFY DEVICE
ef 03 0b 00 00 00 a0 00 03:38:07.438 SET FEATURES [Set transfer mode]
ec 00 00 00 00 00 a0 00 03:38:07.438 IDENTIFY DEVICE
00 00 01 01 00 00 a0 00 03:38:07.313 NOP [Abort queued commands]
Error 57 occurred at disk power-on lifetime: 2989 hours (124 days + 13 hours)
When the command that caused the error occurred, the device was active or idle.
After command completion occurred, registers were:
ER ST SC SN CL CH DH
-- -- -- -- -- -- --
40 51 08 2e a1 c7 e5 Error: UNC at LBA = 0x05c7a12e = 96969006
Commands leading to the command that caused the error were:
CR FR SC SN CL CH DH DC Powered_Up_Time Command/Feature_Name
-- -- -- -- -- -- -- -- ---------------- --------------------
20 00 08 2e a1 c7 e5 00 03:38:05.875 READ SECTOR(S)
ec 00 00 00 00 00 a0 00 03:38:05.813 IDENTIFY DEVICE
ef 03 0c 00 00 00 a0 00 03:38:05.813 SET FEATURES [Set transfer mode]
ec 00 00 00 00 00 a0 00 03:38:05.813 IDENTIFY DEVICE
00 00 01 01 00 00 a0 00 03:38:05.688 NOP [Abort queued commands]
Error 56 occurred at disk power-on lifetime: 2989 hours (124 days + 13 hours)
When the command that caused the error occurred, the device was active or idle.
After command completion occurred, registers were:
ER ST SC SN CL CH DH
-- -- -- -- -- -- --
40 51 08 2e a1 c7 e5 Error: UNC at LBA = 0x05c7a12e = 96969006
Commands leading to the command that caused the error were:
CR FR SC SN CL CH DH DC Powered_Up_Time Command/Feature_Name
-- -- -- -- -- -- -- -- ---------------- --------------------
20 00 08 2e a1 c7 e5 00 03:38:04.250 READ SECTOR(S)
ec 00 00 00 00 00 a0 00 03:38:04.250 IDENTIFY DEVICE
ef 03 0c 00 00 00 a0 00 03:38:04.250 SET FEATURES [Set transfer mode]
ec 00 00 00 00 00 a0 00 03:38:04.250 IDENTIFY DEVICE
00 00 01 01 00 00 a0 00 03:38:04.188 NOP [Abort queued commands]
I wonder what those errors indicate....
Any society that would give up a little liberty to gain a little security will deserve neither and lose both.
-Benjamin Franklin
The reasonable man adapts himself to the world; the unreasonable one persists in trying to adapt the world to himself. Therefore all progress depends on the unreasonable man.
-George Bernard Shaw
Offline
225 Load_Cycle_Count 0x0012 039 039 000 Old_age Always - 626045
I had that same result on the alienware laptop. It went from old age to failing within a couple of weeks, but that was mainly because my load_cycle_count was much higher, i dont remember the exact number.
edit to add - do you get a lot of kernel errors?
cat /var/log/kernel.log
or /var/log/errors.log
those errors on your second post remind me of the ones i used to see on the logs, and i had a lot of problems copying large files, with crc errors all over the place.
Last edited by toxygen (2009-10-28 06:19:58)
"I know what you're thinking, 'cause right now I'm thinking the same thing. Actually, I've been thinking it ever since I got here:
Why oh why didn't I take the BLUE pill?"
Offline
Hmm, guess I'll have to test it more... it appears the errors I got were related to that file transfer. But yeah, I wonder how long "Old Age" will hold up.
Oct 27 21:23:22 Thorin kernel: ata5.00: status: { DRDY DRQ ERR }
Oct 27 21:23:22 Thorin kernel: ata5.00: error: { UNC }
Oct 27 21:23:22 Thorin kernel: ata5.00: exception Emask 0x0 SAct 0x0 SErr 0x0 action 0x6 frozen
Oct 27 21:23:22 Thorin kernel: ata5.00: ST-ATA: BUSY|DRQ persists on ERR|DF, dev_stat 0x59
Oct 27 21:23:22 Thorin kernel: ata5.00: cmd 20/00:08:2e:a1:c7/00:00:00:00:00/e5 tag 0 pio 4096 in
Oct 27 21:23:22 Thorin kernel: res 59/40:03:33:a1:c7/00:00:00:00:00/e5 Emask 0x3 (HSM violation)
Oct 27 21:23:22 Thorin kernel: ata5.00: status: { DRDY DRQ ERR }
Oct 27 21:23:22 Thorin kernel: ata5.00: error: { UNC }
Oct 27 21:23:22 Thorin kernel: end_request: I/O error, dev sda, sector 96969011
Oct 27 21:23:22 Thorin kernel: ata5.00: exception Emask 0x0 SAct 0x0 SErr 0x0 action 0x6 frozen
Oct 27 21:23:22 Thorin kernel: ata5.00: ST-ATA: BUSY|DRQ persists on ERR|DF, dev_stat 0x59
Oct 27 21:23:22 Thorin kernel: ata5.00: cmd 20/00:08:2e:a1:c7/00:00:00:00:00/e5 tag 0 pio 4096 in
Oct 27 21:23:22 Thorin kernel: res 59/40:03:33:a1:c7/00:00:00:00:00/e5 Emask 0x3 (HSM violation)
Oct 27 21:23:22 Thorin kernel: ata5.00: status: { DRDY DRQ ERR }
Oct 27 21:23:22 Thorin kernel: ata5.00: error: { UNC }
Oct 27 21:23:22 Thorin kernel: ata5.00: exception Emask 0x0 SAct 0x0 SErr 0x0 action 0x6 frozen
Oct 27 21:23:22 Thorin kernel: ata5.00: ST-ATA: BUSY|DRQ persists on ERR|DF, dev_stat 0x59
Oct 27 21:23:22 Thorin kernel: ata5.00: cmd 20/00:08:2e:a1:c7/00:00:00:00:00/e5 tag 0 pio 4096 in
Oct 27 21:23:22 Thorin kernel: res 59/40:03:33:a1:c7/00:00:00:00:00/e5 Emask 0x3 (HSM violation)
Oct 27 21:23:22 Thorin kernel: ata5.00: status: { DRDY DRQ ERR }
Oct 27 21:23:22 Thorin kernel: ata5.00: error: { UNC }
Oct 27 21:23:22 Thorin kernel: ata5.00: exception Emask 0x0 SAct 0x0 SErr 0x0 action 0x6 frozen
Oct 27 21:23:22 Thorin kernel: ata5.00: ST-ATA: BUSY|DRQ persists on ERR|DF, dev_stat 0x59
Oct 27 21:23:22 Thorin kernel: ata5.00: cmd 20/00:08:2e:a1:c7/00:00:00:00:00/e5 tag 0 pio 4096 in
Oct 27 21:23:22 Thorin kernel: res 59/40:03:33:a1:c7/00:00:00:00:00/e5 Emask 0x3 (HSM violation)
Oct 27 21:23:22 Thorin kernel: ata5.00: status: { DRDY DRQ ERR }
Oct 27 21:23:22 Thorin kernel: ata5.00: error: { UNC }
Oct 27 21:23:22 Thorin kernel: ata5.00: exception Emask 0x0 SAct 0x0 SErr 0x0 action 0x6 frozen
Oct 27 21:23:22 Thorin kernel: ata5.00: ST-ATA: BUSY|DRQ persists on ERR|DF, dev_stat 0x59
Oct 27 21:23:22 Thorin kernel: ata5.00: cmd 20/00:08:2e:a1:c7/00:00:00:00:00/e5 tag 0 pio 4096 in
Oct 27 21:23:22 Thorin kernel: res 59/40:03:33:a1:c7/00:00:00:00:00/e5 Emask 0x3 (HSM violation)
Oct 27 21:23:22 Thorin kernel: ata5.00: status: { DRDY DRQ ERR }
Oct 27 21:23:22 Thorin kernel: ata5.00: error: { UNC }
Oct 27 21:23:22 Thorin kernel: ata5.00: exception Emask 0x0 SAct 0x0 SErr 0x0 action 0x6 frozen
Oct 27 21:23:22 Thorin kernel: ata5.00: ST-ATA: BUSY|DRQ persists on ERR|DF, dev_stat 0x59
Oct 27 21:23:22 Thorin kernel: ata5.00: cmd 20/00:08:2e:a1:c7/00:00:00:00:00/e5 tag 0 pio 4096 in
Oct 27 21:23:22 Thorin kernel: res 59/40:03:33:a1:c7/00:00:00:00:00/e5 Emask 0x3 (HSM violation)
Oct 27 21:23:22 Thorin kernel: ata5.00: status: { DRDY DRQ ERR }
Oct 27 21:23:22 Thorin kernel: ata5.00: error: { UNC }
Oct 27 21:23:22 Thorin kernel: ata5.00: exception Emask 0x0 SAct 0x0 SErr 0x0 action 0x6 frozen
Oct 27 21:23:22 Thorin kernel: ata5.00: ST-ATA: BUSY|DRQ persists on ERR|DF, dev_stat 0x59
Oct 27 21:23:22 Thorin kernel: ata5.00: cmd 20/00:08:2e:a1:c7/00:00:00:00:00/e5 tag 0 pio 4096 in
Oct 27 21:23:22 Thorin kernel: res 59/40:03:33:a1:c7/00:00:00:00:00/e5 Emask 0x3 (HSM violation)
Oct 27 21:23:22 Thorin kernel: ata5.00: status: { DRDY DRQ ERR }
Oct 27 21:23:22 Thorin kernel: ata5.00: error: { UNC }
Oct 27 21:23:22 Thorin kernel: end_request: I/O error, dev sda, sector 96969011
Any society that would give up a little liberty to gain a little security will deserve neither and lose both.
-Benjamin Franklin
The reasonable man adapts himself to the world; the unreasonable one persists in trying to adapt the world to himself. Therefore all progress depends on the unreasonable man.
-George Bernard Shaw
Offline
if you still have it under warranty, i'd send it back to alienware and have them replace the drive (when they test it they'll see the same "old age" or "failing" results). otherwise you'll be looking at a dead duck soon.
"I know what you're thinking, 'cause right now I'm thinking the same thing. Actually, I've been thinking it ever since I got here:
Why oh why didn't I take the BLUE pill?"
Offline
Well, the laptop is >4 years old, and gets a decent 10000 fps in glxgears, so whatever. I guess i'll have to back important stuff up and perhaps get a new drive...
The funny thing is that my thinkpad says old age at 543193 cycles, and I've experienced no disk problems....
Any society that would give up a little liberty to gain a little security will deserve neither and lose both.
-Benjamin Franklin
The reasonable man adapts himself to the world; the unreasonable one persists in trying to adapt the world to himself. Therefore all progress depends on the unreasonable man.
-George Bernard Shaw
Offline
Pages: 1