NASLite Network Attached Storage

www.serverelements.com
Task-specific simplicity with low hardware requirements.
It is currently Wed Oct 16, 2019 12:19 pm

All times are UTC - 5 hours [ DST ]




Post new topic Reply to topic  [ 19 posts ]  Go to page Previous  1, 2
Author Message
PostPosted: Sun May 12, 2013 7:07 pm 
Offline

Joined: Sat May 27, 2006 1:56 pm
Posts: 59
Ralph,

As requested:

Code:
Disk-2 Hardware Details:
   MODEL: WDC WD30EZRX-00MMMB0, SN# WD-WCAWZ2549821, v.80.00A80
   INTERFACE: DEVICE-SDB, HOST-1, BUS-0, TARGET-0, LUN-0

Filesystem Details:
tune2fs 1.40.4 (31-Dec-2007)
Filesystem volume name:   NASLite-SE000121
Last mounted on:         
Filesystem UUID:          5fe9aa1c-33ac-4ec1-acfd-4fc2c2b1c5dc
Filesystem magic number:  0xEF53
Filesystem revision #:    1 (dynamic)
Filesystem features:      has_journal ext_attr resize_inode dir_index filetype needs_recovery sparse_super large_file
Filesystem flags:         signed directory hash
Default mount options:    user_xattr acl
Filesystem state:         clean
Errors behavior:          Continue
Filesystem OS type:       Linux
Inode count:              183148544
Block count:              732565353
Reserved block count:     0
Free blocks:              405830698
Free inodes:              183145523
First block:              0
Block size:               4096
Fragment size:            4096
Reserved GDT blocks:      849
Blocks per group:         32768
Fragments per group:      32768
Inodes per group:         8192
Inode blocks per group:   512
Filesystem created:       Fri May  3 17:39:46 2013
Last mount time:          Sun May 12 23:43:44 2013
Last write time:          Sun May 12 23:43:44 2013
Mount count:              9
Maximum mount count:      -1
Last checked:             Fri May  3 17:39:46 2013
Check interval:           15552000 (6 months)
Next check after:         Wed Oct 30 17:39:46 2013
Reserved blocks uid:      0 (user admin)
Reserved blocks gid:      0 (group admin)
First inode:              11
Inode size:        256
Journal inode:            8
Default directory hash:   half_md4
Directory Hash Seed:      b5396727-da3a-448a-87d1-51c62432123f
Journal backup:           inode blocks

 Disk-3 Hardware Details:
   MODEL: WDC WD30EZRX-00MMMB0, SN# WD-WCAWZ2549990, v.80.00A80
   INTERFACE: DEVICE-SDC, HOST-2, BUS-0, TARGET-0, LUN-0

Filesystem Details:
tune2fs 1.40.4 (31-Dec-2007)
Filesystem volume name:   NASLite-SE000121
Last mounted on:         
Filesystem UUID:          728138c9-e3a2-4f7a-adf2-216b580addf4
Filesystem magic number:  0xEF53
Filesystem revision #:    1 (dynamic)
Filesystem features:      has_journal ext_attr resize_inode dir_index filetype needs_recovery sparse_super large_file
Filesystem flags:         signed directory hash
Default mount options:    user_xattr acl
Filesystem state:         clean
Errors behavior:          Continue
Filesystem OS type:       Linux
Inode count:              183148544
Block count:              732565353
Reserved block count:     0
Free blocks:              355122828
Free inodes:              183144982
First block:              0
Block size:               4096
Fragment size:            4096
Reserved GDT blocks:      849
Blocks per group:         32768
Fragments per group:      32768
Inodes per group:         8192
Inode blocks per group:   512
Filesystem created:       Fri May  3 19:23:27 2013
Last mount time:          Sun May 12 23:43:44 2013
Last write time:          Sun May 12 23:43:44 2013
Mount count:              7
Maximum mount count:      -1
Last checked:             Fri May  3 19:23:27 2013
Check interval:           15552000 (6 months)
Next check after:         Wed Oct 30 19:23:27 2013
Reserved blocks uid:      0 (user admin)
Reserved blocks gid:      0 (group admin)
First inode:              11
Inode size:        256
Journal inode:            8
Default directory hash:   half_md4
Directory Hash Seed:      a35df227-7082-410a-b537-3329f6b6e54e
Journal backup:           inode blocks


Hard drive spec sheet: http://www.wdc.com/wdproducts/library/SpecSheet/ENG/2879-771438.pdf


Top
 Profile  
 
PostPosted: Mon May 13, 2013 10:58 am 
Offline
Site Admin

Joined: Tue Jul 13, 2004 4:11 pm
Posts: 1771
Location: Server Elements
Hello JDK,

Your server uses an AMD SB820M for SATA support, so that shouldn't be a problem - the ahci driver handles that hardware out of the box.

The drive you are using however is a different story. Couple of things you may need to address if not done so already:

1. Make sure the drive is set as a SATA-2 and not as a SATA-3 drive. The chipset/driver combination will peak at SATA-2. Make sure the BIOS is set as SATA-2 (if such option is available to you) to enforce that. Data on the SB820M is here: http://support.amd.com/us/Embedded_TechDocs/47283.pdf

2. In my experience, the WD green drives need to be tweaked to disable the head-parking feature. Without doing so, when used as e server drive, a WD green will reach it's design limit within a matter of months. That's not at all safe for your data. Some more info on the subject is here: http://koitsu.wordpress.com/2012/05/30/ ... d-parking/

Anyway, I do use 2TB tweaked greens in my server and have been happy with the results for the better part of an year. I don't however have any SB820M based controllers to test, so I'm relying on research for answers. Can't find any issues other than the two items I mentioned above. Also, I am pretty sure that the partitioning code used by NASLite-2/M2 is sound. I have not had any problems deploying large format drives or RAID volumes once the hardware is properly set.

Hope that helps.

Tony.

PS - Looking at the HP specs, the MicroServer supports 2TB drives but doesn't mention 3TB drives. I doubt that's significant in this case, but who knows...
http://h18000.www1.hp.com/products/quic ... 16_na.html


Top
 Profile  
 
PostPosted: Mon May 13, 2013 12:56 pm 
Offline
Site Admin

Joined: Tue Jul 13, 2004 4:01 pm
Posts: 798
Location: ServerElements
As far as misaligned partitions, I'm really not seeing that from the filesystem details, we're using 4K blocks and starting the data partition on block 0

First block: 0
Block size: 4096


Quote:
I am pretty sure that the partitioning code used by NASLite-2/M2 is sound.


On that note, after looking at the filesystem details from your drives, there's a couple of really odd things.

Default mount options: user_xattr acl
Default directory hash: half_md4

Neither of those options was set by NASLite. ACL's aren't supported at all by the NL kernel.


Top
 Profile  
 
PostPosted: Mon May 13, 2013 5:25 pm 
Offline

Joined: Sat May 27, 2006 1:56 pm
Posts: 59
Tony wrote:
Hello JDK,

Your server uses an AMD SB820M for SATA support, so that shouldn't be a problem - the ahci driver handles that hardware out of the box.

The drive you are using however is a different story. Couple of things you may need to address if not done so already:

<snip>

Tony -- thanks for the detailed info. I did experiment with using jumpers to limit the drives to SATA-2. I'll check whether they are limited at the moment. And I did tweak the disks for the head parking issue (like many WD users I'm used to doing that as a matter of course now).

Ralph wrote:
As far as misaligned partitions, I'm really not seeing that from the filesystem details, we're using 4K blocks and starting the data partition on block 0
Quote:
I am pretty sure that the partitioning code used by NASLite-2/M2 is sound.
On that note, after looking at the filesystem details from your drives, there's a couple of really odd things.

Default mount options: user_xattr acl
Default directory hash: half_md4

Neither of those options was set by NASLite. ACL's aren't supported at all by the NL kernel.

Ralph -- the disk info I posted above is the data after I re-partitioned the disks with gdisk (i.e. I re-partitioned them outside of NASLite). All I can say is that, as I said in a previous post, transfer speeds jumped markedly after I did so. It may just be a particular hardware combination that is causing issues in my case.

If it's any help, this is what fdisk said about both of my disks prior to being re-partitioned in gdisk:
https://dl.dropboxusercontent.com/u/13895942/fdisk-partition-data.png

As I said, I'm no expert in these matters, but I have read elsewhere that for Advanced Format disks, the start parameter must be divisible by 4, which it was not for the 3TB disks, according to fdisk.

And this is what gdisk said (about both disks) prior to being re-partitioned (it claimed the GPT was corrupt):
https://dl.dropboxusercontent.com/u/13895942/GDisk-GPT-damaged.png

Sorry I did not post these screengrabs before, it slipped my mind.


Top
 Profile  
 
Display posts from previous:  Sort by  
Post new topic Reply to topic  [ 19 posts ]  Go to page Previous  1, 2

All times are UTC - 5 hours [ DST ]


Who is online

Users browsing this forum: No registered users and 3 guests


You cannot post new topics in this forum
You cannot reply to topics in this forum
You cannot edit your posts in this forum
You cannot delete your posts in this forum
You cannot post attachments in this forum

Search for:
Jump to:  
cron
Powered by phpBB® Forum Software © phpBB Group