Linux - GeneralThis Linux forum is for general Linux questions and discussion.
If it is Linux Related and doesn't seem to fit in any other forum then this is the place.
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.
Ok, here's an addition to this thread and a question all rolled into one.
I have a fileserver in my home network, running RH9, that has two identical WD 200G HDs.
/dev/hda reports as this:
Timing buffered disk reads: 64 MB in 1.85 seconds = 34.59 MB/sec
/dev/hdb, however, reports as this:
Timing buffered disk reads: read() failed: Input/output error
I've tried this with hdb mounted, and with -c and -d turned on and off. I cannot unmount hdb; it claims that /dev/hdb is busy. I've still got a few more tricks to try, but I didn't see any mention of a problem like this in this forum; if anyone has seen this before, let me know.
You should start your own thread for this issue. First, this thread is for
reporting hard drive performance, and not dealing with problems.
Second, your thread belongs in the Hardware Forum, and as such will
get more exposure because it's there, and it's new. And you should
also list your distribution, kernel version, etc. You can look at either Eric Raymond's or XavierP's articles to get more information about
making a proper post.
I'm using a Seagate Barracuda ATA/133 HDD hooked up to an Ultra DMA IDE controller integrated into the mobo's VIA 8237 southbridge under Fedora Core 5:
Code:
[root@blackhole hda]# hdparm -Tt /dev/hda
/dev/hda:
Timing cached reads: 2396 MB in 2.00 seconds = 1198.02 MB/sec
Timing buffered disk reads: 152 MB in 3.02 seconds = 50.28 MB/sec
[root@blackhole hda]# cat /proc/ide/drivers
ide-disk version 1.18
ide-cdrom version 4.61
ide-floppy version 0.99.newide
[root@blackhole hda]# cat /proc/ide/hda/model
ST3160023A
[root@blackhole hda]#
I know it means there is physical damage to the HDD itself, probabily bad sectors, but is there any bash scripts I could run to really give the HDD a test (like never-ending kernel compiling to test cpu reliability)?
A guy called here because "he couldn't get on the internet." When I asked him to launch a web browser, he said, "You're gonna have to help me out with that one, buddy." Actually, he was quite well connected to the internet, but his Windoze system had 7 trojans, and a virus had infected every .exe file on his system. So Internut Exploder couldn't work properly (can it ever?). Further, his hard drive was well on the way to dying...
So I installed a new hard drive in his computer, and since he didn't know what he was doing with Windoze anyway, he now has a dual boot with Slackware and Windoze, only commented Windoze out of LiLO to see if he could use Slackware.
His comment: "I like that system of yours. Man, it really zings right along!"
Code:
root@matthews:/home/dave# hdparm /dev/hda
/dev/hda:
multcount = 0 (off)
IO_support = 0 (default 16-bit)
unmaskirq = 0 (off)
using_dma = 1 (on)
keepsettings = 0 (off)
readonly = 0 (off)
readahead = 256 (on)
geometry = 16383/255/63, sectors = 156301488, start = 0
root@matthews:/home/dave# hdparm -iI /dev/hda
/dev/hda:
Model=ST3802110A, FwRev=3.AAE, SerialNo=4LR0KSXG
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=off
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: device does not report version:
* signifies the current active mode
ATA device, with non-removable media
Model Number: ST3802110A
Serial Number: <munged>
Firmware Revision: 3.AAE
Standards:
Supported: 7 6 5 4
Likely used: 7
Configuration:
Logical max current
cylinders 16383 64761
heads 16 1
sectors/track 63 255
--
CHS current addressable sectors: 16514055
LBA user addressable sectors: 156301488
LBA48 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)
Queue depth: 1
Standby timer values: spec'd by Standard, no device specific minimum
R/W multiple sector transfer: Max = 16 Current = ?
Recommended acoustic management value: 208, 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=240ns IORDY flow control=120ns
Commands/features:
Enabled Supported:
* READ BUFFER cmd
* WRITE BUFFER cmd
* Host Protected Area feature set
* Look-ahead
* Write cache
* Power Management feature set
Security Mode feature set
* SMART feature set
* FLUSH CACHE EXT command
* Mandatory FLUSH CACHE command
* Device Configuration Overlay feature set
* 48-bit Address feature set
SET MAX security extension
* DOWNLOAD MICROCODE cmd
* General Purpose Logging feature set
* SMART self-test
* SMART error logging
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 = 0 determined by the jumper
Checksum: correct
root@matthews:/home/dave# hdparm -tT /dev/hda
/dev/hda:
Timing cached reads: 3092 MB in 2.00 seconds = 1547.87 MB/sec
Timing buffered disk reads: 216 MB in 3.02 seconds = 71.45 MB/sec
root@matthews:/home/dave# hdparm -tT /dev/hda
/dev/hda:
Timing cached reads: 3040 MB in 2.00 seconds = 1520.99 MB/sec
Timing buffered disk reads: 216 MB in 3.02 seconds = 71.47 MB/sec
That drive is a Seagate ST3802110A, 80GB, Ultra ATA/100, 7200RPM, 2MB cache.
Though I prefer AMD processors, the fact is that Linux kernel support for this Intel IDE bus is better than for my VIA K8T800 IDE or VIA VT6420 SATA RAID Controller on my Asus K8V-X board in my workstation.
I know it means there is physical damage to the HDD itself, probabily bad sectors, but is there any bash scripts I could run to really give the HDD a test (like never-ending kernel compiling to test cpu reliability)?
Which filesystem are you using on hda1? Issue and read "man fsck" for details.
If you need further help, you'd be better off starting a new thread in the Hardware forum.
The drive I posted above getting 71.45 MB/sec is a Seagate 7200 RPM 2MB cache drive on an Intel ICH5 controller. You must have something seriously wrong in your kernel. I'm on the road away from that box right now, but if you'll start your own thread, you should get some help. Send me a notice of your thread and I'll check it out.
I expect at LEAST 40MB/s.
But I think I found my problem, it seems there is an Intel PIIX Sata support burried under SCSI / Low level drivers that I did not notice. I just avoided the scsi drivers as there were not any. Rebuilding now, will post if this makes a difference, if I can enable DMA I believe it will make a big difference. It is fairly moot point as I am switching the drives for Raptors anyway. But I am using this setup for testing for a few days and it is more curiosity.
:EDIT:
Well it appears enabling that option Intel PIIX Sata under SCSI:Low Level Drivers did not solve the problem. Where can I find out what is required to enable full support for ICH5. PS: Thanks for the welcome aboard. Linux is not my strong point since I ussually use BSD.
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.