New install fails to boot

I am having a problem with a new install of arch. The boot goes normally showing all the text as the kernel starts up and stuff but then then stops at the line
[<c140b0d7>] i386_start_kernel +0xd7/0xdf19f/0x74/0x50 #1sk!c13c7f441 0f 84 cc
I really don't know why it's hanging. If anyone can help I would really appreciate it.
Tim
Last edited by tpolich (2010-06-25 01:38:19)

If you haven't put too much work into your install yet, I would just reinstall. You can also boot into a live cd, chroot, and reinstall the kernel (pacman -S kernel26).

Similar Messages

[PPC] new install fails to boot: root partition not found

Hi,
new ArchPPC installation on a iMac G3. It does not boot further than initramfs because root partition is not found. I get something like:
Root device /dev/sda4 doesn't exist
Attempting to created it
ERROR: unable to determine major/minor number of root device /dev/sda4
then I get a dropbox recovery console but keyboard doesn't work.
I chroot in the installed system to change mkinicpio pata hook to ide, regenerated initramfs but that didn't help.
Any guidance to diagnose and solve this issue would be greatly appreciated.

Hi, sorry I just realized you replied to my thread.
I don't have my mac at the moment, but I must have done something like :
- boot the live CD
- get the output of lsmod
- copy this output to mkinitcpio.conf (the one that's on your HD), remove the autodetect hook
- chroot into your HD setup
- regenerate initramfs
- update yaboot (is this really mandatory?)
- exit chroot and reboot.

Will WebNS 7.5 auto fallback if new code failed to boot?

Hi,
I'm preparing for WebNs upgrade from 7.4 to 7.5 to 8.2
And change will be done remotely.
My question is, what will happen if the new code doesn't boot up after we reboot the CSS?
Will it auto fall back to the previous working code?
Thank you.

Hello,
Good to see your going to 8.20 software.
I can't say for sure whether or not your CSS will fall back to the original image, although my suspicion is that it will not. I will assume that your CSS is in a redundant configuration consisting of a pair of CSS. Please correct me if I'm wrong. You can alway upgrade the standby CSS, and make sure if boots up OK on the new code. Then you can fail over to it, while you upgrade the second CSS. This way, you would always be upgrading the standby CSS, so traffic should not be impacted, even in the event of a boot failure. Then you can recover the standby that didn't boot properly while the master CSS is safely handling production traffic.
Also, I would recommend using the upgrade script rather than the manual upgrade process, especially if you have any custom user accounts and/or custom scripted probes. Another good idea as a backup plan is to temporarily (or permanently) arrange for console access to the two CSS during the upgrade process, just in case it is needed, as you are doing the upgrade remotely.
Sean

Snow Leopard New install failed

I know there are several topics on this subject but I couldn't find one that matched my isue
My Spec: Macbook, 2.4ghz (?) Intel Procsesor, 4GB Ram, superdrive, 250GB Hard Disk (purchased off of eBay about 10 months ago)
I was using my Mac to rip some DVD's to put on my iPhone (home made from files on my old PC one) using Islysoft DVD Ripper. Anyway, one of the files that it was ripping must have been bad as it was stuck for ages. It was also making a funy noise, later I found out that it was due to a poor label, it took quite a few attempts to get it out, ending up with the laptop being on its side so I could grab the DVD out of the superdrive.
In the midst of all this I was trying to shut down the system as it had locked up, in theend I had to push the power button for10 seconds to get it to go off. Once I had got the DVD out I tried rebooting but it came up with a prohibitory/no entry sign and wouldn't let me in. I also had boot camp but the Windows partition was corrupt and had mising files too. I didn't get the original install disk with the machine, just a copy. When I tried installing this it must have been a bad burn as some of the files could not be loaded.
So I went back to my Windows partition on BootCamp, re installed it and al was fine and dandy, it worked OK.
So today I went out and got Snow Leopard from our local apple reseller (Square) and tried installing it. It came up with an error upon trying to install it, saying that it could not install on the original hard drive. After reading up on the net, it turned out I had to re partition. I decided that as I had not done much on Windows, I would go the whole hog and start off with a fresh 1 partition hard drive, as I use VMware fusion for my Windows use anyway.
So, fresh new hard drive, now it allowed me to install. But I got a message saying installation failed, please contact the software vendor. I tried installing again and got the same message
So seen as the hard drive has not worked for OSX since the crash, I am leaning towards that as being the problem. But I have also seen on here that it could be RAM also, possibly came unseated during earlier trying to get the DVD out?
I am seriously considering getting a new hard drive as I am thinking of using my external hard drive for time machine as opposed to documents. But before I do I wanted to ask on here to make sure of what the problem is, before I spend out my money. It seems strange that Windows worked fine (albeit on a different partition) and OSX does not, but there you go, I ditched Vista to get away from all this palaver!

Hi Russ, Welcome to Apple Discussions.
When you repartitioned your drive, did you choose GUID?
This could potentially cause the problem or your disk may be on it's way out.
Run http://www.macupdate.com/info.php/id/15837/rember for your RAM.
Also run Apple Hardware Test. Option-boot from your SL DVD and choose Apple Hardware Test.
Let us know.
-mj

New install hangs on boot when GDM or LXDM services are enabled

Greetings Arch users,
I've been trying out installing Arch on a USB drive in order to get familiar with the process and use it on my main machine in the future. I've been following the Beginners' Guide, and after a few hiccups, I managed to install what appears to be a fully-functional Arch system onto a 16 GB USB drive, albeit without a window manager or desktop environment.
When I tried that is where I ran into problems. I installed X, vesa driver, and GNOME and enabled gdm.service, and upon the next reboot the system hung after or in the middle of the fsck process, exactly as described in this thread.
rebooted, hangs after the fsck bit where it says something like /dev/sda4: clean, 112977/9296096 files, 185427/21217024 blocks
I just get the blinking cursor. I left it there long enough to take a nap and nothing else came up.
Examining the journalctl output, I see an error exactly like mentioned in this thread:
GLib-GObject-CRITICAL: g_object_ref: assertion 'object->refcount > 0' failed
GLib-GObject-CRITICAL: g_object_unref: assertion 'object->refcount > 0' failed
Chrooting into the system and disabling gdm.service allowed for normal boot.
Well, I thought, maybe there's an issue with GDM or GNOME. I'll try LXDE and LXDM instead. Unfortunately, that hung at the exact same point in the loading process. Looking at the journalctl, I saw an output exactly like what was described in this thread:
Lxdm.service main process exited code=exited status=1/FAILURE
lxdm.service entered failed state
I'm stumped. I've searched and haven't come up with anything. Does anyone have any ideas about what might be the cause? What additional information would be helpful in diagnosing the issue? Thank you for your help.
Last edited by AbortToddlers (2014-01-28 15:06:04)

Neburski wrote:
slowpoke1584 wrote:
killall gdm
GDM then restarts immediately. Problem recurring each boot.
Can you check the logs (dmesg, journalctl, xorg) and see if there are any differences for the startup of GDM before and after a successful GDM start.
Technically from the lack of information you provided it's not possible to state if you actually have the same issue or not. It might be better for you to start your own separate thread.
If you start your separate thread please provide some more details so people don't need to start guessing.
I think I'll just RTM.

Win7 x64 install fails at boot with alternating Mac and Cross-Circle Logo

Thanks for reading.
I have a new late 2009 i7 2.6Ghz Macbook (6.1 model) that I purchased in February this year. I'm having real problem trying to get a Windows 7 DVD to boot on it; whenever I try (either by using the bootcamp assistant to parition my drive then start the boot process, or by holding down the OPTION key, or even using the C key at boot) instead of the normal Windows 7 boot process, the disc spins, then I am left with an alternating Apple logo with a circle with a angled cross line through it, sometimes showing a folder with a ? mark.
I have tried resetting the PRAM, using other Windows 7 media, but I just can't seem to get a disk to boot. I have even tried wiping my Mac parition in case it was a corrupt partition by backing up to a timedesk then reinstalling, but again when I come to install Windows 7 I get the same problem.
I can boot the Mac OS install disks not problems.
Really appreciate if anybody has any guidance or resolutions?

Hi - no nothing plugged, except my external DVD drive.
I managed to install TechTool Pro's emergency EDRIVE from DVD, and have managed to reinstall Mac OS X without any problems, so unsure about a hardware problem. All TechTool tests come back ok, so no issues seem visible from that.
You might be thinking why I am using an external DVD; well this is because I've taken out the internal DVD using OWC Datadoubler http://eshop.macsales.com/item/Other%20World%20Computing/DDAMBS0GB/
I have a 512GB SSD in the normal hard drive space, and a 500Gb Hybrid disk where the DVD drive was. The drives are seen perfectly well in Max OSX; indeed when I did a reinstall I used the 2nd internal hard disk as the time machine and then restored from it.
Could it be a problem with partitions or some issue with the EFIboot from the Windows 7 DVD's? I've tried looking at rEFIit http://refit.sourceforge.net/ to see if that would help, but no luck.
The data doubler shows examples of this being used in my mac model for a specific Windows implementation (which is why I bought it) so don't think its that. Anybody have any ideas?

10.3 Server new install won't boot from Mirrored RAID - HELP!!

Hi all,
I had 10.3 Server running fine on a 450 MHz B&W G3 (home server use, nothing too demanding), when I decided to add a 2nd HD and run the server from a RAID mirror (both 80GB drives). I had problems enabling RAID on the boot drive with diskutil in Terminal, so I decided to rebuild the server. I didn't have much besides the system on it, so backing up data and re-installing isn't a big ordeal (or so I thought).
No problems creating the mirror set once I re-formatted the drives. The install seemed to go fine (10.3.4 on install disk), but upon restart, I got the flashing system folder/question mark. When booting from the install disk, Disk Utility recognizes the RAID, and Startup Disk recognizes the mirror as a viable boot drive and allows me to select it and restart. Same problem, no system found.
When I run diskutil info for the mirror, it lists the mirror volume as Not Bootable.
I've checked the disks with both Disk Utility and DiskWarrior - all looks OK. I've reset PRAM and NVRAM, taken out added PCI cards, and disconnected all FW and USB devices (besides kbd and mouse).
Unfortunately, B&W G3 can't boot from an external FW drive, so I'm stuck with booting from a CD/DVD for troubleshooting.
My next step is to re-install on a single drive again and try to enable RAID and mirror, but I'd sure like to avoid that if I could.
I've searched through this board and didn't really see this particular situation. Any of you smart server folks seen this before -- any ideas or suggestions??
TIA,
Brad
B&W G3 Mac OS X (10.3.4) 450 MHz, 10.3 Server, 80GB RAID mirror

if you backup your data from a NON-RAID Drive (Single drive), create a RAID array and then Restore from the backup you created... you will find you cannot boot from the drive.
Apparently the sector or drive header information in a non-RAID drive is different than in a RAID array... so when you restore the backup data from the non-RAID drive to the new RAID Array; you effectively corrupt the RAID array not allowing it to be booted from.
The solution is to create the RAID array and then re-install your system from scratch... copying over the data you want to keep from your initial backup one file at a time (don't do a complete system copy or you will once again, corrupt your new RAID install).
I had the same problem and it took me a great deal of time to figure it out.
Joe

New install won't boot

I got a new laptop a couple of days ago and wanted to install Arch on it. Everything went fine until I tried booting it. I'm not sure where it gets stuck but I believe it's at the step where it waits for UDev uevents to be processed. Why I believe this is, is because that's also the point where it takes a fairly long while to get past when booting the install CD.
I took some pictures and a video of my laptop trying to boot into Arch which you can find here: http://yuri.vm.madoka.be/arch/
The first picture is where it gets stuck when booting normally, the next pictures are taken when booting from the CD.
If anyone could help me it'd be greatly appreciated.

JokerBoy wrote:adding nomodeset to the kernel boot line helps?
That one worked. Before this I also tried blacklisting nouveau by booting System Rescue CD. On that CD I also noticed I couldn't boot into a graphical environment so is it nouveau not playing nicely with my hardware or my hardware acting up? (New laptop...)
I also just tried installing the official NVidia driver and so far I have successfully started an X server which seems to work perfectly.
So basically I'm just wondering if there's a way to get Nouveau working in case I need it. I'll be using the official drivers when using Arch but if I ever need a GUI on my System Rescue CD I'm pretty much f'ed at the moment...

Netboot live install fails to boot

Hi,
I'm having massive amounts of trouble trying to get a netboot live install to work. The target has GRUB legacy on its HDD. Following https://releng.archlinux.org/pxeboot/ ,
I copied ipxe.lkrn to /boot/, added a section to menu.lst.
Reboot, select that new option; it loads correctly ipxe and I get to the graphical menu ( like http://jadelinux.com/images/archimg/1.png ). I select Release64, then any mirror (tried 3), and then I see vmlinuz and archiso.img getting downloaded correctly (I presume), then
Booting the kernel.
:: running hook [xyz]
... (more hooks)
:: running hook [archiso_pxe_common]
IP-Config: eth0 hardware address 00:14..... mtu 1500 DHCP RARP
And then nothing.
Fun facts :
- from either the graphical or text menu, pressing [tab] to try adding kernel options doesn't work, i.e. I can't edit the command before booting ! Swapping keyboards doesn't help
- from either graph or text menu, pressing Esc gets me to a "boot: " prompt, but I can't enter kernel options from there !
- from another computer running wireshark, connected to the same hub, the last traffic I see is some (unanswered ?) DHCP requests from the machine stuck at "IP-Config ..." So I thought maybe my router doesn't like these repeat / redundant dhcp query... I tried manually releasing the IP just before that "IP-Config : eth0 ...." line. The only difference I see is that the DHCP query now succeeds ( I see the new assigned IP in the router's table), but the netboot process still doesn't continue !
Any ideas ?

If you haven't put too much work into your install yet, I would just reinstall. You can also boot into a live cd, chroot, and reinstall the kernel (pacman -S kernel26).

Install fails at boot

I am trying to reinstall Arch, but when I boot with the installation CD I'm just presented with a GRUB command line.
Looking through the forums it seems that using the isolinux image typically solves this kind of problem, but unfortunately it occurs even when attempting that. When I try the regular image (netinstall-x86_64.iso) I get a "grub>" prompt and when using the isolinux image there's a "boot>" prompt in GRUB.
I've burnt at 1x speed using several burners and also used different kinds of CD:s. When I originally installed Arch I had no problems at all.
Possibly useful info:
- AMD II x4 620, 6 GB RAM, NVidia GT220, lots of free disc space
- Dual-booting with Windows7
- Having a separate /boot partition
- Attempting to use an Ubuntu install CD also fails with similar symptoms
Any help would be greatly appreciated.

Sorry for bumping this topic, but I have the same problem. I've tried installing some 10 times with various versions of the Arch disks, but fail miserably everytime. So I used the previous .iso (2009.03?) and went so far as to configuring the system, but then there were completely blank config files. I consider myself quite advanced, but that's just too much.
Can anyone please tell me how to get the ordinary arch install cd images working (netinstall, x86_64.isolinux)? I'm desperate for help!

New install failed

Hi all
I'm a new user of APEX. I downloaded the XE 10 Database, installed it as Administrator, Apex is working as 2.0, then i downloaded the 3.2.1 update for APEX. And here I get the error. As you can see at the end I'm getting an error in a package. I've downloaded the APEX3.2.1 update 3 times. All show the same problem. Can somebody help me?
Regards
Erwin
F
2
PL/SQL-Prozedur erfolgreich abgeschlossen.
FOO_USR
FLOWS_020100
Proceeding with upgrade installation.
PL/SQL-Prozedur erfolgreich abgeschlossen.
PL/SQL-Prozedur erfolgreich abgeschlossen.
Es wurden keine Zeilen ausgewählt
PL/SQL-Prozedur erfolgreich abgeschlossen.
Es wurden keine Zeilen ausgewählt
PL/SQL-Prozedur erfolgreich abgeschlossen.
I. O R A C L E S Y S I N S T A L L P R O C E S S
...create flows user
Benutzer wurde erstellt.
Benutzer wurde geändert.
Benutzer wurde geändert.
Benutzerzugriff (Grant) wurde erteilt.
Benutzerzugriff wurde aufgehoben (Revoke).
Benutzerzugriff (Grant) wurde erteilt.
...create validate procedure in SYS schema and start registration
Prozedur wurde erstellt.
Keine Fehler.
core_grants
...grant APEX owner core privileges
Benutzerzugriff (Grant) wurde erteilt.
PL/SQL-Prozedur erfolgreich abgeschlossen.
Package wurde erstellt.
Keine Fehler.
Library wurde erstellt.
Benutzerzugriff (Grant) wurde erteilt.
...remove views created from previous APEX installations
PL/SQL-Prozedur erfolgreich abgeschlossen.
...wwv_dbms_sql
...wwv_dbms_sql
Package wurde erstellt.
Keine Fehler.
Benutzerzugriff (Grant) wurde erteilt.
...wwv_flow_create_key_package
...wwv_flow_create_key_package
Package wurde erstellt.
Keine Fehler.
Prozedur wurde erstellt.
Keine Fehler.
PL/SQL-Prozedur erfolgreich abgeschlossen.
Package wurde gelöscht.
Prozedur wurde gelöscht.
Benutzerzugriff (Grant) wurde erteilt.
...CONNECT as the Oracle user who will own the flows engine
Session wurde geändert.
I. I N S T A L L P R E - C R E A T E T A B L E S P E C S
...wwv_flow_init_htp_buffer
Prozedur wurde erstellt.
Keine Fehler.
Benutzerzugriff (Grant) wurde erteilt.
TEMP
ldap.sql
TEMP2
custom_auth_ldap.sql
...wwv_flow_ldap
Keine Fehler.
...wwv_flow_custom_auth_ldap
Keine Fehler.
...installing files dependend upon 9iR2
...if errors are encountered, ignore if not 9iR2
...wwv_flow_web_services
Keine Fehler.
...wwv_flow_process_utility
Keine Fehler.
Timing für: Package Specs
Abgelaufen: 00:00:09.00
IV. I N S T A L L F L O W P A C K A G E B O D I E S
...wwv_dbms_sql
Keine Fehler.
......Message wwv_flow_wizard_api_get_next_prev_pk_process
......Message wwv_flow_form_control_get_next_or_prev_pk_error
......Message wwv_flow_form_control_check_process
......Message wwv_dbms_sql_invalid_datatype
......Message total
......Message report_total
......Message build_query
......Message f4000_p4719_inline
......Message f4500_p40_previous_runs
......Message page_name_required
......Message f4050_primary_schema
......Message f4050_additional_schema
......Message f4050_create_schema
......Message f4050_reuse_schema
......Message f4050_action_assign
......Message f4050_action_no_assign
......Message f4050_schema_not_exist
......Message f4050_schema_restricted_no_warn
......Message f4050_schema_reserved_no_warn
......Message table_name_too_long
......Message page_template
......Message page_header_body_and_footer
......Message current_tab
......Message non_current_tab
......Message success_message
......Message navigation_bar
......Message error_page_template
......Message region_content
......Message 4000_invalid_date_format
......Message page_process
......Message page_process_condition
......Message item_condition
......Message branch_condition
......Message wwv_flow_create_model_app_navigation
......Message sc_name_nn
......Message wwv_flow_create_model_app_create_form_page
......Message wwv_flow_create_model_app_create_tabular_form
......Message wwv_flow_create_model_app_create_pages
......Message wwv_flow_create_model_app_fetch_row
......Message wwv_flow_create_model_app_process_row
......Message navbar_item_condition
......Message std_tab_condition
......Message lov_item_condition
......Message list_of_values
......Message sc_vq
......Message sc_sc
......Message wwv_calendar_invalid_query
......Message no_avail_jobs
......Message application_computation_condition
......Message application_process_condition
......Message list_item_condition
......Message menu_item_condition
......Message shared_static_lov_condition
......Message shared_dynamic_lov
......Message authorization_scheme
......Message authentication_scheme
......Message session_verify_function
......Message pre_auth_process
......Message authentication_function
......Message post_auth_process
......Message ldap_username_edit_function
......Message region_condition
......Message page_computation_condition
......Message page_validation_condition
......Message page_item_source
......Message page_item_default
......Message page_item_post_computation
......Message page_item_display_condition
......Message page_item_read_only_display_condition
......Message page_item_lov
......Message invalid_sort_order
......Message workspace_image
......Message application_image
......Message button_attributes
......Message web_service
......Message f4000_chart
......Message f4000_help_text
......Message f4000_tree
......Message tabular_form
......Message edit_all_region
......Message sc_not_valid_object
......Message debugging_off
......Message plsql_function_body_lov_error
......Message f4000_p3005_import_authorization_scheme
......Message f4000_p3005_import_navbar
......Message sc_report_rows
......Message wwv_flow_create_model_app_running_script_x
......Message wwv_flow_quick_flow_is_date
......Message button_template
......Message label_template
......Message list_template
......Message report_column_template
......Message report_template
......Message menu_template
......Message calendar_template
......Message logo
......Message login_url
......Message image_prefix
......Message logging
......Message application_owner
......Message static_substitution_strings
......Message application_status
......Message enable_debugging
......Message home_link
......Message application_deleted
......Message wwv_render_report3_dublicate_alias_names
......Message confirm_chart_dial
......Message confirm_chart_dialsweep
......Message wwv_flow_create_model_app_rpt_max_row
......Message editor_exit
......Message application_name
......Message application_alias
......Message exact_subs
......Message security_scheme
......Message proxy_server
......Message page_protection
......Message vpd
......Message acl_add_user
......Message wwv_flow_session_mon_no_index
......Message no_corresponding_region
......Message sql_inject_schema
......Message sql_inject_package
......Message sql_inject_procedure
......Message sql_inject_var
......Message sql_inject_line
......Message copy_page_select_named_lov
......Message copy_page_select_list
......Message copy_page_select_authorization
......Message edit_region
......Message edit_report_cols
......Message edit_component
......Message exported_from_another_workspace
......Message exported_from_current_workspace
......Message copy_page_copy_from_page
......Message copy_page_copy_to_page
......Message wwv_flow_wiz_confirm_copy_lov
......Message wwv_flow_wiz_confirm_use_existing_lov
......Message wwv_flow_wiz_confirm_copy_list
......Message wwv_flow_wiz_confirm_use_existing_list
......Message wwv_flow_wiz_confirm_copy_auth_scheme
......Message f4000_p598_exported_from_another_app_or_workspace
......Message gray_text
......Message white_text
......Message blue_text
......Message black_text
......Message f4000_p48_manifest
......Message wwv_flow_api_err_page_group
......Message unassigned
......Message installer_workspace_images
......Message installer_application_image
......Message installer_workspace_css
......Message installer_application_css
......Message installer_workspace_static
......Message installer_application_static
......Message no_application_selected
......Message 4000_639_seq_mesg
......Message 4000_641_seq_mesg
......Message 4000_646_seq_mesg
......Message 4000_749_seq_mesg
......Message f4000_p612_exported_from_another_workspace
......Message ob_fk_name
......Message ob_fk_referenced
......Message ob_fk_referenced_tab
......Message ob_cascade_delete
......Message ob_set_null
......Message since_date_mask
......Message ob_constraint_name
......Message ob_cons_info
......Message ob_select_datatype
......Message f4500_p101_no_varchar
......Message f4300_text_import
......Message acl_cust_auth_page_comment1
......Message acl_cust_auth_page_comment2
......Message waiting_app_definition
......Message waiting_generic
......Message waiting_supporting_objects
......Message edit_list_dev
......Message edit_attribute
......Message edit_component_def
......Message breadcrumb_entry
......Message wwv_flow_provision_cannot_extend_ts
......Message f4000_p4311_p371_static_text
......Message f4000_p4311_p371_db_column
......Message f4000_p4311_p371_sql_query
......Message f4000_p4311_p371_plsql_exp
......Message f4000_p4311_p371_plsql_func_body
......Message master
......Message detail
......Message detail_2
......Message edit_this_attribute
......Message f4400_enhanced_qry
......Message f4400_custom_qry
......Message list_initcap
......Message built_in_report_template
......Message f4000_link_column
......Message f4400_object_library_file_type
......Message f4400_plsql_library_file_type
......Message no_updateable_report_found
......Message f4400_p53_alerts_info
......Message f4400_p53_canvas_info
......Message f4400_p53_windows_info
......Message f4400_p53_visual_attribs_info
......Message f4400_p53_property_class_info
......Message f4400_p53_attachlibs_info
......Message f4400_p53_objgrps_info
......Message f4400_p53_coordinates_info
......Message f4400_p53_triggers_info
......Message f4400_p53_modparams_info
......Message f4400_p53_reports_info
......Message f4400_p53_menus_info
......Message wwv_flow_help_context_help
......Message create_demo_app_no_create_priv
......Message create_demo_app_no_exec_priv
......Message create_demo_app_grant
......Message 4000_424_value_must_be_numeric
......Message not_valid_view_name
......Message create_flow_ldap
......Message create_flow_sso
......Message svg_plugin
......Message query
......Message qb_warn_message
......Message wwv_flow_api_replace_script_file
......Message wwv_flow_api_new_script_file
......Message wwv_flow_api_import_script_error
......Message wwv_flow_api_script_exceeds_max
......Message f4500_p115_confirm
......Message f4500_p115_error
......Message f4500_p115_scripts_to_install
......Message not_null
......Message test_query
......Message f4400_block_comment
......Message script_exported_from_foreign_workspace
......Message wwv_flow_create_model_app_set_username_cookie
......Message wwv_flow_create_model_app_get_username_cookie
......Message f4400_report_comment
......Message wwv_flow_help_no_index_map
......Message wwv_flow_help_contents
......Message wwv_flow_help_find
......Message wwv_flow_help_score
......Message ok
......Message return_to_application
......Message no_region_position_in_page_template
......Message unauthenticated_user
......Message new_schema_name
......Message existing_schema_name
......Message f4350_confirm_schema_existing
......Message f4350_confirm_schema_new
......Message wwv_flow_mail_invalid_email_address
......Message package_globals
......Message non_package
......Message no_job_queue_processes
......Message session_mon_current
......Message session_mon_previous
......Message session_mon_elapsed
......Message session_mon_cpu
......Message session_mon_disk
......Message session_mon_buffer
......Message apex_region
......Message f4400_generic_comment
......Message f4400_p3_find_forms_file
......Message f4400_p18_script_name
......Message f4400_p18_script_size
......Message reset_to_null
......Message f4000_on
......Message f4000_off
......Message password_with_submit_dnss
......Message password_dnss
......Message password_with_submit
......Message qb_duplicate_query
......Message page_processing
......Message cache_created
......Message partial_page
......Message encryption_input_too_long
......Message f4000_p811_c_secure
......Message qb_actions
......Message f4400_item_prompt_label
......Message f4400_include_label
......Message f4400_migrate_to_label
......Message index_noun
......Message materialized_view
......Message synonym_noun
......Message add_column_name
......Message modify_column
......Message rename_column
......Message drop_column
......Message rename_table
......Message copy_table
......Message truncate_table
......Message username
......Message password
......Message analyze_table
......Message create_trigger
......Message drop_trigger
......Message enable_trigger
......Message disable_trigger
......Message sql_commands
......Message rows_in_seconds
......Message link_to_this
......Message parent_report_column
......Message f4400_p57_lovs_help
......Message f4400_p58_lovcols_help
......Message f4400_p19_triggers_info
......Message f4400_p54_blocks_help
......Message f4400_p53_objects_help
......Message f4400_p55_blockitems_help
......Message f4400_p61_howto_forms_step1
......Message f4400_p61_howto_forms_step2
......Message f4400_p61_howto_forms_step3
......Message f4400_p61_howto_forms_step4
......Message f4400_p61_howto_forms_step5
......Message f4400_p61_howto_forms_step6
......Message page_header
......Message region_button_positons
......Message include
......Message exclude
......Message ui_def_view_db_col_defn
......Message f4400_p17_attribs_info
......Message f4400_p51_migproj_info
......Message f4400_p44_alerts_info
......Message f4400_p59_canvas_info
......Message trigger_flowid_sgid_mismatch
......Message f4400_p63_coords_info
......Message f4400_p64_editor_info
......Message f4400_p65_propclass_info
......Message f4400_p66_recgrps_info
......Message f4400_p67_windows_info
......Message file_upload_toomanyfiles_err
......Message file_upload_authentication_err
......Message file_upload_nosession_err
......Message file_upload_publicuser_err
......Message password_reuse_error
......Message f4400_p69_progunit_info
......Message not_found
......Message navbar
......Message lock
......Message unlock
......Message qb_table_actions
......Message qb_view_actions
......Message ob_position
......Message wwv_flow_create_model_app_release
......Message application
......Message details_for_alt_tag
......Message view_for_alt_tag
......Message error_set_item_state_for_ppr_region
......Message results
......Message compile_failure_trigger
......Message f4400_attribute_module_parameter
......Message f4400_attribute_report
......Message static_files_no_application
......Message redirect
......Message submit
......Message redirect_button_warning
......Message availability_init_cap
......Message schema_is_available
......Message schema_is_not_available
......Message provisioned_space
......Message space_utilization
......Message adjust_provisioned_space
......Message invalid_workspace_name
......Message invalid_schema_name
......Message using_existing_schema
......Message db_object_creation_exception
......Message insert_exception
......Message schema_insert_exception
......Message failure
......Message f4000_lov_name_exists
......Message developers
......Message f4000_applications
......Message changes
......Message dial_chart_low_value
......Message dial_chart_high_value
......Message dial_chart_alert_value
......Message quick_app_load_detail
......Message f4400_p53_blocks_info
......Message f4400_p53_lovs_info
......Message f4400_p53_recgrps_info
......Message f4400_p53_editors_info
......Message f4400_chkbox_selectall
......Message f4400_chkbox_deselectall
......Message f4400_p53_progunits_info
......Message print
......Message template_driven
......Message wwv_flow_tab_mgr_add_new_parent_tab
......Message wwv_flow_copy_metadata_parent_not_found
......Message list_items
......Message shortcuts
......Message trees
......Message page_attributes
......Message page_processes
......Message application_builder
......Message sql_workshop
......Message data_workshop
......Message manage_workspace
......Message create_application
......Message create_object
......Message database_browser
......Message manage_users
......Message monitor_activity
......Message manage_service
......Message wwv_flow_wizard_api_no_page_help
......Message wwv_flow_wizard_api_update_error
......Message wwv_flow_wizard_api_delete_error
......Message wwv_flow_wizard_api_add_row_error
......Message wwv_flow_wizard_api_update_applied
......Message wwv_flow_wizard_api_update_insert_success
......Message wwv_flow_wizard_api_delete_success
......Message wwv_flow_wizard_api_request_error
......Message wwv_flow_wizard_api_tree_root
......Message wwv_flow_help_initial_index_creation
......Message wwv_flow_wizard_api_show_tree
......Message create_flow_no_tabs
......Message create_flow_one_level_tabs
......Message create_flow_two_level_tabs
......Message create_flow_htmldb_auth
......Message create_flow_no_auth
......Message locked
......Message unlocked
......Message run
......Message wwv_flow_save_routine_numeric_err
...dynamic translations used by application: 4411
...Language Maps for Application 4411
...Shortcuts
...web services (9iR2 or better)
...shared queries
...report layouts
...authentication schemes
......scheme 36917030094496871
......scheme 36917105493496871
......scheme 91645213681389498
...application deployment
...application install scripts
...application deployment checks
...application deployment build options
begin
FEHLER in Zeile 1:
ORA-01756: Anführungsstrich fehlt bei Zeichenfolge
ORA-06512: in Zeile 2

Hello
I've downloaded the zip file about 6 times and I'm getting always the same error. I dont even know in which package or part of the script I get this error.
Regards
Erwin

New Install Won't boot after GRUB

I have been using ArchBang for the past year and a half so I finally thought that I knew enough about Linux to try installing a true Arch Linux system.
I followed the beginner instructions carefully and was able to successfully install my system (or at least I thought) and GRUB. I am currently running my system on a Dell inspiron with two separate hard drives. The primary drive is the one I am trying to install Arch on while I have Windows 7 installed on the second drive.
The drive I installed Arch on is /dev/sde. I think that I successfully installed GRUB given that when I boot my computer it goes into GRUB and shows both my Arch Linux install and my Windows 7 system and when I select Windows 7 in GRUB it successfully boots.
But when I selected my Arch install in GRUB the system does not boot. It just shows:
/dev/sda1: clean, 31087/3751936 files, 478966/15000685 blocks
and then I am left with a blinking cursor and after a few minutes I get:
Welcome to emergency mode. Use "systemctl default" or ^D to enter default mode.
Give root password for maintance:
Anyone one how I fix this? Do I need to reinstall? As I said before I didn't receive any errors during the install and GRUB seems to be working correctly. Please remember that I am a newbie but please help!

Trilby wrote:
No you don't need to reinstall, you do need to fix your grub configuration though. It sounds like it is not properly pointing to the root partition.
Post your grub config and your partitioning scheme.
Partition Scheme from lsblk output:
Name MAJ:MIN RM SIZE RO TYPE MOUNTPOINT
sda 8:0 0 931G 0 disk
sda1 8:1 0 57G 0 disk /
sda2 8:2 0 7G 0 disk
sda3 8:3 0 866G 0 disk
sdb 8:16 0 111G 0 disk
sdb 1 8:17 0 111G 0 disk
sr0 11:0 1 1024M 0 disk
I don't now if this output of the partition table is what you want given that the lsblk is the only command I am familiar with. The sdb disk is where the windows install is.
Here is the /boot/grub/grub.cfg file:
### BEGIN /etc/grub.d/00_header ###
insmod part_gpt
insmod part_msdos
if [ -s $prefix/grubenv ]; then
load_env
fi
set default="0"
if [ x"${feature_menuentry_id}" = xy ]; then
menuentry_id_option="--id"
else
menuentry_id_option=""
fi
export menuentry_id_option
if [ "${prev_saved_entry}" ]; then
set saved_entry="${prev_saved_entry}"
save_env saved_entry
set prev_saved_entry=
save_env prev_saved_entry
set boot_once=true
fi
function savedefault {
if [ -z "${boot-once}" ]; then
saved_entry="${chosen}"
saved_env saved_entry
fi
function load_video {
if [ x$feature_all_video_module = xy ]; then
insmod all_video
else
insmod efi_gop
insmod efi_uga
insmod ieee1275_fb
insmod vbe
insmod vga
insmod video_bochs
insmod video_cirrus
fi
if [ x$feature_default_font_path = xy ]; then
font=unicode
else
insmod part_msdos
insmod ext2
set root='hd4,msdos1'
if [x$feature_platform_search_hint = xy ]; then
search --no-floppy --fs-uuid --set=root --hint-bios=hd4,msdos1 --hint-efi=hd4,msdos1 --hint-baremetal=ahci4, msdos1 9fd0e01-89b1-494c-908f-e89db34d80e0
else
search --no-floppy --fs-uuid --set=root 9fd0e01-89b1-494c-908f-e89db34d80e0
fi
font="/usr/share/grub/unicode.pf2"
fi
if loadfont $font ; then
set gfxmode=auto
load_video
insmod gfxterm
set locale_dir=$prefix/locale
set lang=en_US
insmod gettext
fi
terminal_input console
terminal_output gfxterm
set timeout=5
### END /etc/grub.d/00_header ###
### BEGIN /etc/grub.d/10_linux ###
menuentry 'Arch GNU/Linux, with Linux core repo kernel' --class arch --class gnu-linux --class gnu --class os $menuentry_id_option 'gnulinux-core repo kernel-true-9fd0e01-89b1-494c-908f-e89db34d80e0' {
load_video
set gfxpayload=keep
insmod gzio
insmod part_msdos
insmod ext2
set root='hd4,msdos1'
if [ x$feature_platform_search_hint = xy ]; then
search --no-floppy --fs-uuid --set=root --hint-bios=hd4,msdos1 --hint-efi=hd4,msdos1 --hint-baremetal=ahci4, msdos1 9fd0e01-89b1-494c-908f-e89db34d80e0
else
search --no-floppy --fs-uuid --set=root 9fd0e01-89b1-494c-908f-e89db34d80e0
fi
echo 'Loading Linux core repo kernel ...'
linux /boot/vmlinux-linux root=UUID=9fd0e01-89b1-494c-908f-e89db34d80e0 ro quiet
echo 'Loading initial ramdisk ...'
initrd /boot/initramfs-linux-fallback.img
### END /etc/grub.d/10_linux ###
### BEGIN /etc/grub.d/20_linux_xen ###
### END /etc/grub.d/20_linux_xen ###
### BEGIN /etc/grub.d/20_memtext86+ ###
### END /etc/grub.d/20_memtext86+ ###
### BEGIN /etc/grub.d/30_os-prober ###
menuentry 'Windows 7 (loader) (on /dev/sdf1)' --class windows --class os $menuentry_id_option 'osprober-chain-44F084A6F0849FB2' {
insmod part_msdos
insmod ntfs
set root="hd5,msdos1'
if [ x$feature_platform_search_hint = xy ]; then
search --no-floppy --fs-uuid --set=root --hint-bios=hd4,msdos1 --hint-efi=hd4,msdos1 --hint-baremetal=ahci4, msdos1 44F084A6F0849FB2
else
search --no-floppy --fs-uuid --set=root 44F084A6F0849FB2
fi
chainloader +1
### END /etc/grub.d/30_os-prober ###
### BEGIN /etc/grub.d/40_custom ###
# This files provides an easy way to add custom menu entries. Simply type the
# menu entries you want to add after this comment. Be careful not to change
# the 'exec tail' line above.
### END /etc/grub.d/40_custom ###
### BEGIN /etc/grub.d/41_custom ###
if [ -f ${config_directory}/custom.cfg ]; then
source ${config_directory}/custom.cfg
elif [ -z "${config_directory}" -a -f $prefix/custom.cfg ]; then
source $prefix/custom.cfg;
fi
### END /etc/grub.d/41_custom ###
Last edited by johnnymike (2012-10-15 01:52:09)

New install fails at checking file system. HELP!

I just installed arch for the first time and followed everything very carefully. They only part that i was heasitant about was where to install the MBR. I installed it on the SDA. not sda 1 or sda2 ect.......i think that is what went wrong but dont know how to fix it.....or it might be something completely different. can someone help?

JoeKer wrote:
fsckd wrote:To answer your question on reformatting the boot partition, using a different linux system, mount it, perhaps on /mnt/brokenboot. Then, copy the files over to another disk by cp -rp /mnt/brokenboot /anotherdisk/. Unmount the broken boot. Format it using mke2fs. Mount it again. Copy the files back. You may need to reinstall grub afterwords.
i would do that but boot is ext2.....it ooks lke the problem is wth the superblock of root.....any ideas?
Then why did you write this:
JoeKer wrote:so i really just want to rewrite the /boot partition as ext 2 or 3 and be done with it but cant figure out how to do this.....can anyone tell me exactly what is written in boot? could i boot into a live cd and try to fix it from there? (like system rescue cd)
Meh, figure out what your problem is before asking for help, and when people ask you for more info, give it.

IBook G4 fails to boot with internal HD installed, works when removed

The short version: My iBook started failing to boot via any method (gray screen) and the boot menu (Option during startup) would freeze. Replaced HD, things were better. Six months into new HD, nearly the same symptoms appear again. Removed HD, now running off different HD via FireWire.
The long version–
Back in late 2008-12, my iBook started failing to boot up. Usually it would refuse to boot from any source. Booting the internal disk (10.4.11) would get to a gray screen without any logo and stay there. Holding down Option, the boot menu would come up, but it would usually freeze before it displayed any volumes. Booting from CD (AHT, or OS install disc) would fail in nearly the same way as booting from the internal drive. Target Disk Mode would start, but once the other machine tried to access the drive, the FireWire logo would stop moving and the drive would never show up on the other computer. Very rarely, the machine would get a bit further through one of the boot mechanisms, but it usually froze while booting or just after login.
This machine has gone through three logic boards in the past, so I suspected that was the problem again. I took it to a local Genius Bar and the Genius explained that it was probably the hard drive. He said that sometimes, depending on the way the drive fails, it can "take out" other parts of the system due to drawing too much current, etc.
I was a bit skeptical, but it was going to be much cheaper to replace the HD myself than it would be to send it in for a MLB replacement. So I ordered a new HD (80G) and a USB-to-ATA/SATA adapter. I hoped that I would be able to use the adapter to savlage a bit more data off the drive (it originally failed right before a backup!).
After extracting the HD (40G), I connected it to the USB adapter and was able to access the drive just fine. I used another machine to run another backup from the recently removed HD (40G) to one of my FireWire backup drives and proceeded to put the iBook back together with the new HD (80G).
Once it was all back together, the new HD worked fine. I was able to restore the recent backup from my FireWire drive to the internal, and it worked fine. The only oddity I noticed was that the new drive was apparently trying to sleep several times a minute. I used smartctl (installed via MacPorts) to adjust the power management setting on the drive, and that seemed to help. I also started running smartd (also via MacPorts) to better monitor the new drive.
Recently, a bit more than six months after the new HD was installed, the new HD started showing errors in the system.log. I never found any errors in the logs after the previous HD failed (even though I could look through the logs just fine with the drive attached through the ATA-USB adapter).
Jul 2 18:04:40 Blinky kernel\[0]: disk0s3: I/O error.
Jul 2 18:33:43 Blinky smartd\[217]: Device: disk0, ATA error count increased from 0 to 30\n
Jul 3 02:03:42 Blinky smartd\[217]: Device: disk0, ATA error count increased from 30 to 31\n
Jul 3 03:03:42 Blinky smartd\[217]: Device: disk0, ATA error count increased from 31 to 32\n
Jul 6 23:33:42 Blinky smartd\[217]: Device: disk0, ATA error count increased from 32 to 33\n
Jul 7 00:33:42 Blinky smartd\[217]: Device: disk0, ATA error count increased from 33 to 34\n
Jul 7 12:42:24 Blinky smartd\[217]: Device: disk0, ATA error count increased from 34 to 36\n
Jul 7 13:17:59 Blinky kernel\[0]: disk0s3: I/O error.
+same error message a bit faster than one every 3 seconds+
Jul 7 13:23:00 Blinky kernel\[0]: disk0s3: I/O error.
Jul 7 13:33:44 Blinky smartd\[217]: Device: disk0, ATA error count increased from 36 to 615\n
Jul 7 21:17:05 Blinky kernel\[0]: disk0s3: I/O error.
Jul 7 21:17:12 Blinky kernel\[0]: disk0s3: I/O error.
Jul 7 21:17:12 Blinky kernel\[0]: disk0s3: I/O error.
Jul 7 21:17:12 Blinky kernel\[0]: disk0s3: I/O error.
Jul 7 21:17:15 Blinky kernel\[0]: disk0s3: I/O error.
Jul 7 21:17:18 Blinky kernel\[0]: disk0s3: I/O error.
Jul 7 21:17:21 Blinky kernel\[0]: disk0s3: I/O error.
Jul 7 21:17:23 Blinky kernel\[0]: disk0s3: I/O error.
Jul 7 21:17:29 Blinky kernel\[0]: disk0s3: I/O error.
Jul 7 21:18:17 Blinky kernel\[0]: disk0s3: I/O error.
Jul 7 21:19:21 Blinky kernel\[0]: disk0s3: I/O error.
Jul 7 21:19:23 Blinky kernel\[0]: disk0s3: I/O error.
I did not notice the errors until the afternoon of the 7th when the problem became evident. The events around 13:00 happened when I was trying to run a backup. The first backup failed in an odd way (when I came back to check on it later that evening, SuperDuper! seemed to have quit running). So I restarted the backup and started looking around in the logs. That is when I noticed the kernel I/O error messages. When I asked smartctl to query the drive, it showed that many errors had been occurring and it displayed the drive's log of the last five or so errors (alas, I did not save this output). Meanwhile the re-run of SuperDuper! was having problems again. It seemed to have hung (no SDAgent or SDCopy processes were running, but the main UI was still there). Since the backup was not getting anywhere, I decided to shutdown for a while and try again later.
When I did try again later, I was back in the situation of six months ago. It would not boot at all (no internal, no FireWire, no CD/DVD, boot menu hangs, Target Disk Mode hangs). So, I opened up the system, removed the HD and put it back together without an internal HD. The machine is now able to boot and run from FireWire. Again, the (6 month old, 80G) HD "works fine" via the USB adapter. If SMART were available through the USB adapter, I could check to see if the drive is continuing to have problems. I used SuperDuper! to copy the HD to a volume on my FireWire drive which is how I an now running the system.
Has anyone had any similar problems? Any idea why my iBook seems to be killing/rejecting hard drives? (I say killing because, while the drive is connected internally, it certainly seems to be dying. I say rejecting because once the drive is out of the system, both the drive and the system seem to "recover".) I have read messages there where others report success having their iBook MLB resoldered ("reball"). Has anyone experienced substantially similar issues that were solved with a resolder repair?
Thanks!

I was able to test my “failing” ATA drives in a G4 Mac mini (I had to take the mini apart because its drive had finally failed). I was able to successfully boot the Mac mini with either of my iBook drives installed. Once booted, +Disk Utility+ said that each one's SMART Status was Verified. I used smartctl to pull the full SMART info while I had them installed in the Mac mini.
Since the drives were still “good”, I think this emphasizes that the problem is with the ATA interface on my iBook's logic board. Maybe it is broken, or maybe it just needs to be resoldered. For now I am happy just booting off an external Firewire drive.
BTW, I ended up installing the 6 month old 80G drive in the mini. It has been working OK for 10 days now. As long as it continues to operate normally in the mini, it will serve as evidence that my iBook's HD ATA controller is borked. I just hope the ATA controller is more capable of accepting its fallibility than was HAL.
There is a minor problem with the 80G in the mini in that I am unable to use hdapm to change the aggressive head unloading that the drive suffers. I was able to adjust it with hdapm while it was in my iBook. I am able to adjust it with hdparm under Linux on the mini. Luckily the change I made while booted in Linux "sticks" after rebooting back into Mac OS X (I hear it will be lost if the drive is completely powered off though).

New Windows server 2003 Hyper-V guest fails to boot

Hello,
I'm currently doing some virtualization experiments on my new server hardware. The host hardware is:
IBM x3650 M4
x2 Xeon E5-2609
32GB RAM
x2 480 GB SSDs
Server OS: Windows server 2012
I'd like to test some legacy app virtualization. I've configured a VM and have installed Windows server 2003. The install is done via DVD. The issue at hand is that after the initial installation, the server fails to boot. The VM goes into a reboot loop
and so far the only error logging I'm able to find is in the hosts event log.
Log Name: Microsoft-Windows-Hyper-V-Worker-Admin
Source: Microsoft-Windows-Hyper-V-Worker
Date: 7/8/2014 2:14:48 PM
Event ID: 18560
Task Category: None
Level: Critical
Keywords:
User: NT VIRTUAL MACHINE\A0D20FA4-B27B-4B58-85C1-87D74B0ADD2D
Computer: CCSTS1.cnet2k.cornerstonecredit.net
Description:
'LegacyTS' was reset because an unrecoverable error occurred on a virtual processor that caused a triple fault. If the problem persists, contact Product Support. (Virtual machine ID A0D20FA4-B27B-4B58-85C1-87D74B0ADD2D)
Event Xml:
<Event xmlns="http://schemas.microsoft.com/win/2004/08/events/event">
<System>
<Provider Name="Microsoft-Windows-Hyper-V-Worker" Guid="{51DDFA29-D5C8-4803-BE4B-2ECB715570FE}" />
<EventID>18560</EventID>
<Version>0</Version>
<Level>1</Level>
<Task>0</Task>
<Opcode>0</Opcode>
<Keywords>0x8000000000000000</Keywords>
<TimeCreated SystemTime="2014-07-08T21:14:48.544007000Z" />
<EventRecordID>159</EventRecordID>
<Correlation />
<Execution ProcessID="1512" ThreadID="3536" />
<Channel>Microsoft-Windows-Hyper-V-Worker-Admin</Channel>
<Computer>CCSTS1.cnet2k.cornerstonecredit.net</Computer>
<Security UserID="S-1-5-83-1-2698121124-1264104059-3615998341-769460811" />
</System>
<UserData>
<VmlEventLog xmlns:auto-ns2="http://schemas.microsoft.com/win/2004/08/events" xmlns="http://www.microsoft.com/Windows/Virtualization/Events">
<VmName>LegacyTS</VmName>
<VmId>A0D20FA4-B27B-4B58-85C1-87D74B0ADD2D</VmId>
<Rax>0x0</Rax>
<Rbx>0x0</Rbx>
<Rcx>0x0</Rcx>
<Rdx>0x0</Rdx>
<Rsp>0x804de00c</Rsp>
<Rbp>0x0</Rbp>
<Rsi>0x0</Rsi>
<Rdi>0x0</Rdi>
<R8>0x0</R8>
<R9>0x0</R9>
<R10>0x0</R10>
<R11>0x0</R11>
<R12>0x0</R12>
<R13>0x0</R13>
<R14>0x0</R14>
<R15>0x0</R15>
<Rip>0x80547c7c</Rip>
<Rflags>0x10046</Rflags>
<FpControlStatus>7F030000000000000000000000000000</FpControlStatus>
<XmmControlStatus>0000000000000000801F0000FFFF0000</XmmControlStatus>
<Cr0>0x8001003d</Cr0>
<Cr2>0x804ddffc</Cr2>
<Cr3>0xa02000</Cr3>
<Cr4>0x20</Cr4>
<Cr8>0xf</Cr8>
<Xfem>0x1</Xfem>
<Dr0>0x0</Dr0>
<Dr1>0x0</Dr1>
<Dr2>0x0</Dr2>
<Dr3>0x0</Dr3>
<Dr6>0xffff0ff0</Dr6>
<Dr7>0x400</Dr7>
<Es>0000000000000000FFFFFFFF2300F3C0</Es>
<Cs>0000000000000000FFFFFFFF08009BC0</Cs>
<Ss>0000000000000000FFFFFFFF100093C0</Ss>
<Ds>0000000000000000FFFFFFFF2300F3C0</Ds>
<Fs>00F0DFFF00000000FF1F0000300093C0</Fs>
<Gs>0000000000000000FFFFFFFF00000000</Gs>
<Ldtr>00000000000000000000000000000000</Ldtr>
<Tr>90685580000000006800000050008B00</Tr>
<Idtr>000000000000FF0700F4038000000000</Idtr>
<Gdtr>000000000000FF0300F0038000000000</Gdtr>
<Tsc>0x148e4294</Tsc>
<ApicBase>0xfee00900</ApicBase>
<SysenterCs>0x0</SysenterCs>
<SysenterEip>0x0</SysenterEip>
<SysenterEsp>0x0</SysenterEsp>
</VmlEventLog>
</UserData>
</Event>
My VM config
<?xml version="1.0" encoding="UTF-16" standalone="yes"?>
<configuration>
<_24984ed0-bdad-4b90-82b2-5d59f874e91e_>
<ChannelInstanceGuid type="string">{E4E9CD0E-4BBF-4C1B-B655-715781690655}</ChannelInstanceGuid>
</_24984ed0-bdad-4b90-82b2-5d59f874e91e_>
<_7d80d3db-61ee-4879-8879-5609f1100ad0_>
<address type="string">5353,00000000,00</address>
<version type="integer">1</version>
</_7d80d3db-61ee-4879-8879-5609f1100ad0_>
<_83f8638b-8dca-4152-9eda-2ca8b33039b4_>
<controller0>
<drive0>
<pathname type="string">E:\Hyper-V\VHD\LegacyTS.vhdx</pathname>
<pool_id type="string"></pool_id>
<type type="string">VHD</type>
</drive0>
<drive1>
<pathname type="string"></pathname>
<type type="string">NONE</type>
</drive1>
</controller0>
<controller1>
<drive0>
<pathname type="string">SCSI\CDROM&VEN_IBM_SATA&PROD_DEVICE_81Y3681\4&1864BF9E&0&010000</pathname>
<pool_id type="string"></pool_id>
<type type="string">ISO</type>
</drive0>
<drive1>
<pathname type="string"></pathname>
<type type="string">NONE</type>
</drive1>
</controller1>
<version type="integer">5</version>
</_83f8638b-8dca-4152-9eda-2ca8b33039b4_>
<_8e3a359f-559a-4b6a-98a9-1690a6100ed7_>
<port0>
<connection type="string"></connection>
</port0>
<port1>
<connection type="string"></connection>
</port1>
<version type="integer">2</version>
</_8e3a359f-559a-4b6a-98a9-1690a6100ed7_>
<_8f0d2762-0b00-4e04-af4f-19010527cb93_>
<controller0>
<drive0>
<pathname type="string"></pathname>
<type type="string">VFD</type>
</drive0>
</controller0>
<version type="integer">1</version>
</_8f0d2762-0b00-4e04-af4f-19010527cb93_>
<_a80e9c62-750a-4a6b-9548-d46677e806be_>
<ChannelInstanceGuid type="string">{23c9c636-93de-4aec-9bef-220766177a24}</ChannelInstanceGuid>
<Connection>
<AltPortName type="string">Dynamic Ethernet Switch Port</AltPortName>
<AltSwitchName type="string">Intel(R) I350 Gigabit Network Connection - Virtual Switch</AltSwitchName>
<AuthorizationScope type="string"></AuthorizationScope>
<ChimneyOffloadWeight type="integer">0</ChimneyOffloadWeight>
<Feature_C885BFD1-ABB7-418F-8163-9F379C9F7166>
<DisplayName type="string"></DisplayName>
<Flags type="integer">0</Flags>
<Setting_97274751-A1EC-4DC2-941D-B7F9A1AED814>
<Data type="bytes">AAIAAGQAAAAAAAAAAQAAAAAAAAA=
</Data>
<Version type="integer">256</Version>
</Setting_97274751-A1EC-4DC2-941D-B7F9A1AED814>
<Settings>
<Id type="string">97274751-A1EC-4DC2-941D-B7F9A1AED814</Id>
</Settings>
</Feature_C885BFD1-ABB7-418F-8163-9F379C9F7166>
<Features>
<Id type="string">C885BFD1-ABB7-418F-8163-9F379C9F7166</Id>
</Features>
<HostResources>
<HostResource type="string">8758EB1A-9687-41FC-9319-AE867D46BA5C</HostResource>
</HostResources>
<PoolId type="string"></PoolId>
<PreventIPSpoofing type="bool">False</PreventIPSpoofing>
<TestReplicaPoolId type="string"></TestReplicaPoolId>
<TestReplicaSwitchName type="string"></TestReplicaSwitchName>
</Connection>
<FriendlyName type="string">Network Adapter</FriendlyName>
<IsConnected type="bool">True</IsConnected>
<MacAddress type="string">00-15-5D-01-18-02</MacAddress>
<MacAddressIsStatic type="bool">False</MacAddressIsStatic>
<PortName type="string">E7F02418-A1EB-4FF9-84F8-BF461B2D00C6</PortName>
<SwitchName type="string">8758EB1A-9687-41FC-9319-AE867D46BA5C</SwitchName>
<VpciInstanceGuid type="string">{E9444985-111B-404A-82FE-48608A397676}</VpciInstanceGuid>
</_a80e9c62-750a-4a6b-9548-d46677e806be_>
<_ac6b8dc1-3257-4a70-b1b2-a9c9215659ad_>
<base_board>
<serial_number type="string">9595-3600-2199-6834-7686-3927-30</serial_number>
</base_board>
<bios_guid type="string">{B54BE7B5-05A4-4C4A-A2BD-D63272C7CCCD}</bios_guid>
<bios_serial_number type="string">9595-3600-2199-6834-7686-3927-30</bios_serial_number>
<boot>
<device0 type="string">Optical</device0>
<device1 type="string">HardDrive</device1>
<device2 type="string">Network</device2>
<device3 type="string">Floppy</device3>
</boot>
<chassis>
<asset_tag type="string">8437-8592-0329-9603-9215-1886-12</asset_tag>
<serial_number type="string">9595-3600-2199-6834-7686-3927-30</serial_number>
</chassis>
<num_lock type="bool">False</num_lock>
<version type="integer">2</version>
</_ac6b8dc1-3257-4a70-b1b2-a9c9215659ad_>
<_db8b9818-b4bb-4725-b99d-b4612716b6b4_>
<version type="integer">0</version>
</_db8b9818-b4bb-4725-b99d-b4612716b6b4_>
<global_settings>
<devices>
<allow_reduced_fc_redundancy type="bool">False</allow_reduced_fc_redundancy>
<generation_id type="string">883d11122d9b7b2c521be0c045ef3760</generation_id>
<storage_allow_full_scsi_command_set type="bool">False</storage_allow_full_scsi_command_set>
</devices>
<disk_merge_pending type="bool">False</disk_merge_pending>
<metrics>
<devicetype>
<deviceinstance>
<guid type="string">B637F346-6A0E-4DEC-AF52-BD70CB80A21D</guid>
<metric>
<enabled type="bool">False</enabled>
<lastcomputedtime type="integer">0</lastcomputedtime>
<peaktime type="integer">0</peaktime>
<poolid type="string"></poolid>
<resourcetypeid type="string">B637F347-6A0E-4DEC-AF52-BD70CB80A21D</resourcetypeid>
<starttime type="integer">0</starttime>
<typecode type="string">3F6F1051-C8FC-47EF-9821-C07240848748;0</typecode>
<value type="integer">0</value>
</metric>
</deviceinstance>
<guid type="string">B637F346-6A0E-4DEC-AF52-BD70CB80A21D</guid>
</devicetype>
<devicetype>
<deviceinstance>
<guid type="string">4764334D-E001-4176-82EE-5594EC9B530E</guid>
<metric>
<enabled type="bool">False</enabled>
<lastcomputedtime type="integer">0</lastcomputedtime>
<peaktime type="integer">0</peaktime>
<poolid type="string"></poolid>
<resourcetypeid type="string">4764334E-E001-4176-82EE-5594EC9B530E</resourcetypeid>
<starttime type="integer">0</starttime>
<typecode type="string">394DCE66-458F-4895-AE56-41D7C9602A49</typecode>
<value type="integer">0</value>
</metric>
<metric>
<enabled type="bool">False</enabled>
<lastcomputedtime type="integer">0</lastcomputedtime>
<peaktime type="integer">0</peaktime>
<poolid type="string"></poolid>
<resourcetypeid type="string">4764334E-E001-4176-82EE-5594EC9B530E</resourcetypeid>
<starttime type="integer">0</starttime>
<typecode type="string">FF85EA46-9933-4436-BE5D-C96827399966</typecode>
<value type="integer">0</value>
</metric>
<metric>
<enabled type="bool">False</enabled>
<lastcomputedtime type="integer">0</lastcomputedtime>
<peaktime type="integer">0</peaktime>
<poolid type="string"></poolid>
<resourcetypeid type="string">4764334E-E001-4176-82EE-5594EC9B530E</resourcetypeid>
<starttime type="integer">0</starttime>
<typecode type="string">04BDF59E-580D-4441-8828-FFFE44472D2D</typecode>
<value type="integer">0</value>
</metric>
</deviceinstance>
<guid type="string">4764334D-E001-4176-82EE-5594EC9B530E</guid>
</devicetype>
<devicetype>
<deviceinstance>
<guid type="string">83F8638B-8DCA-4152-9EDA-2CA8B33039B4</guid>
<metric>
<enabled type="bool">False</enabled>
<lastcomputedtime type="integer">0</lastcomputedtime>
<peaktime type="integer">0</peaktime>
<poolid type="string"></poolid>
<resourcetypeid type="string">70BB60D2-A9D3-46AA-B654-3DE53004B4F8</resourcetypeid>
<starttime type="integer">0</starttime>
<typecode type="string">AD29978B-AAB6-44AE-81CD-0609BF929F18;0\0\L</typecode>
<value type="integer">0</value>
</metric>
</deviceinstance>
<guid type="string">83F8638B-8DCA-4152-9EDA-2CA8B33039B4</guid>
</devicetype>
</metrics>
<owner>
<sid type="string">S-1-5-21-1940488291-1951097212-1584025624-1392</sid>
</owner>
<power>
<host_shutdown>
<action type="integer">1</action>
</host_shutdown>
<host_startup>
<action type="integer">1</action>
</host_startup>
</power>
<snapshots>
<list>
<size type="integer">0</size>
</list>
</snapshots>
<unexpected_termination>
<action type="integer">1</action>
</unexpected_termination>
<vhd_path_acled type="bool">True</vhd_path_acled>
</global_settings>
<manifest>
<size type="integer">11</size>
<vdev001>
<device type="string">58f75a6d-d949-4320-99e1-a2a2576d581c</device>
<flags type="integer">1</flags>
<instance type="string">58F75A6D-D949-4320-99E1-A2A2576D581C</instance>
<name type="string">Microsoft Synthetic Mouse</name>
</vdev001>
<vdev002>
<device type="string">197f74e3-b84b-46de-8ae6-82f1cd181cdc</device>
<flags type="integer">1</flags>
<instance type="string">197F74E3-B84B-46DE-8AE6-82F1CD181CDC</instance>
<name type="string">Microsoft Synthetic Keyboard</name>
</vdev002>
<vdev003>
<device type="string">f3cf6965-e8d3-44a9-9b7d-a04245ea7525</device>
<flags type="integer">1</flags>
<instance type="string">F3CF6965-E8D3-44A9-9B7D-A04245EA7525</instance>
<name type="string">Microsoft Synthetic Video</name>
</vdev003>
<vdev004>
<device type="string">84eaae65-2f2e-45f5-9bb5-0e857dc8eb47</device>
<flags type="integer">1</flags>
<instance type="string">84EAAE65-2F2E-45F5-9BB5-0E857DC8EB47</instance>
<name type="string">Microsoft Heartbeat Component</name>
</vdev004>
<vdev005>
<device type="string">2a34b1c2-fd73-4043-8a5b-dd2159bc743f</device>
<flags type="integer">1</flags>
<instance type="string">2A34B1C2-FD73-4043-8A5B-DD2159BC743F</instance>
<name type="string">Microsoft Key-Value Pair Exchange Component</name>
</vdev005>
<vdev006>
<device type="string">9f8233ac-be49-4c79-8ee3-e7e1985b2077</device>
<flags type="integer">1</flags>
<instance type="string">9F8233AC-BE49-4C79-8EE3-E7E1985B2077</instance>
<name type="string">Microsoft Shutdown Component</name>
</vdev006>
<vdev007>
<device type="string">2497f4de-e9fa-4204-80e4-4b75c46419c0</device>
<flags type="integer">1</flags>
<instance type="string">2497F4DE-E9FA-4204-80E4-4B75C46419C0</instance>
<name type="string">Microsoft Time Synchronization Component</name>
</vdev007>
<vdev008>
<device type="string">5ced1297-4598-4915-a5fc-ad21bb4d02a4</device>
<flags type="integer">1</flags>
<instance type="string">5CED1297-4598-4915-A5FC-AD21BB4D02A4</instance>
<name type="string">Microsoft VSS Component</name>
</vdev008>
<vdev009>
<device type="string">6c5addb9-a11a-4e8e-84cb-e6208201db63</device>
<flags type="integer">1</flags>
<instance type="string">6C5ADDB9-A11A-4E8E-84CB-E6208201DB63</instance>
<name type="string">Microsoft RDV Component</name>
</vdev009>
<vdev010>
<device type="string">2fc216b0-d2e2-4967-9b6d-b8a5c9ca2778</device>
<flags type="integer">1</flags>
<instance type="string">A80E9C62-750A-4A6B-9548-D46677E806BE</instance>
<name type="string">Synthetic Ethernet Port</name>
</vdev010>
<vdev011>
<device type="string">d422512d-2bf2-4752-809d-7b82b5fcb1b4</device>
<flags type="integer">1</flags>
<instance type="string">24984ED0-BDAD-4B90-82B2-5D59F874E91E</instance>
<name type="string">Synthetic SCSI Controller</name>
</vdev011>
<version type="integer">260</version>
</manifest>
<properties>
<global_id type="string">B37E54CD-FFBB-44DA-8B7C-322B922EAD72</global_id>
<highly_available type="bool">False</highly_available>
<last_powered_off_time type="integer">130493284127496105</last_powered_off_time>
<last_powered_on_time type="integer">130493284065876653</last_powered_on_time>
<last_state_change_time type="integer">130493284127496105</last_state_change_time>
<name type="string">LegacyTS</name>
<notes type="string"></notes>
<type_id type="string">Virtual Machines</type_id>
<version type="integer">1024</version>
</properties>
<settings>
<global>
<logical_id type="string">B37E54CD-FFBB-44DA-8B7C-322B922EAD72</logical_id>
</global>
<memory>
<bank>
<dynamic_memory_enabled type="bool">True</dynamic_memory_enabled>
<limit type="integer">1048576</limit>
<priority type="integer">5000</priority>
<reservation type="integer">512</reservation>
<size type="integer">4096</size>
<target_memory_buffer type="integer">20</target_memory_buffer>
</bank>
<vnuma>
<max_size_per_node type="integer">14770</max_size_per_node>
</vnuma>
</memory>
<processors>
<count type="integer">1</count>
<features>
<limit type="bool">False</limit>
</features>
<limit type="integer">100000</limit>
<limit_cpuid type="bool">False</limit_cpuid>
<reservation type="integer">0</reservation>
<vnuma>
<count_per_node>
<max type="integer">4</max>
</count_per_node>
<node_per_socket>
<max type="integer">1</max>
</node_per_socket>
</vnuma>
<weight type="integer">100</weight>
</processors>
<stopped_at_host_shutdown type="bool">False</stopped_at_host_shutdown>
<vnuma>
<enabled type="bool">False</enabled>
</vnuma>
</settings>
</configuration>
If its relevant, the host is not yet activated license wise. I downloaded the demo version so I could test my idea before making a purchase to go ahead with full implementation.
As it stands right now I'm not sure how to troubleshoot this. Many searches on google have not turned up any helpful info. Does anyone have any ideas?
Thanks,
D

Hi ,
First , please refer to the supported guest OS of windows 2012 hyper-v :
http://technet.microsoft.com/library/hh831531.aspx
2003/R2 should be with sp2 and max 2 virtual processors .
"'LegacyTS' was reset because an unrecoverable error occurred on a virtual processor that caused a triple fault."
If the issue is not due to the above items , you can try to check the "CPU compatibility " in that VM settings for troubleshooting:
Hope it helps
Best Regards
Elton Ji
We
are trying to better understand customer views on social support experience, so your participation in this
interview project would be greatly appreciated if you have time.
Thanks for helping make community forums a great place.

New install fails to boot

Similar Messages

Maybe you are looking for