CRS-1 boot failed problem ( REDFS-5-INIT_FAILED)

Hi expert ,
today I face new problem with one RP , :
Initializing DDR SDRAM...found 4096 MB
Initializing ECC on bank 0
Initializing ECC on bank 1
Initializing ECC on bank 2
Initializing ECC on bank 3
Turning off data cache, using DDR for first time
Initializing NVRAM...
Testing a portion of DDR SDRAM ...done
Reading ID EEPROMs ...
Initializing SQUID ...
Initializing PCI ...
PCI0 device[1]: Vendor ID 0x10ee
PCI0 device[1]: Device ID 0x300e
PCI1 device[1]: Device ID 0x1100
PCI1 device[1]: Vendor ID 0x1013
PCI1 device[2]: Device ID 0x680
PCI1 device[2]: Vendor ID 0x1095
PCI1 device[3]: Device ID 0x5618
PCI1 device[3]: Vendor ID 0x14e4
Configuring MPPs ...
Configuring PCMCIA slots ...
System Bootstrap, Version 1.53(20090311:225342) [CRS-1 ROMMON],
Copyright (c) 1994-2009 by Cisco Systems, Inc.
Acquiring backplane mastership ........failed
Board type is 0x100002 (1048578)
Switch 0 initialized
Backplane FE port Up... Enabling
Enabling watchdog
G4(7457-NonSMP-MV64360 Rev 4) platform with 4096 MB of main memory
Acquiring backplane mastership....failed.
Unable to access backplane ... invoking READ EEPROM protocol
Enabling only inter-RP port... successful
Sending backplane ID EEPROM read request
Our MAC address is 0249.4450.0008
Interface link changed state to UP.
Sending ID EEPROM read request.
HIT CTRL-C to abort
ID EEPROM read request successful.
Reconfiguring switches with default config ...
Chassis type: 484
    CARD_RACK_NUMBER: 0
    CARD_SLOT_NUMBER: 0
        CPU_INSTANCE: 1
RACK_SERIAL_NUMBER: TBM13332678
MBI Validation starts ...Our MAC address is 001e.1392.84ee
Interface link changed state to UP.
Interface link state up.
MBI validation sending request.
HIT CTRL-C to abort
MBI validation sending request.
HIT CTRL-C to abort
mbi_val_process_packet: received response.
RACK_NUM = 0, RACK_TYPE=0
Local image to boot : bootflash:disk0/hfr-os-mbi-3.8.2/mbihfr-rp.vm
boot: booting from bootflash:disk0/hfr-os-mbi-3.8.2/mbihfr-rp.vm
tracelogger: starting tracing in background ring mode
tracelogger running with args: -startring -F 1 -F 2
               Restricted Rights Legend
Use, duplication, or disclosure by the Government is
subject to restrictions as set forth in subparagraph
(c) of the Commercial Computer Software - Restricted
Rights clause at FAR sec. 52.227-19 and subparagraph
(c) (1) (ii) of the Rights in Technical Data and Computer
Software clause at DFARS sec. 252.227-7013.
           cisco Systems, Inc.
           170 West Tasman Drive
           San Jose, California 95134-1706
Cisco IOS XR Software for the Cisco XR HFR, Version 3.8.2
Copyright (c) 2009 by Cisco Systems, Inc.
This (D)RP Node is not ready or active for login /configuration
This (D)RP Node is not ready or active for login /configuration
RP/0/RP0/CPU0:Jan 15 09:28:36 : redfs_svr[83]: %OS-REDFS-5-INIT_FAILED : Failed to initialize no devices available: 0x13:No such device
and reboot again , I disabled WATCHDOG but nothing happen,?
this is the show platform from RP0
RP/0/RP1/CPU0:BGD-JAD-PGW1#sh plat
Wed Jan 15 12:08:50.549 Iraq
[KNode            Type            PLIM            State           Config State
0/0/CPU0        MSC             Jacket Card     IOS XR RUN      PWR,NSHUT,MON
0/0/0           MSC(SPA)        10X1GE          OK              PWR,NSHUT,MON
0/0/1           MSC(SPA)        1x10GE          OK              PWR,NSHUT,MON
0/0/2           MSC(SPA)        10X1GE          OK              PWR,NSHUT,MON
0/0/4           MSC(SPA)        1x10GE          OK              PWR,NSHUT,MON
0/RP0/CPU0      RP(Standby)     N/A             MBI-BOOTING     PWR,NSHUT,MON
0/RP1/CPU0      RP(Active)      N/A             IOS XR RUN      PWR,NSHUT,MON
thanks alot

Duplicate posts.
Go here: https://supportforums.cisco.com/thread/2260981

Similar Messages

CRS-1 boot failed problem

Hi expert
after greeting ,
I have CRS1/8 with two RPs installed, suddenly RP0 failed to boot and standby RP1 is running as active RP, when i console to RP0 i got the following output :
Initializing DDR SDRAM...found 4096 MB
Initializing ECC on bank 0
Initializing ECC on bank 1
Initializing ECC on bank 2
Initializing ECC on bank 3
Turning off data cache, using DDR for first time
F
*** Exception ***
Exception vector =
Initializing DDR SDRAM...found 4096 MB
Initializing ECC on bank 0
Initializing ECC on bank 1
Initializing ECC on bank 2
Initializing ECC on bank 3
Turning off data cache, using DDR for first time
f0
Initializing DDR SDRAM...found 4096 MB
Initializing ECC on bank 0
Initializing ECC on bank 1
Initializing ECC on bank 2
Initializing ECC on bank 3
Turning off data cache, using DDR for first time
EC
*** Exception ***
Exception vector = 0x00
CPU context of the most recent exception:
PC = 0x
Initializing DDR SDRAM...found 4096 MB
Initializing ECC on bank 0
Initializing ECC on bank 1
Initializing ECC on bank 2
Initializing ECC on bank 3
Turning off data cache, using DDR for first time
F
*** ÿÿÿÓÿÿÿÏÿÕ
Î Exception ***
Exception vector = 0x0[0000000000000
CPU context of the most recent exception:
PC = 0x
and i can't enter the rommon so I really appreciate if you help me to solve this issue

RMA is replacement of the product that is under warranty or contract. If the RSP is broken due to hardware issue, and if it is under Cisco contract or warranty, you can open the TAC case to investigate this further. If TAC conclude this is hardware issue, then you will receive replacement. I do not think this is a bug, you can open case now and i can work with you to confirm this.
thanks,
rivalino

Beige G3 boot from **** problem; open firmware issues; bad motherboard?

Dear all,
I'm having huge boot/startup problems with my beige G3 that had been happily running OSX 10.3.9, but for purposes of this discussion we can (mostly) revert to OS 9. Originally, the machine was a G3 @300; was upgraded more than a year ago to a ZIF G4 @500.
To make a long story short, it won't boot from any hard drives, will not boot from any OS X CD, and will only occasionally boot from a 9.x startup CD (whether Apple or Norton Utilities). I think it's an open firmware issue, possibly caused by a bad motherboard (rev. 2).
All this started happening after I used techtool pro, but I think that's coincidence (even though I acknowledge that, for cops and computer users, there are no coincidences.) Also, as discussed below, I'm having the same problems with an HD that wasn't even in the computer when all these things began.
Here are some of the things I've done.
--repeatedly reset PRAM, both with key combinations and removing battery. The only time it will boot from a 9.x CD is after resetting PRAM.
--removed all add-on PCI cards.
--removed additional VRAM
--removed all memory cards and tried replacing one at a time.
--disconnected both existing hard drives and replaced with an older OS 9.x hard drive (approx 60 mb) that I'd used before. Also tried different ribbon cables.
--unplugged floppy drive
--disconnected PCI ATA disk controller that I'd been using for running a large (1.8 gb) hard drive.
--regarding open firmware: readenv usually shows totally normal default AND installed settings. Using reset-all works fine -- at least it makes the machine reboot, but doesn't solve the problem. reset-nvram does NOT work -- says it's an "unknown word."
--using startup keys like holding down the option key, or shift key, or X key or cmd-option plus two others I can't remember, has no effect. Again, after I've tried any kind of reboot, the ONLY way to get the C-key at startup to boot the CD is by resetting the pram (key combination). Otherwise, the usual result of these experiments is a dark screen on startup -- nothing at all (and the LCD monitor tells me "no input.")
--regarding OSX: sometimes (and I emphasize sometimes) I can get the machine to start booting from an OSX 10.2 CD, but it won't complete the process. Sometimes I get a "prohibited" (as in no-parking, no-smoking) icon; sometimes it will start booting (grey screen, OS X Apple icon), then crash (horizontal grey and white jagged bars); sometimes it will show the OS 9 start icon (the tiny smiling Mac SE), but not boot at all.
--when I get the mac successfully booted with an OS 9.x CD (again, this works sometimes, but not always), the old hard drive with two partitions does show on the desktop and can be accessed. Using either disk repair or Norton Utilities shows the 9.2 system partition on the hard drive to be fine. But if I go to the startup disk control panel, confidently set the 9.2 partition as my startup disk, then reboot, there's no change. It won't boot and I'm back at square one.
--even when I do get successfully booted with 9.x, the machine will still occasionally crash for no reason -- ie when I'm moving a Window.
--the only thing I haven't done is slowed down the processor. It's a ZIF G4 bought more than a year ago from XLR8 your Mac. I'm running at the default 500 mhz, and it's never given me any trouble.
So I think it's a bad motherboard or ROM. Thoughts?
Thanks.

The beige Mac is now operating happily again. My original tentative diagnosis remains the same (although still tentative): corrupted PRAM from bad battery, compounded by bad cables that wrote corrupted data to hard drives, and also (possibly) allowing Tech Tool Pro (a utility that I now regard with deep suspicion) to create a "virtual" startup partition.
A few things I've learned along the way that hopefully may be useful:
--remember that the Ex Post Facto utility can be used to help OS X startup, not just installation. This applies to hard drives, emergency CDs, installation CDs, etc. If you can boot into any working hard drive partition (OS 9 or a backup OS 10), then run Ex Post Facto (same program runs on either OS 9 or X -- don't ask me how) and tell it what system you want to start up from. Also, the utility has sometimes told me that the startup extensions on the disc that I wanted to boot up from were bad, and offered to fix them (which works).
--at least on my Mac (beige, v. 2 motherboard), resetting the CUDA button, resetting the PRAM, resetting Open Firmware and "draining" the memory by unplugging the computer and disconnecting the battery for several hours ALL DO DIFFERENT THINGS.
Specifically, if I'm having trouble booting (from a hard drive or a CD), the FIRST thing I do is restart and resetting the PRAM on the fly -- holding down command, option, P and R at startup, and waiting for the chimes (preferably at least 3-4 times).
If I do that and DON'T hear the chimes, that's my cue for my SECOND action -- restarting into open firmware (command, option O and F keys on startup). That should bring up the black text on white background open firmware screen. View other posts or apple support for details, but if you do PRINTENV and see a bunch of weird gibberish after the default/installed lists, you know that it was messed up and you need to clear it through reset nvram and reset all commands. Be aware some of these commands do or do not work depending upon what version of Open Firmware you have.
After I've rebooted with Open Firmware, then on restart I should be able to reset the PRAM on the fly. If that works, then either let the machine run and see what happens, or hold down the C command and see if it will boot from the CD
Usually, if I've fixed everything as above, the machine will boot into whatever version of OS 9 it finds on a hard drive. That's fine with me -- at that point, use Ex Post Facto to reboot into your OS X. (Before I forget: I used the shareware startup CD creator program BootCD to make an emergency boot CD based on OS 10.2.8 (which theoretically will support a beige mac in native fashion) and Disk Warrior, the god of disk repair utilities. Even though the CD should boot just by holding down the C key on startup, it doesn't -- but if I use Ex Post Facto to boot it, no problems (although the process is very slow -- be patient). Then I can fix almost anything using Disk Warrior.)
If none of the above works, then I'll try resetting the CUDA (on my beige minitower, it's a very small black button inconveniently located between a PCI slot and the side of the computer housing). Hold it down for 15 seconds. That should REALLY clear the PRAM. I know this does something different from the previous steps because this is the only action (except the battery disconnect -- next) that clears the date and time from the memory.
If all else fails, I will unplug the computer and disconnect the battery, then push the CUDA button for 15 seconds and let the machine sit overnight.
One final finding -- I thought I'd fixed everything, but both my hard drives suddenly quit working, I discovered that during all this repeated connect/disconnect of things, one of the male pins inside one of the connectors on my Acard ATA PCI card had broken off. Not good. Fortunately, the card had a second connector, which works fine. And I did some extensive shaking of the computer to make sure (I hope) that the broken pin hadn't landed on a circuit board.
All this took more than two weeks, and the advice of this board was much appreciated. Now I'm on to my next adventure -- trying to figure out why a combo Firewire/USB PCI card won't mount an external drive on Firewire, but will on USB. I've tried two cards with same result -- but a Firewire-only card works just fine.)
Regards to all,
Graham

Laptop stopped booting due to EFI boot device problems [SOLVED]

Hi,
I'm writing this from my old laptop. My Lenovo U330 touch will not boot. When I turn it on it states that 'default boot device is missing or boot failed'. It used to go to gummiboot and there were Linux and Windows boot options.
I can boot from an Arch USB drive and chroot but when I try to reinstall gummiboot or grub I get errors:
#gummiboot --path=$esp install
#failed to check filesystem type of install: No such file or directory
# grub-install --target=x86_64-efi --efi-directory=$esp --bootloader-id=grub --recheck --debug
#grub install error failed to get canonical path of `'
On this laptop there are various partitions for EFI and a small Windows 8 partition.
I guess there is some problem with the $esp
It should be /dev/sda2 and / is dev/sda6. All seem to be present and correct with fdisk -l, however, for some reason there is a boot flag on /
I've tried to sort it out for a few hours now. Please if anyone can help that would be amazing.
P
Last edited by pepedopolous (2014-06-22 22:38:55)

Head_on_a_Stick wrote:
pepedopolous wrote:[..] it is btrfs. [...]
Try again without using btrfs --- it is not production ready...
This is a pretty ridiculous suggestion. It may not be production ready and it may not be the best choice for the user, but it has nothing to do with the problem at hand.
@OP, are you literally typing:
gummiboot --path=$esp install
If so, $esp is a variable. So in your case you would need to set esp=/boot. But gummiboot's default --path for install is actually /boot. So you should only need to do:
gummiboot install

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.

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...

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!

Extended partition on old MBR HDD makes Windows 7 UEFI boot fail

There seems to be a bug in Windows 7 Pro x64 that prevents it from booting on a GPT partitioned HDD when the same machine also has an MBR partitioned HDD with an extended partition.
I have a UEFI bootable PC with two HDDs:
Disk 0 is GPT partitioned and contains Windows 7 Pro x64 and openSUSE systems.
Disk 1 is MBR partitioned and contains Windows XP Pro x64 systems and bootable ISO images.
Both the disks also have separate partitions for data and for booting.
They are normally booted via rEFInd on disk 0 as follows:
UEFI => rEFInd => Windows 7 or GRUB2.
UEFI => rEFInd => disk 1 MBR => GRUB4DOS.
I had previously installed Windows 7 when it was first released, but abandoned it in favour of XP and openSUSE instead. With the end of support for XP I decided to re-install W7. Before doing so I unplugged disk 1 to ensure that W7 booted completely
independently of XP. After installing W7 I installed SP1 and all the Windows updates. The new W7 system could be booted without problem via rEFInd => \EFI\Microsoft\Boot\bootmgfw.efi
However when I plugged in disk 1 W7 would no longer boot. It displayed the message "Windows is Loading Files" as the bar progressed twice before returning to the rEFInd menu. On selecting W7 again it presented the option to "Launch
Startup Repair", but on doing so it too just displayed "loading files" and returned to the reEFInd menu.
I UEFI booted from the installation DVD and ran Repair. When re-booted W7 presented a menu with choice of new and recovered systems, but both failed as before. Neither could be booted in safe mode. Booting directly from the UEFI firmware menu
into W7, instead of via rEFInd, gave similar results.
Investigations showed that the problem is caused by the extended partition on disk 1. If it is deleted, or just hidden by changing the partition type from 0x0F to 0x00, then W7 boots OK. Plugging in an external USB HDD with logical partitions also
prevents W7 from booting.
This all seemed to be similar to the problem described in KB979374, so I downloaded the hotfix (404153_intl_x64_zip.exe), which is supposed to be applicable to Windows 7 as well as WindowsServer 2008 R2. However when the hotfix was run it displayed "The
update is not applicable to your computer" and logged the following error:
error 2149842967 "" (Command line: ""C:\Windows\system32\wusa.exe" "<pathname>\Windows6.1-KB979374-x64.msu" ")
Is this because the version of files mentioned in KB979374 is older (6.1.7600.20617) than the version of Winload.exe in my system (6.1.7601.17556)?
According to http://www.techienewsnetwork.com/247/22/ SP1 included hotfix 979374, but it doesn't appear in the list of Installed Updates given in my W7 control panel. Should it, are hotfixes included in a service pack listed individually? If
not is there any way to tell whether or not hotfix 979374 has been applied?
How can W7 be booted without having to change the partition type code of extended partitions every time, is there a newer hotfix that will fix the problem in Windows 7 SP1?
Almost all the references I can find to this problem are at least 2 years old, which suggests it might have been fixed. Does anyone else with an up to date Windows 7 SP1 have this problem with extended partitions. An easy test is to plug in an external
HDD with logical partitions and see if W7 will still boot.
I don't want to convert disk 1 to GPT as that would make XP un-bootable. Also GRUB4DOS only supports MBR, and it is very useful for booting ISO images as well as XP.
Cheers.

Hi Wade,
To be sure that openSUSE, XP, or any other software on my PC isn't part of the problem I decided to do a new install of Windows 7 on a blank HDD. As I don't have a spare one I had to backup everything on disk 1 (MBR) and then wipe it, including the MBR,
with zeros (using AOMEI Partition Assistant).
I unplugged the original disk 0 so that the PC had just single completely blank HDD (previously disk 1), UEFI booted the Windows 7 DVD and installed W7 again. Unfortunately at this first attempt W7 partitioned the blank HDD as an MBR disk and booted
in legacy BIOS mode, even though I had booted the DVD in UEFI mode. So I deleted all the partitions it had just created and converted the disk to a GPT one.
The next time I installed W7 it was a UEFI one, with an EFI system partition. After installing SP1 and re-booting it a few times to make sure it was working OK I plugged in the external HDD with an extended partition before re-booting. The result
was exactly the same as reported above for the main GPT disk: it briefly flashed "Starting Windows" then displayed "Loading files" for a few seconds as the bars progressed; when Startup Repair was launched it failed as well.
After removing the HDD I booted the new W7 and added some missing drivers and installed all the Windows Updates, including the optional ones. Many hours later the result was a new up to date installation of Windows that worked perfectly (no errors in
any log files), with no other software on the PC. However as soon as the external HDD was plugged in it failed to boot, as described previously.
I then ran Bootrec from the DVD, trying all the commands, but the results were exactly the same: everything worked successfully but no Windows installations were found, and it didn't fix the problem.
The documentation on how to use Bootrec describes how to backup the BCD store that is on the C: drive (e.g. "ren c:\boot\bcd bcd.old"). However the BCD store for UEFI based systems is in the EFI system partition, NOT on the C: drive. This suggest
that Bootrec does not apply to UEFI based systems.
Are you sure that the MBR is used when booting in UEFI mode? From what I have read in several places (not MS pages) the protective MBR on the GPT isn't used, but instead the UEFI firmware runs \EFI\Microsoft\Boot\bootmgfw.efi which looks in the BCD store
in the EFI partition. Can you point me to any MS documentation please that explains exactly how UEFI booting works for Window 7, including its use of the MBR.
Do you have a Windows 7 system that can boot from UEFI when an MBR disk with an extended partition is attached. If so how is your installation different from the one I have just set up, i.e. Windows 7 installed on a PC with just
a single empty GPT HDD?
Do you work at Microsoft? If so perhaps you could find out if anybody with a straightforward UEFI booted Windows 7 has problems when an MBR HDD with an extended partition is attached.
Sorry for the delay in responding, but a lot of work was involved.

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

U530 boot failed

I have a Lenovo U530 laptop that intermittently encounters a 'boot failed' error.
This has happened 6 times in a 4 month period. Each time it has occurred I have clicked
through the following 5 screens until it requested a system restart:
1. EFI Network 0 for IPv4 (08-9E-01-F5-44-D4) boot failed. [Ok]
2. EFI Network 0 for IPv6 (08-9E-01-F5-44-D4) boot failed. [Ok]
3. Default Boot Device Missing or Boot Failed.
     Insert Recovery Media and HIT any key
     Then Select 'Boot Manager' to choose a new Boot          [Ok]
     Device or to Boot Recovery Media
4. Boot Manager
     Boot Option Menu
     EFI Network 0 for IPv4 (08-9E-01-F5-44-D4) boot failed. (this line is selected)
     EFI Network 0 for IPv6 (08-9E-01-F5-44-D4) boot failed. [Ok]
     ^ and v to change option, ENTER to select an option
5. EFI Network 0 for IPv4 (08-9E-01-F5-44-D4) boot failed. [Ok]
Screen 6: No bootable device -- Please restart system
At this point I power off, then on via the power switch and it boots normally.
I am aware of the suggestions to boot from a recovery drive but that is not my problem.
I am able to successfully boot by powering off/on.
I would like to figure out what is causing this. Any suggestions on what steps to take
to diagnose this the next time it occurs?
Lenovo phone support has been of no help.
TIA
Luke

If you are not connecting to a lan at boot up try to disable "PXE boot to Lan" in the bios. Else temporarily disable it. Once booted try running in command prompt with admin rights "sfc /scannow". Do not include the quotation mark. You might also try running chkdsk to check the hdd for defects.

Toshiba A665 Satellite boot failed and recover disc failed to boot

For some odd reason after my computer froze up and I restarted it I get stuck on the black screen and then it says the boot failed. I thought I could use the toshiba recover disc to fix the problem but it wont work either. I can get in the
bios screen but that is about it. Is there anything I can do?
Says the HDD/SDD not installed in bios

i had this problem
and my discs were not working either
but if you press f12 while the toshiba logo it will bring you to the boot manager and you can boot the disc drive. a messege will appear asking you to press any key to boot the cd and press "enter" then windows will load youre discs and start the toshiba reformat wizard! so i hope this works

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.

Boot Failed. EFI SCSI Device 1. Hyper-V Windows 2012 R2 Preview

Hello,
I am new to Hyper-V. I installed Windows Server 2012 R2 Preview on a physical server and installed Hyper-V role on it.
I am trying to install Windows 2008 R2 on Hyper-V as a guest OS.
From Hyper-V manager, I created a VM and supplied 2008 R2 ISO as a boot device.
Windows 2008 R2 ISO is bootable. I have used the same ISO on VMware and it works.
I connected the VM and powered on, but OS instalaltion doesn't start.
I get error " Boot Failed. EFI SCSI Device 1." Below is th screen capture.
How to fix this problem ?
How do I go to Hyper-v VM BIOS settings ?
How do I change the boot sequence for Hyper-V VM ?
Thanks ! Jayawardhane

I was getting the same error but with WINDOWS 2012 STD Edition.
My case: I was trying to use the existing WINDOWS 2012 VHDX with Generation 2 Virtual Machine, as I wanted to make use of 'Virtual Hard Disk Sharing' feature which is only supported on SCSI Controller. But during boot, it looked for UEFI code, whereas
I had created VHDX using BIOS boot partition. So I guess, In order to use 'VHD Sharing' feature, I have to convert boot partition to GPT which supports UEFI.
If I use the Generation 1 virtual machine, and then change the VHDX Controller from IDE to SCSI from settings, I see the option 'VHD Sharing' getting enabled, but unfortunately the Generation 1 BIOS does not have support for SCSI only IDE.

K8N Neo2 Platinum ed. XP Boot freese problem !!!

After the bios post screen, when the xp logo disappered, it's freese 2-3 minutes. XP starts normally and full functionally after the freese. I have no stability problem.
I have install XPSP2 ( SP2 embedded XP cd. Created autostremer) Install all latest drivers and bios update (1.B0)
I've use only one hdd, no raid array. I've try the bios settings optimized. Guided like this documents FAQ
Specially thanks for your interest
K8N Neo2 Platinum ed nforce3 ultra
AMD64 Athlon venice 3000+
sata1 Samsung HD080HJ SATA 80Gb
ide1 LG-DVD writter
MSI Geforce FX5200 AGP
2*256 Kingston DDR
No FDD
A4Tech keyboard and mouse PS2
CPU-Z Report CPUZ

Check eventviewer for drivers/sw thats fails to load .
Other than that most boot delay problems are related to bad IDE (master/slave) configuration or cables .

CRS-1 boot failed problem ( REDFS-5-INIT_FAILED)

Similar Messages

Maybe you are looking for