• 0

hp microserver gen 8 - recovered after upgrade but DSM not loading


Go to solution Solved by wanye,

Question

ok, i have a bare metal gen8 microserver i accidentally upgraded from 5.2 to 6.2.2 (i didnt click manual install, so it grabbed the latest version and installed) and bricked it. fiddled with trying to roll it back and a few other bits, but nothing really worked.

 

anyway. an external NIC arrived today, and i've been wrestling with it all day. after setting up a new sd card with ds3615_6.2 synoboot.img, setting vid/pic/sn/mac1/mac2 in grub, starting in recovery mode. it then doesnt re-detect it after the recovery reboot.

 

it is now back to a stage where most things are loading (plex/etc) but DSM on port 5000 isnt loading, find.synology.com and the synology assistant are saying theres no devices found on my network. 

 

i can ssh in and the packages seem ok, however i have an SHR array of 4 disks, and im getting errors in the apps saying 'missing folder', yet when i navigate to it in the ssh window, it all seems to be there, but as i cant get DSM to load, i'm having trouble making sure the array is ok.

 

scemd and/or nginx seem to be the culprits, right? (see services below)

 

anyway, some logfiles in case they are any help:

 

Spoiler

/var/log/synoservice.log:

2020-03-30T16:52:14+01:00 DiskStation synoservice: service_reload.c:20 synoservice: reload [ftpd-ssl].
2020-03-30T16:52:14+01:00 DiskStation synoservice: service_reload.c:33 synoservice: [ftpd-ssl] is not enabled, skip reload action
2020-03-30T16:52:14+01:00 DiskStation synoservice: service_reload.c:46 synoservice: finish reload [ftpd-ssl].
2020-03-30T16:52:14+01:00 DiskStation synoservice: service_reload.c:20 synoservice: reload [ftpd-ssl].
2020-03-30T16:52:14+01:00 DiskStation synoservice: service_reload.c:33 synoservice: [ftpd-ssl] is not enabled, skip reload action
2020-03-30T16:52:14+01:00 DiskStation synoservice: service_reload.c:46 synoservice: finish reload [ftpd-ssl].
2020-03-30T16:52:14+01:00 DiskStation synoservice: service_stop.c:23 synoservice: [synowifid] stopping ...
2020-03-30T16:52:14+01:00 DiskStation synoservice: service_stop.c:38 synoservice: [synowifid] is already stopped.
2020-03-30T16:52:14+01:00 DiskStation synoservice: service_stop.c:86 synoservice: [synowifid] stopped.
2020-03-30T16:52:14+01:00 DiskStation synoservice: service_reload.c:20 synoservice: reload [syslog-ng].
2020-03-30T16:52:19+01:00 DiskStation synoservice: service_restart.c:21 synoservice: restart [synotunnel] ...
2020-03-30T16:52:19+01:00 DiskStation synoservice: service_restart.c:34 synoservice: [synotunnel] is not enabled, skip restart action ...
2020-03-30T16:52:19+01:00 DiskStation synoservice: service_restart.c:52 synoservice: finish restart [synotunnel].
2020-03-30T16:52:19+01:00 DiskStation synoservice: service_reload.c:20 synoservice: reload [nginx].
2020-03-30T16:52:19+01:00 DiskStation synoservice: service_reload.c:46 synoservice: finish reload [nginx].
2020-03-30T16:52:19+01:00 DiskStation synoservice: service_restart.c:21 synoservice: restart [synotunnel] ...
2020-03-30T16:52:19+01:00 DiskStation synoservice: service_restart.c:34 synoservice: [synotunnel] is not enabled, skip restart action ...
2020-03-30T16:52:19+01:00 DiskStation synoservice: service_restart.c:52 synoservice: finish restart [synotunnel].
2020-03-30T16:52:22+01:00 DiskStation synoservice: service_restart.c:21 synoservice: restart [synotunnel] ...
2020-03-30T16:52:22+01:00 DiskStation synoservice: service_restart.c:34 synoservice: [synotunnel] is not enabled, skip restart action ...
2020-03-30T16:52:22+01:00 DiskStation synoservice: service_restart.c:52 synoservice: finish restart [synotunnel].
2020-03-30T16:52:22+01:00 DiskStation synoservice: service_restart.c:21 synoservice: restart [synotunnel] ...
2020-03-30T16:52:22+01:00 DiskStation synoservice: service_restart.c:34 synoservice: [synotunnel] is not enabled, skip restart action ...
2020-03-30T16:52:22+01:00 DiskStation synoservice: service_restart.c:52 synoservice: finish restart [synotunnel].
2020-03-30T16:52:30+01:00 DiskStation synoservice: service_resume_by_reason.c:12 synoservice: resume [synologanalyzer] by reason [volume-action-hook] ...

2020-03-30T16:52:30+01:00 DiskStation s2s_volume_hook: service_start.c:74 synoservice: [s2s_daemon] starting ...
2020-03-30T16:52:30+01:00 DiskStation synoservice: service_reload.c:20 synoservice: reload [nginx].
2020-03-30T16:52:30+01:00 DiskStation s2s_volume_hook: service_start.c:178 synoservice: [s2s_daemon] started.
2020-03-30T16:52:30+01:00 DiskStation synoservice: service_reload.c:46 synoservice: finish reload [nginx].
2020-03-30T16:52:36+01:00 DiskStation synoservice: service_resume_by_reason.c:12 synoservice: resume [synologanalyzer] by reason [volume-action-hook] ...
2020-03-30T16:52:37+01:00 DiskStation synoservice: service_resume_by_reason.c:12 synoservice: resume [synologanalyzer] by reason [volume-action-hook] ...
2020-03-30T16:52:37+01:00 DiskStation synoservice: SYSTEM: Last message 'service_resume_by_re' repeated 1 times, suppressed by syslog-ng on DiskStation
2020-03-30T16:52:37+01:00 DiskStation synoservice: service_reload.c:20 synoservice: reload [synosnmpcd].
2020-03-30T16:52:37+01:00 DiskStation synoservice: service_reload.c:46 synoservice: finish reload [synosnmpcd].
2020-03-30T16:52:37+01:00 DiskStation synoservice: service_resume_by_reason.c:12 synoservice: resume [synologanalyzer] by reason [volume-action-hook] ...
2020-03-30T16:52:39+01:00 DiskStation synoservice: service_restart.c:21 synoservice: restart [nmbd] ...
2020-03-30T16:52:40+01:00 DiskStation synoservice: service_restart.c:52 synoservice: finish restart [nmbd].
2020-03-30T16:52:40+01:00 DiskStation synoservice: service_restart.c:21 synoservice: restart [avahi] ...
2020-03-30T16:52:40+01:00 DiskStation synoservice: service_restart.c:52 synoservice: finish restart [avahi].
2020-03-30T16:53:10+01:00 DiskStation synoservice: service_pause_by_reason.c:11 synoservice: pause [avahi] by reason [ipv4_change] ...
2020-03-30T16:53:10+01:00 DiskStation synoservice: service_pause.c:23 synoservice: [avahi] pausing ...
2020-03-30T16:53:11+01:00 DiskStation synoservice: service_pause.c:79 synoservice: [avahi] paused.
2020-03-30T16:53:12+01:00 DiskStation synoservice: service_restart.c:21 synoservice: restart [synotunnel] ...
2020-03-30T16:53:12+01:00 DiskStation synoservice: service_restart.c:34 synoservice: [synotunnel] is not enabled, skip restart action ...
2020-03-30T16:53:12+01:00 DiskStation synoservice: service_restart.c:52 synoservice: finish restart [synotunnel].
2020-03-30T16:53:12+01:00 DiskStation synoservice: service_resume_by_reason.c:12 synoservice: resume [avahi] by reason [ipv4_change] ...
2020-03-30T16:53:12+01:00 DiskStation synoservice: service_restart.c:21 synoservice: restart [ssdp] ...
2020-03-30T16:53:12+01:00 DiskStation synoservice: service_restart.c:21 synoservice: restart [pppoerelay] ...
2020-03-30T16:53:12+01:00 DiskStation synoservice: service_restart.c:21 synoservice: restart [nmbd] ...
2020-03-30T16:53:12+01:00 DiskStation synoservice: service_start.c:74 synoservice: [avahi] starting ...
2020-03-30T16:53:13+01:00 DiskStation synoservice: service_start.c:178 synoservice: [avahi] started.
2020-03-30T16:53:13+01:00 DiskStation synoservice: service_reload.c:20 synoservice: reload [nginx].
2020-03-30T16:53:13+01:00 DiskStation synoservice: service_restart.c:52 synoservice: finish restart [pppoerelay].
2020-03-30T16:53:13+01:00 DiskStation synoservice: service_restart.c:52 synoservice: finish restart [nmbd].
2020-03-30T16:53:13+01:00 DiskStation synoservice: service_reload.c:46 synoservice: finish reload [nginx].
2020-03-30T16:53:13+01:00 DiskStation synoservice: service_restart.c:21 synoservice: restart [winbindd] ...
2020-03-30T16:53:13+01:00 DiskStation synoservice: service_restart.c:34 synoservice: [winbindd] is not enabled, skip restart action ...
2020-03-30T16:53:13+01:00 DiskStation synoservice: service_restart.c:52 synoservice: finish restart [winbindd].
2020-03-30T16:53:14+01:00 DiskStation synoservice: service_restart.c:52 synoservice: finish restart [ssdp].
2020-03-30T17:17:08+01:00 DiskStation synoservice: service_reload.c:20 synoservice: reload [nginx].
2020-03-30T17:17:08+01:00 DiskStation synoservice: service_reload.c:46 synoservice: finish reload [nginx].
2020-03-30T17:27:18+01:00 DiskStation synoservice: service_reload.c:20 synoservice: reload [nginx].
2020-03-30T17:27:18+01:00 DiskStation synoservice: service_reload.c:46 synoservice: finish reload [nginx].

 

 

Spoiler

root@DiskStation:~# synoservice -status

Service [avahi] status=[enable]

required upstart job: 

[avahi] is start. 

=======================================

Service [miniupnpd-handler] status=[disable]

required upstart job: 

[miniupnpd-handler] is stop. 

=======================================

Service [pkgctl-Docker] status=[disable]

required upstart job: 

[pkgctl-Docker] is stop. 

=======================================

Service [ups-usb] status=[disable]

required upstart job: 

[upsd-usb-adapter] is stop. 

=======================================

Service [pkgctl-SurveillanceStation] status=[disable]

required upstart job: 

[pkgctl-SurveillanceStation] is stop. 

=======================================

service [findhost] status=[error]

required upstart job: 

[findhostd] is stop. 

=======================================

Service [hotplugd] status=[enable]

required upstart job: 

[hotplugd] is start. 

=======================================

Service [synosnmpcd] status=[enable]

required upstart job: 

[synosnmpcd] is start. 

=======================================

Service [pkgctl-OpenHAB-demo-configuration] status=[enable]

required upstart job: 

[pkgctl-OpenHAB-demo-configuration] is start. 

=======================================

Service [synonetd] status=[enable]

required upstart job: 

[synonetd] is start. 

=======================================

Service [cups-lpd] status=[disable]

required upstart job: 

[cups-lpd] is stop. 

[inetd] is stop. 

=======================================

Service [syslog-acc] status=[enable]

required upstart job: 

[syslog-acc] is start. 

=======================================

Service [manutild] status=[disable]

required upstart job: 

[manutild] is stop. 

=======================================

Service [pkgctl-nzbdrone] status=[enable]

required upstart job: 

[pkgctl-nzbdrone] is start. 

=======================================

Service [s2s_daemon] status=[enable]

required upstart job: 

[s2s_daemon] is start. 

=======================================

Service [support-remote-access] status=[disable]

required upstart job: 

[synorelayd] is stop. 

=======================================

Service [pkgctl-JavaManager] status=[disable]

required upstart job: 

[pkgctl-JavaManager] is stop. 

=======================================

Service [nmbd] status=[enable]

required upstart job: 

[nmbd] is start. 

=======================================

Service [ldap-server] status=[disable]

required upstart job: 

[slapd-adapter] is stop. 

=======================================

Service [telnetd] status=[disable]

required upstart job: 

[telnetd] is stop. 

[inetd] is stop. 

=======================================

Service [synoconfd] status=[enable]

required upstart job: 

[synoconfd] is start. 

=======================================

Service [pkgctl-radarr] status=[enable]

required upstart job: 

[pkgctl-radarr] is start. 

=======================================

Service [nfsd] status=[disable]

required upstart job: 

[nfsd-adapter] is stop. 

=======================================

Service [crond] status=[enable]

required upstart job: 

[crond] is start. 

=======================================

Service [pkgctl-SqueezeCenter] status=[disable]

required upstart job: 

[pkgctl-SqueezeCenter] is stop. 

=======================================

Service [rsyncd] status=[disable]

required upstart job: 

[rsyncd-adapter] is stop. 

[sshd] is start. 

=======================================

Service [synogpoclient] status=[enable]

required upstart job: 

[synogpoclient] is start. 

=======================================

Service [synocrond] status=[enable]

required upstart job: 

[synocrond] is start. 

=======================================

Service [synotunnel] status=[disable]

required upstart job: 

[synotunnel] is stop. 

=======================================

Service [tftp] status=[disable]

required upstart job: 

[opentftp] is stop. 

=======================================

Service [ntpd-client] status=[enable]

required upstart job: 

[ntpd] is start. 

=======================================

Service [syslog-notify] status=[enable]

required upstart job: 

[syslog-ng] is start. 

[syslog-notify] is start. 

=======================================

Service [pkgctl-OpenHAB] status=[enable]

required upstart job: 

[pkgctl-OpenHAB] is start. 

=======================================

Service [pkgctl-Plex Media Server] status=[enable]

required upstart job: 

[pkgctl-Plex Media Server] is start. 

=======================================

Service [pkgctl-TimeBackup] status=[disable]

required upstart job: 

[pkgctl-TimeBackup] is stop. 

=======================================

Service [dbus] status=[enable]

required upstart job: 

[dbus-system] is start. 

[dbus-session] is start. 

=======================================

Service [synorelayd] status=[disable]

required upstart job: 

[synorelayd] is stop. 

=======================================

Service [synoindexd] status=[enable]

required upstart job: 

[synoindexd] is start. 

=======================================

Service [dc-output] status=[enable]

required upstart job: 

[dc-output] is start. 

=======================================

Service [synowstransfer] status=[disable]

required upstart job: 

[synowstransfer-adapter] is stop. 

=======================================

Service [synoagentregisterd] status=[disable]

required upstart job: 

[synoagentregisterd] is stop. 

=======================================

Service [apparmor] status=[enable]

required upstart job: 

[apparmor] is start. 

=======================================

Service [ftpd] status=[disable]

required upstart job: 

[ftpd] is stop. 

[ftpd-pure] is stop. 

=======================================

Service [ddns] status=[disable]

required upstart job: 

[ddnsd] is stop. 

=======================================

Service [nslcd] status=[disable]

required upstart job: 

[nslcd] is stop. 

=======================================

Service [synocachepinfiletool] status=[enable]

required upstart job: 

[synocachepinfiletool] is stop. 

=======================================

Service [DSM] status=[enable]

required upstart job: 

[synoscgi] is start. 

=======================================

Service [btacd] status=[disable]

required upstart job: 

[btacd] is stop. 

=======================================

Service [usbipd] status=[disable]

required upstart job: 

[usbipd] is stop. 

=======================================

Service [synomkthumbd] status=[enable]

required upstart job: 

[synomkthumbd] is start. 

=======================================

Service [synocontentextractd] status=[disable]

required upstart job: 

[synocontentextractd] is stop. 

=======================================

Service [synoperfeventd] status=[disable]

required upstart job: 

[synoperfeventd] is stop. 

=======================================

Service [synomount] status=[enable]

required upstart job: 

[synomount] is start. 

=======================================

Service [synoovs-db] status=[disable]

required upstart job: 

[synoovs-db] is stop. 

=======================================

Service [atalk] status=[enable]

required upstart job: 

[netatalk] is start. 

=======================================

Service [pgsql] status=[enable]

required upstart job: 

[pgsql-adapter] is start. 

=======================================

Service [pkgctl-deluge] status=[enable]

required upstart job: 

[pkgctl-deluge] is start. 

=======================================

Service [heartbeat] status=[disable]

required upstart job: 

[heartbeatd] is stop. 

=======================================

Service [synowifid] status=[disable]

required upstart job: 

[synowifid] is stop. 

=======================================

Service [pkgctl-AudioStation] status=[disable]

required upstart job: 

[pkgctl-AudioStation] is stop. 

=======================================

Service [pkgctl-python] status=[enable]

required upstart job: 

[pkgctl-python] is start. 

=======================================

Service [synologanalyzer] status=[enable]

required upstart job: 

[synologand] is start. 

=======================================

Service [ftpd-ssl] status=[disable]

required upstart job: 

[ftpd] is stop. 

[ftpd-ssl] is stop. 

=======================================

Service [pppoerelay] status=[enable]

required upstart job: 

[pppoerelay] is start. 

=======================================

service [gcpd] status=[pause]

required upstart job: 

[gcpd] is stop. 

=======================================

Service [upnpd] status=[disable]

required upstart job: 

[upnpd] is stop. 

=======================================

Service [sftp] status=[disable]

required upstart job: 

[sshd] is start. 

[ssh-sftp] is stop. 

=======================================

Service [synoovs-vswitch] status=[disable]

required upstart job: 

[synoovs-vswitch] is stop. 

=======================================

Service [synostoraged] status=[enable]

required upstart job: 

[synostoraged] is start. 

=======================================

Service [synocgid] status=[enable]

required upstart job: 

[synocgid] is start. 

=======================================

Service [pkgctl-nzbget] status=[enable]

required upstart job: 

[pkgctl-nzbget] is start. 

=======================================

Service [bonjour] status=[disable]

required upstart job: 

[bonjour] is stop. 

=======================================

Service [cupsd] status=[disable]

required upstart job: 

[cupsd] is stop. 

=======================================

Service [synotifyd] status=[disable]

required upstart job: 

[synotifyd] is stop. 

=======================================

Service [syslog-ng] status=[enable]

required upstart job: 

[syslog-ng] is start. 

=======================================

Service [natpmpd] status=[disable]

required upstart job: 

[natpmpd] is stop. 

=======================================

Service [sssd] status=[disable]

required upstart job: 

[sssd] is stop. 

=======================================

Service [bluetoothd] status=[disable]

required upstart job: 

[bluetoothd] is stop. 

=======================================

service [scemd] status=[error]

required upstart job: 

[scemd] is stop. 

=======================================

service [nginx] status=[error]

required upstart job: 

[nginx] is stop. 

=======================================

Service [synomkflvd] status=[enable]

required upstart job: 

[synomkflvd] is start. 

=======================================

Service [pkgctl-mono] status=[enable]

required upstart job: 

[pkgctl-mono] is start. 

=======================================

Service [synovpnclient] status=[enable]

required upstart job: 

[synovpnclient] is start. 

=======================================

Service [winbindd] status=[disable]

required upstart job: 

[winbindd] is stop. 

=======================================

Service [snmp] status=[enable]

required upstart job: 

[snmpd] is start. 

=======================================

Service [pkgctl-Perl] status=[disable]

required upstart job: 

[pkgctl-Perl] is stop. 

=======================================

Service [synopyntlmd] status=[disable]

required upstart job: 

[synopyntlmd] is stop. 

=======================================

Service [ntpd-server] status=[enable]

required upstart job: 

[ntpd] is start. 

=======================================

Service [samba] status=[enable]

required upstart job: 

[smbd] is start. 

=======================================

Service [iscsitrg] status=[enable]

required upstart job: 

[iscsitrg-adapter] is start. 

=======================================

Service [ssh-shell] status=[enable]

required upstart job: 

[ssh-shell] is start. 

[sshd] is start. 

=======================================

Service [synocacheclient] status=[enable]

required upstart job: 

[synocacheclient] is start. 

=======================================

Service [synologrotate] status=[enable]

required upstart job: 

[synologrotated] is start. 

=======================================

Service [ups-net] status=[disable]

required upstart job: 

[upsd-net-adapter] is stop. 

=======================================

Service [ssdp] status=[enable]

required upstart job: 

[minissdpd] is start. 

=======================================

Service [synobackupd] status=[enable]

required upstart job: 

[synobackupd] is start. 

=======================================

 

 

Spoiler

==> /var/log/messages <==

2020-03-30T17:35:52+01:00 DiskStation afpd[25414]: [dsi_tcp.c:473-E] dsi_tcp_init: no suitable network config for TCP socket

2020-03-30T17:35:52+01:00 DiskStation afpd[25414]: [afp_config.c:229-E] no suitable network address found, use "afp listen" or "afp interfaces"

2020-03-30T17:35:52+01:00 DiskStation afpd[25414]: [main.c:448-E] main: no servers configured

2020-03-30T17:35:52+01:00 DiskStation afpd[25418]: [dsi_tcp.c:473-E] dsi_tcp_init: no suitable network config for TCP socket

2020-03-30T17:35:52+01:00 DiskStation afpd[25418]: [afp_config.c:229-E] no suitable network address found, use "afp listen" or "afp interfaces"

2020-03-30T17:35:52+01:00 DiskStation afpd[25418]: [main.c:448-E] main: no servers configured

2020-03-30T17:35:54+01:00 DiskStation afpd[25421]: [dsi_tcp.c:473-E] dsi_tcp_init: no suitable network config for TCP socket

2020-03-30T17:35:54+01:00 DiskStation afpd[25421]: [afp_config.c:229-E] no suitable network address found, use "afp listen" or "afp interfaces"

2020-03-30T17:35:54+01:00 DiskStation afpd[25421]: [main.c:448-E] main: no servers configured

 

 

Spoiler

root@DiskStation:/var/log/nginx# more /var/log/nginx/error.log 
2020/03/30 13:36:08 [emerg] 13082#13082: socket() [::]:5000 failed (97: Address family not supported by protocol)
2020/03/30 13:36:09 [emerg] 13281#13281: socket() [::]:5000 failed (97: Address family not supported by protocol)
2020/03/30 13:36:09 [notice] 13286#13286: signal process started
2020/03/30 13:36:09 [error] 13286#13286: invalid PID number "" in "/run/nginx.pid"
2020/03/30 14:15:00 [emerg] 13726#13726: socket() [::]:5000 failed (97: Address family not supported by protocol)
2020/03/30 14:15:00 [emerg] 13768#13768: socket() [::]:5000 failed (97: Address family not supported by protocol)
2020/03/30 14:15:00 [notice] 13773#13773: signal process started
2020/03/30 14:15:00 [error] 13773#13773: invalid PID number "" in "/run/nginx.pid"
2020/03/30 14:48:16 [emerg] 13258#13258: socket() [::]:5000 failed (97: Address family not supported by protocol)
2020/03/30 14:48:16 [emerg] 13316#13316: socket() [::]:5000 failed (97: Address family not supported by protocol)
2020/03/30 14:48:16 [notice] 13327#13327: signal process started
2020/03/30 14:48:16 [error] 13327#13327: invalid PID number "" in "/run/nginx.pid"
2020/03/30 15:36:52 [emerg] 13156#13156: socket() [::]:5000 failed (97: Address family not supported by protocol)
2020/03/30 15:36:52 [emerg] 13181#13181: socket() [::]:5000 failed (97: Address family not supported by protocol)
2020/03/30 15:36:52 [notice] 13192#13192: signal process started
2020/03/30 15:36:52 [error] 13192#13192: invalid PID number "" in "/run/nginx.pid"
2020/03/30 16:52:34 [emerg] 12321#12321: socket() [::]:5000 failed (97: Address family not supported by protocol)
2020/03/30 16:52:34 [emerg] 12451#12451: socket() [::]:5000 failed (97: Address family not supported by protocol)
2020/03/30 16:52:34 [notice] 12458#12458: signal process started
2020/03/30 16:52:34 [error] 12458#12458: invalid PID number "" in "/run/nginx.pid"
2020/03/30 17:47:03 [emerg] 28121#28121: socket() [::]:5000 failed (97: Address family not supported by protocol)
2020/03/30 17:47:03 [emerg] 28130#28130: socket() [::]:5000 failed (97: Address family not supported by protocol)
2020/03/30 17:47:03 [notice] 28135#28135: signal process started
2020/03/30 17:47:03 [error] 28135#28135: invalid PID number "" in "/run/nginx.pid"

 

 

Spoiler

root@DiskStation:/var/log/nginx# synoservice -start nginx
service [nginx] start failed, synoerr=[0x0000]

 

 

Spoiler

root@DiskStation:/var/log/nginx# synoscgi
Copyright (c) 2003-2019 Synology Inc. All rights reserved.

Usage: synoscgi (Version 24922)
	--help: this help
	--mode: scgi|apid (required) run as synoscgi or synoapid

	scgi related params:
	--idle-child={childNumber} (optional, default: 10) max idle child number
	--max-child={childNumber} (optional, default: 65535) max child number

	apid related params:
	--conf (required) apid config realpath

 

Edited by Polanskiman
Added spoiler tag. Post was excessively long.
Link to post
Share on other sites

22 answers to this question

Recommended Posts

  • 0
  • Solution
Posted (edited)

ok, back up and running mostly! heres how in case anyone else has a similar problem in future.....

 

to "fix" i flash my boot microsd card with jun's 6.2 loader for DS3615xs - v1.03b and downloaded DSM_DS3615xs_24922.pat off the synology firmware site

 

booted, pressed C when the grub boot menu appeared and set vid/pid/sn (a new generated one from https://xpenogen.github.io/serial_generator/index.html )/mac1/mac2 and booted the second (recovery) option.

after a few mins, it was detectable in synology assistant (and the find.synology.com site)... from there i was able to choose REINSTALLATION from the select install type menu. i then pointed it manually at the 24922 pat file. it formatted system partitions, then copied the contents of the PAT file. after around 10 mins i wasnt able to connect.

 

at this point i discovered the server wouldnt properly shut down/reboot, so i had to power it off/on manually. it used to work ok with the original install, any idea whats changed, or what i need to do to sort that out?

 

after the reboot, the server appeared again in synology assistant, and i was able to connect and set it back up from scratch. i'm now going through and trying to remember how i had things configured (i only backed up a couple of apps configs. doh!)

 

so yeah. i'm back up. thanks! but if anyone knows why it isnt shutting down/rebooting, that would be useful, i dont want to have to go into the basement comms cab each time i need to reboot it :)

 

its a hp microserver gen8 and it worked ok on 5.2, and i've not changed any bios settings or anything. when SSHing onto it, even a sudo shutdown -h now just kills the ssh connection, and i have to manually power it off.

 

cheers

 

 

 

 

 

Edited by wanye
Link to post
Share on other sites
  • 0

after reading this: 

 

i figured i should grab the PAT file for my box, and extract libsynopkg.so.1  and  libsynoshare.so.6 and copy to /lib.... but when i extract the PAT file (im using keka on macos but have tried betterzip too) i cant see the files i need

 

the pat file im using is 6.2.2 for 3615xs - is that right?: https://archive.synology.com/download/DSM/release/6.2.2/24922/DSM_DS3615xs_24922.pat

Link to post
Share on other sites
  • 0
Posted (edited)

ok, i found the files in the PAT file, extracted them, copied to my box. then made sure permissions were ok - "chmod u-w /lib/libsynopkg.so.1 /lib/libsynoshare.so.6"

 

scemd and nginx still arent running. i think (hope) ive included all the info asked for by Polanskiman in the original thread. i may be reading things wrong due to how SHR is set up, but am i missing 2 HDDs? there should be 4... 2*10tb and 2*5tb disks with ~18tb storage in the array

 

service [scemd] status=[error]

required upstart job: 

[scemd] is stop. 

=======================================

service [nginx] status=[error]

required upstart job: 

[nginx] is stop. 

 

root@DiskStation:~# ls -ld /var /var/services /var/services/homes

drwxr-xr-x  17 root root 4096 Mar 31 14:07 /var

drwxr-xr-x   2 root root 4096 Mar 31 14:08 /var/services

lrwxrwxrwx+  1 root root   14 Mar 31 14:08 /var/services/homes -> /volume1/homes

 

root@DiskStation:~# ps -ef | grep synoscgi

root      8924     1  0 14:07 ?        00:00:00 synoscgi

system    9052  8924  0 14:07 ?        00:00:00 synoscgi

system    9053  8924  0 14:07 ?        00:00:00 synoscgi

system    9054  8924  0 14:07 ?        00:00:00 synoscgi

system    9055  8924  0 14:07 ?        00:00:00 synoscgi

system    9056  8924  0 14:07 ?        00:00:00 synoscgi

root     16628 13956  0 14:13 pts/3    00:00:00 grep --color=auto synoscgi

root@DiskStation:~# synoscgi

Copyright (c) 2003-2019 Synology Inc. All rights reserved.

 

Usage: synoscgi (Version 24922)

--help: this help

--mode: scgi|apid (required) run as synoscgi or synoapid

 

scgi related params:

--idle-child={childNumber} (optional, default: 10) max idle child number

--max-child={childNumber} (optional, default: 65535) max child number

 

apid related params:

--conf (required) apid config realpath

 

root@DiskStation:~# fdisk -l
Disk /dev/sda: 4.6 TiB, 5000981078016 bytes, 9767541168 sectors
Units: sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 4096 bytes
I/O size (minimum/optimal): 4096 bytes / 4096 bytes
Disklabel type: gpt
Disk identifier: CCE935F3-151F-450E-8BEB-49BD19EE18DB

Device       Start        End    Sectors  Size Type
/dev/sda1     2048    4982527    4980480  2.4G Linux RAID
/dev/sda2  4982528    9176831    4194304    2G Linux RAID
/dev/sda5  9453280 9767334239 9757880960  4.6T Linux RAID


Disk /dev/sdb: 4.6 TiB, 5000981078016 bytes, 9767541168 sectors
Units: sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 4096 bytes
I/O size (minimum/optimal): 4096 bytes / 4096 bytes
Disklabel type: gpt
Disk identifier: 566502CA-59F4-4F8C-92A9-4B9B6E33934C

Device       Start        End    Sectors  Size Type
/dev/sdb1     2048    4982527    4980480  2.4G Linux RAID
/dev/sdb2  4982528    9176831    4194304    2G Linux RAID
/dev/sdb5  9453280 9767334239 9757880960  4.6T Linux RAID


Disk /dev/sdc: 9.1 TiB, 10000831348736 bytes, 19532873728 sectors
Units: sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 4096 bytes
I/O size (minimum/optimal): 4096 bytes / 4096 bytes
Disklabel type: gpt
Disk identifier: 4278E253-78CD-4DC8-9849-A3EDDFE6089F

Device          Start         End    Sectors  Size Type
/dev/sdc1        2048     4982527    4980480  2.4G Linux RAID
/dev/sdc2     4982528     9176831    4194304    2G Linux RAID
/dev/sdc5     9453280  9767334239 9757880960  4.6T Linux RAID
/dev/sdc6  9767350336 19532653311 9765302976  4.6T Linux RAID


Disk /dev/sdd: 9.1 TiB, 10000831348736 bytes, 19532873728 sectors
Units: sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 4096 bytes
I/O size (minimum/optimal): 4096 bytes / 4096 bytes
Disklabel type: gpt
Disk identifier: 2D27780F-C084-43FD-B9FB-0832E88F1CC7

Device          Start         End    Sectors  Size Type
/dev/sdd1        2048     4982527    4980480  2.4G Linux RAID
/dev/sdd2     4982528     9176831    4194304    2G Linux RAID
/dev/sdd5     9453280  9767334239 9757880960  4.6T Linux RAID
/dev/sdd6  9767350336 19532653311 9765302976  4.6T Linux RAID


Disk /dev/md0: 2.4 GiB, 2549940224 bytes, 4980352 sectors
Units: sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 4096 bytes
I/O size (minimum/optimal): 4096 bytes / 4096 bytes


Disk /dev/md1: 2 GiB, 2147418112 bytes, 4194176 sectors
Units: sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 4096 bytes
I/O size (minimum/optimal): 4096 bytes / 4096 bytes


Disk /dev/md3: 4.6 TiB, 4999833911296 bytes, 9765300608 sectors
Units: sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 4096 bytes
I/O size (minimum/optimal): 4096 bytes / 4096 bytes


Disk /dev/md2: 13.6 TiB, 14988101419008 bytes, 29273635584 sectors
Units: sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 4096 bytes
I/O size (minimum/optimal): 65536 bytes / 196608 bytes


Disk /dev/mapper/vg1000-lv: 18.2 TiB, 19987930546176 bytes, 39038926848 sectors
Units: sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 4096 bytes
I/O size (minimum/optimal): 65536 bytes / 196608 bytes

root@DiskStation:~# ls -ld /var /var/services /var/services/homes

drwxr-xr-x  17 root root 4096 Mar 31 14:07 /var

drwxr-xr-x   2 root root 4096 Mar 31 14:08 /var/services

lrwxrwxrwx+  1 root root   14 Mar 31 14:08 /var/services/homes -> /volume1/homes

Edited by wanye
Link to post
Share on other sites
  • 0

I might be totally off-topic, but did your DSM 5.2 use the "xpenoboot" bootloader?

If so, you are now using Jun's bootloader?

 

Then, you might as well look for, and delete the xpenoboot folder (sudo rm -r .xpenoboot), as that is known to cause funky sh*t.

  • Like 1
Link to post
Share on other sites
  • 0
Posted (edited)

i was, yes. i deleted .xpenoboot a few days ago though!

 

 

root@DiskStation:/volume1# cd ~

root@DiskStation:~# ls -alh

total 20K

drwx------  2 root root 4.0K Mar 30 18:31 .

drwxr-xr-x 22 root root 4.0K Mar 31 14:07 ..

-rw-r--r--  1 root root 1.1K Mar 31  2019 .profile

-rw-------  1 root root 1.7K Mar 30 18:31 .viminfo

-rw-r--r--  1 root root  267 Mar 30 14:31 .wget-hsts

root@DiskStation:~# sudo rm -r .xpenoboot

rm: cannot remove ‘.xpenoboot’: No such file or directory

 

*edit*

heres what happens when i try to run nginx from the command line

nginx: [emerg] socket() [::]:5000 failed (97: Address family not supported by protocol)

 

root@DiskStation:~# nginx -t

nginx: the configuration file /etc/nginx/nginx.conf syntax is ok

nginx: [emerg] socket() [::]:5000 failed (97: Address family not supported by protocol)

nginx: configuration file /etc/nginx/nginx.conf test failed

 

 

so it looks like nginx was listening via ipv6 as well, which was screwing things up? i commented out the second LISTEN entry for each SERVER entry in nginx.conf and nginx started.

 

just rebooting now, will update with how it goes!

 

(its saying i sent too many forms when i try to make a new post, so having to do it via edits for now)

 

 

 

nginx and scemd are still failing on startup

 

/var/log/nginx/error.log entries since the reboot. looks like its uncommented out the ipv6 entries again

 

 

0/03/31 15:06:24 [error] 29330#29330: *1 upstream prematurely closed connection while reading response header from upstream, client: 192.168.1.66, server: _, request: "GET /webman/index.cgi HTTP/1.1", upstream: "scgi://unix:/run/synoscgi.sock:", host: "192.168.1.253:5000"

2020/03/31 15:11:23 [emerg] 12306#12306: socket() [::]:5000 failed (97: Address family not supported by protocol)

2020/03/31 15:11:23 [emerg] 12357#12357: socket() [::]:5000 failed (97: Address family not supported by protocol)

2020/03/31 15:11:23 [notice] 12368#12368: signal process started

2020/03/31 15:11:23 [error] 12368#12368: invalid PID number "" in "/run/nginx.pid"


example entry in nginx.conf:

    server {

        listen 5000 default_server;

        listen [::]:5000 default_server;

 

is there something i need to do to make a change permanent? or an easy CLI-way to disable ipv6 on nginx?

 

 

*edit*

still cant make a new post...

 

so i deleted the entries instead of commenting out, and tried to start nginx without rebooting. now getting invalid PID....

 

root@DiskStation:/var/log/nginx# synoservicecfg -start nginx

service [nginx] start failed, synoerr=[0x0000]

 

 

root@DiskStation:/var/log/nginx# tail /var/log/nginx/error.log 

2020/03/31 15:04:56 [emerg] 29024#29024: socket() [::]:80 failed (97: Address family not supported by protocol)

2020/03/31 15:06:24 [error] 29330#29330: *1 upstream prematurely closed connection while reading response header from upstream, client: 192.168.1.66, server: _, request: "GET /webman/index.cgi HTTP/1.1", upstream: "scgi://unix:/run/synoscgi.sock:", host: "192.168.1.253:5000"

2020/03/31 15:11:23 [emerg] 12306#12306: socket() [::]:5000 failed (97: Address family not supported by protocol)

2020/03/31 15:11:23 [emerg] 12357#12357: socket() [::]:5000 failed (97: Address family not supported by protocol)

2020/03/31 15:11:23 [notice] 12368#12368: signal process started

2020/03/31 15:11:23 [error] 12368#12368: invalid PID number "" in "/run/nginx.pid"

2020/03/31 15:28:15 [emerg] 19356#19356: socket() [::]:5000 failed (97: Address family not supported by protocol)

2020/03/31 15:28:15 [emerg] 19364#19364: socket() [::]:5000 failed (97: Address family not supported by protocol)

2020/03/31 15:28:15 [notice] 19369#19369: signal process started

2020/03/31 15:28:15 [error] 19369#19369: invalid PID number "" in "/run/nginx.pid"

 

 

tried deleting /run/nginx/pid but still get the error.... all the ipv6 listener entries are back in the config again, so i guess it refreshes the config every time it starts? how do i disable ipv6 in nginx via CLI?

Edited by wanye
Link to post
Share on other sites
  • 0
Posted (edited)

so i found 4 copies of nginx.conf on the filesystem

 

root@DiskStation:/var/log/nginx# find / -xdev -name nginx.conf -print

/usr/share/init/nginx.conf

/etc.defaults/syslog-ng/patterndb.d/nginx.conf

/etc/syslog-ng/patterndb.d/nginx.conf

/etc/nginx/nginx.conf

 

/usr/share/init/nginx.conf is a script. is it this and/or apparmour that is doing this?

 

description "Nginx"
author "Development Infrastructure Team"
console log
reload signal SIGHUP

start on runlevel 1 and syno.share.ready and syno.network.ready and (started apparmor or stopped apparmor)
stop on runlevel [06]

nice -10
oom score -999

expect fork

respawn
respawn limit 5 10

pre-start script
    SZD_LOCAL_NGINX="/usr/local/etc/nginx"
    SZD_LOCAL_CONF_D="$SZD_LOCAL_NGINX/conf.d"
    SZD_LOCAL_SITES_ENABLED="$SZD_LOCAL_NGINX/sites-enabled"
    SZD_NGINX_TMP="/var/tmp/nginx"
    SZF_NGINX_UPSTART_ARG="/var/tmp/nginx/nginx-upstart-argument"

    MakeDirectory()
    {
        local path="$1"
        local mode="$2"
        local owner="$3"

        [ ! -d "$path" ] && /bin/mkdir -p "$path" || true
        /usr/bin/chmod "$mode"  "$path" || true
        /usr/bin/chown "$owner" "$path" || true
    }

    /usr/bin/rm -rf /var/services/tmp/nginx || true
    MakeDirectory /var/services/tmp/nginx 700 http:root

    /usr/bin/rm -rf /var/lib/nginx || true
    /bin/ln -s /var/services/tmp/nginx /var/lib/nginx || true

    MakeDirectory /var/log/nginx 750 http:root
    MakeDirectory $SZD_LOCAL_CONF_D 755 root:root
    MakeDirectory $SZD_LOCAL_SITES_ENABLED 755 root:root
    MakeDirectory $SZD_NGINX_TMP 755 root:root

    /usr/syno/bin/mkcert > /dev/null 2>&1
    /usr/syno/bin/cgi-keygen > /dev/null 2>&1 &

    for numbits in 2048 1024; do
        pem="/usr/syno/etc/ssl/dh${numbits}.pem"
        pem_default="/usr/syno/etc.defaults/ssl/dh${numbits}.pem"

        [ ! -e $pem ] && /usr/bin/cp -fp $pem_default $pem
    done

    /usr/bin/rm -f "$SZF_NGINX_UPSTART_ARG"
    /usr/bin/touch "$SZF_NGINX_UPSTART_ARG"
    /usr/bin/chmod 600 "$SZF_NGINX_UPSTART_ARG"

    /usr/bin/touch $SZD_LOCAL_CONF_D/{main,events}.conf || true

    if ! /usr/syno/bin/synow3tool --deploy-init; then
        /usr/bin/echo "startArg=\"-c /etc.defaults/nginx/nginx.conf.default\"" > "$SZF_NGINX_UPSTART_ARG"
    fi
end script

script
    . /var/tmp/nginx/nginx-upstart-argument
    exec /usr/bin/nginx $startArg -g 'pid /run/nginx.pid; daemon on; master_process on;'
end script

post-start script
    /usr/bin/rm -f /var/tmp/nginx/nginx-upstart-argument
end script

post-stop script
    /usr/bin/echo "Stop Nginx Server ......"
    [ -f /run/nginx.pid ] && /usr/bin/nginx -g 'pid /run/nginx.pid;' -s quit || true
    /bin/rm -f /etc/avahi/services/dsminfo.service
end script
~                        

 

Edited by wanye
Link to post
Share on other sites
  • 0

@wanye

 

are you sure you need the few things you got from updating, you might just use the 2nd option in the loader and do a fresh install, your raid/data partitons should not be effected, this step would on do a fresh install of dsm on the system partition(s)

it might be much less time consuming to redo the ip address and user/group, shares configuration, the plugins would be needing reinstalling new versions anyway even if ou could use the updated dsm

 

you also need diferent drivers when using 6.2.2, the loader 1.03b has drivers that will fail in a lot of cases with 6.2.2 as the "original" drivers from jun a made for 6.2.0 and synology made some kernel config changes with 6.2.2

 

https://xpenology.com/forum/topic/21663-driver-extension-jun-103b104b-for-dsm622-for-3615xs-3617xs-918/

 

Edited by IG-88
  • Like 2
Link to post
Share on other sites
  • 0

@wanye I might be wrong, as my new glasses are in quarentine, but I sptted this line from your log

" request: "GET /webman/index.cgi HTTP/1.1", upstream: "scgi://unix:/run/synoscgi.sock:", host: "192.168.1.253:5000"""

 

Is your service trying to run on the same default port as your DSM interface?

That will crash... (I guess)

 

  • Like 1
Link to post
Share on other sites
  • 0
5 hours ago, bearcat said:

@wanye I might be wrong, as my new glasses are in quarentine, but I sptted this line from your log

" request: "GET /webman/index.cgi HTTP/1.1", upstream: "scgi://unix:/run/synoscgi.sock:", host: "192.168.1.253:5000"""

 

Is your service trying to run on the same default port as your DSM interface?

That will crash... (I guess)

 

 

the way i read that was me trying to access DSM from my web browser. the full entry is:

2020/03/31 15:06:24 [error] 29330#29330: *1 upstream prematurely closed connection while reading response header from upstream, client: 192.168.1.66, server: _, request: "GET /webman/index.cgi HTTP/1.1", upstream: "scgi://unix:/run/synoscgi.sock:", host: "192.168.1.253:5000"

 

(from memory) this was after i edited the nginx.conf to remove the ipv6 listener entries, then manually ran nginx (and it loaded a standard nginx page not found error. i assumed this was because scemd wasnt running?)

 

 

14 hours ago, IG-88 said:

@wanye

 

are you sure you need the few things you got from updating, you might just use the 2nd option in the loader and do a fresh install, your raid/data partitons should not be effected, this step would on do a fresh install of dsm on the system partition(s)

it might be much less time consuming to redo the ip address and user/group, shares configuration, the plugins would be needing reinstalling new versions anyway even if ou could use the updated dsm

 

you also need diferent drivers when using 6.2.2, the loader 1.03b has drivers that will fail in a lot of cases with 6.2.2 as the "original" drivers from jun a made for 6.2.0 and synology made some kernel config changes with 6.2.2

 

https://xpenology.com/forum/topic/21663-driver-extension-jun-103b104b-for-dsm622-for-3615xs-3617xs-918/

 

 

i was going from 5.2, half of the packages i run wouldnt update on it anymore. it hadnt been updated since i built the box 5 years ago!

 

the original plan was to go to 6.1 (IIRC) and leave it there, but instead of clicking the manual install button to upload the relevant PAT file, i clicked next accidentally, and it connected to the web and grabbed the latest version (6.2.2) which then disabled my onboard NICs. after fiddling with various posts on here trying to roll it back and/or get it working, i ordered an intel NIC. 

 

fitted that, and now i have the nginx/scemd not starting issue, which seems to be related to ipv6 entries. which, if DSM was working, i could probably figure out how to disable it, but from an ssh prompt on an unfamiliar linux box? i'm not so comfortable....

Link to post
Share on other sites
  • 0
7 hours ago, wanye said:

i could probably figure out how to disable it, but from an ssh prompt on an unfamiliar linux box? i'm not so comfortable....

 

/etc/sysconfig/network-scripts/

 ifcfg-eth0

 ifcfg-eth1

...

in these files set

IPV6INIT=off

 

  • Like 1
Link to post
Share on other sites
  • 0

thanks. tried disabling ipv6 there and still getting the same errors in /var/log/nginx/error.log

 

heres everything after changing ipv6init=off for eth-/eth1 and rebooting. its exactly the same errors i was getting previously...

 

2020/04/01 23:26:44 [emerg] 12223#12223: socket() [::]:5000 failed (97: Address family not supported by protocol)

2020/04/01 23:26:44 [emerg] 12318#12318: socket() [::]:5000 failed (97: Address family not supported by protocol)

2020/04/01 23:26:44 [notice] 12326#12326: signal process started

2020/04/01 23:26:44 [error] 12326#12326: invalid PID number "" in "/run/nginx.pid"

 

 

so. do you think i should attempt to "upgrade" to 6.1 to resolve things? i don't mind if theres an easy way, its just that the posts i read here mentioned i needed to drop in a different HDD to set it up on initially, and that seemed like far too fiddly a task, and preserving the data in the array is the most important thing here (its not just tv shows, its my main home server) - unfortunately i don't have enough spare storage to hand to back up everything i need and start it all from scratch again.

 

also, theres definitely some screwy permissions too, apps can no longer read/write to /volume1/ so i think i need to restore access to the apps. but without DSM, its hard working out what apps are running as what. i can access the SMB shares using the admin credentials. previously it was set up for guest read-only (and apps that access it read/write)

 

drwxrwx---+ 17 root  users     4096 Mar 25 12:59 downloads

inside there

drwxrwxrwx+ 404 admin      users      36864 Apr  1 16:44 TV

inside TV there seems to be a mixture of 3 users that have write access

drwxrwx---+  4 admin              users       4096 Dec 12  2016 TV show 1

drwxrwx---+  3 svc-nzbdrone users       4096 Aug 13  2019 TV show 2

drwxrwx---+  4                   100 users       4096 Nov  1  2016 TV Show 3

 

 

Link to post
Share on other sites
  • 0
On 4/2/2020 at 12:48 AM, wanye said:

so. do you think i should attempt to "upgrade" to 6.1 to resolve things?

 

you would just do the same as using the 2nd boot option in the 6.2 loader, a fresh install of dsm and keeping your raid as it is

so its less effort to "keep" 6.2.2 and just do the install without knocking out your raid - thats a usual option on original systems too, when the dsm system is wonky for some reason or does not come up after a systemupdate you can put the loader (internal usb on original units)  in fresh install mode and you can choose to install just the system (dsm) and keep your data or to a complete new install knocking out you "old" raid/data  (wizard in web gui when booting up 2nd boot loader option)

https://global.download.synology.com/download/Document/Software/UserGuide/Firmware/DSM/6.2/enu/Syno_UsersGuide_NAServer_enu.pdf

page 25

 

dsm is a custom linux appliance that handles some things there own way, if you want do find out whats wrong with your upgrade attempt it can take some time, on the more you change you might make things less predictable or might come into tha same situation after a bigger uddate (like 6.2.2, full 200-300MB dsm *.pat file) whre the whole system partition is overwritten and only config data are reapplied)

the efficient way (imho) is a fresh install and redo the shares/permissions in the gui and reinstall the plugins

  • Like 1
Link to post
Share on other sites
  • 0
3 hours ago, wanye said:

at this point i discovered the server wouldnt properly shut down/reboot, so i had to power it off/on manually. it used to work ok with the original install, any idea whats changed, or what i need to do to sort that out?

thats usually a sigh for crashed drivers (kernel oops, check the log)

you istalled 24922 aka 6.2.2, did you also copy new drives to you usb boot device?

6.2.0 -> 6.2.2 had kernel oprion changes requiring new drivers so the drivers that come with jun's loader will not work and you fall back to drivers delivered with dsm

https://xpenology.com/forum/topic/21663-driver-extension-jun-103b104b-for-dsm622-for-3615xs-3617xs-918/

 

Link to post
Share on other sites
  • 0

the only oops in dmesg is SMP. i didnt copy and additional drivers. im just using ds3615_6.2/synoboot.img... so which files do you suggest i copy onto it? is it just a matter of copying the file(s) and then booting off the sd card? it's all a little confusing...

 

root@microserver:/var/log# more synopoweroff.log

2020-04-09T05:01:16-07:00 DiskStation synoupgrade_SYNO.Core.Upgrade_1_start[17135]: system_poweroff_pre_hook.c:17 synopoweroff: Begin SYNOPowerOffPreHook action.

2020-04-09T05:01:17-07:00 DiskStation synoupgrade_SYNO.Core.Upgrade_1_start[17135]: system_poweroff_pre_hook.c:22 synopoweroff: Finish SYNOPowerOffPreHook action.

2020-04-09T05:01:17-07:00 DiskStation synoupgrade_SYNO.Core.Upgrade_1_start[17135]: system_sys_init.c:95 synopoweroff: System is going to reboot

2020-04-09T13:56:32+01:00 microserver synoscgi_SYNO.Core.System_1_shutdown[32364]: system_poweroff_pre_hook.c:17 synopoweroff: Begin SYNOPowerOffPreHook action.

2020-04-09T13:56:32+01:00 microserver synoscgi_SYNO.Core.System_1_shutdown[32364]: system_poweroff_pre_hook.c:22 synopoweroff: Finish SYNOPowerOffPreHook action.

2020-04-09T13:56:32+01:00 microserver synoscgi_SYNO.Core.System_1_shutdown[32364]: system_sys_init.c:95 synopoweroff: System is going to poweroff

 

root@microserver:/var/log# grep -i oops dmesg 

[Thu Apr  9 05:16:08 2020] Oops: 0002 [#1] SMP 

[Thu Apr  9 14:02:06 2020] Oops: 0002 [#1] SMP 

Link to post
Share on other sites
  • 0

I have 2 microservers gen8 baremetal running and I have none of these issues.

 

However let me share my insights

 

1 - Check if you are running latest bios and ilo firmwares

2 - Do not use sd card for loader, on my systems the loader got corrupted  after some reboots, use a usb flash drive.

3 - Use extra.lzma from IG-88 and remove the intel network card, its no longer needed, internal networking works fine

4 - Please double check if you really removed the .xpenoboot folder in root directory, ie /

 

 

 

 

  • Like 1
Link to post
Share on other sites
  • 0
53 minutes ago, wanye said:

so which files do you suggest i copy onto it? is it just a matter of copying the file(s) and then booting off the

as in the link in the description above

when you have 3615 and already installed 24922 aka 6.2.2 then the new kernel is already installed on your boot media

so you download the zip file extract it to get extra.lzma and copy that to the loader, replacing the file there

DS3615: extra.lzma for loader 1.03b_mod ds3615 DSM 6.2.2 v0.5_test
http://s000.tinyupload.com/?file_id=87576629927396429210
SHA256: BAA019C55B0D4366864DE67E29D45A2F624877726552DA2AD64E4057143DBAF0

 

 

53 minutes ago, wanye said:

sd card?

 

sd card? usually a usb flash drive is used for booting and where the *.img file is installed to

if you use a sd card as boot media instead of usb then yes that would be the place

 

53 minutes ago, wanye said:

 

it's all a little confusing...

 

its kind of dangerous to do things you dont understand, try to read the install tutorial again?

the loader keeps its drivers in the file extra.lzma, to get new drivers you need to replace it and as drivers are specific for every model it needs to be the extra.lzma for the specific model (and loader version too), its linux not windows, drivers are usually very specific for one version of a distribution, any change of kernel version or even compile options of the kernel (what happend in 6.2.2) will make you need to compile drivers newly specific for that change

  • Like 1
Link to post
Share on other sites
  • 0
Posted (edited)

ok, so i upgraded the BIOS and ilo firmware on it. that took *much* longer than it should have! why dont HP provide OS-agnostic ISO files for creating a bootable usb, or providing the bios binary as a standalone file, rather than one embedded in a windows exe or RHEL rpm? i use a mac and a raspberry pi, so had to dig out an old laptop and put windows on, just to get at the files i need!

 

(i also forked out for an ilo licence so i can access the remote console, so the server can go back down in the comms cab rather than under my desk with a monitor/keyboard plugged in)

 

anyway. all sorted and updated. i created a new boot image, and copied extra.lzma  plus zImage and rd.gz off the 24922.pat file onto the stick. booted up, and the old NICs are now working so i assume the modded extras.lzma has done its job

 

havent tried rebooting yet, as i'm waiting for disk scrubbing to complete, will update once thats completed and i've tried to shutdown and/or reboot

Edited by wanye
Link to post
Share on other sites
  • 0

Next time you can just rename the downloaded windows exe file to zip and just extract it using keka or other utility, you can update bios and ilo firmwares from ilo directly

  • Like 1
Link to post
Share on other sites
  • 0

 disk scrubbing completed (took 23 hours for 4 drives in an 18tb SHR array) and shutdown completed. all working fine now.

 

i'd say my question is resolved. thanks for your help!

 

the only issue i'm having now is occasional buffering from the SMB share on the box to my firetv/kodi machine (firetv2 with wired network connection) only seems to happen randomly, but still annoying. got iperf3 installed and tested, that seems fine......

Quote

 

Waynes-Mac-mini:bin wanye$ iperf3 -c 192.168.1.253

Connecting to host 192.168.1.253, port 5201

[  4] local 192.168.1.66 port 63261 connected to 192.168.1.253 port 5201

[ ID] Interval           Transfer     Bandwidth

[  4]   0.00-1.00   sec   114 MBytes   954 Mbits/sec                  

[  4]   1.00-2.00   sec   112 MBytes   941 Mbits/sec                  

[  4]   2.00-3.00   sec   112 MBytes   940 Mbits/sec                  

[  4]   3.00-4.00   sec   112 MBytes   940 Mbits/sec                  

[  4]   4.00-5.00   sec   112 MBytes   940 Mbits/sec                  

[  4]   5.00-6.00   sec   112 MBytes   941 Mbits/sec                  

[  4]   6.00-7.00   sec   112 MBytes   940 Mbits/sec                  

[  4]   7.00-8.00   sec   112 MBytes   940 Mbits/sec                  

[  4]   8.00-9.00   sec   112 MBytes   940 Mbits/sec                  

[  4]   9.00-10.00  sec   112 MBytes   940 Mbits/sec                  

- - - - - - - - - - - - - - - - - - - - - - - - -

[ ID] Interval           Transfer     Bandwidth

[  4]   0.00-10.00  sec  1.10 GBytes   942 Mbits/sec                  sender

[  4]   0.00-10.00  sec  1.09 GBytes   941 Mbits/sec                  receiver

 

iperf Done.

Waynes-Mac-mini:bin wanye$ 

 

 

could be the firetv though (i recently upgraded the version of kodi after a few other issues with it) so i'm going to stick the lid back on and put it back in the comms cab. everything else can be done remotely now :)

Link to post
Share on other sites
  • 0
The question(s) in this topic have been answered and/or the topic author has resolved their issue. This topic is now closed. If you have other questions, please open a new topic.
Link to post
Share on other sites
Guest
This topic is now closed to further replies.