Matty123

Transition Members
  • Content Count

    5
  • Joined

  • Last visited

Community Reputation

0 Neutral

About Matty123

  • Rank
    Newbie

Recent Profile Visitors

The recent visitors block is disabled and is not being shown to other users.

  1. So tonight I decided to try and configure the virtual machine manager on top of my normal network bond. To cut the story short as soon as I enabled the virtual switch on the bond I lost connectivity even after a reboot. I then did a reinstall option during boot and chose to migrate my data, all was good with the find.synology.com piece but after a reboot it didn't come up and now a further reinstall isn't establishing standard DHCP networking to the unit. So i'm concerned that the migrate option may have pulled down the new 6.2.x release and borked the entire thing I've had xpenology running for 6 months or so, but generally without issue. I'm now concerned I may have just made my system unrecoverable? This is on a HP Microserver Gen8 bare metal Not sure what to do next, so would appreciate any advice you can offer to help me remedy the situation!
  2. Just tried to restart the DSM Service which has errored as before now. The kernel log shows the following; 2017-10-18T21:06:50+01:00 Synology-NAS kernel: [ 59.133796] cgroup: docker-runc (16032) created nested cgroup for controller "blkio" which has incomplete hierarchy support. Nested cgroups may change behavior in the future. 2017-10-19T03:41:34+01:00 Synology-NAS kernel: [23729.495250] perf interrupt took too long (2502 > 5000), lowering kernel.perf_event_max_sample_rate to 50000 2017-10-19T09:51:00+01:00 Synology-NAS kernel: [45889.037217] uart write failed 2017-10-19T09:51:01+01:00 Synology-NAS kernel: [45890.148756] uart write failed 2017-10-19T09:51:02+01:00 Synology-NAS kernel: [45891.250474] uart write failed 2017-10-19T09:51:04+01:00 Synology-NAS kernel: [45893.245612] SYNO.Core.Polli[723]: segfault at 7f4994cc27cc ip 00007f40dc3f5eea sp 00007fff9a69e700 error 4 in ld-2.20-2014.11.so[7f40dc3ed000+21000] 2017-10-19T09:51:05+01:00 Synology-NAS kernel: [45893.365873] SYNO.Core.Netwo[14506]: segfault at 7fbb734f3db4 ip 00007fb6fda91eea sp 00007ffdca5fa440 error 4 in ld-2.20-2014.11.so[7fb6fda89000+21000] 2017-10-19T09:51:05+01:00 Synology-NAS kernel: [45893.505629] SYNO.Finder.Fil[747]: segfault at 7f4994cc27cc ip 00007f40dc3f5eea sp 00007fff9a69e6b0 error 4 in ld-2.20-2014.11.so[7f40dc3ed000+21000] 2017-10-19T09:51:05+01:00 Synology-NAS kernel: [45894.199806] SYNO.Core.Syste[783]: segfault at 7f4555465db4 ip 00007f40dc3f5eea sp 00007fff9a69e310 error 4 in ld-2.20-2014.11.so[7f40dc3ed000+21000] 2017-10-19T09:51:08+01:00 Synology-NAS kernel: [45896.406349] SYNO.Core.UserS[781]: segfault at 7f4994cc27cc ip 00007f40dc3f5eea sp 00007fff9a69e6e0 error 4 in ld-2.20-2014.11.so[7f40dc3ed000+21000] 2017-10-19T09:51:08+01:00 Synology-NAS kernel: [45896.997674] SYNO.Core.DataC[785]: segfault at 7f4994cc27cc ip 00007f40dc3f5eea sp 00007fff9a69e700 error 4 in ld-2.20-2014.11.so[7f40dc3ed000+21000] 2017-10-19T09:51:08+01:00 Synology-NAS kernel: [45897.196172] SYNO.Entry.Requ[787]: segfault at 7f4994cc27cc ip 00007f40dc3f5eea sp 00007fff9a69f080 error 4 in ld-2.20-2014.11.so[7f40dc3ed000+21000] 2017-10-19T09:51:08+01:00 Synology-NAS kernel: [45897.255280] SYNO.Entry.Requ[791]: segfault at 7f4994cc27cc ip 00007f40dc3f5eea sp 00007fff9a69ed90 error 4 in ld-2.20-2014.11.so[7f40dc3ed000+21000] 2017-10-19T09:51:08+01:00 Synology-NAS kernel: [45897.268886] SYNO.Core.CMS.I[789]: segfault at 7f4994cc27cc ip 00007f40dc3f5eea sp 00007fff9a69e6f0 error 4 in ld-2.20-2014.11.so[7f40dc3ed000+21000] 2017-10-19T09:51:08+01:00 Synology-NAS kernel: [45897.283250] SYNO.Core.CMS.I[792]: segfault at 7f4994cc27cc ip 00007f40dc3f5eea sp 00007fff9a69e6f0 error 4 in ld-2.20-2014.11.so[7f40dc3ed000+21000] 2017-10-19T09:51:10+01:00 Synology-NAS kernel: [45898.407657] SYNO.Core.Polli[793]: segfault at 7f4994cc27cc ip 00007f40dc3f5eea sp 00007fff9a69e700 error 4 in ld-2.20-2014.11.so[7f40dc3ed000+21000] 2017-10-19T09:51:10+01:00 Synology-NAS kernel: [45898.561702] SYNO.Finder.Fil[795]: segfault at 7f4994cc27cc ip 00007f40dc3f5eea sp 00007fff9a69e6b0 error 4 in ld-2.20-2014.11.so[7f40dc3ed000+21000] 2017-10-19T09:51:10+01:00 Synology-NAS kernel: [45899.310076] SYNO.Core.Syste[800]: segfault at 7f4555465db4 ip 00007f40dc3f5eea sp 00007fff9a69e310 error 4 in ld-2.20-2014.11.so[7f40dc3ed000+21000] 2017-10-19T09:51:11+01:00 Synology-NAS kernel: [45899.984006] SYNO.Core.UserS[798]: segfault at 7f4994cc27cc ip 00007f40dc3f5eea sp 00007fff9a69e6e0 error 4 in ld-2.20-2014.11.so[7f40dc3ed000+21000] 2017-10-19T09:51:15+01:00 Synology-NAS kernel: [45903.363405] SYNO.Entry.Requ[808]: segfault at 7f4994cc27cc ip 00007f40dc3f5eea sp 00007fff9a69ed90 error 4 in ld-2.20-2014.11.so[7f40dc3ed000+21000] 2017-10-19T09:51:15+01:00 Synology-NAS kernel: [45903.464630] SYNO.Core.Polli[806]: segfault at 7f4994cc27cc ip 00007f40dc3f5eea sp 00007fff9a69e700 error 4 in ld-2.20-2014.11.so[7f40dc3ed000+21000] 2017-10-19T09:51:15+01:00 Synology-NAS kernel: [45903.615551] SYNO.Finder.Fil[809]: segfault at 7f4994cc27cc ip 00007f40dc3f5eea sp 00007fff9a69e6b0 error 4 in ld-2.20-2014.11.so[7f40dc3ed000+21000] 2017-10-19T09:51:15+01:00 Synology-NAS kernel: [45904.071579] SYNO.Entry.Requ[810]: segfault at 7f4994cc27cc ip 00007f40dc3f5eea sp 00007fff9a69f100 error 4 in ld-2.20-2014.11.so[7f40dc3ed000+21000] 2017-10-19T09:51:16+01:00 Synology-NAS kernel: [45904.418279] SYNO.Core.Syste[814]: segfault at 7f4555465db4 ip 00007f40dc3f5eea sp 00007fff9a69e310 error 4 in ld-2.20-2014.11.so[7f40dc3ed000+21000] 2017-10-19T09:51:16+01:00 Synology-NAS kernel: [45904.685134] SYNO.Entry.Requ[815]: segfault at 7f4994cc27cc ip 00007f40dc3f5eea sp 00007fff9a69f080 error 4 in ld-2.20-2014.11.so[7f40dc3ed000+21000] 2017-10-19T09:51:17+01:00 Synology-NAS kernel: [45906.241663] SYNO.Entry.Requ[816]: segfault at 7f4994cc27cc ip 00007f40dc3f5eea sp 00007fff9a69f100 error 4 in ld-2.20-2014.11.so[7f40dc3ed000+21000] 2017-10-19T09:51:18+01:00 Synology-NAS kernel: [45906.389310] SYNO.Entry.Requ[818]: segfault at 7f4555465db4 ip 00007f40dc3f5eea sp 00007fff9a69f060 error 4 in ld-2.20-2014.11.so[7f40dc3ed000+21000] 2017-10-19T09:51:19+01:00 Synology-NAS kernel: [45907.468741] SYNO.Entry.Requ[822]: segfault at 7f4994cc27cc ip 00007f40dc3f5eea sp 00007fff9a69ed90 error 4 in ld-2.20-2014.11.so[7f40dc3ed000+21000] 2017-10-19T09:51:19+01:00 Synology-NAS kernel: [45908.103518] SYNO.Core.UserS[820]: segfault at 7f4994cc27cc ip 00007f40dc3f5eea sp 00007fff9a69e6e0 error 4 in ld-2.20-2014.11.so[7f40dc3ed000+21000] 2017-10-19T09:51:19+01:00 Synology-NAS kernel: [45908.108376] synoscgi_______[823]: segfault at 7f4555465db4 ip 00007f40dc3f5eea sp 00007fff9a69d320 error 4 in ld-2.20-2014.11.so[7f40dc3ed000+21000] 2017-10-19T09:51:20+01:00 Synology-NAS kernel: [45909.099885] synoscgi_______[824]: segfault at 7f4555465db4 ip 00007f40dc3f5eea sp 00007fff9a69d320 error 4 in ld-2.20-2014.11.so[7f40dc3ed000+21000] 2017-10-19T09:51:21+01:00 Synology-NAS kernel: [45909.637583] synoscgi_______[827]: segfault at 7f4555465db4 ip 00007f40dc3f5eea sp 00007fff9a69d320 error 4 in ld-2.20-2014.11.so[7f40dc3ed000+21000] 2017-10-19T09:51:21+01:00 Synology-NAS kernel: [45909.852265] synoscgi_______[828]: segfault at 7f4555465db4 ip 00007f40dc3f5eea sp 00007fff9a69d320 error 4 in ld-2.20-2014.11.so[7f40dc3ed000+21000] 2017-10-19T09:51:21+01:00 Synology-NAS kernel: [45909.993599] synoscgi_______[829]: segfault at 7f4555465db4 ip 00007f40dc3f5eea sp 00007fff9a69d320 error 4 in ld-2.20-2014.11.so[7f40dc3ed000+21000] 2017-10-19T09:51:21+01:00 Synology-NAS kernel: [45910.134312] synoscgi_______[830]: segfault at 7f4555465db4 ip 00007f40dc3f5eea sp 00007fff9a69d320 error 4 in ld-2.20-2014.11.so[7f40dc3ed000+21000] 2017-10-19T09:51:21+01:00 Synology-NAS kernel: [45910.303305] synoscgi_______[831]: segfault at 7f4555465db4 ip 00007f40dc3f5eea sp 00007fff9a69d320 error 4 in ld-2.20-2014.11.so[7f40dc3ed000+21000] 2017-10-19T09:51:22+01:00 Synology-NAS kernel: [45910.763111] synoscgi_______[832]: segfault at 7f4555465db4 ip 00007f40dc3f5eea sp 00007fff9a69d320 error 4 in ld-2.20-2014.11.so[7f40dc3ed000+21000] 2017-10-19T09:51:22+01:00 Synology-NAS kernel: [45911.010932] synoscgi_______[834]: segfault at 7f4555465db4 ip 00007f40dc3f5eea sp 00007fff9a69d320 error 4 in ld-2.20-2014.11.so[7f40dc3ed000+21000] 2017-10-19T09:51:26+01:00 Synology-NAS kernel: [45914.899217] synoscgi_______[835]: segfault at 7f4555465db4 ip 00007f40dc3f5eea sp 00007fff9a69d320 error 4 in ld-2.20-2014.11.so[7f40dc3ed000+21000] 2017-10-19T09:51:29+01:00 Synology-NAS kernel: [45917.907168] SYNO.Core.Deskt[669]: segfault at 7f4994cc27cc ip 00007f40dc3f5eea sp 00007fff9a6982b0 error 4 in ld-2.20-2014.11.so[7f40dc3ed000+21000] 2017-10-19T09:51:30+01:00 Synology-NAS kernel: [45918.608297] synoscgi_______[847]: segfault at 7f4555465db4 ip 00007f40dc3f5eea sp 00007fff9a69d320 error 4 in ld-2.20-2014.11.so[7f40dc3ed000+21000] 2017-10-19T09:51:33+01:00 Synology-NAS kernel: [45921.396562] synoscgi_______[857]: segfault at 7f4555465db4 ip 00007f40dc3f5eea sp 00007fff9a69d320 error 4 in ld-2.20-2014.11.so[7f40dc3ed000+21000] 2017-10-19T09:51:33+01:00 Synology-NAS kernel: [45921.808960] synoscgi_______[859]: segfault at 7f4555465db4 ip 00007f40dc3f5eea sp 00007fff9a69d320 error 4 in ld-2.20-2014.11.so[7f40dc3ed000+21000] 2017-10-19T09:51:33+01:00 Synology-NAS kernel: [45922.054167] synoscgi_______[861]: segfault at 7f4555465db4 ip 00007f40dc3f5eea sp 00007fff9a69d320 error 4 in ld-2.20-2014.11.so[7f40dc3ed000+21000] 2017-10-19T09:51:33+01:00 Synology-NAS kernel: [45922.214950] synoscgi_______[862]: segfault at 7f4555465db4 ip 00007f40dc3f5eea sp 00007fff9a69d320 error 4 in ld-2.20-2014.11.so[7f40dc3ed000+21000] 2017-10-19T09:52:47+01:00 Synology-NAS kernel: [45995.703834] synoscgi_______[863]: segfault at 7f4555465db4 ip 00007f40dc3f5eea sp 00007fff9a69d320 error 4 in ld-2.20-2014.11.so[7f40dc3ed000+21000] 2017-10-19T10:01:47+01:00 Synology-NAS kernel: [46535.635544] synoscgi_______[941]: segfault at 7f4555465db4 ip 00007f40dc3f5eea sp 00007fff9a69d320 error 4 in ld-2.20-2014.11.so[7f40dc3ed000+21000] 2017-10-19T10:03:25+01:00 Synology-NAS kernel: [46633.876323] synoscgi_______[1464]: segfault at 7f4555465db4 ip 00007f40dc3f5eea sp 00007fff9a69d320 error 4 in ld-2.20-2014.11.so[7f40dc3ed000+21000] 2017-10-19T10:04:29+01:00 Synology-NAS kernel: [46697.435215] synoscgi_______[1543]: segfault at 7f4555465db4 ip 00007f40dc3f5eea sp 00007fff9a69d320 error 4 in ld-2.20-2014.11.so[7f40dc3ed000+21000] 2017-10-19T10:07:25+01:00 Synology-NAS kernel: [46873.898628] synoscgi_______[1650]: segfault at 7f4555465db4 ip 00007f40dc3f5eea sp 00007fff9a69d320 error 4 in ld-2.20-2014.11.so[7f40dc3ed000+21000]
  3. Yes, I ended up doing a re-install option when booting as a reboot didn't cure it. That got me back up and running until this morning when the same thing has happened again! I've just checked the synoscgi log and can see the invlaid ELF header messages 2017-10-18T19:46:51+0100 /usr/syno/sbin/synoscgi________________________________________________________: error while loading shared libraries: /lib/libsynoshare.so.6: invalid ELF header
  4. Hi I could do with some help. Device has been fine and no recent update installed, but came to the device tonight and couldn't get to the main synology page, i just got "Sorry, the page you are looking for is not found". I could still access the device via SSH and SMB so I did a reboot thinking that would cure it. No services are now starting, I can access it via SSH only. Checking the logs, no update has happened since v5 /var/log/synoupdate.log start critical update to buildnumber: 15152 original smallfixnumber: 5 new_smallfixnumber: 6 build date: 2017/10/03 /var/log/upstart/synoscgi.log /usr/syno/sbin/synoscgi________________________________________________________: error while loading shared libraries: /lib/libsynoshare.so.6: invalid ELF header root@Synology-NAS:/var/log# synoservice --status DSM service [DSM] status=[error] required upstart job: [synoscgi] is stop. ======================================= find.synology.com is unable to locate the device I could really do with some help please, Its been fine and I've never had an issue until now. Is there a way for me to recover without loosing my data? I did a config backup a couple of days ago