headers
Karl Pielorz | 1 Jan 2011 14:01
Picon

Re: WARNING: Using smartctl with Samsung F4 EcoGreen may result in bad blocks


--On 09 December 2010 07:41 +0100 Christian Franke 
<Christian.Franke <at> t-online.de> wrote:

> Christian Franke wrote:
>> Dear smartmontools users,
>>
>> please read the following warning about smartmontools and Samsung F4
>> EcoGreen drives:
>>
>> http://sourceforge.net/apps/trac/smartmontools/wiki/SamsungF4EGBadBlocks
>
> Samsung released a firmware patch:
> http://www.samsung.com/global/business/hdd/faqView.do?b2b_bbs_msg_id=386

Hi,

I just bought a couple of these drives (Firmware 1AQ10001) - I've applied 
the above patch. I didn't get a chance to 'test' these before applying the 
patch.

If I can 'safely' (i.e. without error) leave something like 'dd 
if=/dev/ada0 of=/dev/null' running in background, while running multiple 
"smartctl -a /dev/ada0" in another window - is that a good enough test to 
know the drives are patched, and OK now?

I've left this running for about 30 minutes (running the smartctl over and 
over) - and have no errors logged...

The firmware ID hasn't changed on the drives after patching, which is a
(Continue reading)

Permalink | Reply | 1 comment |
headers
Christian Franke | 1 Jan 2011 14:17
Picon
Favicon

Re: WARNING: Using smartctl with Samsung F4 EcoGreen may result in bad blocks

Karl Pielorz wrote:
>
>
> I just bought a couple of these drives (Firmware 1AQ10001) - I've 
> applied the above patch. I didn't get a chance to 'test' these before 
> applying the patch.
>
> If I can 'safely' (i.e. without error) leave something like 'dd 
> if=/dev/ada0 of=/dev/null' running in background, while running 
> multiple "smartctl -a /dev/ada0" in another window - is that a good 
> enough test to know the drives are patched, and OK now?

Sorry no. The problem only occurs when data is written (NCQ enabled). It 
does not produce any error condition visible to dd. Therefore it is 
necessary write changed data, read it back and compare the result.

This can be done with badblocks command:
http://sourceforge.net/apps/trac/smartmontools/wiki/SamsungF4EGBadBlocks#Howtoreproduce

Thanks,
Christian

------------------------------------------------------------------------------
Learn how Oracle Real Application Clusters (RAC) One Node allows customers
to consolidate database storage, standardize their database environment, and, 
should the need arise, upgrade to a full multi-node Oracle RAC database 
without downtime or disruption
http://p.sf.net/sfu/oracle-sfdevnl
Permalink | Reply | 0 comments |
headers
sunny.song | 1 Jan 2011 15:12
Favicon

Sunny Song/Singapore/HGST is out of the office.


I will be out of the office starting  12/27/2010 and will not return until
01/02/2011.

I do not have access to my email. If there is any urgent issues, pls
contact my Manager Mr.David Ngoi at "david.ngoi <at> hitachigst.com " .

Thanks.

------------------------------------------------------------------------------
Learn how Oracle Real Application Clusters (RAC) One Node allows customers
to consolidate database storage, standardize their database environment, and, 
should the need arise, upgrade to a full multi-node Oracle RAC database 
without downtime or disruption
http://p.sf.net/sfu/oracle-sfdevnl
Permalink | Reply | 0 comments |
headers
Orcan Ogetbil | 3 Jan 2011 20:23
Picon
Favicon

Re: smartctl output too long for Fujitsu

On Monday, December 13, 2010 16:54:17 Christian Franke wrote:
> Orcan Ogetbil wrote:
> > Hi all,
> > 
> > I get the following smartctl output for our Fujitsu boxes. Is this
> > normal, are there any fixes or workarounds? I am using
> > smartmontools-5.40
> > 
> > Thanks,
> > Orcan
> > 
> > 
> > # smartctl -d megaraid,4 /dev/sda
> > 
> > smartctl 5.40 2010-10-16 r3189 [x86_64-koji-linux-gnu] (local build)
> > Copyright (C) 2002-10 by Bruce Allen,
> > http://smartmontools.sourceforge.net
> > 
> > Device: FUJITSU  MBD2147RC        Version: 5203
> > Serial number: D0A7PA604EV0
> > Device type: disk
> > Transport protocol: SAS
> > Local Time is: Wed Nov 10 10:22:19 2010 EST
> > Device supports SMART and is Enabled
> > Temperature Warning Disabled or Not Supported
> > SMART Health Status: OK
> > 
> > Current Drive Temperature:     23 C
> > Drive Trip Temperature:        65 C
> > Manufactured in week 25 of year 2010
(Continue reading)

Permalink | Reply | 1 comment |
headers
Douglas Gilbert | 3 Jan 2011 21:08
Picon

Re: smartctl output too long for Fujitsu

On 11-01-03 02:23 PM, Orcan Ogetbil wrote:
> On Monday, December 13, 2010 16:54:17 Christian Franke wrote:
>> Orcan Ogetbil wrote:
>>> Hi all,
>>>
>>> I get the following smartctl output for our Fujitsu boxes. Is this
>>> normal, are there any fixes or workarounds? I am using
>>> smartmontools-5.40
>>>
>>> Thanks,
>>> Orcan
>>>
>>>
>>> # smartctl -d megaraid,4 /dev/sda
>>>
>>> smartctl 5.40 2010-10-16 r3189 [x86_64-koji-linux-gnu] (local build)
>>> Copyright (C) 2002-10 by Bruce Allen,
>>> http://smartmontools.sourceforge.net
>>>
>>> Device: FUJITSU  MBD2147RC        Version: 5203
>>> Serial number: D0A7PA604EV0
>>> Device type: disk
>>> Transport protocol: SAS
>>> Local Time is: Wed Nov 10 10:22:19 2010 EST
>>> Device supports SMART and is Enabled
>>> Temperature Warning Disabled or Not Supported
>>> SMART Health Status: OK
>>>
>>> Current Drive Temperature:     23 C
>>> Drive Trip Temperature:        65 C
(Continue reading)

Permalink | Reply | 0 comments |
headers
Matt Taggart | 3 Jan 2011 23:35
Picon
Favicon

update of drivedb causes failure

I am using the debian package version 5.39.1+svn3124-1 of smartmontools and 
if I update drivedb.h (r3221) I get an error

  foo.error(118): Syntax error in preset option string

line 118 is in the "SandForce Driven SSDs" section. If I remove that entire 
section things start working. I tested and the last version that works is 
r3134 before that section was added in r3135.

Do newer versions of drivedb have something that trips up older versions of 
smartctl? Is this expected to work?

Thanks,

--

-- 
Matt Taggart
taggart <at> debian.org

------- End of Blind-Carbon-Copy

------------------------------------------------------------------------------
Learn how Oracle Real Application Clusters (RAC) One Node allows customers
to consolidate database storage, standardize their database environment, and, 
should the need arise, upgrade to a full multi-node Oracle RAC database 
without downtime or disruption
http://p.sf.net/sfu/oracle-sfdevnl
Permalink | Reply | 1 comment |
headers
Christian Franke | 4 Jan 2011 07:44
Picon
Favicon

Re: update of drivedb causes failure

Matt Taggart wrote:
> I am using the debian package version 5.39.1+svn3124-1 of smartmontools and
> if I update drivedb.h (r3221) I get an error
>
>    foo.error(118): Syntax error in preset option string
>
>    
New raw print formats were added after r3124.

> line 118 is in the "SandForce Driven SSDs" section. If I remove that entire
> section things start working. I tested and the last version that works is
> r3134 before that section was added in r3135.
>
>    
For a r3124 SVN snapshot the following should work:

Use drivedb.h from trunk but replace the incompatible entry by the entry 
from the RELEASE_5_39_DRIVEDB branch.

> Do newer versions of drivedb have something that trips up older versions of
> smartctl? Is this expected to work?
>
>    
For SVN snapshot builds like the debian package it may work or not.

It is expected to work for official releases:
5.39[.X] -> Use drivedb.h from RELEASE_5_39_DRIVEDB branch
5.40[.X] -> Use drivedb.h from RELEASE_5_40_DRIVEDB branch if present 
else use trunk.
...
(Continue reading)

Permalink | Reply | 0 comments |
headers
Hoang Pham | 4 Jan 2011 15:22
Picon

smartmontools on Dell Perc 6/i RAID Controller using SATA Disks

I am trying to work out how to call scterc commands on a theoretical 
SATA drive connected through a Dell Perc 6/i

the array isn't up yet hence i can't test whether it works. but from my 
understanding
you are required to use
-d megaraid,N
where N is the drive 'number'
to reach a drive behind a perc(megaraid based)
now knowing this, this sounds like it was written for SAS drives behind 
the perc, but I am proposing the use of SATA drives

it apparently works in a sense with -T permissive, as in your able to 
get some sort of response
according to 
http://markmail.org/thread/nuidhcmsyheynhv2#query:+page:1+mid:nuidhcmsyheynhv2+state:results

but the functionality seems impaired,as per

Rejecting SMART/ATA command to controller
Rejecting SMART/ATA command to controller
Error SMART Status command failed

and i'm not sure scterc would work in this case

usually I would imagine the use of -d SAT would work around the problem 
of SATA drives on SAS controllers
but I need to use -d megaraid already?

------------------------------------------------------------------------------
(Continue reading)

Permalink | Reply | 0 comments |
headers
Hartmut | 6 Jan 2011 01:13

What means Error: ABRT

Hi Folks,

smartctl drops me the following line. What means "Error. ABRT"?

----------------------
Error 37 occurred at disk power-on lifetime: 4914 hours (204 days + 18 hours)
  When the command that caused the error occurred, the device was
active or idle.

  After command completion occurred, registers were:
  ER ST SC SN CL CH DH
  -- -- -- -- -- -- --
  04 51 00 03 4f c2 00  Error: ABRT

  Commands leading to the command that caused the error were:
  CR FR SC SN CL CH DH DC   Powered_Up_Time  Command/Feature_Name
  -- -- -- -- -- -- -- --  ----------------  --------------------
  b0 d4 00 03 4f c2 00 00      01:20:22.563  SMART EXECUTE OFF-LINE IMMEDIATE
  b0 d1 01 01 4f c2 00 00      01:20:22.500  SMART READ ATTRIBUTE
THRESHOLDS [OBS-4]
  b0 d0 01 00 4f c2 00 00      01:20:22.438  SMART READ DATA
  b0 da 00 00 4f c2 00 00      01:20:22.375  SMART RETURN STATUS
  b0 da 00 00 4f c2 00 00      01:20:22.375  SMART RETURN STATUS

Error 36 occurred at disk power-on lifetime: 4912 hours (204 days + 16 hours)
  When the command that caused the error occurred, the device was
active or idle.

  After command completion occurred, registers were:
  ER ST SC SN CL CH DH
(Continue reading)

Permalink | Reply | 1 comment |
headers
Dan Lukes | 6 Jan 2011 01:42
Picon

Re: What means Error: ABRT

On 6.1.2011 1:13, Hartmut:
> Hi Folks,
>
> smartctl drops me the following line. What means "Error. ABRT"?

The Error Register states the definition for ABRT is:

Bit 2 - ABRT (command aborted) is set to one to indicate the requested 
command has been command aborted because the command code or a command 
parameter is invalid, the command is not supported, a prerequisite for 
the command has not been met, or some other error has occurred.

Dan

------------------------------------------------------------------------------
Learn how Oracle Real Application Clusters (RAC) One Node allows customers
to consolidate database storage, standardize their database environment, and, 
should the need arise, upgrade to a full multi-node Oracle RAC database 
without downtime or disruption
http://p.sf.net/sfu/oracle-sfdevnl
Permalink | Reply | 0 comments |

Gmane