Topic: DegradedArray on single disk

[pfloor]

Well certainly no one could disagree if I said the raid reporting is convoluted to some vast degree.

A simple Table format might have served to overcome the confusion the current report presents to first time viewing.

The ability to convolute something is a favorite past time of the Linux world.

It lends itself to the main reason why there aren't more Linux user's then M$.
 

No need to excuse ignorance, on the other hand there is always a need to excuse Stupidity.

So your not excused, however the possibility exists that you may be excused in the future.

Only time will tell. LOL

hth

electroman00, stick to the topic at hand and keep comments like this to yourself.

Your next off topic comment will be removed and if you continue, you will be banned.

[electroman00]

--

[electroman00]

--

[Agent86]

electroman00- Funny 

pfloor- I understand now that SME creates my raid from 2) partitions on the same drive

Let me consider this out loud again just to be sure I understand this.
For example in my case,of course I"m not positive if this is the case, but lets say hda1[1] is the boot partition which is synced to hdc1[1] in this case the SME system is ok, because the mda1 checks out so the first partition on the first drive is sync'd with the first partition on the second drive.

Second the mda2 lets say is data partition etc. which is the second partition on the first drive aka=hda2[0] sync'd to the second partition of the second drive aka=hdc2[0]

So in this case the first mda1 which is the raid, and the [UU] shows that both the first partition of the first drive and the first partition of the second drive or OK

And the mda2 shows the [_U] which indicates the second partition of the first drive has failed and the second partition of the second drive is good.

I think I understand now.

Thanks to all this is a great help, and please correct me if I"m wrong.

I'll move to testing the drive now using the wiki linked here. Thanks
 

[Agent86]

Here is the smart report in email to admin:

The following warning/error was logged by the smartd daemon:

Device: /dev/hda, 103 Offline uncorrectable sectors

and this:

The following warning/error was logged by the smartd daemon:

Device: /dev/hda, 13 Currently unreadable (pending) sectors

And this from the smart report:

=== START OF INFORMATION SECTION ===
Device Model:     Maxtor 6Y060L0
Serial Number:    Y2P6KRYE
Firmware Version: YAR41BW0
User Capacity:    61,492,838,400 bytes
Device is:        In smartctl database [for details use: -P show]
ATA Version is:   7
ATA Standard is:  ATA/ATAPI-7 T13 1532D revision 0
Local Time is:    Sat Nov  8 09:04:27 2008 EST
SMART support is: Available - device has SMART capability.
SMART support is: Enabled

=== START OF READ SMART DATA SECTION ===
SMART overall-health self-assessment test result: PASSED

General SMART Values:
Offline data collection status:  (0x80)   Offline data collection activity
               was never started.
               Auto Offline Data Collection: Enabled.
Self-test execution status:      (   0)   The previous self-test routine completed
               without error or no self-test has ever
               been run.
Total time to complete Offline
data collection:        ( 181) seconds.
Offline data collection
capabilities:           (0x5b) SMART execute Offline immediate.
               Auto Offline data collection on/off support.
               Suspend Offline collection upon new
               command.
               Offline surface scan supported.
               Self-test supported.
               No Conveyance Self-test supported.
               Selective Self-test supported.
SMART capabilities:            (0x0003)   Saves SMART data before entering
               power-saving mode.
               Supports SMART auto save timer.
Error logging capability:        (0x01)   Error logging supported.
               No General Purpose Logging support.
Short self-test routine
recommended polling time:     (   2) minutes.
Extended self-test routine
recommended polling time:     (  31) minutes.

SMART Attributes Data Structure revision number: 16
Vendor Specific SMART Attributes with Thresholds:
ID# ATTRIBUTE_NAME          FLAG     VALUE WORST THRESH TYPE      UPDATED  WHEN_FAILED RAW_VALUE
  3 Spin_Up_Time            0x0027   224   223   063    Pre-fail  Always       -       4981
  4 Start_Stop_Count        0x0032   253   253   000    Old_age   Always       -       41
  5 Reallocated_Sector_Ct   0x0033   253   253   063    Pre-fail  Always       -       1
  6 Read_Channel_Margin     0x0001   253   253   100    Pre-fail  Offline      -       0
  7 Seek_Error_Rate         0x000a   253   029   000    Old_age   Always       -       0
  8 Seek_Time_Performance   0x0027   252   245   187    Pre-fail  Always       -       52170
  9 Power_On_Minutes        0x0032   161   161   000    Old_age   Always       -       247h+58m
 10 Spin_Retry_Count        0x002b   253   252   157    Pre-fail  Always       -       0
 11 Calibration_Retry_Count 0x002b   253   252   223    Pre-fail  Always       -       0
 12 Power_Cycle_Count       0x0032   253   253   000    Old_age   Always       -       44
192 Power-Off_Retract_Count 0x0032   253   253   000    Old_age   Always       -       0
193 Load_Cycle_Count        0x0032   253   253   000    Old_age   Always       -       0
194 Temperature_Celsius     0x0032   253   253   000    Old_age   Always       -       37
195 Hardware_ECC_Recovered  0x000a   253   252   000    Old_age   Always       -       543
196 Reallocated_Event_Count 0x0008   253   253   000    Old_age   Offline      -       0
197 Current_Pending_Sector  0x0008   253   253   000    Old_age   Offline      -       0
198 Offline_Uncorrectable   0x0008   253   253   000    Old_age   Offline      -       0
199 UDMA_CRC_Error_Count    0x0008   199   199   000    Old_age   Offline      -       0
200 Multi_Zone_Error_Rate   0x000a   253   252   000    Old_age   Always       -       0
201 Soft_Read_Error_Rate    0x000a   253   119   000    Old_age   Always       -       26
202 TA_Increase_Count       0x000a   253   252   000    Old_age   Always       -       0
203 Run_Out_Cancel          0x000b   253   252   180    Pre-fail  Always       -       0
204 Shock_Count_Write_Opern 0x000a   253   252   000    Old_age   Always       -       0
205 Shock_Rate_Write_Opern  0x000a   253   252   000    Old_age   Always       -       0
207 Spin_High_Current       0x002a   253   252   000    Old_age   Always       -       0
208 Spin_Buzz               0x002a   253   252   000    Old_age   Always       -       0
209 Offline_Seek_Performnce 0x0024   179   179   000    Old_age   Offline      -       0
 99 Unknown_Attribute       0x0004   253   253   000    Old_age   Offline      -       0
100 Unknown_Attribute       0x0004   253   253   000    Old_age   Offline      -       0
101 Unknown_Attribute       0x0004   253   253   000    Old_age   Offline      -       0

SMART Error Log Version: 1
No Errors Logged

SMART Self-test log structure revision number 1
No self-tests have been logged.  [To run self-tests, use: smartctl -t]


SMART Selective self-test log data structure revision number 1
 SPAN  MIN_LBA  MAX_LBA  CURRENT_TEST_STATUS
    1        0        0  Not_testing
    2        0        0  Not_testing
    3        0        0  Not_testing
    4        0        0  Not_testing
    5        0        0  Not_testing
Selective self-test flags (0x0):
  After scanning selected spans, do NOT read-scan remainder of disk.
If Selective self-test is pending on power-up, resume after 0 minute delay.

So I did have some power outages, but not sure if this could cause this type of failure or if this means replace drive.

Anyhow I don't understand the message other then degraded raid and looks to me like hard drive failure.

What do you think ?

[electroman00]

Agent86

Here's something really funny.

Check the date on the drive, if it's more then 38 months old (3yrs-2months) get a hammer
and take all your frustrations out on that drive so nobody can recover data from it and then send it to the scrap yard.

Could have save a whole thread if I knew it was a MAXTOR drive.

Shame on me, I should have asked.

That 60 gig is probably clocking in at > 4years old.

Seagate or WD drives, use them for 25 years and they are the the best.

Yes Seagate bought Maxtor few years ago but I'm not going to be a guinea pig for Maxtor any more
even if god bought them.

What's that about lipstick on a pig....still a pig...LOL

I've grown quite fond of Maxtor drives if you haven't noticed. LOL

BTW they don't make good hockey pucks either, I tried that.

Just in case you don't have one http://www.computerhammer.com/

Have a good one...

[Agent86]

electroman00-
I understand you have had bad experience with Maxtor, however I've had bad experience with Seagate over the past 20 years, in fact I've never had a Seagate drive last more then 1 year for some reason. So I stopped using them and went with Western Digital mostly, however lately those have failed early as well also.

My opinion is that all of the drives are about the same to me. I can't say that I've had much luck with Seagate, however I know that many people use them and like them.

Anyhow this maxtor was used when I got it, about 3 years old already and I used it for about 3+ years myself so I can't complain too much about it. Also I have additional square trade warranty on my stuff So I still have it covered under warranty LOL that is one good thing about ebay I do like.

Anyhow thanks for all the help I'll be looking to upgrade the server and perhaps ditch this old one.

[electroman00]

Agent86

Tried to AIM ya. Got some server info for ya.

[Agent86]

Got it thanks,

[byte]

This thread has gone (way) off topic, locking thread.