Void's Forums

by **X11** » Thu Feb 13, 2003 4:11 am

hdparm -l just gives me the usage for hdparm, can you tell me what things i should change? im kinda worried i might fsck my disk up.

by **Void Main** » Thu Feb 13, 2003 4:23 am

Not "-l", but "-I" (upper case 'i' (eye)).

by **X11** » Thu Feb 13, 2003 4:44 am

[root@exeleven root]# hdparm -I /dev/hda
-bash: /sbin/hdparm: Input/output error

hmmmmmmmmmm

by **Void Main** » Thu Feb 13, 2003 4:54 am

How about lower case i?

# hdparm -i /dev/hda

by **X11** » Thu Feb 13, 2003 5:07 am

im on my brothers computer now, my computer crashed (at 14 days uptime). I was about to post a message when my system crashed (video glitched and froze). Then after i reboot it, it wont detect my hard disk.

I unplug it and plug it back in, actually its probably the power. I got it to see the partiton table from my slackware cd. Now it wont boot it tells me some interupt bull hockey. Nevermind i should get it working.

by **Void Main** » Thu Feb 13, 2003 5:10 am

What are you running on that machine that the hdparm doesn't have a "-I" option?

And I don't know what you guys do to crash your systems. Typically my systems stay up from the time I install them. The only things that will bring them down is a power outage, or if I install a new kernel which I rarely do except right after initial installation.

For instance I built a PDC on a P-100 with RH 8.0 61 days ago and that's how much uptime it has. This web site has been up since the day I installed it sometime in November (I hacked the uptime on it so I don't remember exactly when in November I stopped hacking the kernel). My main desktop only has 6 days of uptime right now, don't remember why I rebooted it. I believe I was doing some kernel hacking or doing some boot loader testing.. I have another web server that as you know got up to around 490 days of uptime before a *major* extended power outage where the UPS couldn't keep it up, it's been up another 245 days since the power came back on... What a bunch of whimps. :)

by **X11** » Thu Feb 13, 2003 10:59 pm

Its got somthing to do with the fact that we like to fsck around with old hardware and stuff.

by **Void Main** » Thu Feb 13, 2003 11:25 pm

My old P-100s just keep chugging along. I finally upgraded my gateway to RH 8 on the machine that fried the power supply a couple of months back. I saw remnants of Red Hat 5.2 on it so I believe it's upgrade cycle went 5.2->6.0->6.1->6.2->8.0. I believe that also is likely to be the number of times it has been rebooted (except for the fried power supply where I started a small fire with it by soldering a piece of wire in place of the burned out fuse).

by **X11** » Fri Feb 14, 2003 6:07 am

you crazy barsted, i go on holidays a bit and my dad wont let em leave my computers on when i go because of the fact that he does not like the idea of going to a pile of ash for a house.

Anyways i have been wanting to move to slack, and now i have, and that 14 days uptime has been how long my install of Red-Hat 8.0 lasted. Until my Hard Disk fscked up again (i had to reinstall then because of that). I think i have fixed it, except now my hdd is stuck as slave. No matter where the jumper is, when i have cash i might get a 40 or 80 gig hdd.

by **X11** » Sat Feb 15, 2003 8:54 am

okay now what should i do with this info:

Code: Select all: root@exeleven:~# hdparm -I /dev/hdb /dev/hdb: ATA device, with non-removable media Model Number: QUANTUM FIREBALLP AS20.5 Serial Number: 192115576763 Firmware Revision: A1Y.1500 Standards: Used: ATA/ATAPI-5 T13 1321D revision 1 Supported: 5 4 3 2 & some of 6 Configuration: Logical max current cylinders 16383 17475 heads 16 15 sectors/track 63 63 -- CHS current addressable sectors: 16513875 LBA user addressable sectors: 40132503 device size with M = 1024*1024: 19595 MBytes device size with M = 1000*1000: 20547 MBytes (20 GB) Capabilities: LBA, IORDY(can be disabled) bytes avail on r/w long: 4 Queue depth: 1 Standby timer values: spec'd by Vendor, no device specific minimum R/W multiple sector transfer: Max = 16 Current = 0 Recommended acoustic management value: 254, current value: 254 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: * 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 * Automatic Acoustic Management feature set SET MAX security extension * DOWNLOAD MICROCODE cmd Security: Master password revision code = 65534 supported not enabled not locked not frozen not expired: security count not supported: enhanced erase 12min for SECURITY ERASE UNIT. HW reset results: CBLID- above Vih Device num = 1 determined by CSEL Checksum: correct

by **X11** » Sat Feb 15, 2003 8:57 am

Wait Slackware (Had to put slackware in bold because its 1337 (Had to put l33t in bold as an excuse to include more crap)). Seems to have pretty good preformance anyway:

Code: Select all: root@exeleven:~# hdparm -Tt /dev/hdb /dev/hdb: Timing buffer-cache reads: 128 MB in 1.18 seconds =108.47 MB/sec Timing buffered disk reads: 64 MB in 1.91 seconds = 33.51 MB/sec

Im sure i could go faster (note, the hard disk is broken, and is now stuck in slave).

Void's Forums

Fast

Who is online