simkard Posted October 8, 2018 Share #1 Posted October 8, 2018 (edited) Hello Everyone, I'm writing here because I tried to upgrade my DS1010+ to various different DSM releases (based on DS1511+ which is still supported by Synology). The only one that got 100% working was 6.0 ... I mean, everything higher than this release seems to end up with these problems : No more informations regarding CPU/RAM in the WebUI widget System monitor refuses to open with an error message Volumes are not available thru WebUI ... but connecting with SSH seems to be fine to access them /var/log LOGs seem to contain some informations (see at the bottom of this POST) NB1 : DS1511+ and DS1010+ are pretty similar : CPU : Intel ATOM D510 (1.6Ghz) vs Intel ATOM D525 (1.8Ghz) RAM : same (1GB ; Max 3GB) HDD slots : same (5) LAN ports : same (2) NB2 : Major fact : BIOS are the same on DS1010+ and on DS1511+ It seems that something is related to scemd or manutil parts which are likely to provide system informations, LED/button controls, etc ... As XPenology people must have more knowledge than me on these subjects, I'm asking some help. Thanks Spoiler 07:58:10+02:00 Synology kernel: [ 0.000000] ACPI: RSDP 00000000000f9db0 00014 (v00 ACPIAM) 07:58:10+02:00 Synology kernel: [ 0.000000] ACPI: RSDT 00000000bf690000 0003C (v01 041610 RSDT1824 20100416 MSFT 00000097) 07:58:10+02:00 Synology kernel: [ 0.000000] ACPI: FACP 00000000bf690200 00084 (v01 041610 FACP1824 20100416 MSFT 00000097) 07:58:10+02:00 Synology kernel: [ 0.000000] ACPI: DSDT 00000000bf690440 06848 (v01 1AAAA 1AAAA000 00000000 INTL 20051117) 07:58:10+02:00 Synology kernel: [ 0.000000] ACPI: FACS 00000000bf69e000 00040 07:58:10+02:00 Synology kernel: [ 0.000000] ACPI: APIC 00000000bf690390 0006C (v01 041610 APIC1824 20100416 MSFT 00000097) 07:58:10+02:00 Synology kernel: [ 0.000000] ACPI: MCFG 00000000bf690400 0003C (v01 041610 OEMMCFG 20100416 MSFT 00000097) 07:58:10+02:00 Synology kernel: [ 0.000000] ACPI: OEMB 00000000bf69e040 00072 (v01 041610 OEMB1824 20100416 MSFT 00000097) 07:58:10+02:00 Synology kernel: [ 0.000000] ACPI: HPET 00000000bf69a440 00038 (v01 041610 OEMHPET 20100416 MSFT 00000097) 07:58:10+02:00 Synology kernel: [ 0.000000] ACPI: GSCI 00000000bf69e0c0 02024 (v01 041610 GMCHSCI 20100416 MSFT 00000097) 07:58:10+02:00 Synology kernel: [ 0.000000] Zone ranges: 07:58:10+02:00 Synology kernel: [ 0.000000] DMA [mem 0x00001000-0x00ffffff] 07:58:10+02:00 Synology kernel: [ 0.000000] DMA32 [mem 0x01000000-0xffffffff] 07:58:10+02:00 Synology kernel: [ 0.000000] Normal empty 07:58:10+02:00 Synology kernel: [ 0.000000] Movable zone start for each node 07:58:10+02:00 Synology kernel: [ 0.000000] Early memory node ranges 07:58:10+02:00 Synology kernel: [ 0.000000] node 0: [mem 0x00001000-0x0009efff] 07:58:10+02:00 Synology kernel: [ 0.000000] node 0: [mem 0x00100000-0xbf68ffff] 07:58:10+02:00 Synology kernel: [ 0.000000] Built 1 zonelists in Zone order, mobility grouping on. Total pages: 773178 07:58:10+02:00 Synology kernel: [ 0.000000] Internal HD num: 0 07:58:10+02:00 Synology kernel: [ 0.000000] Internal netif num: 2 07:58:10+02:00 Synology kernel: [ 0.000000] Synology Hardware Version: DS1010+-j 07:58:10+02:00 Synology kernel: [ 0.000000] Serial Number: XXXXXXXXXX 07:58:10+02:00 Synology kernel: [ 0.025533] ACPI: All ACPI Tables successfully acquired 07:58:10+02:00 Synology kernel: [ 0.200354] raid6: sse2x1 gen() 113 MB/s 07:58:10+02:00 Synology kernel: [ 0.221200] raid6: sse2x1 xor() 701 MB/s 07:58:10+02:00 Synology kernel: [ 0.242332] raid6: sse2x2 gen() 390 MB/s 07:58:10+02:00 Synology kernel: [ 0.263218] raid6: sse2x2 xor() 1220 MB/s 07:58:10+02:00 Synology kernel: [ 0.284260] raid6: sse2x4 gen() 746 MB/s 07:58:10+02:00 Synology kernel: [ 0.305199] raid6: sse2x4 xor() 1365 MB/s 07:58:10+02:00 Synology kernel: [ 0.310006] raid6: using algorithm sse2x4 gen() (746 MB/s) 07:58:10+02:00 Synology kernel: [ 0.315005] raid6: .... xor() 1365 MB/s, rmw enabled 07:58:10+02:00 Synology kernel: [ 0.320005] raid6: using ssse3x2 recovery algorithm 07:58:10+02:00 Synology kernel: [ 0.349297] ACPI: Executed 1 blocks of module-level executable AML code 07:58:10+02:00 Synology umount: can't umount /initrd: Invalid argument 07:58:10+02:00 Synology kernel: [ 0.795763] ACPI: Enabled 2 GPEs in block 00 to 3F 07:58:10+02:00 Synology kernel: [ 4.302499] bounce pool size: 64 pages 07:58:10+02:00 Synology kernel: [ 4.315046] Dquot-cache hash table entries: 512 (order 0, 4096 bytes) 07:58:10+02:00 Synology kernel: [ 8.922004] ata7: limiting SATA link speed to 1.5 Gbps 07:58:10+02:00 Synology kernel: [ 10.952470] ata8: limiting SATA link speed to 1.5 Gbps 07:58:10+02:00 Synology kernel: [ 13.657788] pineview_synobios: module license 'Synology Inc.' taints kernel. 07:58:10+02:00 Synology kernel: [ 13.665042] Disabling lock debugging due to kernel taint 07:58:10+02:00 Synology kernel: [ 13.671402] 2018-10-8 5:58:2 UTC 07:58:10+02:00 Synology kernel: [ 13.678963] Brand: Synology 07:58:10+02:00 Synology kernel: [ 13.681809] Model: DS-1010+ 07:58:10+02:00 Synology kernel: [ 13.684642] set group disks wakeup number to 5, spinup time deno 1 07:58:10+02:00 Synology kernel: [ 14.231480] synobios: unload 07:58:10+02:00 Synology kernel: [ 14.293311] md: invalid raid superblock magic on sda5 07:58:10+02:00 Synology kernel: [ 14.298378] md: sda5 does not have a valid v0.90 superblock, not importing! 07:58:10+02:00 Synology kernel: [ 14.343542] md: invalid raid superblock magic on sdb5 07:58:10+02:00 Synology kernel: [ 14.348610] md: sdb5 does not have a valid v0.90 superblock, not importing! 07:58:10+02:00 Synology kernel: [ 14.421316] md: invalid raid superblock magic on sdc5 07:58:10+02:00 Synology kernel: [ 14.426384] md: sdc5 does not have a valid v0.90 superblock, not importing! 07:58:10+02:00 Synology kernel: [ 14.480543] md: invalid raid superblock magic on sdd5 07:58:10+02:00 Synology kernel: [ 14.485603] md: sdd5 does not have a valid v0.90 superblock, not importing! 07:58:10+02:00 Synology kernel: [ 14.573768] md: invalid raid superblock magic on sde5 07:58:10+02:00 Synology kernel: [ 14.578830] md: sde5 does not have a valid v0.90 superblock, not importing! 07:58:10+02:00 Synology kernel: [ 14.600089] md: sda2 has different UUID to sda1 07:58:10+02:00 Synology kernel: [ 14.607881] md: sdb2 has different UUID to sda1 07:58:10+02:00 Synology kernel: [ 14.615672] md: sdc2 has different UUID to sda1 07:58:10+02:00 Synology kernel: [ 14.623453] md: sdd2 has different UUID to sda1 07:58:10+02:00 Synology kernel: [ 14.631246] md: sde2 has different UUID to sda1 07:58:10+02:00 Synology s30_synocheckuser: s30_synocheckuser.c:383 The number of cron command fields is invalid! iNum=1 07:58:10+02:00 Synology s30_synocheckuser: s30_synocheckuser.c:383 The number of cron command fields is invalid! iNum=1 07:58:13+02:00 Synology s30_synocheckuser: SYSTEM: Last message 's30_synocheckuser.c:' repeated 1 times, suppressed by syslog-ng on Synology 07:58:13+02:00 Synology synoservice: synoservice.c:1575 pause gcpd due to require service cupsd runkey is stop 07:58:13+02:00 Synology root: mkcert: Verifying certificate in [/usr/syno/etc/certificate/system/default]. 07:58:14+02:00 Synology [ 26.196924] init: syno-auth-check main process (4892) killed by TERM signal 07:58:14+02:00 Synology synonetd: net_if_is_link.c:40 Cannot get link status: No such device 07:58:14+02:00 Synology synonetd: net_if_is_link.c:119 get link status failed on eth0 07:58:15+02:00 Synology synonetd: net_if_is_link.c:40 Cannot get link status: No such device 07:58:15+02:00 Synology synonetd: net_if_is_link.c:119 get link status failed on eth0 07:58:17+02:00 Synology kernel: [ 28.118915] 2018-10-8 5:58:17 UTC 07:58:17+02:00 Synology kernel: [ 28.126611] Brand: Synology 07:58:17+02:00 Synology kernel: [ 28.129523] Model: DS-1010+ 07:58:17+02:00 Synology kernel: [ 28.132405] set group disks wakeup number to 5, spinup time deno 1 07:58:22+02:00 Synology interface-catcher: eth0 (dhcp) is added 07:58:22+02:00 Synology interface-catcher: eth1 (dhcp) is added 07:58:22+02:00 Synology interface-catcher: lo (inet 127.0.0.1 netmask 255.0.0.0 ) is added 07:58:23+02:00 Synology dhcp-client: started on eth0 07:58:25+02:00 Synology dhcp-client: started on eth1 07:58:25+02:00 Synology kernel: [ 37.093378] md: md2: current auto_remap = 0 07:58:25+02:00 Synology kernel: [ 37.097682] md: md2: flushing inflight I/O 07:58:26+02:00 Synology kernel: [ 37.107718] md: resync of RAID array md2 07:58:26+02:00 Synology spacetool.shared: spacetool.c:3088 [Info] Old vg path: [/dev/vg1000], New vg path: [/dev/vg1000], UUID: [cU8wIS-uckM-eUmu-rW07-nG21-fFyk-tUfDiy] 07:58:26+02:00 Synology spacetool.shared: spacetool.c:3095 [Info] Activate all VG 07:58:26+02:00 Synology spacetool.shared: spacetool.c:3106 Activate LVM [/dev/vg1000] 07:58:26+02:00 Synology spacetool.shared: spacetool.c:3149 space: [/dev/vg1000] 07:58:26+02:00 Synology spacetool.shared: spacetool.c:3175 space: [/dev/vg1000], ndisk: [5] 07:58:27+02:00 Synology [ 38.143177] init: dhcp-client (eth0) main process (8242) killed by TERM signal 07:58:27+02:00 Synology dhcp-client: stopped on eth0 07:58:27+02:00 Synology dhcp-client: started on eth0 07:58:27+02:00 Synology spacetool.shared: hotspare_repair_config_set.c:36 Failed to hup synostoraged 07:58:27+02:00 Synology synovspace: virtual_space_conf_check.c:78 [INFO] "PASS" checking configuration of virtual space [FCACHE], app: [1] 07:58:27+02:00 Synology synovspace: virtual_space_conf_check.c:74 [INFO] No implementation, skip checking configuration of virtual space [HA] 07:58:27+02:00 Synology synovspace: virtual_space_conf_check.c:74 [INFO] No implementation, skip checking configuration of virtual space [SNAPSHOT_ORG] 07:58:27+02:00 Synology synovspace: vspace_wrapper_load_all.c:76 [INFO] No virtual layer above space: [/volume1] / [/dev/vg1000/lv] 07:58:29+02:00 Synology dhcp-client: eth0 get new IP 172.16.0.200/24 07:58:29+02:00 Synology synocheckhotspare: synocheckhotspare.c:149 [INFO] No hotspare config, skip hotspare config check. [0x2000 virtual_space_layer_get.c:98] 07:58:31+02:00 Synology synocheckiscsitrg: iscsi_snapshot_repair.c:177 opendir(/volume1/@Snapshot) failed, err=No such file or directory 07:58:32+02:00 Synology syno_hdd_util: Model:[ST2000DL003-9VT166], Firmware:[CC32], S/N:[5YD544N3] in [/dev/sde] is not ssd 07:58:32+02:00 Synology syno_hdd_util: Model:[ST2000VN004-2E4164], Firmware:[SC60], S/N:[W524SLDS] in [/dev/sdd] is not ssd 07:58:32+02:00 Synology syno_hdd_util: Model:[ST2000DL003-9VT166], Firmware:[CC32], S/N:[6YD0YDBQ] in [/dev/sdc] is not ssd 07:58:32+02:00 Synology syno_hdd_util: Model:[ST32000542AS], Firmware:[CC34], S/N:[5XW0D3BQ] in [/dev/sdb] is not ssd 07:58:32+02:00 Synology syno_hdd_util: Model:[ST2000DM001-1CH164], Firmware:[CC29], S/N:[Z1E7AGT3] in [/dev/sda] is not ssd 07:58:32+02:00 Synology synobackupd: (9856) [err] command_server.cpp:341 add watch to [/usr/local/share/synobackup] failed 07:58:32+02:00 Synology dhclient: eth0 emit network ready event 07:58:32+02:00 Synology kernel: [ 43.965951] sd 8:0:0:0: [synoboot] Asking for cache data failed 07:58:32+02:00 Synology kernel: [ 43.971951] sd 8:0:0:0: [synoboot] Assuming drive cache: write through 07:58:32+02:00 Synology kernel: [ 43.981467] sd 8:0:0:0: [synoboot] Asking for cache data failed 07:58:32+02:00 Synology kernel: [ 43.987490] sd 8:0:0:0: [synoboot] Assuming drive cache: write through 07:58:32+02:00 Synology kernel: [ 44.091744] sd 8:0:0:0: [synoboot] Asking for cache data failed 07:58:32+02:00 Synology kernel: [ 44.097765] sd 8:0:0:0: [synoboot] Assuming drive cache: write through 07:58:33+02:00 Synology dms: nginx_deploy.cpp:579 Failed to open share memory, No such file or directory 07:58:33+02:00 Synology dms: nginx_deploy.cpp:579 Failed to open share memory, No such file or directory 07:58:33+02:00 Synology dms: nginx_deploy.cpp:579 Failed to open share memory, No such file or directory 07:58:34+02:00 Synology dms: SYSTEM: Last message 'nginx_deploy.cpp:579' repeated 4 times, suppressed by syslog-ng on Synology 07:58:34+02:00 Synology manutild: manutild.c:2866 /.start_manutild not exist, finish manutild 07:58:35+02:00 Synology root: mkcert: Verifying certificate in [/usr/syno/etc/certificate/system/default]. 07:58:36+02:00 Synology synoiscsiep: iscsi_start_all.cpp:96 Successfully started iSCSI service. 07:58:37+02:00 Synology [ 48.338429] init: iscsi_pluginserverd main process (11090) terminated with status 255 07:58:37+02:00 Synology [ 48.346650] init: iscsi_pluginserverd main process ended, respawning 07:58:37+02:00 Synology [ 48.551428] init: iscsi_pluginserverd main process (11141) terminated with status 255 07:58:37+02:00 Synology [ 48.560002] init: iscsi_pluginserverd main process ended, respawning 07:58:48+02:00 Synology [ 60.191923] init: smbd main process (11308) killed by TERM signal 07:58:50+02:00 Synology synoiscsiep: iscsi_stop_all.cpp:110 Terminated all lunbackup processes. 07:58:50+02:00 Synology synoiscsiep: iscsi_stop_all.cpp:162 Successfully stopped iSCSI service. 07:58:50+02:00 Synology synocheckiscsitrg: iscsi_snapshot_repair.c:177 opendir(/volume1/@Snapshot) failed, err=No such file or directory 07:58:54+02:00 Synology synocheckshare: synocheckshare_vol_unmount.c:147 Unmount Share [INTERNAL] [/dev/vg1000/lv] [/volume1] 07:58:57+02:00 Synology umount: Kill the process "dms" with /volume1/@appstore/MediaServer/sbin/dms. 07:58:57+02:00 Synology umount: Kill the process "lighttpd" with /volume1/@appstore/MediaServer/sbin/lighttpd. 07:58:57+02:00 Synology umount: Kill the process "dms" with /volume1/@appstore/MediaServer/synovte. 07:58:57+02:00 Synology umount: kill the process "dms" [pid = 10082] using /volume1/@appstore/MediaServer/sbin/dms 07:58:58+02:00 Synology dhclient: eth1 emit network ready event 07:58:59+02:00 Synology dnsdsm: Check failed. H 07:58:59+02:00 Synology synousbdisk: RCClean succeeded 07:59:01+02:00 Synology hotplugd: hotplugd.c:1304 ##### ACTION:add 07:59:01+02:00 Synology hotplugd: DEVNAME:sda 07:59:01+02:00 Synology hotplugd: DEVGUID:Z1E7AGT30 07:59:01+02:00 Synology hotplugd: DEVPATH:sda 07:59:01+02:00 Synology hotplugd: SUBSYSTEM:block 07:59:01+02:00 Synology hotplugd: PHYSDEVPATH:/devices/pci0000:00/0000:00:1f.2/ata1/host0/target0:0:0/0:0:0:0 07:59:01+02:00 Synology hotplugd: hotplugd.c:1400 ==== SATA disk [sda] hotswap [add] ==== 07:59:01+02:00 Synology hotplugd: disk/smartctl_enable.c:99 open /dev/sda failed. 07:59:01+02:00 Synology hotplugd: SmartFirmAndSerialRead(146) open device /dev/sda fail 07:59:01+02:00 Synology hotplugd: hotplugd.c:1418 SmartFirmAndSerialRead failed 07:59:01+02:00 Synology hotplugd: hotplugd.c:1421 ==== SATA disk [sda] Model: [ST2000DM001-1CH164 ] ==== 07:59:01+02:00 Synology hotplugd: hotplugd.c:1422 ==== SATA disk [sda] Serial number: [] ==== 07:59:01+02:00 Synology hotplugd: hotplugd.c:1423 ==== SATA disk [sda] Firmware version: [] ==== 07:59:01+02:00 Synology hotplugd: hotplugd.c:1304 ##### ACTION:add 07:59:01+02:00 Synology hotplugd: DEVNAME:sdb 07:59:01+02:00 Synology hotplugd: DEVGUID:5XW0D3BQ0 07:59:01+02:00 Synology hotplugd: DEVPATH:sdb 07:59:01+02:00 Synology hotplugd: SUBSYSTEM:block 07:59:01+02:00 Synology hotplugd: PHYSDEVPATH:/devices/pci0000:00/0000:00:1f.2/ata2/host1/target1:0:0/1:0:0:0 07:59:01+02:00 Synology hotplugd: hotplugd.c:1400 ==== SATA disk [sdb] hotswap [add] ==== 07:59:01+02:00 Synology hotplugd: disk/smartctl_enable.c:99 open /dev/sdb failed. 07:59:01+02:00 Synology hotplugd: SmartFirmAndSerialRead(146) open device /dev/sdb fail 07:59:01+02:00 Synology hotplugd: hotplugd.c:1418 SmartFirmAndSerialRead failed 07:59:01+02:00 Synology hotplugd: hotplugd.c:1421 ==== SATA disk [sdb] Model: [ST32000542AS ] ==== 07:59:01+02:00 Synology hotplugd: hotplugd.c:1422 ==== SATA disk [sdb] Serial number: [] ==== 07:59:01+02:00 Synology hotplugd: hotplugd.c:1423 ==== SATA disk [sdb] Firmware version: [] ==== 07:59:01+02:00 Synology hotplugd: hotplugd.c:1304 ##### ACTION:add 07:59:01+02:00 Synology hotplugd: DEVNAME:sdc 07:59:01+02:00 Synology hotplugd: DEVGUID:6YD0YDBQ0 07:59:01+02:00 Synology hotplugd: DEVPATH:sdc 07:59:01+02:00 Synology hotplugd: SUBSYSTEM:block 07:59:01+02:00 Synology hotplugd: PHYSDEVPATH:/devices/pci0000:00/0000:00:1f.2/ata3/host2/target2:0:0/2:0:0:0 07:59:01+02:00 Synology hotplugd: hotplugd.c:1400 ==== SATA disk [sdc] hotswap [add] ==== 07:59:01+02:00 Synology hotplugd: disk/smartctl_enable.c:99 open /dev/sdc failed. 07:59:01+02:00 Synology hotplugd: SmartFirmAndSerialRead(146) open device /dev/sdc fail 07:59:01+02:00 Synology hotplugd: hotplugd.c:1418 SmartFirmAndSerialRead failed 07:59:01+02:00 Synology hotplugd: hotplugd.c:1421 ==== SATA disk [sdc] Model: [ST2000DL003-9VT166 ] ==== 07:59:01+02:00 Synology hotplugd: hotplugd.c:1422 ==== SATA disk [sdc] Serial number: [] ==== 07:59:01+02:00 Synology hotplugd: hotplugd.c:1423 ==== SATA disk [sdc] Firmware version: [] ==== 07:59:01+02:00 Synology hotplugd: hotplugd.c:1304 ##### ACTION:add 07:59:01+02:00 Synology hotplugd: DEVNAME:sdd 07:59:01+02:00 Synology hotplugd: DEVGUID:W524SLDS0 07:59:01+02:00 Synology hotplugd: DEVPATH:sdd 07:59:01+02:00 Synology hotplugd: SUBSYSTEM:block 07:59:01+02:00 Synology hotplugd: PHYSDEVPATH:/devices/pci0000:00/0000:00:1f.2/ata4/host3/target3:0:0/3:0:0:0 07:59:01+02:00 Synology hotplugd: hotplugd.c:1400 ==== SATA disk [sdd] hotswap [add] ==== 07:59:01+02:00 Synology hotplugd: disk/smartctl_enable.c:99 open /dev/sdd failed. 07:59:01+02:00 Synology hotplugd: SmartFirmAndSerialRead(146) open device /dev/sdd fail 07:59:01+02:00 Synology hotplugd: hotplugd.c:1418 SmartFirmAndSerialRead failed 07:59:01+02:00 Synology hotplugd: hotplugd.c:1421 ==== SATA disk [sdd] Model: [ST2000VN004-2E4164 ] ==== 07:59:01+02:00 Synology hotplugd: hotplugd.c:1422 ==== SATA disk [sdd] Serial number: [] ==== 07:59:01+02:00 Synology hotplugd: hotplugd.c:1423 ==== SATA disk [sdd] Firmware version: [] ==== 07:59:01+02:00 Synology hotplugd: hotplugd.c:1304 ##### ACTION:add 07:59:01+02:00 Synology hotplugd: DEVNAME:sde 07:59:01+02:00 Synology hotplugd: DEVGUID:5YD544N30 07:59:01+02:00 Synology hotplugd: DEVPATH:sde 07:59:01+02:00 Synology hotplugd: SUBSYSTEM:block 07:59:01+02:00 Synology hotplugd: PHYSDEVPATH:/devices/pci0000:00/0000:00:1f.2/ata5/host4/target4:0:0/4:0:0:0 07:59:01+02:00 Synology hotplugd: hotplugd.c:1400 ==== SATA disk [sde] hotswap [add] ==== 07:59:01+02:00 Synology hotplugd: disk/smartctl_enable.c:99 open /dev/sde failed. 07:59:01+02:00 Synology hotplugd: SmartFirmAndSerialRead(146) open device /dev/sde fail 07:59:01+02:00 Synology hotplugd: hotplugd.c:1418 SmartFirmAndSerialRead failed 07:59:01+02:00 Synology hotplugd: hotplugd.c:1421 ==== SATA disk [sde] Model: [ST2000DL003-9VT166 ] ==== 07:59:01+02:00 Synology hotplugd: hotplugd.c:1422 ==== SATA disk [sde] Serial number: [] ==== 07:59:01+02:00 Synology hotplugd: hotplugd.c:1423 ==== SATA disk [sde] Firmware version: [] ==== 07:59:02+02:00 Synology serv-bootup-timeout.sh: all service finish boot up. 07:59:02+02:00 Synology synofstool: volume_fs_cache_dump.c:38 [Info] NO volume exists, skip generate fstab 07:59:02+02:00 Synology root: == DSM 6.0 8754-0 finished boot up == 07:59:30+02:00 Synology sk: SmartDataRead(102) open device /dev/sda fail 07:59:30+02:00 Synology sk: disk/disk_temperature_get.c:75 read value /dev/sda fail 07:59:30+02:00 Synology sk: SmartDataRead(102) open device /dev/sdb fail 07:59:30+02:00 Synology sk: disk/disk_temperature_get.c:75 read value /dev/sdb fail 07:59:30+02:00 Synology sk: SmartDataRead(102) open device /dev/sdc fail 07:59:30+02:00 Synology sk: disk/disk_temperature_get.c:75 read value /dev/sdc fail 07:59:30+02:00 Synology sk: SmartDataRead(102) open device /dev/sdd fail 07:59:30+02:00 Synology sk: disk/disk_temperature_get.c:75 read value /dev/sdd fail 07:59:30+02:00 Synology sk: SmartDataRead(102) open device /dev/sde fail 07:59:30+02:00 Synology sk: disk/disk_temperature_get.c:75 read value /dev/sde fail 08:00:25+02:00 Synology kernel: [ 157.147156] perf interrupt took too long (2519 > 5000), lowering kernel.perf_event_max_sample_rate to 50000 08:00:30+02:00 Synology sk: SmartDataRead(102) open device /dev/sda fail 08:00:30+02:00 Synology sk: disk/disk_temperature_get.c:75 read value /dev/sda fail 08:00:30+02:00 Synology sk: SmartDataRead(102) open device /dev/sdb fail 08:00:30+02:00 Synology sk: disk/disk_temperature_get.c:75 read value /dev/sdb fail Spoiler 19:31:08+02:00 Synology syno_scemd_connector: scemd_connector/scemd_connector.c:133 Fail to sendto() for scemd connector client. 19:31:09+02:00 Synology syno_scemd_connector: scemd_connector/scemd_connector.c:133 Fail to sendto() for scemd connector client. 19:31:13+02:00 Synology syno_scemd_connector: scemd_connector/scemd_connector.c:133 Fail to sendto() for scemd connector client. 19:31:15+02:00 Synology syno_scemd_connector: SYSTEM: Last message 'scemd_connector/scem' repeated 2 times, suppressed by syslog-ng on Synology 19:31:15+02:00 Synology scemd: event_handler.c:291 event handler thread 139921202009856 created 19:31:15+02:00 Synology scemd: event_handler.c:98 Fail to sendto() for scemd event handler client. 19:31:15+02:00 Synology scemd: show_module_type.c:35 fan_type=6, raid_type=1, led_type=3, thermal_type=2, diskled_ctrl_type=1, auto_poweron_type=1, dual_power_type=1, usbcopy_type=0, fan_number=1, eunit_pwron_type=2, pis_type=0, rtc_type=3, lcm_type=2, wifi_wps_type=254 19:31:16+02:00 Synology syno_scemd_connector: scemd_connector/scemd_connector.c:133 Fail to sendto() for scemd connector client. 19:31:43+02:00 Synology scemd: fan_config_get.c:46 Type: INTERNAL Fan Mode: LOW 19:31:43+02:00 Synology scemd: cpu_frequency_handler.c:75 glob cpu gover fail 19:31:43+02:00 Synology scemd: manage_services.c:497 hw polling thread 139921185224448 created 19:31:43+02:00 Synology scemd: manage_services.c:497 disk led ctrl thread 139921109022464 created 19:31:43+02:00 Synology scemd: manage_services.c:497 scemd connector thread 139921100629760 created 19:31:43+02:00 Synology scemd: scemd_connector.c:150 scemd connector thread start. 19:31:43+02:00 Synology scemd: manage_services.c:497 led ctrl thread 139921092237056 created 19:31:46+02:00 Synology scemd: SmartDataRead(102) open device /dev/sda fail 19:31:46+02:00 Synology scemd: disk/disk_temperature_get.c:75 read value /dev/sda fail 19:31:46+02:00 Synology scemd: SmartDataRead(102) open device /dev/sdb fail 19:31:46+02:00 Synology scemd: disk/disk_temperature_get.c:75 read value /dev/sdb fail 19:31:46+02:00 Synology scemd: SmartDataRead(102) open device /dev/sdc fail 19:31:46+02:00 Synology scemd: disk/disk_temperature_get.c:75 read value /dev/sdc fail 19:31:46+02:00 Synology scemd: SmartDataRead(102) open device /dev/sdd fail 19:31:46+02:00 Synology scemd: disk/disk_temperature_get.c:75 read value /dev/sdd fail 19:31:46+02:00 Synology scemd: SmartDataRead(102) open device /dev/sde fail 19:31:46+02:00 Synology scemd: disk/disk_temperature_get.c:75 read value /dev/sde fail 19:31:46+02:00 Synology scemd: SmartDataRead(102) open device /dev/sda fail 19:31:46+02:00 Synology scemd: disk/disk_temperature_get.c:75 read value /dev/sda fail ... 2018-10-07T19:31:47+02:00 Synology scemd: fan_config_get.c:46 Type: INTERNAL Fan Mode: LOW 2018-10-07T19:31:47+02:00 Synology scemd: raid_sys_volume_check.c:164 MD0 active disks 5, designed disks 5 2018-10-07T19:31:47+02:00 Synology scemd: raid_sys_volume_check.c:164 MD1 active disks 5, designed disks 5 2018-10-07T19:31:47+02:00 Synology scemd: polling_hibernation_timer.c:1194 Hibernation enable, idle minutes 20 ... 2018-10-07T19:33:17+02:00 Synology scemd: manutild_ip_check.c:40 stop manutild. ... 2018-10-07T19:53:58+02:00 Synology scemd: disk_xml.c:352 Error: Failed to get firmware and SN of /dev/sda 2018-10-07T19:53:59+02:00 Synology scemd: fan_config_get.c:46 Type: INTERNAL Fan Mode: LOW 2018-10-07T19:53:59+02:00 Synology scemd: fan/fan_table_type_disk_temperature_ops.c:69 Get temperature failed 2018-10-07T19:53:59+02:00 Synology scemd: fan/fan_table_type_disk_temperature_ops.c:69 Get temperature failed 2018-10-07T19:53:59+02:00 Synology scemd: fan/fan_table_type_disk_temperature_ops.c:69 Get temperature failed 2018-10-07T19:53:59+02:00 Synology scemd: SYSTEM: Last message 'fan/fan_table_type_d' repeated 4 times, suppressed by syslog-ng on Synology 2018-10-07T19:53:59+02:00 Synology scemd: fan/fan_table_type_disk_temperature_ops.c:220 Invalid Disks temperature -1 2018-10-07T19:53:59+02:00 Synology scemd: fan/fan_config_table_lookup.c:175 <disk_temperature> Temperature Get fail 2018-10-07T19:53:59+02:00 Synology scemd: cpu_frequency_handler.c:75 glob cpu gover fail 2018-10-07T19:54:03+02:00 Synology scemd: event_handler.c:291 event handler thread 139903537268480 created 2018-10-07T19:54:03+02:00 Synology scemd: show_module_type.c:35 fan_type=6, raid_type=1, led_type=3, thermal_type=2, diskled_ctrl_type=1, auto_poweron_type=1, dual_power_type=1, usbcopy_type=0, fan_number=1, eunit_pwron_type=2, pis_type=0, rtc_type=3, lcm_type=2, wifi_wps_type=254 Edited June 25, 2019 by Polanskiman Added spoiler. Quote Link to comment Share on other sites More sharing options...
Olegin Posted October 8, 2018 Share #2 Posted October 8, 2018 Ask it to synology support. Quote Link to comment Share on other sites More sharing options...
simkard Posted October 8, 2018 Author Share #3 Posted October 8, 2018 😁 Except the fact that this model (DS1010+) is not made to support anything higher than DSM 5.2 Update 8. This is why I'm looking for a solution here 😉 Quote Link to comment Share on other sites More sharing options...
Olegin Posted October 8, 2018 Share #4 Posted October 8, 2018 It seems to me unlikely to help you unless you decide to make xpenology 😀 Quote Link to comment Share on other sites More sharing options...
simkard Posted October 8, 2018 Author Share #5 Posted October 8, 2018 Hum I agree on that, except the fact that I just started investagating DSM contents and structure. As XPenology seems to work with versions above 6.0, I'm quite sure it already experienced such problems like the one I'm facing. By the way, I'm pretty sure the workaroung is easy (maybe copying files from DSM6.0 to the one I want to install), except the fact that I don't know the software/hardware protections that are contained in DSM starting on the problematic version I'm facing. Good thing to know : All versions up to 6.2.1 seems to have the same behavior, so resolving 1 problem on 1 version ... might resolve all problems for all versions and that is a good pain point that can be killed. Do you have some knowledge about this ? I'm willing to have new ideas to try on my actual environment. Good thing on my side : I own a DS1010+ but I have access to a DS1511+ too, so maybe I have all I is needed to resolve this damn thing for me and others with Synology NASes that are not supported any longer but can work perfectly fine with new DSM updates. Thanks for yout time anyway. Quote Link to comment Share on other sites More sharing options...
Olegin Posted October 8, 2018 Share #6 Posted October 8, 2018 I mean, you'll create a new one. Quote Link to comment Share on other sites More sharing options...
simkard Posted October 8, 2018 Author Share #7 Posted October 8, 2018 Hum ... I did not understand what you said. Does that means : I won't help you because you're not helping XPEnology ? If that is the case ... then it is too bad unfortunately ☹️ Quote Link to comment Share on other sites More sharing options...
Olegin Posted October 8, 2018 Share #8 Posted October 8, 2018 I meant that in this forum discuss xpenology only, and not the synology hardware products and their problems with the support. Quote Link to comment Share on other sites More sharing options...
simkard Posted October 8, 2018 Author Share #9 Posted October 8, 2018 Ah ok, I understand that, and actually this is not a Synology support related problem ... hum not really at least What I'm trying to achieve is something pretty similar to XPEnology : putting DSM on unsupported hardware. Unsupported hardware can be server H/W ... or Synology's products (which are not supported any logner) right ? I'm quite sure that when XPEnology has been made, the case I'm facing has been encountered. Quote Link to comment Share on other sites More sharing options...
Olegin Posted October 8, 2018 Share #10 Posted October 8, 2018 37 минут назад, simkard сказал: Unsupported hardware can be server H/W ... or Synology's products (which are not supported any logner) right ? The old hw is very likely to not work with the latest versions of the DSM, no matter who is the manufacturer of it. Quote Link to comment Share on other sites More sharing options...
simkard Posted October 8, 2018 Author Share #11 Posted October 8, 2018 DS1010+ and DS1511+ are identical in terms of H/W. Only exceptions are : CPU (Intel ATOM D510 vs D525) : just a matter of Mhz eSATA port config Why shouldn't they be compatible so ? Quote Link to comment Share on other sites More sharing options...
Dfds Posted October 8, 2018 Share #12 Posted October 8, 2018 @simkard Please do not post multiple threads about the same topic, I have deleted your other thread. Quote Link to comment Share on other sites More sharing options...
simkard Posted October 8, 2018 Author Share #13 Posted October 8, 2018 il y a 1 minute, Dfds a dit : @simkard Please do not post multiple threads about the same topic, I have deleted your other thread. Sorry, When I created it I wanted to move here, but I couldn't using the thread options I had ... my bad. Quote Link to comment Share on other sites More sharing options...
Dfds Posted October 8, 2018 Share #14 Posted October 8, 2018 4 minutes ago, simkard said: Sorry, When I created it I wanted to move here, but I couldn't using the thread options I had ... my bad. No problem, for future reference you can message myself or one of the other moderators to get the thread moved. Quote Link to comment Share on other sites More sharing options...
Olegin Posted October 8, 2018 Share #15 Posted October 8, 2018 19 минут назад, simkard сказал: Why shouldn't they be compatible so ? I have already said that only synology support can answer to your question. I haven't seen discussions about DS1010+ and DS1511+ hw on this forum. Quote Link to comment Share on other sites More sharing options...
simkard Posted October 8, 2018 Author Share #16 Posted October 8, 2018 Olegin, I know that no one probably discussed such a thing here ... I'm just trying something that no one tried at all. Like we say in French : "There is a beginning for everything" ... and here I'm trying to do so. I think my problem is software dependant and not related to hardware here. Quote Link to comment Share on other sites More sharing options...
Olegin Posted October 8, 2018 Share #17 Posted October 8, 2018 (edited) 14 минуты назад, simkard сказал: Like we say in French : "There is a beginning for everything" ... and here I'm trying to do so. If you want to begin, you can try to inatall 6.1(for example from 3516) on your DS1010+. Read this Edited October 8, 2018 by Olegin Quote Link to comment Share on other sites More sharing options...
simkard Posted October 26, 2018 Author Share #18 Posted October 26, 2018 Hello All, Just to inform you that I successfully installed latest DS 6.2.1 on my DS1010+ with everything running fine so far ... even automatic updates apply and run fine after reboot of NAS. I managed to get this damn thing running and installing updates after some modifications. Not publishing this method will allow me to keep the new updates running ... maybe I'll publish them when DSM 7.0 will be out and if I successfully manage to deploy it on my DS1010+. Cheers 2 Quote Link to comment Share on other sites More sharing options...
clemthion Posted January 2, 2019 Share #19 Posted January 2, 2019 Would be very keen to know how you performed the update from 5.2 to 6.2.1 on 1010+ .... Mine would like to be upgraded too ;-) It works perfectly, not reason to buy a new one except because of the software limitation ..... Thkx Quote Link to comment Share on other sites More sharing options...
ElJojo Posted January 3, 2019 Share #20 Posted January 3, 2019 I also asked him on PM, and even twitter, he never answered, he definitevly doesnt want to share this even privately sadly. Quote Link to comment Share on other sites More sharing options...
simkard Posted January 3, 2019 Author Share #21 Posted January 3, 2019 Hello everyone, As I said, I will wait for the DSM 7.x to be released. At that point, my hack works fine on a DS1010, and it even receives automatic updates. In a near future, I will probably release something, but anywa, in the meantime, please be patient and keep your good'ol NASes devices preciously ... they are still not good to go to the recycle bin ! And don't worry, I will post back here soon. Quote Link to comment Share on other sites More sharing options...
coderCK Posted January 14, 2019 Share #22 Posted January 14, 2019 I am also wanting to know more about this potential upgrade for my DS1010+. It is a shame that Synology discontinued support even though there is no hardware limitation, only a self-imposed artificial limitation. What is the reason you are waiting for DSM 7.0 to be released? Quote Link to comment Share on other sites More sharing options...
ElJojo Posted January 21, 2019 Share #23 Posted January 21, 2019 I think he wants to wait cause there's no chances Synology would patch then the DSM6 to make it not compatble with the hack for ds1010. So ok i'll wait for any news from you @simkard and i'll come back to check Quote Link to comment Share on other sites More sharing options...
coderCK Posted January 23, 2019 Share #24 Posted January 23, 2019 That sounds like a decent enough reason, though I still get patches for DSM 5.2 on my DS1010+. Yes, they are security patches for vulnerabilities, but I wouldn't put it past Synology to sneak in a patch disabling "unauthorized" upgrades if they really wanted to do it. In any case, I'm looking forward to the release of DSM 7 so we can see this upgrade process. Quote Link to comment Share on other sites More sharing options...
simkard Posted January 28, 2019 Author Share #25 Posted January 28, 2019 I'm still around guys, don't worry. Just waiting for DSM7 BETA to be released for me to test my things, and then, I will release something when DSM7 stable will be release definetely. Please stay notified on this post 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.