System BOOT Fail

I'm hoping somebody can help me shed some light on this one because in my research I've come across at least one other Arch user who had similar issues.
First I'll lay out my system hardware since it seems to be a common trend for people who have this issue.
Asus P5N-D
Intel Core 2 Quad Q6700
Dual nVidia 7900 GTS SLI
4 GB RAM
Anyhow, everytime I boot my system the BIOS splash screen comes up and then I hear the fans on my video cards spool up to full speed then spool back down and the BIOS splash screen disappears a second then comes back and once it's done on the splash screen I get to a screen that says "Warning System BOOT Fail. Your system last boot fail or POST interrupted." Then I can choose F1 to continue and ignore the problem or hit DEL to go to system settings.
I've done lots of googling on the problem and the most informative thing I believe I've come across is this ... https://bugs.launchpad.net/ubuntu/+sour … bug/791089
I tried using their method of blacklisting nv_tco but it didn't do anything for me. So then I tried sudo rmmod nv_tco and I get a message that it doesn't even exist.
I did just run pacman -Syu and noticed there was an update to the kernel. There were some mentions of updating some nVidia stuff. However towards the end of running the update I get an error about conflicting files. "initscripts: /etc/profile.d/locale.sh exists in filesystem" I'll have to look into that one as well.
EDIT: Did a quick search on the pacman thing.... guess I missed that post in the news section. Updating now!
I'm pretty new so if there is any type of configuration files or anything I need to post up here please let me know. Thanks!
Last edited by bronco21016 (2011-10-30 16:12:36)

KingX wrote:Looks like all the users having this difficulty have the same ASUS motherboard P5N series. Try checking for any BIOS update by ASUS, pretty sure the problem lies with the board and not with kernel or OS. Just a wild shot by try booting with just one video card instead of the SLi setup. Lastly, does your system gives any beeps when the bios is flashing/disappearing?
I'm running the latest BIOS 1401 from the ASUSTeK website.
I did some experimenting with removing video cards testing each card individually. One card gives me absolutely nothing on the screen so it's dead. I tried the other card on its own and I still get the issue of POST fail.
No beeps from the system at all. I even installed the system speaker to see if it would give me any codes but it doesn't.
One thing I did notice is that after the first BIOS splash screen the system is completely restarting. All of the fan lighting turns off for about a second then comes back on and I get the BIOS splashscreen again.

Similar Messages

WL 7.0 Node Manager - auto restart after system boot fails

I have configured node manager to automatically restart managed servers on my Solaris
2.8 host. When I kill the managed server from the command line, node manager automatically
restarts the managed server just as I would expect. But when I reboot the system,
node manager does not restart the managed server. I started the managed server before
the reboot using node manager/admin console as the documentation states. I see nothing
in the logs that indicate any attempt by node manager to start the previously running
managed server, although node manager itself starts up OK after the reboot. Any
suggestions on how to get this working?
Here is my node manager config.xml contents:
#Saved configuration for webdevDomain_apps
#Sun Jul 14 23:12:08 EDT 2002
serverListenProtocol=http
serverListenHost=198.242.140.49
serverHealthCheckIntervalSeconds=180
TimeStamp=1026702630479
javaHome=/usr/jdk1.3
serverRestartDelaySeconds=60
command=online
ts2={3DES}QQj3hoYUACzB1csbrEth8Q\=\=
ts1=system
serverHealthCheckTimeoutSeconds=60
weblogic.Name=apps
java.security.policy=/home/weblogic/weblogic700/server/lib/weblogic.policy
RootDirectory=/home/webdev/weblogic700
serverStartArgs=-Xms64m -Xmx256m
- John

you are 100% right.
NM restarts MS's incase of
i) server crashes
ii) system reboots.
Kumar
John wrote:
Actually we were given a solution to this problem:
The node manager (NM) should restart managed servers (MS) upon reboot of the box.
There is one exception however - this can't happen if the MS is part of a cluster
and it hosts a migratable service. Currently there are two migratable services
- JMS and JTA. You need to have explicitly setup the migratable services for the
MS via the console.
Assuming you are not using these as migratable services you must explicitly set
a flag to indicate the MS is not hosting migratable services. This can be done
via the command line. It only needs to be done once and it will update the config.xml
file. The command line is:
java weblogic.Admin -url t3://adminhost:port -username <user> -password <password>
SET -mbean <domain>:Name=<MS name>,Type=Server -property HostsMigratableServices
false
You should see a simple reply of 'OK'.
Once this is done your should be able to reboot the box and after restart the
managed server should be running.
It worked!
Kumar Allamraju <[email protected]> wrote:
NM will only restart managed server's if they are abruptly killed.
We have no mechanism inplace to start managed server's upon system reboot.
May be you should write some startup scripts to start WLS upon system
start.
Kumar
John wrote:
I have configured node manager to automatically restart managed servers
on my Solaris
2.8 host. When I kill the managed server from the command line, node
manager automatically
restarts the managed server just as I would expect. But when I reboot
the system,
node manager does not restart the managed server. I started the managed
server before
the reboot using node manager/admin console as the documentation states.
I see nothing
in the logs that indicate any attempt by node manager to start the
previously running
managed server, although node manager itself starts up OK after the
reboot. Any
suggestions on how to get this working?
- John

Zones not booting - failed to create devlinks: Interrupted system call

I just installed the latest 10_Recommended cluster with 118833-36 kernel patch and now my zones won't boot. I get the error:
(root)Yes Master?> zoneadm list -iv
ID NAME STATUS PATH
0 global running /
- samba installed /export/home/zones/samba
- web installed /export/home/zones/web
- dhcp installed /export/home/zones/dhcp
- dns installed /export/home/zones/dns
- vs1 installed /zdata/zones/vs1
- dss installed /zdata/zones/dss
- test installed /zdata/zones/test
(root)Yes Master?> zoneadm -z test boot
failed to create devlinks: Interrupted system call
console setup: device initialization failed
zoneadm: zone 'test': could not start zoneadmd
zoneadm: zone 'test': call to zoneadmd failed
Also, running devfsadm or drvconfig;devlinks from the global zone will core dump.
Any ideas..??
tia..

First, you gotta change your prompt to something less embarrassing when you post to a public forum :)
I'd forget about the zones problem and focus on why devfsadm core dumps -- that's the core of the problem (no pun intended...no, really!).
First, review the install logs of all the patches installed during the recent service (/var/sadm/patch/*/log). Even if they all show a good completion, check the messages they generated, sometimes they have errors that aren't bad enough to cause a complete failure of the patch. The KJP (118833-36) is probably a good one to start with.
Next I'd "truss" the devfsadm command while it core dumps then get a stack trace of the core (run "adb <corefile>" and type "$C" -- that's old school, I'm sure mdb is much cooler...).
Throw some of the strings from those against sunsolve and see if something sticks.
Good luck!

Recovery Manager fail to start at system boot when pressing F11 in HP mini 210

Product Name : HP mini 210-1118TU
Product Number: CNF01784X4
OS: 7 starter 32 bit
When i press F11 at system boot, it give error message :
" windows could not start because the following file is missing or corrupted
<windows root>\System32\hal.dll.
please re-install a copy of the above file."
Before it I install Windows XP pro, then I use system recover option in my system recover disc to restore my original OS .Afetr it I face some startup issue like "Boot device not found" & "Hard disk not exist" which was solved by F10->Hard disk test & Memory test.
Please, help me to solve it

Factory Reset will wipe all partitions and restore it to a factory state (just like it was when shipped from HP), recovery partition included.

System boot failure after upgrade from linux3.13.8-1 to linux3.14.6-1

I have tried to update the kernel again from 3.13 to 3.14 again, but no luck.
My arch system boot failure with black screen, tried [ctrl]+[alt]+[F1-6] and nothing happen, no any recure shell prompt out.
Then I boot with kernel debug parameters
systemd.log_level=debug systemd.log_target=kmsg log_buf_len=1M
althrough the screen was black, when I reboot and chroot into my system,
I entered the following to find any error messages, please see the link below:
journalctl -b -0 >> ~/3.13_no_problem.log
journalctl -b -1 >> ~/3.14-6_nodebug.log
journalctl -b -2 >> ~/3.14-6_debug.log
3.13_no_problem.log: http://pastebin.com/EQ2Mucq8
3.14-6_nodebug.log: http://pastebin.com/18TRZVRp
3.14-6_debug.log: http://pastebin.com/0QZJBPnf
In both 3.14 journal messages, I found some similar error message:
Jun 15 14:37:47 arch-desktop kernel: [drm:atom_op_jump] *ERROR* atombios stuck in loop for more than 5secs aborting
Jun 15 14:37:47 arch-desktop kernel: [drm:atom_execute_table_locked] *ERROR* atombios stuck executing D218 (len 62, WS 0, PS 0) @ 0xD234
Jun 15 14:37:55 arch-desktop kernel: [drm:atom_op_jump] *ERROR* atombios stuck in loop for more than 5secs aborting
Jun 15 14:37:55 arch-desktop kernel: [drm:atom_execute_table_locked] *ERROR* atombios stuck executing D218 (len 62, WS 0, PS 0) @ 0xD234
Jun 15 14:38:00 arch-desktop kernel: [drm:cypress_dpm_set_power_state] *ERROR* rv770_restrict_performance_levels_before_switch failed
Jun 15 14:38:01 arch-desktop kernel: [drm:atom_op_jump] *ERROR* atombios stuck in loop for more than 5secs aborting
Jun 15 14:38:01 arch-desktop kernel: [drm:atom_execute_table_locked] *ERROR* atombios stuck executing D218 (len 62, WS 0, PS 0) @ 0xD234
Jun 15 14:38:07 arch-desktop kernel: [drm:atom_op_jump] *ERROR* atombios stuck in loop for more than 5secs aborting
Jun 15 14:38:07 arch-desktop kernel: [drm:atom_execute_table_locked] *ERROR* atombios stuck executing D218 (len 62, WS 0, PS 0) @ 0xD234
Jun 15 14:38:13 arch-desktop kernel: [drm:atom_op_jump] *ERROR* atombios stuck in loop for more than 5secs aborting
Jun 15 14:38:13 arch-desktop kernel: [drm:atom_execute_table_locked] *ERROR* atombios stuck executing D218 (len 62, WS 0, PS 0) @ 0xD234
I searched on internet, I think this is caused by my graphic card(ATI 5750), but I have no idea to solve it
I don't know my system boot failure due to these error or another things.
my PC specs:
motherbroad - gigabyte GA-P55A-UD3 (bios ver - F11)
cpu - i5-750
display - ati 5750
os - arch 64bit
Currently, I have downgraded back to 3.13.
I hope someone can give me some idea,
Thanks
Last edited by samtai (2014-06-17 12:17:02)

As there are errors associated with ntpd, I would temporarily disable the ntpd service and also ipv6.
If they are not the only problem, at least your logs would be easier to examine for other problems.

Hyper-V 2012 R2 new VM with ISO in DVD boot failed - default SCSI not IDE

Hi, have created some VMs fine on 2008R2 and 2012 Hyper-V but now onto 2012 R2, am using the Gen 2 VM and hitting install error when booting them from the 2012R2 RTM .ISO (downloaded straight from Technet) loaded into virtual DVD:
I see from http://social.technet.microsoft.com/Forums/windowsserver/en-US/53f901e4-5bd0-4e13-80a2-bca2f57b15e9/hyperv-unable-to-boot-from-cd-or-iso-in-vm-machine?forum=winserverhyperv that Hyper-V seems unable to boot from a synthetic SCSI until guest OS actually
installed - so Catch-22! But I can't add an IDE Controller because it's not on the list:
I tried the Integration Services and it seems fine on the Settings (including ticking the only one unticked - Guest Services) although if you need to run them from the DVD, it has the same problem - you can see them loaded (or the Win2012R2 ISO) in the DVD
Media but you can't make them run through booting on SCSI!
The physical drives are SATA not SCSI but presumably no matter as Hyper-V runs SCSI virtually, but why does Hyper-V default to SCSI and how do I get the DVD to run off an IDE instead if that is the way to install a base OS from .ISO? Or is there an easier
way than all this?
TIA, Phil.

I found this article:
http://blogs.technet.com/b/jhoward/archive/2013/11/11/hyper-v-generation-2-virtual-machines-part-9.aspx
I hope this help.
"...yes, we’re acutely aware that the generation 2 EFI boot loader messages persist on the screen and it can be a little confusing. Essentially what the generation 2 virtual machine did was:
Attempt to boot from the CD SCSI device containing the Windows 8 ISO. This is where the ‘Press any key…’ message came from. As no key was pressed, we went to the next boot entry. (And this is where we didn’t clear the message from the EFI CD boot loader)
I didn’t press F12 (in fact, this VM wasn’t connected to a network), so network boot failed
The SCSI VHDX is raw with no partitioning or file system, so this too failed
So why did the generation 1 virtual machine start setup from the Windows media? The answer is simply that it’s the way Windows media is built, and it’s inconsistent between the PCAT and EFI loaders.
However, it’s relatively simple to solve if you want to avoid the press any key message. In fact, we almost have all the pieces from previous parts. In particular, part 4 where we injected keyboard drivers into the Windows 8 media.
If you loopback mount Windows 8 or 8.1 RTM media, and navigate to the \efi\microsoft\boot directory, you will see there are two versions of cdboot.efi
The default version, cdboot.efi prompts for a keypress. The unused version, cdboot_noprompt.efi doesn’t prompt.
So it’s fairly simple to create modified media which uses the noprompt version. First, copy the contents of the ISO to a working directory, rename cdboot.efi to cdboot_prompt.efi, and rename cdboot_noprompt.efi to cdboot.efi.
Do the same with efisys.bin and efisys_prompt.bin
Then re-use our oscdimg command (in an elevated deployment and imaging tools environment) from part 4 to recreate the media.
Best Regards:
Tamás

Satellite A660 - Will not boot up and HDD boot fail

Hi,
firstly thanks for your time.
Model: Satellite A660 (PSAW3A-07U00R)
The problem started yesterday, the computer was going slow as an application closed, so I held the off button untill the pc turned off. When I restarded the laptop it went to a screen saying: Start windows normally or repair Windows (recomended)
When started normally it just hangs at a blank screen, the repair Windows recommends a system restore to earlier point which didnt work. As it just hangs again. I tried pressing F8 and starting in safe mode but again it just hangs. Then after a few times trying safe mode and another system restore the computer then hangs when I press F8. After this the computer goes past the Toshiba logo screen with F2 and F12 options (which both still work), and then it comes up boot failed then goes blank and comes with boot failed bootfailed with some numbers and letters, then it goes to a small box titled boot menu with 4 options.These are
HDD/SSD Toshiba MK6465GSX
CD/DVD MAT****ABD-CMB UJ141ES
FDD
LAN
If I press ESC it goes through the bootfailed loop and ends up at same screen, if I press enter on "HDD/SSD Toshiba MK6465GSX" then it quickly comes back to screen and at the bottom it says [HDD/SSD Toshiba MK6465GSX] is failed.
I dont understand why it got worse over time. Can anyone think of why this has happend and more importantly how can I get my pc working again? Note: holding 0 then starting does nothing for me atm
regards, Matthew

All you people looking here on this dead thread.....
Toshiba A660 laptops are renowned for having hard drive fails and boot up problems after grinding to a halt.
My solution (after losing 3 hard drives [and a terabyte of family treasured times]) is the following.
Use MALWAREBYTES (free download and use for 28 days)
Scan and fix. Mine found over 300 trojans that 2013 Norton 360 could not find.
Re-boot into safe mode.
SCAN again.
Re-boot and empty the malwarebytes repair files it retains...
Run Norton/McAfee (whichever you have) and you should still have no issues.
Make a back-up repair disc. Ooooops......no you cant...........at least my laptop can`t.
I don`t know why.....
Tell me tosh..... why does windows x64 refuse to allow me to make a system boot disc (even though the laptop is all driver updated and Windows updated)?
Uninstall MalwareBytes when Norton/McAfee tells you there will be a conflict between the two programs.
It tells you to re-boot after uninstalling it.
Then when it re-boots you get a black screen. You cannot even get to bios. You think ytour laptop is turned into a brick frisbee. You pull out the battery in frustration after five minutes.
You replace and re-boot....but again you get no bios or boot up.... you think its destroyed the Bios or graphics somehow....youo can hear the hard-drive but you have no clue whats going on..
Around this time you shake the laptop in frustration.....
Calm down.
Switch on and leave FIFTEEN MINUTES....Ten of which will be a Black nothing screen with maybe a single white underscore line in the top left corner.LEAVE IT ALONE.
Make a sunday dinner for ten people....When you go back to the computer it will be up and running.
When you re-boot again, it will be dead black for five minutes...then boots up... you still think it has a problem... LEAVE IT.
When you reboot again it should work perfect (assuming you have not been overheating it by using it on a cushion on your lap and overheating the insides [use a laptop fan tray]) if you have not shaken your hard drive or caused scrambled damage by pulling the power fifty times like some people do.
I have lost three hard drives and thousands of Gigabytes of treasured family memories discovering the secret the hard way.
Enjoy.
Buy a different brand next time.
ALL Windows system files should be on a SWITCHED (to update) version of Windows.
Spinning drives should be for Data only.

Where to find a driver for a seagate product or the operating system (OS) fails to recognize a seagate drive

Where to find a driver for a seagate product or the operating system (OS) fails to recognize a seagate drive
Name : Seagate Backup+ BL Media
          Type :           Disk
          Partition Map Scheme :           Master Boot Record
          Disk Identifier :           disk1
          Media Name :           Seagate Backup+ BL Media
          Media Type :           Generic
          Connection Bus :           USB
          USB Serial Number :           NA5B83S2
          Device Tree :           IODeviceTree:/PCI0@0/XHC1@14
          Writable :           Yes
          Ejectable :           Yes
          Location :           External
          Total Capacity :           1 TB (10,00,20,48,85,504 Bytes)
          Disk Number :           1
          Partition Number :           0
          S.M.A.R.T. Status :           Not Supported

Seagate website.
Why don't you reformat the drive in Disk Utility or Terminal. Screw that rubbish backup software on the seagate drive.

Boot fails after pacman -Syu [SOLVED]

Hello forums,
I did a full system upgrade two days ago. Getting this on boot
early console in decompress_kernel
Decompressing Linux... Parsing ELF... done.
Booting the kernel.
:: running early hook [udev]
:: running early hook [lvm2]
:: running hook [udev]
:: Triggering uevents...
:: running hook [v86d]
:: running hook [xfs]
:: performing fsck on '/dev/mapper/vg_phobos-lv_root'
/sbin/fsck.xfs: XFS file system.
filesystem '' cannot be mounted, unable to open the datases
:: running cleanup hook [lvm2]
:: running cleanup hook [udev]
ERROR: Failed to mount the real root device
Bailing out, you are on your own. Good luck.
sh: can't access tty: job control turned off
[rootfs /]#
LVM is fine and root partition is fine. I can mount it manually from initramfs console.
Running "./init" or exit at the console results in kernel panic, root mounted in /new_root or not.
pacman -Syu went without problems.
Thanks in advance.
Last edited by zb10948 (2013-11-10 18:00:52)

The issue was initcpio ZFS hook. Evidently, if root partition isn't on ZFS the boot breaks.
In this case, ZFS should be handled by systemd service which will mount ZFS partitions from userland.
Procedure :
inside initcpio console, manually mount the root filesystem, chroot to it and run init
mount /dev/path/to/root /new_root
switch_root /new_root /sbin/init
System boots. Afterwards, remove zfs hook from /etc/mkinitcpio.conf and rerun mkinitcpio. Also check that zfs.service system unit is active and enabled.
Last edited by zb10948 (2013-11-10 18:00:37)

New Error - Unable to Create Any Backups (com.adobe.versioncue.boot - Failed to start com.adobe.vers

A new error just started showing up in my Vc logs: com.adobe.versioncue.boot - Failed to start com.adobe.versioncue.backup.schedule.
Since the report of this error, I am unable to create any kind of Version Cue backups. Has anyone else seen this error?
I had hoped that a simple reboot would alleviate the problem, but it didn't. The error occurs during Vc startup (boot). It's a little odd that Vc was mostly fine until I rescheduled my Windows Backup (ntbackup.exe) to run 90 minutes earlier, and failed to tell Diskeeper to also not auto-defrag 90 minutes earlier. (In other words, it's possible that Diskeeper did its thing the same time ntbackup was running.)
Running Windows XP SP3. I'm going to try a repair install of Vc in a few moments.

Update 2: ntbackup restore of System State to day before last successful Vc backup failed to correct the problem. I can't even run a manual backup.
Can anyone tell me how to determine the ClassPath used by Vc?
There is no stack trace from this error - the exception is caught and handled, so Vc continues to run after creating the single log entry posted in Msg-1 above. By knowing the ClassPath, I may be able to restore the corrupted Java JARs, if that is the root of this problem.
I'd really hate to have to (ntbackup) restore the whole computer back to last Monday...

Boot failed: solaris server does not boot

Hi All,
one of my support person who has administrator previlages tried move the contents of root to trash directory, in the middle it got hung,and he had restrted the server.
Now the solaris does not boot. It says
boot failed
Enter Filename [platform/sun4v/kernel/sparcv9/unix]
and what ever we enter there it says boot cannot read.
Please suggest some workaround, nearly 200 users are down, actually it is our licnese server.

Hi,
What you could try is the following :
Boot the system from the solaris cd into single user mode.
Find out what the disk is you need to mount and mount it under /a
After you have done this you can see if you can move back the stuff that was moved from the root directory to the trash.
If that works then you could try and boot again from the disk to see if everything works again.
Nico

BDD 2007 -- ZTI -- OSD error "The Operating System Installation Failed Unspecified Error (80004005)

Hi there
Wonder if anyone can advise me on a BDD 2007 OS deployment issue? (Apologies if this is in the wrong forum, I couldn't see a forum for BDD 2007.)
First of all, this BDD 2007 server and the OSD config was not done by me. For info, it is part of a SMS 2003 infrastructure.
I am trying to get the XP Pro build process working. I am led to believe the config has been completed.
Unfortunately, after booting the pc from the nic, I get an error. This is the order:
- the 'Initializing Windows PE' splash appears for perhaps 15 seconds
- very briefly, the text changes to 'Initializing Network'
- for a second or two only 'Initializing Windows PE' appears again
- then this error message appears:
"SMS Operating System Deployment - The Operating System Installation failed. Please contact your system administrator for assistance. Unspecified Error (80004005)"
I've spent some time looking into this error (80004005) and from what I can gather it possibly means 'access denied'.
I'm assuming after Windows PE loads the first Task Sequence begins, and if this possibly is where the issue lies?
One thing I cannot understand - the first Task Sequence (Initialization) has this command line (as do most, with different .wsf file):
cscript.exe "%SCRIPTROOT%\ZTIGather.wsf" /localonly
However, I cannot access %SCRIPTROOT% at all, Windows says it can't find it. I can run other variables such as %USERPROFILE%, %SYSTEMROOT%, etc, but cannot open %SCRIPTROOT%.
Is it simply the case that I should create a new system variable (that has not been created by whoever built the server)?
Thanks
John Henry

Since no one has answer this post, I recommend opening a support case with CSS as they can work with you to solve this problem.
Garth Jones | My blogs: Enhansoft and
Old Blog site | Twitter:
@GarthMJ

[SOLVED] System boot halts at [OK] reached target Network

Hello everyone,
I just finished updating my system ( the java-runtime-common was included ) which went well with the instructions provided in the home page. Time for reboot, everything still fine, on the boot everything is green and good to go as always but this time around everything just stands there.
I tried running systemd-analyze blame but the output didn't give me any clue on what's really going on:
5.090s NetworkManager.service
1.569s alsa-restore.service
1.553s systemd-logins.service
1.212s accounts-daemon.service
1.150s systemd-tmpfiles-clean.service
1.027s systemd-vconsole-setup.service
... others less than second services start ups
Any suggestion on what May be the problem?
If you need any more information just tell me what outputs you need, I can't really figure what could be of help at the moment.
Last edited by FacelessJim (2014-11-02 21:32:18)

Ok, I've found him: Light Display Manager. He stops everything. I've cross checked the most recent boot with older boots and the only strings that actually change are these:
Here's the output from
journalctl -b -u lightdm
Nov 02 12:00:25 Archibald systems[1]: Starting Light Display Manager...
Nov 02 12:00:26 Archibald systems[1]: Started Light Display Manager.
Nov 02 12:00:30 Archibald systems[1]: lightdm.service: main process exited, code=exited, status=1/FAILURE
Nov 02 12:00:30 Archibald systems[1]: Unit lightdm.service entered failed state.
Nov 02 12:00:30 Archibald systems[1]: lightdm.service holdoff time over, scheduling restart.
Nov 02 12:00:30 Archibald systems[1]: Stopping Light Display Manager...
It goes on for a while with the same output, and then:
Nov 02 12:00:32 Archibald systems[1]: Starting Light Display Manager...
Nov 02 12:00:32 Archibald systems[1]: lightdm.service start request repeated too quickly, refusing to start.
Nov 02 12:00:32 Archibald systems[1]: Failed to start Light Display Manager.
Nov 02 12:00:32 Archibald systems[1]: Unit lightdm.service entered failed state.
I tried to restart it manually but nothing change.
Any clues?

Boot failed:Enter Filename [/kernel/sparcv9/unix]

Hi All,
one of my support person who has administrator previlages tried move the contents of root to trash directory, in the middle it got hung,and he had restrted the server.
Now the solaris does not boot. It says
boot failed
Enter Filename [platform/sun4v/kernel/sparcv9/unix]
and what ever we enter there it says boot cannot read.
ELF64 read error.
Please suggest some workaround, nearly 200 users are down, actually it is our licnese server.

Hi,
What you could try is the following :
Boot the system from the solaris cd into single user mode.
Find out what the disk is you need to mount and mount it under /a
After you have done this you can see if you can move back the stuff that was moved from the root directory to the trash.
If that works then you could try and boot again from the disk to see if everything works again.
Nico

Is or is not "Application & Driver Recovery DVD" bootable? - SafeMode boot fails-corrupt CryptUI.dll

I'm trying to recover my daughter's Pavilion dm4-3170se. My daughter had not made a recovery disk and has no recent back-up of her data file set.
Problems (and what I have done so far) are quite parallel to what the user reported in this amazingly detailed post:
Difference is that in Safe Mode boot (command line or not), Windows boot fails on a dll, specifically CryptUI.DLL.
While amazingly detailed post user isn't getting into Windows boot, I am...for about 30 DLLs before it chokes on the corrupted one. I have tried a number of other things to get past it to no avail.
My daughter's original Recovery Disc set bought the farm when her house burned. So I ordered and got a replacement set from HP. I am loathe to use it before recovering her data files because she will lose maybe 40% of her professional work.
The delivered Recovery Disc set includes an "Application and Driver Recovery DVD". Given >20 years of Wintel machine tradition, I'm presuming it's bootable. Amazingly Detailed Post user got hers to boot from her DVD drive. But configuring the BIOS to seek the DVD drive as the first boot choice doesn't get it to boot after two tries.
Before I pour more time into this, I'd like the Collective Wisdom here.
Q1: Is this HP disc, numbered 691822-B22, meant to be bootable?
Q2a: If it is, do you imagine I can use the command line interface to copy identifed-as-bad DLL(s) to the HD?
Q2b: If it isn't, why the, er, gollygoshdarn isn't it? Must be an actual reasonable thing...
Thanks for all insights based on experience.
This question was solved.
View Solution.

Hi:
Any HP application and driver DVD I have ever used is not bootable.
It should autorun from the windows desktop once windows has been reinstalled.
That is the only question I can answer of the ones you asked.
Suggestion...
Make your own W7 installation ISO from the link below.
Use that to install W7 and do not delete any partitions or format the drive.
Windows will install and create a Windows.old folder of the current operating system.
Then you can copy any files you need from the Windows.old folder after W7 is installed.
Once you are sure you got what you need, run the recovery disk set to restore the hard drive to its out of the box condition.
Link to W7 ISO files is below. Use the W7 x64 home premium file from the SP1 Media Refresh listing.
http://forums.mydigitallife.info/threads/14709-Windows-7-Digital-River-direct-links-Multiple-Languag...
Then use this tool to transfer the iso file onto a DVD or 4 GB USB flash drive. The tool will also make the iso file bootable.
http://www.microsoftstore.com/store/msusa/html/pbPage.Help_Win7_usbdvd_dwnTool

System BOOT Fail

Similar Messages

Maybe you are looking for