Search the Community
Showing results for tags 'dsm6.1.7'.
-
Hi, I am looking for some pointers for diagnostics please. Microserver was running DSM 5.1 so updated to 5.2-5967 and all was well. From there followed the tutorial to update to 6.1.4, then 6.1.7, and finally 6.1.7 update 3. Again all was well, tried some reboots everything worked. About 2 hrs later the DSM disappeared from the network, no web ui, no ssh. Finally pulled the power and restarted it, still doesn't appear nor does find.synology.com see it (not that I thought it would). So where do I go from here? I note that Juns loader has 3 options at startup, the default first one, reinstall as a second option, and the third is a VMWare/ESXI option. If I opt for the 2nd does that put the system back into the "migration" state and allow me to re-install 6.1.7 from .pat ? How about volume1, is data retained (I don't want to lose it). With the previous loaders I might have logged in on the local terminal to see what is happening, but with Juns all I see is "booting kernel" (the same as I see when it is all working) I'm scratching my head at the moment as everything seemed fine, then its just fallen completely on it ar$e... Thanks!