<?xml version="1.0" encoding="UTF-8"?><rss version="2.0"
	xmlns:content="http://purl.org/rss/1.0/modules/content/"
	xmlns:dc="http://purl.org/dc/elements/1.1/"
	xmlns:atom="http://www.w3.org/2005/Atom"
	xmlns:sy="http://purl.org/rss/1.0/modules/syndication/"
	
	>
<channel>
	<title>
	Comments on: Synology: &#8220;DSM updating in process&#8230;&#8221; forever	</title>
	<atom:link href="https://www.BeatificaBytes.be/synology-dsm-updating-in-process-forever/feed/" rel="self" type="application/rss+xml" />
	<link>https://www.BeatificaBytes.be/synology-dsm-updating-in-process-forever/</link>
	<description>The Joys of Computing</description>
	<lastBuildDate>Thu, 08 Jul 2021 09:05:30 +0000</lastBuildDate>
	<sy:updatePeriod>
	hourly	</sy:updatePeriod>
	<sy:updateFrequency>
	1	</sy:updateFrequency>
	<generator>https://wordpress.org/?v=6.8</generator>
	<item>
		<title>
		By: franck		</title>
		<link>https://www.BeatificaBytes.be/synology-dsm-updating-in-process-forever/#comment-315</link>

		<dc:creator><![CDATA[franck]]></dc:creator>
		<pubDate>Thu, 08 Jul 2021 09:05:30 +0000</pubDate>
		<guid isPermaLink="false">http://www.BeatificaBytes.be/wordpress/?p=2967#comment-315</guid>

					<description><![CDATA[sudo synoupgrade -patch synology_88f6282_112.pat

same pswd admin

best regards]]></description>
			<content:encoded><![CDATA[<p>sudo synoupgrade -patch synology_88f6282_112.pat</p>
<p>same pswd admin</p>
<p>best regards</p>
]]></content:encoded>
		
			</item>
		<item>
		<title>
		By: Christopher Smith		</title>
		<link>https://www.BeatificaBytes.be/synology-dsm-updating-in-process-forever/#comment-314</link>

		<dc:creator><![CDATA[Christopher Smith]]></dc:creator>
		<pubDate>Mon, 24 Jul 2017 04:31:25 +0000</pubDate>
		<guid isPermaLink="false">http://www.BeatificaBytes.be/wordpress/?p=2967#comment-314</guid>

					<description><![CDATA[I encountered this problem about an hour ago and found your post.  I was stuck for a while at the explicit path as I had browsed to a folder where I had downloaded the update (synology_88f6282_112.pat) and was trying to do the update by typing: 

synoupgrade -patch synology_88f6282_112.pat 

but it wasn&#039;t working until I realised as you stated it has to be the absolute path to the file so even though I had CD&#039;d to the folder I still had to type it out:

synoupgrade -patch /volume1/Downloads/synology_88f6282_112.pat 

It upgraded after that but upon reboot, would not boot up. I had to reinstall with synology assistant which was no fun, but my data was untouched thank God though I have a lot of reconfiguration to do!

Thank you for posting this and helping me and others!!]]></description>
			<content:encoded><![CDATA[<p>I encountered this problem about an hour ago and found your post.  I was stuck for a while at the explicit path as I had browsed to a folder where I had downloaded the update (synology_88f6282_112.pat) and was trying to do the update by typing: </p>
<p>synoupgrade -patch synology_88f6282_112.pat </p>
<p>but it wasn&#8217;t working until I realised as you stated it has to be the absolute path to the file so even though I had CD&#8217;d to the folder I still had to type it out:</p>
<p>synoupgrade -patch /volume1/Downloads/synology_88f6282_112.pat </p>
<p>It upgraded after that but upon reboot, would not boot up. I had to reinstall with synology assistant which was no fun, but my data was untouched thank God though I have a lot of reconfiguration to do!</p>
<p>Thank you for posting this and helping me and others!!</p>
]]></content:encoded>
		
			</item>
	</channel>
</rss>
