Pratul Kalia wrote:
Ah yes, in my case, smartctl did show failed when I ran the test.
That's the reason I got the HDD replaced.
Some manufacturers ( and in some case Vendors for all manufacturers )
insist you run their own diagnostic tools and give them the report from
their own tool before
Karanbir Singh [EMAIL PROTECTED] wrote:
A bit more info on the hardware you have, the setup you run, smartctl
status etc would go a long way in even starting to look at this issue.
It is a ST3500320AS with Firmware revision SD15
I have tested it well enough. But still I am not sure.
1. Those
Mani A wrote:
(I believe this is due to the drive warming up and self-test being
enabled). Will check it after it cools down :)
Smartctl reports drive temp if its working properly, also running the
drive of the seagate specific max for that model would invalidate your
warranty, and if you
you may be knowing this on Seagate SATA drives (Barracuda):
ata2: exception Emask 0x10 SAct 0x0 SErr 0x90202 action 0xe frozen
[ 116.038145] ata2: irq_stat 0x0040, PHY RDY changed
[ 116.038190] ata2: SError: { RecovComm Persist PHYRdyChg 10B8B }
[ 116.038242] ata2: hard resetting link
[
you may be knowing this on Seagate SATA drives (Barracuda):
ata2: exception Emask 0x10 SAct 0x0 SErr 0x90202 action 0xe frozen
[ 116.038145] ata2: irq_stat 0x0040, PHY RDY changed
[ 116.038190] ata2: SError: { RecovComm Persist PHYRdyChg 10B8B }
[ 116.038242] ata2: hard resetting link
Mani A wrote:
Is the latest kernel OK on this?
Or is it a firmware problem? ... esp as it is apparently a
cross-platform problem?
A bit more info on the hardware you have, the setup you run, smartctl
status etc would go a long way in even starting to look at this issue.
- KB
On Sun, Nov 30, 2008 at 5:28 AM, Karanbir Singh [EMAIL PROTECTED] wrote:
Is the latest kernel OK on this?
Or is it a firmware problem? ... esp as it is apparently a
cross-platform problem?
A bit more info on the hardware you have, the setup you run, smartctl status
etc would go a long way
