Synology Soft Reset
Abbie Buesing
There are two ways to reset your Synology NAS running DSM 7.0, including a soft and hard reset. Regardless of which method you use, your data will not be wiped, though it's highly recommended to make a backup of everything, just in case.
Working on your NAS enclosure and need some additional drives? We've rounded up some excellent NAS-class drives, including Seagate IronWolf and Western Digital Red. We'd recommend having at least two drives installed on an enclosure with more than a single drive bay, which allows for the creation of a RAID array for enhanced data redundancy.
Rich Edmonds was formerly a Senior Editor of PC hardware at Windows Central, covering everything related to PC components and NAS. He's been involved in technology for more than a decade and knows a thing or two about the magic inside a PC chassis. You can follow him on Twitter at @RichEdmonds."}), " -0-10/js/authorBio.js"); } else console.error('%c FTE ','background: #9306F9; color: #ffffff','no lazy slice hydration function available'); Rich EdmondsSocial Links NavigationSenior Editor, PC BuildRich Edmonds was formerly a Senior Editor of PC hardware at Windows Central, covering everything related to PC components and NAS. He's been involved in technology for more than a decade and knows a thing or two about the magic inside a PC chassis. You can follow him on Twitter at @RichEdmonds.
Are you able to access the management interface? This will hopefully tell you more about what is happening. If you cannot access it, there are a series of steps to take to reset the interface, but not affect any data on the disks. This should be in your documentation, but you can also find it here: -my/DSM/tutorial/What_can_I_do_to_troubleshoot_NAS_connection_problems
So I can't access the management interface neither by using the IP, nor by using Synology Assistant (NAS not detected). Is this situation still possible if the NAS is trying to rebuild the array, or should I still be able to access DSM? Pressing the Power button does not emit any bip and if I keep pressing the NAS shuts down. When I power it back up, the same situation occurs (status and hard drives leds flashing). What would you recommend?
I can't tell you absolutely for Synology, but every NAS I have worked with would still let you access the management interface, even if the array is rebuilding. So there may be a larger problem here. If resetting the network connection doesn't help, I'd second the vote to contact Synology support as they can properly diagnose the issue and perhaps repair something under warranty.
- check whether that model has a serial console. if you are lucky enough to have one, this is the one and only way to grab early boot failures and clearly know what is going on and possibly correct things. i am not entirely sure but the baudrate should be 115200. plug a cable and (re)boot.
- likewise, if you have a vga or some other screen output, try that but i never saw a synology with a graphic card so do not expect much. on the other hand all models i encountered had a serial output.
rebuilding is quite unlikely since you did not change a drive. on or off probably does not matter though if you have a reason to believe it is indeed rebuilding, leave it on until the rebuild completes which could take days.
Hi all. SSH did not work. Synology technical support asked me to remove the HDDs and start the NAS, with the intent to check if the motherboard was faulty. This is not the case (heard the bip at start and power blue led solid). So one or several of the HDDs are faulty. Next step is to test each of them using SeaTools. I still need to do these tests. Just wondering, if all disks are ok, if I would be better off formatting all of them and recreating my array from scratch.
it seems very unlikely to me that the mb and disks and all the hardware is ok and it still breaks. and if it does, the only conclusion is not to ever reuse the same product. or you missed something. i have no specific liking of the tech but syno is definitely not that bad.
bip and blue led do not mean much. bad ram, bad disk controller and a number of other hardware issues will not prevent that from happening. much like plugging a tv and getting a red led lighting up does not mean the tv works.
- I do have backups of all my files, but as you say, it will take a long time to copy everything back on the 3 HDDS when my NAS will be up and running with working drives (total to copy is around 12-13 TB of data as the last 3rd HDD was empty and had just been added to expand the SHR raid array with the 2 original drives)
resilvering is a dangerous operation in this case and can lead easily to either data loss or just kill the existing drives if they were close to their end of life. the temporality seems meaningful. it is obvious to me that broke everything and i must say i wonder why you hid that crucial information in the first place.
ironwolf pro are low end 7200 spindle drives rebranded as pro. the tech itself is quite unsuitable for such disk sizes. platter is not much of an issue imho but i believe most people around would just discard it as a tech of the past altogether. seagate is famous for it's altrnatively great and awful series.
Update: upon Synology technical service recos, I removed all the disks and switched back on the NAS diskless - No issue on LEDs and DSM access which means that the hardware is ok. Then I inserted the disks one by one each time checking the status on DSM. When the 3 HDDs were in I had 2 issues: HDD N2 partition failure and array degraded. I repaired with DSM the partition first (took one minute), and repaired the array (one full day). As soon as the repair was finished the 3HHDs LEDs were solid green but status flashing green... No DSM access any longer... I forced switched off and back on and... back to my initial issue with all 4 LEDs flashing (Status + 3HHDs). I am bored and frustrated. Synology assistance is closed and I am thinking about formating the 3 drives and restarting from scratch. So I have 2 questions
- Before reinserting the drives, how should I format each HDD? Can I just use the 'Erase' button in Seatools? Should I erase all partitions with a dedicated software (eg: Minitool Partition Wizard)? Should I create a new partition without formating ? Then format? At which step should I stop?
i do assume something bad went on when the drives were rebalanced. maybe producing overlapping or otherwise broken scheme that would fail to load on startup or try to finish some operation. a console cable would probably produce that info.
Bottom line, I have decided to reinstall everything. Deleted all partitions on each HDD and re-tested them with Seatools. Then re-insterted the drives and created a new storage pool using RAID-5 instead on SHR. So far so good, but DSM is in the process of optimizing the HDDs in the background, which will take around 16 hours. I will just let it complete before copying anything file
As I don't intend to use HDDs of different sizes RAID5 gives the same overall space capacity as SHR. SHR is advantageous when HDDs of different sizes are mixed. And I would think that rebuilds just take as much time using SHR as RAID5
I understand your comments. But all your suggestions require me to buy another $300-350 16TB HDD while I have just spent a decent amount of money to upgrade my NAS (I had a DS215+ before) and another 16 TB HDD Seagate. Your comments are NOT solutions to my issue but recos for the future. And by the way, rindi, when you say "16TB total which in my opinion usually is more than enough", note that my motivation to buy a new NAS and another HDD was triggered by an alert that my pool was running low on space (
As I said before, my data is backed up on other media and that's what I am using today to recopy the data on the newly formatted Synology RAID5 array. My data being backed up and my money limited, I could not come up with a better option than the RAID5. Except RAID 0, which is another story. Anyone disagreeing with a better option, feel free to comment
As an genuine feedback from a loyal multi-year 'Experts Exchange' subscriber and not limited to this post, please focus on what people CAN do instead of SHOULD do. Because people like me can't do what you think they should from money or expertise standpoint. Help them, don't tell them how they should live
Guys. You have the right approach and your are right to inform/educate people on what could be done. Just balance your comments clearly on 'what you can do today' and 'what I think you could do later'. We sometimes feel the 'could' or 'should' is heavier than the 'can' or is mixed up which, at the precise moment, is putting people at stress and in panic. This is my feedback. You can agree or disagree, but this is a feedback, and by definition, a feedback from others can't be denied.
one option could be to do what shr does under the hood but manually : divide all 3 disks into 2 partitions and create 3 mirrors in ring fashion. you end up with 24T of fast mirrored reliable storage instead of 32 slow much less reliable. may or may not fit your bill but probably worth considering.
"I recently purchased a DS920+ but I just can't access it from my router. Can anyone help, please? My Windows can't connect to Synology NAS on the local network. What do I need to do to get it working again?"
In today's digitally connected world, Network Attached Storage (NAS) devices like Synology NAS have become essential for individuals and businesses alike. These devices allow us to store, access, and manage our data efficiently. Also, you can sync cloud data to NAS, such as syncing Google Photos to Synology.
But, having trouble connecting to your Synology NAS can be frustrating, especially if you rely on it for storing important data or running applications. There could be several reasons behind this issue, ranging from network-related problems to device-specific issues.
Before diving into more complex solutions, it's important to rule out basic network connectivity problems. Check whether your computer or device is connected to the same network as your Synology NAS. A weak Wi-Fi signal or a faulty Ethernet cable could be causing the connection problem.
c80f0f1006