My cousin stuffed a 4TB block into the NAS storage pool, but the available capacity didn't increase by one byte

My cousin's four-bay Synology machine, after last year after a round of digging around and replacing it with a broken unit, had two 4T Cool Wolf set mirror arrays in the cabinet, while the other two bays were empty. Not long ago, Movie Kuga Photos was about to use up the 4TB available capacity, so he placed an order for a 4TB block. When it arrived, he slotted it into the empty spot. Synology clicked step by step in the backend and got a prompt for expansion successful—the available capacity was still 4TB, not a single byte had increased. His exact message to me was, "Did I buy a fake list?"
First, clarify: just because a space is available doesn't mean adding space means you have capacity
The drive doesn't take effect as soon as you plug it in. For Synology's types that can add to old pools, the official documentation clearly states: JBOD, RAID 5, RAID 6, SHR with at least two disks—adding to the pool increases capacity. RAID 1 is also on the list of add-ons, but it comes with a terrible message—adding hard drives to RAID 1 does not increase capacity.
This is
exactly what my cousin stepped on. The two 4TB drives are RAID 1, meaning the two drives are mirrored together, and the available capacity is always equal to one drive. Add a third 4TB drive, and Synology accepts it all, making the three drives into three-channel mutual backup—safety is indeed higher, if two disks fail, no data loss, and usable capacity remains 4TB. I spent over 400 yuan on a "more stable" device, which is like spending money at all for a home movie storage machine.
The
root of this whole thing was on the day the PC was installed. If you had built the pool according to the beginner's recommended SHR deck, two 4T blocks would have been 4T, and now adding a third 4T would instantly increase to 8T, doubling the amount. How to choose between SHR and RAID 1, how to calculate mixed-capacity drives, I once calculated with 4TB and 8TB, so I won't repeat here. By the way, don't rush to pay when the full < is full. > a href="https://www.shunot.com/en/nas/993.html" I cleared my 4TB Feiniu a full circle. The snapshots, recycle bin, and Docker logs combined yielded over 400GB. This cleaning step is zero-cost.
Which pools can add and how much after adding: a table to understand
First, lay the account on the table. Add one block of 4T to the three common pools, and what happens if you put them in
?| adding a 4T | before the market | ||
|---|---|---|---|
| RAID 1 (two 4T | ) chips? Can youuse 4T | or 4T | for free? Only an extra mirror |
| added SHR (three 4TB modules) | can use 8TB | ,12TB | can be used for true expansion |
| RAID 5 (three 4TB modules) | can use 8TB | ,12TB | can be used for true expansion |
| Basic (single 4TB) | can use 4TB | Creating a separate pool | does not count as expansion, but as a new listing |
The pattern is simple: single validation pools (SHR, RAID 5) add to the market, and the increase is the share of redundancy removed; Pure mirror pools (RAID 1) are adding up, increasing redundancy shares, while capacity remains stagnant. Back then, when I < a href="https://www.shunot.com/en/nas/822.html" > chose RAID, how I fit the line directly decided whether today's buying was just a bargain or a wasted effort.
There's another rule that's easy to overlook: for new accounts added in the SHR pool, the capacity must be greater than or equal to the smallest part of the pool. For example, if the pool is 2T, 2T, or 4T SHR, if you add an 8T chunk, the extra portion won't be used. So don't be stingy with extra bets—buy according to the largest piece in the pool, or you'll waste the price difference. My cousin was lucky; both of his pools were 4T, and the new one he bought was also 4T, so at least he didn't get caught up in this one.
Synology buying is done in two steps; after clicking the first step, don't rush to close the page
When helping him check, I went through the official documentation and tutorials. The complete process for adding Synology 7.x to the pool is actually two parts:
The first paragraph is expanding the storage pool. In Storage Manager, select Lao Chi, click the three dots in the upper right corner, choose 'Add Hard Drive,' check the box for the newly inserted drive, and confirm. After this step, the pool grows, but you still don't see the new capacity in the file system—many people get confused at this point, thinking they've failed again.
Section two: Expand storage space. After the pool is expanded, the storage (volumes) is still stuck at the old size, so you need to expand the storage space again to push the file system to the new pool size, and only then will the capacity truly fall into your hands. Sometimes Synology will proactively pop up prompts to guide you to step two, sometimes it doesn't. Pay attention to whether the storage space section still shows the old capacity.
Time must be anticipated. Adding a new account isn't just about formatting the new account; the validation data for the entire pool must be rearranged across the board, with both old and new accounts written together. My cousin's three-panel 4TB mirror array can't get on the right path. I used Synology users' records for reference: SHR with three drives plus one 4TB usually takes over ten to twenty hours to reboot, which is on the same scale as rebuilding a whole drive. During this time, the machine worked as usual, but the speed was noticeably weaker. SMB copying files and Jellyfin database scanning slowed down by a beat.
The rulesfor the day of expansion: wait if you can, don't add fuel to the fire
During the rescheduled days, there were a few things I specifically reminded him to remember.
First, don't run big projects. Reorder for full-disk read/write. At this point, arrange a full backup or a few TB download tasks, with both sides competing for disk, dragging rescheduling from one day to three days. My lesson is that backup tasks and hard drive rework are delayed, < a href="https://www.shunot.com/en/nas/836.html"> the article specifically records this in the article about detecting the stolen drive.
Second, don't cut off the power. During rescheduling, redundancy remains, and a broken drive doesn't lose data, but if the power suddenly goes out, you might have to redo the rearrangement from scratch, wasting more than ten hours. If Synology machines don't have UPS, make up for this lesson the night before expansion. I caught the time it tripped, and the RAID rebuilt to 62% and disconnected. I never wanted to go back to that feeling.
Third, don't recklessly add scenes halfway. Halfway through the rearrangement, I found another seat still empty, so I thought I might as well add two at once—no, I'll add one at a time, and after the run is stable, I'll add the next. It's the same as changing one block at a time for expansion.
Feiniu's approach is different: there's no "Add Hard Drive" button
My own N100 dual-drive Feiniu has a different choice when fully loaded than Synology users. In Feiniu's graphical interface storage management, the official expansion method is to replace the large drive one by one—remove the small one, plug in the large disk, wait for the array to be repaired, then replace the next drive, and manually expand the capacity once after all replacements. Synology's approach of "directly adding to the old pond" is two different approaches.
If you want to add drives to old pools on Feiniu, it's not impossible. You can add mdadm drives in the command line, expand LVM, and support the file system—this whole setup can be done, and there are complete tutorials available online. But let me leave it this way: command line expansion has too low tolerance for error. If you mistype one drive letter, it's a whole different story. Regular players shouldn't touch this path. In the feature reconciliation article between Feiniu and Synology, I mentioned that Feiniu really still has a breath to be sung in array online scaling.
So for Feiniu users with available slots, the most practical method is actually the second method: don't move the old storage, hang the new as a separate storage space, move the movie library over, and focus on photos and documents. Zero risk, done in ten minutes, but the cost is that the two pools are managed separately, and shared folders have to be moved over.
Ifthe tray is full but the budget is tight: try the three backup options in order
If all the slots are full, or like RAID 1, where adding pools is pointless, these are the ones you can go down
to:Clean up first, then talk money. There are plenty of snapshots with dozens of gigabytes, uncleaned recycle bins, and Docker logs piled up for years. following those five steps can most likely squeeze out a month or so buffer.
Then consider swapping each unit for the main market. Replace all 4T units with 8T units, double available capacity, follow the process the disc replacement and moving article, only replace one piece at a time, fix it and then replace the next. SHR's rules were also written in 928. This path is slow, but every old property can be resold for resale after retirement. Wipe the data clean before selling second-hand — don't skip that step.
If I really don't want to run the storage pool, I attach a portable hard drive to the USB port as a storage drive, store some "no worries if lost" cold data, I've been running it for three months, so just know the power supply and format issues in advance. As for the total lack of bays and the old machine, that's a signal to replace the machine. How the accounts for the two and four bays were calculated back then is now recalculated.
| In your situation | ,which option should you prioritize |
|---|---|
| market is empty, the pool is SHR or RAID 5 | ,then add the pool directly. Two-step expansion, and the capacity really increases |
| If the market is empty, the pool is RAID 1 or Basic | ,don't add more. Put it in a new independent space, or switch to the main market |
| When the tray is fully filled | ,you can trade for the larger board one block at a time. |
| Feiniu users | can set up independent new spaces for the most stable setup, but swapping each block is secondary. Be cautious when executing commands |
My cousin's 4TB was never refunded, so it was installed as a standalone download drive. The movie library was moved over, and Lao Chi freed up over 300GB to catch his breath. He said that when the movie library is full again next year, he will follow the path of switching the market. Alright, the process is all over here anyway.
