Orbi WiFi 7 RBE973
Reply

4k sector support.

kllngtme
Aspirant

4k sector support.

Due to having both HD's fail in my DUO at the same time, I have replaced the drives with new ones, 2 2TB Seagate Barracuda XT ST32000641AS. They are on the HCL so I know they work with the readynas. From what I have looked at online, it shows these drives do support the new 4k sector size. I popped 1 HD in, performed a factory reset, and then once it was accessible via frontview I popped in the 2nd HD. It's still in the middle of the drive resync but I wanted to check the sector issue and see if it's still using 512k sectors..

From looking at the partition.log file, it shows the following, which I'm assuming means that it's using 512 sectors still... Is there anything else I need to do for this to use 4k sectors?

From partition.log:

Disk /dev/hdc: 2000.3 GB, 2000388448256 bytes
255 heads, 63 sectors/track, 243200 cylinders, total 3907008688 sectors
Units = sectors of 1 * 512 = 512 bytes
Disk identifier: 0x00000000

Device Boot Start End Blocks Id System
/dev/hdc1 32 4096031 2048000 83 Linux
Partition 1 does not end on cylinder boundary.
/dev/hdc2 4096032 4608031 256000 82 Linux swap / Solaris
Partition 2 does not end on cylinder boundary.
/dev/hdc3 4608032 3906992335 1951192152 5 Extended
/dev/hdc5 4608040 3906992335 1951192148 8e Linux LVM

Disk /dev/hde: 2000.3 GB, 2000388448256 bytes
255 heads, 63 sectors/track, 243200 cylinders, total 3907008688 sectors
Units = sectors of 1 * 512 = 512 bytes
Disk identifier: 0x00000000
Message 1 of 11
fbmachines
Guide

4k sector support.

It is configured for 4k sectors.

The partition start sector (in this case 32) will be divisible by 8 if it's setup for 4k sectors.
Message 2 of 11
zamboni
Aspirant

Re: 4k sector support.

Wow - how cryptic. It would be cool if FrontView actually said "512b sector" or "4096b sector" or something similar. That way, one could manually remove & re-add each disc individually and get easy confirmation the drive (and when done, the entire array) is upgraded to 4k sectors.
Message 3 of 11
mdgm-ntgr
NETGEAR Employee Retired

Re: 4k sector support.

On Sparc ReadyNAS (e.g. Duo), a factory reset after upgrading to 4.1.7 is needed to get 4k sector alignment. Only having new disks in the NAS is one way to do a factory reset.

For x86 where you can replace the disks one by one to get 4k sector alignment there may be some point to what you're suggesting.
Message 4 of 11
Retired_Member
Not applicable

Re: 4k sector support.

mdgm wrote:
On Sparc ReadyNAS (e.g. Duo), a factory reset after upgrading to 4.1.7 is needed to get 4k sector alignment. Only having new disks in the NAS is one way to do a factory reset.



Do I need to do a factory reset after I changed the discs? Or before?

Is there any lost of data?
Message 5 of 11
mdgm-ntgr
NETGEAR Employee Retired

Re: 4k sector support.

Either will work. Factory reset will wipe the disks so do need to backup first.

Recommended procedure suggested here: Why you might want to factory reset a Sparc ReadyNAS
Message 6 of 11
Retired_Member
Not applicable

Re: 4k sector support.

I tried to figure out which size my sector is. Here is extraction from partition.log:

Device Boot Start End Blocks Id System
/dev/hdc1 2 4096001 2048000 83 Linux
Partition 1 does not end on cylinder boundary.
/dev/hdc2 4096002 4608001 256000 82 Linux swap / Solaris
Partition 2 does not end on cylinder boundary.
/dev/hdc3 4608002 1953108615 974250307 5 Extended
/dev/hdc5 4608003 976736305 486064151+ 8e Linux LVM
/dev/hdc6 976736307 1953092230 488177962 8e Linux LVM
Message 7 of 11
StephenB
Guru

Re: 4k sector support.

bruse wrote:
I tried to figure out which size my sector is. Here is extraction from partition.log...
Look for "block size" in volume.log - 4096 is what it should be for 4K.
Message 8 of 11
Retired_Member
Not applicable

Re: 4k sector support.

StephenB wrote:
bruse wrote:
I tried to figure out which size my sector is. Here is extraction from partition.log...
Look for "block size" in volume.log - 4096 is what it should be for 4K.

OK:
Block size: 16384
Message 9 of 11
PapaBear1
Apprentice

Re: 4k sector support.

No, No, No. The block size has nothing to do with the disk sector. Originally the Sparc based ReadyNAS had 4K BLOCK size under RAIDiator versions prior to 4.x. But that limited the max size of the volume. As larger and larger drives started coming to the market, they increased the BLOCK size in RAIDiator to 16K. Any factory default after version 4.0 has the 16K BLOCK size. This has nothing to do with SECTOR size. I believe that the 16K block size is unique to the sparc based ReadyNAS units as well.

As hard drives started getting larger and larger, they also started running into limitations so beginning a little over a year ago, they started using the 4K SECTOR size rather than the traditional 512K SECTOR size that had been used since the first hard drive was marketed.

BLOCK size - function of OS (RAIDiator)

SECTOR size - function of HDD structure.
Message 10 of 11
StephenB
Guru

Re: 4k sector support.

PapaBear wrote:
No, No, No. The block size has nothing to do with the disk sector. Originally the Sparc based ReadyNAS had 4K BLOCK size under RAIDiator versions prior to 4.x. But that limited the max size of the volume. As larger and larger drives started coming to the market, they increased the BLOCK size in RAIDiator to 16K. Any factory default after version 4.0 has the 16K BLOCK size. This has nothing to do with SECTOR size. I believe that the 16K block size is unique to the sparc based ReadyNAS units as well.

As hard drives started getting larger and larger, they also started running into limitations so beginning a little over a year ago, they started using the 4K SECTOR size rather than the traditional 512K SECTOR size that had been used since the first hard drive was marketed.

BLOCK size - function of OS (RAIDiator)

SECTOR size - function of HDD structure.
Sorry for confusing the issue - clearly I misunderstood the post here: viewtopic.php?f=66&t=61193&p=344748#p344748

Anyway, checking sector alignment on DUO and NV+ V1 is found here: http://www.rnasguide.com/2011/06/22/why ... -readynas/

You need to check the starting sector of each partition, and see if is divisible by 8. In your partition.log that does not seem to be the case.
Message 11 of 11
Top Contributors
Discussion stats
  • 10 replies
  • 2667 views
  • 0 kudos
  • 7 in conversation
Announcements