I have sent about 3 emails, tried contacting you on ICQ... are you around? My drive is about to fail, please I need someone to replace it asap. I emailed you about a week ago and you told me it was going to be replaced on Wednesday, but it is now Sunday (about 1 week later).. I don't mind the wait on other issues, but this issue is fairly important... :(

Guys, I thought you offered a good service... Anyone know any other way to get in contact with them?

They are sleeping.... shh...... you'll wake them up.....

Have you tried calling them?

What email address did you use?

Your drive is not about to fail.. I have responded to your icq's and you know that.

Hate to sound BS but this is your LAST reply to me...

Jay> when the drive gets here. we will schedule it


Why offer to replace it when nothing is supposely WRONG with it?

Your drive is not about to fail.. I have responded to your icq's and you know that.


Furthermore this is your initial ICQ message after I sent you this..

universal2001>
i did a scan on my logfile just today and i see:
Sep 1 06:26:14 ... kernel: hda: status timeout: status=0xd0 { Busy }
Sep 1 09:14:50 ... kernel: hda: status timeout: status=0xd0 { Busy }
Sep 1 06:26:15 ... kernel: hda: no DRQ after issuing WRITE
Sep 1 09:14:50 ... kernel: hda: no DRQ after issuing WRITE
Sep 1 06:26:15 ... kernel: ide0: reset: success
Sep 1 09:14:50 ... kernel: ide0: reset: success



Jay> yeah that sounds about right. ready for failure

I am not saying nothing is wrong. What I am saying is it is not critical as it is not going to fail today/tomorrow. One of our backup drives has been doing that for 6 months and it hasn't died yet.

Jay,

That drive could still fail any moment. I had the same thing happen to a machine at my house, a computer tech swore it would be fine. Two days later, my drive was grinding, and smoking.

We have a replacment on the way.

Thank you. Case close.

Seems like the drive died a week later: http://www.webhostingtalk.com/showthread.php?s=&threadid=74336

universal2001,
Just curious, what were the symptoms that lead you to believe that a hard drive failure was imminent?

Originally posted by Kiwi
Seems like the drive died a week later: http://www.webhostingtalk.com/showthread.php?s=&threadid=74336

I don't know why you fished that topic.

Others will do the same to you when you hit a bad time and no one is protected from it.

See the other thread. Its because we experienced the same thing with pwebtech twice - 12 hours for a reboot. And the thread is only a week old, not 3 or 4 months.

Originally posted by jayglate
I am not saying nothing is wrong. What I am saying is it is not critical as it is not going to fail today/tomorrow. One of our backup drives has been doing that for 6 months and it hasn't died yet.

Yeah might not have been that day or the next, just the next week :D

I know its not funny to the person that this happend too, but I'm sorry I can't help but laugh...

Originally posted by Kiwi
See the other thread. Its because we experienced the same thing with pwebtech twice - 12 hours for a reboot. And the thread is only a week old, not 3 or 4 months.

still old and I am sure you would not like it if a competitor does the same things to you.

I have never phoned pwebtech or their nac for a reboot and was not done within 2 minutes.

I did have bad time with pwebtech but can you tell me which provider does not have it so we can all join them at a reasonable monthly fee.

Originally posted by Dedicated
still old and I am sure you would not like it if a competitor does the same things to you.

pwebtech is not a competitor of ours, but a provider - even though we only have 1 almost empty server with them. i think i do have the right to express opinions or concerns.

By the way, the server we have with them is experiencing similar errors:


hda: drive_cmd: status=0x51 { DriveReady SeekComplete Error }
hda: drive_cmd: error=0x04 { DriveStatusError }
hda: drive_cmd: status=0x51 { DriveReady SeekComplete Error }
hda: drive_cmd: error=0x04 { DriveStatusError }
hda: drive_cmd: status=0x51 { DriveReady SeekComplete Error }
hda: drive_cmd: error=0x04 { DriveStatusError }
hda: drive_cmd: status=0x51 { DriveReady SeekComplete Error }
hda: drive_cmd: error=0x04 { DriveStatusError }


I'm still not allowed to voice my opinions, even though our drive seems to be dying as well? Luckily we have off-network backups of the entire machine and the few remaining dozen customers will be off the server within the next days.

:rolleyes:

I'm still not allowed to voice my opinions, even though our drive seems to be dying as well? Luckily we have off-network backups of the entire machine and the few remaining dozen customers will be off the server within the next days.

Don't see any problems with your posts marc.. just your hard drive.. hope it holds out until you get those accounts off of it ...

Originally posted by GeorgeC
universal2001,
Just curious, what were the symptoms that lead you to believe that a hard drive failure was imminent?

GeorgeC,

I never saw anyone respond to your question so I will. If you look at the top of this thread, you'll see some messages that indicate a hard drive problem:


Sep 1 06:26:14 ... kernel: hda: status timeout: status=0xd0 { Busy }
Sep 1 09:14:50 ... kernel: hda: status timeout: status=0xd0 { Busy }
Sep 1 06:26:15 ... kernel: hda: no DRQ after issuing WRITE
Sep 1 09:14:50 ... kernel: hda: no DRQ after issuing WRITE
Sep 1 06:26:15 ... kernel: ide0: reset: success
Sep 1 09:14:50 ... kernel: ide0: reset: success


Those messages come out of your /var/log/messages (at least on Linux boxes). Since you have a log scanning program running (you do scan your logs, right ;) ) you'll see them long before they cause problems (hopefully).

Frank

so did the server's hd ever get replaced?

http://www.webhostingtalk.com/showthread.php?s=&threadid=74472

Would like to know as well on the HD replacement, the suspense (and mystery) is killing me! :D

- John C.

As an existing pwebtech customer, I am curious to know what the resolution to this was too. I just ordered another server from them/mehost.

What happened to the other thread on this topic?

Click the link two posts above yours.

Samuel,

Thanks

Tried to send universal a PM on why he wanted it deleted, but I guess a lot of people have sent him a PM on the subject as his box is too full.

Originally posted by Kiwi
I'm still not allowed to voice my opinions, even though our drive seems to be dying as well? Luckily we have off-network backups of the entire machine and the few remaining dozen customers will be off the server within the next days.


People who live in glass houses shouldn't throw stones, you don't like your clients complaining about you anywhere in public, going as far as banning one forum where people do complain about your services, yet you have no qualms about coming here to complain about your provider? Grow up Marc, I don't know what's worse, doing here what you complain about your own clients doing, or watching a competitors forums when said competitor was locked out of your forums because he was a competitor (and at the time still a client as well).

If you see the following errors:

hda: drive_cmd: status=0x51 { DriveReady SeekComplete Error }
hda: drive_cmd: error=0x04 { DriveStatusError }
hda: drive_cmd: status=0x51 { DriveReady SeekComplete Error }
hda: drive_cmd: error=0x04 { DriveStatusError }
hda: drive_cmd: status=0x51 { DriveReady SeekComplete Error }
hda: drive_cmd: error=0x04 { DriveStatusError }
hda: drive_cmd: status=0x51 { DriveReady SeekComplete Error }
hda: drive_cmd: error=0x04 { DriveStatusError }

Upgrade your kernel to 2.4.19 as you may have older drivers attempting to use more recent (unsupported) hardware, resulting in the above errors/warnings in dmesg.

You may also want to change lilo.conf to show linear rather than lba32.

" no DRQ after issuing WRITE
ide0 reset: success"

It seems that the pbm isn't a faulty hard disk drive but a pbm with the linux driver who waits for only 50ms.

it is not a faulty HDD. Here is an explication and a cure to stop this message.

Because That Message appears hundreds
of times per day; you're soon reduced to a
quivering wreck of frustration, desperately
reading HOW-TOS and manpages and DejaNews and
zillions of mail archives. But all you can
find is thousands of pleas from other poor
sods with the same problem, and hundreds of
replies saying "the hard disk is faulty".

But more often than not, your IDE hard disk
is either brand new, or it was running that
other popular operating system for months
or years before you rescued it.


SO WHY IS IT HAPPENING?
The kernel hackers reading this know the
answer already (and can probably recite
the relevant source code from memory ;-)

But in simple terms, this message is Linux's
way of telling you that it tried to WRITE to
a batch of disk sectors at once; but the drive
controller didn't respond with the IDE
"standard reply" to this multi-sector write.

Some newer drives such as many Seagate
models extend their capabilities by
providing extra info in their response to a
WRITE. Or they may be waiting for another
batch of data before actually doing the WRITE
and issuing the response.

An antique drive may also have trouble because
its controller doesn't respond in a "standard
IDE" way. This one probably won't affect you
unless you're a Linux minimalist trying to
run everything from a 20MB Conner... ;-)

Anyway, whenever Linux accesses these drives,
it detects what it thinks is a hardware glitch,
tries to reset the drive controller, and issues
That Message.

Your drive ISN'T broken, but it's speaking
in an accent. Linux needs a bit of help to
understand what the drive controller is saying.


A CURE
You need to use "hdparm" to interrogate the
disk controller, and then to tell Linux how to
access the drive in future. To save you from
reading the manpage (recommended, hdparm has
a ton of features...) here's the procedure that
gets rid of That Message in most cases:

(1) log in as root

(2) hdparm -i /dev/hda

This interrogates your first IDE hard disk,
and displays a pile of info about your disk
and its controller. The interesting bit is
the value of "MaxMultSect", which describes
your disk's multi-sector read/write capability.
You can do hdparm -i /dev/hdb to find out about
your second IDE hard disk, and so on.
As an example, my server's second drive
(a 2GB Seagate) returns a value of 32 for
MaxMultSect.

(3) hdparm -mX /dev/hda

where X is the MaxMultSect value reported
in step (2). This tells Linux about your
disk's multi-sector read/write capability.
Using my second drive as an example again:
hdparm -m32 /dev/hdb

If this stops That Message from appearing, then

(4) Add the hdparm -mX... command to your startup
script (typically /etc/rc.local) so that this
cure is automatically applied if you reboot.

However, if That Message continues to appear,
you may need to specify other hdparm settings.
Or you may really have a faulty hard drive or
controller.

But for most sufferers, the above procedure
should alleviate much wailing and gnashing
of teeth. It's helped me on many occasions.


Also When you look at the man hdparm there
is for the -m option (multplie mode) this text :

"Western Digital recommends lower settings
of 4 to 8 on many of their drives, due tiny (32kB) drive buffers and non-optimized buffering algorithms."

A RH link may help too :
bugzilla dot redhat dot com /bugzilla/ show_bug.cgi?id=5562


Good luck

-------------------------------------
Pascal
President/CEO
carat-hosting dot com
-------------------------------------

wow.. talk about digging up an old thread!

this particular one is over 2 years old.

Why bring alive a 2 year old thread? :confused:

Probably he wants to show the feature of hdparm ;)

I think this thread is past it's use by date.