1. Current Location: Home >  NAS >  The NAS system drive broke, so I reinstalled Feiniu, and 40,000 photos without missing a single one

The NAS system drive broke, so I reinstalled Feiniu, and 40,000 photos without missing a single one

If the NAS system disk breaks, does the system data still remain? Diagram illustrating the separation structure of the system disk and data disk, the six-step reinstallation process, and five things to redo after reinstallation

At 11 p.m., my wife's phone popped up with a 'Backup failed' message. I opened the Feiniu app and searched around for a long time. I pinged the NAS internal network address, but it didn't connect. That N100 had no screen, so I couldn't even see where it died.

First, to clarify: the system disk and data disk are separate entities

What

I should have figured out on the day of installation, I only truly realized on the night the system drive failed: NAS systems and data are stored separately. When installing Feiniu, it will ask you to select a drive to use as the system drive, where the system, packages, and account information are all stored; Your movies, photos, and downloads are all stored in a storage pool made up of separate data disks. The water from the east and west wells is diverted twice, so it does not encroach upon the river water.

Here's my setup: a 64GB old Kingston SSD as the system drive, taken from an obsolete computer years ago; A 4TB Cool Wolf is the main storage, with 46,000 photos and 186GB of all the phone photo backup libraries on it; There's also an old SSD dedicated to < a href="https://www.shunot.com/en/nas/993.html"> download disk, and all the QB work is handled by it.

So "system drive failure" and "data lost" are two different things. What truly determines the fate of your data is which disk is faulty, and whether your hands are steady when reloading.

Is the? . is used, .
situation data still there? What should we do
Only the system disk is broken, reinstalling the system, manually mounting the storage pool
If a damaged data diskcheck for redundant RAID 1/5 disk swaps and rebuilds. For Basic, rely on backups
If all system data is broken, dig up the backup. Taking the old path of 3-2-1

My family's time: the 64GB system drive just disappeared without a

second thought Tell me the order

of the checks that night, and you'll know them well. The app won't connect, so first check the router's backend device list—this N100 hasn't come for IP for several hours. Power out, wait half a minute, power on again, wait another twenty minutes, but it's still not in the device list. At this point, it's basically clear it's not a network issue, but the machine itself not starting.

The next day, I disassembled the computer, unplugged the 64GB system drive, and inserted it into the hard drive enclosure to connect the computer. CrystalDiskInfo pops up as soon as you open it, a warning pops up, SMART info can't be read across the entire page, and the health bar is simply empty. A single disk can't even hand over its own medical report; it's basically a controller or firmware issue, nothing to fix.

The most ironic thing is, I stared at that 4T Cool Wolf SMART for a whole year, memorized the red and yellow card indicators by heart, wrote an article > how to interpret

Full process of heavy equipment Feiniu: removing the data drive saved me

Before reinstalling, the first thing I did wasn't install the boot drive; I cut off the power and removed both data drives. This step is the most valuable experience in the entire process. Because the installation interface asks you to manually select the target drive. A row of drives is placed there, and if your hand shakes and you pick the wrong one, you click formatting. 46,000 photos are cremated on the spot—not even a god can save you. Physical disc removal is the dumbest yet safest foolproof feature—if the disc isn't in the machine, you have no choice.

The rest of the process is straightforward and straightforward. I wrote the USB drive into Feiniu's ISO with Rufus to make a boot drive, plugged it into the network cable to power on the monitor, and the brand new 128G SSD cost 89 yuan—make sure to install it. Installation takes about twenty minutes. This time, I'll turn on the system drive with it plugged in separately, confirm the system can enter, then turn it off and plug the two data drives back in.

. . . . . .
Key points of the steps
1. Power off and unplug all data drives to prevent errors and prevent selection errors
2Write the USB drive to ISO as a boot disk and write Rufus directly
3. Install on the new system drive and confirm the target disk capacity matches
4. After installation, power on separately to verify system access, then shut down
5Plug back into the data drive, power on, and enter storage space management
6. Manually mount the old storage pool. The new system will not recognize it automatically

The sixth step is the pitfall I had previously checked: the reinstalled new system does not automatically recognize the old storage pool; you have to enter storage management and manually mount the original hard drive and storage pool. All the data is on the drive, not a single layer is missing, but the system doesn't actively recognize it. If you don't click it, the file manager is completely empty. After uploading, I opened the photo catalog—46,000 photos, not a single one missing. That night, I finally slept soundly.

Reinstalling is not all the best: Five things I did again

The data is back, but don't think it's all right. The other side of the system and data separation is that the configurations on the system drive are cremated along with the old disk. Which items were revived with the data, and which needed to be redone—I'll first cross-check this account for you. Survived: All files in /vol1, Docker containers mapped to the data disk, and downloads. Lost: user accounts, shared directory permissions, container definitions, scheduled tasks, network settings.

So from the night of the renovation to the next day, I did five things. First, create an account. My parents reopened both read-only accounts, and the permission matrix for shared directories was reconfigured with the previous setup. Who can only view photos, who can write the download directory—check them one by one. Second, the Docker container is rebuilt by copying parameters. I've written about the old three things—port mapping, directory mounting, and environment variables—before. I followed the parameter copying routine one by one, and the qB download directory points to the original location of the data disk. I kept a record without any interruption.

Third, re-reattach the album directory and rerun the index. It takes over a day to scan 46,000 images with the N100, and the CPU buzzes all day—there's no way to avoid this. Fourth, reconfigure the disk water level and the SMART inspection script, and connect the alarm channel back to Bark. Otherwise, if it fails again next time, I'm the last one to know—last time I set up an alarm, which was a loss, backup silence failed for three nights. Fifth, learn your lesson this time: export the system configuration as a bin file in System Settings, save one copy each to the data drive and the cloud drive. Next time you reinstall, you won't have to manually do these five things.

Synology follows a different logic: the system is hidden in every disk

My cousin's second-hand four-bay Synology car is completely different from mine. DSM's system partitions mirror each disk, so even if you remove one drive, the system can still work. This is where it is more robust than single-system disk design. When the day DSM doesn't work, the reinstallation process is different: when you open the browser find.synology.com search for machines on the local network, the page will prompt "DSM can be installed." Choose a version that matches the original system and reinstall it. The installer only rewrites the system partition, not the data partition.

What really needs to be opened is the installation option. A pop-up will ask you to choose "Preserve system configuration and data files" or "Keep only files"—the former repairs the installation and retains all configuration data; The latter is equivalent to reinstalling, keeping the files but wiping out the configuration. If you choose the wrong step at this step, your account and package configuration will be explained. By the way, to clarify two things: this is called a reload, which is different from the usual system update that pops up. An update is a static upgrade, while a reinstall is a system layer overhaul from scratch; The guide for Black Synosys is even more unconventional, but that's a matter for another article.

Caught in a trap: the system is a mess, and you have to keep an eye on

it

After this incident, I put all three SMART drives at home for inspection, and the system drive is not exempt. Old SSDs have a hidden risk when used as system drives: they often fail without any warning before they fail, and mechanical drives at least give abnormal noises or red card indicators to slow things off, so the SSD controller can just leave at any moment. So that 64GB Kingston has served five years without a checkup, which is just my luck.

These two things have now become routines. System configuration exports the bin once a month, stored together with the data disk backup; The foundation for important data is still the old 3-2-1 rule: two local copies plus one remote copy, previously calculated the backup ledger. Because "reinstalling to protect data" has a premise you must remember—it only covers cases where the system drive fails. If the damage is the data drive itself, or if you accidentally formatted the drive during installation, how much you can recover depends on how reliable the backup is. If that happens, you'll have to < a href="https://www.shunot.com/en/nas/986.html"> try to recover by accidental deletion.

Here's a sequence: if you can't connect, first distinguish whether it's a network or a machine. For machine issues, disassemble and connect to the computer to test SMART; before reinstalling, always remove the data drive; after installation, manually mount the storage pool; finally, send back the account container alert and send a configuration bin. The first time I went through the full process, it took me half a night and half a day. Now I have configuration backups, so doing it again might take about an hour.

Read More


Copyright Notice Scan to read on mobile
All Rights Reserved: 《SHUNOT》 => 《The NAS system drive broke, so I reinstalled Feiniu, and 40,000 photos without missing a single one》
Article URL: https://www.shunot.com/en/nas/1146.html
Unless otherwise stated, all articles are original by 《SHUNOT》. Reposting is welcome! Please indicate the original URL when reposting, thank you.

Contact Us

Online Consultation: Click here to send me a message

WeChat ID: master_135

Scan to follow