Festplattenfehler in der VM mit IDE Disk

[konabi]

Hallo,

ich habe verschiedene VMs mit SUSE 12.3 Kernel 3.7.10-1.11.
Ich habe festgetsellt dass bei den VMs die mit Festplatte IDE eingerichtet sind folgende Fehlermeldungen erscheinen: (dmseg)

[ 4464.110856] ata1.00: status: { DRDY }
[ 4464.111152] ata1: soft resetting link
[ 4464.264483] ata1.01: NODEV after polling detection
[ 4464.265336] ata1.00: configured for MWDMA2
[ 4464.265342] ata1.00: device reported invalid CHS sector 0
[ 4464.265357] ata1: EH complete
[ 4496.111107] ata1.00: exception Emask 0x0 SAct 0x0 SErr 0x0 action 0x6 frozen
[ 4496.111140] ata1.00: failed command: WRITE DMA
[ 4496.111319] ata1.00: cmd ca/00:10:10:98:8a/00:00:00:00:00/e2 tag 0 dma 8192 out
[ 4496.111319]          res 40/00:01:00:00:00/00:00:00:00:00/a0 Emask 0x4 (timeout)
[ 4496.111703] ata1.00: status: { DRDY }
[ 4496.111978] ata1: soft resetting link
[ 4496.268490] ata1.01: NODEV after polling detection
[ 4496.269322] ata1.00: configured for MWDMA2
[ 4496.269329] ata1.00: device reported invalid CHS sector 0
[ 4496.269341] ata1: EH complete
[ 4571.629657] ata1.00: exception Emask 0x0 SAct 0x0 SErr 0x0 action 0x6 frozen
[ 4571.629703] ata1.00: failed command: WRITE DMA
[ 4571.629928] ata1.00: cmd ca/00:08:98:c1:0a/00:00:00:00:00/e0 tag 0 dma 4096 out
[ 4571.629928]          res 40/00:01:00:00:00/00:00:00:00:00/a0 Emask 0x4 (timeout)
[ 4571.630391] ata1.00: status: { DRDY }
[ 4571.630804] ata1: soft resetting link
[ 4571.784508] ata1.01: NODEV after polling detection
[ 4571.785319] ata1.00: configured for MWDMA2
[ 4571.785326] ata1.00: device reported invalid CHS sector 0
[ 4571.785339] ata1: EH complete
[ 4749.660129] ata1.00: limiting speed to MWDMA1:PIO4
[ 4749.660155] ata1.00: exception Emask 0x0 SAct 0x0 SErr 0x0 action 0x6 frozen
[ 4749.660185] ata1.00: failed command: WRITE DMA
[ 4749.660431] ata1.00: cmd ca/00:08:28:b3:18/00:00:00:00:00/e3 tag 0 dma 4096 out
[ 4749.660431]          res 40/00:01:00:00:00/00:00:00:00:00/a0 Emask 0x4 (timeout)
[ 4749.660776] ata1.00: status: { DRDY }
[ 4749.661055] ata1: soft resetting link
[ 4749.816496] ata1.01: NODEV after polling detection
[ 4749.817570] ata1.00: configured for MWDMA1
[ 4749.817576] ata1.00: device reported invalid CHS sector 0
[ 4749.817587] ata1: EH complete
[ 4843.762906] ata1.00: exception Emask 0x0 SAct 0x0 SErr 0x0 action 0x6 frozen
[ 4843.762936] ata1.00: failed command: WRITE DMA
[ 4843.763115] ata1.00: cmd ca/00:08:50:8b:5b/00:00:00:00:00/e1 tag 0 dma 4096 out
[ 4843.763115]          res 40/00:01:00:00:00/00:00:00:00:00/a0 Emask 0x4 (timeout)
[ 4843.763445] ata1.00: status: { DRDY }
[ 4843.763683] ata1: soft resetting link
[ 4843.916507] ata1.01: NODEV after polling detection
[ 4843.917330] ata1.00: configured for MWDMA1
[ 4843.917336] ata1.00: device reported invalid CHS sector 0
[ 4843.917347] ata1: EH complete
[ 5436.372709] ata1.00: exception Emask 0x0 SAct 0x0 SErr 0x0 action 0x6 frozen
[ 5436.372754] ata1.00: failed command: WRITE DMA
[ 5436.373018] ata1.00: cmd ca/00:08:40:ee:18/00:00:00:00:00/e3 tag 0 dma 4096 out
[ 5436.373018]          res 40/00:01:00:00:00/00:00:00:00:00/a0 Emask 0x4 (timeout)
[ 5436.380229] ata1.00: status: { DRDY }
[ 5436.381667] ata1: soft resetting link
[ 5436.536498] ata1.01: NODEV after polling detection
[ 5436.537325] ata1.00: configured for MWDMA1
[ 5436.537332] ata1.00: device reported invalid CHS sector 0
[ 5436.537344] ata1: EH complete
[ 5468.429302] ata1.00: exception Emask 0x0 SAct 0x0 SErr 0x0 action 0x6 frozen
[ 5468.430378] ata1.00: failed command: WRITE DMA
[ 5468.431396] ata1.00: cmd ca/00:08:40:ee:18/00:00:00:00:00/e3 tag 0 dma 4096 out
[ 5468.431396]          res 40/00:01:00:00:00/00:00:00:00:00/a0 Emask 0x4 (timeout)
[ 5468.433493] ata1.00: status: { DRDY }
[ 5468.434633] ata1: soft resetting link
[ 5468.436029] [sched_delayed] sched: RT throttling activated
[ 5468.588496] ata1.01: NODEV after polling detection
[ 5468.589324] ata1.00: configured for MWDMA1
[ 5468.589331] ata1.00: device reported invalid CHS sector 0
[ 5468.589345] ata1: EH complete
[ 5501.970477] ata1.00: exception Emask 0x0 SAct 0x0 SErr 0x0 action 0x6 frozen
[ 5501.971574] ata1.00: failed command: WRITE DMA
[ 5501.972631] ata1.00: cmd ca/00:08:40:ee:18/00:00:00:00:00/e3 tag 0 dma 4096 out
[ 5501.972631]          res 40/00:01:00:00:00/00:00:00:00:00/a0 Emask 0x4 (timeout)
[ 5501.974675] ata1.00: status: { DRDY }
[ 5501.974792] ata1: soft resetting link
[ 5502.128473] ata1.01: NODEV after polling detection
[ 5502.129275] ata1.00: configured for MWDMA1
[ 5502.129281] ata1.00: device reported invalid CHS sector 0
[ 5502.129292] ata1: EH complete
[ 5591.947337] ata1.00: exception Emask 0x0 SAct 0x0 SErr 0x0 action 0x6 frozen
[ 5591.949261] ata1.00: failed command: WRITE DMA
[ 5591.949823] CIFS VFS: Server 192.168.222.7 has not responded in 120 seconds. Reconnecting...
[ 5591.951951] ata1.00: cmd ca/00:58:48:ee:18/00:00:00:00:00/e3 tag 0 dma 45056 out
[ 5591.951951]          res 40/00:01:00:00:00/00:00:00:00:00/a0 Emask 0x4 (timeout)
[ 5591.954270] ata1.00: status: { DRDY }
[ 5591.954426] ata1: soft resetting link
[ 5592.108508] ata1.01: NODEV after polling detection
[ 5592.109327] ata1.00: configured for MWDMA1
[ 5592.109335] ata1.00: device reported invalid CHS sector 0
[ 5592.109347] ata1: EH complete
[ 7766.161577] ata1.00: exception Emask 0x0 SAct 0x0 SErr 0x0 action 0x6 frozen
[ 7766.167469] ata1.00: failed command: WRITE DMA
[ 7766.168757] ata1.00: cmd ca/00:08:18:08:9c/00:00:00:00:00/e1 tag 0 dma 4096 out
[ 7766.168757]          res 40/00:01:00:00:00/00:00:00:00:00/a0 Emask 0x4 (timeout)
[ 7766.168758] ata1.00: status: { DRDY }
[ 7766.168915] ata1: soft resetting link
[ 7766.324517] ata1.01: NODEV after polling detection
[ 7766.325379] ata1.00: configured for MWDMA1
[ 7766.325386] ata1.00: device reported invalid CHS sector 0
[ 7766.325423] ata1: EH complete
[ 7895.146006] ata1.00: exception Emask 0x0 SAct 0x0 SErr 0x0 action 0x6 frozen
[ 7895.147112] ata1.00: failed command: WRITE DMA
[ 7895.148254] ata1.00: cmd ca/00:b0:20:b0:19/00:00:00:00:00/e3 tag 0 dma 90112 out
[ 7895.148254]          res 40/00:01:00:00:00/00:00:00:00:00/a0 Emask 0x4 (timeout)
[ 7895.150333] ata1.00: status: { DRDY }
[ 7895.151504] ata1: soft resetting link
[ 7895.304496] ata1.01: NODEV after polling detection
[ 7895.305328] ata1.00: configured for MWDMA1
[ 7895.305337] ata1.00: device reported invalid CHS sector 0
[ 7895.305349] ata1: EH complete
[ 9870.717914] ata1.00: exception Emask 0x0 SAct 0x0 SErr 0x0 action 0x6 frozen
[ 9870.725114] ata1.00: failed command: WRITE DMA
[ 9870.726347] ata1.00: cmd ca/00:10:10:98:8a/00:00:00:00:00/e2 tag 0 dma 8192 out
[ 9870.726347]          res 40/00:01:00:00:00/00:00:00:00:00/a0 Emask 0x4 (timeout)
[ 9870.726348] ata1.00: status: { DRDY }
[ 9870.726473] ata1: soft resetting link
[ 9870.880495] ata1.01: NODEV after polling detection
[ 9870.881357] ata1.00: configured for MWDMA1
[ 9870.881363] ata1.00: device reported invalid CHS sector 0
[ 9870.881373] ata1: EH complete

Die VMs liegen auf einen ISCSI Storage. Den CAche für die Festplatten habe auf Direct sync eingestellt.

 pveversion -v
proxmox-ve: 4.4-88 (running kernel: 4.4.62-1-pve)
pve-manager: 4.4-13 (running version: 4.4-13/7ea56165)
pve-kernel-4.4.35-1-pve: 4.4.35-77
pve-kernel-4.4.62-1-pve: 4.4.62-88
lvm2: 2.02.116-pve3
corosync-pve: 2.4.2-2~pve4+1
libqb0: 1.0.1-1
pve-cluster: 4.0-50
qemu-server: 4.0-110
pve-firmware: 1.1-11
libpve-common-perl: 4.0-95
libpve-access-control: 4.0-23
libpve-storage-perl: 4.0-76
pve-libspice-server1: 0.12.8-2
vncterm: 1.3-2
pve-docs: 4.4-4
pve-qemu-kvm: 2.7.1-4
pve-container: 1.0-100
pve-firewall: 2.0-33
pve-ha-manager: 1.0-40
ksm-control-daemon: 1.2-1
glusterfs-client: 3.5.2-2+deb8u3
lxc-pve: 2.0.7-4
lxcfs: 2.0.6-pve1
criu: 1.6.0-1
novnc-pve: 0.5-9
smartmontools: 6.5+svn4324-1~pve80
zfsutils: 0.6.5.9-pve15~bpo80

Ich bin für jede Hilfe dankbar.

 

[LnxBil]

Dann gleich die Frage: Warum IDE in 2017?

 

[konabi]

Ja, wurde vor Jahren mal so eingerichtet. Ist wahrscheinlich nicht Optimal.
Die anderen haben virtio oder iscsi was wahrscheinlich auch nicht so Optimal ist

 

[LnxBil]

Dann wäre das jetzt der richtige Zeitpunkt mal eine Migration ins Auge fassen. Das System ist seit fast 3 Jahren EOL und somit mindestens so lange ungepatchet.