Synology hängt sich alle 2-3 Wochen auf

[FricklerAtHome]

@Rotbart
Geht sicher auch! Werde ich mal testen.
Ich bin aktuell bei PRTG da ich auch mein gesamtes Smart-Home und viele andere Komponenten im DASH-Board (also auch ohne snmp, aber mittels SQL Abfrage) auf einer Seite abbilden kann. PRTG kann also auch nicht nur snmp-Meldungen.

Man verläßt leider viel zu selten den geritten Gaul, mangels Erfahrung oder Erkenntnis mit den neuen Pferden!
Danke für den Tipp!

Mein PRTG läuft auch in einer WIN10 VM zusammen mit meinem kommerziellen MAIL-STORE Archiver.

F@H

 

[threadstone]

Du könntest die Temperaturen soweit das möglich ist dszu nehmen

Bei mir sieht es jetzt so aus. Ich habe auch noch die I/O-Werte der Platten mit reingenommen, falls es an den Platten liegen sollte.

 

[StanleyS]

Interessanter Weise habe ich mit meiner 918+ seit einiger Zeit das selbe Problem.
Die Diskstation ist jedoch eher unregelmäßig und ohne erkennbaren Grund plötzlich nicht erreichbar.
Die Diskstation an sich selbst scheint ganz normal weiter zu laufen, die Loginseite ist via https erreichbar, es erscheint jedoch keine Loginmaske. In Entwicklertools sieht man, dass die entsprechende Anfrage mit einem 502er beanwortet wird.
Login via SSH auch nicht möglich.
Alles was hilft ist die hart neu zu starten, danach läuft die einige Zeit weiter.

 

[plang.pl]

Poste doch mal die SMART-Werte. Anleitung siehe meine Signatur

 

[StanleyS]

Falls ich damit gemeint war..

 

[dil88]

Die SMART-Werte sind ok. Hast Du schon ins Protokoll-Center/Logfiles geschaut?

 

[StanleyS]

Da findet sich absolut nichts verwertbares. Die Synology hat sich z.B. gestern wohl gegen 10-11 Uhr aufgehangen, bis ich die kurz nach 18 Uhr vollständig aus und wieder eingeschaltet habe.
Zwischen 03:07 und dem Neustart finden sich allerdings gar keine Einträge im Log.

Interessant ist auch, dass wohl nicht alle Dienste gekillt werden, paar Docker-Container laufen weiterhin und sind erreichbar.
Anmeldung, SSH, Dateidienste, Surveillance sind jedoch tot, bzw. nicht erreichbar.

Ich habe inzwischen schon eingestellt, dass die Diskstation täglich um 3 Uhr nachts neustartet, das hilft auch nicht. Früher ist die Monate lang durchgelaufen, ohne ausgeschaltet zu werden.

 

[Rotbart]

Kannst ja mal ein Ram-Test machen.

 

[adahmen]

Ich hatte bei meiner 720+ ein ähnliches Verhalten. Spontane Neustarts und teils sehr langsam bis nicht erreichbar.
Am Ende war es ein korruptes Filesystem kombiniert mit einem Speicher (hatte auf 10 GB erweitert), der scheinbar auch nicht mehr okay war (der Speichertest nach dem Einbau war okay - aber nach einiger Zeit dann nicht mehr). Ich hatte auch einen Stromausfall :-(
Ich habe am Ende komplett neu aufgesetzt und ein Backup zurückgespielt - und natürlich den Speicher getauscht. Seitdem ist Ruhe.

Im Protokoll-Center war damals auch absolut nichts zu finden.

Am Ende war aber /var/log/messages voll mit Fehlermeldungen.
Hast Du da schonmal nachgeschaut?

 

[threadstone]

Speicherproblem könnte bei mir auch fast der Fall sein. Ich hatte vor ca. 2 Monaten auch meinen Speicher aufgerüstet (original Synology-Riegel).
Wie macht man den am besten einen Ram-Test?

@adahmen wie komme ich denn auf /var/log/messages um mal nachzusehen?

 

[ctrlaltdelete]

Über den Synology Assistenten, ist eine APP für Windows.

 

[threadstone]

Danke. Ich habs gefunden. Mache ich die Tage mal. Erst mal den Samstag abwarten. Da hängt sie sich ja i.d.R. auf.

 

[adahmen]

@adahmen wie komme ich denn auf /var/log/messages um mal nachzusehen?

Entweder über SSH auf der Synology anmelden und sich die Datei anschauen.
Zum Beispiel mit dem Befehl: "tail -500 /var/log/messages". Damit kann man sich die letzten 500 Zeilen anzeigen.

Oder das Community-Paket LogAnalysis installieren. Dann geht es auch über den DSM (so habe ich es gemacht). Einfach mal hier im Forum nach LogAnalysis suchen.

Gib mal Bescheid, ob da Fehlermeldungen zu sehen sind.

 

[threadstone]

Gib mal Bescheid, ob da Fehlermeldungen zu sehen sind.

Das Installieren hat funktioniert. Nachdem ich dann auch noch root-Rechte vergeben habe, kann ich nun auf die messages-Datei zugreifen.

Ich bin mir nicht sicher ob da wirklich Fehler drin sind. Ein paar Sachen sind mir jedoch aufgefallen.

1) Ich hatte vor ein paar Tagen folgende Einträge. Diese tauchen nur am 18.2. von 3:15 bis 18:15 stündlich auf. Kann das evtl. mit AVR-Chart zusammenhängen? Ich hatte hier mit der Installation Probleme und habe erst später die Benutzerrechte eingestellt, so dass ich auch AVR-Chart sehen konnte (vorher war nur AVR-Einstellungen sichtbar)

2024-02-18T19:15:23+01:00 DS918plus synostgd-disk[12204]: smartctl/smartctl_ata_smart_info_get.c:528 Failed to get smart info on /dev/sda, 0xA00
2024-02-18T19:15:23+01:00 DS918plus synostgd-disk[12204]: smartctl/smartctl_ata_smart_info_update.c:49 Failed to update smart info on /dev/sda, 0xA00
2024-02-18T19:15:23+01:00 DS918plus synostgd-disk[12204]: smartctl/smartctl_total_status_cache_update.c:46 Failed to update smart info on device /dev/sda, 0xA00
2024-02-18T19:15:23+01:00 DS918plus synostgd-disk[12207]: smartctl/smartctl_ata_smart_info_get.c:528 Failed to get smart info on /dev/sdb, 0xA00
2024-02-18T19:15:23+01:00 DS918plus synostgd-disk[12207]: smartctl/smartctl_ata_smart_info_update.c:49 Failed to update smart info on /dev/sdb, 0xA00
2024-02-18T19:15:23+01:00 DS918plus synostgd-disk[12207]: smartctl/smartctl_total_status_cache_update.c:46 Failed to update smart info on device /dev/sdb, 0xA00
2024-02-18T19:15:23+01:00 DS918plus synostgd-disk[12211]: smartctl/smartctl_ata_smart_info_get.c:528 Failed to get smart info on /dev/sdc, 0xA00
2024-02-18T19:15:23+01:00 DS918plus synostgd-disk[12211]: smartctl/smartctl_ata_smart_info_update.c:49 Failed to update smart info on /dev/sdc, 0xA00
2024-02-18T19:15:23+01:00 DS918plus synostgd-disk[12211]: smartctl/smartctl_total_status_cache_update.c:46 Failed to update smart info on device /dev/sdc, 0xA00
2024-02-18T19:15:23+01:00 DS918plus synostgd-disk[12218]: smartctl/smartctl_ata_smart_info_get.c:528 Failed to get smart info on /dev/sda, 0xA00
2024-02-18T19:15:23+01:00 DS918plus synostgd-disk[12218]: smartctl/smartctl_ata_smart_info_get.c:246 Failed to get smart info on /dev/sda, 0xA00
2024-02-18T19:15:23+01:00 DS918plus synostgd-disk[12219]: smartctl/smartctl_ata_smart_info_get.c:528 Failed to get smart info on /dev/sdb, 0xA00
2024-02-18T19:15:23+01:00 DS918plus synostgd-disk[12219]: smartctl/smartctl_ata_smart_info_get.c:246 Failed to get smart info on /dev/sdb, 0xA00
2024-02-18T19:15:23+01:00 DS918plus synostgd-disk[12221]: smartctl/smartctl_ata_smart_info_get.c:528 Failed to get smart info on /dev/sdc, 0xA00
2024-02-18T19:15:23+01:00 DS918plus synostgd-disk[12221]: smartctl/smartctl_ata_smart_info_get.c:246 Failed to get smart info on /dev/sdc, 0xA00
2024-02-18T19:15:23+01:00 DS918plus synostgd-disk[12218]: smartctl/smartctl_ata_smart_info_get.c:528 Failed to get smart info on /dev/sda, 0xA00
2024-02-18T19:15:23+01:00 DS918plus synostgd-disk[12218]: smartctl/smartctl_ata_smart_info_get.c:246 Failed to get smart info on /dev/sda, 0xA00
2024-02-18T19:15:23+01:00 DS918plus synostgd-disk[12218]: disk/disk_current_health_get.c:122 SYNODiskAtaSmartInfoParse failed on /dev/sda
2024-02-18T19:15:23+01:00 DS918plus synostgd-disk[12219]: smartctl/smartctl_ata_smart_info_get.c:528 Failed to get smart info on /dev/sdb, 0xA00
2024-02-18T19:15:23+01:00 DS918plus synostgd-disk[12219]: smartctl/smartctl_ata_smart_info_get.c:246 Failed to get smart info on /dev/sdb, 0xA00
2024-02-18T19:15:23+01:00 DS918plus synostgd-disk[12219]: disk/disk_current_health_get.c:122 SYNODiskAtaSmartInfoParse failed on /dev/sdb
2024-02-18T19:15:23+01:00 DS918plus synostgd-disk[12221]: smartctl/smartctl_ata_smart_info_get.c:528 Failed to get smart info on /dev/sdc, 0xA00
2024-02-18T19:15:23+01:00 DS918plus synostgd-disk[12221]: smartctl/smartctl_ata_smart_info_get.c:246 Failed to get smart info on /dev/sdc, 0xA00
2024-02-18T19:15:23+01:00 DS918plus synostgd-disk[12221]: disk/disk_current_health_get.c:122 SYNODiskAtaSmartInfoParse failed on /dev/sdc
2024-02-18T19:15:23+01:00 DS918plus synostgd-disk[12204]: smartctl/smartctl_ata_smart_info_get.c:528 Failed to get smart info on /dev/sda, 0xA00
2024-02-18T19:15:23+01:00 DS918plus synostgd-disk[12204]: smartctl/smartctl_ata_smart_info_update.c:49 Failed to update smart info on /dev/sda, 0xA00
2024-02-18T19:15:23+01:00 DS918plus synostgd-disk[12204]: disk/disk_bad_sector_check.c:48 Failed to update smart info on device /dev/sda, 0xA00
2024-02-18T19:15:23+01:00 DS918plus synostgd-disk[12204]: disk_monitor.c:213 Failed to check disk error count /dev/sda
2024-02-18T19:15:23+01:00 DS918plus synostgd-disk[12207]: smartctl/smartctl_ata_smart_info_get.c:528 Failed to get smart info on /dev/sdb, 0xA00
2024-02-18T19:15:23+01:00 DS918plus synostgd-disk[12207]: smartctl/smartctl_ata_smart_info_update.c:49 Failed to update smart info on /dev/sdb, 0xA00
2024-02-18T19:15:23+01:00 DS918plus synostgd-disk[12207]: disk/disk_bad_sector_check.c:48 Failed to update smart info on device /dev/sdb, 0xA00
2024-02-18T19:15:23+01:00 DS918plus synostgd-disk[12207]: disk_monitor.c:213 Failed to check disk error count /dev/sdb
2024-02-18T19:15:23+01:00 DS918plus synostgd-disk[12211]: smartctl/smartctl_ata_smart_info_get.c:528 Failed to get smart info on /dev/sdc, 0xA00
2024-02-18T19:15:23+01:00 DS918plus synostgd-disk[12211]: smartctl/smartctl_ata_smart_info_update.c:49 Failed to update smart info on /dev/sdc, 0xA00
2024-02-18T19:15:23+01:00 DS918plus synostgd-disk[12211]: disk/disk_bad_sector_check.c:48 Failed to update smart info on device /dev/sdc, 0xA00
2024-02-18T19:15:23+01:00 DS918plus synostgd-disk[12211]: disk_monitor.c:213 Failed to check disk error count /dev/sdc

2) Ich habe mal geschaut, ob vor dem Absturz letzten Samstag etwas vermerkt ist. Direkt davor sind zwei Einträge, die mir nichts sagen. Dafür sind ab 15:54 Uhr jede Menge Einträge drin. Das müsste die Zeit sein, in der ich die Synology hart ausgeschaltet habe.

2024-02-17T12:09:52+01:00 DS918plus synouser[8450]: synouser.c:1114 ret 0
2024-02-17T15:30:33+01:00 DS918plus synoappnotify[20495]: io_utils.cpp:58 Failed to read, Resource temporarily unavailable
2024-02-17T15:30:33+01:00 DS918plus synoappnotify[20495]: /run/synoscgi-fastapi.sock APIRunner.cpp:1872 recv broken
2024-02-17T15:49:22+01:00 DS918plus root[24675]: No guests migrating
2024-02-17T15:54:28+01:00 DS918plus kernel: ACPI: RSDP 0x000000007AFFE014 000024 (v02 INSYDE)
2024-02-17T15:54:28+01:00 DS918plus kernel: ACPI: XSDT 0x000000007AFDA188 0000DC (v01 INSYDE INSYDE 00000003 01000013)
2024-02-17T15:54:28+01:00 DS918plus kernel: ACPI: FACP 0x000000007AFF5000 000114 (v06 INSYDE INSYDE 00000003 ACPI 00040000)
2024-02-17T15:54:28+01:00 DS918plus kernel: ACPI: DSDT 0x000000007AFE6000 00772B (v02 INSYDE INSYDE 00000003 ACPI 00040000)
2024-02-17T15:54:28+01:00 DS918plus kernel: ACPI: FACS 0x000000007AFAF000 000040
2024-02-17T15:54:28+01:00 DS918plus kernel: ACPI: FACS 0x000000007AFAF000 000040
2024-02-17T15:54:28+01:00 DS918plus kernel: ACPI: UEFI 0x000000007AFFD000 000236 (v01 INSYDE INSYDE 00000001 ACPI 00040000)
2024-02-17T15:54:28+01:00 DS918plus kernel: ACPI: BDAT 0x000000007AFFB000 000030 (v02 INSYDE INSYDE 00000000 ACPI 00040000)
2024-02-17T15:54:28+01:00 DS918plus kernel: ACPI: UEFI 0x000000007AFFA000 000042 (v01 INSYDE INSYDE 00000002 ACPI 00040000)
2024-02-17T15:54:28+01:00 DS918plus kernel: ACPI: SSDT 0x000000007AFF9000 000554 (v01 INSYDE Tpm2Tabl 00001000 ACPI 00040000)
2024-02-17T15:54:28+01:00 DS918plus kernel: ACPI: TPM2 0x000000007AFF8000 000034 (v03 INSYDE INSYDE 00000002 ACPI 00040000)
2024-02-17T15:54:28+01:00 DS918plus kernel: ACPI: PSDS 0x000000007AFF7000 00004D (v01 INSYDE INSYDE 00000005 ACPI 00040000)
2024-02-17T15:54:28+01:00 DS918plus kernel: ACPI: HPET 0x000000007AFF4000 000038 (v01 INSYDE INSYDE 00000003 ACPI 00040000)
2024-02-17T15:54:28+01:00 DS918plus kernel: ACPI: LPIT 0x000000007AFF3000 00005C (v01 INSYDE INSYDE 00000003 ACPI 00040000)
2024-02-17T15:54:28+01:00 DS918plus kernel: ACPI: APIC 0x000000007AFF2000 000084 (v03 INSYDE INSYDE 00000003 ACPI 00040000)
2024-02-17T15:54:28+01:00 DS918plus kernel: ACPI: MCFG 0x000000007AFF1000 00003C (v01 INSYDE INSYDE 00000003 ACPI 00040000)
2024-02-17T15:54:28+01:00 DS918plus kernel: ACPI: NPKT 0x000000007AFF0000 000065 (v01 INSYDE INSYDE 00000003 ACPI 00040000)
2024-02-17T15:54:28+01:00 DS918plus kernel: ACPI: WDRT 0x000000007AFEF000 000047 (v01 INSYDE INSYDE 00000003 ACPI 00040000)
2024-02-17T15:54:28+01:00 DS918plus kernel: ACPI: WSMT 0x000000007AFEE000 000028 (v01 INSYDE INSYDE 00000003 ACPI 00040000)
2024-02-17T15:54:28+01:00 DS918plus kernel: ACPI: SSDT 0x000000007AFE4000 00024A (v02 INSYDE UsbCTabl 00000003 ACPI 00040000)
2024-02-17T15:54:28+01:00 DS918plus kernel: ACPI: SSDT 0x000000007AFE3000 0000BC (v01 INSYDE Platform 00001000 ACPI 00040000)
2024-02-17T15:54:28+01:00 DS918plus kernel: ACPI: SSDT 0x000000007AFE2000 00045A (v02 INSYDE Cpu0Ist 00003000 ACPI 00040000)
2024-02-17T15:54:28+01:00 DS918plus kernel: ACPI: SSDT 0x000000007AFE1000 00072B (v02 INSYDE CpuSsdt 00003000 ACPI 00040000)
2024-02-17T15:54:28+01:00 DS918plus kernel: ACPI: SSDT 0x000000007AFDE000 002760 (v02 INSYDE SaSsdt 00003000 ACPI 00040000)
2024-02-17T15:54:28+01:00 DS918plus kernel: ACPI: FPDT 0x000000007AFDD000 000034 (v01 INSYDE INSYDE 00000002 ACPI 00040000)
2024-02-17T15:54:28+01:00 DS918plus kernel: ACPI: WDAT 0x000000007AFF6000 000104 (v01 INSYDE INSYDE 00000000 ACPI 00040000)
2024-02-17T15:54:28+01:00 DS918plus kernel: ACPI: BGRT 0x000000007AFE5000 000038 (v01 INSYDE INSYDE 00000001 ACPI 00040000)
2024-02-17T15:54:28+01:00 DS918plus kernel: ACPI: NHLT 0x000000007AFDC000 00002D (v00 INTEL EDK2 00000002 01000013)
2024-02-17T15:54:28+01:00 DS918plus kernel: Internal HD num: 4
2024-02-17T15:54:28+01:00 DS918plus kernel: Internal netif num: 2
2024-02-17T15:54:28+01:00 DS918plus kernel: Support HDD Hotplug.
2024-02-17T15:54:28+01:00 DS918plus kernel: Sata Port Map: 23
2024-02-17T15:54:28+01:00 DS918plus kernel: Synology Hardware Version: DS918+
2024-02-17T15:54:28+01:00 DS918plus kernel: Vender format version: 2
2024-02-17T15:54:28+01:00 DS918plus kernel: SYNO GPIO hdd detect pin: 18 179 176 175
2024-02-17T15:54:28+01:00 DS918plus kernel: SYNO GPIO hdd enable pin: 21 20 19 9
2024-02-17T15:54:28+01:00 DS918plus kernel: USB Vbus GPIO Control:
2024-02-17T15:54:28+01:00 DS918plus kernel: Gpp#13 - Host: dev_name:usb2 - Port:1 - Polarity: ACTIVE_HIGH
2024-02-17T15:54:28+01:00 DS918plus kernel: Gpp#13 - Host: dev_name:usb1 - Port:3 - Polarity: ACTIVE_HIGH
2024-02-17T15:54:28+01:00 DS918plus kernel: Gpp#11 - Host: dev_name:usb2 - Port:2 - Polarity: ACTIVE_HIGH
2024-02-17T15:54:28+01:00 DS918plus kernel: Gpp#11 - Host: dev_name:usb1 - Port:1 - Polarity: ACTIVE_HIGH
2024-02-17T15:54:28+01:00 DS918plus kernel: Serial Number: **********
2024-02-17T15:54:28+01:00 DS918plus kernel: [ 0.035143] ACPI: 7 ACPI AML tables successfully acquired and loaded
2024-02-17T15:54:28+01:00 DS918plus kernel: [ 0.485986] ACPI: Executed 3 blocks of module-level executable AML code
2024-02-17T15:54:28+01:00 DS918plus kernel: [ 0.499503] ACPI: Dynamic OEM Table Load:
2024-02-17T15:54:28+01:00 DS918plus kernel: [ 0.503784] ACPI: SSDT 0xFFFF88027639B800 00015F (v02 PmRef ApIst 00003000 INTL 20130117)
2024-02-17T15:54:28+01:00 DS918plus kernel: [ 0.825312] ACPI: Enabled 3 GPEs in block 00 to 7F
2024-02-17T15:54:28+01:00 DS918plus kernel: [ 14.141266] ata1: link is slow to respond, please be patient (ready=0)
2024-02-17T15:54:28+01:00 DS918plus kernel: [ 18.946032] ata1: softreset failed (device not ready)
2024-02-17T15:54:28+01:00 DS918plus kernel: [ 18.951677] ata1: SRST fail, set srst fail flag
2024-02-17T15:54:28+01:00 DS918plus kernel: [ 24.311773] ata1: link is slow to respond, please be patient (ready=0)
2024-02-17T15:54:28+01:00 DS918plus kernel: [ 25.954708] ata1: SATA link up 6.0 Gbps (SStatus 133 SControl 300)
2024-02-17T15:54:28+01:00 DS918plus kernel: [ 25.961614] ata1: link reset sucessfully clear error flags
2024-02-17T15:54:28+01:00 DS918plus kernel: [ 35.076258] ata2: link is slow to respond, please be patient (ready=0)
2024-02-17T15:54:28+01:00 DS918plus kernel: [ 39.881031] ata2: softreset failed (device not ready)
2024-02-17T15:54:28+01:00 DS918plus kernel: [ 39.886669] ata2: SRST fail, set srst fail flag
2024-02-17T15:54:28+01:00 DS918plus kernel: [ 45.246766] ata2: link is slow to respond, please be patient (ready=0)
2024-02-17T15:54:28+01:00 DS918plus kernel: [ 45.971742] ata2: SATA link up 6.0 Gbps (SStatus 133 SControl 300)
2024-02-17T15:54:28+01:00 DS918plus kernel: [ 45.978654] ata2: link reset sucessfully clear error flags
2024-02-17T15:54:28+01:00 DS918plus kernel: [ 46.054110] Change defer qc mode on external port for compatibility
2024-02-17T15:54:28+01:00 DS918plus kernel: [ 46.054111] Change defer qc mode on external port for compatibility
2024-02-17T15:54:28+01:00 DS918plus kernel: [ 46.054111] Change defer qc mode on external port for compatibility
2024-02-17T15:54:28+01:00 DS918plus kernel: [ 54.436328] ata3: link is slow to respond, please be patient (ready=0)
2024-02-17T15:54:28+01:00 DS918plus kernel: [ 59.237099] ata3: softreset failed (device not ready)
2024-02-17T15:54:28+01:00 DS918plus kernel: [ 59.242741] ata3: SRST fail, set srst fail flag
2024-02-17T15:54:28+01:00 DS918plus kernel: [ 64.600835] ata3: link is slow to respond, please be patient (ready=0)
2024-02-17T15:54:28+01:00 DS918plus kernel: [ 66.649752] ata3: SATA link up 6.0 Gbps (SStatus 133 SControl 300)
2024-02-17T15:54:28+01:00 DS918plus kernel: [ 66.656665] ata3: link reset sucessfully clear error flags
2024-02-17T15:54:28+01:00 DS918plus kernel: [ 75.092334] ata4: link is slow to respond, please be patient (ready=0)
2024-02-17T15:54:28+01:00 DS918plus kernel: [ 79.893100] ata4: softreset failed (device not ready)
2024-02-17T15:54:28+01:00 DS918plus kernel: [ 79.898743] ata4: SRST fail, set srst fail flag
2024-02-17T15:54:28+01:00 DS918plus kernel: [ 85.256842] ata4: link is slow to respond, please be patient (ready=0)
2024-02-17T15:54:28+01:00 DS918plus kernel: [ 86.846781] ata4: SATA link up 6.0 Gbps (SStatus 133 SControl 300)
2024-02-17T15:54:28+01:00 DS918plus kernel: [ 86.853693] ata4: link reset sucessfully clear error flags
2024-02-17T15:54:28+01:00 DS918plus kernel: [ 87.229763] ata5: SATA link down (SStatus 0 SControl 300)
2024-02-17T15:54:28+01:00 DS918plus kernel: [ 87.235810] ata5: No present pin info for SATA link down event
2024-02-17T15:54:28+01:00 DS918plus kernel: [ 88.113675] apollolake_synobios: loading out-of-tree module taints kernel.
2024-02-17T15:54:28+01:00 DS918plus kernel: [ 88.137870] correction with 0x00
2024-02-17T15:54:28+01:00 DS918plus kernel: [ 88.142559] 2024-2-17 14:54:13 UTC
2024-02-17T15:54:28+01:00 DS918plus kernel: [ 88.151137] Brand: Synology
2024-02-17T15:54:28+01:00 DS918plus kernel: [ 88.154256] Model: DS-918+
2024-02-17T15:54:28+01:00 DS918plus kernel: [ 88.157275] This is default settings: set group disks wakeup number to 1, spinup time deno 1
2024-02-17T15:54:28+01:00 DS918plus kernel: [ 88.195426] Module [apollolake_synobios] is removed.
2024-02-17T15:54:28+01:00 DS918plus kernel: [ 88.201095] synobios: unload
2024-02-17T15:54:28+01:00 DS918plus kernel: [ 91.034086] EXT4-fs (md0): couldn't mount as ext3 due to feature incompatibilities
2024-02-17T15:54:28+01:00 DS918plus kernel: [ 91.160286] EXT4-fs (md0): couldn't mount as ext3 due to feature incompatibilities
2024-02-17T15:54:28+01:00 DS918plus kernel: [ 91.672935] drivers/usb/core/hub.c (2962) Same device found. Change serial to 000000000
2024-02-17T15:54:28+01:00 DS918plus kernel: [ 93.736040] drivers/usb/core/hub.c (2962) Same device found. Change serial to 000000000
2024-02-17T15:54:28+01:00 DS918plus kernel: [ 93.745089] drivers/usb/core/hub.c (2962) Same device found. Change serial to 000000001
2024-02-17T15:54:28+01:00 DS918plus kernel: [ 93.754129] drivers/usb/core/hub.c (2962) Same device found. Change serial to 000000002
2024-02-17T15:54:28+01:00 DS918plus kernel: [ 93.763362] usb 1-3: ep 0x81 - rounding interval to 128 microframes, ep desc says 160 microframes
2024-02-17T15:54:28+01:00 DS918plus kernel: [ 95.765352] EXT4-fs (md0): couldn't mount as ext3 due to feature incompatibilities
2024-02-17T15:54:28+01:00 DS918plus kernel: [ 96.184681] EXT4-fs (md0): couldn't mount as ext3 due to feature incompatibilities
2024-02-17T15:54:28+01:00 DS918plus kernel: [ 102.448486] flashcache: flashcache-1.0-2023-09-23-22:10 initialized
2024-02-17T15:54:28+01:00 DS918plus kernel: [ 102.465068] flashcache_syno: flashcache-1.0-syno-v25-pin-file-2023-09-23-22:10-debug initialized
2024-02-17T15:54:28+01:00 DS918plus kernel: [ 103.394222] correction with 0x00
2024-02-17T15:54:28+01:00 DS918plus kernel: [ 103.396010] 2024-2-17 14:54:28 UTC
2024-02-17T15:54:28+01:00 DS918plus kernel: [ 103.396021] Brand: Synology
2024-02-17T15:54:28+01:00 DS918plus kernel: [ 103.396023] Model: DS-918+
2024-02-17T15:54:28+01:00 DS918plus kernel: [ 103.396026] This is default settings: set group disks wakeup number to 1, spinup time deno 1
2024-02-17T15:54:28+01:00 DS918plus kernel: [ 103.425622] syno_hddmon: module license 'Synology Inc.' taints kernel.
2024-02-17T15:54:28+01:00 DS918plus kernel: [ 103.425624] Disabling lock debugging due to kernel taint
2024-02-17T15:54:28+01:00 DS918plus kernel: [ 103.425885] Syno_HddMon: Initialization completed.
2024-02-17T15:54:28+01:00 DS918plus synocheckuser[6582]: synocheckuser.c:1228 start to check user data
2024-02-17T15:54:28+01:00 DS918plus synocheckuser[6582]: synocheckuser.c:1311 check user data finished
2024-02-17T15:54:29+01:00 DS918plus kernel: [ 104.624249] sd 5:0:0:0: [sdq] No Caching mode page found
2024-02-17T15:54:29+01:00 DS918plus kernel: [ 104.624251] sd 5:0:0:0: [sdq] Assuming drive cache: write through
2024-02-17T15:54:29+01:00 DS918plus kernel: [ 104.705832] sd 6:0:0:0: [sdr] No Caching mode page found
2024-02-17T15:54:29+01:00 DS918plus kernel: [ 104.705835] sd 6:0:0:0: [sdr] Assuming drive cache: write through
2024-02-17T15:54:29+01:00 DS918plus kernel: [ 104.798241] sd 7:0:0:0: [synoboot] No Caching mode page found
2024-02-17T15:54:29+01:00 DS918plus kernel: [ 104.798243] sd 7:0:0:0: [synoboot] Assuming drive cache: write through
2024-02-17T15:54:29+01:00 DS918plus kernel: [ 104.804383] GPT:Primary header thinks Alt. header is not at the end of the disk.
2024-02-17T15:54:29+01:00 DS918plus kernel: [ 104.804385] GPT:239649 != 245759
2024-02-17T15:54:29+01:00 DS918plus kernel: [ 104.804385] GPT:Alternate GPT header not at the end of the disk.
2024-02-17T15:54:29+01:00 DS918plus kernel: [ 104.804386] GPT:239649 != 245759
2024-02-17T15:54:29+01:00 DS918plus kernel: [ 104.804387] GPT: Use GNU Parted to correct GPT errors.
...

Wann die anderen Abstürze waren kann ich nicht mehr genau nachvollziehen. Daher würde ich einfach warten und erneut nachsehen, wenn sie wieder abstürzt.

 

[threadstone]

Teil 2 vom Log, da ich max. 30.000 Zeichen posten kann.

2024-02-17T15:54:31+01:00 DS918plus umount[6791]: can't umount /initrd: Invalid argument
2024-02-17T15:54:31+01:00 DS918plus synodrnode[6873]: Clear temp credential of DRNode
2024-02-17T15:54:32+01:00 DS918plus synostorage[7554]: synostorage_int_disk.c:448 Disk [sdc] info cache generated
2024-02-17T15:54:32+01:00 DS918plus synostorage[7566]: synostorage_int_disk.c:448 Disk [sda] info cache generated
2024-02-17T15:54:32+01:00 DS918plus synostorage[7565]: synostorage_int_disk.c:448 Disk [sdd] info cache generated
2024-02-17T15:54:32+01:00 DS918plus synostorage[7573]: synostorage_int_disk.c:448 Disk [sdb] info cache generated
2024-02-17T15:54:32+01:00 DS918plus udev[8129]: [UPS] add USB UPS(PRODUCT=463/ffff/100)
2024-02-17T15:54:32+01:00 DS918plus interface-catcher[8191]: lo (inet 127.0.0.1 netmask 255.0.0.0 ) is added
2024-02-17T15:54:33+01:00 DS918plus synoencvolume[8527]: encvol_internal_lib.c:684 Not support volume encryption
2024-02-17T15:54:33+01:00 DS918plus /usr/sbin/irqbalance[8601]: Daemon couldn't be bound to the file-based socket.
2024-02-17T15:54:33+01:00 DS918plus rc.network[8641]: Wait for all netlink & hook event done
2024-02-17T15:54:33+01:00 DS918plus synoconfd[8562]: user-refreshquota.cpp:444 No available volume
2024-02-17T15:54:34+01:00 DS918plus synopkgctl[8899]: sock_connect.cpp:51 (8899, 0) Failed to connect server [err: No such file or directory]
2024-02-17T15:54:34+01:00 DS918plus synopkgctl[8912]: sock_connect.cpp:51 (8912, 0) Failed to connect server [err: No such file or directory]
2024-02-17T15:54:34+01:00 DS918plus synopkgctl[8912]: /run/synoscgi-fastapi.sock APIRunner.cpp:1866 connection broken
2024-02-17T15:54:34+01:00 DS918plus synopkgctl[8899]: /run/synoscgi-fastapi.sock APIRunner.cpp:1866 connection broken
2024-02-17T15:54:34+01:00 DS918plus synopkgctl[8913]: sock_connect.cpp:51 (8913, 0) Failed to connect server [err: No such file or directory]
2024-02-17T15:54:34+01:00 DS918plus synopkgctl[8913]: /run/synoscgi-fastapi.sock APIRunner.cpp:1866 connection broken
2024-02-17T15:54:34+01:00 DS918plus synopkgctl[8907]: sock_connect.cpp:51 (8907, 0) Failed to connect server [err: No such file or directory]
2024-02-17T15:54:34+01:00 DS918plus synopkgctl[8907]: /run/synoscgi-fastapi.sock APIRunner.cpp:1866 connection broken
2024-02-17T15:54:34+01:00 DS918plus synopkgctl[8895]: sock_connect.cpp:51 (8895, 0) Failed to connect server [err: No such file or directory]
2024-02-17T15:54:34+01:00 DS918plus synopkgctl[8895]: /run/synoscgi-fastapi.sock APIRunner.cpp:1866 connection broken
2024-02-17T15:54:34+01:00 DS918plus synopkgctl[8895]: sock_connect.cpp:51 (8895, 0) Failed to connect server [err: No such file or directory]
2024-02-17T15:54:34+01:00 DS918plus synopkgctl[8895]: /run/synoscgi-fastapi.sock APIRunner.cpp:1866 connection broken
2024-02-17T15:54:35+01:00 DS918plus synopkgctl[8899]: sock_connect.cpp:51 (8899, 0) Failed to connect server [err: No such file or directory]
2024-02-17T15:54:35+01:00 DS918plus synopkgctl[8899]: /run/synoscgi-fastapi.sock APIRunner.cpp:1866 connection broken
2024-02-17T15:54:35+01:00 DS918plus spacetool.shared[9535]: partition_table_type_get.c:66 pTable 3
2024-02-17T15:54:35+01:00 DS918plus spacetool.shared[9536]: partition_table_type_get.c:66 pTable 3
2024-02-17T15:54:35+01:00 DS918plus spacetool.shared[9538]: partition_table_type_get.c:66 pTable 3
2024-02-17T15:54:35+01:00 DS918plus spacetool.shared[9543]: raid_obj_enum.c:371 assemble: Find raid 9a6e7f36:d1193829:2b913d73:fa29545f
2024-02-17T15:54:35+01:00 DS918plus spacetool.shared[9543]: raid_obj_enum.c:371 assemble: Find raid 9a6e7f36:d1193829:2b913d73:fa29545f
2024-02-17T15:54:36+01:00 DS918plus rc.network[9689]: Link up all bonding slaves, bond: ovs_bond0 : [ eth0 eth1]
2024-02-17T15:54:36+01:00 DS918plus spacetool.shared[9543]: lvm_obj_enum.c:330 assemble: Find lvm mqDQPD-bgKM-UAFt-NRRg-eB89-zjzA-HfYKa7
2024-02-17T15:54:36+01:00 DS918plus spacetool.shared[9543]: space_obj_enum.c:174 assemble: Find space /dev/vg1000/lv
2024-02-17T15:54:36+01:00 DS918plus spacetool.shared[9543]: lvm_obj_start.c:99 [Info] Activate all VG
2024-02-17T15:54:36+01:00 DS918plus spacetool.shared[9543]: lvm_obj_start.c:117 Activate LVM [/dev/vg1000], UUID: [mqDQPD-bgKM-UAFt-NRRg-eB89-zjzA-HfYKa7]
2024-02-17T15:54:36+01:00 DS918plus spacetool.shared[9715]: space_assemble.c:756 space: [/dev/vg1000/lv]
2024-02-17T15:54:36+01:00 DS918plus interface-catcher[9728]: ovs_bond0 (inet 192.168.178.110 netmask 255.255.255.0 ) is added
2024-02-17T15:54:36+01:00 DS918plus spacetool.shared[9715]: space_assemble.c:785 space: [/dev/vg1000/lv], ndisk: [3]
2024-02-17T15:54:37+01:00 DS918plus spacetool.shared[9792]: space_assemble.c:756 space: [/dev/vg1000/lv]
2024-02-17T15:54:37+01:00 DS918plus spacetool.shared[9792]: space_assemble.c:785 space: [/dev/vg1000/lv], ndisk: [3]
2024-02-17T15:54:37+01:00 DS918plus synosocket[9613]: synosocket.cpp:63 service not active. synoscgi-socket
2024-02-17T15:54:37+01:00 DS918plus synosocket[9613]: sock_connect.cpp:51 (9613, 0) Failed to connect server [err: No such file or directory]
2024-02-17T15:54:37+01:00 DS918plus synosocket[9613]: /run/synoscgi-fastapi.sock APIRunner.cpp:1866 connection broken
2024-02-17T15:54:37+01:00 DS918plus synopkgctl[8913]: sock_connect.cpp:51 (8913, 0) Failed to connect server [err: No such file or directory]
2024-02-17T15:54:37+01:00 DS918plus synopkgctl[8913]: /run/synoscgi-fastapi.sock APIRunner.cpp:1866 connection broken
2024-02-17T15:54:37+01:00 DS918plus synovspace[9897]: virtual_space_implement.c:1071 Can not find flash cache conf, use dummy mode instead
2024-02-17T15:54:37+01:00 DS918plus synovspace[9897]: flashcache_create.c:86 Create Cache: /usr/bin/flashcache_create -n 12 -s 19523194880 -p dummy cachedev_0 none /dev/vg1000/lv
2024-02-17T15:54:37+01:00 DS918plus kernel: [ 112.986974] flashcache_syno: /dev/vg1000/lv exclude check success
2024-02-17T15:54:37+01:00 DS918plus synocheckhotspare[9965]: synocheckhotspare.c:223 [INFO] No hotspare config, skip hotspare config check. [0x0000 (null):0]
2024-02-17T15:54:37+01:00 DS918plus synopkgctl[9959]: sock_connect.cpp:51 (9959, 0) Failed to connect server [err: No such file or directory]
2024-02-17T15:54:37+01:00 DS918plus synopkgctl[9959]: /run/synoscgi-fastapi.sock APIRunner.cpp:1866 connection broken
2024-02-17T15:54:37+01:00 DS918plus synopkgctl[8907]: sock_connect.cpp:51 (8907, 0) Failed to connect server [err: No such file or directory]
2024-02-17T15:54:37+01:00 DS918plus synopkgctl[8907]: /run/synoscgi-fastapi.sock APIRunner.cpp:1866 connection broken
2024-02-17T15:54:37+01:00 DS918plus synowebapi[10033]: sock_connect.cpp:51 (10033, 0) Failed to connect server [err: No such file or directory]
2024-02-17T15:54:37+01:00 DS918plus synowebapi[10033]: /run/synoscgi-fastapi.sock APIRunner.cpp:1866 connection broken
2024-02-17T15:54:37+01:00 DS918plus synowebapi[10033]: sock_connect.cpp:51 (10033, 0) Failed to connect server [err: No such file or directory]
2024-02-17T15:54:37+01:00 DS918plus synowebapi[10033]: /run/synoscgi-fastapi.sock APIRunner.cpp:1866 connection broken
2024-02-17T15:54:37+01:00 DS918plus synopkgctl[8912]: sock_connect.cpp:51 (8912, 0) Failed to connect server [err: No such file or directory]
2024-02-17T15:54:37+01:00 DS918plus synopkgctl[8912]: /run/synoscgi-fastapi.sock APIRunner.cpp:1866 connection broken
2024-02-17T15:54:38+01:00 DS918plus synopkgctl[10138]: sock_connect.cpp:51 (10138, 0) Failed to connect server [err: No such file or directory]
2024-02-17T15:54:38+01:00 DS918plus synopkgctl[10138]: /run/synoscgi-fastapi.sock APIRunner.cpp:1866 connection broken
2024-02-17T15:54:38+01:00 DS918plus s00_synocheckfstab[10226]: s00_synocheckfstab.c:116 [Info] Success to generate fstab
2024-02-17T15:54:38+01:00 DS918plus synopkgctl[9959]: sock_connect.cpp:51 (9959, 0) Failed to connect server [err: No such file or directory]
2024-02-17T15:54:38+01:00 DS918plus synopkgctl[9959]: /run/synoscgi-fastapi.sock APIRunner.cpp:1866 connection broken
2024-02-17T15:54:38+01:00 DS918plus supportservicetool[10425]: session_cookie.cpp:58 Successfully loaded session cookie.
2024-02-17T15:54:39+01:00 DS918plus synopkgctl[10138]: sock_connect.cpp:51 (10138, 0) Failed to connect server [err: No such file or directory]
2024-02-17T15:54:39+01:00 DS918plus synopkgctl[10138]: /run/synoscgi-fastapi.sock APIRunner.cpp:1866 connection broken
2024-02-17T15:54:44+01:00 DS918plus spacetool[10345]: space_fs_info_on_pool_meta.c:293 Failed to set fs info on pool meta for [/volume1]
2024-02-17T15:54:44+01:00 DS918plus spacetool[10345]: volume_mount.c:274 Failed to store fs info into pool meta for [/volume1]
2024-02-17T15:54:44+01:00 DS918plus configupdate.volume[11054]: configupdate_volume.cpp:160 Original info before upgrade: volume: /volume1, version: 69057
2024-02-17T15:54:45+01:00 DS918plus s2s_volume_hook[11271]: s2s_volume_hook.cpp:126 skip volume hook. (System is booting up)
2024-02-17T15:54:45+01:00 DS918plus synocheckshare[11287]: synocheckshare_vol_mount.c:175 Export Share [INTERNAL] [/dev/mapper/cachedev_0] [/volume1]
2024-02-17T15:54:46+01:00 DS918plus syno-coredump-store.sh[11347]: Set coredump path to [/volume1]
2024-02-17T15:54:46+01:00 DS918plus usbhid-ups[11357]: Startup successful
2024-02-17T15:54:46+01:00 DS918plus upsmsg[11358]: The UPS is connected. driver=[usbhid-ups]
2024-02-17T15:54:46+01:00 DS918plus upsd[11498]: /run/ups_state is world readable
2024-02-17T15:54:46+01:00 DS918plus upsd[11550]: Startup successful
2024-02-17T15:54:46+01:00 DS918plus upsd[11550]: upsd.c:743 IP [127.0.0.1] add to ACL list
2024-02-17T15:54:46+01:00 DS918plus upsd[11550]: upsd.c:747 IP [::1] add to ACL list
2024-02-17T15:54:48+01:00 DS918plus upsmon[11580]: Startup successful
2024-02-17T15:54:48+01:00 DS918plus upsmsg[11583]: /usr/syno/lib/systemd/scripts/ups-usb.sh start invoked.
2024-02-17T15:54:48+01:00 DS918plus upsmon[11581]: UPS [ups@localhost] connected
2024-02-17T15:54:51+01:00 DS918plus ssrecsharectl_SYNO.SurveillanceStation.Recording.Reindex_1_Start[11341]: APIRunner.cpp:1405 set eid to root failed [Operation not permitted]
2024-02-17T15:54:51+01:00 DS918plus ssrecsharectl_SYNO.SurveillanceStation.Recording.Reindex_1_Start[11341]: APIRunner.cpp:1408 (11341) setgroups(groupCount, groups) Failed [err: Operation not permitted]
2024-02-17T15:54:51+01:00 DS918plus synocacheadvisord[11769]: synocacheadvisord.c:891 Cache Advisor Start
2024-02-17T15:54:51+01:00 DS918plus synocacheadvisord[11860]: synocacheadvisord.c:937 No Need to start advisor
2024-02-17T15:54:52+01:00 DS918plus chronyd[11513]: System clock wrong by 1.115769 seconds
2024-02-17T15:54:52+01:00 DS918plus chronyd[11513]: System clock was stepped by 1.115769 seconds
2024-02-17T15:54:53+01:00 DS918plus synocachepinfiled[11782]: synocachepinfiled.cpp:1753 Start Service (Build time: 2023/09/23-22:22)
2024-02-17T15:54:53+01:00 DS918plus synocacheadvisord[11860]: synocacheadvisord.c:1022 Cache Advisor Stop
2024-02-17T15:54:53+01:00 DS918plus synocrtregister[12075]: synocrtregister.cpp:283 Register certificate for AppPortal/SurveillanceStation_AltPort
2024-02-17T15:54:54+01:00 DS918plus synocrtregister[12141]: synocrtregister.cpp:283 Register certificate for system/default
2024-02-17T15:54:56+01:00 DS918plus share-hook[12520]: (12520: 3360) [ERROR] share-hook.cpp(322): failed to connect to cloud monitor
2024-02-17T15:54:56+01:00 DS918plus share-hook[12520]: (12520: 3360) [ERROR] share-hook.cpp(323): notification is not sent ({"notify": "share_hook", "result": 0, "share_name": "homes", "type": "set_privilege_change"})
2024-02-17T15:54:56+01:00 DS918plus update_share_folder_alias[12540]: update_share_folder_alias.cpp:22 Fail to SLIBCFileLockTimeByFile().[0x0900 file_lock_time_by_file.c:22]
2024-02-17T15:54:56+01:00 DS918plus update_share_folder_alias[12540]: update_share_folder_alias.cpp:121 Fail to AcquireFileLock
2024-02-17T15:54:58+01:00 DS918plus synoactiveinsight[12862]: [Upgrade SynoOnlinePack_v2][Stage prepare_upgrade] Run ActiveInsight package action pre-hook.
2024-02-17T15:54:58+01:00 DS918plus share-hook[13060]: (13060:95968) [ERROR] share-hook.cpp(322): failed to connect to cloud monitor
2024-02-17T15:54:58+01:00 DS918plus update_share_folder_alias[13059]: update_share_folder_alias.cpp:22 Fail to SLIBCFileLockTimeByFile().[0x0900 file_lock_time_by_file.c:22]
2024-02-17T15:54:58+01:00 DS918plus update_share_folder_alias[13059]: update_share_folder_alias.cpp:121 Fail to AcquireFileLock
2024-02-17T15:54:58+01:00 DS918plus share-hook[13060]: (13060:95968) [ERROR] share-hook.cpp(323): notification is not sent ({"notify": "share_hook", "result": 0, "share_name": "photo", "type": "set_privilege_change"})
2024-02-17T15:54:59+01:00 DS918plus synocheckshare[11775]: synocheckshare_sync_conf.c:632 Remove Share config: WD_Elements_8TB / /volumeUSB2/usbshare
2024-02-17T15:54:59+01:00 DS918plus synocheckshare[11775]: synocheckshare_sync_conf.c:632 Remove Share config: WD_MyBook_16TB / /volumeUSB1/usbshare
2024-02-17T15:55:00+01:00 DS918plus share-hook[13321]: (13321:65856) [INFO] share-hook.cpp(410): shared folder 'WD_Elements_8TB' is about to be deleted
2024-02-17T15:55:00+01:00 DS918plus share-hook[13321]: (13321:65856) [ERROR] share-hook.cpp(322): failed to connect to cloud monitor
2024-02-17T15:55:00+01:00 DS918plus share-hook[13321]: (13321:65856) [ERROR] share-hook.cpp(323): notification is not sent ({"notify": "share_hook", "result": 0, "share_name": "WD_Elements_8TB", "type": "delete"})
2024-02-17T15:55:00+01:00 DS918plus share-hook[13321]: (13321:65856) [INFO] share-hook.cpp(410): shared folder 'WD_MyBook_16TB' is about to be deleted
2024-02-17T15:55:00+01:00 DS918plus share-hook[13321]: (13321:65856) [ERROR] share-hook.cpp(322): failed to connect to cloud monitor
2024-02-17T15:55:00+01:00 DS918plus share-hook[13321]: (13321:65856) [ERROR] share-hook.cpp(323): notification is not sent ({"notify": "share_hook", "result": 0, "share_name": "WD_MyBook_16TB", "type": "delete"})
2024-02-17T15:55:02+01:00 DS918plus synocheckshare[11775]: volume_is_writable.c:19 Fail to parse volume path from [/volumeUSB2/@eaDir/usbshare]
2024-02-17T15:55:02+01:00 DS918plus synocheckshare[11775]: volume_is_writable.c:19 Fail to parse volume path from [/volumeUSB1/@eaDir/usbshare]
2024-02-17T15:55:02+01:00 DS918plus synoiscsiep[13432]: iscsi_start_all.cpp:90:SYNOiSCSIStartAllWithoutLock Successfully started iSCSI service.
2024-02-17T15:55:02+01:00 DS918plus kernel: [ 137.033905] workqueue: max_active 1024 requested for vhost_scsi is out of range, clamping between 1 and 512
2024-02-17T15:55:03+01:00 DS918plus update_share_folder_alias[13562]: update_share_folder_alias.cpp:22 Fail to SLIBCFileLockTimeByFile().[0x0900 file_lock_time_by_file.c:22]
2024-02-17T15:55:03+01:00 DS918plus update_share_folder_alias[13562]: update_share_folder_alias.cpp:121 Fail to AcquireFileLock
2024-02-17T15:55:04+01:00 DS918plus synoactiveinsight[13777]: [Upgrade SynoOnlinePack_v2][Stage installed_and_stopped] Run ActiveInsight package action post-hook.
2024-02-17T15:55:04+01:00 DS918plus synousbdisk[13922]: RCClean succeeded
2024-02-17T15:55:05+01:00 DS918plus hotplugd[13952]: hotplugd.c:1260 ##### ACTION:add
2024-02-17T15:55:05+01:00 DS918plus hotplugd[13952]: DEVNAME:sdc
2024-02-17T15:55:05+01:00 DS918plus hotplugd[13952]: DEVGUID:2YJJUUBD 0
2024-02-17T15:55:05+01:00 DS918plus hotplugd[13952]: DEVPATH:sdc
2024-02-17T15:55:05+01:00 DS918plus hotplugd[13952]: SUBSYSTEM:block
2024-02-17T15:55:05+01:00 DS918plus hotplugd[13952]: PHYSDEVPATH:/devices/pci0000:00/0000:00:12.0/ata1/host0/target0:0:0/0:0:0:0
2024-02-17T15:55:05+01:00 DS918plus hotplugd[13952]: hotplugd.c:1421 ==== SATA disk [sdc] hotswap [add] ====
2024-02-17T15:55:06+01:00 DS918plus hotplugd[13952]: disk/disk_config_single.c:122 apply /usr/syno/bin/DiskApmSet.sh 255 /dev/sdc 1>/dev/null 2>&1
2024-02-17T15:55:06+01:00 DS918plus hotplugd[13952]: disk/disk_config_single.c:122 apply /usr/syno/bin/syno_disk_ctl --ncq-on /dev/sdc 1>/dev/null 2>&1
2024-02-17T15:55:06+01:00 DS918plus hotplugd[13952]: disk/disk_config_single.c:352 /dev/sdc apply wd idle off
2024-02-17T15:55:06+01:00 DS918plus hotplugd[13952]: hotplugd.c:1461 ==== SATA disk [sdc] Model: [WD100EFAX-68LHPN0] ====
2024-02-17T15:55:06+01:00 DS918plus hotplugd[13952]: hotplugd.c:1462 ==== SATA disk [sdc] Serial number: [2YJJUUBD] ====
2024-02-17T15:55:06+01:00 DS918plus hotplugd[13952]: hotplugd.c:1463 ==== SATA disk [sdc] Firmware version: [83.H0A83] ====
2024-02-17T15:55:06+01:00 DS918plus hotplugd[13952]: hotplugd.c:1260 ##### ACTION:add
2024-02-17T15:55:06+01:00 DS918plus hotplugd[13952]: DEVNAME:sdd
2024-02-17T15:55:06+01:00 DS918plus hotplugd[13952]: DEVGUID:JEGWNZJN 0
2024-02-17T15:55:06+01:00 DS918plus hotplugd[13952]: DEVPATH:sdd
2024-02-17T15:55:06+01:00 DS918plus hotplugd[13952]: SUBSYSTEM:block
2024-02-17T15:55:06+01:00 DS918plus hotplugd[13952]: PHYSDEVPATH:/devices/pci0000:00/0000:00:12.0/ata2/host1/target1:0:0/1:0:0:0
2024-02-17T15:55:06+01:00 DS918plus hotplugd[13952]: hotplugd.c:1421 ==== SATA disk [sdd] hotswap [add] ====
2024-02-17T15:55:06+01:00 DS918plus hotplugd[13952]: disk/disk_config_single.c:122 apply /usr/syno/bin/DiskApmSet.sh 255 /dev/sdd 1>/dev/null 2>&1
2024-02-17T15:55:06+01:00 DS918plus hotplugd[13952]: disk/disk_config_single.c:122 apply /usr/syno/bin/syno_disk_ctl --ncq-on /dev/sdd 1>/dev/null 2>&1
2024-02-17T15:55:06+01:00 DS918plus hotplugd[13952]: disk/disk_config_single.c:352 /dev/sdd apply wd idle off
2024-02-17T15:55:06+01:00 DS918plus hotplugd[13952]: hotplugd.c:1461 ==== SATA disk [sdd] Model: [WD100EFAX-68LHPN0] ====
2024-02-17T15:55:06+01:00 DS918plus hotplugd[13952]: hotplugd.c:1462 ==== SATA disk [sdd] Serial number: [JEGWNZJN] ====
2024-02-17T15:55:06+01:00 DS918plus hotplugd[13952]: hotplugd.c:1463 ==== SATA disk [sdd] Firmware version: [83.H0A83] ====
2024-02-17T15:55:06+01:00 DS918plus hotplugd[13952]: hotplugd.c:1260 ##### ACTION:add
2024-02-17T15:55:06+01:00 DS918plus hotplugd[13952]: DEVNAME:sda
2024-02-17T15:55:06+01:00 DS918plus hotplugd[13952]: DEVGUID:2YJH317D 0
2024-02-17T15:55:06+01:00 DS918plus hotplugd[13952]: DEVPATH:sda
2024-02-17T15:55:06+01:00 DS918plus hotplugd[13952]: SUBSYSTEM:block
2024-02-17T15:55:06+01:00 DS918plus hotplugd[13952]: PHYSDEVPATH:/devices/pci0000:00/0000:00:13.0/0000:01:00.0/ata3/host2/target2:0:0/2:0:0:0
2024-02-17T15:55:06+01:00 DS918plus hotplugd[13952]: hotplugd.c:1421 ==== SATA disk [sda] hotswap [add] ====
Internal disk info:
01: /dev/sda (2YJH317D)
02: /dev/sdb (JEGJM8AN)
03: /dev/sdc (2YJJUUBD)
04: /dev/sdd (JEGWNZJN)
2024-02-17T15:55:07+01:00 DS918plus hotplugd[13952]: disk/disk_config_single.c:122 apply /usr/syno/bin/DiskApmSet.sh 255 /dev/sda 1>/dev/null 2>&1
2024-02-17T15:55:07+01:00 DS918plus hotplugd[13952]: disk/disk_config_single.c:122 apply /usr/syno/bin/syno_disk_ctl --ncq-on /dev/sda 1>/dev/null 2>&1
2024-02-17T15:55:07+01:00 DS918plus hotplugd[13952]: disk/disk_config_single.c:352 /dev/sda apply wd idle off
2024-02-17T15:55:07+01:00 DS918plus hotplugd[13952]: hotplugd.c:1461 ==== SATA disk [sda] Model: [WD100EFAX-68LHPN0] ====
2024-02-17T15:55:07+01:00 DS918plus hotplugd[13952]: hotplugd.c:1462 ==== SATA disk [sda] Serial number: [2YJH317D] ====
2024-02-17T15:55:07+01:00 DS918plus hotplugd[13952]: hotplugd.c:1463 ==== SATA disk [sda] Firmware version: [83.H0A83] ====
2024-02-17T15:55:07+01:00 DS918plus hotplugd[13952]: hotplugd.c:1260 ##### ACTION:add
2024-02-17T15:55:07+01:00 DS918plus hotplugd[13952]: DEVNAME:sdb
2024-02-17T15:55:07+01:00 DS918plus hotplugd[13952]: DEVGUID:JEGJM8AN 0
2024-02-17T15:55:07+01:00 DS918plus hotplugd[13952]: DEVPATH:sdb
2024-02-17T15:55:07+01:00 DS918plus hotplugd[13952]: SUBSYSTEM:block
2024-02-17T15:55:07+01:00 DS918plus hotplugd[13952]: PHYSDEVPATH:/devices/pci0000:00/0000:00:13.0/0000:01:00.0/ata4/host3/target3:0:0/3:0:0:0
2024-02-17T15:55:07+01:00 DS918plus hotplugd[13952]: hotplugd.c:1421 ==== SATA disk [sdb] hotswap [add] ====
2024-02-17T15:55:07+01:00 DS918plus hotplugd[13952]: hotplugd.c:199 ==== Finish all boot-up disks ====
2024-02-17T15:55:07+01:00 DS918plus hotplugd[13952]: disk/disk_config_single.c:122 apply /usr/syno/bin/DiskApmSet.sh 255 /dev/sdb 1>/dev/null 2>&1
2024-02-17T15:55:07+01:00 DS918plus synonotify[14123]: mail_get.cpp:136 mail_get.cpp (136) Failed to get access token.
2024-02-17T15:55:08+01:00 DS918plus hotplugd[13952]: disk/disk_config_single.c:122 apply /usr/syno/bin/syno_disk_ctl --ncq-on /dev/sdb 1>/dev/null 2>&1
2024-02-17T15:55:08+01:00 DS918plus synostgd-cache[11897]: scemd_connector/scemd_connector.c:147 Fail to sendto() for scemd connector client.
2024-02-17T15:55:08+01:00 DS918plus synocheckhotspare[15057]: synocheckhotspare.c:223 [INFO] No hotspare config, skip hotspare config check. [0x0000 (null):0]
2024-02-17T15:55:08+01:00 DS918plus hotplugd[13952]: disk/disk_config_single.c:352 /dev/sdb apply wd idle off
2024-02-17T15:55:08+01:00 DS918plus hotplugd[13952]: hotplugd.c:1461 ==== SATA disk [sdb] Model: [WD100EFAX-68LHPN0] ====
2024-02-17T15:55:08+01:00 DS918plus hotplugd[13952]: hotplugd.c:1462 ==== SATA disk [sdb] Serial number: [JEGJM8AN] ====
2024-02-17T15:55:08+01:00 DS918plus hotplugd[13952]: hotplugd.c:1463 ==== SATA disk [sdb] Firmware version: [83.H0A83] ====
2024-02-17T15:55:08+01:00 DS918plus hotplugd[13952]: hotplugd.c:1260 ##### ACTION:add
2024-02-17T15:55:08+01:00 DS918plus hotplugd[13952]: DEVNAME:sdq
2024-02-17T15:55:08+01:00 DS918plus hotplugd[13952]: DEVICE:/proc/bus/usb/002/003
2024-02-17T15:55:08+01:00 DS918plus hotplugd[13952]: DEVGUID:384C47384C4230450
2024-02-17T15:55:08+01:00 DS918plus hotplugd[13952]: DEVPATH:sdq
2024-02-17T15:55:08+01:00 DS918plus hotplugd[13952]: SUBSYSTEM:block
2024-02-17T15:55:08+01:00 DS918plus hotplugd[13952]: PHYSDEVPATH:/devices/pci0000:00/0000:00:15.0/usb2/2-2/2-2.1/2-2.1:1.0/host5/target5:0:0/5:0:0:0
2024-02-17T15:55:08+01:00 DS918plus hotplugd[13952]: hotplugd.c:795 SLIBCFileGetSection(1058:25ed:384C47384C423045) from /run/usbdev.conf failed
2024-02-17T15:55:08+01:00 DS918plus hotplugd[13952]: hotplugd.c:1484 ==== USB disk [sdq] plugged in ====
2024-02-17T15:55:08+01:00 DS918plus hotplugd[13952]: hotplugd.c:1485 goto USB disk, szDeviceName=sdq
2024-02-17T15:55:08+01:00 DS918plus hotplugd[13952]: external_storage_parts_vol_info_get.c:107 Dev:sdq cannot find PostfixNumber.
2024-02-17T15:55:10+01:00 DS918plus synocrtregister[16296]: synocrtregister.cpp:283 Register certificate for AppPortal/SurveillanceStation_AltPort
2024-02-17T15:55:15+01:00 DS918plus kernel: [ 149.488021] exFAT-fs (sdq1): deprecated mount option "utf8"
2024-02-17T15:55:15+01:00 DS918plus kernel: [ 149.498059] exFAT-fs (sdq1): Volume was not properly unmounted. Some data may be corrupt. Please run fsck.
2024-02-17T15:55:16+01:00 DS918plus synocheckshare[17531]: synocheckshare_vol_mount.c:175 Export Share [USB] [/dev/sdq1] [/volumeUSB1/usbshare]
2024-02-17T15:55:16+01:00 DS918plus kernel: [ 150.131773] exFAT-fs (sdq1): exfat mounted successfully
2024-02-17T15:55:16+01:00 DS918plus root[17675]: == DSM 7.2.1 69057-4 finished boot up ==
2024-02-17T15:55:18+01:00 DS918plus fileindeX[18268]: fileindex.cpp:763 (UpdateLogLocation) fileindex update log location
2024-02-17T15:55:18+01:00 DS918plus fileindeX[18268]: fileindex.cpp:767 (UpdateLogLocation) ignored volume: []
2024-02-17T15:55:18+01:00 DS918plus fileindeX[18268]: fileindex.cpp:440 (PickDir) enum [volume1]
2024-02-17T15:55:18+01:00 DS918plus fileindeX[18268]: fileindex.cpp:770 (UpdateLogLocation) picked new log dir [/volume1/@SynoFinder-log]
2024-02-17T15:55:18+01:00 DS918plus fileindeX[18268]: fileindex.cpp:725 (MoveOldLogLocationLink) Old log dir link does not exist [/var/log/SynoFinder]
2024-02-17T15:55:18+01:00 DS918plus fileindeX[18268]: fileindex.cpp:525 (relocateTo) link exists [/var/packages/SynoFinder/var/log] -> [/volume1/@SynoFinder-log]
2024-02-17T15:55:20+01:00 DS918plus updater[18742]: utils.cpp:518 (RunAvailableUpdaters) Run SUS available updates
2024-02-17T15:55:20+01:00 DS918plus updater[18742]: utils.cpp:537 (RunAvailableUpdaters) Run SUS mandatory updates
2024-02-17T15:55:21+01:00 DS918plus fileindeX[19011]: fileindex.cpp:786 (UpdateEtcLocation) fileindex update etc location
2024-02-17T15:55:21+01:00 DS918plus fileindeX[19011]: fileindex.cpp:790 (UpdateEtcLocation) ignored volume: []
2024-02-17T15:55:21+01:00 DS918plus fileindeX[19011]: fileindex.cpp:440 (PickDir) enum [volume1]
2024-02-17T15:55:21+01:00 DS918plus fileindeX[19011]: fileindex.cpp:793 (UpdateEtcLocation) picked new etc dir [/volume1/@SynoFinder-etc-volume]
2024-02-17T15:55:21+01:00 DS918plus fileindeX[19011]: fileindex.cpp:525 (relocateTo) link exists [/var/packages/SynoFinder/etc/etc-volume] -> [/volume1/@SynoFinder-etc-volume]
2024-02-17T15:55:21+01:00 DS918plus synofinderdb[19065]: synofinderdb.cpp:101 (main) synofinderdb tool desc: update synofinder.db
2024-02-17T15:55:21+01:00 DS918plus synocheckshare[17531]: volume_is_writable.c:19 Fail to parse volume path from [/volumeUSB1/@eaDir/usbshare]
2024-02-17T15:55:22+01:00 DS918plus hotplugd[13952]: hotplugd.c:1260 ##### ACTION:add
2024-02-17T15:55:22+01:00 DS918plus hotplugd[13952]: DEVNAME:sdr
2024-02-17T15:55:22+01:00 DS918plus hotplugd[13952]: DEVICE:/proc/bus/usb/002/004
2024-02-17T15:55:22+01:00 DS918plus hotplugd[13952]: DEVGUID:32534732573556570
2024-02-17T15:55:22+01:00 DS918plus hotplugd[13952]: DEVPATH:sdr
2024-02-17T15:55:22+01:00 DS918plus hotplugd[13952]: SUBSYSTEM:block
2024-02-17T15:55:22+01:00 DS918plus hotplugd[13952]: PHYSDEVPATH:/devices/pci0000:00/0000:00:15.0/usb2/2-2/2-2.3/2-2.3:1.0/host6/target6:0:0/6:0:0:0
2024-02-17T15:55:22+01:00 DS918plus hotplugd[13952]: hotplugd.c:1484 ==== USB disk [sdr] plugged in ====
2024-02-17T15:55:22+01:00 DS918plus hotplugd[13952]: hotplugd.c:1485 goto USB disk, szDeviceName=sdr
2024-02-17T15:55:22+01:00 DS918plus hotplugd[13952]: external_storage_parts_vol_info_get.c:107 Dev:sdr cannot find PostfixNumber.
2024-02-17T15:55:27+01:00 DS918plus synocheckshare[20213]: synocheckshare_vol_mount.c:175 Export Share [USB] [/dev/sdr1] [/volumeUSB2/usbshare]
2024-02-17T15:55:35+01:00 DS918plus synocheckshare[20213]: volume_is_writable.c:19 Fail to parse volume path from [/volumeUSB2/@eaDir/usbshare]
2024-02-17T15:55:43+01:00 DS918plus dhcp-client6[22567]: started on ovs_bond0 with action=info
2024-02-17T15:55:46+01:00 DS918plus dns_change_hook_event[22669]: [PRE] (2) DNS1=192.168.178.1 DNS2=fd00::464e:6dff:fe42:fecf
2024-02-17T15:55:46+01:00 DS918plus dns_change_hook_event[22690]: [POST] (2) DNS1=192.168.178.1 DNS2=fd00::464e:6dff:fe42:fecf
2024-02-17T15:55:48+01:00 DS918plus dhcp-client6[22764]: stopped on ovs_bond0 with action=info
2024-02-17T15:55:50+01:00 DS918plus synouser[23079]: synouser.c:1114 ret 0
2024-02-17T15:56:01+01:00 DS918plus synopkgctl[23844]: util.cpp:80 Install extension, name=synology_drive_file_parser, config_path=/var/packages/SynologyDrive/target/lib/extension/file_parser.conf, parser_path=/var/packages/SynologyDrive/target/lib/extension/file_parser.so
2024-02-17T15:56:02+01:00 DS918plus synopkgctl[23844]: util.cpp:127 Install extension done
2024-02-17T15:56:02+01:00 DS918plus root[25328]: CS: [start-stop-status]: Synology Drive start...
2024-02-17T15:56:08+01:00 DS918plus redis-server[25942]: oO0OoO0OoO0Oo Redis is starting oO0OoO0OoO0Oo
2024-02-17T15:56:08+01:00 DS918plus redis-server[25942]: Redis version=6.2.13, bits=64, commit=937e4c06, modified=0, pid=25942, just started
2024-02-17T15:56:08+01:00 DS918plus redis-server[25942]: Configuration loaded
2024-02-17T15:56:08+01:00 DS918plus synodrive-redis[25942]: WARNING Memory overcommit must be enabled! Without it, a background save or replication may fail under low memory condition. Being disabled, it can can also cause failures without low memory condition, see https://github.com/jemalloc/jemalloc/issues/1328. To fix this issue add 'vm.overcommit_memory = 1' to /etc/sysctl.conf and then reboot or run the command 'sysctl vm.overcommit_memory=1' for this to take effect.
2024-02-17T15:56:11+01:00 DS918plus redis-server[26444]: oO0OoO0OoO0Oo Redis is starting oO0OoO0OoO0Oo
2024-02-17T15:56:11+01:00 DS918plus redis-server[26444]: Redis version=6.2.7, bits=64, commit=0ffc3f13, modified=0, pid=26444, just started
2024-02-17T15:56:11+01:00 DS918plus redis-server[26444]: Configuration loaded
2024-02-17T15:56:12+01:00 DS918plus if_link_down_hook_event[26612]: virbr0
2024-02-17T15:56:16+01:00 DS918plus srvctl[27412]: (27412: 5280) [INFO] client-updater.cpp(303): ====== ClientUpdater Starting. ======
2024-02-17T15:56:16+01:00 DS918plus srvctl[27412]: (27412: 5280) [INFO] client-updater.cpp(322): ClientUpdater: release version from DB: 38
2024-02-17T15:56:16+01:00 DS918plus srvctl[27412]: (27412: 5280) [INFO] client-updater.cpp(528): ====== ClientUpdater Success. ======
2024-02-17T15:56:23+01:00 DS918plus ipv6_add_hook_event[28697]: ovs_bond0 added { 2003:e4:ef43:4100:211:32ff:fe94:dd5d/64 } from { fe80::211:32ff:fe94:dd5d/64 }
2024-02-17T15:56:28+01:00 DS918plus synodr[29220]: report/plan_reporter.cpp:647(UpdateGlobalReport)[WARN][29220]: Update global report [queue_report]: success
2024-02-17T15:56:28+01:00 DS918plus synodr[29220]: report/plan_reporter.cpp:647(UpdateGlobalReport)[WARN][29220]: Update global report [setting_report]: success
2024-02-17T15:56:28+01:00 DS918plus umount[29348]: can't umount /tmp/ccc/guestmeta/46dbad9e-cff8-4906-a90f-6c8010a6f0fd: Invalid argument
2024-02-17T15:56:32+01:00 DS918plus kernel: [ 226.509215] got iSCSI disk[0]
2024-02-17T15:56:33+01:00 DS918plus kernel: [ 227.313818] got iSCSI disk[1]

 

[StanleyS]

Bei mir hat der Speichertest keine Fehler gefunden. Jetzt eben wieder festgestellt, dass die Synology nicht nutzbar ist.
Die Synology an sich läuft. Festplatten drehen und man hört hin und wieder auch Schreibvorgänge.
Login nicht möglich, die Loginseite als solche lädt, kann jedoch den eigentlichen Inhalt nicht nachladen, da die Anfrage mit dem 502er HTTP-Fehler beantwortet wird.
Über SSH nicht erreichbar.
SynologyAssistant findet die auch nicht mehr.
Alles was ich jetzt machen kann ist hart aus und wieder einschalten.

 

[threadstone]

Bei mir scheint das Problem aktuell behoben. Ich hatte nun zwei Samstage in Folge keinen Ausfall (wenn sie ausgefallen ist, war das Samstag im Laufe des Tages).
Anscheinend lag es wirklich an dem Antivirenprogramm, dass Samstags automatisch gelaufen ist.

@StanleyS hast du vielleicht auch eine automatische Prüfung mit dem Antivirus Essential eingestellt?

 

[StanleyS]

Nein, ich habe keine Antivirus Prüfung eingestellt.

 

[Benie]

Was Du machen könntest, die HDDs, bei ausgeschaltetem NAS, ziehen und mal über einen Adapter an den PC anschließen und die SMART Werte auslesen.
zb. mit CristalDiskInfo
Bitte so die Einstellungen setzen, hiermit sind die Wete leichter zu bestimmen.

 

[ctrlaltdelete]

Oder hiermit auslesen der SMART Werte:
https://www.synology-forum.de/threads/smart-werte-auslesen-und-interpretieren.131057/