search for: ata_id

...booting 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 09:05:02 daisy ata_id[21644]: HDIO_GET_IDENTITY failed for '/dev/sdb' Apr 22 09:10:01 daisy ata_id[22282]: HDIO_GET_IDENTITY failed for '/d...

...penvz 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're running a 3ware controller in it. What exactly is /dev/sdb? I don't know 3ware so I can only guess but it looks to me like at least one of your drives is havi...

...; 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're running a > 3ware controller in it. > > What exactly is /dev/sdb? I don't know 3ware so I can only guess but it > looks to me...

...t;> 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're running a >> 3ware controller in it. >> >> What exactly is /dev/sdb? I don't know 3ware so I can only guess...

...ces! Starting udevd 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" Wai...

The following patches introduce support for multipath and cciss devices to the ovirt-node and node-image. Comments are appreciated. These patches assume that the 3 patches (2 node, 1 node-image) from Joey are all incorporated. Mike

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

...Mounting /dev for udev ... [ 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 ......

...yright (c) 2015 FUJITSU LIMITED [ 3.965913] audit: type=1130 audit(1483728791.839:9): pid=1 uid=0 auid=4294967295 ses=4294967295 subj=kernel msg='unit=plymouth-start comm="systemd" exe="/usr/lib/systemd/systemd" hostname=? addr=? terminal=? res=success' [ 3.982307] ata_id (418) used greatest stack depth: 12656 bytes left [ 3.998001] usb-storage 2-4:1.0: USB Mass Storage device detected [ 4.013086] scsi host1: usb-storage 2-4:1.0 [ 4.013518] usbcore: registered new interface driver usb-storage [ 4.018946] usbcore: registered new interface driver uas [...