Initial problems with WD20EARS - bad sign? Should I RMA it?

Silencing hard drives, optical drives and other storage devices

Moderators: NeilBlanchard, Ralf Hutter, sthayashi, Lawrence Lee

Post Reply
graysky
Posts: 147
Joined: Fri Sep 16, 2005 4:14 pm
Location: My desk

Initial problems with WD20EARS - bad sign? Should I RMA it?

Post by graysky » Thu Jun 24, 2010 3:51 pm

I just installed a new WD Green WD20EARS in my system (Linux with latest kernel 2.6.34). When I attempted to query it via smartmontools I got:

Code: Select all

# smartctl -a /dev/sdc
smartctl 5.39.1 2010-01-28 r3054 [x86_64-unknown-linux-gnu] (local build)
Copyright (C) 2002-10 by Bruce Allen, http://smartmontools.sourceforge.net

Device: °ód  Version: 
>> Terminate command early due to bad response to IEC mode page
A mandatory SMART command failed: exiting. To continue, add one or more '-T permissive' options.
Further, after I partitioned it (single partition starting on sector 2048 to keep everything aligned to the 4k sector size), I couldn't write an ext4 file system to the drive:

Code: Select all

# mkfs.ext4 /dev/sdc1
mke2fs 1.41.12 (17-May-2010)
Filesystem label=
OS type: Linux
Block size=4096 (log=2)
Fragment size=4096 (log=2)
Stride=0 blocks, Stripe width=0 blocks
122101760 inodes, 488378390 blocks
24418919 blocks (5.00%) reserved for the super user
First data block=0
Maximum filesystem blocks=4294967296
14905 block groups
32768 blocks per group, 32768 fragments per group
8192 inodes per group
Superblock backups stored on blocks: 
	32768, 98304, 163840, 229376, 294912, 819200, 884736, 1605632, 2654208, 
	4096000, 7962624, 11239424, 20480000, 23887872, 71663616, 78675968, 
	102400000, 214990848

Writing inode tables: done                            
ext2fs_mkdir: Attempt to read block from filesystem resulted in short read while creating root dir
As you can see, it gave this odd "ext2fs_mkdir: Attempt to read block from filesystem resulted in short read while creating root dir" error.

I have since nuked the MBR and partition tables with dd and repeated the process which did not give errors. I have been rsyncing files on to it for the past few hours with no complaints. It seems to be okay but should I be worried about this and should I RMA the drive?

joetekubi
Posts: 38
Joined: Mon May 24, 2010 11:21 am
Location: Atlanta

wierd

Post by joetekubi » Fri Jun 25, 2010 4:40 am

I've never seen a SATA disk not report for "smartctl".
A google search shows only very old Linux versions with problems.

My BIOS menus show something like:
"Drive SATA 1 SMART" etc

You might check there.

You might also boot the latest Knoppix or other live distro to check if it's possibly a problem with your OS.

re: ext4.
Sorry, no knowledge. Looks like you partitioned the drive correctly.

-joe

Post Reply