qemu-discuss
[Top][All Lists]
Advanced

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: errors in virtual disc


From: Lentes, Bernd
Subject: Re: errors in virtual disc
Date: Tue, 23 Feb 2021 21:12:58 +0100 (CET)


----- On Feb 22, 2021, at 4:54 PM, Bernd Lentes 
bernd.lentes@helmholtz-muenchen.de wrote:

> Hi,
> 
> i have a VirtualDomain which often does not boot completely, but stucks in
> emergency mode or while starting D-Bus.
> Host and guest are SLES 12 SP5. qemu on the host is qemu-3.1.1.1-45.1.x86_64.
> The virtual disc is a raw file which resides on a SAN on an OCFS2 Volume.
> 
> In the log i found, beneath other irregular stuff, the following:
> Nov 25 23:47:57 geneious udisksd[2354]: Error probing device: Error sending 
> ATA
> command IDENTIFY DEVICE to /dev/sda: Unexpected sense data returned:
>                                        0000: 70 00 05 00  00 00 00 0a  00 58 
> 00 01  21 04 00 00    p........X..!...
>                                        0010: 00 00 00 00  00 00 00 00  00 00 
> 00 00  00 00 00 00    ................
>                                         (g-io-error-quark, 0)
> Jan 26 23:58:06 geneious udisksd[2422]: Error probing device: Error sending 
> ATA
> command IDENTIFY DEVICE to /dev/sda: Unexpected sense data returned:
>                                        0000: 70 00 05 00  00 00 00 0a  00 58 
> 00 01  21 04 00 00    p........X..!...
>                                        0010: 00 00 00 00  00 00 00 00  00 00 
> 00 00  00 00 00 00    ................
>                                         (g-io-error-quark, 0)
> Feb 01 23:44:52 geneious udisksd[2510]: Error probing device: Error sending 
> ATA
> command IDENTIFY DEVICE to /dev/sda: Unexpected sense data returned:
>                                        0000: 70 00 05 00  00 00 00 0a  00 58 
> 00 01  21 04 00 00    p........X..!...
>                                        0010: 00 00 00 00  00 00 00 00  00 00 
> 00 00  00 00 00 00    ................
>                                         (g-io-error-quark, 0)
> Feb 18 23:45:35 geneious udisksd[2566]: Error probing device: Error sending 
> ATA
> command IDENTIFY DEVICE to /dev/sda: Unexpected sense data returned:
>                                        0000: 70 00 05 00  00 00 00 0a  00 58 
> 00 01  21 04 00 00    p........X..!...
>                                        0010: 00 00 00 00  00 00 00 00  00 00 
> 00 00  00 00 00 00    ................
>                                         (g-io-error-quark, 0)
> 
> Also sometimes:
> 
> Feb 03 22:49:04 linux-8i1i kernel: ata1.00: exception Emask 0x0 SAct 0x8000 
> SErr
> 0x0 action 0x6 frozen
> Feb 03 22:49:04 linux-8i1i kernel: ata1.00: failed command: WRITE FPDMA QUEUED
> Feb 03 22:49:04 linux-8i1i kernel: ata1.00: cmd
> 61/08:78:b8:41:00/00:00:05:00:00/40 tag 15 ncq dma 4096 out
>                                            res 
> 40/00:00:00:00:00/00:00:00:00:00/00 Emask 0x4 (timeout)
> Feb 03 22:49:04 linux-8i1i kernel: ata1.00: status: { DRDY }
> Feb 03 22:49:04 linux-8i1i kernel: ata1: hard resetting link
> Feb 03 22:49:05 linux-8i1i kernel: ata1: SATA link up 1.5 Gbps (SStatus 113
> SControl 300)
> Feb 03 22:49:05 linux-8i1i kernel: ata1.00: configured for UDMA/100
> Feb 03 22:49:05 linux-8i1i kernel: ata1.00: device reported invalid CHS 
> sector 0
> Feb 03 22:49:05 linux-8i1i kernel: sd 0:0:0:0: [sda] tag#13 FAILED Result:
> hostbyte=DID_OK driverbyte=DRIVER_TIMEOUT
> Feb 03 22:49:05 linux-8i1i kernel: sd 0:0:0:0: [sda] tag#13 CDB: Write(10) 2a 
> 00
> 04 c0 43 58 00 00 10 00
> Feb 03 22:49:05 linux-8i1i kernel: print_req_error: I/O error, dev sda, sector
> 79709016
> Feb 03 22:49:05 linux-8i1i kernel: Buffer I/O error on dev dm-1, logical block
> 9437291, lost async page write
> Feb 03 22:49:05 linux-8i1i kernel: Buffer I/O error on dev dm-1, logical block
> 9437292, lost async page write
> Feb 03 22:49:05 linux-8i1i kernel: sd 0:0:0:0: [sda] tag#12 FAILED Result:
> hostbyte=DID_OK driverbyte=DRIVER_TIMEOUT
> Feb 03 22:49:05 linux-8i1i kernel: sd 0:0:0:0: [sda] tag#12 CDB: Write(10) 2a 
> 00
> 04 04 42 c0 00 00 08 00
> Feb 03 22:49:05 linux-8i1i kernel: print_req_error: I/O error, dev sda, sector
> 67388096
> Feb 03 22:49:05 linux-8i1i kernel: print_req_error: I/O error, dev sda, sector
> 67388096
> Feb 03 22:49:05 linux-8i1i kernel: sd 0:0:0:0: [sda] tag#11 FAILED Result:
> hostbyte=DID_OK driverbyte=DRIVER_TIMEOUT
> Feb 03 22:49:05 linux-8i1i kernel: sd 0:0:0:0: [sda] tag#11 CDB: Write(10) 2a 
> 00
> 04 c0 43 18 00 00 08 00
> Feb 03 22:49:05 linux-8i1i kernel: print_req_error: I/O error, dev sda, sector
> 79708952
> Feb 03 22:49:05 linux-8i1i kernel: Buffer I/O error on dev dm-1, logical block
> 9437283, lost async page write
> Feb 03 22:49:05 linux-8i1i kernel: Aborting journal on device dm-1-8.
> Feb 03 22:49:05 linux-8i1i kernel: sd 0:0:0:0: [sda] tag#10 FAILED Result:
> hostbyte=DID_OK driverbyte=DRIVER_TIMEOUT
> Feb 03 22:49:05 linux-8i1i kernel: sd 0:0:0:0: [sda] tag#10 CDB: Write(10) 2a 
> 00
> 04 c0 42 c8 00 00 08 00
> Feb 03 22:49:05 linux-8i1i kernel: print_req_error: I/O error, dev sda, sector
> 79708872
> Feb 03 22:49:05 linux-8i1i kernel: Buffer I/O error on dev dm-1, logical block
> 9437273, lost async page write
> Feb 03 22:49:05 linux-8i1i kernel: sd 0:0:0:0: [sda] tag#9 FAILED Result:
> hostbyte=DID_OK driverbyte=DRIVER_TIMEOUT
> Feb 03 22:49:05 linux-8i1i kernel: sd 0:0:0:0: [sda] tag#9 CDB: Write(10) 2a 
> 00
> 04 c0 42 a8 00 00 08 00
> Feb 03 22:49:05 linux-8i1i kernel: print_req_error: I/O error, dev sda, sector
> 79708840
> Feb 03 22:49:05 linux-8i1i kernel: Buffer I/O error on dev dm-1, logical block
> 9437269, lost async page write
> Feb 03 22:49:05 linux-8i1i kernel: sd 0:0:0:0: [sda] tag#8 FAILED Result:
> hostbyte=DID_OK driverbyte=DRIVER_TIMEOUT
> Feb 03 22:49:05 linux-8i1i kernel: sd 0:0:0:0: [sda] tag#8 CDB: Write(10) 2a 
> 00
> 04 c0 42 90 00 00 10 00
> Feb 03 22:49:05 linux-8i1i kernel: print_req_error: I/O error, dev sda, sector
> 79708816
> Feb 03 22:49:05 linux-8i1i kernel: Buffer I/O error on dev dm-1, logical block
> 9437266, lost async page write
> Feb 03 22:49:05 linux-8i1i kernel: Buffer I/O error on dev dm-1, logical block
> 9437267, lost async page write
> Feb 03 22:49:05 linux-8i1i kernel: sd 0:0:0:0: [sda] tag#7 FAILED Result:
> hostbyte=DID_OK driverbyte=DRIVER_TIMEOUT
> Feb 03 22:49:05 linux-8i1i kernel: sd 0:0:0:0: [sda] tag#7 CDB: Write(10) 2a 
> 00
> 04 c0 42 68 00 00 08 00
> Feb 03 22:49:05 linux-8i1i kernel: print_req_error: I/O error, dev sda, sector
> 79708776
> Feb 03 22:49:05 linux-8i1i kernel: Buffer I/O error on dev dm-1, logical block
> 9437261, lost async page write
> Feb 03 22:49:05 linux-8i1i kernel: sd 0:0:0:0: [sda] tag#6 FAILED Result:
> hostbyte=DID_OK driverbyte=DRIVER_TIMEOUT
> Feb 03 22:49:05 linux-8i1i kernel: sd 0:0:0:0: [sda] tag#6 CDB: Write(10) 2a 
> 00
> 04 c0 42 50 00 00 08 00
> Feb 03 22:49:05 linux-8i1i kernel: print_req_error: I/O error, dev sda, sector
> 79708752
> Feb 03 22:49:05 linux-8i1i kernel: Buffer I/O error on dev dm-1, logical block
> 9437258, lost async page write
> Feb 03 22:49:05 linux-8i1i kernel: sd 0:0:0:0: [sda] tag#5 FAILED Result:
> hostbyte=DID_OK driverbyte=DRIVER_TIMEOUT
> Feb 03 22:49:05 linux-8i1i kernel: sd 0:0:0:0: [sda] tag#5 CDB: Write(10) 2a 
> 00
> 04 c0 42 40 00 00 08 00
> Feb 03 22:49:05 linux-8i1i kernel: print_req_error: I/O error, dev sda, sector
> 79708736
> Feb 03 22:49:05 linux-8i1i kernel: Buffer I/O error on dev dm-1, logical block
> 9437256, lost async page write
> Feb 03 22:49:05 linux-8i1i kernel: sd 0:0:0:0: [sda] tag#4 FAILED Result:
> hostbyte=DID_OK driverbyte=DRIVER_TIMEOUT
> Feb 03 22:49:05 linux-8i1i kernel: sd 0:0:0:0: [sda] tag#4 CDB: Write(10) 2a 
> 00
> 04 c0 41 48 00 00 10 00
> Feb 03 22:49:05 linux-8i1i kernel: ata1: EH complete
> Feb 03 22:49:05 linux-8i1i kernel: EXT4-fs error (device dm-1):
> ext4_journal_check_start:60: Detected aborted journal
> Feb 03 22:49:05 linux-8i1i kernel: EXT4-fs (dm-1): Remounting filesystem
> read-only
> 
> 
> Feb 20 22:43:14 linux-8i1i systemd[1]: Starting File System Check on
> /dev/mapper/vg_local-lv_root...
> -- Subject: Unit systemd-fsck-root.service has begun start-up
> -- Defined-By: systemd
> -- Support: http://lists.freedesktop.org/mailman/listinfo/systemd-devel
> --
> -- Unit systemd-fsck-root.service has begun starting up.
> Feb 20 22:43:16 linux-8i1i systemd-fsck[440]: /dev/mapper/vg_local-lv_root:
> recovering journal
> Feb 20 22:44:12 linux-8i1i kernel: sd 0:0:0:0: [sda] tag#11 FAILED Result:
> hostbyte=DID_OK driverbyte=DRIVER_TIMEOUT
> Feb 20 22:44:12 linux-8i1i kernel: sd 0:0:0:0: [sda] tag#11 CDB: Write(10) 2a 
> 00
> 04 41 50 10 00 00 10 00
> Feb 20 22:44:12 linux-8i1i kernel: print_req_error: I/O error, dev sda, sector
> 71389200
> Feb 20 22:44:12 linux-8i1i kernel: Buffer I/O error on dev dm-0, logical block
> 8397314, lost async page write
> Feb 20 22:44:12 linux-8i1i kernel: Buffer I/O error on dev dm-0, logical block
> 8397315, lost async page write
> Feb 20 22:44:12 linux-8i1i kernel: sd 0:0:0:0: [sda] tag#8 FAILED Result:
> hostbyte=DID_OK driverbyte=DRIVER_TIMEOUT
> Feb 20 22:44:12 linux-8i1i kernel: sd 0:0:0:0: [sda] tag#8 CDB: Write(10) 2a 
> 00
> 04 40 44 a0 00 00 08 00
> Feb 20 22:44:12 linux-8i1i kernel: print_req_error: I/O error, dev sda, sector
> 71320736
> Feb 20 22:44:12 linux-8i1i kernel: Buffer I/O error on dev dm-0, logical block
> 8388756, lost async page write
> Feb 20 22:44:12 linux-8i1i kernel: sd 0:0:0:0: [sda] tag#7 FAILED Result:
> hostbyte=DID_OK driverbyte=DRIVER_TIMEOUT
> Feb 20 22:44:12 linux-8i1i kernel: sd 0:0:0:0: [sda] tag#7 CDB: Write(10) 2a 
> 00
> 04 40 43 20 00 00 08 00
> Feb 20 22:44:12 linux-8i1i kernel: print_req_error: I/O error, dev sda, sector
> 71320352
> Feb 20 22:44:12 linux-8i1i kernel: Buffer I/O error on dev dm-0, logical block
> 8388708, lost async page write
> Feb 20 22:44:12 linux-8i1i kernel: sd 0:0:0:0: [sda] tag#12 FAILED Result:
> hostbyte=DID_OK driverbyte=DRIVER_TIMEOUT
> Feb 20 22:44:12 linux-8i1i kernel: sd 0:0:0:0: [sda] tag#12 CDB: Write(10) 2a 
> 00
> 04 c0 41 28 00 00 08 00
> Feb 20 22:44:12 linux-8i1i kernel: print_req_error: I/O error, dev sda, sector
> 79708456
> Feb 20 22:44:12 linux-8i1i kernel: Buffer I/O error on dev dm-0, logical block
> 9437221, lost async page write
> Feb 20 22:44:12 linux-8i1i kernel: sd 0:0:0:0: [sda] tag#13 FAILED Result:
> hostbyte=DID_OK driverbyte=DRIVER_TIMEOUT
> Feb 20 22:44:12 linux-8i1i kernel: sd 0:0:0:0: [sda] tag#13 CDB: Write(10) 2a 
> 00
> 04 c0 41 00 00 00 08 00
> Feb 20 22:44:12 linux-8i1i kernel: print_req_error: I/O error, dev sda, sector
> 79708416
> Feb 20 22:44:12 linux-8i1i kernel: Buffer I/O error on dev dm-0, logical block
> 9437216, lost async page write
> Feb 20 22:44:12 linux-8i1i kernel: sd 0:0:0:0: [sda] tag#10 FAILED Result:
> hostbyte=DID_OK driverbyte=DRIVER_TIMEOUT
> Feb 20 22:44:12 linux-8i1i kernel: sd 0:0:0:0: [sda] tag#10 CDB: Write(10) 2a 
> 00
> 04 c0 40 80 00 00 08 00
> Feb 20 22:44:12 linux-8i1i kernel: print_req_error: I/O error, dev sda, sector
> 79708288
> Feb 20 22:44:12 linux-8i1i kernel: Buffer I/O error on dev dm-0, logical block
> 9437200, lost async page write
> Feb 20 22:44:12 linux-8i1i kernel: sd 0:0:0:0: [sda] tag#9 FAILED Result:
> hostbyte=DID_OK driverbyte=DRIVER_TIMEOUT
> Feb 20 22:44:12 linux-8i1i kernel: sd 0:0:0:0: [sda] tag#9 CDB: Write(10) 2a 
> 00
> 04 c0 40 08 00 00 08 00
> Feb 20 22:44:12 linux-8i1i kernel: print_req_error: I/O error, dev sda, sector
> 79708168
> Feb 20 22:44:12 linux-8i1i kernel: Buffer I/O error on dev dm-0, logical block
> 9437185, lost async page write
> Feb 20 22:44:12 linux-8i1i kernel: sd 0:0:0:0: [sda] tag#14 FAILED Result:
> hostbyte=DID_OK driverbyte=DRIVER_TIMEOUT
> Feb 20 22:44:12 linux-8i1i kernel: sd 0:0:0:0: [sda] tag#14 CDB: Write(10) 2a 
> 00
> 04 c0 41 38 00 00 08 00
> Feb 20 22:44:12 linux-8i1i kernel: print_req_error: I/O error, dev sda, sector
> 79708472
> Feb 20 22:44:12 linux-8i1i kernel: Buffer I/O error on dev dm-0, logical block
> 9437223, lost async page write
> Feb 20 22:44:12 linux-8i1i kernel: sd 0:0:0:0: [sda] tag#16 FAILED Result:
> hostbyte=DID_OK driverbyte=DRIVER_TIMEOUT
> Feb 20 22:44:12 linux-8i1i kernel: sd 0:0:0:0: [sda] tag#16 CDB: Write(10) 2a 
> 00
> 04 c0 41 60 00 00 08 00
> Feb 20 22:44:12 linux-8i1i kernel: print_req_error: I/O error, dev sda, sector
> 79708512
> Feb 20 22:44:12 linux-8i1i kernel: Buffer I/O error on dev dm-0, logical block
> 9437228, lost async page write
> Feb 20 22:44:12 linux-8i1i kernel: sd 0:0:0:0: [sda] tag#15 FAILED Result:
> hostbyte=DID_OK driverbyte=DRIVER_TIMEOUT
> Feb 20 22:44:12 linux-8i1i kernel: sd 0:0:0:0: [sda] tag#15 CDB: Write(10) 2a 
> 00
> 04 c0 41 48 00 00 08 00
> Feb 20 22:44:12 linux-8i1i kernel: print_req_error: I/O error, dev sda, sector
> 79708488
> Feb 20 22:44:18 linux-8i1i systemd-fsck[440]: fsck.ext4: Unknown code ____ 251
> while recovering journal of /dev/mapper/vg_local-lv_root
> Feb 20 22:44:19 linux-8i1i systemd-fsck[440]: /dev/mapper/vg_local-lv_root was
> not cleanly unmounted, check forced.
> Feb 20 22:44:31 linux-8i1i systemd-fsck[440]: /dev/mapper/vg_local-lv_root:
> 140199/3932160 files (0.1% non-contiguous), 1409418/15728640 blocks
> Feb 20 22:44:31 linux-8i1i systemd[1]: Started File System Check on
> /dev/mapper/vg_local-lv_root.
> -- Subject: Unit systemd-fsck-root.service has finished start-up
> -- Defined-By: systemd
> -- Support: http://lists.freedesktop.org/mailman/listinfo/systemd-devel
> --
> -- Unit systemd-fsck-root.service has finished starting up.
> --
> -- The start-up result is done.
> 
> I checked the virtual disc with badblocks - no error.
> I checked the discs of the SAN via the web-interface from the controller (HP 
> MSA
> G3000 FC) - no error.

Furthermore i checked the ocfs2 volume with badblocks and fsck.ocfs2 - no error.
So for me the disks seem to be ok.
Maybe a timeout from the SAN ?

> Feb 20 22:44:12 linux-8i1i kernel: sd 0:0:0:0: [sda] tag#11 FAILED Result:
> hostbyte=DID_OK driverbyte=DRIVER_TIMEOUT

This indicates something like that.
But how can i debug that ?


Bernd
Helmholtz Zentrum M√ľnchen

Helmholtz Zentrum Muenchen
Deutsches Forschungszentrum fuer Gesundheit und Umwelt (GmbH)
Ingolstaedter Landstr. 1
85764 Neuherberg
www.helmholtz-muenchen.de
Aufsichtsratsvorsitzende: MinDir.in Prof. Dr. Veronika von Messling
Geschaeftsfuehrung: Prof. Dr. med. Dr. h.c. Matthias Tschoep, Kerstin Guenther
Registergericht: Amtsgericht Muenchen HRB 6466
USt-IdNr: DE 129521671




reply via email to

[Prev in Thread] Current Thread [Next in Thread]