[PVE-User] WG: disk error messages on kvm guest

[Meike Stone]

Hello,

thanks for help!
I changed the virtual disk (raw) from scsi to ide and all errors are gone!
But what I don't understand, after the change, the Partition (lvm) is
furthermore reachable as /dev/sdb1?
Should it not be now an hdX? Also fdisk -l shows the old name!

Thanks, Meike


2011/11/4 Holger Ernst <he at ernstdatenmedien.de>:
> Hi Meike,
>
> Any special reason to use scsi for the virtual disk? Maybe there is some mismatch between scsi driver in SUSE and the virtual implementation in the host (this is very wild guessing, I know).
> Have you tried to use the IDE interface? You can change that any time (stop the VM in advance ;-)).
>
> Regards, Holger
>
> ------------------------------------------------
> Thanks for answer,
>
> 2011/11/4 Robert Fantini <rob at fantinibakery.com>:
>> On 11/04/2011 05:18 AM, Meike Stone wrote:
>>>
>>> Hello,
>>>
>>> I've running proxmox (1.9) on a notebook* and I'm very satisfied!
>>>
>>> * AMD Athlon(tm) II P360 Dual-Core Processor
>>> * SATA controller:    SB7x0/SB8x0/SB9x0 SATA Controller [AHCI mode]
>>> (ATITechnologies Inc)
>>> * Disk: Seagate ST9320325AS,  320GB  (ATA )
>>> * 4GByte RAM (1333MHz)
>>> (Are there more information needed, please tell it me. )
>>>
>>> Yesterday I tried to import a backup from OpenLDAP via slapadd running
>>> on a openSuSE 11.3  Guest (kvm).
>>> (Kernel: Linux test01 2.6.34.8-0.2-desktop #1 SMP PREEMPT 2011-04-06
>>> 18:11:26 +0200 x86_64 x86_64 x86_64 GNU/Linux)
>>>
>>> During this import, I got following message in the syslog from the
>>> guest and the guest system was temporary hanging:
>>>
>>> Nov  3 16:18:14 test01: [ 6258.766426] sd 0:0:0:0: [sda] ABORT operation
>>> started
>>> Nov  3 16:18:14 test01: [ 6258.766428] sd 0:0:0:0: ABORT operation failed.
>>> Nov  3 16:18:14 test01: [ 6258.766432] sd 0:0:0:0: [sda] DEVICE RESET
>>> operation started
>>> Nov  3 16:18:14 test01: [ 6258.766460] sd 0:0:0:0: DEVICE RESET
>>> operation complete.
>>> Nov  3 16:18:14 test01: [ 6258.766652] scsi target0:0:0: control msgout:
>>> c.
>>> Nov  3 16:18:14 test01: [ 6258.766785] scsi target0:0:0: has been reset
>>> Nov  3 16:18:14 test01: [ 6258.766889] sd 0:0:0:0: [sda] BUS RESET
>>> operation started
>>> Nov  3 16:18:14 test01: [ 6258.769315] sym0: SCSI BUS reset detected.
>>> Nov  3 16:18:14 test01: [ 6258.776098] sym0: SCSI BUS has been reset.
>>> Nov  3 16:18:14 test01: [ 6258.776113] sd 0:0:0:0: BUS RESET operation
>>> complete.
>>> Nov  3 16:18:24 test01: [ 6268.776202] sym0: unknown interrupt(s)
>>> ignored, ISTAT=0x5 DSTAT=0x80 SIST=0x0
>>> Nov  3 16:18:55 test01: [ 6299.741617] sd 0:0:0:0: [sda] ABORT operation
>>> started
>>> Nov  3 16:18:55 test01: [ 6299.741624] sd 0:0:0:0: ABORT operation failed.
>>> Nov  3 16:18:55 test01: [ 6299.741626] sd 0:0:0:0: [sda] ABORT operation
>>> started
>>> Nov  3 16:18:55 test01: [ 6299.741628] sd 0:0:0:0: ABORT operation failed.
>>> Nov  3 16:18:55 test01: [ 6299.741632] sd 0:0:0:0: [sda] DEVICE RESET
>>> operation started
>>> Nov  3 16:18:55 test0l: [ 6299.741654] sd 0:0:0:0: DEVICE RESET
>>> operation complete.
>>> Nov  3 16:18:55 test0l: [ 6299.741794] scsi target0:0:0: control msgout:
>>> c.
>>> Nov  3 16:18:55 test0l: [ 6299.741892] scsi target0:0:0: has been reset
>>> Nov  3 16:18:55 test0l: [ 6299.741995] sd 0:0:0:0: [sda] BUS RESET
>>> operation started
>>> Nov  3 16:18:55 test0l: [ 6299.744359] sym0: SCSI BUS reset detected.
>>> Nov  3 16:18:55 test0l: [ 6299.751360] sym0: SCSI BUS has been reset.
>>> Nov  3 16:18:55 test0l: [ 6299.751388] sd 0:0:0:0: BUS RESET operation
>>> complete.
>>> Nov  3 16:19:05 test0l: [ 6309.752287] sym0: unknown interrupt(s)
>>> ignored, ISTAT=0x5 DSTAT=0x80 SIST=0x0
>>> Nov  3 16:21:02 test0l: [ 6426.765054] sd 0:0:0:0: [sda] ABORT operation
>>> started
>>> Nov  3 16:21:02 test0l: [ 6426.765059] sd 0:0:0:0: ABORT operation failed.
>>> Nov  3 16:21:02 test0l: [ 6426.765065] sd 0:0:0:0: [sda] DEVICE RESET
>>> operation started
>>>
>>> In the syslog from proxmox are no messages seen.
>>>
>>> What does it mean, how can i fix it?
>>>
>>> Thanks for help an proxmox!
>>>
>>> Kindly regards, Meike
>>> _______________________________________________
>>> pve-user mailing list
>>> pve-user at pve.proxmox.com
>>> http://pve.proxmox.com/cgi-bin/mailman/listinfo/pve-user
>>
>> The 'sd' errors are related to disk .  so check the disk.
>> and  in case this has not been done,  backup your kvm's and openvz's and
>> copy off of that system.
>>
>> if the disk needs to be replaced, it is easy to reinstall when there are
>> backups.
>>
>>
>
>
> The error messages are from the virtual disk in the guest. No error
> messages seen in the syslog from the host  (proxmox) system with the
> real hardware disk.
>
> Thanks Meike
> _______________________________________________
> pve-user mailing list
> pve-user at pve.proxmox.com
> http://pve.proxmox.com/cgi-bin/mailman/listinfo/pve-user
>
>
>
>
>
>
> _______________________________________________
> pve-user mailing list
> pve-user at pve.proxmox.com
> http://pve.proxmox.com/cgi-bin/mailman/listinfo/pve-user
>