Running a NAS

Running a NAS, Part 9: NAS Problems Found Too Late

Hardware and setup problems NAS owners find after the build, from SMR drives and chip errata to dropping 2.5GbE ports and shared M.2 lanes, and how to check.

On this page 13 sections

Part 8, Keeping a NAS Healthy, covered the habits that catch trouble early, from SMART alerts and scrubs to the rules for replacing a drive. This last part of Running a NAS covers the faults those habits cannot catch, because they were bought into the box before its first boot. Each one below comes from a drive maker’s, chip vendor’s, board maker’s or project’s own notice, and each ends with a check you can run before paying, such as a model code lookup, a spec sheet line or a manual table.

Three NAS problems found after the build: overlapping drive tracks, a stopped chip clock and a switched-off SATA portThree numbered panels. First, the drive: five magnetic tracks that overlap like shingles. Second, the chip: a processor with pins on each side and a dashed clock face for the clock that may stop. Third, the slot: an M.2 slot joined to a dashed SATA port that is switched off.GUIDE / RUNNING A NAS, PART 9What owners find after the buildDRIVE · CHIP · SLOT01 THE DRIVETracks overlap02 THE CHIPClock may stop03 THE SLOTPort switched off

Shingled drives sold as NAS drives

In 2020, Western Digital said in a post about its Red NAS drives that the WD Red 2TB, 3TB, 4TB, and 6TB models used device-managed shingled magnetic recording (DMSMR), and that WD Red Plus was the new name for its drives based on conventional magnetic recording (CMR). Shingled magnetic recording (SMR) is the part that matters on a NAS, because of what a rebuild does to it. How a Hard Drive Works explains how the overlapping tracks make rewrites slow.

Shingled drives sold as NAS drives

Shingled WD Reds slow a ZFS resilver; Red Plus does not

Two panels compare tracks on a WD Red drive. The left panel draws five magnetic tracks that overlap like roof shingles, which is how the WD Red 2TB, 3TB, 4TB and 6TB drives with EFAX in the model code record data. Western Digital says a ZFS resilver is a long run of random writes that leaves these drives no idle time for housekeeping, so users report much lower performance, while a rebuild on a typical Synology or QNAP system runs about as fast as on conventional drives or slightly slower. The right panel draws five separate tracks, as on WD Red Plus and WD Red Pro, which are conventional magnetic recording drives that Western Digital says should be used with ZFS systems.01 EFAX · SHINGLEDWD Red 2TB, 3TB, 4TB, 6TBZFS resilver:much lower performanceSynology or QNAP rebuild:about as fast as CMR02 RED PLUS · CONVENTIONALWD Red Plus, WD Red ProZFS resilver:WD says use theseSynology or QNAP rebuild:the reference speedtracks overlaptracks apart
Figure 9.1 · Western Digital says EFAX Reds use device-managed shingled recording and that Red Plus and Red Pro are conventional, the type to use with ZFS. Source: Western Digital, 2020 post and support page; iXsystems notice.

In WD’s account, a ZFS resilver is a long run of random writes that leaves DMSMR drives no idle time for internal housekeeping, and users report much lower performance. On a typical Synology or QNAP (non-ZFS) platform, the same drives rebuild as well as CMR drives or take slightly longer. Part 2 covers how each pool layout rebuilds, and Part 8 puts a data-sheet floor under rebuild time.

iXsystems found one Red model faulty in its lab

iXsystems, the company behind TrueNAS, found in its lab that the 4TB WD40EFAX on firmware 82.00A82 could enter a faulty state under heavy writes, including a resilver, and disqualified it from its products. Past that one model, the TrueNAS hardware guide is blunt. Device-managed and host-aware SMR drives function poorly with TrueNAS, so expect degraded writes and longer, less reliable resilvers, and host-managed SMR is not supported at all.

What Toshiba, Seagate and Western Digital said

Other makers answered the same question differently. Toshiba said in April 2020 that its N300 NAS drive does not use SMR, and disclosed that its P300, DT02, and DT02-V desktop and surveillance drives in 4TB and 6TB do. Seagate’s current IronWolf drives use CMR, and Blocks & Files reported Seagate’s April statement that no IronWolf or IronWolf Pro drive uses SMR. Western Digital’s support page says WD Red Plus and WD Red Pro are CMR drives and should be used with ZFS systems.

Reading a model number

Check the exact model number against the maker’s own CMR and SMR list before buying, since a family name does not settle it. In the WD Red line, EFAX in the model code marks the DMSMR drives in 2TB, 3TB, 4TB, and 6TB, and EFRX marks the earlier CMR drives of the same sizes. For any pool that will resilver, the better buy is a drive its maker lists as CMR. Each pick in the NAS tier of Best HDDs shows its recording type on its card.

A clock fault in Atom C2000 boards

Erratum AVR54 in Intel’s Atom C2000 specification update is a clock problem. Its low pin count (LPC) clock outputs may stop functioning, and the system can then no longer boot. Stepping B0 has it and stepping C0 fixes it. Intel offers a workaround at the platform level, which means a board redesign and not a software fix.

A clock fault in Atom C2000 boards

One stopped clock can keep an Atom C2000 NAS from booting

A two-row diagram. The top row is the fault as a chain of three boxes joined by arrows: an Atom C2000 in stepping B0, whose low pin count clock outputs may stop working, after which the system can no longer boot. This is Intel erratum AVR54. The row below shows what answered it, one box under each link. Stepping C0 has the fix. Intel's workaround is a platform-level change, which means a board redesign and not a software fix. Synology extended the warranty by one year on six models built on the Atom C2538. A wide box at the bottom gives the check for a used unit: ask the seller for the CPU model and the build date.01 THE FAULTAtom C2000stepping B0LPC clock outputsmay stop workingThe system canno longer boot02 WHAT ANSWERED ITStepping C0has the fixIntel workaround:a board redesignSynology: warrantyextended one yearUsed unit: ask the seller forthe CPU model and the build datethe faultthe answerthe check
Figure 9.2 · Intel lists erratum AVR54 in stepping B0 and fixed in C0, and Synology extended the warranty on six models built on the part. Source: Intel Atom C2000 specification update; Synology notice, February 2017.

Synology’s notice from February 2017 extended the warranty by one year on six models: DS415+, DS1515+, DS1815+, DS2415+, RS815(RP)+, and RS2416(RP)+. The Italian-language copy of the same notice names the Atom C2538 as the chip, which Intel’s update also lists. The company called the erratum rare and not known to cause data loss or safety hazards, and says improvements suggested by the component maker have been in current and future models since February 2017.

For a used unit, ask the seller for the CPU model and the build date. Synology draws its line at February 2017, and Intel puts the fix in stepping C0.

When a 2.5GbE port drops to a crawl

Intel’s specification update for the I225 documents that the v1 silicon supports a gap between packets down to 8 bytes, but not down to 5 bytes in 2.5Gbps operation, which is the minimum the IEEE standard requires. A link that hits it can fall from 2.5Gbps to below 1Gbps, and with some link partners to 1 to 10Mbps.

When a 2.5GbE port drops to a crawl

The I225 v1 cannot space packets as tightly as 2.5Gbps needs

Two strips of packets drawn to one scale compare the gap between packets. The top strip shows the 5-byte gap that the IEEE standard requires at 2.5Gbps. The bottom strip shows the 8-byte gap that is the tightest the I225 v1 silicon supports, so its packets sit visibly farther apart. Below the strips, three boxes follow. A link that hits the limit can fall from 2.5Gbps to below 1Gbps. Setting the link speed to 1Gbps works around it. Intel's support article for the I225-V prescribes updating the controller's non-volatile memory and the driver, with the NVM coming from the motherboard maker.01 THE IEEE MINIMUM AT 2.5GBPS5 bytes02 WHAT I225 V1 CAN DO8 bytesLink can fall from2.5Gbps to below 1GbpsWorkaround: set thelink speed to 1GbpsFix: update the NVMand driverpacketgapthe faultthe answer
Figure 9.3 · Gaps drawn to one scale: the standard minimum is 5 bytes and the v1 silicon stops at 8, so some links fall below 1Gbps. Source: Intel I225 specification update 1.2; Intel I225-V support article.

Setting the link speed in the driver to 1Gbps works around it, and later drivers and NVM reset the link to 1Gbps automatically when drops occur. For the I225-V, a separate Intel support article names connection drops and an undetected cable among the symptoms, and prescribes an update of the controller’s non-volatile memory (NVM) and driver. Intel points owners to the motherboard maker for the NVM.

Before buying, find the controller chip on the board’s or NAS’s spec sheet, not only the port speed, and see whether its maker publishes an NVM update. Part 5 covers what each link speed can carry and how to measure it.

Port multipliers, USB and hardware RAID

OpenZFS’s hardware documentation calls support for SATA port multipliers inconsistent across platforms. Linux drivers generally support them, Illumos drivers generally do not, and FreeBSD sits in between. It also tells readers not to expect SAS controllers to be compatible with them. USB hard drives and adapters get a harsher verdict: they have problems with sector size reporting, SMART passthrough, and setting error recovery control (ERC), and should be considered unreliable. TrueNAS’s hardware guide advises the same for its systems and says to avoid USB-connected disks for primary storage. Part 8 covers why SMART passthrough matters, since the SMART attributes are how a NAS watches a drive.

Port multipliers, USB and hardware RAID

Only a plain SATA or IT-mode path passes the pool-drive check

A decision tree for how a pool drive reaches the NAS. The top box asks how the drive is attached, with four branches below it. A cable to a SATA port is fine if the board keeps that port when its RAID function is off. A SAS card or hardware RAID is acceptable only with IT or Target Mode firmware that disables the RAID function. A SATA port multiplier has inconsistent support: Linux drivers generally support it, Illumos drivers generally do not, FreeBSD sits between, and SAS controllers should not be expected to work with it. A USB drive or adapter has problems with sector size reporting, SMART passthrough and setting error recovery control, and is considered unreliable. The first two branches pass the check and the last two fail it.How does the pooldrive reach the NAS?Cable to aSATA portFine, if theboard keeps itSAS card orhardware RAIDIT or TargetMode firmwareSATA portmultiplierSupport differsby platformUSB driveor adapterConsideredunreliablepassesfails or varies
Figure 9.4 · OpenZFS and TrueNAS documentation rate four attachment paths for pool drives, and two of them fail. Source: OpenZFS hardware documentation; TrueNAS hardware guide.

Hardware RAID is the third trap. TrueNAS’s hardware guide says to flash Broadcom SAS controllers with IT or Target Mode firmware, which disables the optional RAID function, and not to use a motherboard’s hardware RAID at all. Disabling it in the BIOS might remove some SATA functionality, depending on the board.

Before buying a card, confirm that it can run in IT mode, and before buying a board, find out which SATA ports survive with its RAID function off. A USB enclosure for pool drives fails the check on the first line of both documents.

M.2 slots that give something up

Board manuals state the trade in a table. The ASUS PRIME B560M-A manual says its M.2_2 slot shares bandwidth with SATA6G_2, which is disabled when the slot runs in SATA mode. On the ASRock B760M-H/M.2, SATA3_3 is disabled if M2_2 holds a SATA-type M.2 device. A NAS built on either board gives up a drive port when the cache slot holds a SATA-type M.2 SSD, and Part 4 covers what that SSD is for.

M.2 slots that give something up

A shared M.2 slot costs a SATA port; a flash NAS gives one lane each

Two panels. The left panel shows a second M.2 slot linked to a SATA port that is drawn dashed because it goes off. The ASUS PRIME B560M-A manual says its M.2_2 slot shares bandwidth with SATA6G_2, which is disabled when the slot runs in SATA mode, and the ASRock B760M-H/M.2 manual says SATA3_3 is disabled if M2_2 holds a SATA-type M.2 device. The right panel draws the twelve M.2 slots of the ASUSTOR Flashstor 12 Pro in a grid of four by three, each marked x1. The datasheet gives the slot count and the spec page gives the interface as PCIe 3.0 x1, two separate lines to read.01 A SLOT COSTS A PORTASUS PRIME B560M-A:SATA6G_2 is disabledASRock B760M-H/M.2:SATA3_3 is disabled02 ONE LANE PER SLOTDatasheet:12 M.2 PCIe 3.0 slotsSpec page:M.2 interface PCIe 3.0 x1M.2_2 slotSATA-type SSDSATA portswitched offx1x1x1x1x1x1x1x1x1x1x1x1M.2 slotport that goes off
Figure 9.5 · Two boards switch off a SATA port when their second M.2 slot holds a SATA-type SSD, and the Flashstor 12 Pro lists twelve slots at PCIe 3.0 x1. Source: ASUS and ASRock board manuals; ASUSTOR Flashstor 12 Pro datasheet and spec page.

Dedicated flash NAS units trade differently. ASUSTOR’s Flashstor 12 Pro datasheet describes 12 M.2 PCIe 3.0 SSD slots, and the spec page lists the M.2 PCIe interface as PCIe 3.0 x1. Slot count and lane width are separate lines in the spec, so read both. Part 4 sets the all-M.2 boxes side by side.

The check is the shared-bandwidth table in a board’s manual, and the M.2 PCIe interface line in a NAS’s spec sheet.

Cache SSDs that wear out

A cache or log SSD takes writes all day, so it is the drive in a NAS most likely to reach its endurance rating. TrueNAS’s SLOG documentation calls disk latency and write endurance the primary concerns for a ZFS write log device, and its L2ARC documentation says that from OpenZFS 2.4, a drive-writes-per-day budget limits writes to the ZFS read cache, with a default of 1.

Cache SSDs that wear out

Both ZFS cache SSDs take heavy writes and have an endurance limit

A block diagram with the storage pool in the middle and a cache SSD on each side, each joined to the pool by a link. The left SSD is the write log, called a SLOG, and under it a note says TrueNAS gives disk latency and write endurance as the primary concerns. The right SSD is the L2ARC read cache, and under it a note says that from OpenZFS 2.4 a drive-writes-per-day budget limits its writes, with a default of 1. A wide box at the bottom gives the check: look up the endurance rating on the data sheet and the workload the maker used to calculate it.Storage poolSLOG SSDthe write logL2ARC SSDthe read cachePrimary concerns:latency andwrite enduranceOpenZFS 2.4 writebudget: 1 drivewrite per dayLook up the endurance rating on the data sheet,and the workload the maker used to calculate itcache SSDlimitlink
Figure 9.6 · TrueNAS names latency and write endurance as the main concerns for a write log, and OpenZFS 2.4 budgets L2ARC writes at 1 drive write per day by default. Source: TrueNAS SLOG and L2ARC documentation.

Look up the endurance rating on the data sheet, and the workload the maker used to calculate it. Part 4 explains the ratings and what each SSD job asks of a drive.

What error-correcting memory buys

OpenZFS’s hardware documentation says error-correcting code (ECC) memory is highly recommended, because no filesystem technique protects against bit flips. Its FAQ is more measured. ECC is strongly recommended for enterprise use, while for home users the added safety might not justify the cost, and the choice is left to the user.

What error-correcting memory buys

No filesystem technique guards RAM, which is what ECC covers

A three-box path for data in a ZFS NAS: data in RAM, the ZFS filesystem, and the pool drives. The RAM box shows a row of memory cells with one hollow cell for a flipped bit. A bracket under the RAM box marks the part that ECC memory covers, and the filesystem box is dashed because OpenZFS says no filesystem technique protects against bit flips. Three boxes below give the stances. The OpenZFS hardware documentation says ECC is highly recommended. The OpenZFS FAQ says home users might not find the added safety worth the cost. The TrueNAS hardware guide says many TrueNAS systems run every day without ECC. A last box says to test all new RAM before use, ECC or not, since RAM failures usually occur in the first three months.01 WHERE A BIT FLIP LANDSData in RAMZFS filesystemPool drivesECC covers this part02 WHAT THE DOCS SAYOpenZFS docs:highly recommendedOpenZFS FAQ:home users weigh itTrueNAS guide:many run without itTest all new RAM before use, ECC or not:RAM failures usually occur in the first 3 monthsmemoryno protection hereECCflipped bit
Figure 9.7 · OpenZFS says no filesystem technique protects against bit flips, and its FAQ leaves ECC to home users to weigh against the cost. Source: OpenZFS hardware documentation and FAQ; TrueNAS hardware guide.

The TrueNAS hardware guide says many TrueNAS systems operate every day without ECC RAM, though most of its users strongly recommend it. It adds that RAM failures usually occur in the first 3 months, so all RAM should be tested before deployment, ECC or not. Look up ECC support on both the CPU’s and the board’s spec pages before choosing memory, and decide with the cost in view. Whatever you choose, run the memory test on the new RAM.

Compatibility lists and the day support ends

Drives on Synology’s list are tested with simulated abnormal shutdowns, extreme temperatures, functional stress, and power cycling, according to its drive compatibility policy. Part 1 covers how that list became a recommendation on 2025 models.

Compatibility lists and the day support ends

A drive list covers tested drives, and End of Life ends updates

Two lanes, each a left-to-right pair of boxes. The first lane is the drive list. A drive on Synology's compatibility list is tested with simulated abnormal shutdowns, extreme temperatures, functional stress and power cycling, and that testing covers the listed drives alone, so a drive off the list is not covered by it; on 2025 Plus models Synology allows third-party drives but still recommends listed ones. The second lane is a model's support life. While a model is supported it gets firmware, software and security updates. At End of Life, those future updates are discontinued, which matters more for a used unit, so the status page is the check before paying.01 THE DRIVE LISTListed drive:shutdown, heat, stressand power-cycle testsDrive off the list:not covered by thattesting02 THE SUPPORT STATUSSupported model:firmware, softwareand security updatesEnd of Life:future updatesare discontinuedcoverednot covered
Figure 9.8 · Synology tests the drives on its list, and its End of Life status means no further firmware, software or security updates. Source: Synology drive compatibility policy and product support status page.

A model’s last day of updates matters more for a used unit. Synology’s product support status page defines End of Life as future firmware, software, and security updates being discontinued. Check any model, new or used, against that page before paying. Part 1 compares how each maker words its support levels.

Full bays and vibration

Western Digital’s WD Red Plus datasheet rates the drive for RAID-optimized NAS systems with up to 8 bays.

Full bays and vibration

A chassis with more bays than the drive's rating is the gap

Two chassis drawn as grids of drive bays. The left chassis has eight filled bays, the most that Western Digital rates the WD Red Plus for in a RAID-optimized NAS. The right chassis draws the same eight filled bays plus a further row of dashed bays, a chassis with more bays than the rating. The datasheet says drives that are not properly balanced may cause excessive vibration and noise in multi-drive systems, which could reduce drive life and degrade performance, so the bay count of the chassis is checked against the rating before buying.01 WITHIN THE RATINGDatasheet rating:up to 8 baysRated for RAID-optimizedNAS systems02 PAST THE RATINGChassis with more baysthan the ratingUnbalanced drives mayadd vibration and noiserated baybay past the rating
Figure 9.9 · Western Digital rates the Red Plus for up to 8 bays and warns that unbalanced drives can shorten drive life and degrade performance. Source: Western Digital WD Red Plus datasheet.

The same sheet says drives that are not properly balanced may cause excessive vibration and noise in multi-drive systems, which could reduce drive life and degrade performance. Compare a drive’s rated bay count with the chassis before buying. A chassis with more bays than the rating is the gap.

Where to look first

Where to look first

Each problem can be looked up in one of four places

A lookup map with six problems in a left column joined by straight links to four places to look in a right column. An SMR drive sold as a NAS drive is found in the model code, such as EFAX. A 2.5GbE controller bug, an M.2 slot's lane width and a bay count past a drive's rating are all found in one spec sheet or datasheet line. An M.2 slot that shares a port with a SATA port is found in the board manual's shared-bandwidth table. A model whose support has ended is found on the maker's support status page.01 THE PROBLEM02 WHERE TO LOOKSMR drive sold as NAS2.5GbE controller bugM.2 slot lane widthBay count past ratingM.2 slot shares a portSupport endsModel codeSpec sheet ordatasheet lineManual tableStatus pageproblemplace to looklookup
Figure 9.10 · A model code, a spec sheet or datasheet line, a manual table and a status page answer every check on this page. Source: the maker documents cited in Parts 1 to 9 of Running a NAS.

That ends Running a NAS. Every part is listed on the series hub, and Part 1, NAS Operating Systems Compared is the place to start again with a new build.

Sources

Primary is the original paper, standard or datasheet. Secondary is a review, a vendor summary or a news report. Measured is my own test data.

Show all 22 sources, 21 primary