Skip to content

Instantly share code, notes, and snippets.

@ludoo0d0a
Created June 11, 2015 18:54
Show Gist options
  • Star 23 You must be signed in to star a gist
  • Fork 3 You must be signed in to fork a gist
  • Save ludoo0d0a/8d0cfd1cab22598cb5d8 to your computer and use it in GitHub Desktop.
Save ludoo0d0a/8d0cfd1cab22598cb5d8 to your computer and use it in GitHub Desktop.
Synology boot locked
Sometimes after a hard reboot (power cut), if your synology cannot be logged in with DSM and it shows "System is getting ready. Please log in later" , please do these steps :
#Admin login via ssh
> synobootseq --set-boot-done
> synobootseq --is-ready
#optional
> /usr/syno/etc/rc.d/S97apache-sys.sh start
> /usr/syno/etc/rc.d/S95sshd.sh start
@IIIdefconIII
Copy link

Thank you!

@theAusMenace
Copy link

Thanks, saved me

@xxdesmus
Copy link

xxdesmus commented Jan 8, 2023

You saved me as well.

@billyjbryant
Copy link

You saved my ass! Thanks so much for this!

@billyjbryant
Copy link

I expanded on this by creating a simple shell script that you can place in /usr/local/bin then execute from SSH:

https://gist.github.com/billyjbryant/993b4e8669659444006823a68f1bd509

@rajkumarindia
Copy link

I encountered the "System is getting ready" issue, and SSH wasn't enabled previously. After troubleshooting, here's what finally worked:

  1. Remove all hard drives and power on the Synology. It will boot into a blank state. Use either the IP address assigned by your router or visit "finds.synology.com" to discover the IP address.

  2. When the interface indicates "no HDD available," insert the hard drives one by one, allowing a 10-second gap for each insertion while the power is on and the Synology is live.

  3. Wait for 1 minute once all the disks come online, then proceed to install DSM from the web interface. It will install and restart.

  4. After booting, your old volumes should be accessible, but you'll need to reinstall all apps. However, all your data will remain intact, including active backup for business tasks and VMs, as well as previous backups.

  5. Snapshots already taken will be preserved, but you'll need to enable new scheduled snapshots.

It's a nerve-wracking process, but it worked for me. also will recomend repairing disks from storage console.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment