<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom" xmlns:content="http://purl.org/rss/1.0/modules/content/"><channel><title>Synology on berezovskyi notes</title><link>https://blog.berezovskyi.dev/tags/synology/</link><description>Recent content in Synology on berezovskyi notes</description><generator>Hugo</generator><language>en-us</language><lastBuildDate>Sat, 16 May 2026 00:00:00 +0000</lastBuildDate><atom:link href="https://blog.berezovskyi.dev/tags/synology/index.xml" rel="self" type="application/rss+xml"/><item><title>Migrating a Seagate HDD to Native 4K Sectors on a Synology NAS</title><link>https://blog.berezovskyi.dev/notes/seagate-hdd-4k-sector-synology/</link><pubDate>Sat, 16 May 2026 00:00:00 +0000</pubDate><guid>https://blog.berezovskyi.dev/notes/seagate-hdd-4k-sector-synology/</guid><description>&lt;h2 id="the-goal"&gt;The Goal&lt;/h2&gt;
&lt;p&gt;I was adding a new Seagate Exos X20 (ST20000NM007D, 20 TB) to my Synology DS1821+
running DSM 7.2.2. These drives ship from the factory in 512e mode - they physically
use 4096-byte sectors but advertise 512-byte sectors for legacy OS compatibility. Since
my NAS and DSM support native 4K sectors, I converted the drive to 4Kn (native 4K)
before adding it to the storage pool.&lt;/p&gt;
&lt;h2 id="why-native-4k"&gt;Why Native 4K?&lt;/h2&gt;
&lt;p&gt;512e is a compatibility shim. The drive&amp;rsquo;s physical sectors are 4096 bytes, but when the
OS writes a 512-byte block, the drive must read the entire 4096-byte physical sector that
contains it, modify the relevant 512 bytes, and write the full sector back - a
read-modify-write cycle on every write. Native 4K eliminates this: every OS write maps
directly onto a physical sector.&lt;/p&gt;</description></item></channel></rss>