rellew

Transition Members
  • Content Count

    5
  • Joined

  • Last visited

Community Reputation

0 Neutral

About rellew

  • Rank
    Newbie
  1. It seems the usb flash drive was faulty. Did a new one with Jun's loader 1.03, network was working again with it and I could migrate my data after that. Gave me alot of trouble for nothing - if you should stumble over this thread, just make a backup of your config, create a new flash drive and install DSM over it to keep your data.
  2. It seems nobody knows about this bug or whatever failure here is happening. After reading a little bit in the forum someone mentioned to reinstall DSM, when you just delete the system partitions. I did this and I can still access my data with with ubuntu & fdisk, but I can't reinstall DSM. When i plug in my usb run the loader (tried reinstall, too) the diskstation can't be found in my network. I pulled the hard disks and bootet once more, but still nothing. Does anyone has a hint here? I just want to reinstall DSM on my disks and keep my data, but unfortunately I can't find my diskstation with the assistent.
  3. Hi all, I have a strange behaviour with my Microserver Gen8 with 6.2-23739 Update 2. All was working nice and without error for about half a year, when I've shut down the server for holiday. After that, started the server as normally, but when I tried to access the DSM on Port 5000 or 5001 the server was shutting down. The website was showing only the typical Synology log with the message, that the site couldn't be found. I connected with ssh and took a look. When doing the same thing I could see, that the session was aborted with the following message and the server was going down: sh-4.3# Connection to 192.168.178.20 closed by remote host. Connection to 192.168.178.20 closed. So I tried to investigate a little bit and took a look on the error logs of nginx, where I could these lines (/var/log/nginx/error.log) : 2019/04/15 21:24:09 [error] 13240#13240: *34 upstream prematurely closed connection while reading response header from upstream, client: 192.168.178.20, server: _, request: "GET / HTTP/2.0", upstream: "scgi://unix:/run/synoscgi.sock:", host: "192.168.178.15:5001" 2019/04/16 20:02:56 [error] 17294#17294: *1 upstream prematurely closed connection while reading response header from upstream, client: 192.168.178.20, server: _, request: "GET / HTTP/1.1", upstream: "scgi://unix:/run/synoscgi.sock:", host: "192.168.178.15:5000" Further I found these in the /var/log/syslog.log: 2019-04-16T19:40:46+02:00 Skyship syslog-ng[1275]: syslog-ng starting up; version='3.7.3' 2019-04-16T19:40:49+02:00 Skyship syslog-ng[1275]: Connection failed; fd='25', server='AF_UNIX(/var/run/synologan.sock)', local='AF_UNIX(anonymous)', error='No such file or directory (2)' 2019-04-16T19:40:49+02:00 Skyship syslog-ng[1275]: Initiating connection failed, reconnecting; time_reopen='10' 2019-04-16T19:40:49+02:00 Skyship syslog-ng[1275]: Configuration reload request received, reloading configuration; 2019-04-16T19:40:58+02:00 Skyship syslog-ng[1275]: Syslog connection established; fd='31', server='AF_UNIX(/var/run/synologan.sock)', local='AF_UNIX(anonymous)' 2019-04-16T20:02:56+02:00 Skyship syslog-ng[1275]: Syslog connection broken; fd='31', server='AF_UNIX(/var/run/synologan.sock)', time_reopen='10' 2019-04-16T20:03:06+02:00 Skyship syslog-ng[1275]: Connection failed; fd='46', server='AF_UNIX(/var/run/synologan.sock)', local='AF_UNIX(anonymous)', error='No such file or directory (2)' 2019-04-16T20:03:06+02:00 Skyship syslog-ng[1275]: Initiating connection failed, reconnecting; time_reopen='10' 2019-04-16T20:03:16+02:00 Skyship syslog-ng[1275]: Connection failed; fd='29', server='AF_UNIX(/var/run/synologan.sock)', local='AF_UNIX(anonymous)', error='No such file or directory (2)' 2019-04-16T20:03:16+02:00 Skyship syslog-ng[1275]: Initiating connection failed, reconnecting; time_reopen='10' 2019-04-16T20:03:26+02:00 Skyship syslog-ng[1275]: Connection failed; fd='49', server='AF_UNIX(/var/run/synologan.sock)', local='AF_UNIX(anonymous)', error='No such file or directory (2)' 2019-04-16T20:03:26+02:00 Skyship syslog-ng[1275]: Initiating connection failed, reconnecting; time_reopen='10' 2019-04-16T20:03:36+02:00 Skyship syslog-ng[1275]: Connection failed; fd='33', server='AF_UNIX(/var/run/synologan.sock)', local='AF_UNIX(anonymous)', error='No such file or directory (2)' 2019-04-16T20:03:36+02:00 Skyship syslog-ng[1275]: Initiating connection failed, reconnecting; time_reopen='10' 2019-04-16T20:03:43+02:00 Skyship syslog-ng[1275]: syslog-ng shutting down; version='3.7.3' Services are all up and running, data ist still there and as long as I don't try to use the web gui everything seems fine. But it seems the one service, which is faulty, is DSM. When I hard-stop it the server won't shutdown, but yeah...I can't access DSM logically. Hopefully anyone can help me out here. Thanks in advance for this great community! EDIT: I've already tried just to reinstall DSM with the method /etc.defaults/VERSION, but unfortunately when I try to reconfigure and adding the name, IP and password the server is going for a shutdown, because I'm using DSM and it seems I can't reconfigure, when I have the DSM service stopped.
  4. Good luck, berwhale. Would be great to hear from you and if everything went fine. Maybe this will help me get my open-vm-tools to work. Greetings
  5. Hi Sancome, thx for your efforts, but I get only errors when I'm trying to shutdown or reboot my XPEnology. Used both, the 9.4.6 and 9.10 versions, they both are installed fine in the XPEnology, but when I'm trying to shutdown or reboot the VM in ESXi I get these errors: Vix Errorcode 1 and 3009. Both must mean, that the script can't be run? Using ESXi 5.5 Update 2 and the latest 5.2 XPEnology Release. Hopefully you can help.