New Members
  • Content Count

  • Joined

  • Last visited

Community Reputation

0 Neutral

About apelders

  • Rank

Recent Profile Visitors

The recent visitors block is disabled and is not being shown to other users.

  1. Maybe my scenario can help you. See post "Recover a bricked system after DSM 6.1.1 upgrade accident"
  2. I just posted a scenario which can help you if you have an spare disk. Look for here:
  3. It happens already two times to me that I upgraded my Syno and ended up with an unresponsive system. The last time I updated my system (which was already on DSM 6.1, and I was not aware that this was a dangerous upgrade) to the latest version DSM 6.1.1. The update seems succesfull until a few days later I noticed I could not contact my shared drives anymore. The diskstation could not be found by the Synology Assistant anymore. This scenario in the end helped me to recover my NAS and return back to DSM 6.1 It also should work for other mistakes resulting in unbootable or unresponsive systems. I have a HP gen8 server with one disk and one volume and another older Synology acting as a rsync backup destination. To prove what the real problem was, i turned off the Syno and took out the harddisk. Then I booted up the Syno again and it was possible to find my Syno with Synology Assistant. I connected using the web interface and it offered me to install a new Synology server. When I instructed to do a manual install with DSM_DS3615xs_15047.pat the installer refused and asked me to install 15101, so the USB stick seems to be updated to the new version already. After bringing down the system, I put a fresh v1.02a image on the USB stick and placed it back into the HP gen8. I also put in an complete empty hardddisk (I first removed all partititions using a PC) and booted the system with a regular boot. After the Synology Assistant found my DiskStation, I opened the web interface and did a manual install using DSM_DS3615xs_15047.pat which resulted in a functional DSM 6.1 system! I did not create any volume, just installed the system and after I found out that a reboot was successfull I placed my bricked disk with all my data next to the disk I just installed with a fresh 6.1 image. After rebooting (and have some patience) Storage Manager noticed a disk with a corrupt partition and offered to repair it for you. This is the trick who will recover your system, but be aware that you have to reinstall your apps and reconfigure some things or restore a system configuration after all. Now the system partitions of your fresh DSM 6.1 system will by copied to the "corrupted" disk and shortly after that the system will respond with System is healthy. This is great news!! Now you can bring the system down gently and take out both disk and put your disk with all your valuable data in the first slot and reboot again. With a relief you will notice that the system will nicely boot and your disk is back on DSM 6.1 again. To make the recovery complete I had to reinstall my previous installed packages and I had to recover my rsync task in Hyper Backup. This takes a while because Hyper Backup has to read back the whole index from my backup station. The Photo Station also has to reindex but that will be done at a glance. I restored my system settings (Configuration Backup) which I made months ago after successfull install of 6.1 in the way I just described with a new disk. This backup I stored on my old backup Synology server in a shared folder. So I'm a happy user with a working DSM6.1 system who has learned not to update without special attention anymore. I will wait until there are signs that 6.1.1 should be able to funcion on my gen8, but I will first start to practice using VMware and then with an empty disk. Then I will give it a try to upgrade my existing disk with data using the method I described here. I can recommend everyone to have a backup of all your data on another system in another location with a regular sync. You will not be afraid to lose your data when you got into trouble and that helps you to try some new & risky scenarios. This method is not new in this forum. I found it on the Russian forum section I believe and with Google Translate I was able to understand and perform it with good results. Please respond to this topic if you have questions or doubts.
  4. I updated my HP Proliant MicroServer Gen8 to v5.2-5644 and got it working. After I manually uploaded the correct PAT file (DS3615xs) the system rebooted and I told in the XPENboot menu that I want to upgrade (option 3). The syno upgrade assistant noticed I moved my disks ( ???) and that it has to upgrade the DSM system. ( OK??) I followed the default options and after a new reboot of the system I let it go (boot option 1). Everything fine. No data or config settings lost as far as I can see. Pfew.