Linux - HardwareThis forum is for Hardware issues.
Having trouble installing a piece of hardware? Want to know if that peripheral is compatible with Linux?
Notices
Welcome to LinuxQuestions.org, a friendly and active Linux Community.
You are currently viewing LQ as a guest. By joining our community you will have the ability to post topics, receive our newsletter, use the advanced search, subscribe to threads and access many other special features. Registration is quick, simple and absolutely free. Join our community today!
Note that registered members see fewer ads, and ContentLink is completely disabled once you log in.
If you have any problems with the registration process or your account login, please contact us. If you need to reset your password, click here.
Having a problem logging in? Please visit this page to clear all LQ-related cookies.
Get a virtual cloud desktop with the Linux distro that you want in less than five minutes with Shells! With over 10 pre-installed distros to choose from, the worry-free installation life is here! Whether you are a digital nomad or just looking for flexibility, Shells can put your Linux machine on the device that you want to use.
Exclusive for LQ members, get up to 45% off per month. Click here for more info.
Hi, I'm currently using the 2.6.19-gentoo-r5 sources for a home server. I used to have w2k3 but after a little while I moved to Gentoo (my main system on my PC is also Gentoo).
I noticed from the beginning that Samba transfers were really slow (4/5/6 (6 if I get lucky) MB/sec on a 100mbps LAN), so I started using FTP, which was a little better but not where it should be. I also noticed that when transferring, CPU usage went through the roof, stuck at 100%, both with Samba and FTP.
The disk is a 7200RPM 80GB Seagate Barracuda, using a 40pin ATA cable, on a Soyo 7VBA motherboard, with a P3 633MHz and 512MB. I have (or at least I guess I have) the necessary drivers compiled in the kernel
Code:
<*> ATA/ATAPI/MFM/RLL support
<*> Enhanced IDE/MFM/RLL disk/cdrom/tape/floppy support
<*> Include IDE/ATA-2 DISK support
[*] Use multi-mode by default
<*> Include IDE/ATAPI CDROM support
<*> generic/default IDE chipset support
[*] CMD640 chipset bugfix/support
[*] PCI IDE chipset support
[*] Sharing PCI IDE interrupts support
<*> Generic PCI IDE Chipset Support
<*> RZ1000 chipset bugfix/support
[*] Generic PCI bus-master DMA support
[*] Use PCI DMA by default when available
<*> VIA82CXXX chipset support
Those are all the options under ATA/ATAPI/MFM/RLL support. I used to have enabled the new SATA support (for PATA & stuff) section but disabled it as I'm not sure which one of them (the normal ATA or the new SATA) to use (anyways, I've made some reading and the drive shows up as hda so I guess the ATA section is the one that recognizes the drive).
tanya godlike # hdparm -d1 /dev/hda
/dev/hda:
setting using_dma to 1 (on)
using_dma = 1 (on)
tanya linux # hdparm -tT /dev/hda
/dev/hda:
Timing cached reads: 400 MB in 2.02 seconds = 198.44 MB/sec
Timing buffered disk reads: 52 MB in 3.01 seconds = 17.28 MB/sec
Of course, CPU Usage during the hdparm test went through the roof too.
Neither top nor ps show any cpu-eating process during disk i/o usage (when CPU % explodes), and that this also happens when deleting files (which takes longer than usual).
I don't know if those values are OK, but I keep getting 100% cpu usage.
I believe I have something wrong on the kernel config, as I have this same kernel on my PC (which is a DFI Lanparty NF4 with a SATA2 7200RPM 320GB Seagate disk) and I also get 100% cpu usage when using the disk, but this later issue is subject for another thread and not this one :P. I'm mainly worried about my server issue, and I'll worry about my PC issue later.
In case anyone is wondering, maybe I should remark that I didn't have this issue when I was using w2k3.
It could be the hard drive is going. I suggest using hard drives from ether Hitachi or Western Digital. Hitachi has a terabyte hard drive that is fast in sequential read/write and accessing times are good. Also it is said to be low noise. For less than 400 US dollars, it is a steal.
Check the IDE cable. If is mangled, replace the cable.
Another problem that does not show in any test is the age of the power supply. Seagate drives are pickier on the quality of the power supply.
I have Athlon 700 MHz (Slot A) with 512 MB of ECC SDRAM memory, I did not experience any slowness in Mandrake 9 with SAMBA. The system gets 10 to 12 MB per second when sending or receiving files. Though right now, it is compiling programs to get ready to be as a server. The distribution is Gentoo. The filesystem that is uses to serve files is XFS. I am thinking of upgrading its memory to a gigabyte or more and maybe getting the terabyte hard drive.
Read that there thread first.. Funny, there have been a rash of DMA issues lately..
Also, all IDE cables are 40 pins, but have a good close look at yours and let us know if it is a 40 WIRE or 80-WIRE variety. Modern drives and machinery won't go over UDMA-2 unless they have an 80-conductor wire.
You can tell by either counting the wires in the cable (a rough count is good enough) or by placing a 40 wire beside an 80-wire and the difference is obvious.
Also, note that on some|all|many machines, ide0 is capable of higher transfer speeds than ide1.
You perhaps want to type 'hdparm -Ii /dev/hda' or 'smartctl --all /dev/hda' in a console. The first will give you identifying info on the drive itself (note the DMA level) and the smartctl command will give you SMART diagnostic info from the drive, where you can look for drive troubles.
So.. Let us know what happens next/how you make out
@ Electro - LOL every time I run into you, I learn something thanks for the info re: seagates and power supplies. Useful for me, I just got a brand new one again.
Last edited by GrapefruiTgirl; 05-06-2007 at 09:24 PM.
Thanks for the tips. Although I'm currently not looking for a larger drive :P also I'm from Argentina so, drives so big haven't massively arrived here yet.
Yes, excuse my mistake, it's a 40 WIRE cable, that's what I meant. And I know about the udma2 limit for these cables, but the weird thing is that hdparm reports the drive as working in udma4. I set it recently to udma2 but the CPU usage was as high as usual (and the test results were roughly the same), so I set it back to udma4 =/ (although I know it's physically impossible).
That's the reason why I think it is a kernel-related problem. I've been using this drive until this summer as my main drive on my computer with no problems at all, and kept on using it on the server for a while on w2k3 before moving to Gentoo. And I never had any issue like this.
What keeps knocking me out is that I have the correct drivers loaded on the kernel. Or at least I think I have. I don't know if I should disable this ATA section in favor of the new ATA/SATA section. What would you recommend?
Oh, btw, the results:
Code:
tanya godlike # hdparm -Ii /dev/hda
/dev/hda:
Model=ST380021A, FwRev=3.19, SerialNo=3HV37EGR
Config={ HardSect NotMFM HdSw>15uSec Fixed DTR>10Mbs RotSpdTol>.5% }
RawCHS=16383/16/63, TrkSize=0, SectSize=0, ECCbytes=4
BuffType=unknown, BuffSize=2048kB, MaxMultSect=16, MultSect=16
CurCHS=4047/16/255, CurSects=16511760, LBA=yes, LBAsects=156301488
IORDY=on/off, tPIO={min:240,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=no WriteCache=enabled
Drive conforms to: Unspecified: ATA/ATAPI-1 ATA/ATAPI-2 ATA/ATAPI-3 ATA/ATAPI-4 ATA/ATAPI-5
* signifies the current active mode
ATA device, with non-removable media
Model Number: ST380021A
Serial Number: 3HV37EGR
Firmware Revision: 3.19
Standards:
Supported: 5 4 3
Likely used: 6
Configuration:
Logical max current
cylinders 16383 4047
heads 16 16
sectors/track 63 255
--
CHS current addressable sectors: 16511760
LBA user addressable sectors: 156301488
device size with M = 1024*1024: 76319 MBytes
device size with M = 1000*1000: 80026 MBytes (80 GB)
Capabilities:
LBA, IORDY(can be disabled)
bytes avail on r/w long: 4
Standby timer values: spec'd by Standard
R/W multiple sector transfer: Max = 16 Current = 16
Recommended acoustic management value: 128, 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=240ns 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
SET_MAX security extension
* Automatic Acoustic Management feature set
Device Configuration Overlay feature set
Security:
Master password revision code = 65534
supported
not enabled
not locked
not frozen
not expired: security count
not supported: enhanced erase
HW reset results:
CBLID- above Vih
Device num = 1
Checksum: correct
tanya godlike # smartctl --all /dev/hda
smartctl version 5.36 [i686-pc-linux-gnu] Copyright (C) 2002-6 Bruce Allen
Home page is http://smartmontools.sourceforge.net/
=== START OF INFORMATION SECTION ===
Model Family: Seagate Barracuda ATA IV family
Device Model: ST380021A
Serial Number: 3HV37EGR
Firmware Version: 3.19
User Capacity: 80,026,361,856 bytes
Device is: In smartctl database [for details use: -P show]
ATA Version is: 5
ATA Standard is: Exact ATA specification draft version not indicated
Local Time is: Mon May 7 02:26:54 2007 ART
SMART support is: Available - device has SMART capability.
SMART support is: Disabled
SMART Disabled. Use option -s with argument 'on' to enable it.
First things first -- If your BIOS has an option for SMART test during boot, enable that, and you *might* get some indications when you boot, if there is an internal problem.
My new Seagate drive worked like a charm for almost 5 months before the problems developed, and then I had to exchange it as defective; I have an exact replacement now, which again works perfect.
As that output suggests, read up on SMART, and the smartd daemon and enable SMART for the drive if possible. You will get much more info from the drive.
I'll post my kernel ATA config section for you to compare. NOTE: I use kernel 2.6.20, on Slackware 11... Perhaps comparing my kernel harddisk section to yours might give you some indication if something is misconfigured, but pay attention to any specific differences for your controller/chipset etc..
Here's my HD-related kernel config stuff for comparison:
(NOTE - I have an Intel i845PE motherboard, Seagate 320MB drive and Western Digital secondary hard drive; also a CDRW and DVDROM --- so some of this stuff may apply, and some not.)
Code:
# Block devices
#
CONFIG_BLK_DEV_FD=y
# CONFIG_PARIDE is not set
# CONFIG_BLK_CPQ_DA is not set
# CONFIG_BLK_CPQ_CISS_DA is not set
# CONFIG_BLK_DEV_DAC960 is not set
# CONFIG_BLK_DEV_UMEM is not set
# CONFIG_BLK_DEV_COW_COMMON is not set
CONFIG_BLK_DEV_LOOP=y
# CONFIG_BLK_DEV_CRYPTOLOOP is not set
# CONFIG_BLK_DEV_NBD is not set
# CONFIG_BLK_DEV_SX8 is not set
CONFIG_BLK_DEV_UB=y
# CONFIG_BLK_DEV_RAM is not set
# CONFIG_BLK_DEV_INITRD is not set
CONFIG_CDROM_PKTCDVD=y
CONFIG_CDROM_PKTCDVD_BUFFERS=16
# CONFIG_CDROM_PKTCDVD_WCACHE is not set
# CONFIG_ATA_OVER_ETH is not set
#
# Misc devices
#
# CONFIG_IBM_ASM is not set
# CONFIG_SGI_IOC4 is not set
# CONFIG_TIFM_CORE is not set
#
# ATA/ATAPI/MFM/RLL support
#
CONFIG_IDE=y
CONFIG_BLK_DEV_IDE=y
#
# Please see Documentation/ide.txt for help/info on IDE drives
#
# CONFIG_BLK_DEV_IDE_SATA is not set
# CONFIG_BLK_DEV_HD_IDE is not set
CONFIG_BLK_DEV_IDEDISK=y
CONFIG_IDEDISK_MULTI_MODE=y
CONFIG_BLK_DEV_IDECD=y
# CONFIG_BLK_DEV_IDETAPE is not set
# CONFIG_BLK_DEV_IDEFLOPPY is not set
# CONFIG_BLK_DEV_IDESCSI is not set
CONFIG_IDE_TASK_IOCTL=y
#
# IDE chipset support/bugfixes
#
CONFIG_IDE_GENERIC=y
# CONFIG_BLK_DEV_CMD640 is not set
# CONFIG_BLK_DEV_IDEPNP is not set
CONFIG_BLK_DEV_IDEPCI=y
CONFIG_IDEPCI_SHARE_IRQ=y
# CONFIG_BLK_DEV_OFFBOARD is not set
CONFIG_BLK_DEV_GENERIC=y
# CONFIG_BLK_DEV_OPTI621 is not set
# CONFIG_BLK_DEV_RZ1000 is not set
CONFIG_BLK_DEV_IDEDMA_PCI=y
# CONFIG_BLK_DEV_IDEDMA_FORCED is not set
CONFIG_IDEDMA_PCI_AUTO=y
# CONFIG_IDEDMA_ONLYDISK is not set
# CONFIG_BLK_DEV_AEC62XX is not set
# CONFIG_BLK_DEV_ALI15X3 is not set
# CONFIG_BLK_DEV_AMD74XX is not set
# CONFIG_BLK_DEV_ATIIXP is not set
# CONFIG_BLK_DEV_CMD64X is not set
# CONFIG_BLK_DEV_TRIFLEX is not set
# CONFIG_BLK_DEV_CY82C693 is not set
# CONFIG_BLK_DEV_CS5520 is not set
# CONFIG_BLK_DEV_CS5530 is not set
# CONFIG_BLK_DEV_CS5535 is not set
# CONFIG_BLK_DEV_HPT34X is not set
# CONFIG_BLK_DEV_HPT366 is not set
# CONFIG_BLK_DEV_JMICRON is not set
# CONFIG_BLK_DEV_SC1200 is not set
CONFIG_BLK_DEV_PIIX=y
# CONFIG_BLK_DEV_IT821X is not set
# CONFIG_BLK_DEV_NS87415 is not set
# CONFIG_BLK_DEV_PDC202XX_OLD is not set
CONFIG_BLK_DEV_PDC202XX_NEW=y
# CONFIG_BLK_DEV_SVWKS is not set
# CONFIG_BLK_DEV_SIIMAGE is not set
# CONFIG_BLK_DEV_SIS5513 is not set
# CONFIG_BLK_DEV_SLC90E66 is not set
# CONFIG_BLK_DEV_TRM290 is not set
# CONFIG_BLK_DEV_VIA82CXXX is not set
# CONFIG_IDE_ARM is not set
CONFIG_BLK_DEV_IDEDMA=y
CONFIG_IDEDMA_IVB=y
CONFIG_IDEDMA_AUTO=y
# CONFIG_BLK_DEV_HD is not set
#
# SCSI device support
#
# CONFIG_RAID_ATTRS is not set
CONFIG_SCSI=m
CONFIG_SCSI_TGT=m
# CONFIG_SCSI_NETLINK is not set
CONFIG_SCSI_PROC_FS=y
#
# SCSI support type (disk, tape, CD-ROM)
#
# CONFIG_BLK_DEV_SD is not set
# CONFIG_CHR_DEV_ST is not set
# CONFIG_CHR_DEV_OSST is not set
# CONFIG_BLK_DEV_SR is not set
# CONFIG_CHR_DEV_SG is not set
# CONFIG_CHR_DEV_SCH is not set
#
# Some SCSI devices (e.g. CD jukebox) support multiple LUNs
#
# CONFIG_SCSI_MULTI_LUN is not set
# CONFIG_SCSI_CONSTANTS is not set
# CONFIG_SCSI_LOGGING is not set
# CONFIG_SCSI_SCAN_ASYNC is not set
#
# SCSI Transports
#
# CONFIG_SCSI_SPI_ATTRS is not set
# CONFIG_SCSI_FC_ATTRS is not set
# CONFIG_SCSI_ISCSI_ATTRS is not set
# CONFIG_SCSI_SAS_ATTRS is not set
# CONFIG_SCSI_SAS_LIBSAS is not set
#
# SCSI low-level drivers
#
# CONFIG_ISCSI_TCP is not set
# CONFIG_BLK_DEV_3W_XXXX_RAID is not set
# CONFIG_SCSI_3W_9XXX is not set
# CONFIG_SCSI_ACARD is not set
# CONFIG_SCSI_AACRAID is not set
# CONFIG_SCSI_AIC7XXX is not set
# CONFIG_SCSI_AIC7XXX_OLD is not set
# CONFIG_SCSI_AIC79XX is not set
# CONFIG_SCSI_AIC94XX is not set
# CONFIG_SCSI_DPT_I2O is not set
# CONFIG_SCSI_ADVANSYS is not set
# CONFIG_SCSI_ARCMSR is not set
# CONFIG_MEGARAID_NEWGEN is not set
# CONFIG_MEGARAID_LEGACY is not set
# CONFIG_MEGARAID_SAS is not set
# CONFIG_SCSI_HPTIOP is not set
# CONFIG_SCSI_BUSLOGIC is not set
# CONFIG_SCSI_DMX3191D is not set
# CONFIG_SCSI_EATA is not set
# CONFIG_SCSI_FUTURE_DOMAIN is not set
# CONFIG_SCSI_GDTH is not set
# CONFIG_SCSI_IPS is not set
# CONFIG_SCSI_INITIO is not set
# CONFIG_SCSI_INIA100 is not set
# CONFIG_SCSI_PPA is not set
# CONFIG_SCSI_IMM is not set
# CONFIG_SCSI_STEX is not set
# CONFIG_SCSI_SYM53C8XX_2 is not set
# CONFIG_SCSI_QLOGIC_1280 is not set
# CONFIG_SCSI_QLA_FC is not set
# CONFIG_SCSI_QLA_ISCSI is not set
# CONFIG_SCSI_LPFC is not set
# CONFIG_SCSI_DC395x is not set
# CONFIG_SCSI_DC390T is not set
# CONFIG_SCSI_NSP32 is not set
# CONFIG_SCSI_DEBUG is not set
# CONFIG_SCSI_SRP is not set
#
# Serial ATA (prod) and Parallel ATA (experimental) drivers
#
# CONFIG_ATA is not set
#
# Multi-device support (RAID and LVM)
#
# CONFIG_MD is not set
I enabled the ata_piix driver as I thought it would make a difference but I think not. I think I better disable it.
I'm confused. I don't know if I should update the kernel and try with a newer one, or just give it a try into the new ATA/SATA section and see what happens.
BTW, here is the SMART info:
Code:
tanya godlike # smartctl --all /dev/hda
smartctl version 5.36 [i686-pc-linux-gnu] Copyright (C) 2002-6 Bruce Allen
Home page is http://smartmontools.sourceforge.net/
=== START OF INFORMATION SECTION ===
Model Family: Seagate Barracuda ATA IV family
Device Model: ST380021A
Serial Number: 3HV37EGR
Firmware Version: 3.19
User Capacity: 80,026,361,856 bytes
Device is: In smartctl database [for details use: -P show]
ATA Version is: 5
ATA Standard is: Exact ATA specification draft version not indicated
Local Time is: Mon May 7 11:49:11 2007 ART
SMART support is: Available - device has SMART capability.
SMART support is: Enabled
=== START OF READ SMART DATA SECTION ===
SMART overall-health self-assessment test result: PASSED
General SMART Values:
Offline data collection status: (0x82) Offline data collection activity
was completed without error.
Auto Offline Data Collection: Enabled.
Self-test execution status: ( 0) The previous self-test routine completed
without error or no self-test has ever
been run.
Total time to complete Offline
data collection: ( 422) seconds.
Offline data collection
capabilities: (0x1b) SMART execute Offline immediate.
Auto Offline data collection on/off support.
Suspend Offline collection upon new
command.
Offline surface scan supported.
Self-test supported.
No Conveyance Self-test supported.
No Selective Self-test supported.
SMART capabilities: (0x0003) Saves SMART data before entering
power-saving mode.
Supports SMART auto save timer.
Error logging capability: (0x01) Error logging supported.
No General Purpose Logging support.
Short self-test routine
recommended polling time: ( 1) minutes.
Extended self-test routine
recommended polling time: ( 57) minutes.
SMART Attributes Data Structure revision number: 10
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 069 066 034 Pre-fail Always - 18500579
3 Spin_Up_Time 0x0003 070 070 000 Pre-fail Always - 0
4 Start_Stop_Count 0x0032 100 100 020 Old_age Always - 330
5 Reallocated_Sector_Ct 0x0033 099 099 036 Pre-fail Always - 53
7 Seek_Error_Rate 0x000f 086 060 030 Pre-fail Always - 416070290
9 Power_On_Hours 0x0032 069 069 000 Old_age Always - 27421
10 Spin_Retry_Count 0x0013 100 100 097 Pre-fail Always - 0
12 Power_Cycle_Count 0x0032 099 099 020 Old_age Always - 1247
194 Temperature_Celsius 0x0022 033 056 000 Old_age Always - 33
195 Hardware_ECC_Recovered 0x001a 069 065 000 Old_age Always - 18500579
197 Current_Pending_Sector 0x0012 100 100 000 Old_age Always - 1
198 Offline_Uncorrectable 0x0010 100 100 000 Old_age Offline - 1
199 UDMA_CRC_Error_Count 0x003e 200 182 000 Old_age Always - 120
200 Multi_Zone_Error_Rate 0x0000 100 253 000 Old_age Offline - 0
202 TA_Increase_Count 0x0032 081 234 000 Old_age Always - 19
SMART Error Log Version: 1
ATA Error Count: 1126 (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 1126 occurred at disk power-on lifetime: 27377 hours (1140 days + 17 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
-- -- -- -- -- -- --
84 51 00 3f e5 91 e1 Error: ICRC, ABRT at LBA = 0x0191e53f = 26338623
Commands leading to the command that caused the error were:
CR FR SC SN CL CH DH DC Powered_Up_Time Command/Feature_Name
-- -- -- -- -- -- -- -- ---------------- --------------------
c8 00 4a 3f e5 91 e1 00 00:01:49.804 READ DMA
c8 00 00 bd 6b 0a e0 00 00:01:49.717 READ DMA
c8 00 12 29 74 0a e0 00 00:01:49.706 READ DMA
c8 00 84 39 6b 0a e0 00 00:01:49.698 READ DMA
c8 00 5a ff 5a 0a e0 00 00:01:49.697 READ DMA
Error 1125 occurred at disk power-on lifetime: 27331 hours (1138 days + 19 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
-- -- -- -- -- -- --
84 51 00 07 9a e2 e4 Error: ICRC, ABRT at LBA = 0x04e29a07 = 81959431
Commands leading to the command that caused the error were:
CR FR SC SN CL CH DH DC Powered_Up_Time Command/Feature_Name
-- -- -- -- -- -- -- -- ---------------- --------------------
c8 00 4c 07 9a e2 e4 00 02:12:09.684 READ DMA
c8 00 08 e9 99 e2 e4 00 02:12:09.683 READ DMA
c8 00 10 61 99 e2 e4 00 02:12:09.673 READ DMA
c8 00 06 4b 96 e2 e4 00 02:12:09.668 READ DMA
c8 00 06 c7 8a e2 e4 00 02:12:09.661 READ DMA
Error 1124 occurred at disk power-on lifetime: 27311 hours (1137 days + 23 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
-- -- -- -- -- -- --
84 51 00 fb dc b3 e3 Error: ICRC, ABRT at LBA = 0x03b3dcfb = 62119163
Commands leading to the command that caused the error were:
CR FR SC SN CL CH DH DC Powered_Up_Time Command/Feature_Name
-- -- -- -- -- -- -- -- ---------------- --------------------
c8 00 82 fb dc b3 e3 00 06:40:32.685 READ DMA
c8 00 68 93 dc b3 e3 00 06:40:32.676 READ DMA
c8 00 22 51 24 c2 e3 00 06:40:28.451 READ DMA
c8 00 14 31 24 c2 e3 00 06:40:28.450 READ DMA
c8 00 ca 5d 23 c2 e3 00 06:40:28.448 READ DMA
Error 1123 occurred at disk power-on lifetime: 27310 hours (1137 days + 22 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
-- -- -- -- -- -- --
84 51 00 0b 44 69 e2 Error: ICRC, ABRT at LBA = 0x0269440b = 40453131
Commands leading to the command that caused the error were:
CR FR SC SN CL CH DH DC Powered_Up_Time Command/Feature_Name
-- -- -- -- -- -- -- -- ---------------- --------------------
c8 00 96 0b 44 69 e2 00 05:58:20.863 READ DMA
c8 00 2a d1 43 69 e2 00 05:58:20.863 READ DMA
c8 00 16 a1 43 69 e2 00 05:58:20.862 READ DMA
c8 00 14 85 43 69 e2 00 05:58:20.862 READ DMA
c8 00 14 71 43 69 e2 00 05:58:20.860 READ DMA
Error 1122 occurred at disk power-on lifetime: 27310 hours (1137 days + 22 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
-- -- -- -- -- -- --
84 51 00 3b 36 f7 e3 Error: ICRC, ABRT at LBA = 0x03f7363b = 66532923
Commands leading to the command that caused the error were:
CR FR SC SN CL CH DH DC Powered_Up_Time Command/Feature_Name
-- -- -- -- -- -- -- -- ---------------- --------------------
c8 00 e6 3b 36 f7 e3 00 05:57:43.349 READ DMA
c8 00 da 61 35 f7 e3 00 05:57:43.347 READ DMA
c8 00 04 2d 33 f7 e3 00 05:57:43.344 READ DMA
c8 00 02 2f 32 f7 e3 00 05:57:43.334 READ DMA
c8 00 04 21 37 f7 e3 00 05:57:43.330 READ DMA
SMART Self-test log structure revision number 1
No self-tests have been logged. [To run self-tests, use: smartctl -t]
Device does not support Selective Self Tests/Logging
Not sure what the very last line of that output means, but try running:
smartctl --test=long /dev/hda
Then wait an hour or so, and re-check the drive with the smartctl --all /dev/hda command again to see the results of the self test. Looks like no self tests were ever done on it.
There are a bunch of errors listed there, but can't necessarily say yet if it's any hardware problem, or simply a communication/software/driver related problem.
EDIT: Updating the kernel will likely not solve the problem. The configurations of yours and the next newer one are very similar, so if you can fix the problem first, you will know what it was and what config options are needed, regardless which kernel you use. (This assumes it IS a configuration issue)
The Piix driver is specific to my machine (or any intel machine with that chip device) so it may or may not apply to your machine.
Last edited by GrapefruiTgirl; 05-07-2007 at 10:01 AM.
Thanks GrapefruiTgirl. I gotta go now but I will run those commands as soon as I get back and post the results. I will also mess around with my kernel a bit more ;p and see what comes of it.
I hate to be right, but it does seems that it is a power supply issue. I suggest a Seasonic S12-430 or any Eneramax model. After you upgrade your power supply, problems should start going away.
The piix module is for enabling DMA. It should be compiled as built-in. The ata_piix module is for Intel SATA controllers.
Sorry, but I don't see how a crappy power supply can boost CPU usage when using the disk =/ if you could explain it to me, I'd apprieciate it, as I don't see the logic behind that.
I started running the test. In about an hour I'll have the results .
Well, completed the test, now smartctl --all throws these additional lines:
Code:
SMART Self-test log structure revision number 1
Num Test_Description Status Remaining LifeTime(hours) LBA_of_first_error
# 1 Extended offline Completed without error 00% 27427 -
Device does not support Selective Self Tests/Logging
I tested the ATA/ATAPI drivers removing completely support for the new experimental SATA/ATA drivers, and removing support for generic ide. Results were the same.
Next I tested the experimental SATA/ATA drivers, removing completely support for ATA/ATAPI. At least now the drive is recognized as udma2.
I was told the VT82C686 chipset for AMD (I have a P3 though) had serious DMA issues which were patched in the Windows version. Guess I'm gonna do a bit of research into this.
Sorry, but I don't see how a crappy power supply can boost CPU usage when using the disk =/ if you could explain it to me, I'd apprieciate it, as I don't see the logic behind that.
I started running the test. In about an hour I'll have the results .
A better or a new power supply will not boost CPU usage. Really I do not know why you think that. A crappy power supply can make devices malfunction or work off-on-off. In my previous post, Seagate drives are pickier on the quality of the power supply. I had a faulty power supply for USB external enclosure. My Hitachi drives worked, but the Seagate drives did not work. I have also seen this while working at my college. The old power supplies can not provide the same amount of power that they once did. The hard drive light lits and the drive will not work thereby will not boot. Your drive is showing similar signs. One of these days, Linux will not boot up. Power supplies should be replaced every two to four years.
Get a new power supply and pick the brands that I suggested.
You can try setting ATA-2 as a module. If you need it, load the module. If you do not and it works better, then thats the problem.
If you have mixed VT82C686 and Creative Labs cards together before or now, there will be DMA problems. You will not have any problems using other sound cards.
I suggest upgrading the BIOS. It will fix most problems. IMHO, Soyo makes poor motherboards.
What I meant is how a "crappy" (it's a Topower 320, as good as it can get here :P) power supply can boost CPU usage. The disk has never shown any problems, not even now. I don't have any boot problems or hard disk stall issues. The only problem revolves around CPU usage.
I have been reading this and I think the source of the problem is in the VIA chipset.
I never put any Creative Labs card. In fact, sound is disabled on the server . I guess I could try a BIOS upgrade, but the release notes for the latest Soyo BIOS for that motherboard don't give me much confidence. Anybody knows where I can get 3rd party BIOS for the 7VBA?
Yes, I know, Soyo is not a good manufacturer, but it's what I currently have :P.
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.
thanks for the info re: seagates and power supplies. Useful for me, I just got a brand new one again.
.
. I guess I could try a BIOS upgrade, but the release notes for the latest Soyo BIOS for that motherboard don't give me much confidence. Anybody knows where I can get 3rd party BIOS for the 7VBA?
