wergor
connoisseur de mimi
|
ich bekomme in den nächsten tagen 4x3tb platten, die in meinem homeserver als raid5 werkeln sollen. vorher will ich die aber noch durchchecken. aus zeitgründen würde ich gerne alle festplatten gleichzeitig checken. gibts da eine bessere möglichkeit, als 4 screen-sessions aufzumachen und dann über jede platte einen badblocks read-write test test zu fahren? die voraussichtlich mindestens 4 tage die der test braucht sind kein problem, länger als 1 woche sollts halt nicht dauern 
|
davebastard
Vinyl-Sammler
|
brauchst nichtmal screen dazu. einfach strg+z wenn der erste läuft, dann "bg" in der shell ausführen dann läufts im hintergrund. dann die nächste platte starten und wieder Strg+z und wieder "bg" usw. http://wiki.ubuntuusers.de/Shell/Prozesssteuerungmit "jobs" und "fg" kannst sie wieder in den vordergrund bringen usw. siehe wiki
|
wergor
connoisseur de mimi
|
brauchst nichtmal screen dazu. einfach strg+z wenn der erste läuft, dann "bg" in der shell ausführen dann läufts im hintergrund. dann die nächste platte starten und wieder Strg+z und wieder "bg" usw.
http://wiki.ubuntuusers.de/Shell/Prozesssteuerung
mit "jobs" und "fg" kannst sie wieder in den vordergrund bringen usw. siehe wiki das kannte ich noch gar nicht. thx
|
Ringding
Pilot
|
Trotzdem ist es wohl mit screen angenehmer, sonst kommt irgendein Output, und du weißt vielleicht nicht einmal, von welchem Job der nun kommt.
Generell ist das Verhalten teilweise sehr ungünstig, wenn der Hintergrundprozess irgendwas auf die Konsole schreibt. Unter Umständen (die ich noch nie durchschaut habe), geht er dann durch diese Schreiboperation von sich aus wieder in den Stop-Zustand zurück und tut nicht weiter.
|
davebastard
Vinyl-Sammler
|
Trotzdem ist es wohl mit screen angenehmer, sonst kommt irgendein Output, und du weißt vielleicht nicht einmal, von welchem Job der nun kommt. stimmt schon hier kann man schon screen auch verwenden. alternativ kannst die ausgabe in ein file umleiten. würd ich sowieso machen wenns so lang dauert.
|
COLOSSUS
AdministratorGNUltra
|
|
davebastard
Vinyl-Sammler
|
a reptyr klingt nice, sowas hätt ich schon öfter gebraucht
|
wergor
connoisseur de mimi
|
hab die tests gerade gestartet. ich hab screen benutzt - da kenne ich mich schon ein bissl aus trotzdem danke für die tipps, werde ich mir genauer anschauen.
|
COLOSSUS
AdministratorGNUltra
|
Ich kann uebrigens meine Version einer screenrc empfehlen - ist eines der ersten beiden Config-Files, die auf einen neuen Host kommen, wo ich mich haeuslich einrichte: http://johannes.truschnigg.info/assets/screenrc"Installieren" mit (z. B.): wget -O${HOME}/.screenrc http://johannes.truschnigg.info/assets/screenrc
|
wergor
connoisseur de mimi
|
kann mir jemand erklären was diese logeinträge genau bedeuten? Sep 7 03:53:50 localhost kernel: ata5: limiting SATA link speed to 3.0 Gbps
Sep 7 03:53:50 localhost kernel: ata5.00: exception Emask 0x0 SAct 0x7fffffff SErr 0x400000 action 0x6 frozen
Sep 7 03:53:50 localhost kernel: ata5: SError: { Handshk }
Sep 7 03:53:50 localhost kernel: ata5.00: failed command: READ FPDMA QUEUED
Sep 7 03:53:50 localhost kernel: ata5.00: cmd 60/08:00:08:c3:0f/00:00:00:00:00/40 tag 0 ncq 4096 in
Sep 7 03:53:50 localhost kernel: res 40/00:08:00:7c:68/00:00:01:00:00/40 Emask 0x4 (timeout)
Sep 7 03:53:50 localhost kernel: ata5.00: status: { DRDY }
Sep 7 03:53:50 localhost kernel: ata5.00: failed command: READ FPDMA QUEUED
Sep 7 03:53:50 localhost kernel: ata5.00: cmd 60/08:08:10:c3:0f/00:00:00:00:00/40 tag 1 ncq 4096 in
Sep 7 03:53:50 localhost kernel: res 40/00:08:00:7c:68/00:00:01:00:00/40 Emask 0x4 (timeout)
Sep 7 03:53:50 localhost kernel: ata5.00: status: { DRDY }
Sep 7 03:53:50 localhost kernel: ata5.00: failed command: READ FPDMA QUEUED
Sep 7 03:53:50 localhost kernel: ata5.00: cmd 60/08:10:18:c3:0f/00:00:00:00:00/40 tag 2 ncq 4096 in
Sep 7 03:53:50 localhost kernel: res 40/00:08:00:7c:68/00:00:01:00:00/40 Emask 0x4 (timeout)
Sep 7 03:53:50 localhost kernel: ata5.00: status: { DRDY }
Sep 7 03:53:50 localhost kernel: ata5.00: failed command: READ FPDMA QUEUED
Sep 7 03:53:50 localhost kernel: ata5.00: cmd 60/08:18:20:c3:0f/00:00:00:00:00/40 tag 3 ncq 4096 in
Sep 7 03:53:50 localhost kernel: res 40/00:08:00:7c:68/00:00:01:00:00/40 Emask 0x4 (timeout)
Sep 7 03:53:50 localhost kernel: ata5.00: status: { DRDY }
Sep 7 03:53:50 localhost kernel: ata5.00: failed command: READ FPDMA QUEUED
Sep 7 03:53:50 localhost kernel: ata5.00: cmd 60/08:20:28:c3:0f/00:00:00:00:00/40 tag 4 ncq 4096 in
Sep 7 03:53:50 localhost kernel: res 40/00:60:38:c6:db/00:00:00:00:00/40 Emask 0x4 (timeout)
Sep 7 03:53:50 localhost kernel: ata5.00: status: { DRDY }
Sep 7 03:53:50 localhost kernel: ata5.00: failed command: READ FPDMA QUEUED
Sep 7 03:53:50 localhost kernel: ata5.00: cmd 60/08:28:38:c3:0f/00:00:00:00:00/40 tag 5 ncq 4096 in
Sep 7 03:53:50 localhost kernel: res 40/00:60:38:c6:db/00:00:00:00:00/40 Emask 0x4 (timeout)
Sep 7 03:53:50 localhost kernel: ata5.00: status: { DRDY }
Sep 7 03:53:50 localhost kernel: ata5.00: failed command: READ FPDMA QUEUED
Sep 7 03:53:50 localhost kernel: ata5.00: cmd 60/08:30:40:c3:0f/00:00:00:00:00/40 tag 6 ncq 4096 in
Sep 7 03:53:50 localhost kernel: res 40/00:38:30:de:77/00:00:02:00:00/40 Emask 0x4 (timeout)
Sep 7 03:53:50 localhost kernel: ata5.00: status: { DRDY }
Sep 7 03:53:50 localhost kernel: ata5.00: failed command: READ FPDMA QUEUED
Sep 7 03:53:50 localhost kernel: ata5.00: cmd 60/08:38:48:c3:0f/00:00:00:00:00/40 tag 7 ncq 4096 in
Sep 7 03:53:50 localhost kernel: res 40/00:38:30:de:77/00:00:02:00:00/40 Emask 0x4 (timeout)
Sep 7 03:53:50 localhost kernel: ata5.00: status: { DRDY }
Sep 7 03:53:50 localhost kernel: ata5.00: failed command: READ FPDMA QUEUED
Sep 7 03:53:50 localhost kernel: ata5.00: cmd 60/08:40:50:c3:0f/00:00:00:00:00/40 tag 8 ncq 4096 in
Sep 7 03:53:50 localhost kernel: res 40/00:50:c8:71:62/00:00:01:00:00/40 Emask 0x4 (timeout)
Sep 7 03:53:50 localhost kernel: ata5.00: status: { DRDY }
Sep 7 03:53:50 localhost kernel: ata5.00: failed command: READ FPDMA QUEUED
Sep 7 03:53:50 localhost kernel: ata5.00: cmd 60/08:48:58:c3:0f/00:00:00:00:00/40 tag 9 ncq 4096 in
Sep 7 03:53:50 localhost kernel: res 40/00:50:c8:71:62/00:00:01:00:00/40 Emask 0x4 (timeout)
Sep 7 03:53:50 localhost kernel: ata5.00: status: { DRDY }
Sep 7 03:53:50 localhost kernel: ata5.00: failed command: READ FPDMA QUEUED
Sep 7 03:53:50 localhost kernel: ata5.00: cmd 60/08:50:60:c3:0f/00:00:00:00:00/40 tag 10 ncq 4096 in
Sep 7 03:53:50 localhost kernel: res 40/00:50:c8:71:62/00:00:01:00:00/40 Emask 0x4 (timeout)
Sep 7 03:53:50 localhost kernel: ata5.00: status: { DRDY }
Sep 7 03:53:50 localhost kernel: ata5.00: failed command: READ FPDMA QUEUED
Sep 7 03:53:50 localhost kernel: ata5.00: cmd 60/08:58:68:c3:0f/00:00:00:00:00/40 tag 11 ncq 4096 in
Sep 7 03:53:50 localhost kernel: res 40/00:48:58:76:da/00:00:00:00:00/40 Emask 0x4 (timeout)
Sep 7 03:53:50 localhost kernel: ata5.00: status: { DRDY }
Sep 7 03:53:50 localhost kernel: ata5.00: failed command: READ FPDMA QUEUED
Sep 7 03:53:50 localhost kernel: ata5.00: cmd 60/08:60:70:c3:0f/00:00:00:00:00/40 tag 12 ncq 4096 in
Sep 7 03:53:50 localhost kernel: res 40/00:48:58:76:da/00:00:00:00:00/40 Emask 0x4 (timeout)
Sep 7 03:53:50 localhost kernel: ata5.00: status: { DRDY }
Sep 7 03:53:50 localhost kernel: ata5.00: failed command: READ FPDMA QUEUED
Sep 7 03:53:50 localhost kernel: ata5.00: cmd 60/08:68:78:c3:0f/00:00:00:00:00/40 tag 13 ncq 4096 in
Sep 7 03:53:50 localhost kernel: res 40/00:18:a8:46:79/00:00:02:00:00/40 Emask 0x4 (timeout)
Sep 7 03:53:50 localhost kernel: ata5.00: status: { DRDY }
Sep 7 03:53:50 localhost kernel: ata5.00: failed command: READ FPDMA QUEUED
Sep 7 03:53:50 localhost kernel: ata5.00: cmd 60/08:70:80:c3:0f/00:00:00:00:00/40 tag 14 ncq 4096 in
Sep 7 03:53:50 localhost kernel: res 40/00:18:a8:46:79/00:00:02:00:00/40 Emask 0x4 (timeout)
Sep 7 03:53:50 localhost kernel: ata5.00: status: { DRDY }
Sep 7 03:53:50 localhost kernel: ata5.00: failed command: READ FPDMA QUEUED
Sep 7 03:53:50 localhost kernel: ata5.00: cmd 60/08:78:88:c3:0f/00:00:00:00:00/40 tag 15 ncq 4096 in
Sep 7 03:53:50 localhost kernel: res 40/00:18:a8:46:79/00:00:02:00:00/40 Emask 0x4 (timeout)
Sep 7 03:53:50 localhost kernel: ata5.00: status: { DRDY }
Sep 7 03:53:50 localhost kernel: ata5.00: failed command: READ FPDMA QUEUED
Sep 7 03:53:50 localhost kernel: ata5.00: cmd 60/08:80:90:c3:0f/00:00:00:00:00/40 tag 16 ncq 4096 in
Sep 7 03:53:50 localhost kernel: res 40/00:18:a8:46:79/00:00:02:00:00/40 Emask 0x4 (timeout)
Sep 7 03:53:50 localhost kernel: ata5.00: status: { DRDY }
Sep 7 03:53:50 localhost kernel: ata5.00: failed command: READ FPDMA QUEUED
Sep 7 03:53:50 localhost kernel: ata5.00: cmd 60/08:88:98:c3:0f/00:00:00:00:00/40 tag 17 ncq 4096 in
Sep 7 03:53:50 localhost kernel: res 40/00:18:a8:46:79/00:00:02:00:00/40 Emask 0x4 (timeout)
Sep 7 03:53:50 localhost kernel: ata5.00: status: { DRDY }
Sep 7 03:53:50 localhost kernel: ata5.00: failed command: READ FPDMA QUEUED
Sep 7 03:53:50 localhost kernel: ata5.00: cmd 60/08:90:a0:c3:0f/00:00:00:00:00/40 tag 18 ncq 4096 in
Sep 7 03:53:50 localhost kernel: res 40/00:18:a8:46:79/00:00:02:00:00/40 Emask 0x4 (timeout)
Sep 7 03:53:50 localhost kernel: ata5.00: status: { DRDY }
Sep 7 03:53:50 localhost kernel: ata5.00: failed command: READ FPDMA QUEUED
Sep 7 03:53:50 localhost kernel: ata5.00: cmd 60/08:98:a8:c3:0f/00:00:00:00:00/40 tag 19 ncq 4096 in
Sep 7 03:53:50 localhost kernel: res 40/00:b0:00:04:68/00:00:01:00:00/40 Emask 0x4 (timeout)
Sep 7 03:53:50 localhost kernel: ata5.00: status: { DRDY }
Sep 7 03:53:50 localhost kernel: ata5.00: failed command: READ FPDMA QUEUED
Sep 7 03:53:50 localhost kernel: ata5.00: cmd 60/08:a0:b0:c3:0f/00:00:00:00:00/40 tag 20 ncq 4096 in
Sep 7 03:53:50 localhost kernel: res 40/00:b0:00:04:68/00:00:01:00:00/40 Emask 0x4 (timeout)
Sep 7 03:53:50 localhost kernel: ata5.00: status: { DRDY }
Sep 7 03:53:50 localhost kernel: ata5.00: failed command: READ FPDMA QUEUED
Sep 7 03:53:50 localhost kernel: ata5.00: cmd 60/08:a8:b8:c3:0f/00:00:00:00:00/40 tag 21 ncq 4096 in
Sep 7 03:53:50 localhost kernel: res 40/00:b0:00:04:68/00:00:01:00:00/40 Emask 0x4 (timeout)
Sep 7 03:53:50 localhost kernel: ata5.00: status: { DRDY }
Sep 7 03:53:50 localhost kernel: ata5.00: failed command: READ FPDMA QUEUED
Sep 7 03:53:50 localhost kernel: ata5.00: cmd 60/08:b0:c0:c3:0f/00:00:00:00:00/40 tag 22 ncq 4096 in
Sep 7 03:53:50 localhost kernel: res 40/00:b0:00:04:68/00:00:01:00:00/40 Emask 0x4 (timeout)
Sep 7 03:53:50 localhost kernel: ata5.00: status: { DRDY }
Sep 7 03:53:50 localhost kernel: ata5.00: failed command: READ FPDMA QUEUED
Sep 7 03:53:50 localhost kernel: ata5.00: cmd 60/08:b8:c8:c3:0f/00:00:00:00:00/40 tag 23 ncq 4096 in
Sep 7 03:53:50 localhost kernel: res 40/00:18:a8:46:79/00:00:02:00:00/40 Emask 0x4 (timeout)
Sep 7 03:53:50 localhost kernel: ata5.00: status: { DRDY }
Sep 7 03:53:50 localhost kernel: ata5.00: failed command: READ FPDMA QUEUED
Sep 7 03:53:50 localhost kernel: ata5.00: cmd 60/08:c0:d0:c3:0f/00:00:00:00:00/40 tag 24 ncq 4096 in
Sep 7 03:53:50 localhost kernel: res 40/00:18:a8:46:79/00:00:02:00:00/40 Emask 0x4 (timeout)
Sep 7 03:53:50 localhost kernel: ata5.00: status: { DRDY }
Sep 7 03:53:50 localhost kernel: ata5.00: failed command: READ FPDMA QUEUED
Sep 7 03:53:50 localhost kernel: ata5.00: cmd 60/08:c8:d8:c3:0f/00:00:00:00:00/40 tag 25 ncq 4096 in
Sep 7 03:53:50 localhost kernel: res 40/00:18:a8:46:79/00:00:02:00:00/40 Emask 0x4 (timeout)
Sep 7 03:53:50 localhost kernel: ata5.00: status: { DRDY }
Sep 7 03:53:50 localhost kernel: ata5.00: failed command: READ FPDMA QUEUED
Sep 7 03:53:50 localhost kernel: ata5.00: cmd 60/08:d0:e0:c3:0f/00:00:00:00:00/40 tag 26 ncq 4096 in
Sep 7 03:53:50 localhost kernel: res 40/00:18:a8:46:79/00:00:02:00:00/40 Emask 0x4 (timeout)
Sep 7 03:53:50 localhost kernel: ata5.00: status: { DRDY }
Sep 7 03:53:50 localhost kernel: ata5.00: failed command: READ FPDMA QUEUED
Sep 7 03:53:50 localhost kernel: ata5.00: cmd 60/08:d8:e8:c3:0f/00:00:00:00:00/40 tag 27 ncq 4096 in
Sep 7 03:53:50 localhost kernel: res 40/00:18:a8:46:79/00:00:02:00:00/40 Emask 0x4 (timeout)
Sep 7 03:53:50 localhost kernel: ata5.00: status: { DRDY }
Sep 7 03:53:50 localhost kernel: ata5.00: failed command: READ FPDMA QUEUED
Sep 7 03:53:50 localhost kernel: ata5.00: cmd 60/08:e0:f0:c3:0f/00:00:00:00:00/40 tag 28 ncq 4096 in
Sep 7 03:53:50 localhost kernel: res 40/00:18:a8:46:79/00:00:02:00:00/40 Emask 0x4 (timeout)
Sep 7 03:53:50 localhost kernel: ata5.00: status: { DRDY }
Sep 7 03:53:50 localhost kernel: ata5.00: failed command: READ FPDMA QUEUED
Sep 7 03:53:50 localhost kernel: ata5.00: cmd 60/08:e8:f8:c3:0f/00:00:00:00:00/40 tag 29 ncq 4096 in
Sep 7 03:53:50 localhost kernel: res 40/00:18:a8:46:79/00:00:02:00:00/40 Emask 0x4 (timeout)
Sep 7 03:53:50 localhost kernel: ata5.00: status: { DRDY }
Sep 7 03:53:50 localhost kernel: ata5.00: failed command: READ FPDMA QUEUED
Sep 7 03:53:50 localhost kernel: ata5.00: cmd 60/08:f0:30:c3:0f/00:00:00:00:00/40 tag 30 ncq 4096 in
Sep 7 03:53:50 localhost kernel: res 40/00:18:a8:46:79/00:00:02:00:00/40 Emask 0x4 (timeout)
Sep 7 03:53:50 localhost kernel: ata5.00: status: { DRDY }
Sep 7 03:53:50 localhost kernel: ata5: hard resetting link
Sep 7 03:53:51 localhost kernel: ata5: SATA link up 3.0 Gbps (SStatus 123 SControl 320)
Sep 7 03:53:51 localhost kernel: ata5.00: configured for UDMA/100
Sep 7 03:53:51 localhost kernel: sd 4:0:0:0: [sde] Result: hostbyte=DID_OK driverbyte=DRIVER_SENSE
Sep 7 03:53:51 localhost kernel: sd 4:0:0:0: [sde] Sense Key : Aborted Command [current] [descriptor]
Sep 7 03:53:51 localhost kernel: Descriptor sense data with sense descriptors (in hex):
Sep 7 03:53:51 localhost kernel: 72 0b 00 00 00 00 00 0c 00 0a 80 00 00 00 00 00
Sep 7 03:53:51 localhost kernel: 01 68 7c 00
Sep 7 03:53:51 localhost kernel: sd 4:0:0:0: [sde] Add. Sense: No additional sense information
Sep 7 03:53:51 localhost kernel: sd 4:0:0:0: [sde] CDB: Read(10): 28 00 00 0f c3 08 00 00 08 00
Sep 7 03:53:51 localhost kernel: sd 4:0:0:0: [sde] Result: hostbyte=DID_OK driverbyte=DRIVER_SENSE
Sep 7 03:53:51 localhost kernel: sd 4:0:0:0: [sde] Sense Key : Aborted Command [current] [descriptor]
Sep 7 03:53:51 localhost kernel: Descriptor sense data with sense descriptors (in hex):
Sep 7 03:53:51 localhost kernel: 72 0b 00 00 00 00 00 0c 00 0a 80 00 00 00 00 00
Sep 7 03:53:51 localhost kernel: 01 68 7c 00
Sep 7 03:53:51 localhost kernel: sd 4:0:0:0: [sde] Add. Sense: No additional sense information
Sep 7 03:53:51 localhost kernel: sd 4:0:0:0: [sde] CDB: Read(10): 28 00 00 0f c3 10 00 00 08 00
Sep 7 03:53:51 localhost kernel: sd 4:0:0:0: [sde] Result: hostbyte=DID_OK driverbyte=DRIVER_SENSE
Sep 7 03:53:51 localhost kernel: sd 4:0:0:0: [sde] Sense Key : Aborted Command [current] [descriptor]
Sep 7 03:53:51 localhost kernel: Descriptor sense data with sense descriptors (in hex):
Sep 7 03:53:51 localhost kernel: 72 0b 00 00 00 00 00 0c 00 0a 80 00 00 00 00 00
Sep 7 03:53:51 localhost kernel: 01 68 7c 00
Sep 7 03:53:51 localhost kernel: sd 4:0:0:0: [sde] Add. Sense: No additional sense information
Sep 7 03:53:51 localhost kernel: sd 4:0:0:0: [sde] CDB: Read(10): 28 00 00 0f c3 18 00 00 08 00
Sep 7 03:53:51 localhost kernel: sd 4:0:0:0: [sde] Result: hostbyte=DID_OK driverbyte=DRIVER_SENSE
Sep 7 03:53:51 localhost kernel: sd 4:0:0:0: [sde] Sense Key : Aborted Command [current] [descriptor]
Sep 7 03:53:51 localhost kernel: Descriptor sense data with sense descriptors (in hex):
Sep 7 03:53:51 localhost kernel: 72 0b 00 00 00 00 00 0c 00 0a 80 00 00 00 00 00
Sep 7 03:53:51 localhost kernel: 01 68 7c 00
Sep 7 03:53:51 localhost kernel: sd 4:0:0:0: [sde] Add. Sense: No additional sense information
Sep 7 03:53:51 localhost kernel: sd 4:0:0:0: [sde] CDB: Read(10): 28 00 00 0f c3 20 00 00 08 00
Sep 7 03:53:51 localhost kernel: sd 4:0:0:0: [sde] Result: hostbyte=DID_OK driverbyte=DRIVER_SENSE
Sep 7 03:53:51 localhost kernel: sd 4:0:0:0: [sde] Sense Key : Aborted Command [current] [descriptor]
Sep 7 03:53:51 localhost kernel: Descriptor sense data with sense descriptors (in hex):
Sep 7 03:53:51 localhost kernel: 72 0b 00 00 00 00 00 0c 00 0a 80 00 00 00 00 00
Sep 7 03:53:51 localhost kernel: 00 db c6 38
Sep 7 03:53:51 localhost kernel: sd 4:0:0:0: [sde] Add. Sense: No additional sense information
Sep 7 03:53:51 localhost kernel: sd 4:0:0:0: [sde] CDB: Read(10): 28 00 00 0f c3 28 00 00 08 00
Sep 7 03:53:51 localhost kernel: sd 4:0:0:0: [sde] Result: hostbyte=DID_OK driverbyte=DRIVER_SENSE
Sep 7 03:53:51 localhost kernel: sd 4:0:0:0: [sde] Sense Key : Aborted Command [current] [descriptor]
Sep 7 03:53:51 localhost kernel: Descriptor sense data with sense descriptors (in hex):
Sep 7 03:53:51 localhost kernel: 72 0b 00 00 00 00 00 0c 00 0a 80 00 00 00 00 00
Sep 7 03:53:51 localhost kernel: 00 db c6 38
Sep 7 03:53:51 localhost kernel: sd 4:0:0:0: [sde] Add. Sense: No additional sense information
Sep 7 03:53:51 localhost kernel: sd 4:0:0:0: [sde] CDB: Read(10): 28 00 00 0f c3 38 00 00 08 00
Sep 7 03:53:51 localhost kernel: sd 4:0:0:0: [sde] Result: hostbyte=DID_OK driverbyte=DRIVER_SENSE
Sep 7 03:53:51 localhost kernel: sd 4:0:0:0: [sde] Sense Key : Aborted Command [current] [descriptor]
Sep 7 03:53:51 localhost kernel: Descriptor sense data with sense descriptors (in hex):
Sep 7 03:53:51 localhost kernel: 72 0b 00 00 00 00 00 0c 00 0a 80 00 00 00 00 00
Sep 7 03:53:51 localhost kernel: 02 77 de 30
Sep 7 03:53:51 localhost kernel: sd 4:0:0:0: [sde] Add. Sense: No additional sense information
Sep 7 03:53:51 localhost kernel: sd 4:0:0:0: [sde] CDB: Read(10): 28 00 00 0f c3 40 00 00 08 00
Sep 7 03:53:51 localhost kernel: sd 4:0:0:0: [sde] Result: hostbyte=DID_OK driverbyte=DRIVER_SENSE
Sep 7 03:53:51 localhost kernel: sd 4:0:0:0: [sde] Sense Key : Aborted Command [current] [descriptor]
Sep 7 03:53:51 localhost kernel: Descriptor sense data with sense descriptors (in hex):
Sep 7 03:53:51 localhost kernel: 72 0b 00 00 00 00 00 0c 00 0a 80 00 00 00 00 00
Sep 7 03:53:51 localhost kernel: 02 77 de 30
Sep 7 03:53:51 localhost kernel: sd 4:0:0:0: [sde] Add. Sense: No additional sense information
Sep 7 03:53:51 localhost kernel: sd 4:0:0:0: [sde] CDB: Read(10): 28 00 00 0f c3 48 00 00 08 00
Sep 7 03:53:51 localhost kernel: sd 4:0:0:0: [sde] Result: hostbyte=DID_OK driverbyte=DRIVER_SENSE
Sep 7 03:53:51 localhost kernel: sd 4:0:0:0: [sde] Sense Key : Aborted Command [current] [descriptor]
Sep 7 03:53:51 localhost kernel: Descriptor sense data with sense descriptors (in hex):
Sep 7 03:53:51 localhost kernel: 72 0b 00 00 00 00 00 0c 00 0a 80 00 00 00 00 00
Sep 7 03:53:51 localhost kernel: 01 62 71 c8
Sep 7 03:53:51 localhost kernel: sd 4:0:0:0: [sde] Add. Sense: No additional sense information
Sep 7 03:53:51 localhost kernel: sd 4:0:0:0: [sde] CDB: Read(10): 28 00 00 0f c3 50 00 00 08 00
Sep 7 03:53:51 localhost kernel: sd 4:0:0:0: [sde] Result: hostbyte=DID_OK driverbyte=DRIVER_SENSE
Sep 7 03:53:51 localhost kernel: sd 4:0:0:0: [sde] Sense Key : Aborted Command [current] [descriptor]
Sep 7 03:53:51 localhost kernel: Descriptor sense data with sense descriptors (in hex):
Sep 7 03:53:51 localhost kernel: 72 0b 00 00 00 00 00 0c 00 0a 80 00 00 00 00 00
Sep 7 03:53:51 localhost kernel: 01 62 71 c8
Sep 7 03:53:51 localhost kernel: sd 4:0:0:0: [sde] Add. Sense: No additional sense information
Sep 7 03:53:51 localhost kernel: sd 4:0:0:0: [sde] CDB: Read(10): 28 00 00 0f c3 58 00 00 08 00
Sep 7 03:53:51 localhost kernel: end_request: I/O error, dev sde, sector 1033056
Sep 7 03:53:51 localhost kernel: end_request: I/O error, dev sde, sector 1033064
Sep 7 03:53:51 localhost kernel: end_request: I/O error, dev sde, sector 1033072
Sep 7 03:53:51 localhost kernel: end_request: I/O error, dev sde, sector 1033080
Sep 7 03:53:51 localhost kernel: end_request: I/O error, dev sde, sector 1033088
Sep 7 03:53:51 localhost kernel: end_request: I/O error, dev sde, sector 1033096
Sep 7 03:53:51 localhost kernel: end_request: I/O error, dev sde, sector 1033104
Sep 7 03:53:51 localhost kernel: end_request: I/O error, dev sde, sector 1033112
Sep 7 03:53:51 localhost kernel: end_request: I/O error, dev sde, sector 1033120
Sep 7 03:53:51 localhost kernel: end_request: I/O error, dev sde, sector 1033128
Sep 7 03:53:51 localhost kernel: end_request: I/O error, dev sde, sector 1033136
Sep 7 03:53:51 localhost kernel: end_request: I/O error, dev sde, sector 1033144
Sep 7 03:53:51 localhost kernel: end_request: I/O error, dev sde, sector 1033152
Sep 7 03:53:51 localhost kernel: end_request: I/O error, dev sde, sector 1033160
Sep 7 03:53:51 localhost kernel: end_request: I/O error, dev sde, sector 1033168
Sep 7 03:53:51 localhost kernel: end_request: I/O error, dev sde, sector 1033176
Sep 7 03:53:51 localhost kernel: end_request: I/O error, dev sde, sector 1033184
Sep 7 03:53:51 localhost kernel: end_request: I/O error, dev sde, sector 1033192
Sep 7 03:53:51 localhost kernel: end_request: I/O error, dev sde, sector 1033200
Sep 7 03:53:51 localhost kernel: end_request: I/O error, dev sde, sector 1033208
Sep 7 03:53:51 localhost kernel: ata5: EH complete
Sep 7 03:54:21 localhost kernel: ata5.00: exception Emask 0x0 SAct 0x6 SErr 0x0 action 0x6 frozen
Sep 7 03:54:21 localhost kernel: ata5.00: failed command: WRITE FPDMA QUEUED
Sep 7 03:54:21 localhost kernel: ata5.00: cmd 61/08:08:c8:f2:54/00:00:00:00:00/40 tag 1 ncq 4096 out
Sep 7 03:54:21 localhost kernel: res 40/00:08:00:7c:68/00:00:01:00:00/40 Emask 0x4 (timeout)
Sep 7 03:54:21 localhost kernel: ata5.00: status: { DRDY }
Sep 7 03:54:21 localhost kernel: ata5.00: failed command: WRITE FPDMA QUEUED
Sep 7 03:54:21 localhost kernel: ata5.00: cmd 61/10:10:d0:f2:54/00:00:00:00:00/40 tag 2 ncq 8192 out
Sep 7 03:54:21 localhost kernel: res 40/00:08:00:7c:68/00:00:01:00:00/40 Emask 0x4 (timeout)
Sep 7 03:54:21 localhost kernel: ata5.00: status: { DRDY }
Sep 7 03:54:21 localhost kernel: ata5: hard resetting link
Sep 7 03:54:22 localhost kernel: ata5: SATA link up 3.0 Gbps (SStatus 123 SControl 320)
Sep 7 03:54:22 localhost kernel: ata5.00: configured for UDMA/100
Sep 7 03:54:22 localhost kernel: ata5: EH complete
waren in meiner /var/log/messages. dev sde ist meine ssd mit dem os. edit: noch mehr logs- ähnliche fehler wie bei der ssd hatte ich auch nach dem ersten boot mit den neuen festplatten.
|
davebastard
Vinyl-Sammler
|
die IO error schauen ned gut aus.
würd mal mittels "smartctl" die smart gesundheitszustandsinfos anzeigen lassen.
unter debian/ubuntu heißt das paket wo "smartctl" drinnen ist "smartmontools". eventuell heißt es bei centos eh genauso oder ähnlich. musst selber schauen.
dann "smartctl -H /dev/sde" als root ausführen
|
wergor
connoisseur de mimi
|
die ssd: [root@localhost /]# smartctl -a /dev/sde
smartctl 5.43 2012-06-30 r3573 [x86_64-linux-2.6.32-358.18.1.el6.x86_64] (local build)
Copyright (C) 2002-12 by Bruce Allen, [url]http://smartmontools.sourceforge.net[/url]
=== START OF INFORMATION SECTION ===
Device Model: ADATA SP600
Serial Number: 03605083501000000083
Firmware Version: 2.2
User Capacity: 32,017,047,552 bytes [32.0 GB]
Sector Size: 512 bytes logical/physical
Device is: Not in smartctl database [for details use: -P showall]
ATA Version is: 8
ATA Standard is: ACS-2 (revision not indicated)
Local Time is: Sat Sep 7 13:17:23 2013 CEST
SMART support is: Available - device has SMART capability.
SMART support is: Enabled
=== START OF READ SMART DATA SECTION ===
SMART overall-health self-assessment test result: PASSED
General SMART Values:
Offline data collection status: (0x04) Offline data collection activity
was suspended by an interrupting command from host.
Auto Offline Data Collection: Disabled.
Self-test execution status: ( 0) The previous self-test routine completed
without error or no self-test has ever
been run.
Total time to complete Offline
data collection: ( 32) seconds.
Offline data collection
capabilities: (0x5b) SMART execute Offline immediate.
Auto Offline data collection on/off support.
Suspend Offline collection upon new
command.
Offline surface scan supported.
Self-test supported.
No Conveyance Self-test supported.
Selective Self-test supported.
SMART capabilities: (0x0003) Saves SMART data before entering
power-saving mode.
Supports SMART auto save timer.
Error logging capability: (0x01) Error logging supported.
General Purpose Logging supported.
Short self-test routine
recommended polling time: ( 1) minutes.
Extended self-test routine
recommended polling time: ( 1) minutes.
SCT capabilities: (0x0039) SCT Status supported.
SCT Error Recovery Control supported.
SCT Feature Control supported.
SCT Data Table supported.
SMART Attributes Data Structure revision number: 16
Vendor Specific SMART Attributes with Thresholds:
ID# ATTRIBUTE_NAME FLAG VALUE WORST THRESH TYPE UPDATED WHEN_FAILED RAW_VALUE
1 Raw_Read_Error_Rate 0x000a 100 100 000 Old_age Always - 0
2 Throughput_Performance 0x0005 100 100 050 Pre-fail Offline - 0
3 Spin_Up_Time 0x0007 100 100 050 Pre-fail Always - 0
5 Reallocated_Sector_Ct 0x0013 100 100 050 Pre-fail Always - 0
7 Seek_Error_Rate 0x000b 100 100 050 Pre-fail Always - 0
8 Seek_Time_Performance 0x0005 100 100 050 Pre-fail Offline - 0
9 Power_On_Hours 0x0012 100 100 000 Old_age Always - 758
10 Spin_Retry_Count 0x0013 100 100 050 Pre-fail Always - 0
12 Power_Cycle_Count 0x0012 100 100 000 Old_age Always - 22
167 Unknown_Attribute 0x0022 100 100 000 Old_age Always - 0
168 Unknown_Attribute 0x0012 100 100 000 Old_age Always - 0
169 Unknown_Attribute 0x0013 100 100 010 Pre-fail Always - 0
173 Unknown_Attribute 0x0012 198 198 000 Old_age Always - 0
175 Program_Fail_Count_Chip 0x0013 100 100 010 Pre-fail Always - 0
192 Power-Off_Retract_Count 0x0012 100 100 000 Old_age Always - 7
194 Temperature_Celsius 0x0023 059 059 030 Pre-fail Always - 41 (Min/Max 30/42)
197 Current_Pending_Sector 0x0012 100 100 000 Old_age Always - 0
240 Head_Flying_Hours 0x0013 100 100 050 Pre-fail Always - 0
243 Unknown_Attribute 0x0012 100 100 000 Old_age Always - 1002
SMART Error Log Version: 1
No Errors Logged
SMART Self-test log structure revision number 1
No self-tests have been logged. [To run self-tests, use: smartctl -t]
SMART Selective self-test log data structure revision number 1
SPAN MIN_LBA MAX_LBA CURRENT_TEST_STATUS
1 0 0 Not_testing
2 0 0 Not_testing
3 0 0 Not_testing
4 0 0 Not_testing
5 0 0 Not_testing
Selective self-test flags (0x0):
After scanning selected spans, do NOT read-scan remainder of disk.
If Selective self-test is pending on power-up, resume after 0 minute delay.
edit: die 4 festplatten: [root@localhost /]# smartctl -H /dev/sda
smartctl 5.43 2012-06-30 r3573 [x86_64-linux-2.6.32-358.18.1.el6.x86_64] (local build)
Copyright (C) 2002-12 by Bruce Allen, [url]http://smartmontools.sourceforge.net[/url]
=== START OF READ SMART DATA SECTION ===
SMART overall-health self-assessment test result: PASSED
[root@localhost /]# smartctl -H /dev/sdb
smartctl 5.43 2012-06-30 r3573 [x86_64-linux-2.6.32-358.18.1.el6.x86_64] (local build)
Copyright (C) 2002-12 by Bruce Allen, [url]http://smartmontools.sourceforge.net[/url]
=== START OF READ SMART DATA SECTION ===
SMART overall-health self-assessment test result: PASSED
[root@localhost /]# smartctl -H /dev/sdc
smartctl 5.43 2012-06-30 r3573 [x86_64-linux-2.6.32-358.18.1.el6.x86_64] (local build)
Copyright (C) 2002-12 by Bruce Allen, [url]http://smartmontools.sourceforge.net[/url]
=== START OF READ SMART DATA SECTION ===
SMART overall-health self-assessment test result: PASSED
[root@localhost /]# smartctl -H /dev/sdd
smartctl 5.43 2012-06-30 r3573 [x86_64-linux-2.6.32-358.18.1.el6.x86_64] (local build)
Copyright (C) 2002-12 by Bruce Allen, [url]http://smartmontools.sourceforge.net[/url]
=== START OF READ SMART DATA SECTION ===
SMART overall-health self-assessment test result: PASSED
badblocks läuft seit >26h mit den festplatten, 2. pass (von 4) fast fertig, bisher ohne fehler.
|
davebastard
Vinyl-Sammler
|
sry les ich jetzt ned wirklich was raus das weiterhilft. wenn man nach den fehlern googlet ist es bei den meisten, die das selbe problem hatten so dass ihre festplatten irgendwie defekt waren.
das hat sich dann aber auch in den smart werten abgezeichnet. was ja bei dir nicht der fall ist.
was du ohne viel aufwand probieren kannst ist das sata kabel der ssd tauschen.
edit: ok das zuletzt gepostete logfile ist interessant. demnach tritt es ja bei mehreren platten auf. das spricht eher für ein treiber bzw. softwareproblem mit dem sata controller.
Bearbeitet von davebastard am 09.09.2013, 11:11
|
wergor
connoisseur de mimi
|
ich glaube auch eher an ein problem mit dem controller oder dem treiber, nichtmal ich hab so viel pech dass von 5 neuen geräte 4 hin sind  badblocks ist auf allen festplatten fertig gelaufen, 0 fehler  edit: smart selftest (short) zeigt auch keine fehler.
|
davebastard
Vinyl-Sammler
|
welcher controller ist es und findet man dazu bugreports ? (kannst mit lspci bzw. dmesg|grep -i sata rausfinden)
|
Anmeldung