Disks werden gelockt (hostbyte=DID_BAD_TARGET driverbyte=DRIVER_OK)

T

tigger30926

New Member
Sep 22, 2021
10
0
1
50
Hallo in die Runde,
ich habe seit ein paar Wochen immer wieder das Problem das alle meine VM die
auf den Disk "sdf" und "sdg" liegen abstützen und dann die beiden Disks gelockt sind.

Die VMs booten dann ständig, aber finden kein Boot-Device mehr.
Erst wenn ich den Lock entferne und ProxMox einmal neu starte läuft alles wieder.

Hier mal ein keiner Auszug aus dem Syslog dazu:


Mar 10 03:32:33 proxmox kernel: ata9: hard resetting link
Mar 10 03:32:39 proxmox QEMU[41194]: qcow2_free_clusters failed: Input/output error
Mar 10 03:32:39 proxmox QEMU[41194]: qcow2_free_clusters failed: Input/output error
Mar 10 03:32:39 proxmox QEMU[41194]: qcow2_free_clusters failed: Input/output error
Mar 10 03:32:39 proxmox QEMU[41194]: qcow2_free_clusters failed: Input/output error
Mar 10 03:32:39 proxmox QEMU[41194]: qcow2_free_clusters failed: Input/output error
Mar 10 03:32:39 proxmox QEMU[41194]: qcow2_free_clusters failed: Input/output error
Mar 10 03:32:39 proxmox QEMU[41194]: qcow2_free_clusters failed: Input/output error
Mar 10 03:32:39 proxmox QEMU[41194]: qcow2_free_clusters failed: Input/output error
Mar 10 03:32:39 proxmox QEMU[41194]: qcow2_free_clusters failed: Input/output error
Mar 10 03:32:39 proxmox QEMU[41194]: qcow2_free_clusters failed: Input/output error
Mar 10 03:32:39 proxmox kernel: ata9: COMRESET failed (errno=-16)
Mar 10 03:32:39 proxmox kernel: ata9: reset failed, giving up
Mar 10 03:32:39 proxmox kernel: ata9.00: disabled
Mar 10 03:32:39 proxmox kernel: ata9: EH complete
Mar 10 03:32:39 proxmox kernel: sd 8:0:0:0: [sdf] tag#15 FAILED Result: hostbyte=DID_BAD_TARGET driverbyte=DRIVER_OK cmd_age=90s
Mar 10 03:32:39 proxmox kernel: sd 8:0:0:0: [sdf] tag#15 CDB: Write(10) 2a 00 11 c4 10 78 00 00 08 00
Mar 10 03:32:39 proxmox kernel: blk_update_request: I/O error, dev sdf, sector 298061944 op 0x1:(WRITE) flags 0x103000 phys_seg 1 prio class 0
Mar 10 03:32:39 proxmox kernel: Buffer I/O error on dev sdf, logical block 37257743, lost async page write
Mar 10 03:32:39 proxmox kernel: sd 8:0:0:0: [sdf] tag#23 FAILED Result: hostbyte=DID_BAD_TARGET driverbyte=DRIVER_OK cmd_age=0s
Mar 10 03:32:39 proxmox kernel: sd 8:0:0:0: [sdf] tag#23 CDB: Synchronize Cache(10) 35 00 00 00 00 00 00 00 00 00
Mar 10 03:32:39 proxmox kernel: blk_update_request: I/O error, dev sdf, sector 915448 op 0x1:(WRITE) flags 0x800 phys_seg 1 prio class 0
Mar 10 03:32:39 proxmox kernel: Aborting journal on device sdf-8.
Mar 10 03:32:39 proxmox kernel: sd 8:0:0:0: [sdf] tag#24 FAILED Result: hostbyte=DID_BAD_TARGET driverbyte=DRIVER_OK cmd_age=0s
Mar 10 03:32:39 proxmox kernel: sd 8:0:0:0: [sdf] tag#24 CDB: Write(10) 2a 00 00 00 30 48 00 00 08 00
Mar 10 03:32:39 proxmox kernel: blk_update_request: I/O error, dev sdf, sector 12360 op 0x1:(WRITE) flags 0x800 phys_seg 1 prio class 0
Mar 10 03:32:39 proxmox kernel: blk_update_request: I/O error, dev sdf, sector 12360 op 0x1:(WRITE) flags 0x800 phys_seg 1 prio class 0
Mar 10 03:32:39 proxmox kernel: Buffer I/O error on dev sdf, logical block 1545, lost sync page write
Mar 10 03:32:39 proxmox kernel: JBD2: Error -5 detected when updating journal superblock for sdf-8.
Mar 10 03:32:39 proxmox kernel: sd 8:0:0:0: [sdf] tag#15 FAILED Result: hostbyte=DID_BAD_TARGET driverbyte=DRIVER_OK cmd_age=0s
Mar 10 03:32:39 proxmox kernel: sd 8:0:0:0: [sdf] tag#15 CDB: Write(10) 2a 00 11 e4 10 78 00 00 10 00
Mar 10 03:32:39 proxmox kernel: blk_update_request: I/O error, dev sdf, sector 300159096 op 0x1:(WRITE) flags 0x103000 phys_seg 2 prio class 0
Mar 10 03:32:39 proxmox kernel: Buffer I/O error on dev sdf, logical block 37519887, lost async page write
Mar 10 03:32:39 proxmox kernel: Buffer I/O error on dev sdf, logical block 37519888, lost async page write
Mar 10 03:32:39 proxmox kernel: sd 8:0:0:0: [sdf] tag#16 FAILED Result: hostbyte=DID_BAD_TARGET driverbyte=DRIVER_OK cmd_age=0s
Mar 10 03:32:39 proxmox kernel: sd 8:0:0:0: [sdf] tag#16 CDB: Write(10) 2a 00 11 f4 10 78 00 00 08 00
Mar 10 03:32:39 proxmox kernel: blk_update_request: I/O error, dev sdf, sector 301207672 op 0x1:(WRITE) flags 0x103000 phys_seg 1 prio class 0
Mar 10 03:32:39 proxmox kernel: Buffer I/O error on dev sdf, logical block 37650959, lost async page write
Mar 10 03:32:39 proxmox kernel: sd 8:0:0:0: [sdf] tag#17 FAILED Result: hostbyte=DID_BAD_TARGET driverbyte=DRIVER_OK cmd_age=0s
Mar 10 03:32:39 proxmox kernel: sd 8:0:0:0: [sdf] tag#17 CDB: Write(10) 2a 00 11 f4 24 08 00 00 08 00
Mar 10 03:32:39 proxmox kernel: blk_update_request: I/O error, dev sdf, sector 301212680 op 0x1:(WRITE) flags 0x103000 phys_seg 1 prio class 0
Mar 10 03:32:39 proxmox kernel: Buffer I/O error on dev sdf, logical block 37651585, lost async page write
Mar 10 03:32:39 proxmox kernel: sd 8:0:0:0: [sdf] tag#18 FAILED Result: hostbyte=DID_BAD_TARGET driverbyte=DRIVER_OK cmd_age=0s
Mar 10 03:32:39 proxmox kernel: sd 8:0:0:0: [sdf] tag#18 CDB: Write(10) 2a 00 11 fc 10 60 00 00 08 00
Mar 10 03:32:39 proxmox kernel: blk_update_request: I/O error, dev sdf, sector 301731936 op 0x1:(WRITE) flags 0x103000 phys_seg 1 prio class 0
Mar 10 03:32:39 proxmox kernel: Buffer I/O error on dev sdf, logical block 37716492, lost async page write
Mar 10 03:32:39 proxmox kernel: sd 8:0:0:0: [sdf] tag#19 FAILED Result: hostbyte=DID_BAD_TARGET driverbyte=DRIVER_OK cmd_age=0s
Mar 10 03:32:39 proxmox kernel: sd 8:0:0:0: [sdf] tag#19 CDB: Write(10) 2a 00 11 fc 10 78 00 00 08 00
Mar 10 03:32:39 proxmox kernel: blk_update_request: I/O error, dev sdf, sector 301731960 op 0x1:(WRITE) flags 0x103000 phys_seg 1 prio class 0
Mar 10 03:32:39 proxmox kernel: Buffer I/O error on dev sdf, logical block 37716495, lost async page write
Mar 10 03:32:39 proxmox kernel: sd 8:0:0:0: [sdf] tag#20 FAILED Result: hostbyte=DID_BAD_TARGET driverbyte=DRIVER_OK cmd_age=0s
Mar 10 03:32:39 proxmox kernel: sd 8:0:0:0: [sdf] tag#20 CDB: Write(10) 2a 00 12 0c 10 48 00 00 08 00
Mar 10 03:32:39 proxmox kernel: blk_update_request: I/O error, dev sdf, sector 302780488 op 0x1:(WRITE) flags 0x103000 phys_seg 1 prio class 0
Mar 10 03:32:39 proxmox kernel: Buffer I/O error on dev sdf, logical block 37847561, lost async page write
Mar 10 03:32:39 proxmox kernel: Buffer I/O error on dev sdf, logical block 38961677, lost async page write
Mar 10 03:32:39 proxmox kernel: sd 8:0:0:0: [sdf] tag#17 FAILED Result: hostbyte=DID_BAD_TARGET driverbyte=DRIVER_OK cmd_age=0s
Mar 10 03:32:39 proxmox kernel: sd 8:0:0:0: [sdf] tag#17 CDB: Read(10) 28 00 01 20 71 00 00 00 80 00
Mar 10 03:32:39 proxmox kernel: EXT4-fs error (device sdf): ext4_journal_check_start:83: comm kvm: Detected aborted journal
Mar 10 03:32:39 proxmox kernel: EXT4-fs (sdf): I/O error while writing superblock
Mar 10 03:32:39 proxmox kernel: EXT4-fs (sdf): Remounting filesystem read-only
Mar 10 03:32:39 proxmox QEMU[41194]: qcow2_free_clusters failed: Input/output error
Mar 10 03:32:44 proxmox kernel: scsi_io_completion_action: 239 callbacks suppressed
Mar 10 03:32:44 proxmox kernel: sd 8:0:0:0: [sdf] tag#5 FAILED Result: hostbyte=DID_BAD_TARGET driverbyte=DRIVER_OK cmd_age=0s
Mar 10 03:32:44 proxmox kernel: sd 8:0:0:0: [sdf] tag#5 CDB: Write(10) 2a 00 1d 00 4f 78 00 00 08 00
Mar 10 03:32:44 proxmox kernel: print_req_error: 242 callbacks suppressed
Mar 10 03:32:44 proxmox kernel: blk_update_request: I/O error, dev sdf, sector 486559608 op 0x1:(WRITE) flags 0x8800 phys_seg 1 prio class 0
Mar 10 03:32:44 proxmox kernel: sd 8:0:0:0: [sdf] tag#6 FAILED Result: hostbyte=DID_BAD_TARGET driverbyte=DRIVER_OK cmd_age=0s
Mar 10 03:32:44 proxmox kernel: sd 8:0:0:0: [sdf] tag#6 CDB: Write(10) 2a 00 02 d4 66 60 00 00 20 00
Mar 10 03:32:44 proxmox kernel: blk_update_request: I/O error, dev sdf, sector 47474272 op 0x1:(WRITE) flags 0x8800 phys_seg 4 prio class 0
Mar 10 03:32:44 proxmox kernel: sd 8:0:0:0: [sdf] tag#7 FAILED Result: hostbyte=DID_BAD_TARGET driverbyte=DRIVER_OK cmd_age=0s
Mar 10 03:32:44 proxmox kernel: sd 8:0:0:0: [sdf] tag#7 CDB: Write(10) 2a 00 02 d4 67 00 00 00 60 00
Mar 10 03:32:44 proxmox kernel: blk_update_request: I/O error, dev sdf, sector 47474432 op 0x1:(WRITE) flags 0x8800 phys_seg 12 prio class 0
Mar 10 03:32:44 proxmox kernel: sd 8:0:0:0: [sdf] tag#10 FAILED Result: hostbyte=DID_BAD_TARGET driverbyte=DRIVER_OK cmd_age=0s
Mar 10 03:32:44 proxmox kernel: sd 8:0:0:0: [sdf] tag#10 CDB: Read(10) 28 00 0f c0 50 78 00 00 40 00
Mar 10 03:32:44 proxmox kernel: blk_update_request: I/O error, dev sdf, sector 264261752 op 0x0:(READ) flags 0x0 phys_seg 8 prio class 0
Mar 10 03:32:44 proxmox kernel: sd 8:0:0:0: [sdf] tag#11 FAILED Result: hostbyte=DID_BAD_TARGET driverbyte=DRIVER_OK cmd_age=0s
Mar 10 03:32:44 proxmox kernel: sd 8:0:0:0: [sdf] tag#11 CDB: Read(10) 28 00 1c 3c 71 18 00 00 02 00
Mar 10 03:32:44 proxmox kernel: blk_update_request: I/O error, dev sdf, sector 473723160 op 0x0:(READ) flags 0x0 phys_seg 1 prio class 0
Mar 10 03:32:45 proxmox kernel: sd 8:0:0:0: [sdf] tag#12 FAILED Result: hostbyte=DID_BAD_TARGET driverbyte=DRIVER_OK cmd_age=0s
Mar 10 03:32:45 proxmox kernel: sd 8:0:0:0: [sdf] tag#12 CDB: Read(10) 28 00 0f c0 50 78 00 00 40 00
Mar 10 03:32:45 proxmox kernel: blk_update_request: I/O error, dev sdf, sector 264261752 op 0x0:(READ) flags 0x0 phys_seg 8 prio class 0
Mar 10 03:32:45 proxmox kernel: sd 8:0:0:0: [sdf] tag#13 FAILED Result: hostbyte=DID_BAD_TARGET driverbyte=DRIVER_OK cmd_age=0s
Mar 10 03:32:45 proxmox kernel: sd 8:0:0:0: [sdf] tag#13 CDB: Write(10) 2a 00 02 d4 66 60 00 00 20 00
Mar 10 03:32:45 proxmox kernel: blk_update_request: I/O error, dev sdf, sector 47474272 op 0x1:(WRITE) flags 0x8800 phys_seg 4 prio class 0
Mar 10 03:32:45 proxmox kernel: sd 8:0:0:0: [sdf] tag#14 FAILED Result: hostbyte=DID_BAD_TARGET driverbyte=DRIVER_OK cmd_age=0s
Mar 10 03:32:45 proxmox kernel: sd 8:0:0:0: [sdf] tag#14 CDB: Write(10) 2a 00 02 d4 67 00 00 00 60 00
Mar 10 03:32:45 proxmox kernel: blk_update_request: I/O error, dev sdf, sector 47474432 op 0x1:(WRITE) flags 0x8800 phys_seg 12 prio class 0
Mar 10 03:32:45 proxmox kernel: sd 8:0:0:0: [sdf] tag#15 FAILED Result: hostbyte=DID_BAD_TARGET driverbyte=DRIVER_OK cmd_age=0s
Mar 10 03:32:45 proxmox kernel: sd 8:0:0:0: [sdf] tag#15 CDB: Write(10) 2a 00 1d 00 4f 78 00 00 08 00
Mar 10 03:32:45 proxmox kernel: blk_update_request: I/O error, dev sdf, sector 486559608 op 0x1:(WRITE) flags 0x8800 phys_seg 1 prio class 0
Mar 10 03:32:45 proxmox kernel: sd 8:0:0:0: [sdf] tag#16 FAILED Result: hostbyte=DID_BAD_TARGET driverbyte=DRIVER_OK cmd_age=0s
Mar 10 03:32:45 proxmox kernel: sd 8:0:0:0: [sdf] tag#16 CDB: Read(10) 28 00 1c 3c 71 18 00 00 02 00
Mar 10 03:32:45 proxmox kernel: blk_update_request: I/O error, dev sdf, sector 473723160 op 0x0:(READ) flags 0x0 phys_seg 1 prio class 0
Mar 10 03:32:49 proxmox kernel: scsi_io_completion_action: 23 callbacks suppressed
Mar 10 03:32:49 proxmox kernel: sd 8:0:0:0: [sdf] tag#29 FAILED Result: hostbyte=DID_BAD_TARGET driverbyte=DRIVER_OK cmd_age=0s
Mar 10 03:32:49 proxmox kernel: sd 8:0:0:0: [sdf] tag#29 CDB: Read(10) 28 00 16 ab e0 3a 00 00 38 00
Mar 10 03:32:49 proxmox kernel: print_req_error: 23 callbacks suppressed
Click to expand...

Jetzt meine Frage wie kann ich hier eine Lösung für das Problem finden?

Laut meiner Google Suche kann das echt super viel sein:

- ein defektes Kabel (Kabel ist ca. 8 Monate alt)
- defekte Laufwerke (Beide Laufwerke (SSD) sind ca. 8 Monate alt)
- ein Kernel Problem

Der Fehler tritt nicht sofort auf, sondern wie im Log zu sehen ist, letzte Nacht das letzte Mal.
Ich bin da echt etwas überfordert hier den Fehler zu finden und würde mich echt sehr darüber freuen, wenn Ihr mir helfen würdet.

Vielen Dank
 
Zufällig während dem Backup? Wenn ja, hast du zu der Zeit hohe IO Wait time?
 
SkyDiver79 said:
Zufällig während dem Backup? Wenn ja, hast du zu der Zeit hohe IO Wait time?
Click to expand...
Vielen Dank für deinen Tipp. Habe ich mir sofort angesehen, aber ich kann das es das nicht ist. Die Sicherungen laufen um 21:45, 22:45, 23:45 der jeweiligen HDD/SSD. Zwei Sicherungen einer HDD und SSD überschneiden sich. Wie würde ich den so ein IO Wait Time Problem lösen. Wahrscheinlich keine Backups parallel laufen lassen, oder? Ich habe gestern mal eine VM von einer SSD auf eine HDD verschoben, heute Nacht sind dann alle VM´s durchgelaufen.
 
Warum auch immer, muss man im Einzelfall raus kriegen. Aber das Backup und die damit Verbundene Last ist oft eine Fehlerquelle bei einfachen Disks/SSDs.
 
You must log in or register to reply here.

About

The Proxmox community has been around for many years and offers help and support for Proxmox VE, Proxmox Backup Server, and Proxmox Mail Gateway.
We think our community is one of the best thanks to people like you!

Quick Navigation

Home Get Subscription Wiki Downloads Proxmox Customer Portal About

Get your subscription!

The Proxmox team works very hard to make sure you are running the best software and getting stable updates and security enhancements, as well as quick enterprise support. Tens of thousands of happy customers have a Proxmox subscription. Get yours easily in our online shop.

Buy now!
Community platform by XenForo® © 2010-2024 XenForo Ltd.
Top Bottom