➜ ~ virsh change-media ide sda -update /var/lib/ libvirt/ images/ BOOT.isoĮrror: Failed to complete action update on media Restore it from the saved file by virsh restoreĮrror: Failed to complete action eject on mediaĮrror: internal error: unable to execute QEMU command 'blockdev- remove- medium' : Tray of device 'scsi0-0-0-0' is not open Hello, I found the cdrom media cannot be updated or eject after retore Libvirt-2-format: /tmp/blocktest/cd.iso (raw, read-only) Libvirt-3-format: /var/lib/libvirt/images/systemrescuecd-amd64-6.1.2.iso (raw, read-only) $ virsh qemu-monitor-command -hmp upstream info block Same situation happens on 'reboot' initiated from the guest OS. Tray state in the XML matches the tray state in qemu. Removable device: not locked, tray closed Libvirt-2-format: /tmp/blocktest/ cd.iso (raw, read-only) Libvirt-3-format: /var/lib/ libvirt/ images/ systemrescuecd- amd64-6. $ virsh qemu-monitor- command -hmp upstream info block issue 'eject' in the guest OS on the cdromĤ. Version-Release number of selected component (if applicable):Ģ. State of cdrom tray is not updated (changed to 'closed') when resetting a VM, but the internal tray state in qemu is actually changed to 'closed' without emission of the tray-changed event. Jun 1 17:03:21 dev2cn02 java: WARN (agentRequest- Handler- 3:) (logid:c470e790) Failed to attach device to i-2-354-VM: internal error: unable to execute QEMU command 'blockdev- remove- medium' : Tray of device 'ide0-1-0' is not open Jun 1 17:03:21 dev2cn02 java: libvirt: QEMU Driver error : internal error: unable to execute QEMU command 'blockdev- remove- medium' : Tray of device 'ide0-1-0' is not open Jun 1 17:03:21 dev2cn02 libvirtd: internal error: unable to execute QEMU command 'blockdev- remove- medium' : Tray of device 'ide0-1-0' is not open Maybe this has something to do with how the other drive is shown.Attache a centos/ubuntu iso to VM,after os installation complete, after os reboot, I want to detach iso from VM. This time I booted SystemRescueCd so that it's fully loaded to memory. Same error also for sda2 and sda3 when attempted to mount. Mount: special device /dev/sda1 does not exist Note: The USB drive mentioned above is now mapped as /dev/sdbĪttempts to mount the device give me the following output /root % mount -r /dev/sda1 /mnt/windows Is this a lost cause and the hardrive is simply busted? Or is there something else I can do to discover the drive for mounting it and saving the data?Īnother boot with SystemRescueCd and fdisk -l now shows the drive as Disk /dev/sda: 250.1 GB, 250059350016 bytesĢ55 heads, 63 sectors/track, 30401 cylinders, total 488397168 sectors Lshw gives me some output for SATA controller and such, but can't really say what to look for in here. I also skimmed through dmesg and tried to grep it for "hda", but found no indication of the hardrive. I/O size (minimum/optimal): 512 bytes / 512 bytes Sector size (logical/physical): 512 bytes / 512 bytes Here the DataTraveler 2.0 is my bootable USB stick with the SystemRescueCd on it.įdisk -l Disk /dev/sda: 512 MB, 512753664 bytesĥ6 heads, 32 sectors/track, 558 cylinders, total 1001472 sectors I cannot get any sight of the harddrive, below are the commands I've executed and their outputįsarchiver probe simple Well, I booted the computer with my SystemRescueCd USB installation in order to take a looksy. I suspect that the harddrive is corrupted or broken. My laptop suddendly quit working, simply boots no longer, giving an error stating that it cannot find a disk where to boot from.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |