Den Beitrag hatte ich auch mal gelesen, deswegen hatte ich aufgegeben mich weiter darum zu kümmern. Und wahrscheinlich werden die es auch nicht fixen.
Beiträge von Smellwell
-
-
Traurig, finde ich auch. Bin kurz davor das Ding zu verkaufen. Mich ärgert es auch, dass Kodi nicht aktualisiert wird. Insgesamt gibt es einfach zu viele Bugs (VPN Client, Standby, Kodi, Youtube). Und das sind neben Datengrab nur die Funktionen, die ich benutze. Ich will nicht wissen wie die anderen 95% der Funktionen laufen. Wäre ein super NAS, wenn es einwandfrei liefe.
-
Was haltet Ihr von der Antwort? Ich habe die Frage an Qnap Taiwan auf englisch gestellt...
Zitat"Vielen Dank für Ihre Supportanfrage bei Qnap.
Wir bedauern, dass Ihr QNAP NAS nicht störungsfrei läuft.
Vermutlich ist die Installation der Firmware nicht richtig durchgelaufen oder es sind korrupte Systemdateien auf dem NAS.
Vorgehensweise:
Um die möglichen Fehlerquellen einzugrenzen, bitte die Kompatibilität der eingesetzten Hardware (Festplatten) auf unserer Kompatibilitätsliste, prüfen:3,5-Zoll https://www.qnap.com/i/de/prod…at_intro.php?g_cat=1&hf=0
2,5-Zoll https://www.qnap.com/i/de/prod…at_intro.php?g_cat=2&hf=0
SSD https://www.qnap.com/i/de/prod…at_intro.php?g_cat=3&hf=0
USB https://www.qnap.com/i/de/prod…at_intro.php?g_cat=4&hf=0Der Modelcode der Festplatten ist 10- bis 20-stellig. Die Liste für kompatible Festplatten ist in die Bereiche: "Business" und "Consumer" unterteilt. Weitere Details zu den einzelnen Modellen erhalten Sie zusätzlich auf den Internetseiten der Festplatten-Hersteller. Bitte beachten Sie auch die Fußnoten.
Sind die Festplatten inkompatibel, ist eine einwandfreie Funktion des QNAP-NAS nicht gewährleistet.
Bitte installieren Sie, um korrupten und defekten Systemdateien vorzubeugen, die Firmware des NAS neu.Die Firmware können Sie via QNAP-Finder aktualisieren.
Download(und entpacken): https://www.qnap.com/i/de/product_x_down/Führen Sie diesen Schritt auch durch, wenn bereits eine gleiche Firmware Version installiert ist.
Alle Systemeinstellungen Ihres NAS werden auf Default-Werte gesetzt. Ihre Daten bleiben hiervon unberührt.Wenn das oben genannte Vorgehen nicht erfolgreich ist, stellen Sie bitte folgendes vor dem nächsten Firmware Update sicher:
1. NAS rebooten, sicherstellen, dass das Verzeichnis /mnt/update Directory nicht existiert.
2. Sicherstellen, dass auf /dev/md9 mehr als 200 MB frei sind.Sollte dies nicht zum gewünschten Ergebnis führen, muss ein Firmware-Recovery durchgeführt werden. Informationen dazu finden Sie unter: http://wiki.qnap.com/wiki/Firmware_Recovery
Wir hoffen, wir konnten Ihnen helfen. "
-
Qnap Taiwan angeschrieben. Bin gespannt was die antworten.
-
Mensch antwortest Du schnell! Deine Vermutung schein richtig zu sein. Im Prinzip habe ich nachstehende Einträge.
Da Du jetzt schon das Problem eingegrenzt hast, kennst Du ein workaround, oder kannst Du mal eben ein Bios in Assembler oder Maschinensprache schreiben
Wem kann man das Problem bei Qnap schildern?
Code
Alles anzeigen2411.224775] hpet1: lost 9600 rtc interrupts [ 2414.246618] hpet_rtc_timer_reinit: 11 callbacks suppressed [ 2414.252101] hpet1: lost 9600 rtc interrupts [ 2414.522846] hpet1: lost 9599 rtc interrupts [ 2414.774632] hpet1: lost 9599 rtc interrupts [ 2415.025557] hpet1: lost 9599 rtc interrupts [ 2415.276261] hpet1: lost 9600 rtc interrupts [ 2415.546930] hpet1: lost 9599 rtc interrupts [ 2415.797647] hpet1: lost 9599 rtc interrupts [ 2416.048253] hpet1: lost 9600 rtc interrupts [ 2416.298860] hpet1: lost 9600 rtc interrupts [ 2416.569529] hpet1: lost 9599 rtc interrupts [ 2419.571656] hpet_rtc_timer_reinit: 11 callbacks suppressed [ 2419.577140] hpet1: lost 9600 rtc interrupts [ 2419.828496] hpet1: lost 9600 rtc interrupts [ 2420.079111] hpet1: lost 9600 rtc interrupts [ 2420.349766] hpet1: lost 9600 rtc interrupts [ 2420.600371] hpet1: lost 9600 rtc interrupts [ 2420.851428] hpet1: lost 9600 rtc interrupts [ 2421.102041] hpet1: lost 9600 rtc interrupts [ 2421.372699] hpet1: lost 9600 rtc interrupts [ 2421.623304] hpet1: lost 9600 rtc interrupts [ 2421.873923] hpet1: lost 9600 rtc interrupts [ 2424.898059] hpet_rtc_timer_reinit: 11 callbacks suppressed [ 2424.903542] hpet1: lost 9600 rtc interrupts [ 2425.154177] hpet1: lost 9600 rtc interrupts [ 2425.424838] hpet1: lost 9600 rtc interrupts [ 2425.675460] hpet1: lost 9600 rtc interrupts [ 2425.926164] hpet1: lost 9600 rtc interrupts [ 2426.176774] hpet1: lost 9600 rtc interrupts [ 2426.447418] hpet1: lost 9600 rtc interrupts [ 2426.698038] hpet1: lost 9600 rtc interrupts [ 2426.949005] hpet1: lost 9600 rtc interrupts [ 2427.199702] hpet1: lost 9600 rtc interrupts [ 2430.222197] hpet_rtc_timer_reinit: 11 callbacks suppressed [ 2430.227684] hpet1: lost 9600 rtc interrupts [ 2430.498356] hpet1: lost 9600 rtc interrupts [ 2430.749292] hpet1: lost 9600 rtc interrupts [ 2430.999991] hpet1: lost 9600 rtc interrupts [ 2431.250606] hpet1: lost 9600 rtc interrupts
-
Das müsste es eigentlich sein:
Code
Alles anzeigen/var$ dmesg [ 9.463968] sd 2:0:0:0: [sdc] Assuming drive cache: write through [ 9.476977] sd 2:0:0:0: [sdc] No Caching mode page found [ 9.482289] sd 2:0:0:0: [sdc] Assuming drive cache: write through [ 9.489845] sdc: sdc1 sdc2 sdc3 sdc4 < sdc5 sdc6 > [ 9.503523] sd 2:0:0:0: [sdc] No Caching mode page found [ 9.508838] sd 2:0:0:0: [sdc] Assuming drive cache: write through [ 9.514933] sd 2:0:0:0: [sdc] Attached SCSI removable disk [ 23.257311] usbcore: registered new interface driver usbserial [ 23.264680] usbcore: registered new interface driver pl2303 [ 23.270273] usbserial: USB Serial support registered for pl2303 [ 23.277558] jnl: driver (lke_9.2.0 QNAP, LBD=OFF) loaded at ffffffffa014e000 [ 23.286326] ufsd: module license 'Commercial product' taints kernel. [ 23.292703] Disabling lock debugging due to kernel taint [ 23.299076] ufsd: driver (lke_9.2.0 QNAP, build_host("BuildServer48-1"), acl, ioctl, bdi, sd2(0), fua, bz, rsrc) loaded at ffffffffa0159000 [ 23.299076] NTFS support included [ 23.299076] Hfs+/HfsJ support included [ 23.299076] optimized: speed [ 23.299076] Build_for__QNAP_TS-451_k3.12.6_2014-12-11_lke_9.2.0_r245986_b11 [ 23.299076] [ 23.419969] udevd (207): /proc/207/oom_adj is deprecated, please use /proc/207/oom_score_adj instead. [ 23.429238] udev: starting version 140 [ 23.466566] kjournald starting. Commit interval 5 seconds [ 23.472074] EXT3-fs (sda1): using internal journal [ 23.476879] EXT3-fs (sda1): mounted filesystem with ordered data mode [ 23.590800] kjournald starting. Commit interval 5 seconds [ 23.596310] EXT3-fs (sda1): using internal journal [ 23.601108] EXT3-fs (sda1): mounted filesystem with writeback data mode [ 24.165474] kjournald starting. Commit interval 5 seconds [ 24.170994] EXT3-fs (sdb1): using internal journal [ 24.175846] EXT3-fs (sdb1): mounted filesystem with writeback data mode [ 24.257714] md: md9 stopped. [ 24.261655] md: bind<sda1> [ 24.264527] md: bind<sdb1> [ 24.268187] md/raid1:md9: active with 2 out of 24 mirrors [ 24.273692] created bitmap (1 pages) for device md9 [ 24.278665] md9: bitmap initialized from disk: read 1 pages, set 9 of 9 bits [ 24.304055] md9: detected capacity change from 0 to 542769152 [ 25.321065] md9: unknown partition table [ 25.430810] kjournald starting. Commit interval 5 seconds [ 25.437986] EXT3-fs (md9): using internal journal [ 25.442697] EXT3-fs (md9): mounted filesystem with ordered data mode [ 25.620068] md: md13 stopped. [ 25.626238] md: bind<sda4> [ 25.629114] md: bind<sdb4> [ 25.632768] md/raid1:md13: active with 2 out of 24 mirrors [ 25.638360] created bitmap (1 pages) for device md13 [ 25.643543] md13: bitmap initialized from disk: read 1 pages, set 7 of 8 bits [ 25.700055] md13: detected capacity change from 0 to 469893120 [ 31.061173] md: bind<sdb2> [ 31.066360] md: bind<sda2> [ 31.069947] md/raid1:md256: not clean -- starting background reconstruction [ 31.076910] md/raid1:md256: active with 2 out of 2 mirrors [ 31.090776] created bitmap (1 pages) for device md256 [ 31.095937] md256: bitmap initialized from disk: read 1 pages, set 9 of 9 bits [ 31.116832] md256: detected capacity change from 0 to 542834688 [ 31.123002] md: resync of RAID array md256 [ 31.127112] md: minimum _guaranteed_ speed: 5000 KB/sec/disk. [ 31.132946] md: using maximum available idle IO bandwidth (but not more than 200000 KB/sec) for resync. [ 31.142339] md: Resyncing started: md256 [ 31.146273] md: using 128k window, over a total of 530112k. [ 31.171664] md256: unknown partition table [ 31.470937] Adding 530108k swap on /dev/md256. Priority:-1 extents:1 across:530108k [ 31.594716] md: md1 stopped. [ 31.605836] md: bind<sda3> [ 31.608686] md: bind<sdb3> [ 31.612196] md/raid0:md1: md_size is 3867230976 sectors. [ 31.617514] md: RAID0 configuration for md1 - 1 zone [ 31.622476] md: zone0=[sdb3/sda3] [ 31.625836] zone-offset= 0KB, device-offset= 0KB, size=1933615488KB [ 31.634005] [ 31.635507] md1: detected capacity change from 0 to 1980022259712 [ 31.647338] md1: unknown partition table [ 31.796871] md13: unknown partition table [ 32.985577] dm_create -1 [ 32.988131] mapped_device minor=0 [ 32.992185] dm_table_add_target start linear, start=0, len=38666240, param=9:1 2048, type=18446744071589634592... [ 33.002463] dm-linear: ti->max_io_len = 128 [ 33.006665] bio: create slab <bio-1> at 1 [ 33.011055] dm_create -1 [ 33.013602] mapped_device minor=1 [ 33.017254] dm_table_add_target start linear, start=0, len=3828555776, param=9:1 38668288, type=18446744071589634592... [ 33.028061] dm-linear: ti->max_io_len = 128 [ 34.106545] dm_create -1 [ 34.109089] mapped_device minor=0 [ 34.112733] dm_table_add_target start flashcache, start=0, len=3828555776, param=CG0 /dev/mapper/vg1-lv1 cachedev1, type=18446744072100156192... [ 34.766346] EXT4-fs (dm-0): Mount option "noacl" will be removed by 3.5 [ 34.766346] Contact linux-ext4@vger.kernel.org if you think we should keep it. [ 34.766346] [ 34.819839] ext4_init_reserve_inode_table0: dm-0, 14605 [ 34.825080] ext4_init_reserve_inode_table2: dm-0, 14605, 0, 0, 4096 [ 34.831391] EXT4-fs (dm-0): mounted filesystem with ordered data mode. Opts: usrjquota=aquota.user,jqfmt=vfsv0,user_xattr,data=ordered,delalloc,noacl [ 55.825703] kjournald starting. Commit interval 5 seconds [ 55.875435] EXT3-fs (md13): using internal journal [ 55.880230] EXT3-fs (md13): mounted filesystem with ordered data mode [ 65.678658] cryptodev: driver 0.9 loaded. [ 65.691244] iTCO_wdt: Intel TCO WatchDog Timer Driver v1.10 [ 65.696897] iTCO_wdt: Found a Baytrail SoC TCO device (Version=4, TCOBASE=0x0460) [ 65.704848] iTCO_wdt: initialized. heartbeat=120 sec (nowayout=0) [ 65.724596] fnotify: Load file notify kernel module. [ 65.729982] fnotify: Launch the fnotify thread: 18446612132963782848 [ 65.746289] iTCO_wdt: Timeout value (heartbeat) is set to 120 [ 66.772006] usbcore: registered new interface driver snd-usb-audio [ 66.779701] usbcore: registered new interface driver snd-usb-caiaq [ 66.791818] usbcore: registered new interface driver uvcvideo [ 66.797579] USB Video Class driver (1.1.1) [ 66.845572] 8021q: 802.1Q VLAN Support v1.8 [ 71.801286] md: md256: resync done. [ 71.804792] md: Resyncing done: md256 [ 71.909983] RAID1 conf printout: [ 71.909987] --- wd:2 rd:2 [ 71.909991] disk 0, wo:0, o:1, dev:sdb2 [ 71.909993] disk 1, wo:0, o:1, dev:sda2 [ 91.131559] EXT2-fs (sdc6): warning: mounting unchecked fs, running e2fsck is recommended [ 92.683957] 8021q: adding VLAN 0 to HW filter on device eth0 [ 92.931102] 8021q: adding VLAN 0 to HW filter on device eth1 [ 95.931711] igb: eth1 NIC Link is Up 100 Mbps Full Duplex, Flow Control: RX/TX [ 113.188943] igb: eth1 NIC Link is Up 100 Mbps Full Duplex, Flow Control: RX/TX [ 147.732762] EXT2-fs (sdc6): warning: mounting unchecked fs, running e2fsck is recommended [ 147.834856] rule type=2, num=0 [ 147.931462] Loading iSCSI transport class v2.0-870. [ 147.949326] iscsi: registered transport (tcp) [ 150.041040] hpet1: lost 9600 rtc interrupts [ 150.311980] hpet1: lost 9599 rtc interrupts [ 150.562703] hpet1: lost 9599 rtc interrupts [ 150.813311] hpet1: lost 9600 rtc interrupts [ 151.064204] hpet1: lost 9600 rtc interrupts [ 151.335609] hpet1: lost 9599 rtc interrupts [ 151.442131] tun: Universal TUN/TAP device driver, 1.6 [ 151.447204] tun: (C) 1999-2004 Max Krasnyansky <maxk@qualcomm.com> [ 151.484507] nf_conntrack version 0.5.0 (7146 buckets, 28584 max) [ 151.596210] hpet1: lost 9600 rtc interrupts [ 151.847134] hpet1: lost 9600 rtc interrupts
-
Das mit den ISCSI ist komisch. Nachstehend findest Du ein Screenshot meiner ISCSI Geräte (die nicht vorhanden sind).
Das NAS fahre ich per Zeitplan herunter.
Ich habe keinerlei Fehlermeldungen im Protokoll.
-
@ dr_mike :
Habe jetzt erst gesehen, dass Du mich etwas gefragt hattest. Hatte die Hoffnung schon aufgegeben....Keines meiner Laufwerke ist als ISCSI eingerichtet, der Dienst ist deaktiviert. Weiterhin habe ich kein flexibles Volumen.
Habe aber zwei unterschiedliche Platten je 1TB drin und als RAID0 laufen. Insgesamt sind schon 94% des Speichers belegt.Ich habe mich in englischen Foren durchgearbeitet und es schein ein Bug seitens Qnap zu sein. Veilleicht kennst Du ja ein work around etc.
@ Timer: Freut mich, dass wenigsten einer auch mein Problem hat. Hast Du schon mehr herausgefunden?
Gruß Smellwell
-
Wenn 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:
Code
Alles anzeigen============= 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)
-
Wirklich keiner? Ich kann bei mir das Problem jederzeit bestätigen. Erst nach einem Neustart gehen die Platten in den Standby.
-
Komisches Problem mal wieder mit dem Festplattenstandby. Wenn 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?