DSM 6.1.4-15217 Update 5

Forum rules
1) This is a user forum for Synology users to share experience/help out each other: if you need direct assistance from the Synology technical support team, please use the following form:

https://account.synology.com/support/support_form.php?lang=enu



2) To avoid putting users' DiskStation at risk, please don't paste links to any patches provided by our Support team as we will systematically remove them. Our Support team will provide the correct patch for your DiskStation model.
fremenik
Student
Student
Posts: 78
Joined: Mon Oct 08, 2012 6:12 pm
Location: Canada
Contact:

Re: DSM 6.1.4-15217 Update 5

Postby fremenik » Wed Jan 10, 2018 5:37 am

jeroenvt wrote:For those who are experiencing improper shutdowns: Synology Support suggested to temporarily disable Cloud Station (stop the package on the NAS). Since then (almost 2 days now) no improper shutdowns occurred anymore on my DS114. So this might be a workaround.

I have an idea for those of you running cloud station server on your NAS, if the disabling of cloud station works and your NAS becomes stable, you could try uninstalling cloud station and installing the new Synology Drive package on your NAS. I installed it a few days ago and it works much like cloud station does, I suspect Synology is working toward replacing cloud station with Synology Drive. Anyways, I would also imagine that the Drive package is written with different code and maybe it wont cause the reboot issues.

Also an FYI when I updated my Synology office package, it automatically replaced my cloud station server with the new Synology Drive server, if you want to upgrade from Cloud station to drive, it might be easiest to just install the most recent version Synology Office package on your NAS and it is likely going to perform the replacement for you, so you get to keep your old file versions database, if you don't want Synology Office just uninstall that package after it is done installing the new Synology drive server

Keep in mind this is just a rough theory, but if you rely on cloud station, then leaving it disabled and waiting for Synology to come up with a fix is not acceptable so maybe my idea will work.
I hope this helps others out.
Cheers
bamboo
Trainee
Trainee
Posts: 15
Joined: Tue Jul 07, 2015 7:53 pm

Re: DSM 6.1.4-15217 Update 5

Postby bamboo » Wed Jan 10, 2018 9:21 am

Am I correct that when Cloud Station is replaced by Synology Drive client Cloud Station still works as before?
fremenik
Student
Student
Posts: 78
Joined: Mon Oct 08, 2012 6:12 pm
Location: Canada
Contact:

Re: DSM 6.1.4-15217 Update 5

Postby fremenik » Wed Jan 10, 2018 6:02 pm

bamboo wrote:Am I correct that when Cloud Station is replaced by Synology Drive client Cloud Station still works as before?

I can say that I just replaced my Synology Cloud station package with the cloud station drive package and the cloud station drive works as it did before when I had Cloud station running on my NAS, the package updated my windows client automatically and I had to re sync my windows machines with the NAS, but it worked rather fast. I also had to unlink and re link my mobile devices in the DS cloud app, but that DS cloud app sync also worked well. I hope that helps.
User avatar
windar
Sharp
Sharp
Posts: 162
Joined: Wed May 28, 2008 12:35 pm

Re: DSM 6.1.4-15217 Update 5

Postby windar » Thu Jan 11, 2018 11:45 pm

Hi all,

I have a feeling that DLNA on my NAS (DS114) has been impacted since updating to DSM 6.1.4-15217 Update 5.
The update was installed on december 23rd, I was absent for a few days following that, and then noticed (at some point between december 28 and 31) that DS Video on my android smartphone could not see my remote players/devices anymore. Same thing from Video Station launched in a browser on my Windows PC, only my Chromecast is detected.
The devices are a Samsung TV and Samsung Home Theater which have both been working for years with Video Station, but today (and for over 10 days now) I just cannot make them be seen by my NAS... :(
Nothing else has changed recently on my home network setup, I've tried rebooting just about everything, reset default settings on the Home Theater (with no luck), switched my HT connection from wired to wireless (and back), installed the Media Server synology package (which is not necessary for Video Station to function properly) and the TV and HT do not detect the NAS as a DLNA device on the network (this also worked with no problem a few years back), so this is why I'm thinking this is a DLNA related issue.
Note that I can also use the DS Video app on my Samsung Home Theater and THAT does work properly. I think this is because the connection method is different in this case and does not rely on DLNA (the app is a direct HTTP/HTTPS connection from HT to NAS, whereas DLNA automatically detects devices that broadcast their capabilities on the local network).

Just wondering if anyone out there is having a similar issue, before I dig deeper into this and end up considering rebuilding my whole setup from scratch... :)

Following are before/after (from 2017-03 and 2018-01) screenshots to illustrate the difference seen in the android app:
Image
Jungle Power !
elizarov
I'm New!
I'm New!
Posts: 4
Joined: Fri Jan 12, 2018 10:42 pm

Re: DSM 6.1.4-15217 Update 5

Postby elizarov » Fri Jan 12, 2018 10:53 pm

My DS412+ had auto updated to DSM 6.1.4-15217 Update 5 from DSM 6.1.4-15217 Update 3 automatically and immediately started seeing IO error an 3 drive in my raid array. From the log:

Information System 2017-12-23 04:48 admin Start install [DSM 6.1.4-15217 Update 5] automatically.
Information System 2017-12-23 04:49 admin Update was complete.
Warning System 2017-12-23 04:53 SYSTEM Bad sector was found on disk[1].
Warning System 2017-12-23 04:53 SYSTEM Bad sector was found on disk[3].
Warning System 2017-12-23 04:53 SYSTEM Bad sector was found on disk[2].
Warning System 2017-12-23 04:53 SYSTEM Bad sector was found on disk[3].
Warning System 2017-12-23 04:53 SYSTEM Bad sector was found on disk[2].
Warning System 2017-12-23 04:53 SYSTEM Bad sector was found on disk[2].
Warning System 2017-12-23 04:53 SYSTEM Bad sector was found on disk[1].
Warning System 2017-12-23 04:53 SYSTEM Bad sector was found on disk[3].
Warning System 2017-12-23 04:53 SYSTEM Bad sector was found on disk[3].
Warning System 2017-12-23 04:53 SYSTEM Bad sector was found on disk[1].
Warning System 2017-12-23 04:53 SYSTEM Bad sector was found on disk[1].
Warning System 2017-12-23 04:53 SYSTEM Bad sector was found on disk[2].

It is so bad, that I cannot reassemble array with mdamd. It suspiciously fails to read superblock. It reads it normally when I do `mdadm --examine <device>', but 'mdadm --assemble ...' results in the following errors (from dmesg):

[85674.902711] ata1.00: exception Emask 0x0 SAct 0x20000 SErr 0x0 action 0x0
[85674.909537] ata1.00: irq_stat 0x40000008
[85674.913560] ata1.00: failed command: READ FPDMA QUEUED
[85674.918837] ata1.00: cmd 60/08:88:e8:3e:90/00:00:00:00:00/40 tag 17 ncq 4096 in
res 41/40:00:ea:3e:90/00:00:00:00:00/40 Emask 0x409 (media error) <F>
[85674.934641] ata1.00: status: { DRDY ERR }
[85674.938759] ata1.00: error: { UNC }
[85674.943413] ata1.00: configured for UDMA/133
[85674.947785] sd 0:0:0:0: [sda] read unc at 9453290
[85674.952654] lba 9453290 start 9453280 end 7814023007
[85674.957653] sda5 auto_remap 0
[85674.960695] sd 0:0:0:0: [sda] Medium with UNC error
[85674.965627] sd 0:0:0:0: [sda]
[85674.968883] Result: hostbyte=0x00 driverbyte=0x08
[85674.973725] sd 0:0:0:0: [sda]
[85674.976999] Sense Key : 0x3 [current] [descriptor]
[85674.981925] Descriptor sense data with sense descriptors (in hex):
[85674.988223] 72 03 11 04 00 00 00 0c 00 0a 80 00 00 00 00 00
[85674.995006] 00 90 3e ea
[85674.998369] sd 0:0:0:0: [sda]
[85675.001610] ASC=0x11 ASCQ=0x4
[85675.004635] sd 0:0:0:0: [sda] CDB:
[85675.008213] cdb[0]=0x88: 88 00 00 00 00 00 00 90 3e e8 00 00 00 08 00 00
[85675.015412] end_request: I/O error, dev sda, sector 9453290
[85675.021107] ata1: EH complete
[85675.021215] md: disabled device sda5, could not read superblock.
[85675.021218] md: sda5 does not have a valid v1.2 superblock, not importing!
[85675.021230] md: md_import_device returned -22

I don't belive in coincides. All 3 device could not have failed immediately after update, so there is something wrong with the update. Is there any wait to roll it back to Update 3 that was previously working normally according to the logs?
jeroenvt
I'm New!
I'm New!
Posts: 3
Joined: Thu Dec 28, 2017 1:11 pm

Re: DSM 6.1.4-15217 Update 5

Postby jeroenvt » Sat Jan 13, 2018 6:14 pm

Today I downgraded to DSM 6.1.4-15217 Update 3, thinking the improper shutdowns were caused by Update 5. However, 15 minutes ago another improper shutdown occurred. I then realized that together with the DSM update, I also installed some package updates (Log Center, File Station, VPN Server and PHP 7.0). So maybe one of those is causing the improper shutdowns. I stopped all those packages except File Station (not possible to disable). So now I'll have to wait and see if the improper shutdowns no longer occur.
Last edited by jeroenvt on Sun Jan 14, 2018 1:37 am, edited 1 time in total.
joe002
Trainee
Trainee
Posts: 19
Joined: Wed Dec 17, 2014 2:51 am

Re: DSM 6.1.4-15217 Update 5

Postby joe002 » Sat Jan 13, 2018 6:17 pm

Two days ago I manually updated from DSM 6.0.2-8451 Update 2, to DSM 6.1.4-15217, to DSM 6.1.4-15217 Update 5 on my DS213j and DS413. No issues so far.
DS213j - 2x WD Red, RAID 1
DS413  - 4x WD Red, RAID 6
elizarov
I'm New!
I'm New!
Posts: 4
Joined: Fri Jan 12, 2018 10:42 pm

Re: DSM 6.1.4-15217 Update 5

Postby elizarov » Sun Jan 14, 2018 6:31 pm

I've recovered my array from hardware failure after DSM 6.1.4-15217 Update 5. I'll post more details to a separate topic here: https://forum.synology.com/enu/viewtopi ... 08#p514497

Now, here is my theory on how it is related to DSM Update.

The failure was happening right after the disk sector that stores RAID superblock, which is less than 1Kb in size. It looks like prior to this update, RAID superblock was read and written to disk in 1Kb batches. However, my drive's reported block size is 4Kb and it seems that somehow constantly writing just the first Kb of the block corrupted the rest 3Kb of the block. It might be some bug in the disk firmware, since all 3 disks had failed in exactly the same way. Anyway, what I was seeing is that in direct mode I can read normally the first kb (the first two sectors) that actually store superblock and cannot read the other 6 sectors (unrecoverable read error).

Mostly likely this disk read error was there for quite a while, but previous version of DSM software only read and written the first Kb. Somehow after the patch an attempt to assemble the RAID array my mdadm started trying to read the corrupted sectors right after the superblock and was failing. I've zeroed out the corrupted sectors and now its all fine.
grubbleglobe
I'm New!
I'm New!
Posts: 7
Joined: Sat Feb 25, 2017 5:38 pm

Re: DSM 6.1.4-15217 Update 5

Postby grubbleglobe » Fri Jan 19, 2018 3:49 pm

Hello,
I updated from 6.1.4-15217 update 1 directly to update 5 without issues (so far... keeping fingers crossed).

DS412+, stock unit, no third party RAM and running only File Station and Universal Search.

Return to “DiskStation Manager 6.1-15047 and onward versions”

Who is online

Users browsing this forum: No registered users and 2 guests