search for: hdio_get_identity

At the present moment, my guest is running inside qemu and host is kvm intel, running Ubuntu 14.04, kernel is 4.3.0 stable. From within the guest, when I run "hdparm -i /dev/sdb" on the guest, I get: HDIO_GET_IDENTITY failed: Invalid argument as the error,but on the host, I will get the full harddisk/SSD info. Can I know how to resolve this so that the output is the same for both host and guest? My strace of hdparm from within the guest (just "-e ioctl" is traced): ioctl(3, HDIO_GET_MULTCOUNT, 0x61...

Hello Everyone, Since rebooting my Centos 6.10 Openvz server "daisy" yesterday, I am getting horrible system performance.? /var/log/messages is full of HDIO_GET_IDENTITY failed for /dev/sdb.? The latest entries look like this: Apr 22 08:51:32 daisy kernel: [141224.655699] CT: 1005: stopped Apr 22 08:55:04 daisy ata_id[21513]: HDIO_GET_IDENTITY failed for '/dev/sdb' Apr 22 09:00:05 daisy ata_id[21584]: HDIO_GET_IDENTITY failed for '/dev/sdb' Apr 22...

> Hello Everyone, > > Since rebooting my Centos 6.10 Openvz server "daisy" yesterday, I am > getting horrible system performance.? /var/log/messages is full of > HDIO_GET_IDENTITY failed for /dev/sdb.? The latest entries look like this: > > Apr 22 08:51:32 daisy kernel: [141224.655699] CT: 1005: stopped > Apr 22 08:55:04 daisy ata_id[21513]: HDIO_GET_IDENTITY failed for > '/dev/sdb' Hi, You didn't tell us much about your hardware. It seems you'r...

>> Hello Everyone, >> >> Since rebooting my Centos 6.10 Openvz server "daisy" yesterday, I am >> getting horrible system performance.? /var/log/messages is full of >> HDIO_GET_IDENTITY failed for /dev/sdb.? The latest entries look like >> this: >> >> Apr 22 08:51:32 daisy kernel: [141224.655699] CT: 1005: stopped >> Apr 22 08:55:04 daisy ata_id[21513]: HDIO_GET_IDENTITY failed for >> '/dev/sdb' > > Hi, > > You didn't tell us m...

...our looking for? On 4/22/2020 10:08 AM, Simon Matter via CentOS wrote: >>> Hello Everyone, >>> >>> Since rebooting my Centos 6.10 Openvz server "daisy" yesterday, I am >>> getting horrible system performance.? /var/log/messages is full of >>> HDIO_GET_IDENTITY failed for /dev/sdb.? The latest entries look like >>> this: >>> >>> Apr 22 08:51:32 daisy kernel: [141224.655699] CT: 1005: stopped >>> Apr 22 08:55:04 daisy ata_id[21513]: HDIO_GET_IDENTITY failed for >>> '/dev/sdb' >> Hi, >> >&g...

...Creating devices Loading xennet netfront: Initialising virtual ethernet driver. Loading xenblk Registering block device major 3 hda:Loading dm-mod <6>device-mapper: 4.5.0-ioctl (2005-10-04) initialised: dm-devel@redhat.com unknown partition table Loading dm-snapshot hdb:ata_id[474]: main: HDIO_GET_IDENTITY failed for ''/dev/.tmp-3-0'' Waiting for /dev/mapper/control to appear: ok unknown partition table ata_id[485]: main: HDIO_GET_IDENTITY failed for ''/dev/.tmp-3-64'' Loading reiserfs Unable to find volume group "system" Waiting for device /dev//mnt/boot...

This is a resend of a previously sent patch-set. This patch-set deals with some of the style isues in blkvsc_drv.c. We also get rid most of the "dead code" in this file: 1) Get rid of most of the forward declarations in this file. The only remaining forward declarations are to deal with circular dependencies. 2) Get rid of most of the dead code in the file. Some of the

This is a resend of a previously sent patch-set. This patch-set deals with some of the style isues in blkvsc_drv.c. We also get rid most of the "dead code" in this file: 1) Get rid of most of the forward declarations in this file. The only remaining forward declarations are to deal with circular dependencies. 2) Get rid of most of the dead code in the file. Some of the

...ead code dealing with removable media devices. 2) There were multiple functions to retrieve information about the device. Since much of the code in these functions were identical, we have consolidated these functions into a single function. 3) Enable the ioctl code for handling HDIO_GET_IDENTITY 4) Cleanup the code for getting the geometry. 5) Cleanup code for retreiving device capacity; this has also fixed a bug with regards to presenting physical disks to the guest as an IDE disk. 6) General cleanup: simplify blkvsc_init_rw(), get rid of unnecessary DPRINT*() calls, ge...

...ead code dealing with removable media devices. 2) There were multiple functions to retrieve information about the device. Since much of the code in these functions were identical, we have consolidated these functions into a single function. 3) Enable the ioctl code for handling HDIO_GET_IDENTITY 4) Cleanup the code for getting the geometry. 5) Cleanup code for retreiving device capacity; this has also fixed a bug with regards to presenting physical disks to the guest as an IDE disk. 6) General cleanup: simplify blkvsc_init_rw(), get rid of unnecessary DPRINT*() calls, ge...

...ead code dealing with removable media devices. 2) There were multiple functions to retrieve information about the device. Since much of the code in these functions were identical, we have consolidated these functions into a single function. 3) Enable the ioctl code for handling HDIO_GET_IDENTITY 4) Cleanup the code for getting the geometry. 5) Cleanup code for retreiving device capacity; this has also fixed a bug with regards to presenting physical disks to the guest as an IDE disk. 6) General cleanup: simplify blkvsc_init_rw(), get rid of unnecessary DPRINT*() calls, ge...

...ead code dealing with removable media devices. 2) There were multiple functions to retrieve information about the device. Since much of the code in these functions were identical, we have consolidated these functions into a single function. 3) Enable the ioctl code for handling HDIO_GET_IDENTITY 4) Cleanup the code for getting the geometry. 5) Cleanup code for retreiving device capacity; this has also fixed a bug with regards to presenting physical disks to the guest as an IDE disk. 6) General cleanup: simplify blkvsc_init_rw(), get rid of unnecessary DPRINT*() calls, ge...

Hi there, I'm running a centos 5.2 (with a centos 5.3 kernel) on a box with a samsung 1To green edition, and this disk looks a bit slow to me and it's not recognized by hdparm : # hdparm -iI /dev/sda /dev/sda: HDIO_GET_IDENTITY failed: Invalid argument HDIO_DRIVE_CMD(identify) failed: Invalid argument # hdparm -tT /dev/sda /dev/sda: Timing cached reads: 2252 MB in 2.00 seconds = 1125.57 MB/sec Timing buffered disk reads: 94 MB in 3.05 seconds = 30.81 MB/sec I've got a samsung 640go on my desktop running ub...

...t for flush complete) failed: Inappropriate ioctl for device Timing buffered disk reads: 166 MB in 3.01 seconds = 55.07 MB/sec HDIO_DRIVE_CMD(null) (wait for flush complete) failed: Inappropriate ioctl for device [root at amd64 kai]# [root at amd64 kai]# /sbin/hdparm -i /dev/sda /dev/sda: HDIO_GET_IDENTITY failed: Inappropriate ioctl for device [root at amd64 kai]#

This patch-set deals with some of the style isues in blkvsc_drv.c. We also get rid most of the "dead code" in this file: 1) Get rid of most of the forward declarations in this file. The only remaining forward declarations are to deal with circular dependencies. 2) Get rid of most of the dead code in the file. Some of the functions in this file are place holders - they

This patch-set deals with some of the style isues in blkvsc_drv.c. We also get rid most of the "dead code" in this file: 1) Get rid of most of the forward declarations in this file. The only remaining forward declarations are to deal with circular dependencies. 2) Get rid of most of the dead code in the file. Some of the functions in this file are place holders - they

I upgraded my Centos 4.7 server last night. Switched from a cheaper 50$ asus motherboard to a Supermicro motherboard. I also, using dd, copied entire 500g SATA seagate drive to new 500g SATA seagate drive so as to have two copies in case something went wrong. Anyway, now I keep getting this error: Nov 21 06:08:33 server kernel: hda: status timeout: status=0xd0 { Busy } Nov 21 06:08:33 server

Suse 10.1 AMD64 Xen3 New to Xen. The dom0 is up and running. I am trying to get my first domU working. My approach is to use precompiled images from jailtime.org. After some manual tinkering with the .cfg file the domU proceeds to boot but stalls with the following error. I cannot get past this - any ideas ? Brian Using config file "/etc/xen/vm/vm1". Started domain vm1 Bootdata ok

...dev ... [ ok ] * Seeding /dev with needed nodes ... [ ok ] * Starting udevd ... [ ok ] * Populating /dev with existing devices through uevents ...ata_id[791]: main: HDIO_GET_IDENTITY failed for ''/dev/.tmp-3-0'' [ ok ] * Letting udev process events ... [ ok ] * Finalizing udev configuration ... [ ok ] * Mounting devpts at /dev/pts ......