[prev in list] [next in list] [prev in thread] [next in thread] 

List:       smartmontools-support
Subject:    [smartmontools-support] Samsung F4 EcoGreen and bad blocks (mabye
From:       Stefan Seifert <Steve () owv-hv ! de>
Date:       2010-11-27 22:02:47
Message-ID: 4CF18007.7010301 () owv-hv ! de
[Download RAW message or body]

Hello,

I've recently bought some Samsung F4 EcoGreen HD204UI with the FW
1AQ10001. I had failed WRITE and READ and badblocks in my dmesg on my
Fedora 12. So at first I thought the drives are bad therefore I bought
some more to replace them in the raid.

Nevertheless yesterday I read the articles about the smartctl problem
with the Samsung F4 drives. So I assumed thats where the errors come
from as I had smartd running on Fedora.

Today I made some testings with the disks. I switched from Fedora 12 to
Ubuntu Server 10.10 and had a minimal installation without smartd
running or smartmontools even installed. After running bonnie++ on the
raid5 I again had following erros in my dmesg:

[ 1332.080048] ata4.00: exception Emask 0x0 SAct 0x7fffffff SErr 0x0
action 0x6 frozen
[ 1332.151525] ata4.00: failed command: WRITE FPDMA QUEUED
[ 1332.151530] ata4.00: cmd 61/08:00:57:2b:9a/00:00:2f:00:00/40 tag 0
ncq 4096 out
[ 1332.151531]          res 40/00:ff:00:00:00/00:00:00:00:00/40 Emask
0x4 (timeout)
[ 1332.151533] ata4.00: status: { DRDY }
[ 1332.151776] ata4: hard resetting link
[ 1332.660020] ata4: SATA link up 3.0 Gbps (SStatus 123 SControl 300)
[ 1332.700309] ata4.00: configured for UDMA/133
[ 1332.700313] ata4.00: device reported invalid CHS sector 0
[ 1332.700315] ata4.00: device reported invalid CHS sector 0
[ 1332.700317] ata4.00: device reported invalid CHS sector 0

And this is very reproduceable, everytime I run bonnie++ I get those on
all the different ataX channels.

So no smartd/smartmontools installed still errors.

Then I put a _NEW_ disk, a disk which wasn't yet in the raid or even in
the fileserver, into my workstation (Windows 7 64bit).
After transfering some gb to it I had a NTFS error poping up in my event
log:

The default transaction resource manager on volume E: encountered a
non-retryable error and could not start.  The data contains the error code.

When testing this I didn't have smartmontools installed on windows/linux
or checking the smart status of any disk.
I'm not entirely sure if Windows itself checks the smart status nowadays so.


Ok now the following question arises, if the HDD itself is the problem
and this is not tied to smartmontools etc. Maybe it just can be
triggered faster when using smartctl?

Can anyone confirm this? And has similiar problems?
If my conclusion is wrong or I'm missing something please tell me. :-)


Best regards
Steve



------------------------------------------------------------------------------
Increase Visibility of Your 3D Game App & Earn a Chance To Win $500!
Tap into the largest installed PC base & get more eyes on your game by
optimizing for Intel(R) Graphics Technology. Get started today with the
Intel(R) Software Partner Program. Five $500 cash prizes are up for grabs.
http://p.sf.net/sfu/intelisp-dev2dev
_______________________________________________
Smartmontools-support mailing list
Smartmontools-support@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/smartmontools-support
[prev in list] [next in list] [prev in thread] [next in thread]