Zitat von "Daniel_23"Wo ist der Haken?
Laut deinem Miniauszug aus dem Log sind es Samba-Zugriffe.
Zitat von "Daniel_23"Code<7>[ 3435.679817] smbd(30148): dirtied inode 22544391 (connections.tdb) on md0 <7>[ 3435.679867] smbd(30148): dirtied inode 22544391 (connections.tdb) on md0
Ok, danke erstmal. Wie kann ich das Problem einkreisen?
Das Verbindungslog auf dem NAS aktivieren.
Werde ich mal versuchen wenn ich das finde. Weißt du was die Einträge bedeuten?
<4>[90591.739700] md0_raid1(2009): WRITE block 3906011808 on sda (8 sectors)
<4>[90591.752835] md0_raid1(2009): WRITE block 3906011848 on sda (8 sectors)
<4>[90591.826585] md0_raid1(2009): WRITE block 723541128 on sda (8 sectors)
<4>[90592.052570] md0_raid1(2009): WRITE block 3906011792 on sda (8 sectors)
<4>[90578.482860] md9_raid1(579): WRITE block 1060152 on sdb (8 sectors)
<4>[90578.533717] md9_raid1(579): WRITE block 262504 on sdb (8 sectors)
<4>[90578.752826] md9_raid1(579): WRITE block 1060144 on sdb (8 sectors)
<4>[90578.802857] md9_raid1(579): WRITE block 1060136 on sdb (8 sectors)
<4>[90579.852755] md9_raid1(579): WRITE block 1060144 on sdb (8 sectors)
<4>[90580.922759] md9_raid1(579): WRITE block 1060152 on sdb (8 sectors)
<4>[90581.254623] md0_raid1(2009): WRITE block 3906011792 on sdb (8 sectors)
<4>[90586.199796] md0_raid1(2009): WRITE block 3906011792 on sdb (8 sectors)
<4>[90586.253120] md0_raid1(2009): WRITE block 3906011784 on sdb (8 sectors)
<4>[90586.283168] md0_raid1(2009): WRITE block 3906011792 on sdb (8 sectors)
<4>[90586.296366] md0_raid1(2009): WRITE block 3906011848 on sdb (8 sectors)
<4>[90586.309516] md0_raid1(2009): WRITE block 3906011808 on sdb (8 sectors)
<4>[90586.356740] md0_raid1(2009): WRITE block 3906011792 on sdb (8 sectors)
<4>[90586.369893] md0_raid1(2009): WRITE block 3906011808 on sdb (8 sectors)
<4>[90586.383031] md0_raid1(2009): WRITE block 3906011848 on sdb (8 sectors)
<4>[90586.452981] md0_raid1(2009): WRITE block 723803136 on sdb (8 sectors)
<4>[90586.465769] md0_raid1(2009): WRITE block 2194832 on sdb (8 sectors)
<4>[90586.478655] md0_raid1(2009): WRITE block 1952848672 on sdb (8 sectors)
<4>[90586.491795] md0_raid1(2009): WRITE block 1952848680 on sdb (8 sectors)
<4>[90586.515115] md0_raid1(2009): WRITE block 1952848688 on sdb (8 sectors)
<4>[90586.853125] md0_raid1(2009): WRITE block 3906011792 on sdb (8 sectors)
<4>[90586.923122] md0_raid1(2009): WRITE block 3906011784 on sdb (8 sectors)
<4>[90591.344626] md0_raid1(2009): WRITE block 3906011792 on sdb (8 sectors)
<4>[90591.649726] md0_raid1(2009): WRITE block 3906011792 on sdb (8 sectors)
<4>[90591.683171] md0_raid1(2009): WRITE block 3906011784 on sdb (8 sectors)
<4>[90591.733122] md0_raid1(2009): WRITE block 3906011792 on sdb (8 sectors)
<4>[90591.746259] md0_raid1(2009): WRITE block 3906011808 on sdb (8 sectors)
<4>[90591.759408] md0_raid1(2009): WRITE block 3906011848 on sdb (8 sectors)
<4>[90591.833063] md0_raid1(2009): WRITE block 723541128 on sdb (8 sectors)
<4>[90592.059220] md0_raid1(2009): WRITE block 3906011792 on sdb (8 sectors)Das steht eigentlich am meisten im Log.
ich hate vorher eine DNS-323 dran, die hat diese Zicken nicht gemacht.
Zitat von "Daniel_23"Weißt du was die Einträge bedeuten?
Ja, es werden Daten auf die Platten geschrieben.
ja das sehe ich. Kann man da erkennen warum? Bzw was da geschrieben wird? Wie gesagt, ich habe nur die NAS getasucht, sonst nichts am Rest des netzwerkes geändert.
Seitdem schreibt irgendwas im Sekundentakt auf meine Platten. Ich vermute daß es vom Hauptrechner kommt, der Systemprozess greift jede Minute auf die IP vom NAS zu, Port 445. Ich denke es kommt daher. Falls jemand weiß wie ich es abstelle... Danke 
Zitat von "Daniel_23"der Systemprozess greift jede Minute auf die IP vom NAS zu, Port 445
Das ist Samba
Wie.......? keiner mehr probleme mit dem standby ? :roll:
Ich kämpfe immer noch mit den "md0_raid1: WRITE block 723803136 on sdb (8 sectors)" einträgen.
Nas geht schlafen.. Nach ca. 45 minuten oder ab und zu 90 minuten (unterschiedlich!), wachen die festplatten wieder aus dem nichts auf.
Zitat von "Daan1976"Ich kämpfe immer noch
Hier im Thema sehe ich dich aber das erste Mal.
Daher wären ein paar mehr Angaben und ein Log recht sinnvoll.
Zitat von "dr_mike"Hier im Thema sehe ich dich aber das erste Mal.
Daher wären ein paar mehr Angaben und ein Log recht sinnvoll.
Stimmt... ich lese und probiere aus
Da ich fast nichts mehr eingeschaltet habe, bin ich mit meinen latein am ende.
Das NAS hat es geschafft um von 19:33 bis 20:30 und von 20:35 bis ca. 21:47 ruhe zu behalten..
Zwischendurhc wurden vom NAS die platten wieder hochgefahren... nur warum ??
Sehe sehr oft SED und SETCFG in der blkdevMonitor_v2.log
Auf der suche was da geschrieben wird
[~] # find / -name vg*.log
/mnt/HDA_ROOT/.config/storage_usage_history/vg2.log
/mnt/HDA_ROOT/.config/storage_usage_history/vg1.log
Wo kommen die denn her ?
Hallo, wie so viele habe ich auch neuerdings (ich meine nach dem letzten Firmwareupdate) Probleme mit dem Standbybetrieb. Mein Log ist beigefügt.
Da taucht verdächtig viel Raid auf. ich habe aber nur eine einzelne Festplatte (119 II) oder interpretiere ich falsch?
Zitat von "Daan1976"Das NAS hat es geschafft um von 19:33 bis 20:30 und von 20:35 bis ca. 21:47 ruhe zu behalten.
Aus dem Log:
<7>[ 9768.371258] smbd(26398): dirtied inode 13484 (smb.conf) on md9<7>[ 9768.372455] smbd(26398): dirtied inode 13511 (smbpasswd) on md9<7>[ 9768.377394] create_home(26402): dirtied inode 13465 (usr_quota.conf) on md9...<7>[ 9768.367382] smbd(26398): dirtied inode 346 (gensec) on md13<7>[ 9768.367404] smbd(26398): dirtied inode 347 (krb5.so) on md13<7>[ 9768.378974] smbd(26398): dirtied inode 327 (aio_pthread.so) on md13...<7>[ 9768.367382] smbd(26398): dirtied inode 346 (gensec) on md13<7>[ 9768.367404] smbd(26398): dirtied inode 347 (krb5.so) on md13<7>[ 9768.378974] smbd(26398): dirtied inode 327 (aio_pthread.so) on md13...============= 7/10 test, Fri Apr 3 21:47:36 CEST 2015 ===============
Hier hat sich jemand per Samba eingelogt.
<7>[ 912.162967] setcfg(12735): dirtied inode 13363 (CACHEDEV1_DATA.log) on md9
<7>[ 912.163119] setcfg(12735): dirtied inode 13516 (CACHEDEV1_DATA.log.bak) on md9
<7>[ 912.164213] setcfg(12736): dirtied inode 13363 (CACHEDEV1_DATA.log.bak) on md9
<7>[ 912.165235] setcfg(12737): dirtied inode 13516 (CACHEDEV1_DATA.log.bak) on md9
<7>[ 912.167215] sed(12740): dirtied inode 13363 (CACHEDEV1_DATA.logDQFaeq) on md9
<7>[ 912.190068] setcfg(12781): dirtied inode 13550 (CACHEDEV2_DATA.log) on md9
<7>[ 912.190220] setcfg(12781): dirtied inode 13516 (CACHEDEV2_DATA.log.bak) on md9
<7>[ 912.191382] setcfg(12782): dirtied inode 13550 (CACHEDEV2_DATA.log.bak) on md9
<7>[ 912.192398] setcfg(12783): dirtied inode 13516 (CACHEDEV2_DATA.log.bak) on md9
<7>[ 912.194300] sed(12786): dirtied inode 13550 (CACHEDEV2_DATA.logFQ03Hs) on md9
<7>[ 912.318518] setcfg(12819): dirtied inode 13492 (vg1.log) on md9
<7>[ 912.318692] setcfg(12819): dirtied inode 13516 (vg1.log.bak) on md9
<7>[ 912.320828] sed(12822): dirtied inode 13492 (vg1.logRyTLBB) on md9
<7>[ 912.351200] setcfg(12852): dirtied inode 13545 (vg2.log) on md9
<7>[ 912.351371] setcfg(12852): dirtied inode 13516 (vg2.log.bak) on md9
<7>[ 912.353666] sed(12855): dirtied inode 13545 (vg2.log4dltXD) on md9
<7>[ 912.142917] storage_usage.s(12702): READ block 615960 on md9 (8 sectors)
<7>[ 912.154636] setcfg(12735): READ block 720952 on md9 (24 sectors)
<7>[ 912.184019] setcfg(12781): READ block 611272 on md9 (24 sectors)
...
<7>[ 912.295487] setcfg(12819): READ block 560760 on md9 (24 sectors)
...
<7>[ 912.343961] setcfg(12852): READ block 704592 on md9 (24 sectors)
...
============= 3/10 test, Fri Apr 3 19:20:21 CEST 2015 ===============
Diese Einträge kann ich nicht zuordnen, da es sie auf keinem meiner NAS gibt. Hier muss irgendwo bei dir eine HD-Nutzungshistorie eingestellt sein.
Zitat von "RainerBegeistert"Da taucht verdächtig viel Raid auf. ich habe aber nur eine einzelne Festplatte (119 II) oder interpretiere ich falsch?
Das ist korrekt. Auch in einem 1-Bay NAS werden die Systempartitionen als RAID1 (md9, md13) gemountet.
Zu deinem Log: Schau dir mal die Einstellungen zum Netzwerkpapierkorb an. Alles was ich im Log sehen kann, ist das Bereinigen des Selben zum eingestellten Zeitpunkt.
Danke. Habe das kontrolliert. Tatsächlich war der Netzwerkpapierkorb eingeschaltet. Habe ihn ausgeschaltet, aber keine Änderung. Die neue Log ist beigefügt. Noch eine Idee?
Zitat von "RainerBegeistert"Noch eine Idee?
Ich glaube, die Frage hättest du dir bei einem Blick ins Log selbst beantworten können.
apache, mysqld und owncloud...
Ja und Nein. 
Die Sachen laufen schon lange Zeit bei mir. Aber auch wenn ich die Netzwerkverbindung physikalisch trenne, kein Standby. Das war sonst anders. Sobald alle Maschinen aus waren, kam der Standbymodus pünktlich. Jetzt leider nicht mehr.
Also ich mache gerade einen Dauerversuch auf allen vier NAS. Dabei logge ich via Putty sämtliche Aktivitäten der Block-Devices direkt auf die Konsole.
Dabei habe ich folgendes Ergebnis:
- TS-459 und TS-412: relativ viel Schreib-/Lesetraffic im ram0 jedoch keinerlei Aktionen auf die Platten seit Stunden
- TS-251: ca. 1 zugriff aller 5sec. ins tempfs, wobei es sich um zwei Prozesse handelt (hal_enc_fan und und gen_bandwidth)
- TS-231: dies ist am entspanntesten - 1 bis 2 zugriffe aller 40 sec auf tempfs duch zwei Prozesse (hal_enc_temp und gen_bandwidth)
Im netzwerk angemeldet sind ausserdem mein Laptop (XP), ein Rechner (Win98), ein weiteres NAS (Fujitsu AMS150), ein Handy (Android) und ein Laserdrucker (HP).
Trotzdem schlafen die Platten in den NAS friedlich (eingestellte Standby-Zeit 30min)
Hier mal ein paar Logauszüge:
TS459 (30sec)
<7>[712900.928901] gen_bandwidth(8896): dirtied inode 23362 (bandwidth_record.conf) on ram0<7>[712900.928981] gen_bandwidth(8896): dirtied inode 23362 (bandwidth_record.conf) on ram0<7>[712900.929096] gen_bandwidth(8896): dirtied inode 3226170 (?) on tmpfs<7>[712901.360887] lpb_scheduler(5771): dirtied inode 6265 (?) on ram0<7>[712901.361151] lpb_scheduler(5771): dirtied inode 6265 (?) on ram0<4>[712901.712059] sync_supers(248): WRITE block 2 on ram0 (2 sectors)<4>[712902.566057] flush-1:0(864): WRITE block 49680 on ram0 (2 sectors)<4>[712902.568737] flush-1:0(864): WRITE block 49704 on ram0 (2 sectors)<4>[712902.571417] flush-1:0(864): WRITE block 180226 on ram0 (2 sectors)<4>[712902.574117] flush-1:0(864): WRITE block 180438 on ram0 (2 sectors)<4>[712902.576690] flush-1:0(864): WRITE block 4 on ram0 (2 sectors)<4>[712902.579209] flush-1:0(864): WRITE block 49670 on ram0 (2 sectors)<4>[712902.581736] flush-1:0(864): WRITE block 49672 on ram0 (2 sectors)<7>[712905.932066] gen_bandwidth(8896): dirtied inode 3226179 (?) on tmpfs<7>[712906.361935] lpb_scheduler(5771): dirtied inode 6265 (?) on ram0<7>[712906.362194] lpb_scheduler(5771): dirtied inode 6265 (?) on ram0<4>[712907.584085] flush-1:0(864): WRITE block 53272 on ram0 (2 sectors)<4>[712907.712074] sync_supers(248): WRITE block 2 on ram0 (2 sectors)<7>[712909.655393] hd_util(9372): dirtied inode 6265 (?) on ram0<7>[712909.655411] hd_util(9372): dirtied inode 6169 (NAS) on ram0<7>[712909.655418] hd_util(9372): dirtied inode 6169 (NAS) on ram0<7>[712909.655516] hd_util(9372): dirtied inode 6201 (ledvalue) on ram0<7>[712909.655585] hd_util(9372): dirtied inode 6201 (ledvalue) on ram0<7>[712909.655767] hd_util(9372): dirtied inode 6265 (?) on ram0<7>[712911.363074] lpb_scheduler(5771): dirtied inode 6265 (?) on ram0<7>[712911.363274] lpb_scheduler(5771): dirtied inode 6265 (?) on ram0<4>[712912.586058] flush-1:0(864): WRITE block 180742 on ram0 (2 sectors)<4>[712913.712073] sync_supers(248): WRITE block 2 on ram0 (2 sectors)<7>[712915.935328] gen_bandwidth(8896): dirtied inode 23362 (bandwidth_record.conf) on ram0<7>[712915.935408] gen_bandwidth(8896): dirtied inode 23362 (bandwidth_record.conf) on ram0<7>[712915.936094] gen_bandwidth(8896): dirtied inode 3226205 (?) on tmpfs<7>[712916.363887] lpb_scheduler(5771): dirtied inode 6265 (?) on ram0<7>[712916.364143] lpb_scheduler(5771): dirtied inode 6265 (?) on ram0<4>[712917.588057] flush-1:0(864): WRITE block 49672 on ram0 (2 sectors)<4>[712917.590671] flush-1:0(864): WRITE block 49680 on ram0 (2 sectors)<4>[712917.593960] flush-1:0(864): WRITE block 49698 on ram0 (2 sectors)<4>[712917.596561] flush-1:0(864): WRITE block 49704 on ram0 (2 sectors)<4>[712917.599826] flush-1:0(864): WRITE block 180226 on ram0 (2 sectors)<4>[712917.602480] flush-1:0(864): WRITE block 180438 on ram0 (2 sectors)<4>[712917.605700] flush-1:0(864): WRITE block 4 on ram0 (2 sectors)<4>[712917.608543] flush-1:0(864): WRITE block 49670 on ram0 (2 sectors)<4>[712919.712100] sync_supers(248): WRITE block 2 on ram0 (2 sectors)<7>[712920.939065] gen_bandwidth(8896): dirtied inode 3226214 (?) on tmpfs<7>[712921.364974] lpb_scheduler(5771): dirtied inode 6265 (?) on ram0<7>[712921.365250] lpb_scheduler(5771): dirtied inode 6265 (?) on ram0<4>[712922.611063] flush-1:0(864): WRITE block 53272 on ram0 (2 sectors)<4>[712922.613644] flush-1:0(864): WRITE block 64842 on ram0 (2 sectors)<7>[712923.616670] hwmond(8581): dirtied inode 6248 (hal_util.conf.lck) on ram0<4>[712925.712086] sync_supers(248): WRITE block 2 on ram0 (2 sectors)<7>[712926.366149] lpb_scheduler(5771): dirtied inode 6265 (?) on ram0<7>[712926.366167] lpb_scheduler(5771): dirtied inode 6169 (NAS) on ram0<7>[712926.366174] lpb_scheduler(5771): dirtied inode 6169 (NAS) on ram0<7>[712926.366362] lpb_scheduler(5771): dirtied inode 6265 (?) on ram0<4>[712927.616063] flush-1:0(864): WRITE block 180742 on ram0 (2 sectors)<7>[712930.941663] gen_bandwidth(8896): dirtied inode 23362 (bandwidth_record.conf) on ram0<7>[712930.941742] gen_bandwidth(8896): dirtied inode 23362 (bandwidth_record.conf) on ram0<7>[712930.943090] gen_bandwidth(8896): dirtied inode 3226239 (?) on tmpfs
TS-412 (30sec)
<4>[712200.571755] flush-1:0(508): WRITE block 54278 on ram0 (2 sectors)<4>[712201.761720] sync_supers(138): WRITE block 2 on ram0 (2 sectors)<7>[712203.611852] lpb_scheduler(4030): dirtied inode 2158 (?) on ram0<7>[712203.612223] lpb_scheduler(4030): dirtied inode 2158 (?) on ram0<4>[712203.761720] sync_supers(138): WRITE block 2 on ram0 (2 sectors)<4>[712204.571745] flush-1:0(508): WRITE block 35136 on ram0 (2 sectors)<7>[712205.292187] gen_bandwidth(6341): dirtied inode 5259 (bandwidth_record.conf) on ram0<7>[712205.292357] gen_bandwidth(6341): dirtied inode 5259 (bandwidth_record.conf) on ram0<4>[712205.571739] flush-1:0(508): WRITE block 4 on ram0 (2 sectors)<4>[712205.571799] flush-1:0(508): WRITE block 16662 on ram0 (2 sectors)<4>[712205.571839] flush-1:0(508): WRITE block 16766 on ram0 (2 sectors)<4>[712205.571877] flush-1:0(508): WRITE block 16776 on ram0 (2 sectors)<4>[712205.571915] flush-1:0(508): WRITE block 32770 on ram0 (2 sectors)<4>[712205.571953] flush-1:0(508): WRITE block 49428 on ram0 (2 sectors)<4>[712205.571990] flush-1:0(508): WRITE block 49438 on ram0 (2 sectors)<4>[712205.761735] sync_supers(138): WRITE block 2 on ram0 (2 sectors)<7>[712208.631787] lpb_scheduler(4030): dirtied inode 2158 (?) on ram0<7>[712208.631820] lpb_scheduler(4030): dirtied inode 2197 (NAS) on ram0<7>[712208.631834] lpb_scheduler(4030): dirtied inode 2197 (NAS) on ram0<7>[712208.632183] lpb_scheduler(4030): dirtied inode 2158 (?) on ram0<4>[712209.761724] sync_supers(138): WRITE block 2 on ram0 (2 sectors)<7>[712210.142601] hwmond(5721): dirtied inode 2143 (hal_util.conf.lck) on ram0<4>[712210.571733] flush-1:0(508): WRITE block 54278 on ram0 (2 sectors)<4>[712211.571734] flush-1:0(508): WRITE block 49438 on ram0 (2 sectors)<4>[712211.571804] flush-1:0(508): WRITE block 4 on ram0 (2 sectors)<4>[712211.571844] flush-1:0(508): WRITE block 16662 on ram0 (2 sectors)<4>[712211.571882] flush-1:0(508): WRITE block 16766 on ram0 (2 sectors)<4>[712211.571920] flush-1:0(508): WRITE block 32770 on ram0 (2 sectors)<4>[712211.571957] flush-1:0(508): WRITE block 49428 on ram0 (2 sectors)<4>[712211.761723] sync_supers(138): WRITE block 2 on ram0 (2 sectors)<7>[712213.651788] lpb_scheduler(4030): dirtied inode 2158 (?) on ram0<7>[712213.652160] lpb_scheduler(4030): dirtied inode 2158 (?) on ram0<4>[712213.761720] sync_supers(138): WRITE block 2 on ram0 (2 sectors)<4>[712214.571742] flush-1:0(508): WRITE block 35136 on ram0 (2 sectors)<7>[712215.332182] gen_bandwidth(6341): dirtied inode 5259 (bandwidth_record.conf) on ram0<7>[712215.332355] gen_bandwidth(6341): dirtied inode 5259 (bandwidth_record.conf) on ram0<4>[712215.761779] sync_supers(138): WRITE block 2 on ram0 (2 sectors)<4>[712217.571735] flush-1:0(508): WRITE block 49428 on ram0 (2 sectors)<4>[712217.571803] flush-1:0(508): WRITE block 4 on ram0 (2 sectors)<4>[712217.571844] flush-1:0(508): WRITE block 16662 on ram0 (2 sectors)<4>[712217.571883] flush-1:0(508): WRITE block 16762 on ram0 (2 sectors)<4>[712217.571915] flush-1:0(508): WRITE block 16766 on ram0 (2 sectors)<4>[712217.571953] flush-1:0(508): WRITE block 16776 on ram0 (2 sectors)<4>[712217.571990] flush-1:0(508): WRITE block 32770 on ram0 (2 sectors)<7>[712218.671793] lpb_scheduler(4030): dirtied inode 2158 (?) on ram0<7>[712218.671824] lpb_scheduler(4030): dirtied inode 2197 (NAS) on ram0<7>[712218.671837] lpb_scheduler(4030): dirtied inode 2197 (NAS) on ram0<7>[712218.672189] lpb_scheduler(4030): dirtied inode 2158 (?) on ram0<4>[712219.761724] sync_supers(138): WRITE block 2 on ram0 (2 sectors)<4>[712220.571738] flush-1:0(508): WRITE block 54278 on ram0 (2 sectors)<4>[712221.761726] sync_supers(138): WRITE block 2 on ram0 (2 sectors)<7>[712223.691782] lpb_scheduler(4030): dirtied inode 2158 (?) on ram0<7>[712223.692150] lpb_scheduler(4030): dirtied inode 2158 (?) on ram0<4>[712223.761719] sync_supers(138): WRITE block 2 on ram0 (2 sectors)<7>[712223.893212] hd_util(16004): dirtied inode 2158 (?) on ram0<7>[712223.893384] hd_util(16004): dirtied inode 7019 (ledvalue) on ram0<7>[712223.893511] hd_util(16004): dirtied inode 7019 (ledvalue) on ram0<7>[712223.893792] hd_util(16004): dirtied inode 2158 (?) on ram0<4>[712224.571740] flush-1:0(508): WRITE block 32770 on ram0 (2 sectors)<4>[712224.571800] flush-1:0(508): WRITE block 49428 on ram0 (2 sectors)<4>[712224.571841] flush-1:0(508): WRITE block 49438 on ram0 (2 sectors)<4>[712224.571886] flush-1:0(508): WRITE block 4 on ram0 (2 sectors)<4>[712224.571925] flush-1:0(508): WRITE block 276 on ram0 (2 sectors)<4>[712224.571962] flush-1:0(508): WRITE block 16660 on ram0 (2 sectors)<4>[712224.571994] flush-1:0(508): WRITE block 16662 on ram0 (2 sectors)<4>[712224.572030] flush-1:0(508): WRITE block 16766 on ram0 (2 sectors)<4>[712224.572085] flush-1:0(508): WRITE block 35136 on ram0 (2 sectors)<7>[712225.372193] gen_bandwidth(6341): dirtied inode 5259 (bandwidth_record.conf) on ram0<7>[712225.372366] gen_bandwidth(6341): dirtied inode 5259 (bandwidth_record.conf) on ram0<4>[712225.761730] sync_supers(138): WRITE block 2 on ram0 (2 sectors)<7>[712228.711856] lpb_scheduler(4030): dirtied inode 2158 (?) on ram0<7>[712228.711890] lpb_scheduler(4030): dirtied inode 2197 (NAS) on ram0<7>[712228.711903] lpb_scheduler(4030): dirtied inode 2197 (NAS) on ram0<7>[712228.712248] lpb_scheduler(4030): dirtied inode 2158 (?) on ram0<4>[712229.571739] flush-1:0(508): WRITE block 802 on ram0 (2 sectors)<4>[712229.571833] flush-1:0(508): WRITE block 16766 on ram0 (2 sectors)<4>[712229.571876] flush-1:0(508): WRITE block 16776 on ram0 (2 sectors)<4>[712229.571915] flush-1:0(508): WRITE block 32770 on ram0 (2 sectors)<4>[712229.571952] flush-1:0(508): WRITE block 49428 on ram0 (2 sectors)<4>[712229.571989] flush-1:0(508): WRITE block 65552 on ram0 (2 sectors)<4>[712229.572032] flush-1:0(508): WRITE block 4 on ram0 (2 sectors)<4>[712229.572069] flush-1:0(508): WRITE block 16662 on ram0 (2 sectors)<4>[712229.761724] sync_supers(138): WRITE block 2 on ram0 (2 sectors)<4>[712230.571733] flush-1:0(508): WRITE block 54278 on ram0 (2 sectors)
TS231 (10min)
<7>[711601.610792] hal_enc_temp(2174): dirtied inode 3646052 (em_0.info) on tmpfs<7>[711614.210294] gen_bandwidth(7941): dirtied inode 3647784 (?) on tmpfs<7>[711661.643968] hal_enc_temp(2174): dirtied inode 3646430 (em_0.info) on tmpfs<7>[711709.250325] gen_bandwidth(7941): dirtied inode 3648764 (?) on tmpfs<7>[711734.260377] gen_bandwidth(7941): dirtied inode 3648829 (?) on tmpfs<7>[711804.290406] gen_bandwidth(7941): dirtied inode 3649026 (?) on tmpfs<7>[711829.300352] gen_bandwidth(7941): dirtied inode 3649086 (?) on tmpfs<7>[711841.684348] hal_enc_temp(2174): dirtied inode 3647898 (em_0.info) on tmpfs<7>[711849.310298] gen_bandwidth(7941): dirtied inode 3649148 (?) on tmpfs<7>[711901.717577] hal_enc_temp(2174): dirtied inode 3648318 (em_0.info) on tmpfs<7>[711919.340390] gen_bandwidth(7941): dirtied inode 3649358 (?) on tmpfs<7>[711969.360323] gen_bandwidth(7941): dirtied inode 3649436 (?) on tmpfs<7>[711999.220290] lpb_scheduler(5345): dirtied inode 3649507 (.application.conf.lck) on tmpfs<7>[712014.380383] gen_bandwidth(7941): dirtied inode 3649536 (?) on tmpfs<7>[712021.754647] hal_enc_temp(2174): dirtied inode 3649294 (em_0.info) on tmpfs<7>[712039.390297] gen_bandwidth(7941): dirtied inode 3650628 (?) on tmpfs<7>[712081.787735] hal_enc_temp(2174): dirtied inode 3649819 (em_0.info) on tmpfs<7>[712141.829464] hal_enc_temp(2174): dirtied inode 3650770 (em_0.info) on tmpfs<7>[712159.440303] gen_bandwidth(7941): dirtied inode 3651066 (?) on tmpfs<7>[712179.450306] gen_bandwidth(7941): dirtied inode 3651139 (?) on tmpfs<7>[712229.470293] gen_bandwidth(7941): dirtied inode 3650153 (?) on tmpfs
TS-251 (2min)
<7>[47000.882645] hal_enc_temp(1918): dirtied inode 355067 (em_0.info) on tmpfs
<7>[47001.566704] hal_enc_fan(1923): dirtied inode 357011 (em_0.info) on tmpfs
<7>[47006.570012] hal_enc_fan(1923): dirtied inode 355084 (em_0.info) on tmpfs
<7>[47007.356625] gen_bandwidth(7313): dirtied inode 357049 (?) on tmpfs
<7>[47011.573394] hal_enc_fan(1923): dirtied inode 357043 (em_0.info) on tmpfs
<7>[47017.367156] gen_bandwidth(7313): dirtied inode 357077 (?) on tmpfs
<7>[47017.687342] lpb_scheduler(4948): dirtied inode 355114 (.application.conf.lck) on tmpfs
<7>[47021.579894] hal_enc_fan(1923): dirtied inode 355108 (em_0.info) on tmpfs
<7>[47026.583085] hal_enc_fan(1923): dirtied inode 357096 (em_0.info) on tmpfs
<7>[47027.376640] gen_bandwidth(7313): dirtied inode 357113 (?) on tmpfs
<7>[47027.694856] lpb_scheduler(4948): dirtied inode 355136 (.application.conf.lck) on tmpfs
<7>[47031.586381] hal_enc_fan(1923): dirtied inode 355135 (em_0.info) on tmpfs
<7>[47036.589575] hal_enc_fan(1923): dirtied inode 357134 (em_0.info) on tmpfs
<7>[47036.589651] hal_enc_fan(1923): dirtied inode 357158 (em_0.inf~) on tmpfs
<7>[47037.387175] gen_bandwidth(7313): dirtied inode 357166 (?) on tmpfs
<7>[47047.396651] gen_bandwidth(7313): dirtied inode 357188 (?) on tmpfs
<7>[47051.599355] hal_enc_fan(1923): dirtied inode 355169 (em_0.info) on tmpfs
<7>[47057.407174] gen_bandwidth(7313): dirtied inode 357227 (?) on tmpfs
<7>[47057.717360] lpb_scheduler(4948): dirtied inode 355175 (.application.conf.lck) on tmpfs
<7>[47060.934858] hal_enc_temp(1918): dirtied inode 357209 (em_0.info) on tmpfs
<7>[47061.605778] hal_enc_fan(1923): dirtied inode 357243 (em_0.info) on tmpfs
<7>[47066.609025] hal_enc_fan(1923): dirtied inode 355197 (em_0.info) on tmpfs
<7>[47067.417687] gen_bandwidth(7313): dirtied inode 357282 (?) on tmpfs
<7>[47067.724871] lpb_scheduler(4948): dirtied inode 355202 (.application.conf.lck) on tmpfs
<7>[47076.615585] hal_enc_fan(1923): dirtied inode 357272 (em_0.info) on tmpfs
<7>[47076.615662] hal_enc_fan(1923): dirtied inode 355225 (em_0.inf~) on tmpfs
<7>[47077.427174] gen_bandwidth(7313): dirtied inode 357305 (?) on tmpfs
<7>[47086.622150] hal_enc_fan(1923): dirtied inode 357334 (em_0.inf~) on tmpfs
<7>[47087.437674] gen_bandwidth(7313): dirtied inode 357344 (?) on tmpfs
<7>[47097.447170] gen_bandwidth(7313): dirtied inode 355238 (?) on tmpfs
<7>[47106.635183] hal_enc_fan(1923): dirtied inode 355259 (em_0.info) on tmpfs
<7>[47107.457696] gen_bandwidth(7313): dirtied inode 355278 (?) on tmpfs
<7>[47107.754883] lpb_scheduler(4948): dirtied inode 355279 (.application.conf.lck) on tmpfs
<7>[47111.638438] hal_enc_fan(1923): dirtied inode 357383 (em_0.info) on tmpfs
<7>[47117.467213] gen_bandwidth(7313): dirtied inode 355309 (?) on tmpfs
<7>[47120.987127] hal_enc_temp(1918): dirtied inode 355297 (em_0.info) on tmpfsWenn ich den Server HS-251 (4.1.3 17.02.2015) automatisch über den Energiezeiplan einschalten lasse, dann gehen die Festplatten nicht in den Standby. Wenn ich jedoch einen manuellen Neustart mache, dann ist der Standby kein Problem. Feature/Bug, weiß jemand woran das liegen könnte? Das würde auch viele Beiträge erkläre warum es bei manchen mal funktioniert und manchmal nicht. Das kann sich eigentlich nicht um ein Einzelproblem handeln.
EDIT:
Und bevor jemand fragt:
============= 0/100 test, Mon Apr 6 09:39:19 CEST 2015 ===============
<7>[ 9947.487382] vgdisplay(19641): READ block 0 on md9 (8 sectors)
<7>[ 9947.533454] vgdisplay(19645): READ block 0 on md9 (8 sectors)
<7>[ 9947.548381] vgdisplay(19649): READ block 0 on md9 (8 sectors)
<7>[ 9947.573420] vgdisplay(19653): READ block 0 on md9 (8 sectors)
<7>[ 9947.509560] vgdisplay(19641): READ block 0 on md13 (8 sectors)
<7>[ 9947.533563] vgdisplay(19645): READ block 0 on md13 (8 sectors)
<7>[ 9947.548486] vgdisplay(19649): READ block 0 on md13 (8 sectors)
<7>[ 9947.573642] vgdisplay(19653): READ block 0 on md13 (8 sectors)
<7>[ 9947.485520] vgdisplay(19641): READ block 0 on md1 (8 sectors)
<7>[ 9947.485643] vgdisplay(19641): READ block 8 on md1 (8 sectors)
<7>[ 9947.485745] vgdisplay(19641): READ block 16 on md1 (8 sectors)
<7>[ 9947.485855] vgdisplay(19641): READ block 16 on md1 (8 sectors)
<7>[ 9947.509560] vgdisplay(19641): READ block 0 on md13 (8 sectors)
<7>[ 9947.509881] vgdisplay(19641): READ block 8 on md1 (8 sectors)
<7>[ 9947.510083] vgdisplay(19641): READ block 16 on md1 (8 sectors)
<7>[ 9947.510255] vgdisplay(19641): READ block 16 on md1 (8 sectors)
<7>[ 9947.532863] vgdisplay(19645): READ block 0 on md1 (8 sectors)
<7>[ 9947.533051] vgdisplay(19645): READ block 8 on md1 (8 sectors)
<7>[ 9947.533158] vgdisplay(19645): READ block 16 on md1 (8 sectors)
<7>[ 9947.533271] vgdisplay(19645): READ block 16 on md1 (8 sectors)
<7>[ 9947.533563] vgdisplay(19645): READ block 0 on md13 (8 sectors)
<7>[ 9947.533691] vgdisplay(19645): READ block 8 on md1 (8 sectors)
<7>[ 9947.533790] vgdisplay(19645): READ block 16 on md1 (8 sectors)
<7>[ 9947.533894] vgdisplay(19645): READ block 16 on md1 (8 sectors)
<7>[ 9947.546784] vgdisplay(19649): READ block 0 on md1 (8 sectors)
<7>[ 9947.546905] vgdisplay(19649): READ block 8 on md1 (8 sectors)
<7>[ 9947.547867] vgdisplay(19649): READ block 16 on md1 (8 sectors)
<7>[ 9947.548208] vgdisplay(19649): READ block 16 on md1 (8 sectors)
<7>[ 9947.548486] vgdisplay(19649): READ block 0 on md13 (8 sectors)
<7>[ 9947.548616] vgdisplay(19649): READ block 8 on md1 (8 sectors)
<7>[ 9947.548713] vgdisplay(19649): READ block 16 on md1 (8 sectors)
<7>[ 9947.548814] vgdisplay(19649): READ block 16 on md1 (8 sectors)
<7>[ 9947.572309] vgdisplay(19653): READ block 0 on md1 (8 sectors)
<7>[ 9947.572575] vgdisplay(19653): READ block 8 on md1 (8 sectors)
<7>[ 9947.572728] vgdisplay(19653): READ block 16 on md1 (8 sectors)
<7>[ 9947.573001] vgdisplay(19653): READ block 16 on md1 (8 sectors)
<7>[ 9947.573642] vgdisplay(19653): READ block 0 on md13 (8 sectors)
<7>[ 9947.573913] vgdisplay(19653): READ block 8 on md1 (8 sectors)
<7>[ 9947.574090] vgdisplay(19653): READ block 16 on md1 (8 sectors)
<7>[ 9947.574261] vgdisplay(19653): READ block 16 on md1 (8 sectors)
<7>[ 9947.485358] vgdisplay(19641): READ block 0 on md256 (8 sectors)
<7>[ 9947.532539] vgdisplay(19645): READ block 0 on md256 (8 sectors)
<7>[ 9947.546613] vgdisplay(19649): READ block 0 on md256 (8 sectors)
<7>[ 9947.571982] vgdisplay(19653): READ block 0 on md256 (8 sectors)
============= 1/100 test, Mon Apr 6 09:41:37 CEST 2015 ===============
<7>[10018.418626] touch(20063): dirtied inode 20059 (volumeStatus.conf) on md9
<7>[10019.514312] cp(20107): dirtied inode 20137 (iscsi_trgt.conf.last) on md9
<7>[10019.514323] cp(20107): dirtied inode 20137 (iscsi_trgt.conf.last) on md9
<7>[10018.408844] lvs(20060): READ block 0 on md9 (8 sectors)
<7>[10023.686530] kjournald(262): WRITE block 966736 on md9 (8 sectors)
<7>[10023.686575] md9_raid1(252): WRITE block 1060216 on sdb1 (1 sectors)
<7>[10023.686600] md9_raid1(252): WRITE block 1060216 on sda1 (1 sectors)
<7>[10023.717977] md9_raid1(252): WRITE block 1060232 on sdb1 (1 sectors)
<7>[10023.717989] md9_raid1(252): WRITE block 1060232 on sda1 (1 sectors)
<7>[10023.740601] kjournald(262): WRITE block 547472 on md9 (8 sectors)
<7>[10023.740646] kjournald(262): WRITE block 547480 on md9 (8 sectors)
<7>[10023.740673] kjournald(262): WRITE block 547488 on md9 (8 sectors)
<7>[10023.740698] kjournald(262): WRITE block 547496 on md9 (8 sectors)
<7>[10023.740742] kjournald(262): WRITE block 547504 on md9 (8 sectors)
<7>[10023.740768] kjournald(262): WRITE block 547512 on md9 (8 sectors)
<7>[10023.741156] kjournald(262): WRITE block 547520 on md9 (8 sectors)
<7>[10023.941688] md9_raid1(252): WRITE block 1060216 on sdb1 (1 sectors)
<7>[10023.941735] md9_raid1(252): WRITE block 1060216 on sda1 (1 sectors)
<7>[10023.962656] md9_raid1(252): WRITE block 1060232 on sdb1 (1 sectors)
<7>[10023.962683] md9_raid1(252): WRITE block 1060232 on sda1 (1 sectors)
<7>[10018.409093] lvs(20060): READ block 0 on md13 (8 sectors)
<7>[10018.407762] lvs(20060): READ block 0 on md1 (8 sectors)
<7>[10018.408007] lvs(20060): READ block 8 on md1 (8 sectors)
<7>[10018.408208] lvs(20060): READ block 16 on md1 (8 sectors)
<7>[10018.408407] lvs(20060): READ block 16 on md1 (8 sectors)
<7>[10018.409093] lvs(20060): READ block 0 on md13 (8 sectors)
<7>[10018.409362] lvs(20060): READ block 8 on md1 (8 sectors)
<7>[10018.409535] lvs(20060): READ block 16 on md1 (8 sectors)
<7>[10018.409707] lvs(20060): READ block 16 on md1 (8 sectors)
<7>[10018.407409] lvs(20060): READ block 0 on md256 (8 sectors)
<7>[10023.686600] md9_raid1(252): WRITE block 1060216 on sda1 (1 sectors)
<7>[10023.717989] md9_raid1(252): WRITE block 1060232 on sda1 (1 sectors)
<7>[10023.941735] md9_raid1(252): WRITE block 1060216 on sda1 (1 sectors)
<7>[10023.962683] md9_raid1(252): WRITE block 1060232 on sda1 (1 sectors)
<7>[10023.686575] md9_raid1(252): WRITE block 1060216 on sdb1 (1 sectors)
<7>[10023.717977] md9_raid1(252): WRITE block 1060232 on sdb1 (1 sectors)
<7>[10023.941688] md9_raid1(252): WRITE block 1060216 on sdb1 (1 sectors)
<7>[10023.962656] md9_raid1(252): WRITE block 1060232 on sdb1 (1 sectors)
============= 2/100 test, Mon Apr 6 09:42:31 CEST 2015 ===============
<7>[10038.464161] kworker/u4:2(72): WRITE block 0 on md9 (8 sectors)
<7>[10038.464206] md9_raid1(252): WRITE block 1060216 on sdb1 (1 sectors)
<7>[10038.464233] md9_raid1(252): WRITE block 1060216 on sda1 (1 sectors)
<7>[10038.972380] md9_raid1(252): WRITE block 1060232 on sdb1 (1 sectors)
<7>[10038.972505] md9_raid1(252): WRITE block 1060232 on sda1 (1 sectors)
<7>[10038.994610] kworker/u4:2(72): WRITE block 8 on md9 (8 sectors)
<7>[10038.994623] kworker/u4:2(72): WRITE block 786704 on md9 (8 sectors)
<7>[10038.994634] kworker/u4:2(72): WRITE block 786784 on md9 (8 sectors)
<7>[10038.994646] kworker/u4:2(72): WRITE block 786824 on md9 (8 sectors)
<7>[10039.195559] md9_raid1(252): WRITE block 1060216 on sdb1 (1 sectors)
<7>[10039.195571] md9_raid1(252): WRITE block 1060216 on sda1 (1 sectors)
<7>[10039.216905] md9_raid1(252): WRITE block 1060232 on sdb1 (1 sectors)
<7>[10039.216916] md9_raid1(252): WRITE block 1060232 on sda1 (1 sectors)
<7>[10038.464233] md9_raid1(252): WRITE block 1060216 on sda1 (1 sectors)
<7>[10038.972505] md9_raid1(252): WRITE block 1060232 on sda1 (1 sectors)
<7>[10039.195571] md9_raid1(252): WRITE block 1060216 on sda1 (1 sectors)
<7>[10039.216916] md9_raid1(252): WRITE block 1060232 on sda1 (1 sectors)
<7>[10038.464206] md9_raid1(252): WRITE block 1060216 on sdb1 (1 sectors)
<7>[10038.972380] md9_raid1(252): WRITE block 1060232 on sdb1 (1 sectors)
<7>[10039.195559] md9_raid1(252): WRITE block 1060216 on sdb1 (1 sectors)
<7>[10039.216905] md9_raid1(252): WRITE block 1060232 on sdb1 (1 sectors)
============= 3/100 test, Mon Apr 6 09:43:46 CEST 2015 ===============
<7>[10248.684725] vgdisplay(21264): READ block 0 on md9 (8 sectors)
<7>[10248.703678] vgdisplay(21268): READ block 0 on md9 (8 sectors)
<7>[10248.728998] vgdisplay(21272): READ block 0 on md9 (8 sectors)
<7>[10248.748752] vgdisplay(21276): READ block 0 on md9 (8 sectors)
<7>[10248.684858] vgdisplay(21264): READ block 0 on md13 (8 sectors)
<7>[10248.703789] vgdisplay(21268): READ block 0 on md13 (8 sectors)
<7>[10248.729218] vgdisplay(21272): READ block 0 on md13 (8 sectors)
<7>[10248.748973] vgdisplay(21276): READ block 0 on md13 (8 sectors)
<7>[10248.684209] vgdisplay(21264): READ block 0 on md1 (8 sectors)
<7>[10248.684344] vgdisplay(21264): READ block 8 on md1 (8 sectors)
<7>[10248.684447] vgdisplay(21264): READ block 16 on md1 (8 sectors)
<7>[10248.684557] vgdisplay(21264): READ block 16 on md1 (8 sectors)
<7>[10248.684858] vgdisplay(21264): READ block 0 on md13 (8 sectors)
<7>[10248.684992] vgdisplay(21264): READ block 8 on md1 (8 sectors)
<7>[10248.685091] vgdisplay(21264): READ block 16 on md1 (8 sectors)
<7>[10248.685193] vgdisplay(21264): READ block 16 on md1 (8 sectors)
<7>[10248.703157] vgdisplay(21268): READ block 0 on md1 (8 sectors)
<7>[10248.703280] vgdisplay(21268): READ block 8 on md1 (8 sectors)
<7>[10248.703383] vgdisplay(21268): READ block 16 on md1 (8 sectors)
<7>[10248.703492] vgdisplay(21268): READ block 16 on md1 (8 sectors)
<7>[10248.703789] vgdisplay(21268): READ block 0 on md13 (8 sectors)
<7>[10248.703927] vgdisplay(21268): READ block 8 on md1 (8 sectors)
<7>[10248.704020] vgdisplay(21268): READ block 16 on md1 (8 sectors)
<7>[10248.704123] vgdisplay(21268): READ block 16 on md1 (8 sectors)
<7>[10248.727921] vgdisplay(21272): READ block 0 on md1 (8 sectors)
<7>[10248.728166] vgdisplay(21272): READ block 8 on md1 (8 sectors)
<7>[10248.728337] vgdisplay(21272): READ block 16 on md1 (8 sectors)
<7>[10248.728554] vgdisplay(21272): READ block 16 on md1 (8 sectors)
<7>[10248.729218] vgdisplay(21272): READ block 0 on md13 (8 sectors)
<7>[10248.729487] vgdisplay(21272): READ block 8 on md1 (8 sectors)
<7>[10248.729654] vgdisplay(21272): READ block 16 on md1 (8 sectors)
<7>[10248.729897] vgdisplay(21272): READ block 16 on md1 (8 sectors)
<7>[10248.747568] vgdisplay(21276): READ block 0 on md1 (8 sectors)
<7>[10248.747906] vgdisplay(21276): READ block 8 on md1 (8 sectors)
<7>[10248.748087] vgdisplay(21276): READ block 16 on md1 (8 sectors)
<7>[10248.748308] vgdisplay(21276): READ block 16 on md1 (8 sectors)
<7>[10248.748973] vgdisplay(21276): READ block 0 on md13 (8 sectors)
<7>[10248.749246] vgdisplay(21276): READ block 8 on md1 (8 sectors)
<7>[10248.683930] vgdisplay(21264): READ block 0 on md256 (8 sectors)
<7>[10248.703005] vgdisplay(21268): READ block 0 on md256 (8 sectors)
<7>[10248.727548] vgdisplay(21272): READ block 0 on md256 (8 sectors)
<7>[10248.747269] vgdisplay(21276): READ block 0 on md256 (8 sectors)
============= 4/100 test, Mon Apr 6 09:46:09 CEST 2015 ===============
<7>[10319.603052] touch(21663): dirtied inode 20059 (volumeStatus.conf) on md9
<7>[10319.593103] lvs(21660): READ block 0 on md9 (8 sectors)
<7>[10319.593322] lvs(21660): READ block 0 on md13 (8 sectors)
play(21276): READ block 16 on md1 (8 sectors)
<7>[10248.749586] vgdisplay(21276): READ block 16 on md1 (8 sectors)
<7>[10319.591973] lvs(21660): READ block 0 on md1 (8 sectors)
<7>[10319.592222] lvs(21660): READ block 8 on md1 (8 sectors)
<7>[10319.592415] lvs(21660): READ block 16 on md1 (8 sectors)
<7>[10319.592616] lvs(21660): READ block 16 on md1 (8 sectors)
<7>[10319.593322] lvs(21660): READ block 0 on md13 (8 sectors)
<7>[10319.593589] lvs(21660): READ block 8 on md1 (8 sectors)
<7>[10319.593740] lvs(21660): READ block 16 on md1 (8 sectors)
<7>[10319.593959] lvs(21660): READ block 16 on md1 (8 sectors)
<7>[10319.591646] lvs(21660): READ block 0 on md256 (8 sectors)
============= 5/100 test, Mon Apr 6 09:47:21 CEST 2015 ===============
<7>[10320.631761] cp(21713): dirtied inode 20137 (iscsi_trgt.conf.last) on md9
<7>[10320.631773] cp(21713): dirtied inode 20137 (iscsi_trgt.conf.last) on md9
<7>[10324.879467] kjournald(262): WRITE block 802856 on md9 (8 sectors)
<7>[10324.879506] md9_raid1(252): WRITE block 1060216 on sdb1 (1 sectors)
<7>[10324.879530] md9_raid1(252): WRITE block 1060216 on sda1 (1 sectors)
<7>[10324.912977] md9_raid1(252): WRITE block 1060232 on sdb1 (1 sectors)
<7>[10324.912989] md9_raid1(252): WRITE block 1060232 on sda1 (1 sectors)
<7>[10324.935573] kjournald(262): WRITE block 547528 on md9 (8 sectors)
<7>[10324.935601] kjournald(262): WRITE block 547536 on md9 (8 sectors)
<7>[10324.935628] kjournald(262): WRITE block 547544 on md9 (8 sectors)
<7>[10324.935671] kjournald(262): WRITE block 547552 on md9 (8 sectors)
<7>[10324.935698] kjournald(262): WRITE block 547560 on md9 (8 sectors)
<7>[10324.935725] kjournald(262): WRITE block 547568 on md9 (8 sectors)
<7>[10324.936114] kjournald(262): WRITE block 547576 on md9 (8 sectors)
<7>[10325.136586] md9_raid1(252): WRITE block 1060216 on sdb1 (1 sectors)
<7>[10325.136634] md9_raid1(252): WRITE block 1060216 on sda1 (1 sectors)
<7>[10325.157606] md9_raid1(252): WRITE block 1060232 on sdb1 (1 sectors)
<7>[10325.157633] md9_raid1(252): WRITE block 1060232 on sda1 (1 sectors)
<7>[10339.651984] kworker/u4:2(72): WRITE block 786824 on md9 (8 sectors)
<7>[10339.652010] md9_raid1(252): WRITE block 1060216 on sdb1 (1 sectors)
<7>[10339.652037] md9_raid1(252): WRITE block 1060216 on sda1 (1 sectors)
<7>[10340.167331] md9_raid1(252): WRITE block 1060232 on sdb1 (1 sectors)
<7>[10340.167354] md9_raid1(252): WRITE block 1060232 on sda1 (1 sectors)
<7>[10340.189601] kworker/u4:2(72): WRITE block 0 on md9 (8 sectors)
<7>[10340.189614] kworker/u4:2(72): WRITE block 8 on md9 (8 sectors)
<7>[10340.189625] kworker/u4:2(72): WRITE block 786704 on md9 (8 sectors)
<7>[10340.189635] kworker/u4:2(72): WRITE block 786784 on md9 (8 sectors)
<7>[10340.390454] md9_raid1(252): WRITE block 1060216 on sdb1 (1 sectors)
<7>[10340.390476] md9_raid1(252): WRITE block 1060216 on sda1 (1 sectors)
<7>[10340.411894] md9_raid1(252): WRITE block 1060232 on sdb1 (1 sectors)
<7>[10340.411905] md9_raid1(252): WRITE block 1060232 on sda1 (1 sectors)
<7>[10324.879530] md9_raid1(252): WRITE block 1060216 on sda1 (1 sectors)
<7>[10324.912989] md9_raid1(252): WRITE block 1060232 on sda1 (1 sectors)
<7>[10325.136634] md9_raid1(252): WRITE block 1060216 on sda1 (1 sectors)
<7>[10325.157633] md9_raid1(252): WRITE block 1060232 on sda1 (1 sectors)
<7>[10339.652037] md9_raid1(252): WRITE block 1060216 on sda1 (1 sectors)
<7>[10340.167354] md9_raid1(252): WRITE block 1060232 on sda1 (1 sectors)
<7>[10340.390476] md9_raid1(252): WRITE block 1060216 on sda1 (1 sectors)
<7>[10340.411905] md9_raid1(252): WRITE block 1060232 on sda1 (1 sectors)
<7>[10324.879506] md9_raid1(252): WRITE block 1060216 on sdb1 (1 sectors)
<7>[10324.912977] md9_raid1(252): WRITE block 1060232 on sdb1 (1 sectors)
<7>[10325.136586] md9_raid1(252): WRITE block 1060216 on sdb1 (1 sectors)
<7>[10325.157606] md9_raid1(252): WRITE block 1060232 on sdb1 (1 sectors)
<7>[10339.652010] md9_raid1(252): WRITE block 1060216 on sdb1 (1 sectors)
<7>[10340.167331] md9_raid1(252): WRITE block 1060232 on sdb1 (1 sectors)
<7>[10340.390454] md9_raid1(252): WRITE block 1060216 on sdb1 (1 sectors)
<7>[10340.411894] md9_raid1(252): WRITE block 1060232 on sdb1 (1 sectors)
============= 6/100 test, Mon Apr 6 09:48:27 CEST 2015 ===============
<7>[10580.561927] userConfig.cgi(23061): dirtied inode 20189 (config) on md9
<7>[10580.562149] userConfig.cgi(23061): dirtied inode 20055 (config.tmp) on md9
<7>[10586.052222] kjournald(262): WRITE block 868496 on md9 (8 sectors)
<7>[10586.052281] md9_raid1(252): WRITE block 1060216 on sdb1 (1 sectors)
<7>[10586.052357] md9_raid1(252): WRITE block 1060216 on sda1 (1 sectors)
<7>[10586.082031] md9_raid1(252): WRITE block 1060232 on sdb1 (1 sectors)
<7>[10586.082048] md9_raid1(252): WRITE block 1060232 on sda1 (1 sectors)
<7>[10586.130735] kjournald(262): WRITE block 868504 on md9 (8 sectors)
<7>[10586.131078] kjournald(262): WRITE block 547584 on md9 (8 sectors)
<7>[10586.131124] kjournald(262): WRITE block 547592 on md9 (8 sectors)
<7>[10586.131150] kjournald(262): WRITE block 547600 on md9 (8 sectors)
<7>[10586.131176] kjournald(262): WRITE block 547608 on md9 (8 sectors)
<7>[10586.131219] kjournald(262): WRITE block 547616 on md9 (8 sectors)
<7>[10586.131245] kjournald(262): WRITE block 547624 on md9 (8 sectors)
<7>[10586.131297] kjournald(262): WRITE block 547632 on md9 (8 sectors)
<7>[10586.131342] kjournald(262): WRITE block 547640 on md9 (8 sectors)
<7>[10586.131371] kjournald(262): WRITE block 547648 on md9 (8 sectors)
<7>[10586.131838] kjournald(262): WRITE block 547656 on md9 (8 sectors)
<7>[10586.332430] md9_raid1(252): WRITE block 1060216 on sdb1 (1 sectors)
<7>[10586.332477] md9_raid1(252): WRITE block 1060216 on sda1 (1 sectors)
<7>[10586.348908] md9_raid1(252): WRITE block 1060232 on sdb1 (1 sectors)
<7>[10586.348935] md9_raid1(252): WRITE block 1060232 on sda1 (1 sectors)
<7>[10600.605689] kworker/u4:2(72): WRITE block 786784 on md9 (8 sectors)
<7>[10600.605746] md9_raid1(252): WRITE block 1060216 on sdb1 (1 sectors)
<7>[10600.605824] md9_raid1(252): WRITE block 1060216 on sda1 (1 sectors)
<7>[10601.114012] md9_raid1(252): WRITE block 1060232 on sdb1 (1 sectors)
<7>[10601.114036] md9_raid1(252): WRITE block 1060232 on sda1 (1 sectors)
<7>[10601.136282] kworker/u4:2(72): WRITE block 786824 on md9 (8 sectors)
<7>[10601.136295] kworker/u4:2(72): WRITE block 786848 on md9 (8 sectors)
<7>[10601.136307] kworker/u4:2(72): WRITE block 934016 on md9 (8 sectors)
<7>[10601.136321] kworker/u4:2(72): WRITE block 0 on md9 (8 sectors)
<7>[10601.136332] kworker/u4:2(72): WRITE block 8 on md9 (8 sectors)
<7>[10601.136342] kworker/u4:2(72): WRITE block 786704 on md9 (8 sectors)
<7>[10601.136351] kworker/u4:2(72): WRITE block 786712 on md9 (8 sectors)
<7>[10601.338157] md9_raid1(252): WRITE block 1060216 on sdb1 (1 sectors)
<7>[10601.338171] md9_raid1(252): WRITE block 1060216 on sda1 (1 sectors)
<7>[10601.358582] md9_raid1(252): WRITE block 1060232 on sdb1 (1 sectors)
<7>[10601.358593] md9_raid1(252): WRITE block 1060232 on sda1 (1 sectors)
<7>[10586.052357] md9_raid1(252): WRITE block 1060216 on sda1 (1 sectors)
<7>[10586.082048] md9_raid1(252): WRITE block 1060232 on sda1 (1 sectors)
<7>[10586.332477] md9_raid1(252): WRITE block 1060216 on sda1 (1 sectors)
<7>[10586.348935] md9_raid1(252): WRITE block 1060232 on sda1 (1 sectors)
<7>[10600.605824] md9_raid1(252): WRITE block 1060216 on sda1 (1 sectors)
<7>[10601.114036] md9_raid1(252): WRITE block 1060232 on sda1 (1 sectors)
<7>[10601.338171] md9_raid1(252): WRITE block 1060216 on sda1 (1 sectors)
<7>[10601.358593] md9_raid1(252): WRITE block 1060232 on sda1 (1 sectors)
<7>[10586.052281] md9_raid1(252): WRITE block 1060216 on sdb1 (1 sectors)
<7>[10586.082031] md9_raid1(252): WRITE block 1060232 on sdb1 (1 sectors)
<7>[10586.332430] md9_raid1(252): WRITE block 1060216 on sdb1 (1 sectors)
<7>[10586.348908] md9_raid1(252): WRITE block 1060232 on sdb1 (1 sectors)
<7>[10600.605746] md9_raid1(252): WRITE block 1060216 on sdb1 (1 sectors)
<7>[10601.114012] md9_raid1(252): WRITE block 1060232 on sdb1 (1 sectors)
<7>[10601.338157] md9_raid1(252): WRITE block 1060216 on sdb1 (1 sectors)
<7>[10601.358582] md9_raid1(252): WRITE block 1060232 on sdb1 (1 sectors)Hi,
vielen Dank für das tolle Forum erstmal, ich habe schon beim lesen einige meiner Fragen klären können. Ich bin ein kompletter NAS-Newbie und taste mich momentan an alles neu ran. :oops:
Eine Sache macht mich aber total verrückt. Solange ich die Option bei Microsoft Netzwerk: "Datendienst für MS-Netzwerk aktivieren" mit der Unteroption "Eigenständiger Server" aktiviert habe gehen die beiden Festplatten(Raid1) nie in den Ruhezustand.
Wenn NFS-Dienst aktiviert ist klappt der Ruheszustand ohne Probleme, aber mein Windows 7 Prof hat keine NFS-Unterstützung.
Gibt es eine Möglichkeit MS Netzwerk zu betreiben und die Platten gehen trotzdem in den Ruhezustand?
Vielen Dank
chagall
p.s.: Log von Putty-Session anbei
Ich kämpfe immer noch mit dem Ruhezustand. Habe nun einmal probehalber den Webserver ausgeschaltet und protokolliert. Ich kann aber nichts auffälliges entdecken oder habe ich was übersehen?
Zitat von "Smellwell"weiß jemand woran das liegen könnte?
Hast du eventuell ein iSCSI Laufwerk eingerichtet? Ist eines deiner Volumes ein flexibles Volume?
Zitat von "chagall"Gibt es eine Möglichkeit MS Netzwerk zu betreiben und die Platten gehen trotzdem in den Ruhezustand?
Ja, siehe mein Test zwei Beiträge über deinem. Du solltest herausfinden, welcher deiner Clients ständig Anfragen an dein NAS stellt.
Zitat von "RainerBegeistert"Ich kann aber nichts auffälliges entdecken oder habe ich was übersehen?
Jup, Sambaanfragen an dein NAS bzw. aktiver WINS-Dienst (siehe erster Beitrag in diesem Thema). Weiters ist irgendein PHP-Log aktiv.