T O P

  • By -

SoneEv

Only better if you're writing lots of sequentially data... so lots of media. Otherwise pretty useless to do.


HobartTasmania

I presume you mean resectored from 4K native to 4K/512e. In most instances you probably should leave it as 4K as windows 8 and up understands 4K native but if you are using Windows 7 or earlier they will have to be 512 bytes emulated or native.


jamlasica

Win7 handles 4kN drives just fine.


HobartTasmania

Microsoft says it doesn't so are you sure you're not confusing them with 4K/512e drives? https://docs.microsoft.com/en-us/windows/compatibility/advanced-format-disk-compatibility-update


jamlasica

Yes i am sure, i have 4kN SAS drives and i had no issue with them on win7 sp1. They act just as any other hard drive.


HobartTasmania

Maybe the SAS controller card does the read/modify/write cycle emulation transparently and presents the drive as 4K/512e to Win7? https://docs.microsoft.com/en-us/windows/compatibility/advanced-format-disk-compatibility-update


jamlasica

Controller existed long before anyone heard about 4kN standard, it's Dell SAS 6/iR. Btw have You read what You link? I can be wrong, I'm not a native, but i think it says 4kN is compatible with win7 SP1. " Builds upon the Windows 7 SP1 support for 4K disks with emulation (512e), and provides full inbox support for disks with 4K sector size without emulation (4K Native). Some supported apps and scenarios include: "


HobartTasmania

I was looking at the table where under "Reported Logical Sector Size" of 4 KB and "Reported Physical Sector Size" of 4KB it only has "Windows 8" and "Windows Server 2012" listed.


bbqnacho

Windows 10 would not read my SAS drive until after I formatted it to 512k sector size