Home / server / Questions

Questions[seagate](server)

Martin Hope
aSteve
Asked: 2012-01-20 10:32:00 +0800 CST
  • 5

I bought a 1TB Seagate Barracuda 7200.12 - ST31000528AS drive about 18 months ago because it had a 5-year warranty, and used it alongside a Samsung Spinpoint under Ubuntu Server as one half of a software RAID-1 array.

Yesterday, smartd started reporting a problem:

Jan 18 06:08:03 svr smartd[2672]: Device: /dev/sdb [SAT], 2 Currently unreadable (pending) sectors
Jan 18 06:08:03 svr smartd[2672]: Device: /dev/sdb [SAT], 2 Offline uncorrectable sectors

I followed this up by investigations with smartctl... and, after scheduling some tests, I get these results:

$ smartctl -l error /dev/sdb
smartctl 5.41 2011-06-09 r3365 [x86_64-linux-3.0.0-14-generic] (local build)
Copyright (C) 2002-11 by Bruce Allen, http://smartmontools.sourceforge.net

=== START OF READ SMART DATA SECTION ===
SMART Error Log Version: 1
No Errors Logged
$ smartctl -l selftest /dev/sdb
smartctl 5.41 2011-06-09 r3365 [x86_64-linux-3.0.0-14-generic] (local build)
Copyright (C) 2002-11 by Bruce Allen, http://smartmontools.sourceforge.net

=== START OF READ SMART DATA SECTION ===
SMART Self-test log structure revision number 1
Num  Test_Description    Status                  Remaining  LifeTime(hours)  LBA_of_first_error
# 1  Extended offline    Completed: read failure       10%     12451         1953523918
# 2  Short offline       Completed: read failure       90%     12445         1953523918
# 3  Short offline       Completed: read failure       60%     12445         1953523918
# 4  Extended offline    Completed without error       00%      5532         -

$

Only the 'selftest' output documents any kind of a problem - though I'm not 100% clear how to interpret it. I suspect I may have scheduled two short tests at the same time... though I'm not sure why one has 90% remaining and the other 60%. Come to that, I can't see why my long test has 10% remaining.

Another curious thing is that Raid-1 hasn't detected any kind of problem (or, at least, that's what I understand "[2/2][UU]" means. While there are three partitions on sdb, only one is not trivially small... Of the other two, one is a boot partition (replicated between both drives for disaster recovery) and the other is swap.

$ cat /proc/mdstat
Personalities : [linear] [multipath] [raid0] [raid1] [raid6] [raid5] [raid4] [raid10]
md0 : active raid1 sdb3[1] sda3[0]
      967843840 blocks [2/2] [UU]

unused devices: <none>

A few questions...

  • Am I correct in thinking that this is strong evidence that sdb has a fault? Is it possible that this is a software not hardware issue?
  • Can I get a list of all the blocks that are detected as faulty - and establish which partitions they're in?
  • Can I (do I need to) map-out these bad sectors pending acquisition of a replacement drive?
  • Are a lot of people experiencing this sort of problem with the 1TB Seagate Barracuda drives?
  • Does anyone know if the output from smartmontools above is sufficient evidence of fault to secure a replacement under warranty?

Any advice/comments warmly appreciated... :)

As requested... smartctl --all /dev/sdb

smartctl 5.41 2011-06-09 r3365 [x86_64-linux-3.0.0-14-generic] (local build)
Copyright (C) 2002-11 by Bruce Allen, http://smartmontools.sourceforge.net

=== START OF INFORMATION SECTION ===
Model Family:     Seagate Barracuda 7200.12
Device Model:     ST31000528AS
Serial Number:    9VP5LFZA
LU WWN Device Id: 5 000c50 0200362a0
Firmware Version: CC38
User Capacity:    1,000,204,886,016 bytes [1.00 TB]
Sector Size:      512 bytes logical/physical
Device is:        In smartctl database [for details use: -P show]
ATA Version is:   8
ATA Standard is:  ATA-8-ACS revision 4
Local Time is:    Thu Jan 19 18:54:01 2012 GMT
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:  (0x82)     Offline data collection activity
                                    was completed without error.
                                    Auto Offline Data Collection: Enabled.
Self-test execution status:      ( 113)     The previous self-test completed having
                                    the read element of the test failed.
Total time to complete Offline
data collection:            (  609) seconds.
Offline data collection
capabilities:                        (0x7b) SMART execute Offline immediate.
                                    Auto Offline data collection on/off support.
                                    Suspend Offline collection upon new
                                    command.
                                    Offline surface scan supported.
                                    Self-test supported.
                                    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.
                                    General Purpose Logging supported.
Short self-test routine
recommended polling time:    (   1) minutes.
Extended self-test routine
recommended polling time:    ( 178) minutes.
Conveyance self-test routine
recommended polling time:    (   2) minutes.
SCT capabilities:          (0x103f) SCT Status supported.
                                    SCT Error Recovery Control supported.
                                    SCT Feature Control supported.
                                    SCT Data Table supported.

SMART Attributes Data Structure revision number: 10
Vendor Specific SMART Attributes with Thresholds:
ID# ATTRIBUTE_NAME          FLAG     VALUE WORST THRESH TYPE      UPDATED  WHEN_FAILED RAW_VALUE
  1 Raw_Read_Error_Rate     0x000f   118   099   006    Pre-fail  Always       -       198953639
  3 Spin_Up_Time            0x0003   095   095   000    Pre-fail  Always       -       0
  4 Start_Stop_Count        0x0032   100   100   020    Old_age   Always       -       32
  5 Reallocated_Sector_Ct   0x0033   100   100   036    Pre-fail  Always       -       0
  7 Seek_Error_Rate         0x000f   076   060   030    Pre-fail  Always       -       45828174
  9 Power_On_Hours          0x0032   086   086   000    Old_age   Always       -       12498
 10 Spin_Retry_Count        0x0013   100   100   097    Pre-fail  Always       -       0
 12 Power_Cycle_Count       0x0032   100   100   020    Old_age   Always       -       16
183 Runtime_Bad_Block       0x0032   100   100   000    Old_age   Always       -       0
184 End-to-End_Error        0x0032   100   100   099    Old_age   Always       -       0
187 Reported_Uncorrect      0x0032   100   100   000    Old_age   Always       -       0
188 Command_Timeout         0x0032   100   100   000    Old_age   Always       -       0
189 High_Fly_Writes         0x003a   100   100   000    Old_age   Always       -       0
190 Airflow_Temperature_Cel 0x0022   064   056   045    Old_age   Always       -       36 (Min/Max 25/44)
194 Temperature_Celsius     0x0022   036   044   000    Old_age   Always       -       36 (0 20 0 0)
195 Hardware_ECC_Recovered  0x001a   025   011   000    Old_age   Always       -       198953639
197 Current_Pending_Sector  0x0012   100   100   000    Old_age   Always       -       2
198 Offline_Uncorrectable   0x0010   100   100   000    Old_age   Offline      -       2
199 UDMA_CRC_Error_Count    0x003e   200   200   000    Old_age   Always       -       0
240 Head_Flying_Hours       0x0000   100   253   000    Old_age   Offline      -       253776732631285
241 Total_LBAs_Written      0x0000   100   253   000    Old_age   Offline      -       2894995523
242 Total_LBAs_Read         0x0000   100   253   000    Old_age   Offline      -       2366564210

SMART Error Log Version: 1
No Errors Logged

SMART Self-test log structure revision number 1
Num  Test_Description    Status                  Remaining  LifeTime(hours)  LBA_of_first_error
# 1  Extended offline    Completed: read failure       10%     12451         1953523918
# 2  Short offline       Completed: read failure       90%     12445         1953523918
# 3  Short offline       Completed: read failure       60%     12445         1953523918
# 4  Extended offline    Completed without error       00%      5532         -

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.
hard-drive linux raid smart seagate
Martin Hope
Torben Warberg Rohde
Asked: 2011-05-20 00:36:02 +0800 CST
  • 2

Has anyone got real-life experience with using a Seagate Savvio disk in a HP ML350 G5 server. There are two things I'm worried about.

  1. Will it physically fit the tray, can the tray be inserted and will the SAS-connectors fit the connectors on the HD back plane.

  2. Will the RAID adapter accept it.

I have posted similar questions before and have gotten fairly fluffy answers. So I'm hoping someone have actually tried it with the same server (or at least just a fairly similar HP server with 2.5" disk trays).

hard-drive hp seagate
Martin Hope
Stefan Lasiewski
Asked: 2010-05-27 09:44:41 +0800 CST
  • 3

I'm running FreeBSD 7.2, with Seagate Cheetah (Model ST####) drives.

We are having some problems with the SCSI drives on these machines. Our vendor says that updating the firmware on the drives may fix the problems, and a firmware update did seem to fix some SCSI problems on another FreeBSD host.

How can I view the firmware version of these drives? I tried some tips from nixCraft, but nothing has worked so far. In dmesg, I see the Make and Model, but no firmware revision.

In Linux, this information is often in /var/log/dmesg (Although /var/log/dmesg is sometimes out of date), or I often find this information with something like sudo lshw -class disk, lshal or dmidecode.

Update: Wed May 26 12:00:09 PDT 2010

Well, turns out I was wrong. Or a little misled. 'dmesg' will show the firmware version, provided that the files at /var/log/dmesg.today and /var/log/dmesg.yesterday haven't been clobbered by the log rotation. I also didn't recognize that '0003' stood for the firmware revision.

# grep -i seagate /var/log/*
/var/log/dmesg.today:da2: <SEAGATE ST3300655LC 0003> Fixed Direct Access SCSI-3 device 
/var/log/dmesg.today:da3: <SEAGATE ST3300655LC 0003> Fixed Direct Access SCSI-3 device

The fields listed here are <"Make" "Model" "Firmware">.

freebsd storage seagate
Martin Hope
mjallday
Asked: 2009-06-13 00:44:14 +0800 CST
  • 2

I just got some replacement drives for a server here, went to pop one in, and it turns out that the 72Gig for a Seagate is slightly below the 72gig of the Maxtors that we currently have.

Does anyone know if there is anything hidden on the drive causing this discrepancy? I'm facing a rebuild of the array if I can't find an extra 150MB on this disk. :)

raid dell-poweredge scsi seagate
Martin Hope
Neil
Asked: 2009-05-23 12:57:42 +0800 CST
  • 4

I found this hard drive on NewEgg:

Seagate Barracuda 7200.11 ST31500341AS 1.5TB 7200 RPM 32MB Cache SATA 3.0Gb/s 3.5" Internal Hard Drive (bare drive) - OEM

http://www.newegg.com/Product/Product.aspx?Item=N82E16822148337

And there are quite a few substantial bad reviews about the drive freezing periodically. If you search for a bit, you can find several forums with people having problems, but of course forums don't get updated when resolutions to those problems are found.

I'm just wondering, does anyone know what the final verdict regarding the freezing issue with these hard drives is?

hard-drive firmware seagate