Linux - Hardware This forum is for Hardware issues.
Having trouble installing a piece of hardware? Want to know if that peripheral is compatible with Linux? |
| Notices |
Welcome to LinuxQuestions.org, a friendly and active Linux Community.
You are currently viewing LQ as a guest. By joining our community you will have the ability to post topics, receive our newsletter, use the advanced search, subscribe to threads and access many other special features. Registration is quick, simple and absolutely free. Join our community today!
Note that registered members see fewer ads, and ContentLink is completely disabled once you log in.
Are you new to LinuxQuestions.org? Visit the following links:
Site Howto |
Site FAQ |
Sitemap |
Register Now
If you have any problems with the registration process or your account login, please contact us. If you need to reset your password, click here.
Having a problem logging in? Please visit this page to clear all LQ-related cookies.
 |
GNU/Linux Basic Guide
This 255-page guide will provide you with the keys to understand the philosophy of free software, teach you how to use and handle it, and give you the tools required to move easily in the world of GNU/Linux. Many users and administrators will be taking their first steps with this GNU/Linux Basic guide and it will show you how to approach and solve the problems you encounter.
Click Here to receive this Complete Guide absolutely free. |
|
 |
09-18-2011, 04:56 AM
|
#1
|
|
Member
Registered: May 2006
Posts: 86
Rep:
|
WD20EARS - smartctl is reporting 4K physical sector size ^^
Hiho,
I'm running a raid5 with 3 WD20EARS hard disk drives. These days I bought 2 new drives to expand the current raid set. To eleminate problems during raid builds I always test new drives for errors. When I checked the SMART status I noticed by the way that the new drives report a physical sector size of 4096.
Strange, because the old and new HDDs have the same firmware version installed while the old ones still report a physical sector size of 512 (what's wrong as we know). I guess Western Digital has updated the firmware without changing the firmware number but other explanations are welcome.
This leads to my question. Does it have any impact of the handling from the kernel side or ist this just nice to know that the hard disk drives are reporting the correct physical sector size?
Regards
OK
|
|
|
|
09-18-2011, 01:57 PM
|
#2
|
|
Senior Member
Registered: Jul 2007
Location: Directly above centre of the earth, UK
Distribution: SuSE, plus some hopping
Posts: 3,669
|
Quote:
Originally Posted by Orangutanklaus
Strange, because the old and new HDDs have the same firmware version installed while the old ones still report a physical sector size of 512 (what's wrong as we know). I guess Western Digital has updated the firmware without changing the firmware number but other explanations are welcome.
|
What I remember of drives of this generation is that there was a jumper setting to choose between the drives 'native' 4096 and 'emulated' 512 byte settings. So, if this applies to the drives that you have, the first thing to do is to check the settings of any jumpers.
When you say "what's wrong as we know", then that isn't entirely true; if the drive is successfully emulating a 512 byte size, then, from the point of view of software, it looks exactly like a 512 byte drive, so when you ask the software what size the drive is, it isn't entirely incorrect of it reports that the size is 512. Well, the performance would be different, of course...
|
|
|
|
09-19-2011, 06:30 AM
|
#3
|
|
Senior Member
Registered: Mar 2011
Location: Brisneyland
Distribution: Debian, aptosid
Posts: 2,913
|
Nah, there is no jumper to cheange from 512b to 4K on the EARS drives.
As for why your new drives apear as 4k in SMART, it could be due to SMART upates. But if the older drives apearas 512b drives still thats not likely....
BTW, you do know that the 'green power' drives are not recommended for RAID arrays?
Quote:
Originally Posted by salasi
When you say "what's wrong as we know", then that isn't entirely true; if the drive is successfully emulating a 512 byte size, then, from the point of view of software, it looks exactly like a 512 byte drive, so when you ask the software what size the drive is, it isn't entirely incorrect of it reports that the size is 512. Well, the performance would be different, of course...
|
512b 'emulation' can cause partion alingment problems. If the drives correctly reported as 4K drives to OSes/tools that 'know' about 4K sectors, alignment is not a problem.
|
|
|
|
09-19-2011, 09:36 AM
|
#4
|
|
Senior Member
Registered: Jul 2007
Location: Directly above centre of the earth, UK
Distribution: SuSE, plus some hopping
Posts: 3,669
|
Err, yes, the jumper only offsets by one, it is the align tool that gets closer to 4k emulation. So, I guess, it more closely depends on whether anyone has run the align software tool or the default firmware align state from WD has changed.
|
|
|
|
| Thread Tools |
Search this Thread |
|
|
|
Posting Rules
|
You may not post new threads
You may not post replies
You may not post attachments
You may not edit your posts
HTML code is Off
|
|
|
All times are GMT -5. The time now is 02:49 AM.
|
|
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.
|
Latest Threads
LQ News
|
|