DSM Update Version: 7.2.2-72806 UP1

[Rusty]

While there is no combo update as @fredbert said (as a standalone download), looks like that anyone that started in the past few days applying the 72806 patch, end up with UP1 as well on top of it.

So the 72806 patch is either a combo one (but the date of the last modifications is not up-to-date to confirm this) or it is simply configured to pull the 5MB UP1 as well. All in all, manually trying to install UP1 and you getting an error, is justified as you are clearly on the latest version already.

 

[DeltaGolf]

Good, I'm all up to date and safe. Until the next time!

BTW, I know I had to manually update my 918+ to get to - was it 7.1? - and it seems I don't get the option of auto updates any more. So either I have to keep my eye out or would this update have eventually made its way to me via my control panel?

 

[Rusty]

was it 7.1?

It was 7.2.0. Since that version all x18 and older models are on manual updates only. This will include all upcoming critical or minor/major updates.

 

[fredbert]

Didn't realise the main updater pulled in the patch after it. But I can concur that the DS218+ also has to be manually updated, either that of I don't want to wait for months to be finally told of an update that addresses security vulnerabilities to features I use.

I would add that after the Update 1 patch my DS1520+ had an issue with the RAID. I have drives/bays 1 to 4 as a SHR-1/volume 1, and drive/bay 5 is standalone SHR-0/volume 2. This because I could migrate easily to a 4-bay later, in the event of a failure, and the chassis would be cheaper. The firth bay was spare and a cold standby drive, until a USB drive failed and this was a quick win.

Anyway, upon reboot from the Update 1, drive/bay 3 was missing in Storage Manager. I did a shutdown and reboot with drive 5 in bay 3, to test if the bay was faulty: it booted and worked. So shutdown and rebooted with all drives installed as before, except drive 1 was in bay 3 and drive 3 in bay 1. Just to see what happened. The SHR-1/volume 1 was reported as needing repair so did that and was offered what was drive 3 (in bay 1, keep up!) to do this. Warned that it would wipe the drive, ok, and continued. That all worked and the SHR-1 array has been working since last week. The rebuild also invoked data scrubbing.

The only problem I have had since the Update is Synology Photos was stuck doing something with its database. I only found out a day ago. So stopping and starting the package got it running again, but it appears to have reset it to first run. I have to recreate my albums and all that subject and people tagging has been redone, plus assign access to shared space. For me this isn't a great issue. But I think some would have been rather annoyed.

This was all probably a coincidence with the Update. My DS218+ had no issues.

 

[Rusty]

Tnx for the update. I still have a few machines to bring to this up1, so far no issues, but as you said it could have been a coincidence.

 

[rfawcs]

7.2.2-72806 UP1 has killed my DS418. I can't logon to the machine. When I try, the prompts take a very, very long time to react, if at all. Usually, after I enter the user name and password, I get a spinning indicator that never stops, and the application times out and quits. My DS418 is now a $500 paperweight.

 

[PunchCardBoss]

7.2.2-72806 UP1 has killed my DS418.

Ugg. This may come in handy...

How do I reset my Synology NAS? (For DSM 6.2.4 or above) - Synology Knowledge Center

Synology Knowledge Center offers comprehensive support, providing answers to frequently asked questions, troubleshooting steps, software tutorials, and all the technical documentation you may need.

kb.synology.com

 

[Birdy]

Note: Reset Mode 1

 

[rfawcs]

Thanks for the suggestions. Unfortunately,

I've tried Reset Mode 1 and Reset Mode 2, twice. After the first Mode 2 reset, the 418 showed up in my network as "Diskstation". I could access the shared folders via file explorer, but I could not log onto the 418. After the second Mode 2 reset, the 418 would not show up in my network at all, even through the Synology reset process. After some reading, I downloaded and installed synology-assistant-7.0.5-50070, and I was able to access the DSM via that process. I should say I also disconnected one of the two ethernet cables because that seemed to gum up the works.

The DSM software seems to have loaded, somewhat. I can log onto the 418 as the admin, but I cannot complete the DSM setup process before the program crashes, and I get "The operation failed. Please sign in to DSM and retry." The 418 still does not show up in file explorer, nor can I now access any of the shared folders.

I'm going to keep trying the setup process, at least for a while. If I have to, I'll try Reset Mode 2 process again, but I have a bad feeling about this. I have my data backed up to a Windows 10 machine, but It looks like I'll need a new NAS to put it on.

 

[rfawcs]

Well, progress. I am to the point where I am logged onto the DSM. Although the storage pool indicates all the data is there, I can only see two folders; there should be about fifteen. I am data scrubbing now, so we'll see how that turns out. I can also now access the 418 via file explorer. Fingers crossed.

 

[PunchCardBoss]

Although the storage pool indicates all the data is there, I can only see two folders; there should be about fifteen.

If the other shared drives not visible were encrypted, they would not mount until you load the decryption key. You should see them in the Control Panel but not in File services.

If you had stored decryption keys on the NAS, they may have been wiped out during your Mode 2 reset (not sure about this).

If your shared drives that are not visible are NOT encrypted, then I would suspect a disk corruption issue.

You are doing the right things. Keep us updated please.

 

[Birdy]

If you had stored decryption keys on the NAS

The keys are also downloaded on the PC.

 

[rfawcs]

Fortunately I didn't encrypt the data, so there's that.

The data scrubbing steadily continued and finally gave me an estimate of how long it would take to finish. 35 days. Continuously scrubbing away. Obviously, some serious corruption has occurred.

I don't have 35 days. So, time for the nuclear option. I removed the drives and deleted all data. Loaded the drives back and started from scratch. Surprise, one of the drives had bad sectors and was unusable. I am now reloading all the data from my backup. It should only take 14 days. Gotta replace that drive, also.

I'm glad I followed someone's advice, some time ago. A NAS is not a backup. The daily backup to a different machine is a backup. Lesson learned.

Thanks everyone for your advice. It's been interesting.

 

[zombiephysicist]

Fortunately I didn't encrypt the data, so there's that.

The data scrubbing steadily continued and finally gave me an estimate of how long it would take to finish. 35 days. Continuously scrubbing away. Obviously, some serious corruption has occurred.

I don't have 35 days. So, time for the nuclear option. I removed the drives and deleted all data. Loaded the drives back and started from scratch. Surprise, one of the drives had bad sectors and was unusable. I am now reloading all the data from my backup. It should only take 14 days. Gotta replace that drive, also.

I'm glad I followed someone's advice, some time ago. A NAS is not a backup. The daily backup to a different machine is a backup. Lesson learned.

Thanks everyone for your advice. It's been interesting.

One other suggestion I have. While I do believe a backup to a separate machine is a very good idea, for those who that may not be practical, I highly suggest, if you have enough free slots, to create a separate storage pool with separate physical disks.

For example, on my 1821 I have 5 physical drives in SHR for my primary storage pool. Then I use 2 drive SHR for a 2nd storage pool just as a place to do a hyper backup. That way if the main storage pool gets corrupted, I have physically separate drives from which I can restore/rebuild. Sadly, this has come in handy more than once in the past when my 1815 died. It also is super handy when you Synology makes you nuke your main storage pool to move from ext4 to btrfs or when they make you nuke your main storage pool to reformat it with encryption enabled. You can just rebuild from the backup pool.

 

[fredbert]

I don't have 35 days. So, time for the nuclear option.

You should check the Resync setting. The recommended lower speed does take a lot longer, but the NAS is more responsive during it. But to get it over sooner you can select the faster option, or even set the speed limits. There is also Fast Repair option too.

Sounds like it is now too late to check.

on my 1821 I have 5 physical drives in SHR for my primary storage pool. Then I use 2 drive SHR for a 2nd storage pool just as a place to do a hyper backup

Which is OK if this isn't your sole backup, and I mention this only for others reading this. Having the backup in the same NAS as the primary data still has exposure to malware and unintended manipulation. But if it is for a fast restore point as a first attempt then I see why you do it. For many having the spare bays and drives will be a luxury too far for their budgets. But if you can and it works then why not.

 

[JoHo]

Anyone else having trouble with OpenVPN after the update? I have a DS923+ with several outside users connecting through OpenVPN since July without any issues, but after the update to 7.2.2-72806 last night, no one can connect. Its not a firewall issue since trials show up in the connection list, but as UNDEF.

 

[zombiephysicist]

You should check the Resync setting. The recommended lower speed does take a lot longer, but the NAS is more responsive during it. But to get it over sooner you can select the faster option, or even set the speed limits. There is also Fast Repair option too.

Sounds like it is now too late to check.

View attachment 20974


Which is OK if this isn't your sole backup, and I mention this only for others reading this. Having the backup in the same NAS as the primary data still has exposure to malware and unintended manipulation. But if it is for a fast restore point as a first attempt then I see why you do it. For many having the spare bays and drives will be a luxury too far for their budgets. But if you can and it works then why not.

Agreed. It is not. But it has proven more useful than tertiary backups most of the time. So it's a great luxury and a much faster one to get things back and working again for a fair number of situations.

But as I said in my first post, the ideal is to have other back ups off the same machine.

 

[BobW]

Has anyone seen this update breaking LDAP groups & authentication? All my LDAP groups are showing up as unknown with a number rather than their name.

It could have happened after the initial 7.2.2-72806, but I just stacked Update 1 on top before testing.

Thanks!

I'm also having problems with LDAP and Synology SSO Server after the latest update. Users can not login in anymore using their LDAP account on several services using SSO login.
Already restarted everything, and no setting were changed. Also tried resetting an accounts password, but that didn't help either.