DSM 7.3 Update

[Rusty]

Oct 28th

 

[fredbert]

I thought I heard someone mention synology drive 4 was out, but I see nothing in the downloads about it.

Currently in the Beta section of Package Center. So available insomuch as you can join the beta v4.

 

[wrldtvlr]

I thought I heard someone mention synology drive 4 was out, but I see nothing in the downloads about it.

There's some discussion here: NAS Compares - Synology DSM 7.3 - SHOULD YOU UPGRADE?

 

[Bill Wilder]

I too have updated to 7.3, not out of a desire to be bleeding edge but due to replication failing after applying some 7.2 package updates. Existing replications have resumed syncing but at 7.3 I seem unable to create new shared folder replications due to authentication failures with the destination NAS. Has anyone else tried to create new replications post 7.3? Thanks

 

[Rusty]

I too have updated to 7.3, not out of a desire to be bleeding edge but due to replication failing after applying some 7.2 package updates. Existing replications have resumed syncing but at 7.3 I seem unable to create new shared folder replications due to authentication failures with the destination NAS. Has anyone else tried to create new replications post 7.3? Thanks

Replication via Snapshot Replication package or?

 

[Bill Wilder]

Yes Snapshot replication

 

[zombiephysicist]

Let the installation of 30TB drives begin!! Feels like it’s 2005 all over again only with larger drives

I’m so glad for the turn around.

I hope they don’t try this again, but sadly their messaging seems to be that they will. Which is really crazy. They need to allay people’s fears they will do this again and layout some coherent message like:

We will always let you use any drives, however if it’s not our drive or a verified drive no software support. We will let all the big and popular brands become verified so you will have more choices than our drives.​

Just something simple, easy to understand and coherent like that is all it would take to right this disaster. But right now they seemed to take the worst path possible. Backpeddling on the decision, while doubling down on the message that “we still want to hardware lock our drives sometime in the future|” seems like they have a criminally insane marketing department.

 

[Jan Janowski]

Depends on who's in charge..... The Engineers, or Accountants!

So far, it screams: Accountants!

 

[SdeGat]

Updated my DS923+, worked fine so far.

I did too with no issues. As I use my 923+ only to backup my computer and as a file server, I think I’m less likely to hit compatibility issues.

 

[fredbert]

I updated my DS218+. So far I only experienced the LED brightness issue: it goes to full brightness, and doesn't change when changed in Control Panel. The fix is provided by Synology here:

Synology Community

Hi! Come and join us at Synology Community. A place to answer all your Synology questions. Ask a question or start a discussion now.

community.synology.com

The fix is to run a complex, compound shell command. Either do it as suggested in the post, or on SSH command line you first need to move to a root login using the sudo -i command. For example:

sudo -i
sed -i -E '/<i2c\b[^>]*command_type=/! s|(<i2c\b[^>]*)/>|\1command_type="SMBUS" />|' /usr/syno/etc.defaults/led_brightness.xml; cp /usr/syno/etc.defaults/led_brightness.xml /tmp/syno_led_brightness/led_brightness.xml;

This changes /usr/syno/etc.defaults/led_brightness.xml to this...

<?xml version="1.0" encoding="UTF-8"?>
<led_brightness>
    <i2c bus="0x1" address="0x2e" offset="0x0" command_type="SMBUS" />
    <brightness value="0" i2cValue="0x7d" />
    <brightness value="1" i2cValue="0x4C" />
    <brightness value="2" i2cValue="0x46" />
    <brightness value="3" i2cValue="0x40" default="true"/>
</led_brightness>

---

Addendum [#1 ??]

Just posted by Synology is that a USB UPS may not be recognised.

Synology Community

Hi! Come and join us at Synology Community. A place to answer all your Synology questions. Ask a question or start a discussion now.

community.synology.com

As before the command can be done using SSH, but again use a root shell.

sudo -i
cd /usr/lib/systemd/system/syno-bootup-done.target.wants && ln -s ../ups-usb.service ./

It's a missing symbolic link to the USB UPS service created in a boot up folder. Needs a reboot, but then the USB UPS is recognised.

I'm not rushing to use DSM 7.3 on my main DS1520+. Though the clutch of CVE vulnerability fixes is slightly concerning. I've not seen any discussion about the level of exposure.

 

[Bill Wilder]

I too have updated to 7.3, not out of a desire to be bleeding edge but due to replication failing after applying some 7.2 package updates. Existing replications have resumed syncing but at 7.3 I seem unable to create new shared folder replications due to authentication failures with the destination NAS. Has anyone else tried to create new replications post 7.3? Thanks

UPDATE: RESOLVED - I can now establish new replications but I must select Encrypted in order for authentication to proceed.

 

[Voodoochild]

Well I guess my 1515+ will stay on 7.1