Workstation hangs during boot from OVM Server CD

Newbie here. Downloaded OVM and created bootable CD just this afternoon.
The hardware is a Dell Precision 390 with 4gB RAM; 64bit technology (Intel EM64T); BIOS at 2.2.0; Intel Matrix Storage Manager (RAID5). Virtualization Technology option is "on".
When I boot the Precision, it stalls at the Intel Matrix Storage Manager screen as the boot CD is being accessed. No messages. Simply hangs with the system unresponsive to the hard connected keyboard.
Any hints regarding how to begin diagnosing will be greatly appreciated.

927071 wrote:
When I boot the Precision, it stalls at the Intel Matrix Storage Manager screen as the boot CD is being accessed. No messages. Simply hangs with the system unresponsive to the hard connected keyboard.Verify the md5sum of the downloaded ISO. If that matches, reburn the CD at a lower speed. Try booting the CD on another machine as well, to see if it's just this machine, or the CD itself that doesn't work.

Similar Messages

  • Ultra 5 Hangs During Boot

    My Ultra 5 hangs during boot at the following point....
    setting default ipv4 interface......
    I have tried resetting my router, unplugging the network cable, and nothing seems to work.
    John

    jmorrissey3, is this a system that just suddenly stopped working, or is this a "new" system (it's not like Ultra 5s are really new) that you're trying to bring up?
    If this is a new system for you to tinker with, you should just go ahead and reinstall the operating system. This will blow everything away, of course, but it's good experience if you've never done it before and it will guarantee that the system is clean.
    If the data on there must be retained, you can boot from CD-ROM, mount the / partition, and look at some of the configuration files to try to isolate the problem. I would agree that it either is set up for DHCP and there is no DHCP server or there is an invalid NFS mount that is trying to take place.

  • K8N Neo 2 Platinum -- Hanging during boot --RESOLVED--

    Heres the problem...
    My system will hang during boot at anytime, from bios initalization to full windows boot (No BSOD ever and where the pc hangs in the boot proccess is totally random). And the only way to get past the hang is do a soft reset. I have to restart my system up to 3 times before I get a good boot, but once the pc is up and running, it stay running till I shut it down. (no hangs)
    Now if I shut it down after the system has been running for a while, the pc will restart normally without any hangs. The hangs only occur after the pc has been down for a time.
    I have reseated all the connectors, the memory (even tried different slots), add-in cards, cpu.
    I have a clean install of Windows XP Pro (hard drives have been repartitioned and reformatted as NTFS)
    All fans are spinning up fine, all temps are within norm, power supply voltages are within norm.
    No phsysical signs of bad caps on the system board.
    I ran ran Memtest86 for 18 hours striaght with no errors.
    Ran CPU stress test with no problems.
    No IRQ,DMA,etc conflicts found.
    Windows records no errors during a freeze and I have checked for unwanted services/proccess as well.
    I have tried min install to no avail.
    Bois is retaining its settings (so bios battery is good)
    I do not over clock anything. Bios is set to discover all important setting automaticly. (Bios setting are the same now as they were 6 months ago)
    I am down to a possible cold solder joint on the system board?
    This problem started to occur about a month ago.
    If someone has seen this exact problem and has a resolution, well I would appreciate it if you passed along your knowladge 
    I am down to my last option of RMAing my system board. No. I have not replaced any components due to the fact I don't have extras lieing around nor can I spend the money just to troubleshoot :(
    Specs..
    Athlon 64 3500+
    2 gig (pqi TURBO 1GB 184-Pin DDR SDRAM DDR 400 (PC 3200) Unbuffered System Memory Model PQI3200-1024SB)  Ran in Dual config
    Geforce 6800  (BFG 6800 GT oc)
    Creative X-Fi XtremeMusic
    Antec NeoPower 480
    2 WD 36gig SATA Raptors in raid 0 (system partition)
    2 WD 120gig IDE  in raid 0 (data partition)
    Windows XP Pro
    all drivers and bios are manufacture ref and up-to-date.
    Ok I won't go into all the details of why I missed this but it turns out the northbridge heatsink fan had stopped spinning and thus the hangs during boot due to overheating (hhmmm, when I step back and look at this the symptoms point right to overheating).
    This also expains why after several attempts at booting up, once the pc was up it would run like a champ. The chip would of course overheat and cause random freezes. Now due to the placement of the chip and the design of the heatsink once there was enough airflow over the heatsink the chip would remain cool enough to prevent further freezing of the system.
    What helped to facilitate this is that I have a ducted fan system installed in the bottom of my case which directs a substantal amount of fresh air to the pci slots, the chip set and the AGI slot as well.
    So what have we learned class?
    1. check the obvious
    2. do a complete physical inspection of your system
    3. KISS  -- keep it simple stupid

    Is this your ram:
    Quote
    Part Number: PQI3200-1024SB
    Quality Control: Comprehensively and rigorously tested
    Package: 1024MB single pack
    Organization: 128M x 64-bit
    CAS Latency: 3-4-4-8
    Test Voltage: 2.6 V
    PCB Board: 8 Layers PCB
    Heat Spreader: Mirrored Black Copper
    Speed: DDR 400 MHz (PC3200)
    Type: 184-pin DDR SDRAM
    Error Checking: Non-ECC
    Registered/Unbuffered: Unbuffered
    Warranty: Lifetime
    This is a quote from MSI web site:
    Quote
    Main Memory
      • Supports dual channel DDR 266/333/400, using four 184-pin DDR DIMMs.
    • Supports the memory size up to 4GB 
    • Supports 2.5v DDR SDRAM DIMM 
    Due to the High Performance Memory design, motherboards or system configurations may or may not operate smoothly at the JEDEC (Joint Electron Device Engineering Council) standard settings (BIOS Default on the motherboard) such as DDR voltage, memory speeds and memory timing. Please confirm and adjust your memory setting in the BIOS accordingly for better system stability.
    Example: Kingston HyperX DDR500 PC4000 operates at 2.65V, 3-4-4-8, CL=3.
    For more information about specification of high performance memory modules, please check with your Memory Manufactures for more details.
    Manually adjust your ram voltage to 2.65 volts and then manually adjust your ram timings to 3-4-4-8-2T.
    If that does not work then do as Richard suggested and strip down to a bar-bone system, this is CPU+fan, 1 stick of ram (try other stick and different slots as one may be bad), graphic card and PS-2 keyboard, if it boots fine without any problems then add one device at a time until you find the problem.
    Post back results as there are more things one can try but lets start with the simple stuff and work up.

  • Error during disconnect from FTP Server

    Hi Everyone,
    Here's my problem:
    XI has stopped picking the messages from the repository of one of servers.  Though, we have checked the XI system and can find no problems from the infrastructure side.  The adapters also show no errors and the communication channels show no errors.
    We have also checked the log viewer in XI and found the following entry:
    "Error during disconnect from frtp server ABC, ignored: com.sap.xxx.adapter.file.ftp.XXXXXX: 421 Terminating Connection."
    This FTP error relates to what we FTP server says, "421 service not available, remote server has closed connection."
    We looked at the server side, the server is working fine.
    What do you think is the error? And do we resolve this one? I'm really clueless about this..Im thinking of just restarting the J2EE engine...
    Thanks,
    Grace

    Mary,
    This question would be more relevant to the Xi forum... but on googling the error code..
    http://help.globalscape.com/help/support/Error_Codes/FTP_Codes.htm
    Error 421 Service not available, closing control connection.
    Error 421 User limit reached
    Error 421 You are not authorized to make the connection
    Error 421 Max connections reached
    Error 421 Max connections exceeded
    Possible Solutions:
    You may receive a 421 error if the FTP server you are connected to limits the total number of connections available or limits the connections available to one user.  There are three things you can do:
    1. Limit the number of connections to any one FTP site by selecting Tools > Global Options > Connection and set "Per site max connections / transfers" to 1 (By default it will be set to 2).
    2. Remove items from the Transfer Queue.  The Transfer Queue is where you see items ready for transfer, in transit, or just transferred.  Sometimes the Queue Pane can become cluttered with unfinished transfers.  To clear the queue, right-click inside it and choose Remove All.
    Also try using an FTP manager like cuteFTP or something of that sort to see if you can open the connection - it could be related to the FTP settings...
    Arun
    Hope it helps....

  • Hang during import from camera or media - HELP!

    iPhoto hangs during import from camera or media reader. Works for 20 or more photos, then hangs. No response at all. Must force quit. After restarting the import, it will go further the next time, then hang again. And again. And again. Eventually the import completes. After that, all is OK until next import. VERY FRUSTRATING. Especially with 8GB media cards. ARRGH!
    I've tried rebuilding iPhoto library (all options). Using iPhoto 7.1.5 on OS X 10.5.6. 4GB ram, intel dual core.
    Help me Obe-Wan. You're my only hope.

    LarryHN wrote:
    Once you get your photos use your camera to reformat your media card - problems like this can be caused by a flaw in the card format
    And it is better to use a card reader to import yoru photos and after they are safely in iPhoto use your camera to reformat your card - this assues no data loss and keeps your card format fresh
    LN
    I usually use the media reader. After the imports started hanging is when I tried importing direct from the camera to see if it made a difference. No difference.
    I've reformatted the media. No difference. Still hangs on first import after reformat. Multiple media cards, all same result. Tried different USB ports, same result. Tried different media readers. Same result.

  • P205-s6237 Hangs during boot to recovery after replace HDD

    I replaced a bad HDD and the machine hangs during boot to the recovery disk. it gets past the inspecting screen and then hangs when the VISTA dots appear. the dots continue to scroll left to right but nothing ever happens. Any ideads on getting it past this point?

    I replaced a bad HDD and the machine hangs during boot to the recovery disk. it gets past the inspecting screen and then hangs when the VISTA dots appear. the dots continue to scroll left to right but nothing ever happens. Any ideads on getting it past this point?

  • Hanging on boot after upgrading server.app

    After upgrading to 10.9 Server.App my boot hangs at "/etc/rc.server: line 14: /etc/rc.server.firewall: No such file or directory" and won't boot into safe mode either. Anyone know how I can fix this without restoring from a backup?

    Cameron, thanks for your feedback.
    I'm on a 2011 iMac, with a DIY Fusion Drive (I added a SSD inside). I always had slow startups. I thought it was the custom Fusion Drive's fault, but now I know it was not.
    Now I can't boot at all, just after applying the most recent 10.9.2 security update. This is a software issue. The iMac was running Mountain Lion Server, then I upgraded to Mavericks but did not upgrade to Mavericks Server. However there were remains of the old 10.8 Server app.
    As I said, yesterday I deleted all those remains (booting from an external drive). However I forgot the most obvious thing: open that **** /etc/rc.server file and comment out line 14.
    This morning I booted the iMac again, in verbose mode. The message about /etc/rc.server was not there, at last, but fsck was launched and took a long time. I had to go to work, where I am now, and I don't know if fsck finished its work. I'll let you know...

  • Multiple cPCI Graphics cards - System Hangs during Boot

    We have 2 Kontron dual output CP332 cPCI graphics cards to install into a NI PXI rack in order to give us 4 graphics outputs.
    When one card is installed it acts as the Primary graphics card and it is required to disable to NI on-board graphics card in order for this to boot and function correctley.
    If a 2nd Kontron CP322 card is added the system will hang during WinXP boot, as it switches from VGA to SVGA mode.
    Disabling the 2nd card via device manager allows the system to boot.
    Re-enabling the 2nd card once booted, then configuring with the ATI driver application allows the 4 graphics output to work as expected.
    If the system is re-powered it will once again hang during WinXp booting.
    Is there anything that can be configured on the NI Embedded PC (BIOS) to prevent this ?
    Is there anything in windows that can be set to prevent this ?
    Can we control the windows device manager from labview in order to enable/disable the 2nd card after power-on and before shutdown.
    many thanks

    Hi Scott,
    I have some more information for you regarding your issue. We have tested the Kontron CP332 with the PXI-8196.
    However when we tested the setup, we had 3 monitors working, the on-board graphics and the dual output from the card.
    Until we get the on-board graphics working with a single CP332 I don't think we will get bot CP332's working.
    So these are the steps to get on-board graphics working with a single Kontron card the steps come from talking to our PXI Product Support Engineer:
    "The first thing you need to make sure is that you are using the
    driver for Windows XP, and not the one for Windows 2000. Here's a link
    to the driver download page:
    http://us.kontron.com/index.php?searchword=cp+332&id=363
    Notice that the first two driver downloads look just the same, but if
    you hover over them and look at the url, you'll notice that the first
    one is for Windows 2000 (w2k), and the second one is for Windows XP
    (wxp). So, just make sure you are using the second one. The PSE did
    mention that she was initially using the Win 2k driver, and was having
    some issues with it hanging and all. Here's the information she sent me
    about how she was able to get things working:
    "Here is the info. My controller has BIOS version 1.3 but have him try this first before updating the BIOS.
    The Kontron Board is the CP 332. I was able to get all three monitors working with the PXI-8196.
    Configuration steps:
    1) Insert both the controller and the kontron board in the chassis.
    Note: When the computer is starting it will give you the Windows boot
    up screen on the DVI 1 on the Kontron board and then give you the login
    screen on the monitor connected to the 8196 so make sure you still have
    a monitor connected to the controller.
    2) Cancel the NI installation wizard if it comes up.
    3)
    Unzip the drivers and run the setup.exe file. Make sure you install
    both the ATI display driver and the ATI Control Panel. (Check the zip
    name to make sure you have the xp version of the driver)
    4) After
    restart go to the Display Properties and under the Settings tab you
    should have monitors 1 and 2 on Mobility Radeon 9000 (Kontron CP-332)."
    If you don't have BIOS version 1.20 or higher, please upgrade to BIOS version 1.30, if you need to upgrade the BIOS please make sure you fully understand the readme file. Then follow the steps above to enable triple output on the graphics cards.
    When you have this working please try adding the second Kontron card.
    Regards
    JamesC
    NIUK and Ireland

  • Arch Live CD x64 hanging during boot at "triggering uevents"

    Hello!
    I recently was recommended Arch by a friend, and after I followed the 'Newbies Guide' and burning a live CD to install Arch with, it appears to hang during Live CD boot at "installing uevents."
    I am trying to install Arch as a dual boot on a late 2008 MacBook Pro which is currently running x64 Windows 7. I have plenty of HD space (100gb free and 100gb unallocated to install Arch onto).
    Here is a picture:
    http://i.imgur.com/Y8P41nf.jpg
    I get the same error weather I try to install x64 or i686 (I think that's what it's called). Is there any reason for this?
    Thank you!
    -- mod edit: read the Forum Etiquette and only post thumbnails http://wiki.archlinux.org/index.php/For … s_and_Code --
    (Sorry, missed that. My bad!)
    Last edited by RalphORama (2013-09-07 03:09:13)

    frank604 wrote:
    You can try nomodeset.  Seems to be a failure in loading a driver for your hardware. To read more on similar issues, there's a few posts with more info and suggestions by googling it. 
    Google result: http://lmgtfy.com/?q=halt+at+triggering+uevent
    Results:
    https://bbs.archlinux.org/viewtopic.php?id=151259
    https://bbs.archlinux.org/viewtopic.php?id=140426
    Thanks! I tried googling it myself but got mostly answers that didn't work. I'll try this!

  • Hangs during boot after upgrading to Kernel 2.6.39

    I have just installed Arch on a new computer. It works fine until I upgrade to Kernel 2.6.39. After that it hangs on boot.
    The end of /var/log/everything.log is posted below.
    Jul 26 23:52:06 localhost kernel: [ 6.036766] [drm] nouveau 0000:04:00.0: Parsing VBIOS init table at offset 0x85F3
    Jul 26 23:52:06 localhost kernel: [ 6.129046] adt7475 1-002e: ADT7473 device, revision 1
    Jul 26 23:52:06 localhost kernel: [ 6.138997] [drm] nouveau 0000:04:00.0: Detected monitoring device: adt7473
    Jul 26 23:52:06 localhost kernel: [ 6.139000] [drm] nouveau 0000:04:00.0: 1 available performance level(s)
    Jul 26 23:52:06 localhost kernel: [ 6.139002] [drm] nouveau 0000:04:00.0: 0: memory 405MHz core 270MHz shader 540MHz
    Jul 26 23:52:06 localhost kernel: [ 6.139233] [TTM] Zone kernel: Available graphics memory: 12371030 kiB.
    Jul 26 23:52:06 localhost kernel: [ 6.139236] [TTM] Zone dma32: Available graphics memory: 2097152 kiB.
    Jul 26 23:52:06 localhost kernel: [ 6.139238] [TTM] Initializing pool allocator.
    Jul 26 23:52:06 localhost kernel: [ 6.139252] [drm] nouveau 0000:04:00.0: Detected 5376MiB VRAM
    Jul 26 23:52:06 localhost kernel: [ 6.139260] mtrr: type mismatch for d0000000,8000000 old: write-back new: write-combining
    Jul 26 23:52:06 localhost kernel: [ 6.150626] [drm] nouveau 0000:04:00.0: 512 MiB GART (aperture)
    Jul 26 23:52:06 localhost kernel: [ 6.152371] [drm] nouveau 0000:04:00.0: failed to load fuc409d
    Jul 26 23:52:06 localhost kernel: [ 6.176193] [drm] Supports vblank timestamp caching Rev 1 (10.10.2010).
    Jul 26 23:52:06 localhost kernel: [ 6.176195] [drm] No driver support for vblank timestamp query.
    Jul 26 23:52:06 localhost kernel: [ 6.228800] No connectors reported connected with modes
    Jul 26 23:52:06 localhost kernel: [ 6.228802] [drm] Cannot find any crtc or sizes - going 1024x768
    Jul 26 23:52:06 localhost kernel: [ 6.231002] [drm] nouveau 0000:04:00.0: allocated 1024x768 fb: 0x8020000, bo ffff880608d97800
    Jul 26 23:52:06 localhost kernel: [ 6.233786] Console: switching to colour frame buffer device 128x48
    Jul 26 23:52:06 localhost kernel: [ 6.235094] fb0: nouveaufb frame buffer device
    Jul 26 23:52:06 localhost kernel: [ 6.235094] drm: registered panic notifier
    Jul 26 23:52:06 localhost kernel: [ 6.235098] [drm] Initialized nouveau 0.0.16 20090420 for 0000:04:00.0 on minor 0
    Jul 26 23:52:06 localhost kernel: [ 6.255449] HDA Intel 0000:04:00.1: PCI INT B -> GSI 17 (level, low) -> IRQ 17
    Jul 26 23:52:06 localhost kernel: [ 6.255451] hda_intel: Disable MSI for Nvidia chipset
    Jul 26 23:52:06 localhost kernel: [ 6.255599] HDA Intel 0000:04:00.1: setting latency timer to 64
    Jul 26 23:52:06 localhost kernel: [ 7.663482] EXT4-fs (sda3): re-mounted. Opts: (null)
    Jul 26 23:52:06 localhost kernel: [ 7.807508] EXT4-fs (sda4): mounted filesystem with ordered data mode. Opts: (null)
    Jul 26 23:52:06 localhost kernel: [ 7.851401] Adding 265068k swap on /dev/sda2. Priority:-1 extents:1 across:265068k
    Jul 26 23:52:06 localhost kernel: [ 8.569682] r8169 0000:08:00.0: eth0: link down
    Jul 26 23:52:06 localhost kernel: [ 8.569687] r8169 0000:08:00.0: eth0: link down
    Jul 26 23:52:06 localhost dhcpcd[747]: eth0: waiting for carrier
    Jul 26 23:52:08 localhost dhcpcd[747]: eth0: carrier acquired
    Jul 26 23:52:08 localhost kernel: [ 10.301736] r8169 0000:08:00.0: eth0: link up
    Jul 26 23:52:08 localhost dhcpcd[747]: eth0: broadcasting for a lease
    Jul 26 23:52:12 localhost dhcpcd[747]: eth0: offered 131.181.53.42 from 131.181.127.32
    Jul 26 23:52:13 localhost dhcpcd[747]: eth0: acknowledged 131.181.53.42 from 131.181.59.48
    Jul 26 23:52:13 localhost dhcpcd[747]: eth0: checking for 131.181.53.42
    Jul 26 23:52:18 localhost dhcpcd[747]: eth0: leased 131.181.53.42 for 43200 seconds
    Jul 26 23:52:18 localhost dhcpcd[747]: forked to background, child pid 774
    Jul 26 23:52:18 localhost crond[823]: /usr/sbin/crond 4.5 dillon's cron daemon, started with loglevel info
    Jul 26 23:53:01 localhost crond[823]: FILE /etc/cron.d/prune-cronstamps USER root PID 835 job prune-cronstamps
    Jul 26 23:53:01 localhost crond[823]: FILE /var/spool/cron/root USER root PID 836 job sys-hourly
    Jul 26 23:53:01 localhost crond[823]: FILE /var/spool/cron/root USER root PID 837 job sys-daily
    Jul 26 23:53:01 localhost crond[823]: FILE /var/spool/cron/root USER root PID 838 job sys-weekly
    Any help fixing this would be greatly appreciated.

    I have been trying to isolate the problem a little further. I re-installed (with just the base and sudo) and after upgrading pacman rebooted and it worked without fail. Then I installed libusb and libusb-compat which where required when I tried to upgrade just the kernel using
    pacman -S kernel26
    which initially failed because of the missing dependencies libusb and libusb-compat. I then re-booted and that worked without a problem.
    I then upgraded to Kernel 2.6.39 using the above command and then it hung on rebooting. I saved the logs at each stage.
    The additional logs in errors.log in the reboot that failed are as follows.
    ul 26 16:28:39 O313 kernel: [ 5.120698] [drm] nouveau 0000:04:00.0: Pointer to BIT loadval table invalid
    Jul 26 16:28:39 O313 kernel: [ 5.360508] [drm] nouveau 0000:04:00.0: failed to load fuc409d
    Jul 26 16:28:39 O313 kernel: [ 5.808016] sd 20:0:0:0: [sdb] Assuming drive cache: write through
    Jul 26 16:28:39 O313 kernel: [ 5.809960] sd 20:0:0:0: [sdb] Assuming drive cache: write through
    Jul 26 16:28:39 O313 kernel: [ 5.812116] sd 20:0:0:0: [sdb] Assuming drive cache: write through
    Jul 26 16:28:35 O313 udevd[369]: error: runtime directory '/run/udev' not writable, for now falling back to '/dev/.udev'
    The end of kernel.log is as follows:
    Sat Jul 9 14:57:41 CEST 2011
    Jul 26 16:28:39 O313 kernel: [ 0.000000] Command line: root=/dev/disk/by-uuid/e4733c60-3e54-4001-a83e-415b690dfcb0 ro
    Jul 26 16:28:39 O313 kernel: [ 0.000000] BIOS-provided physical RAM map:
    Jul 26 16:28:39 O313 kernel: [ 0.000000] BIOS-e820: 0000000000000000 - 000000000009f800 (usable)
    Jul 26 16:28:39 O313 kernel: [ 0.000000] BIOS-e820: 000000000009f800 - 00000000000a0000 (reserved)
    Jul 26 16:28:39 O313 kernel: [ 0.000000] BIOS-e820: 00000000000f0000 - 0000000000100000 (reserved)
    Jul 26 16:28:39 O313 kernel: [ 0.000000] BIOS-e820: 0000000000100000 - 00000000cfed0000 (usable)
    Jul 26 16:28:39 O313 kernel: [ 0.000000] BIOS-e820: 00000000cfed0000 - 00000000cfed1000 (ACPI NVS)
    Jul 26 16:28:39 O313 kernel: [ 0.000000] BIOS-e820: 00000000cfed1000 - 00000000cfee0000 (ACPI data)
    Jul 26 16:28:39 O313 kernel: [ 0.000000] BIOS-e820: 00000000cfee0000 - 00000000cff00000 (reserved)
    Jul 26 16:28:39 O313 kernel: [ 0.000000] BIOS-e820: 00000000f0000000 - 00000000f4000000 (reserved)
    Jul 26 16:28:39 O313 kernel: [ 0.000000] BIOS-e820: 00000000fec00000 - 0000000100000000 (reserved)
    Jul 26 16:28:39 O313 kernel: [ 0.000000] BIOS-e820: 0000000100000000 - 0000000630000000 (usable)
    Jul 26 16:28:39 O313 kernel: [ 0.000000] NX (Execute Disable) protection: active
    Jul 26 16:28:39 O313 kernel: [ 0.000000] DMI 2.4 present.
    Jul 26 16:28:39 O313 kernel: [ 0.000000] DMI: Gigabyte Technology Co., Ltd. X58A-UD5/X58A-UD5, BIOS FD 02/01/2011
    Jul 26 16:28:39 O313 kernel: [ 0.000000] e820 update range: 0000000000000000 - 0000000000010000 (usable) ==> (reserved)
    Jul 26 16:28:39 O313 kernel: [ 0.000000] e820 remove range: 00000000000a0000 - 0000000000100000 (usable)
    Jul 26 16:28:39 O313 kernel: [ 0.000000] No AGP bridge found
    Jul 26 16:28:39 O313 kernel: [ 0.000000] last_pfn = 0x630000 max_arch_pfn = 0x400000000
    And this is the end of daemon.log
    Jul 26 16:27:49 O313 init: Switching to runlevel: 6
    Jul 26 16:27:50 O313 dhcpcd: received SIGTERM, stopping
    Jul 26 16:27:50 O313 dhcpcd: eth0: removing interface
    Jul 26 16:28:39 O313 2.352592] udevd[87]: starting version 171
    Jul 26 16:28:39 O313 4.531007] udevd[370]: starting version 171
    Jul 26 16:28:39 O313 dhcpcd: version 5.2.2 starting
    Jul 26 16:28:39 O313 dhcpcd: eth0: waiting for carrier
    Jul 26 16:28:35 O313 udevd[369]: error: runtime directory '/run/udev' not writable, for now falling back to '/dev/.udev'
    Jul 26 16:28:39 O313 init: Entering runlevel: 3
    Please let me know if any further information would be useful in tracking down this problem. Also ignore any timings in my initial post they were incorrect.
    Last edited by TheStatsMan (2011-07-26 07:40:48)

  • VM template image missing from OVM Server 2.2.0

    Hi,
    We have configured couple of linux OVM images on OVM server 2.20. These images were running successfully from 1 month , suddenly we found 1 of the VM image missing from the /OVS/running_pool directory. Can you let me know if there is any bug in OVM 2.20 as we are running 100 of VM's and VM's image missing could be big issue in future.

    Welcome to the forums !
    The scripts should be available in the companion directory of the CD
    http://download.oracle.com/docs/cd/B19306_01/server.102/b14198/installation.htm#I4367
    HTH
    Srini

  • [SOLVED]Hanging after booting from installation media

    Yesterday I booted from a rw-DVD got to the terminal and could execute commands, connect to the internet and use elink etc no problem. I didn't go through with installation as I wanted to read up more on partitioning my drives for dual booting before actually doing so.
    Trying the same thing today, and it hangs soon after I boot, regardless of whether I do anything. Printing the following:
    nouveau E[ DRM] failed to idle channel 0xcccc0000 [DRM]
    pci_pm_runtime_suspend(): nouveau_pmops_runtime_suspend+0x0/0xf0 [nouveau] returns -16
    INFO: rcu_preempt detected stalls on CPUs/tasks: { 6} (detected by 1, t=18002 jiffiess, g=974, c=973, q=604)
    This is without me typing anything. If I try to execute a command quickly after booting it sometimes works, but after a couple of minutes it will complain of a soft lockup.
    I've tried burning another disk, and using a USB installation media, but the same thing happens. Any thoughts?
    Edit: Trying to run it on a laptop with i7-4700MQ, 16GB ram, and Intel(R) HD Graphics 4600 / NVIDIA GeForce GTX 770M
    Second Edit: Booted with nomodeset, which worked and allowed me to install. Just trying to sort out the sodding boot loaders now...
    Last edited by glfharris (2014-07-11 22:42:31)

    Welcome to the forum.
    First of all, you should get in the habit of using [ code ] tags when posting code, not [ quote ] tags (well, unless you want to apply some styling to it, like bold, italic, etc).
    This is wrong:
    # umount /dev/sdc
    This is correct:
    # umount /dev/sdc1
    You were trying to unmount the drive as a whole, which obviously isn't mounted, instead of the first (and probably only) partition. Had you followed the advice from the note to use blkid and check if it's mounted, this wouldn't have happened. But the fact that a DVD produced that error puzzles me... I have no experience with UEFI, but I think you need to press F10, F11, or something like that, to able able to get to a UEFI boot menu, and choose the optical unit as source.
    I hope you used a BitTorrent client when downloading the ISO, and not some direct link (which are prone to CRC errors). If you used a direct link, then check the MD5 and make sure that it matches the one from the Download page. For future reference, torrents are checked while they're being downloaded.

  • Mac Mini keeps hanging during boot

    My ~3 year old Mac Mini keeps freezing during booting with the error message "You need to restart your computer. Hold down the Power button...". This happens every time. Booting in safe mode works.
    This happened with Mac OS X Tiger but keeps happening even after I have completely reformatted that hard disk and reinstalled Leopard from scratch. There are no external devices connected to the computer besides the monitor and a bluetooth mouse and keyboard.
    After reading some discussion forums I have already tried starting into Open Bootware and running "reset-nvram" and "reset-all" but to no avail.

    Welcome to Apple Discussions!
    What you are suffering is a Kernel Panic, and given you have reformatted your drive and reinstalled MacOS, it would tend to suggest the issue is hardware related - most common culprit being RAM.
    http://docs.info.apple.com/article.html?artnum=106227 explains what kernel panics are, and http://www.thexlab.com/faqs/kernelpanics.html and http://www.index-site.com/kernelpanic.html may give some assistance in working through the problem to determine the cause.
    The one good thing is that your system appears sufficiently stable to allow you to boot to the Leopard installer and complete a full install. This makes it less likely there is a fundamental issue with the most expensive component of the system, the logic board.

  • OSX hangs during boot or install

    Hello all,
    I'm writing this because I'm not really sure where else to post this at to get an indepth answer. Currently I have a dual G4 450mhz AGP PowerMac that I bought used. When I purchased it, it had 768mb of ram and the only thing it didn't have was a working hard drive. After putting in a new hard drive the system worked great when i intially installed OS9 and later OSX for fun.
    However I had to remove the 768mb of RAM because a client PC needed it and that took priority over my dual G4 at the time. Just the other week I purchased 2 x 256mb of RAM from Omni Technologies (omnitechnologies.biz) which guarantees working ram for specified Apple systems.
    Upon receiving that ram and installing it, I powered on the G4 only to find it would "hang" when booting OSX (10.3.9). The symptoms are as follows: When powering on I hear the normal chime and the white screen with gray apple logo appears. Seconds later the spinning progress indicator shows up spinning in circles as OSX is booting. However after about 5 minutes with no DVD/hdd activitity, the system then hangs. The gray apple logo changes to a gray 'prohibited' logo. It's the logo of the circle with the slash through it. Like the kind you see over no-smoking signs.
    I figured the hard drive was messed up and I decided to reinstall OSX cleanly. However when I booted from the CD by pressing 'c', the EXACT SAME symptoms above happened. It was at this point I started getting really worried. So I decided to remove the hard drive temporarily and boot from the CD just to make sure it really was booting from the CD. Unfortunately the exact same symptoms happened.
    Out of desperation to make sure that my hardware was OK, I decided to install OS 9.2.1 which installed and WORKED perfectly. I also installed UbuntuPPC and Slackintosh versions of linux which also installed and worked perfectly.
    The issue appears to reside with OSX. I've borrowed friends cd's of 10.2-10.3 and all of them will NOT install. They start to boot from the CD, but never even make it to the first window.
    Help!!
    Brad

    Actually trying one stick in each individual slot was one of the first things I did. Unfortunately that did not provide a resolution for me.
    Thanks for the links regarding the broken folder/prohibitory sign. I read those and they made mention of resetting the nvram and pram. I just did that a bit earlier today but logging into the open firmware by pressing Option-Command-F-O and typing: reset-nvram; set-defaults; reset-all.
    Upon the reboot and after I plugged the hdd with OSX on it back into the system, the resolution was a bit off as I figured. But this time there was no progress indicator. Instead only the gray apple logo showed and there was no response from the hdd or cdrom drive.
    I also noticed that the USB mouses red light went out within the first 45 seconds of booting. I swapped out keyboards and mice and the new ones did the same thing as well. I also tested the memory in an imac I have and OSX that is installed ont heimac works gerat with that stick of memory. I'm leaning towards the fact that the memory I have is fine, being that it was ordered from a company that specifically guaranteed it to work on macs of all kinds.
    Any other thoughts or ideas?

  • Kernel 2.6.37 hangs on boot from rocketraid 2310 array

    Hi,
    I know some people here are using RocketRaid cards and I was hoping somebody could help me with this. Since upgrading to 2.6.37 it seems that the kernel isn't able to load the rr2310 module anymore. When trying to boot from the array, I see a multi-monitor amount of garbled text for a split second before the kernel tries to boot normally and then hangs when trying to detect hdds. I really can't say more than this because none of this will be logged (since obviously the array can't be loaded) and I haven't been able to pause screen output at the exact moment yet. Everything works fine with 2.6.36.
    I'm updating the kernel manually so I can recompile the rr2310 module everytime before invoking mkinitcpio For that I'm using this PKGBUILD and re-running makepkg everytime I've updated the kernel + headers. This has worked for me for more than a year now and I'm clueless as to what might be the issue now. Any ideas?

    Since this thread has the same origin as  this one, all further development shall be discussed there.

Maybe you are looking for