HP LaserJet 5200 - Yet another "GenericClass: waiting for device" problem

I have an HP LaserJet 5200 that worked until today. I have changed nothing and replaced nothing and now I'm getting the ol' "GenericClass: waiting for device." It worked when I first went to 10.5.4, so that's not the issue. The connection obviously works because the computer recognizes the printer. I've deleted and reinstalled everything under the sun related to printing to no avail.
Any ideas? I'm hoping I don't have a $2000 paper weight.
Thanks in advance
Message was edited by: Wesley Johnson

Several Leopard users are reporting that HP printers no longer work with USB-parallel adapter cables. I don't know why.
The best solution is to put the printer on the network, either by buying the jetdirect card that fits that model (on eBay), or by buying a used parallel port print server.

Similar Messages

  • Gimp-Print Driver GenericClass: Waiting for device

    I am running OS X 1.4.8 and I have an HP Photosmart printer connected via USB. I installed the HP print driver and associated utilities. I have added the printer through the Printer setup utility and selected the Photosmart 1100 series driver, which uses the gimp-print 5.0.0 driver.
    I can connect to the printer through HP's test and calibration utility and I can access the printer, send test pages, calibration etc. However, when sending a plain text file or any other file through the normal print driver, Nothinig prints. If you open the print monitor, it shows the message " GenericClass: waiting for device". I attempted to replace the USB cable and connect to another USB port, when you start the printer again it displays: "GIMP-PRINT: Ready to Print" and then the "GenericClass: Waiting for device" message.
    I am stumped on where to go next.
    Any help would be appreciated.
    Thanks

    I fixed my issue with the HP 3180 printer!! Here's what I did:
    1. I followed the HP document that I posted earlier step by step.
    2. I downloaded the latest drivers/software from HP, reset the printer queues and then tried to add the printer. This did not work at all.
    3. I took a look at the error log and found this:
    E [19/Nov/2007:21:51:31 -0500] LoadAllClasses: Unable to open /private/etc/cups/classes.conf - No such file or directory
    I went out on the MacWorld boards and found that the file in the error is deleted when the printer queues are cleared and recreated when the printer is initialized. So I'm not sure the issue is related to the message.
    Since my issues started after I applied the update from Apple from the auto software update that popped up on my MacBook, I decided to try to fix it by downloading the update directly from Apple.com and reapplying it again just in case something was hosed up with the auto software update:
    http://www.apple.com/downloads/macosx/apple/macosx_updates/macosx10411comboupdat eintel.html
    After it ran, I installed the printer software and drivers and the C3180 re-established connections and printing & scanning work perfect again. Hope this helps!

  • "WAITING FOR DEVICE" problem for Map Loader 2.0.2

    i'm sure many have had that problem, but doing a search on topics doesn't seem to produce an answer. if you have resolved that issue please post again your solution here
    Thanks
    Solved!
    Go to Solution.

    Open Nokia Map application, go online whether through through your wireless network if your phone is equipped with or through your ordinary 3G or paid internet connection, downloading of very small amount of Data as about 300 KB is enough to "stamp" your memory card with identification file called QF file then the the solution is simply the following:
    If your phone is hacked or you are able to access the following on your memory card:
    (Memory Card drive):\private\20001f63\diskcache
    copy the file named QF from the above folder and install it on the root of your memory drive.
    The excute Map loader (doesn't make difference whether PC suite or Data transfer) it will be identified and then you can download whatever Map you want.

  • "waiting for device"

    I have tried to print from my MacBook to my HP Photosmart 1215 without consistent success. I'm most likely to get the following error message "GenericClass: waiting for device." I downloaded the latest HPPhotosmart_Installer10.2-10.4.dmg, which eventully gives me a choice between Photosmart 1000 and 1100 Gimp-Print 5.0.0 beta drivers. (I chose the Photosmart 1100.) When I hit print, it starts the Gimp-Print driver, says it has reached 18% of the document, and stalls with the "waiting" message mentioned above. How do I get this all to work together? Thanks, Tom.

    Whoa -- slow down.
    Do not attempt to install any new version of CUPS - that is already part of OS X and if you try to update that you will be sorry!
    The linux-foundation files are STANDARD, OS X .DMG installer files -- don't do any compiling or even think about Unix when you download them and install them.
    If in fact you are just trying to print with the printer directly connected via USB, I don't know why you are doing any of that. That is what the HP driver was designed for. Let's just try some generic OS X printing fixes:
    Delete and re-ADD the printer(s) in Printer Setup.
    Repair permissions (Disk Utility).
    Reset Printing System (new in Tiger) - In Printer Setup, click this menu item found just above Quit Printer Setup.
    Download the Combination Updater from Apple, use it to re-Update OS X.
    Try Printer Setup Repair from www.fixamac.net.
    Use a Disk Utility like Disk Warrior to repair the HD -- or, put in your install DVD and restart while holding the c key. DO NOT start the installer - instead, find Disk Utility in the top (Finder) menus and use it to repair the hard drive.

  • Hp LaserJet 1200 Generic Class: Waiting for device

    I have 2 computers that I want to print to my hp Laserjet 1200 printer. We are using an iogear 4-port usb 2.0 sharing switch. One computer prints fine but the other always displays a message "Generic Class: Waiting for device." Help!

    Both computers have the printer driver installed. The usb device does not have a driver to install. You just plug in the usb cords to each computer and the printer. You only install a driver if using a pc operating system.

  • YAIS - Yet Another Installation Script for Archlinux

    I wrote this script today and placed it in AUR. It can show you the way and make it easier to install an archlinux system.

    orschiro wrote:
    https://aur.archlinux.org/packages/yais/
    Can you provide some more information?
    Your README is not very extensive:
    yais
    Yet another installation script (for archlinux)
    I updated the README, and added a TODO to the git repo. I also rewrote the PKGBUILD. It will be OK now.

  • "Waiting for device to become ready" can't burn additional copies

    I created an iMovie and burned about six copies on iDVD. When i went to put in the seventh disk it sort of froze up with the "Waiting for device to become ready" message never going away. I attempted to shut everything down, even turned the computer off for awhile thinking maybe it was overheated but several hours later its doing the same thing. It will burn the first copy but get hung up when attempting to burn additional ones. Any suggestions???

    It's often recommended areound here to let the optical drive cool down after burning 3-4 disks in a row.
    See if you can burn any kind of disk via the Finder to make sure the drive is OK.  Also I suggest you follow this workflow for future projects:
    Once you have the project as you want it save it as a disk image via the  File ➙ Save as Disk Image  menu option.  This will separate the encoding process from the burn process. 
    To check the encoding mount the disk image and launch DVD Player and play it.  If it plays OK with DVD Player the encoding was good.
    Then burn to disk with Disk Utility or Toast at the slowest speed available (2x-4x) to assure the best burn quality.  Always use top quality media:  Verbatim, Maxell or Taiyo Yuden DVD-R are the most recommended in these forums.
    The save as disk image as mishmumken recommended will save you from having to reencode the project if you want to burn another copy at a later date.  It also lets you verify the encoding process before committing the project to disk.
    OT

  • Force fsck on boot and timeout waiting for device issues [SOLVED]

    Archlinux starts checking fs on every boot since linux and systemd packages were updated last night.
    systemd --->213-5
    linux ---->3.14.5-1
    Another issue appears with last update
    Timed out waiting for device dev-disk-by\x2duuid-9f780ada\x2d0671\
    Dependency failed for /dev/disk/by-uuid/9f780ada-0671-43d8-b036-f9
    Dependency failed for Swap.
    I have this issue on my laptop which was updated yesterday.I have also desktop running archlinux again I've just checked out the systemd and linux versions.The systemd package is not the latest one it's 212-3.I havent any problem on that machine.I guess systemd is responsible of this cause.
    I've just reboot and realized that systemd-fsck says Super block last write is in the future.Date and time is correct in BIOS same as on linux
    Last edited by gecici90 (2014-06-05 21:10:52)

    I had the same problem, I get in the recovery console after forced fsck.
    But downgrading systemd and systemd-sysvcompat to their previous version made it all work back again.
    The sorted list of the upgraded packages:
    [2014-06-05 21:11] [PACMAN] installed libx264 (1:142.20140311-4)
    [2014-06-05 21:11] [PACMAN] upgraded btrfs-progs (3.14.1-1 -> 3.14.2-2)
    [2014-06-05 21:11] [PACMAN] upgraded cifs-utils (6.2-1 -> 6.3-1)
    [2014-06-05 21:11] [PACMAN] upgraded imagemagick (6.8.9.1-2 -> 6.8.9.1-3)
    [2014-06-05 21:11] [PACMAN] upgraded filesystem (2013.05-2 -> 2014.05-2)
    [2014-06-05 21:11] [PACMAN] upgraded lib32-libdbus (1.8.0-1 -> 1.8.2-1)
    [2014-06-05 21:11] [PACMAN] upgraded libproxy (0.4.11-2 -> 0.4.11-3)
    [2014-06-05 21:11] [PACMAN] upgraded libpurple (2.10.9-1 -> 2.10.9-2)
    [2014-06-05 21:11] [PACMAN] upgraded libsystemd (212-3 -> 213-5)
    [2014-06-05 21:11] [PACMAN] upgraded libwbclient (4.1.7-1 -> 4.1.8-1)
    [2014-06-05 21:11] [PACMAN] upgraded openssl (1.0.1.g-1 -> 1.0.1.h-1)
    [2014-06-05 21:11] [PACMAN] upgraded perl (5.18.2-2 -> 5.20.0-2)
    [2014-06-05 21:11] [PACMAN] upgraded perl-xml-parser (2.41-4 -> 2.41-5)
    [2014-06-05 21:11] [PACMAN] upgraded perl-yaml-syck (1.27-1 -> 1.27-2)
    [2014-06-05 21:11] [PACMAN] upgraded pidgin (2.10.9-1 -> 2.10.9-2)
    [2014-06-05 21:11] [PACMAN] upgraded postgresql-libs (9.3.4-1 -> 9.3.4-2)
    [2014-06-05 21:11] [PACMAN] upgraded python2 (2.7.6-3 -> 2.7.7-1)
    [2014-06-05 21:11] [PACMAN] upgraded smbclient (4.1.7-1 -> 4.1.8-1)
    [2014-06-05 21:11] [PACMAN] upgraded subversion (1.8.9-1 -> 1.8.9-2)
    [2014-06-05 21:11] [PACMAN] upgraded systemd (212-3 -> 213-5)
    [2014-06-05 21:11] [PACMAN] upgraded systemd-sysvcompat (212-3 -> 213-5)
    [2014-06-05 21:11] [PACMAN] upgraded x264 (1:142.20140311-1 -> 1:142.20140311-4)
    [2014-06-05 21:11] [PACMAN] upgraded xchat (2.8.8-13 -> 2.8.8-14)
    [2014-06-05 21:11] [PACMAN] upgraded xfconf (4.10.0-3 -> 4.10.0-4)
    Downgrading systemd and systemd-sysvcompat makes my computer boots normally:
    [2014-06-05 21:43] [PACMAN] Running 'pacman -U /var/cache/pacman/pkg/systemd-212-3-x86_64.pkg.tar.xz /var/cache/pacman/pkg/systemd-sysvcompat-212-3-x86_64.pkg.tar.xz'
    [2014-06-05 21:43] [PACMAN] downgraded systemd (213-5 -> 212-3)
    [2014-06-05 21:43] [PACMAN] downgraded systemd-sysvcompat (213-5 -> 212-3)

  • Timed out waiting for device sys-subsystem-net-devices-enp69s0.device

    Hi all,
    Since quite some time I have been waiting for Arch Linux to startup (and shutdown), and today I wanted to figure out what was going wrong. I found out that I could find the boot log file with journalctl, and this seems to be the issue:
    Oct 13 21:01:52 localhost systemd[1]: Job sys-subsystem-net-devices-enp69s0.device/start timed out.
    Oct 13 21:01:52 localhost systemd[1]: Timed out waiting for device sys-subsystem-net-devices-enp69s0.device.
    Oct 13 21:01:52 localhost systemd[1]: Dependency failed for dhcpcd on enp69s0.
    Oct 13 21:01:52 localhost systemd[1]: Starting Network.
    Oct 13 21:01:52 localhost systemd[1]: Reached target Network.
    Oct 13 21:01:52 localhost systemd[1]: Mounting /mnt/homesrv/storage...
    Now, enp69s0 is my LAN network interface, which I barely use, and my WLAN connection is handled by NetworkManager. However, I can't find out what I'm supposed to do to stop this behaviour. I tried:
    systemctl disable sys-subsystem-net-devices-enp69s0.device
    But that does not seem to solve anything. Can anyone help me out?
    Last edited by Hmail (2013-10-13 19:09:53)

    Andreaskem wrote:Maybe try "systemctl disable [email protected]".
    That did the trick! I didn't want to disable the device because I might use it once in a while.
    The shutdown issue is not solved yet, but that seems to be an issue with a samba share that is unmounted after the network services are shutdown. I'll delve in the wiki to figure out how to fix that. But for now, I can at least start my machine up within seconds. Thanks a lot!

  • [SOLVED] dmraid "Timed out waiting for device" at boot

    Created a bug report with solution proposal: https://bugs.archlinux.org/task/33166
    I created a virtual machine to demonstrate the problem
    https://docs.google.com/open?id=0B40Hp1 … WZUQ21xZk0
    The root and the other mount points are all on one raid disk. Although the root mounts quickly, other mount points cause timeouts at boot time.
    dmraid prints that all /dev/mapper/isw_* devices are created.
    I think /dev/disk/by-uuid/* links are created too, but for some reason systemd doesn't see them.
    After boot I can execute "mount -a" without errors.
    here's my fstab:
    tmpfs /tmp tmpfs nodev,nosuid 0 0
    UUID=e89249d8-49a5-415b-8f9b-97de5cfbe82d / ext3 defaults
    UUID=c37f8bdd-3d6c-495f-bf8a-5ef059e55254 swap swap defaults 0 0
    UUID=91988343-dd89-43b9-8975-babb0b9510a2 /media/ARCHLINUXNEW ext4 nofail 0 1
    UUID=62C813E9C813B9ED /media/distrpart ntfs-3g rw,nofail
    UUID=E0A1-D623 /media/realboot vfat rw,codepage=866,iocharset=utf8,umask=002,noatime,nofail
    # journalctl -b
    Dec 15 00:25:24 localhost kernel: firewire_core 0000:05:03.0: created device fw0: GUID 0011d800017a5dd7, S400
    Dec 15 00:26:50 localhost systemd[1]: Job dev-disk-by\x2duuid-E0A1\x2dD623.device/start timed out.
    Dec 15 00:26:50 localhost systemd[1]: Timed out waiting for device dev-disk-by\x2duuid-E0A1\x2dD623.device.
    Dec 15 00:26:50 localhost systemd[1]: Dependency failed for /media/realboot.
    Dec 15 00:26:50 localhost systemd[1]: Job media-realboot.mount/start failed with result 'dependency'.
    Dec 15 00:26:50 localhost systemd[1]: Job dev-disk-by\x2duuid-E0A1\x2dD623.device/start failed with result 'timeout'.
    Dec 15 00:26:50 localhost systemd[1]: Job dev-disk-by\x2duuid-62C813E9C813B9ED.device/start timed out.
    Dec 15 00:26:50 localhost systemd[1]: Timed out waiting for device dev-disk-by\x2duuid-62C813E9C813B9ED.device.
    Dec 15 00:26:50 localhost systemd[1]: Dependency failed for /media/distrpart.
    Dec 15 00:26:50 localhost systemd[1]: Job media-distrpart.mount/start failed with result 'dependency'.
    Dec 15 00:26:50 localhost systemd[1]: Job dev-disk-by\x2duuid-62C813E9C813B9ED.device/start failed with result 'timeout'.
    Dec 15 00:26:50 localhost systemd[1]: Job dev-disk-by\x2duuid-91988343\x2ddd89\x2d43b9\x2d8975\x2dbabb0b9510a2.device/start timed out.
    Dec 15 00:26:50 localhost systemd[1]: Timed out waiting for device dev-disk-by\x2duuid-91988343\x2ddd89\x2d43b9\x2d8975\x2dbabb0b9510a2.device.
    Dec 15 00:26:50 localhost systemd[1]: Dependency failed for /media/ARCHLINUXNEW.
    Dec 15 00:26:50 localhost systemd[1]: Job media-ARCHLINUXNEW.mount/start failed with result 'dependency'.
    Dec 15 00:26:50 localhost systemd[1]: Dependency failed for File System Check on /dev/disk/by-uuid/91988343-dd89-43b9-8975-babb0b9510a2.
    Dec 15 00:26:50 localhost systemd[1]: Job systemd-fsck@dev-disk-by\x2duuid-91988343\x2ddd89\x2d43b9\x2d8975\x2dbabb0b9510a2.service/start failed with result 'dependency
    Dec 15 00:26:50 localhost systemd[1]: Job dev-disk-by\x2duuid-91988343\x2ddd89\x2d43b9\x2d8975\x2dbabb0b9510a2.device/start failed with result 'timeout'.
    Dec 15 00:26:50 localhost systemd[1]: Dependency failed for /dev/disk/by-uuid/c37f8bdd-3d6c-495f-bf8a-5ef059e55254.
    Dec 15 00:26:50 localhost systemd[1]: Reached target Swap.
    Note the 1.5 minute pause
    # mount | grep /dev/mapper
    /dev/mapper/isw_ebaifefjbf_Volume0p9 on / type ext3 (rw,relatime,stripe=64,data=ordered)
    /dev/mapper/isw_ebaifefjbf_Volume0p1 on /media/realboot type vfat (rw,noatime,fmask=0002,dmask=0002,allow_utime=0020,codepage=cp866,iocharset=utf8,shortname=mixed,errors=remount-ro)
    /dev/mapper/isw_ebaifefjbf_Volume0p8 on /media/ARCHLINUXNEW type ext4 (rw,relatime,stripe=64,data=ordered)
    /dev/mapper/isw_ebaifefjbf_Volume0p5 on /media/distrpart type fuseblk (rw,nosuid,nodev,relatime,user_id=0,group_id=0,allow_other,blksize=4096)
    Last edited by leniviy (2012-12-22 16:06:25)

    I've ran into exactly same problem lately, but finally solved it.
    Setup: Intel Fake RAID, mirror, partitioned as:
    /dev/mapper/isw_dfjeffgfaj_rootvol1 /boot
    /dev/mapper/isw_dfjeffgfaj_rootvol2 /
    /dev/mapper/isw_dfjeffgfaj_rootvol3 /home (dm-crypted)
    In /etc/fstab i had following mountpoints:
    # file /etc/fstab
    /dev/mapper/isw_dfjeffgfaj_rootvolp2 / ext4 rw,relatime,data=ordered 0 1
    /dev/mapper/isw_dfjeffgfaj_rootvolp1 /boot ext4 rw,relatime,data=ordered 0 2
    and boot hung on waiting for /dev/mapper/isw_dfjeffgfaj_rootvolp1. Solution involves changing dev path to UUID:
    # file /etc/fstab
    /dev/mapper/isw_dfjeffgfaj_rootvolp2 / ext4 rw,relatime,data=ordered 0 1
    UUID=44809529-11d9-4f53-9652-7b97ed077225 /boot ext4 rw,relatime,data=ordered 0 2
    For some reason symlinks /dev/mapper/isw* are not present during systemd mount.

  • Stuck on waiting for device to become ready...

    I did a slide show on iDVD now I'm trying to burn it on a Phillips dvd but it reads waiting for device to become ready. this continues & it does not burn the dvd. I tried the save as disk image but the same thing happens. the utility was no help on getting it started

    Hi Don't:
    Just assuming here (which is always dangerous)...
    Is there any audio associated with your slideshow?
    Sue
    PS Verbatim DVD-R (you are using DVD-R, right?) is about the best there is....

  • "waiting for device to become ready" then ejects

    Hello,
    I have two music videos set up as chapters and am trying to burn a DVD with this.
    Everything plays fine when "reviewing" then when I hit "burn dvd" it asks for a recordable disc. I put in a DVD-R disc, which has plenty of room on it, and it accepts it. Then is says "waiting for device to become ready" spins it around, stops it, spins it around, stops it, and ejects the disc and says "no disc in drive. please insert a recordable disc".
    Yes, I have a DVD superdrive that can burn DVDs. I do not understand what is going on!!!

    says "no disc in drive. please insert a recordable disc"
    Either your media is bad or your burner is bad.
    Are you certain the media has never been used? What brand and rated burn speed is the media? To test the media and the burner independent of iDVD, try burning a data DVD from the finder.
    F Shippey

  • (Urgent) During CWM flashing - its stuck on "waiting for device"!

    Hi,
    I'm on CWM flashing process...and in the last few mint's it's suck on the CMD - "waiting for device".
    On tablet screen - dark screen with a yellow USB sign.
    What happend?
    What could be the reason for that?
    How can i resolve it?
    Please see the screenshot::
    Thank you!

    Thats wierd...bc's in 100% i installed the fastboot drivers successfully...but when i hooked now my tablet to the pc (while its on fastboot menu) the fastboot is with yellow mark!
    I followed anika200's [HowTo] A2109 Fastboot and did ot successfully.
    What i dont understand is:
    When i did anika200's guide - and i connected the tab' to the pc, in the device manager i've see "A2109"...now, i see "fastboot".
    Regarding the fastboot mode (maybe i didnt understand something?):
    In the fastboot menu - what do i need to chose there (if all)?
    Thanks!
    UPDATE:
    I just try'd updating now fastboot drivers again and i got a message that say's: 
    What is weird, is that it found the drivers without needed to nevigate to the Letools directory...

  • Imessage/facetime waiting for activation problem on a deactivated iphone 5

    Hello people(:
    I was just wondering if anyone out there know how to fix the waiting for activation problem for iPhone 5 on 6.1.4
    My iPhone 5 is deactivated so it has no service on it. It has a sim card but the sim card doesn't have service and I'm guessing thats the problem.
    But i just wanna make sure that it is or if anyones got a solution.
    Thanks(:
    Need answers please

    Well I did a restore of my iPhone 5 (deactivated) using my last iPhone 6 backup (activated) and iMessage still failed to activate.  It's funny because this worked on my old iPhone 4.  I don't know what else I did different.
    Does anyone know why Apple does this?  Why are they against us using iMessage on a deactivated iPhone?

  • XENBUS: Waiting for devices to initialise: 295s...290s.....

    We are using Oracle VM 2.2 for Virtualization.
    In one of the VM machine who's OS is OEL 5.5
    To boost the performance of the VM. i converted HVM to PVHVM.
    reference : https://support.oracle.com/CSP/main/article?cmd=show&type=NOT&doctype=HOWTO&id=1137824.1
    After rebooting the vm machine i see there is some problem with devices initialisation
    logs from /var/log/messages
    Mar 6 22:31:51 OVM_MANAGER_3_0 kernel: XENBUS: Device with no driver: device/vbd/51712
    Mar 6 22:31:51 OVM_MANAGER_3_0 kernel: XENBUS: Device with no driver: device/vbd/5632
    Mar 6 22:31:51 OVM_MANAGER_3_0 kernel: XENBUS: Device with no driver: device/vif/0
    Mar 6 22:31:51 OVM_MANAGER_3_0 kernel: XENBUS: Device with no driver: device/console/0
    Mar 6 22:31:51 OVM_MANAGER_3_0 kernel: Initalizing network drop monitor service
    Mar 6 22:31:51 OVM_MANAGER_3_0 kernel: Write protecting the kernel read-only data: 484k
    Mar 6 22:31:51 OVM_MANAGER_3_0 kernel: Registering block device major 202
    Mar 6 22:31:51 OVM_MANAGER_3_0 kernel: xvda: xvda1 xvda2 xvda3
    Mar 6 22:31:51 OVM_MANAGER_3_0 kernel: XENBUS: Waiting for devices to initialise: 295s...290s...285s...280s...275s...270s...265s...260s...255s...250s...245s
    ...240s...235s...230s...225s...220s...215s...210s...205s...200s...195s...190s...185s...180s...175s...170s...165s...160s...155s...150s...145s...140s...135s...
    130s...125s...120s...115s...110s...105s...100s...95s...90s...85s...80s...75s...70s...65s...60s...55s...50s...45s...40s...35s...30s...25s...20s...15s...10s...
    5s...0s...
    Mar 6 22:31:51 OVM_MANAGER_3_0 kernel: XENBUS: Timeout connecting to device: device/vbd/5632 (local state 3, remote state 2)
    Is anyone of you had encountered this kind of problem.
    Please help me on this......................

    We are using Oracle VM 2.2 for Virtualization.
    In one of the VM machine who's OS is OEL 5.5
    To boost the performance of the VM. i converted HVM to PVHVM.
    reference : https://support.oracle.com/CSP/main/article?cmd=show&type=NOT&doctype=HOWTO&id=1137824.1
    After rebooting the vm machine i see there is some problem with devices initialisation
    logs from /var/log/messages
    Mar 6 22:31:51 OVM_MANAGER_3_0 kernel: XENBUS: Device with no driver: device/vbd/51712
    Mar 6 22:31:51 OVM_MANAGER_3_0 kernel: XENBUS: Device with no driver: device/vbd/5632
    Mar 6 22:31:51 OVM_MANAGER_3_0 kernel: XENBUS: Device with no driver: device/vif/0
    Mar 6 22:31:51 OVM_MANAGER_3_0 kernel: XENBUS: Device with no driver: device/console/0
    Mar 6 22:31:51 OVM_MANAGER_3_0 kernel: Initalizing network drop monitor service
    Mar 6 22:31:51 OVM_MANAGER_3_0 kernel: Write protecting the kernel read-only data: 484k
    Mar 6 22:31:51 OVM_MANAGER_3_0 kernel: Registering block device major 202
    Mar 6 22:31:51 OVM_MANAGER_3_0 kernel: xvda: xvda1 xvda2 xvda3
    Mar 6 22:31:51 OVM_MANAGER_3_0 kernel: XENBUS: Waiting for devices to initialise: 295s...290s...285s...280s...275s...270s...265s...260s...255s...250s...245s
    ...240s...235s...230s...225s...220s...215s...210s...205s...200s...195s...190s...185s...180s...175s...170s...165s...160s...155s...150s...145s...140s...135s...
    130s...125s...120s...115s...110s...105s...100s...95s...90s...85s...80s...75s...70s...65s...60s...55s...50s...45s...40s...35s...30s...25s...20s...15s...10s...
    5s...0s...
    Mar 6 22:31:51 OVM_MANAGER_3_0 kernel: XENBUS: Timeout connecting to device: device/vbd/5632 (local state 3, remote state 2)
    Is anyone of you had encountered this kind of problem.
    Please help me on this......................

Maybe you are looking for