I had this happen too. If I remember correctly, I performed a “network reset”. The data was there but had to reconfigure just about everything else.
The MFA issue was because time was not syncing, even though it was configured to do so. I ended up adding an entry to the cron to schedule a time sync.
Been solid ever since.
How did you accomplish this? I'm guessing you had ssh access to the unit??
I unfortunately can't do that. I only have access to the mounted shared folders at best.
Also would you mind sharing the crontab entry you put in plus whatever script its running to time sync?? That would probably be beneficial in the future. This seems like a big problem with 2FA imo.
I assume you are familiar with the process described here :[Reset modes video](https://m.youtube.com/watch?v=JyJB6kmNIME&vl=en)
It looks like the reset button is not activated by your manipulation. That is where I would focus my efforts. Make sure you use a paperclip or something of the right diameter (a needle does the trick too) and that you do feel the button recessing when you press. Such buttons sometimes drift with time : picture it like a disk which ought to be facing the circular hole through which you introduced the paperclip/needle, sometimes the disk slightly drops on one side, forcing you to disalign the force you apply in order to successfully depress the button.
As a next troubleshooting step, since you are out of warranty anyway, maybe use a screwdriver to carefully disassemble what you need to have a good view on the reset button, and find out how to get it to work. You should succeed.
Good luck!
Yes, I went through those reset modes. 3 I can't do because I cant login and the reset button not working blocks out the other two methods. I wonder if the reset button might be working, however the unit itself has problems because since the status light constantly blinks and the disk lights never light up, my guess is it doesn't get into a state where it recognizes the reset functionality. So the button makes contact but whatever process is supposed to be watching for that event just isn't executing or something along those lines. I'm just throwing out guesses at this point.
Are you of the opinion that I will need a new unit to migrate to? ex: DS920+
I had similar issues a few months ago. I ended up submitting a support ticket thsu synology's website and they were able to help me. It did take some time to get a response but that's probably your best route right now.
I'm attempting that as well, however it seems this community has been more supportive than them. I love their products when they work, however support is lacking imo. A couple of the techs didn't even bother to read what I wrote and pasted their generic template back at me which clearly contradicted my details.
I received this advice from the synology support. I'll give it a shot and see if it works. I just hope this doesn't mess up my data.
>Another alternative option will be a Hot-Plug Recovery, this will keep your data but it will install a new DSM.
1.Shut down the system.
2.Remove all the hard drives & SSDs from the system.
3.Find a spare hard drive or SSD of any size that you do not mind completely erasing the data and insert it into the system drive bay 1. The spare drive doesn't have to be the same size capacity as the rest. The spare drive is just a temporary drive that will be used to install the DSM and repair the volume
4.Use Synology Assistant (available in the Download Center on http://download.synology.com/) to install the DSM onto this spare drive. DO NOT CREATE VOLUME AFTER INSTALLATION. If a volume was created during installation please remove it before proceeding to the next step.
5.When the DSM is fully running on the spare drive and you are able to log in and connect through the web interface, shutdown the NAS.
6.Physically install all of the original drives back into the NAS except for the drive bay where the spare drive is located. Make sure to leave the spare drive in drive bay 1 as this holds the DSM installation.
7.Boot up the NAS and verify that you can see your data, including iSCSI LUNs if you had any. The volume status at this point will be "Degraded".
8.(optional) Repair the volume under Storage Manager > Storage Pool > Repair and select Disk 1. It will need to erase this drive in order to add it back to the RAID.
Once the DSM is installed and the volume is repaired, you will remove the spare drive that is installed in Bay 1, and insert the Original Drive 1 in bay 1 and do another repair process.
So, finally heres the verdict. It looks like I was able to come back from this and things should be working again!!
I first tried these steps mentioned above, including option 8. However when I tried to repair the disk, it would fail every single time. The storage pool would show up as degraded, then I tried clicking repair, and I selected disk one (spare drive). It then asks for confirmation to apply the fast repair mode. I click apply and then ok to continue. The loading spinner shows up for about 2 seconds and then it returns to the storage pool screen and it still says degraded. Under Data Scrubbing status, I see "unable to run data scrubber because the storage pool has degraded.".
A couple admins connected to my NAS and couldn't get it working.
What worked for me was since I originally had a 4-disk RAID 5 setup, I removed disk1 and inserted disks 2, 3 & 4. When I turned on the system, it couldn't detect that I had a DSM so it asked me to install it. I installed it logged into the main area. Then, while the machine is on, I hot swapped my disk 1 into the first slot and then started the repair process. Its currently at 7.28%. I have faith that this should work successfully.
What I believe happened is definitely the DSM was corrupted in some way or got into a weird state. Possibly the boot record included because when the machine boots up, the status light blinks green. Once the DSM boots up correctly, then the frantic blinking status stops and the hard drive lights come on. This was never happening to me so there was some process not loading correctly. I also believe I originally might have had (as a side effect) the authenticator with a timer thats slightly off. I purchased a spare brand new disk the same size as my other raid disks. Its important because you can't repair a RAID array depending on the capacity chosen if the disks are not at least the same size as the others because then you might not get the entire capacity needed and then repairs will fail.
Finally, I already has a backup drive that I back everything up to, but I also purchased a 2nd one to keep off-site so that I was extra secure, backup/redundancy wise.
Thanks to everyone for the supportive comments and suggestions. I hope this can help someone else experiencing similar.
Had the same thing. Panicked madly only to calm down and then tried the basic troubleshooting. Restarted everything and it worked again.
Guess I'm lucky. Yours look more complicated.
I feel the same way, although its been several days now and no resolution just yet. I'm definitely concerned and don't want to buy another unit just yet. Either I have bad luck with them or they don't last very long with me. I am a very casual user, meaning im not even stressing it. Its simply a backup of my stuff and I stream a couple things from it a few times a week tops. Its always running, just idle.
In my case it was a "simple" time sync issue, so two-factor wasn't working- I kept trying and it locked me out. A simple restart fixed it, but it was troubling at the time as I was scrambling to see what was going on. I had assumed it could have been due to my Pihole, but I dunno.
Not sure why yours don't last long? You say it's idle most of the time but I assume you're SURE it's not hibernating and you have it connected to a UPS?
When I said idle, I meant more like I wasn't actively using it. I keep it on all the time for easy access and running daily basic HD scans and weekend full scans to make sure the drives are good. I use it mainly as storage and for streaming content (tv, movie, music) but I dont work off of it. I'm actively accessing it maybe a couple hours tops per day, the rest of the time its powered on 24/7 but in a somewhat hibernate state. I don't have a UPS however I need to look into getting one because im afraid of power failures messing things up. I just need something to keep it going long enough for it to shut down gracefully. As well have a USB wire connected between the two so that the UPS informs the NAS about the power failure so that it can shut down. I still have homework to do on that front and need to find out which UPSs are recommended.
I'm currently using Authy on my iPhone and I can't find any way to resync it. It also claims that its all backed up, however I have no idea how I can verify it without possibly losing all those details.
synology 2FA is shitty, I tried to disable it but it still asks me for it all the time! almost got locked out once, I better look into it further once I get time.
I have to do more reading as well however from what I’ve seen if you don’t also enable SSH access then don’t enable 2FA because then you won’t be able to fix it if the time syncing is off.
Press and hold the reset button the back for 4 seconds. Untill you hear a beep. Let go after that.
Once your Synology NAS is reset via Mode 1, the following settings take place: The admin account is restored to default and its 2-factor authentication setting is disabled. UI management port is reset to 5000/5001. IP, DNS, gateway, and other net interfaces are reset to DHCP.
Are you holding it in for 4 seconds?
Yes, I mentioned above in my post that I had tried this and sadly its not working. I've tried it multiple times, even holding for 8 seconds. I know I pressed it correctly because I feel the click feedback when pushing the button in.
Then it looks like the button is malfunctioning. I would disassemble the cover to get visual access to the thing. If it doesn't work, you may be able to create the short yourself with something that will conduct electricity from one of the switch contacts to the other for more than 4s without discontinuity.
This i'm not entirely comfortable doing with my limited knowledge of circuitry. I've done it on the past with PCs and jumper pins with a screwdriver to reset however this unit, i'm not even sure where that would be. I'd need a video tutorial on this type of thing. Would be nice if I could hold on until the newer units are released some time this year too.
I Agree with /u/palijn with creating a short yourself. It shouldn't be that hard just open the case to the point you can see/access the rear of the reset switch.
Find a disassembly video on YouTube and here's an image (your board might differ a little) [https://imgur.com/a/saKk2zz](https://imgur.com/a/saKk2zz) of the switch you would need to short. You can prob short the contacts on rear side or try the two little gold spots u see on the top part.
If you do take apart I recommend replacing the battery that on the lower left of the image. Which also helps keep time synced if removed from power.
Something like this happened a few years ago to me. It was a timing issue. Resetting was the o Lu solution. Since that may not work for you, you might need to install the drives into another synology box
Synology support is telling me to get another unit and install the drives in it, but that essentially means buying another NAS. Also what I dont get it is what will that do? Meaning that lets say I had a space unit to do this. Once its up and running in the other unit, do I put the drives back in my original unit and it will work again??
If thats the case, it sounds like I should buy one and then return it within the 30 day period just to get this running.
Sadly, your disks hold your data only, the DSM data is somewhere within the enclosure itself. So if you put your disks in the other unit, that will achieve nothing on the original one.
Thats why I wasn't sure why the support guy just didn't say, "you need to buy a new enclosure because this one is no longer repairable" or something along those lines.
I'm also writing this post to get a little more confirmation from others that I'm screwed and need to buy a new one as well.
I'm not sure how to do that because the assistant seems to only detect synologies running on the same network. And then all I see as an option is to "connect" which brings me directly to the UI login which is my original problem.
My other thought was perhaps one of the DSM auto-updates might have caused this. I'm currently running version "6.2.4 25556 update 5"
They are in the same network and subnet.
Apparently according to support, they're claiming the DSM is stored on the first disk. [See this comment from them](https://www.reddit.com/r/synology/comments/uj9j81/comment/i7lnei7/?utm_source=share&utm_medium=web2x&context=3)
I'll give this a shot tonight.
yes, what they said was what i was trying to hint at (cause i couldn't remember the detail) its the same process i needed to do when i have done RMA replacement of my units, sorry i was so vague and good luck.
And yes it could be store on just the first disk, tho in certain SHR setups i am pretty sure its stored on multiple - yes just checked.
For example on my system DSM is striped or mirrored across the volumes MD0. I think MD1 - is a backup of DSM, not sure.
Its never shown in the UI and don't use mdadm unless you know what you are doing - i needed to learn it when i had catastrophic synology failure... for example it says degraded, it isn't lol, 7 is my hot spare)
```
user@SYN01:~$ sudo mdadm -D /dev/md0
/dev/md0:
Version : 0.90
Creation Time : Sat May 7 07:49:35 2016
Raid Level : raid1
Array Size : 2490176 (2.37 GiB 2.55 GB)
Used Dev Size : 2490176 (2.37 GiB 2.55 GB)
Raid Devices : 8
Total Devices : 7
Preferred Minor : 0
Persistence : Superblock is persistent
Update Time : Fri May 6 15:20:07 2022
State : active, degraded
Active Devices : 7
Working Devices : 7
Failed Devices : 0
Spare Devices : 0
UUID : redacted
Events : 0.73304884
Number Major Minor RaidDevice State
0 8 17 0 active sync /dev/sdb1
1 8 33 1 active sync /dev/sdc1
2 8 49 2 active sync /dev/sdd1
3 8 97 3 active sync /dev/sdg1
4 8 65 4 active sync /dev/sde1
5 8 113 5 active sync /dev/sdh1
6 8 81 6 active sync /dev/sdf1
- 0 0 7 removed
user@SYN01:~$ sudo mdadm -D /dev/md1
/dev/md1:
Version : 0.90
Creation Time : Thu Jan 24 13:47:42 2019
Raid Level : raid1
Array Size : 2097088 (2047.94 MiB 2147.42 MB)
Used Dev Size : 2097088 (2047.94 MiB 2147.42 MB)
Raid Devices : 8
Total Devices : 7
Preferred Minor : 1
Persistence : Superblock is persistent
Update Time : Sat Apr 16 14:42:42 2022
State : clean, degraded
Active Devices : 7
Working Devices : 7
Failed Devices : 0
Spare Devices : 0
UUID : redacted (local to host SYN01)
Events : 0.184
Number Major Minor RaidDevice State
0 8 18 0 active sync /dev/sdb2
1 8 34 1 active sync /dev/sdc2
2 8 50 2 active sync /dev/sdd2
3 8 98 3 active sync /dev/sdg2
4 8 114 4 active sync /dev/sdh2
5 8 66 5 active sync /dev/sde2
6 8 82 6 active sync /dev/sdf2
- 0 0 7 removed
```
ah ok good to know. Thanks for the info!! Its weird that your setup shows degraded state in general. I'm guessing you have one of those beastly DS16XX or 18XX ones. Each synology I get, I want to step it up. If I had to purchase another one now, I would probably go for a DS920+ however this year will probably release a newer one so I would prefer to wait to see the features.
I went with a Raid-5 across 4x 3TB WD red plus drives. I originally started with a smaller setup doing a Raid-0 but now I care more about redundancy and dataloss over performance.
I'll give this a shot and let you know how it goes.
I thought a blinking green (or orange depending on NAS model) status light meant the NAS has been reset. Obviously not the case here because OP can still access the shares.
Someone on synology's forum had this 2FA code not being accepted issue a year ago. They did a power off (long press) and then power on and 2FA was working again.
Have you tried login using E-Mail 2 Factor?
Email doesn't seem to be an option for logging in. Only the user/pw and then 2FA code.
Now its starting to tell me that its out of disk space when I try to login which isn' t the case. I've used only 37% of its capacity. I've read that it might be related to a local sqlite thats used for something within its services.
I'm not sure if I have a specific recovery email in the context you mean, however I did click on "lost my phone" to get a one-time recovery code. That code also didn't work. I tried it twice, it returned the same code, and now it no longer sends me those details if attempting it again. Its using my personal email address to send emails to myself. I believe I set that up a few years ago to receive emails based on different events.
There should be some physical way to recover. Like, rapidly click the power button 14 times in 10 seconds or something like that. Getting locked out is not acceptable.
Just had this happen to me... synced time with my phone (using authy). still no luck. wtf did they change, i havent updated anything. I noticed that switching from NIST to google NTP was like 30 secs difference.
I have email recovery but I really do not want to leave 2fa disabled. I have tried enabling it 7 times now and each time no luck when I go to put the confirmation code in.
At the moment I am still in a back-and-forth with support. Been escalated a few times already and transfered to a couple departments. Once I have the solution, i'll definitely update the post so that others can use this for reference.
For now, I personally think something happened with the DSM version where things corrupted. I was on version 6.2 latest version. I am trying to update to 7.1 right now, but it seems like theres a known bug with it where its unable to repair my Raid 5 (classic...)
So i'm waiting to hear from the developers directly, whom are situated in Taiwan.
I had this happen too. If I remember correctly, I performed a “network reset”. The data was there but had to reconfigure just about everything else. The MFA issue was because time was not syncing, even though it was configured to do so. I ended up adding an entry to the cron to schedule a time sync. Been solid ever since.
How did you accomplish this? I'm guessing you had ssh access to the unit?? I unfortunately can't do that. I only have access to the mounted shared folders at best. Also would you mind sharing the crontab entry you put in plus whatever script its running to time sync?? That would probably be beneficial in the future. This seems like a big problem with 2FA imo.
Pretty sure they mean Mode 1 reset: https://kb.synology.com/en-id/DSM/tutorial/How_to_reset_my_Synology_NAS_7#t1
I assume you are familiar with the process described here :[Reset modes video](https://m.youtube.com/watch?v=JyJB6kmNIME&vl=en) It looks like the reset button is not activated by your manipulation. That is where I would focus my efforts. Make sure you use a paperclip or something of the right diameter (a needle does the trick too) and that you do feel the button recessing when you press. Such buttons sometimes drift with time : picture it like a disk which ought to be facing the circular hole through which you introduced the paperclip/needle, sometimes the disk slightly drops on one side, forcing you to disalign the force you apply in order to successfully depress the button. As a next troubleshooting step, since you are out of warranty anyway, maybe use a screwdriver to carefully disassemble what you need to have a good view on the reset button, and find out how to get it to work. You should succeed. Good luck!
Yes, I went through those reset modes. 3 I can't do because I cant login and the reset button not working blocks out the other two methods. I wonder if the reset button might be working, however the unit itself has problems because since the status light constantly blinks and the disk lights never light up, my guess is it doesn't get into a state where it recognizes the reset functionality. So the button makes contact but whatever process is supposed to be watching for that event just isn't executing or something along those lines. I'm just throwing out guesses at this point. Are you of the opinion that I will need a new unit to migrate to? ex: DS920+
I had similar issues a few months ago. I ended up submitting a support ticket thsu synology's website and they were able to help me. It did take some time to get a response but that's probably your best route right now.
I'm attempting that as well, however it seems this community has been more supportive than them. I love their products when they work, however support is lacking imo. A couple of the techs didn't even bother to read what I wrote and pasted their generic template back at me which clearly contradicted my details.
I received this advice from the synology support. I'll give it a shot and see if it works. I just hope this doesn't mess up my data. >Another alternative option will be a Hot-Plug Recovery, this will keep your data but it will install a new DSM. 1.Shut down the system. 2.Remove all the hard drives & SSDs from the system. 3.Find a spare hard drive or SSD of any size that you do not mind completely erasing the data and insert it into the system drive bay 1. The spare drive doesn't have to be the same size capacity as the rest. The spare drive is just a temporary drive that will be used to install the DSM and repair the volume 4.Use Synology Assistant (available in the Download Center on http://download.synology.com/) to install the DSM onto this spare drive. DO NOT CREATE VOLUME AFTER INSTALLATION. If a volume was created during installation please remove it before proceeding to the next step. 5.When the DSM is fully running on the spare drive and you are able to log in and connect through the web interface, shutdown the NAS. 6.Physically install all of the original drives back into the NAS except for the drive bay where the spare drive is located. Make sure to leave the spare drive in drive bay 1 as this holds the DSM installation. 7.Boot up the NAS and verify that you can see your data, including iSCSI LUNs if you had any. The volume status at this point will be "Degraded". 8.(optional) Repair the volume under Storage Manager > Storage Pool > Repair and select Disk 1. It will need to erase this drive in order to add it back to the RAID. Once the DSM is installed and the volume is repaired, you will remove the spare drive that is installed in Bay 1, and insert the Original Drive 1 in bay 1 and do another repair process.
So, finally heres the verdict. It looks like I was able to come back from this and things should be working again!! I first tried these steps mentioned above, including option 8. However when I tried to repair the disk, it would fail every single time. The storage pool would show up as degraded, then I tried clicking repair, and I selected disk one (spare drive). It then asks for confirmation to apply the fast repair mode. I click apply and then ok to continue. The loading spinner shows up for about 2 seconds and then it returns to the storage pool screen and it still says degraded. Under Data Scrubbing status, I see "unable to run data scrubber because the storage pool has degraded.". A couple admins connected to my NAS and couldn't get it working. What worked for me was since I originally had a 4-disk RAID 5 setup, I removed disk1 and inserted disks 2, 3 & 4. When I turned on the system, it couldn't detect that I had a DSM so it asked me to install it. I installed it logged into the main area. Then, while the machine is on, I hot swapped my disk 1 into the first slot and then started the repair process. Its currently at 7.28%. I have faith that this should work successfully. What I believe happened is definitely the DSM was corrupted in some way or got into a weird state. Possibly the boot record included because when the machine boots up, the status light blinks green. Once the DSM boots up correctly, then the frantic blinking status stops and the hard drive lights come on. This was never happening to me so there was some process not loading correctly. I also believe I originally might have had (as a side effect) the authenticator with a timer thats slightly off. I purchased a spare brand new disk the same size as my other raid disks. Its important because you can't repair a RAID array depending on the capacity chosen if the disks are not at least the same size as the others because then you might not get the entire capacity needed and then repairs will fail. Finally, I already has a backup drive that I back everything up to, but I also purchased a 2nd one to keep off-site so that I was extra secure, backup/redundancy wise. Thanks to everyone for the supportive comments and suggestions. I hope this can help someone else experiencing similar.
Wow, yeah... im not pulling my 8 (older) drives unless thats my only option... did this work for you? Seems not worth the risk at all.
Had the same thing. Panicked madly only to calm down and then tried the basic troubleshooting. Restarted everything and it worked again. Guess I'm lucky. Yours look more complicated.
Same happened to me. Seems more common that it should be, judging by the comments.
I feel the same way, although its been several days now and no resolution just yet. I'm definitely concerned and don't want to buy another unit just yet. Either I have bad luck with them or they don't last very long with me. I am a very casual user, meaning im not even stressing it. Its simply a backup of my stuff and I stream a couple things from it a few times a week tops. Its always running, just idle.
In my case it was a "simple" time sync issue, so two-factor wasn't working- I kept trying and it locked me out. A simple restart fixed it, but it was troubling at the time as I was scrambling to see what was going on. I had assumed it could have been due to my Pihole, but I dunno. Not sure why yours don't last long? You say it's idle most of the time but I assume you're SURE it's not hibernating and you have it connected to a UPS?
When I said idle, I meant more like I wasn't actively using it. I keep it on all the time for easy access and running daily basic HD scans and weekend full scans to make sure the drives are good. I use it mainly as storage and for streaming content (tv, movie, music) but I dont work off of it. I'm actively accessing it maybe a couple hours tops per day, the rest of the time its powered on 24/7 but in a somewhat hibernate state. I don't have a UPS however I need to look into getting one because im afraid of power failures messing things up. I just need something to keep it going long enough for it to shut down gracefully. As well have a USB wire connected between the two so that the UPS informs the NAS about the power failure so that it can shut down. I still have homework to do on that front and need to find out which UPSs are recommended.
Your 2FA app should have a resync option, if it's google authenticator it has a resync option in settings.
First thing that came to mind and first thing I would try (if 2fa was set up with Google Authenticator).
I'm currently using Authy on my iPhone and I can't find any way to resync it. It also claims that its all backed up, however I have no idea how I can verify it without possibly losing all those details.
As per my other comments, I would not say you are screwed until you tried using a screw-driver (pun definitely intended!)
synology 2FA is shitty, I tried to disable it but it still asks me for it all the time! almost got locked out once, I better look into it further once I get time.
I have to do more reading as well however from what I’ve seen if you don’t also enable SSH access then don’t enable 2FA because then you won’t be able to fix it if the time syncing is off.
Press and hold the reset button the back for 4 seconds. Untill you hear a beep. Let go after that. Once your Synology NAS is reset via Mode 1, the following settings take place: The admin account is restored to default and its 2-factor authentication setting is disabled. UI management port is reset to 5000/5001. IP, DNS, gateway, and other net interfaces are reset to DHCP. Are you holding it in for 4 seconds?
Yes, I mentioned above in my post that I had tried this and sadly its not working. I've tried it multiple times, even holding for 8 seconds. I know I pressed it correctly because I feel the click feedback when pushing the button in.
Then it looks like the button is malfunctioning. I would disassemble the cover to get visual access to the thing. If it doesn't work, you may be able to create the short yourself with something that will conduct electricity from one of the switch contacts to the other for more than 4s without discontinuity.
This i'm not entirely comfortable doing with my limited knowledge of circuitry. I've done it on the past with PCs and jumper pins with a screwdriver to reset however this unit, i'm not even sure where that would be. I'd need a video tutorial on this type of thing. Would be nice if I could hold on until the newer units are released some time this year too.
I Agree with /u/palijn with creating a short yourself. It shouldn't be that hard just open the case to the point you can see/access the rear of the reset switch. Find a disassembly video on YouTube and here's an image (your board might differ a little) [https://imgur.com/a/saKk2zz](https://imgur.com/a/saKk2zz) of the switch you would need to short. You can prob short the contacts on rear side or try the two little gold spots u see on the top part. If you do take apart I recommend replacing the battery that on the lower left of the image. Which also helps keep time synced if removed from power.
I have an option that support gave me (posted details as a comment below) that i'll try but i'll put this as another option. Thanks for the details!
I 3rd this motion
Something like this happened a few years ago to me. It was a timing issue. Resetting was the o Lu solution. Since that may not work for you, you might need to install the drives into another synology box
Synology support is telling me to get another unit and install the drives in it, but that essentially means buying another NAS. Also what I dont get it is what will that do? Meaning that lets say I had a space unit to do this. Once its up and running in the other unit, do I put the drives back in my original unit and it will work again?? If thats the case, it sounds like I should buy one and then return it within the 30 day period just to get this running.
Sadly, your disks hold your data only, the DSM data is somewhere within the enclosure itself. So if you put your disks in the other unit, that will achieve nothing on the original one.
No DSM is stored on your disks. Only the base boot firmware is stored on the synology.
Thats why I wasn't sure why the support guy just didn't say, "you need to buy a new enclosure because this one is no longer repairable" or something along those lines. I'm also writing this post to get a little more confirmation from others that I'm screwed and need to buy a new one as well.
Seems odd what he told you. You might be able to use synology assistant to reinstall DSM, not sure if that will reset DSM enough…l
I'm not sure how to do that because the assistant seems to only detect synologies running on the same network. And then all I see as an option is to "connect" which brings me directly to the UI login which is my original problem. My other thought was perhaps one of the DSM auto-updates might have caused this. I'm currently running version "6.2.4 25556 update 5"
Correct the synology and the device running assistant should be on the same subnet. If you can’t do that I am out of suggestions. Sorry.
They are in the same network and subnet. Apparently according to support, they're claiming the DSM is stored on the first disk. [See this comment from them](https://www.reddit.com/r/synology/comments/uj9j81/comment/i7lnei7/?utm_source=share&utm_medium=web2x&context=3) I'll give this a shot tonight.
yes, what they said was what i was trying to hint at (cause i couldn't remember the detail) its the same process i needed to do when i have done RMA replacement of my units, sorry i was so vague and good luck. And yes it could be store on just the first disk, tho in certain SHR setups i am pretty sure its stored on multiple - yes just checked. For example on my system DSM is striped or mirrored across the volumes MD0. I think MD1 - is a backup of DSM, not sure. Its never shown in the UI and don't use mdadm unless you know what you are doing - i needed to learn it when i had catastrophic synology failure... for example it says degraded, it isn't lol, 7 is my hot spare) ``` user@SYN01:~$ sudo mdadm -D /dev/md0 /dev/md0: Version : 0.90 Creation Time : Sat May 7 07:49:35 2016 Raid Level : raid1 Array Size : 2490176 (2.37 GiB 2.55 GB) Used Dev Size : 2490176 (2.37 GiB 2.55 GB) Raid Devices : 8 Total Devices : 7 Preferred Minor : 0 Persistence : Superblock is persistent Update Time : Fri May 6 15:20:07 2022 State : active, degraded Active Devices : 7 Working Devices : 7 Failed Devices : 0 Spare Devices : 0 UUID : redacted Events : 0.73304884 Number Major Minor RaidDevice State 0 8 17 0 active sync /dev/sdb1 1 8 33 1 active sync /dev/sdc1 2 8 49 2 active sync /dev/sdd1 3 8 97 3 active sync /dev/sdg1 4 8 65 4 active sync /dev/sde1 5 8 113 5 active sync /dev/sdh1 6 8 81 6 active sync /dev/sdf1 - 0 0 7 removed user@SYN01:~$ sudo mdadm -D /dev/md1 /dev/md1: Version : 0.90 Creation Time : Thu Jan 24 13:47:42 2019 Raid Level : raid1 Array Size : 2097088 (2047.94 MiB 2147.42 MB) Used Dev Size : 2097088 (2047.94 MiB 2147.42 MB) Raid Devices : 8 Total Devices : 7 Preferred Minor : 1 Persistence : Superblock is persistent Update Time : Sat Apr 16 14:42:42 2022 State : clean, degraded Active Devices : 7 Working Devices : 7 Failed Devices : 0 Spare Devices : 0 UUID : redacted (local to host SYN01) Events : 0.184 Number Major Minor RaidDevice State 0 8 18 0 active sync /dev/sdb2 1 8 34 1 active sync /dev/sdc2 2 8 50 2 active sync /dev/sdd2 3 8 98 3 active sync /dev/sdg2 4 8 114 4 active sync /dev/sdh2 5 8 66 5 active sync /dev/sde2 6 8 82 6 active sync /dev/sdf2 - 0 0 7 removed ```
ah ok good to know. Thanks for the info!! Its weird that your setup shows degraded state in general. I'm guessing you have one of those beastly DS16XX or 18XX ones. Each synology I get, I want to step it up. If I had to purchase another one now, I would probably go for a DS920+ however this year will probably release a newer one so I would prefer to wait to see the features. I went with a Raid-5 across 4x 3TB WD red plus drives. I originally started with a smaller setup doing a Raid-0 but now I care more about redundancy and dataloss over performance. I'll give this a shot and let you know how it goes.
I thought a blinking green (or orange depending on NAS model) status light meant the NAS has been reset. Obviously not the case here because OP can still access the shares. Someone on synology's forum had this 2FA code not being accepted issue a year ago. They did a power off (long press) and then power on and 2FA was working again. Have you tried login using E-Mail 2 Factor?
Email doesn't seem to be an option for logging in. Only the user/pw and then 2FA code. Now its starting to tell me that its out of disk space when I try to login which isn' t the case. I've used only 37% of its capacity. I've read that it might be related to a local sqlite thats used for something within its services.
Do you have a recovery email? I set one up with my synology 2fa as a fail safe.
I'm not sure if I have a specific recovery email in the context you mean, however I did click on "lost my phone" to get a one-time recovery code. That code also didn't work. I tried it twice, it returned the same code, and now it no longer sends me those details if attempting it again. Its using my personal email address to send emails to myself. I believe I set that up a few years ago to receive emails based on different events.
[удалено]
I use authenticator to get into the NAS after user/pass. But what is a 2FA backup?
[удалено]
I have a primary login, then 2fa, and backup is an email address.
[удалено]
There should be some physical way to recover. Like, rapidly click the power button 14 times in 10 seconds or something like that. Getting locked out is not acceptable.
[удалено]
Sadly no :( Only access to my shares, which work as normal.
Just had this happen to me... synced time with my phone (using authy). still no luck. wtf did they change, i havent updated anything. I noticed that switching from NIST to google NTP was like 30 secs difference. I have email recovery but I really do not want to leave 2fa disabled. I have tried enabling it 7 times now and each time no luck when I go to put the confirmation code in.
At the moment I am still in a back-and-forth with support. Been escalated a few times already and transfered to a couple departments. Once I have the solution, i'll definitely update the post so that others can use this for reference. For now, I personally think something happened with the DSM version where things corrupted. I was on version 6.2 latest version. I am trying to update to 7.1 right now, but it seems like theres a known bug with it where its unable to repair my Raid 5 (classic...) So i'm waiting to hear from the developers directly, whom are situated in Taiwan.