ATTENTION: You are viewing a page formatted for mobile devices; to view the full web page, click HERE.

Main Area and Open Discussion > Living Room

Decided on RAID 1 - SSDs or HDDs?

<< < (2/4) > >>

Renegade:
Well, that does make sense. I'll still need to go out and buy a new internal drive, but they're cheap. So I'll earmark the savings to get a little something for my wife. :)  :-*

Sigh... I so utterly loathe doing system setups... It's an utter waste of time. Sigh...

I suppose I should quick get over to a liquor store before it closes... I'm gonna need it...

Stoic Joker:
Just wanted to point out that while the error does look ominous...It's not necessarily damning. Get a copy of the manufacturer's diagnostic boot CD, and see what it says first.

I have seen disk errors flood logs simply because of a driver hiccup. The first time it happened I too had a similar reaction. However. The box in question (My SuperMicro server), has continued to run just fine on the very same drives for several years (about 4) after the initial incident.

Best I can tell the Virtual Servers occasionally get into a pissing contest with the host machine, which causes the logs to get flooded with disk events until the next reboot. Damn strange, but I still do an offline diag on the drives now and then just to be sure all is O-Tay.

Renegade:
Just wanted to point out that while the error does look ominous...It's not necessarily damning. Get a copy of the manufacturer's diagnostic boot CD, and see what it says first.

I have seen disk errors flood logs simply because of a driver hiccup. The first time it happened I too had a similar reaction. However. The box in question (My SuperMicro server), has continued to run just fine on the very same drives for several years (about 4) after the initial incident.

Best I can tell the Virtual Servers occasionally get into a pissing contest with the host machine, which causes the logs to get flooded with disk events until the next reboot. Damn strange, but I still do an offline diag on the drives now and then just to be sure all is O-Tay.
-Stoic Joker (June 01, 2011, 06:44 AM)
--- End quote ---

I tried SeaTools, but the S.M.A.R.T. tests wouldn't run.

I've also rebooted once. Same error occurs.

I'll see if I can get some other diagnostic tools to work. The Seagate tools don't seem to want to run now for some reason...

phitsc:
If in any doubt, I would advise to get rid of a possibly defective hard-drive rather sooner than later. Already suspicious noises are reason enough for me. I've learned it the hard way too :(

Stoic Joker:
Hm... if SeaTools wont run on a SeaGate HDD (assuming it is th latest version...), that would indeed be a bad sign. Hitachi has a good one for doing any (or oddball) drives, but there's enough propriatery error checks/codes to make cross brand testing a bit iffy.

 Perhapps best to stop screwing with it until everythng is safely backed up. (Yes, a last minute quicky - for the really critical stuff - is recommended if the ship is sinking slowly enough)

Navigation

[0] Message Index

[#] Next page

[*] Previous page

Go to full version