unmesh Posted May 12, 2020 Share #1 Posted May 12, 2020 When initiated from the DSM GUI, the OS appears to shut down but not all the way as shown by the Vmware GUI. I set up a serial-over-LAN console and got the follwing output [ 357.190206] init: synonetd main process (5393) killed by TERM signal [ 357.192923] init: ddnsd main process (9158) terminated with status 1 [ 357.200603] init: synostoraged main process (9417) terminated with status 15 [ 357.218126] init: hotplugd main process (9940) killed by TERM signal [ 357.233112] init: smbd main process (10212) killed by TERM signal System is going to poweroff. [ 361.195232] init: synoscheduler-vmtouch main process (11420) killed by TERM signal [ 361.290355] init: Disconnected from D-Bus system bus [ 364.414348] iSCSI:extent_pool.c:780:ep_exit syno_extent_pool successfully finalized [ 364.416200] iSCSI:target_core_rodsp_server.c:844:rodsp_server_exit RODSP server stopped. [ 364.479316] EXT4-fs (md2): re-mounted. Opts: (null) [ 364.601074] init: skip respawn syslog-ng during shutdown [ 365.534343] md2: detected capacity change from 29421993984 to 0 [ 365.535315] md: md2: set sdb3 to auto_remap [0] [ 365.536008] md: md2 stopped. [ 365.536456] md: unbind<sdb3> [ 365.536974] md: export_rdev(sdb3) [ 366.678609] md: md0 in immediate safe mode [ 366.679304] md: md1 in immediate safe mode [ 366.681192] init: cgmanager main process (4717) killed by KILL signal [ 366.682227] init: skip respawn cgmanager during shutdown [ 366.683194] init: dhcp-client (eth0) main process (7474) killed by KILL signal [ 366.684645] init: tty main process (10168) killed by KILL signal [ 366.685720] init: skip respawn tty during shutdown [ 366.688852] init: Failed to spawn dhcp-client (eth0) post-stop process: unable to connect to CGManager: Unknown error 196609 [ 366.727126] EXT4-fs (md0): re-mounted. Opts: (null) [ 367.767601] sd 1:0:0:0: [sdb] Stopping disk [ 367.768376] sd 0:0:0:0: [sdm] Stopping disk [ 367.769306] e1000e: EEE TX LPI TIMER: 00000000 [ 367.805455] e1000e 0000:03:00.0: Refused to change power state, currently in D0 Any thoughts on what might be the cause? Running Jun's 1.03b bootloader and the latest DS3615xs DSM with a virtual hard drive Quote Link to comment Share on other sites More sharing options...
luchuma Posted May 12, 2020 Share #2 Posted May 12, 2020 do you have openvtools installed? Quote Link to comment Share on other sites More sharing options...
unmesh Posted May 12, 2020 Author Share #3 Posted May 12, 2020 Yes, open-vm-tools_x64-6.1_10.2.0-1 Quote Link to comment Share on other sites More sharing options...
Recommended Posts
Join the conversation
You can post now and register later. If you have an account, sign in now to post with your account.