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.
I just got a maxtor 20GB HD. For some reason it's writing at normal speed(at least as far as I can tell) but read times are incredibly sloowww. I ran hdparm testing out -d0 -d1 -c0 -c1 and -c2 then tested w/ -t after each one. best was right after I ran -c1 I think but that was really slow... 64 MB in ~32 seconds... or about 1.8MB/s Not good... Any ideas? It was running fine under WinXP but I just couldn't stand the pain of running Windows anymore....
It's on an 80 conductor cable... but I've noticed no difference in the speed from when I had it on an older cable. Also It's set as master w/ a 3gb slave... the slave is really old but it is reading faster than the maxtor... the 3gb writes at like 1/3 the speed of the maxtor though. Oh, and the slave is a seagate if that makes any diff... and I just barely hooked the slave up like today and have noticed no difference in the speed of either drive
I was having a Maxtor drive and when it started slowering down, it died 1 weeks later, watch out!
Maxtor disk should be really fast, are you using the correct chipset in your kernel? Take a look at your cable too.
not really, this is all about the kernel, but maybe the big-slow-not-optimized redhat kernel does not choose the correct chipset. use "dmesg" to see the boot msg and try to locate a line like this one :
ALI15X3: IDE controller at PCI slot 00:04.0
ALI15X3: chipset revision 196
ALI15X3: not 100% native mode: will probe irqs later
ide0: BM-DMA at 0xd400-0xd407, BIOS settings: hdaMA, hdbMA
ide1: BM-DMA at 0xd408-0xd40f, BIOS settings: hdcMA, hddio
of course this msg is about MY chipset, try to find your and make sure it is really the one you should use... is your drive new btw? maybe it's gonna die, as I said.
Alright... Latest Update on my HD:
I didn't really need to use my computer last night so I made a couple of scripts and ran them:
script 1) ran hdparm -aXX /dev/hda using every other value starting at 64 working down to 0 and using hdparm -t /dev/hda 4 times after every hdparm -aXX /dev/hda
script 2) took the 3 XX values that had the best times and tested those ones each 8 times again.
script 3) hdparm -V
hdparm /dev/hda
hdparm -i /dev/hda
hdparm -I /dev/hda
hdparm -t /dev/hda (ran this line 8X)
script 1 was took an excuceating amount of time to execute because each hdparm -t command was averaging about 500kb to 1MB a second but I managed to grab 18, 40, and 42 as the best values to plug in for -a.
I have no idea how long script 2 took because I went to bed and just checked it this morning but I noticed that 18 had the best average of the three with only the first three test below 2MB/s while 40 had the best single time up at 3.5 MB/s
finally I just barely ran script 3 and it dropped below 3 MB/s ONCE! yeah... that's still crap but it's about 2x what I was getting before...
Oh, and if it makes any diff this was all done from runlevel 5 in a failsafe root session except #3 which I ran from a terminal in a root session of KDE (I needed to see the output of the whole script otherwise I would have run it outside of X... yeah I'm sure there's a real easy way to do that but I don't know it) anyhow here's the output of script 3:
ATA device, with non-removable media
Model Number: Maxtor 52049U4
Serial Number: K402TSZC
Firmware Revision: DA620CQ0
Standards:
Used: ATA/ATAPI-4 T13 1153D revision 17
Supported: 5 4 3 2 & some of 5
Configuration:
Logical max current
cylinders 16383 16383
heads 16 16
sectors/track 63 63
--
CHS current addressable sectors: 16514064
LBA user addressable sectors: 40020624
device size with M = 1024*1024: 19541 MBytes
device size with M = 1000*1000: 20490 MBytes (20 GB)
Capabilities:
LBA, IORDY(can be disabled)
bytes avail on r/w long: 57 Queue depth: 1
Standby timer values: spec'd by Standard, no device specific minimum
R/W multiple sector transfer: Max = 16 Current = 16
Advanced power management level: unknown setting (0x0000)
DMA: mdma0 mdma1 mdma2 udma0 udma1 udma2 udma3 *udma4
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:
* NOP cmd
* READ BUFFER cmd
* WRITE BUFFER cmd
* Host Protected Area feature set
* Look-ahead
* Write cache
* Power Management feature set
* SMART feature set
Advanced Power Management feature set
* DOWNLOAD MICROCODE cmd
HW reset results:
CBLID- above Vih
Device num = 0 determined by the jumper
Checksum: correct
/dev/hda:
Timing buffered disk reads: 64 MB in 18.84 seconds = 3.40 MB/sec
/dev/hda:
Timing buffered disk reads: 64 MB in 20.59 seconds = 3.11 MB/sec
/dev/hda:
Timing buffered disk reads: 64 MB in 16.74 seconds = 3.82 MB/sec
/dev/hda:
Timing buffered disk reads: 64 MB in 16.90 seconds = 3.79 MB/sec
/dev/hda:
Timing buffered disk reads: 64 MB in 21.49 seconds = 2.98 MB/sec
/dev/hda:
Timing buffered disk reads: 64 MB in 19.11 seconds = 3.35 MB/sec
/dev/hda:
Timing buffered disk reads: 64 MB in 18.19 seconds = 3.52 MB/sec
/dev/hda:
Timing buffered disk reads: 64 MB in 17.91 seconds = 3.57 MB/sec
And to Half_Elf, is this what you're looking for?
Quote:
Uniform Multi-Platform E-IDE driver Revision: 7.00beta-2.4
ide: Assuming 33MHz system bus speed for PIO modes; override with idebus=xx
VP_IDE: IDE controller at PCI slot 00:07.1
VP_IDE: chipset revision 6
VP_IDE: not 100% native mode: will probe irqs later
ide: Assuming 33MHz system bus speed for PIO modes; override with idebus=xx
VP_IDE: VIA vt82c686b (rev 40) IDE UDMA100 controller on pci00:07.1
ide0: BM-DMA at 0xd000-0xd007, BIOS settings: hda:DMA, hdb:DMA
ide1: BM-DMA at 0xd008-0xd00f, BIOS settings: hdc:DMA, hdd:pio
hda: Maxtor 52049U4, ATA DISK drive
hdb: ST33210A, ATA DISK drive
Alright... so how do I fix that little not in 100% native mode line?
VP_IDE: IDE controller at PCI slot 00:07.1
VP_IDE: chipset revision 6
VP_IDE: not 100% native mode: will probe irqs later
Well I suppose Multi-IO are less effective than real onboard chipset, but I remember you told us that your slave drive was faster... I think the only good thing you can do is to try your HD on another computer to see if there's some speed problem too. Maybe your multi-io card is too stupid to use the correct setting with your disk... or maybe the disk gonna die, I can't think about something else... very weird error
I/O is onboard... actually I've only got 3 cards in my box... vid card, NIC, and an old ISA 33.6k modem... onboard... it's on a VIA chipset umm... EPoX 8KTA3+ is the MoBo I think...
I know your pain. Our company has hundreds of IBM 300 PL desktops that came with the Maxtor 52049U4 20 GB Drives. Guess what. The drive stinks. It's not your computer system at all. Fortunatley our systems are under warranty, and IBM has had to replace probably over 100 of these drives. What I have been told from their reps is the controller board on the drive goes coo-koo and makes the drive retarded and slow. It works perfectly with the exception of the speed. Try to warranty your drive through Maxtor. I promise, your drive is bad. Run Maxtor Power Diags. If it takes longer than 2 hours to test your drive, you have your ammo for the Warranty Claim. Let them know it takes three days to run the Diags. That is about how long it has taken on some of our drives that we actually allowed the test to complete on. (We have some spare time). I relly hope this helps you out. I registered for this board to specifically reply to your post. I was searching google for a FW Flash for this drive and your post was the first hit. Later.
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.