Error with boot-archive - Machine completely corrupted

Hello!
About two weeks ago I installed the current Solaris Os on two v240 to form a cluster. For the first install I used ZFS, but that was incompatible with the cluster software. So I reinstalled the OS, chose "UFS" as the filesystem and mirrored all partitions onto the second drive in each machine with the Solaris Volume Manager.
Today I wanted to patch these machines and rebooted one of them into single user mode. Instead of booting correctly, I got this message:
WARNING: The following files in / differ from the boot archive:
changed /kernel/drv/did.conf
The recommended action is to reboot to the failsafe archive to correct
the above inconsistency. To accomplish this, on a GRUB-based platform,
reboot and select the "Solaris failsafe" option from the boot menu.
On an OBP-based platform, reboot then type "boot -F failsafe". Then
follow the prompts to update the boot archive. Alternately, to continue
booting at your own risk, you may clear the service by running:
"svcadm clear system/boot-archive"
{code}
So I booted the machine into failsafe mode and used the instructions from http://docs.sun.com/app/docs/doc/817-1985/gglbw?a=view to update the boot-archive. During this procedure I was confused that my first disk was listed as c0t0d0s0 and not c1t0d0s0. Also the output of metastat did not work and the system asked me if I wanted to mount a zpool which it found during startup. But there should not be any more zpool now, all partitions are UFS.
The reboot did not work with c0t0d0s0 in the vfstab, so I rebooted once again into failsafe. From this point, the whole system is corrupted. I am unable to boot anymore. The OpenBoot prompt tells me this:
[code]
Rebooting with command: boot
Boot device: disk File and args:
ERROR: Last Trap: Fast Data Access MMU Miss
{1} ok boot
ERROR: /pci@1c,600000: Last Trap: Fast Data Access MMU Miss
{1} ok
[/code]
I am unsure how to proceed from this point. The second machine tells me exactly the same error about "/kernel/drv/did.conf", so I do not think that in both servers a hard drive failed simultaniously.

Yeah, I posted a warning about a week ago about this issue.
If you have SVM mirrored root, then
following the "recommended actions" warnings that solaris gives in this situation results in a corrupted filesytem.
I have a job open with sun about it, and they have confirmed the problem..
From where you are, I recommend you rebuild the machines from scratch..
You might be able to split the mirror and fsck your way out, but its not worth the hassle.
I posted a way to "fix" the root cause of the issue, ie prevent the inconsistent boot archive in the first place yesterday in the "out of sync boot archive" thread in this forum.
So. you can avoid the problem the next time around..
What would have worked when it reported the inconsistent boot archive is to simply ignore it and do the "svcadm clear" command it mentions instead.
Then another reboot.
Alternatively, if you do the failsafe boot, make sure you rebuild the boot archive on both halves of the mirror..

Similar Messages

HT3275 Can some HELP, I keep getting this error with my Time Machine Back up, "The backup disk image "/Volumes/JKPN Safe/JKPN IMAC.sparsebundle" is already in use.

Can some one HELP me , I keep getting this error with my Time Machine Back up, "The backup disk image “/Volumes/JKPN Safe/JKPN IMAC.sparsebundle” is already in use.

See > http://pondini.org/TM/C12.html

Error with Java Virtual Machine Laucher

Hi, I'm getting the follwowing error with I try to lauch universal installer.
Fatal exception occured. Program will exit.
Does anyone have any idea what's going on? I have java ee 5 sdk installed on my machine.

Hello Guys!
I have a problem here and i cant find the solution!
somebody can help me?
In the installation, after run the runInstaller show
this message:
Initializing Java Virtual Machine from
/tmp/OraInstall2008-04-27_0733-08PM/jre/1.4.2/bin/java
. Please wait...
[oracle@localhost ~]$ Oracle Universal Installer,
Version 10.2.0.1.0 Production
Copyright (C) 1999, 2005, Oracle. All rights
reserved.
Exception java.lang.UnsatisfieldLinkError:
/tmp/OraInstall2008-04-27_0733-08PM/jre/1.4.2/lib/i386
/libawt.so: libXp.so.6: cannot open shared object
file: No such file or directory occurred..
java.lang.UnsatisfieldLinkError:
/tmp/OraInstall2008-04-27_0733-08PM/jre/1.4.2/lib/i386
/libawt.so: libXp.so.6: cannot open shared object
file: No such file or directory<snip>
So I went to MetaLink and did a search on the "libXp.so.6: cannot open shared object" found in your error message. The very first hit returned was note 308755.1, titled "OUI Reports The Error: Exception java.lang.UnsatisfiedLinkError: /tmp/OraInstall*/jre/1.4.2/lib/i386/libawt.so: libXp.So.6: Cannot Open Shared Object File"
The terms of MetaLink usage prevent me from quoting from the note, but you would be advised to go read it for yourself. Suffice it to say you are missing some rpms. The specific ones missing are not listed in the above referenced not, but it will point you in the right direction.

Error with boot

Hi all,
i get an error when I start a Sun v240 server. i took this server over from someone else, but can not seem to install the OS.
I get the following error when booting :
"Boot device: disk File and args:
WARNING: unknown command 'B' on line 87 of etc/system
SunOS Release 5.10 Version Generic_118822_29 64-bit
WARNING: exec (/sbin/init) failed with error 13.
(Could not start init) Program Terminated
{0} ok
after this, the system hangs and i can not do anything.
If I insert the OS DVD, the system boot up with the same error.
Any ideas on how to reslove this?

Hello,
Can you open the system in single user mode? Insert Solaris CD/DVD and type
following from OK prompt:
ok boot cdrom -s
if you succeeded control /etc/system and other configuration files related to boot.
regards,
zulusa

Error with boot new zone

hi from Bulgaria
I've made 3 non-global zones and everything was fine but after i tried to the four one the following error occur
when i tried to boot it:
bash-2.05b# zoneadm list -vc
ID NAME STATUS PATH
0 global running /
2 zone3 running /zone/3
3 zone2 running /zone/2
4 zone1 running /zone/1
- zone4 installed /zone/4
bash-2.05b# zoneadm -z zone4 boot
zoneadm: zone 'zone4': bge0: could not add interface: No buffer space available
zoneadm: zone 'zone4': call to zoneadmd failed
Regards
Sofia, Bulgaria 8.26.2004

Hello,
Which build are you running (uname -v)?
Can you try the following command:
# ifconfig bge0 addif 1.2.3.4/24 up
and see if it produces the same error message ("No buffer space available")?
Thanks,
Blaise

Errors with Time Machine (not completing backup, and needing to erase the ".inProgress" package)

I have in a previous discussion been talking about errors with my Time Machine backup. The errors were with a problem with Indexing a file, it fails and stops the whole backup. Each time it attemps another backup, it fills my ".inProgress" package with a (nearly) whole backup, filling my Time Machine hard drive, and thus errasing my previous good backups. The error occurs after about 95% completion.
In my last post of a similar disscussion, the problem was indexing the Preference Pane files and this caused the whole backup to fail. This was my last post there: (below in some additional info of my situation)
I did exclude the MobileMe.prefPane. And I got:
12/16/11 9:24:50.468 PM com.apple.backupd: Starting standard backup
12/16/11 9:24:50.556 PM com.apple.backupd: Backing up to: /Volumes/3 TB GoFlex Drive/Backups.backupdb
12/16/11 9:25:14.418 PM com.apple.backupd: Waiting for index to be ready (101)
12/16/11 9:27:02.366 PM com.apple.backupd: Deep event scan at path:/ reason:must scan subdirs|
12/16/11 9:27:02.366 PM com.apple.backupd: Finished scan
12/16/11 9:33:37.119 PM com.apple.backupd: Deep event scan at path:/Volumes/Mac OS Lion GM reason:must scan subdirs|
12/16/11 9:33:37.119 PM com.apple.backupd: Finished scan
12/16/11 9:36:15.650 PM com.apple.backupd: 758.92 GB required (including padding), 830.32 GB available
12/16/11 10:25:14.873 PM com.apple.backupd: Copied 22.8 GB of 630.5 GB, 782749 of 2357620 items
12/16/11 11:25:15.335 PM com.apple.backupd: Copied 86.6 GB of 630.5 GB, 1167675 of 2357620 items
12/17/11 12:25:16.227 AM com.apple.backupd: Copied 152.2 GB of 630.5 GB, 1393795 of 2357620 items
Dec 17 01:25:16 Thomas-P-Kellys-iMac com.apple.backupd[99858]: Copied 305.2 GB of 630.5 GB, 1413946 of 2357620 items
Dec 17 02:25:16 Thomas-P-Kellys-iMac com.apple.backupd[99858]: Copied 457.1 GB of 630.5 GB, 1419190 of 2357620 items
Dec 17 03:19:07 Thomas-P-Kellys-iMac com.apple.backupd[99858]: Copied 1736865 files (568.3 GB) from volume Macintosh HD.
Dec 17 03:25:16 Thomas-P-Kellys-iMac com.apple.backupd[99858]: Copied 572.1 GB of 630.5 GB, 1848939 of 2357620 items
Dec 17 03:40:33 Thomas-P-Kellys-iMac com.apple.backupd[99858]: Indexing a file failed. Returned 200 for: /Volumes/Mac OS Lion GM/System/Library/PreferencePanes/Mouse.prefPane, /Volumes/3 TB GoFlex Drive/Backups.backupdb/Tom iMac/2011-12-14-171406.inProgress/7DB524DD-EFB9-42A6-8A21-0A2A312EDA6D/Mac OS Lion GM/System/Library/PreferencePanes/Mouse.prefPane
Dec 17 03:40:33 Thomas-P-Kellys-iMac com.apple.backupd[99858]: Aborting backup because indexing a file failed.
Dec 17 03:40:33 Thomas-P-Kellys-iMac com.apple.backupd[99858]: Stopping backup.
Dec 17 03:40:33 Thomas-P-Kellys-iMac com.apple.backupd[99858]: Copied 2164998 files (581.1 GB) from volume Mac OS Lion GM.
Dec 17 03:40:33 Thomas-P-Kellys-iMac com.apple.backupd[99858]: Copy stage failed with error:11
Dec 17 03:40:50 Thomas-P-Kellys-iMac com.apple.backupd[99858]: Backup failed with error: 11
This time it was the Mouse.prefPane that caused the error. I'd like to exclude the entire PreferencePanes directory.
This was my error message this time:
I just realized this was on my small Developers partition. Perhaps there is an error with the build, OR an error with the initial restore. I'd like to perhaps exclude the entire /Volumes/Mac OS Lion GM. I expect that Time Machine is working fine with my main partition and the error happens when it's almost done with the Mac OS Lion GM partition.
The problem now is that I only have 265 GB of 3 TB available on my Time Machine HDD. If attempt another backup, it'll surely erase about 410 GB of my past saved backups. I've already lost 6 months, and I only have two months left of backups. I need to erase the ".inProgress" package again. That'll take time, and it's impossible to do from this main partition, even at root access. This ".inProgress" has a total of two (nearly) full backups; it didn't cleanup the first full backup attempt while starting the second,perhaps it would have had it finished. But I fear even if I exclude the whole "Mac OS Lion GM" partition, It'll create a third full backup before cleanup and erase ~400 GB of previous good backups. Then, I'll have a total of 4 (nearly) full backups! 3 TB is just enough without any past backups.
Maybe I'll just copy my documentations of my 'errasing the ".inProgress" package' last time (from the Mac OS Lion GM partition) and do a full restore of just that partition. Thus erasing the errors all together. If it doesn't fix the errors then this could be a bug in the build that doesn't allow Time Machine to work. I've always included this partition in Time Machine before, even with other Lion builds, so I suspect that it was an error in the initial restore. (I may be answering my own questions, and that the inital restore (of the small partition) is the problem, and I just need to re-restore the small partition)
Again, I'm going to have to erase the ".inProgress" file to regain 1.53 TB of space before proceeding.
Also, I gave myself permission to read the ".Backup.345781513.887697.log", the log that was created last night when I first started Time Machine this last time. It was interesting, but didn't show the error I could see from the console.
Right now, mds and mdworker appear to be going crazy even after I just now turned off Time Machine. I think I'll let it go for the rest of the night. Then I'll work on erasing the ".inProgress" package from the other partition boot up.
That was my entire last post. To add some information, I have two OS X partitons, both Mac OS X Lion. One is my large main partition, the other is one I don't mind testing with. I recently replaced my internal hard drive in my iMac and restored from Time Machine both partitions. This appeared to go smoothly. But I have yet to create a single successful Time Machine backup since. At first it was doing a Full Backup, which I didn't like, but now it just aborts around 95% completion. Each, time, it tries it fills the Time Machine hard drive with duplicate (nearly) full backups errasing my older good backups. I would like to erase the ".inProgress" file to save space.
My main question in this new discussion is does anyone know of a good way of erasing the ".inProgress" file? This is so I can preseerve my previous backups. ACLs and other permissions seem to make it impossible to erase from this startup partition, the one I'm running Time Machine from. Even at root level, if I give myself permission to change permissions or delete a file, it'll say Operation not Permitted instead of Permission Denied. I have been able to delete this ".inProgress" package before when booting from the other partition, but with great difficulty. I have had much help from another Member in this Support Community when it comes to solving my Time Machine problems. I think I have found the problem (indexing files in my small OS X partition), as stated in my copy& pasted post above, but I really need to delete this inProgress package first to save space before continuing!

Pondini wrote:
Gator TPK wrote:
Now I'll have to fix the small partition? How's the best way to do this? There could be thousands of files that won't index fine.
See if there's anything you haven't done, that applies, in the pink box of #C3 in Time Machine - Troubleshooting
Otherwise, since most (or all?) of the indexing errors are in OSX, you might want to just reinstall it. Something may have gone wrong sometime, that damaged those files.
I reviewed #C3 in Time Machine - Troubleshooting and I have already done most of those things. I have just learned something new though:
When I included my Main OS X partition again, I got an indexing error for the first time for that partition. I might be interesting to note that the _spotlight process was running, and it's running again (the magnifying glass has a dot and it generically says "Indexing Tom's iMac"). mdworker, mds and backupd processes really are working hard, one moment they used over 500% of my CPU. It's nice to know for once quad core is good for something other than video encoding. (Now if they could just get the Finder to do more than 100.1%, only 1 thread is doing 100%, I'd like to see file size calculations 8 times quicker!)
I never got an indexing error once in the past 2 weeks for that large Mac OS X v10.7.2 main volume, and it had appeared to finish that partition backup before running into problems with my smaller test partition. Also, I had just updated the smaller test partition with a later build of Mac OS X. But It appears that the beta builds are clearly not the problem. I thought I could just restore again (from the December 4th backup) the small partition and both would be fine.
I'll finish reviewing all the suggestions on Time Machine - Troubleshooting and go from there. Hopefully, the _spotlight indexing simutaniously was the only problem. It's strange that the indexing hasn't happened since the original restore last week untill I finally got a good clean complete partial Time Machine backup. Why would the first Time Machine backup trigger indexing again?
For now, I'm going to exclude the Main Partition again, and let another good backup run. And try your suggestions. (And wait till mds, mdworker, etc. to finish!)
I have the logs of the first two sucsessful backups and the last two failed backups from the last 3 hours, if that would help.?

My Time Machine says there is no backup disk available. I've never had any problems with my time machine. I'm not technologically savvy, so if anyone can help, I'd appreciate it!

My Time Machine says there is no backup disk available. I've never had any problems with my time machine completing backups. I was away from house with my laptop for about 9 days so I'm wondering if there is something I need to do now that I'm home to get it working again. I'm not technologically savvy, so if anyone can help, I'd appreciate it!
Thanks,
Jana

You can lose your ability to backup through TM for any number of reasons, but the most common is what happens after a update. If your drive still works, your best approach is to read this:
http://www.chriscolotti.us/technology/how-to-fix-osx-mountain-lion-time-machine/
The attached link contains helpful graphics, so don't worry if you're not tech savvy.

Corrupt boot-archive? Don't panic :-)

One of my Solaris 10 (update 05) servers runs on a piece of HP hardware, which seems to have some sort of memory error which every now and then causes the box to panic.
After a panic today, the system wouldn't boot, instead it complained about the boot-archive being corrupt, and its gzip-checksum being incorrect.
To solve it i booted into the failsafe mode, which worked, from there i mounted the /a partition and tried to run:
bootadm update-archive -R /a
which returned without any errors within a second. However it didn't actually update the boot archive.
My guess is that the boot-archive (which seemed of a reasonable size) was so corrupted that the bootadm update-archive couldn't read it, and apparently, if it cant be read, it wont return any error nor fix it.
I also tried to move the old boot_archive to a new location and re-run bootadm update-archive, but that didn't work either since the archive didn't exist.
The solution in the end was to rename the boot-archive:
mv /a/platform/i86pc/boot_archive /a/platform/i86pc/corrupt_b_archive
and then reboot the machine into failsafe-mode again, upon booting into failsafe mode a second time, it discovered that the disk didn't have a boot-archive, and created one for me.
After this i just had to reboot and now the system booted normally.
Hope this helps someone someday.. :-)
.7/M.

Thanks for the info. One question: I've tried to boot to failsafe several times on two different machines running Solaris 10 u8 x86 on HP hardware, but it never works. I have /var as a separate data set - does your system? I seem to remember a bug mentioned where this is a problem with /var as a separate dataset?

Boot archive corrupt on both mirrors after live upgrade to Sparc U8

I upgrade from U5 to U8 for an oracle 11g upgrade requirement. I used LU to break my SVM mirror and upgrade one mirror. After the upgrade the U8 mirror was patched, and finally I activated the new BE and shutdown -i6. I was presented with the "file loaded is not bootable" error, so I attempted to boot from my orginal BE. Unfortunately this disk was also not bootable as well. I eventually got the system booted over the network where I used bootadm to re-create the boot archive. The problem I am struggling with is how both of my boot archives could have become corrupt, as my CIO is not allowing our upgrade to move forward until I provide RCA, even though the server is already upgraded and the DB upgrade is completely unrelated. I have a case open with Oracle for this, but they are not making any headway, so I thought I would post and see if anyone has any idea how the boot archives could have both been affected by the live upgrade. The corrupt boot archives are close in size and update time, however they are not exact, so it would seem that I encountered two issues possibly.
Here is the corrupt boot archive of the PBE, which I saved in case it could possibly help with RCA:
# mount /dev/dsk/c0t0d0s0 /mnt
root@wwpxpsdb01 # ls -l /mnt/platform/sun4u/boot_archive.shawn
-rw-r--r-- 1 root root 1161216 Oct 16 17:28 /mnt/platform/sun4u/boot_archive.shawn
Here is the corrupt boot archive of the ABE that was upgraded to U8:
# ls -l /platform/sun4u/boot_archive.shawn
-rw-r--r-- 1 root root 1169408 Oct 16 17:33 /platform/sun4u/boot_archive.shawn
I've found on google that other have had this issue before, but seems that was due to ZFS root disks, I am using UFS. Any help or sugestions are greatly appreciated.

If you have an Oracle contract, have you tried the Oracle communities? There is an active Solaris OS booting community, and an upgrade community. Look here:
https://communities.oracle.com
and search on "Oracle Solaris" and you should see the following (among others)
Oracle Solaris File Systems . ..
Oracle Solaris Installation, Booting and patching
Oracle Solaris System Administration
whatever the method, hope you get your answer soon!

Invalid Partition Error with each boot after BIOS update???

Need help from the experts:
I have all of a sudden had problems with every boot, receiving an "invalid partition" error every timeI start my machine. ONly significant thing I have done lately is flash bios to v 1.1 on the K8N Neo2 Plat board using MSI tool. I had no such problems prior to flashing to 1.1, though I have had other problems related to memory voltage...
What, if anything, does BIOS have to do with it? my drives are both 160GB, formatted NTFS each a single large partition...is the system thinking that's an invalid partition size?
At any rate, I have already tried a complete low level format of my drives and re-install of Win XP Pro from scratch to make sure nothing was corrupted, and sure enough, upon next boot (needed to complete some driver installs) I get the same error. Of note, I also get an error re: one of my 2 DVD drives...related?
So, for now, the only way around this is to boot using XP CD, execute 'R' for recovery, then use DOS command 'FIXMBR' to write a new boot record, and then I am able to get back in...until the next re-boot.
Have had numerous issues with this board / bios, though this is the most profound one.
Need help...this is confounding me. What should I be looking into, trying next?
system:
AMD 64 3500+, stock cooling
Zalman 400B psu
MSI K8N Neo2 PLatinum mobo
2 GB Corsair XMS C2PT ram (4 x 512)
2 x 160 GB Samsung HDD
Asus E616P1 16x DVD rom
Plextor 712A DVD RW / CDRW
MSI 9800PRO 128
Audigy 2 ZS

How did you'll updates your bios?? using liveupdates or what?? what version are you trying to updates? the old to the new version of bios..btw keith can you lists down ur spec's like seacoast guy including the psu (watts and rails) in full details. Gd luck

After reformatting my 1 Tb WD ext drive and tinkering with the "exclude these items" list, I now get the following error message from Time Machine:Are you sure you want to back up to the same device your original data is on? the WD disk has mounted??

After reformatting my 1 Tb WD ext drive and tinkering with the "exclude these items" list, I now get the following error message from Time Machine: "Are you sure you want to back up to the same device your original data is on?" I've reformatted in Disk Utilities...not sure what I did wrong. Any help would be appreciated.

Not sure what you mean by "booted" from it.
If the Mac OS is installed on the external drive, then it's possible to start up from it, just as you do from your internal drive. Please open the Startup Disk preference pane in System Preferences, and verify that your internal drive is selected as the startup disk.
Assuming that's the case, then it may be that your TM settings have been corrupted. Turn off TM, then move or delete the file /Library/Preferences/com.apple.TimeMachine.plist. Turn TM back on, recreate your settings, and try again.

Error with dual boot Win 8/OL6 R3

Hello,
I am hoping to discuss this with someone who has experience with this configuration. My goal is to get Oracle Linux dual booting on my windows 8 machine.
I have installed OL but I am having trouble getting it to dual boot win8/OL using the windows boot menu. Whereas windows 8 boots as expected, the Oracle Linux option gives me the error:
"+Windows failed to start. A recent hardware or software change might be the cause...contact you system administrator or computer manufacturer for assistance+
+File:+ \NST\nst_linux.mbr
+Status: 0xc000007b+
+Info: The selected application or operating system couldn't be loaded because a required file is missing or contains errors.+"
Here are some details of the scenario:
- Documentation followed: Red_Hat_Enterprise_Linux-6-Installation_Guide-en-US.pdf
- Hardware: Dell Precision M4700 64 bit UEFI
- OEM installed/Default OS: Windows 8 Pro 64 bit
- Installation source: OracleLinux-R6-U3-Server-x86_64-dvd.iso (written to DVD)
These are the broad steps I followed:
In windows 8
I:
- downloaded the Linux ISO software. The checksum on the download matched
- wrote the ISO to a bootable installation disk
- created a new 344gb partition for Linux using the DOS DISKPART command - partition 7
Linux Install
- I booted using the Linux installation DVD and started the installation
- When Installing Linux partition 7 became a 500mb system partition and partition 8 became the 343 gb Linux partition
- I manually created the boot partition as ext3 (because the pdf I was following said "+If your 64-bit x86 system uses UEFI instead of BIOS, you will need to manually create a /boot partition. This partition must have an ext3 file system. If you choose to partition automatically, your system will not boot.+"
- I installed the boot loader on sda7. I selected “First sector of boot partition - /dev/sda7”. I assume this installs separate GRUB boot loader on the Linux partition (7) – which will then be 'chain loaded' from the windows boot menu. Put another way, it will boot with the windows boot manager, which will give me an option to chain load the Grub boot loader, which will then run Linux...
- I chose the desktop installation
- The installation reported that it completed successfully
I successfully booted back into windows:
- I used easybcd to edit the microsoft bcd and successfully created a boot menu for Oracle Linux. I used the legacy grub because the Linux documentation says "+Note that the version of GRUB in Red Hat Enterprise Linux 6 is an old and stable version now known as "GRUB Legacy" since upstream development moved to GRUB 2.3 Red Hat remains committed to maintaining the version of GRUB that we ship with Red Hat Enterprise Linux 6, just as we do with all packages that we ship.+".
- After installing Linux and updating the BCD, the BCD now looks like this:
Windows Boot Manager
identifier {bootmgr}
path \EFI\Microsoft\Boot\bootmgfw.efi
description Windows Boot Manager
locale en-US
inherit {globalsettings}
integrityservices Enable
default {current}
resumeobject {2b56acdd-8bbe-11e2-9ba6-b8ca3ad88679}
displayorder {current}
{524cc0d3-8bce-11e2-935f-b8ca3ad88679}
toolsdisplayorder {memdiag}
timeout 30
Windows Boot Loader
identifier {current}
device partition=C:
path \Windows\system32\winload.efi
description Windows 8
locale en-US
inherit {bootloadersettings}
recoverysequence {524cc0d1-8bce-11e2-935f-b8ca3ad88679}
integrityservices Enable
recoveryenabled Yes
isolatedcontext Yes
allowedinmemorysettings 0x15000075
osdevice partition=C:
systemroot \Windows
resumeobject {2b56acdd-8bbe-11e2-9ba6-b8ca3ad88679}
nx OptIn
bootmenupolicy Standard
Real-mode Boot Sector
identifier {524cc0d3-8bce-11e2-935f-b8ca3ad88679}
device partition=C:
path \NST\nst_linux.mbr
description OracleLinux
I'm not sure the BCD entry is correct. I assume that this entry should be pointing to the nst_linux.mbr on the Linux boot partition. However I have verified that this file exists in windows 8:
C:\NST\nst_linux.mbr
I haven't been able to exactly confirm how the boot process should work i.e. whether this file should actually be in the Linux boot partition (as opposed to the windows c drive) and whether the BCD should also point to the Linux boot partition when referring to this partition.
As I mentioned above, I now have the windows boot menu with Windows 8 (which boots successfully) and Oracle Linux (which gives me the error see below for complete wording**). Is the Real-mode Boot sector wrong? Should it point to the Linux boot partition? Is it a problem with my UEFI disk? I don't think it should be because this version of Oracle Linux supports UEFI and my hardware is UEFI.
Has anyone carried out a similar win8/OL dual boot?
2001
** Complete wording of the Linux boot option in the windows boot manager:
Windows failed to start. A recent hardware or software change might be the cause. To fix the problem:
1. Insert your Windows installation disk and restart the computer.
2. Choose your language settings, and then click "next".
3. Click "Repair your computer".
If you do not have this disk, contact you system administrator or computer manufacturer for assistance
File: \NST\nst_linux.mbr
Status: 0xc000007b
Info: The selected application or operating system couldn’t be loaded because a required file is missing or contains errors.
Edited by: 2001 on Apr 1, 2013 4:27 PM
Edited by: 2001 on Apr 17, 2013 5:17 PM

Hi,
Here are my responses:
*[asmirnov]* Could you please confirm, I just want to see if I got it right the first time -
*[2001]* I'm happy to share my progress
Q1)
*[asmirnov]* You did create a partition (where you would install Linux) from Win8, correct?
*[2001]* Yes. I used diskmgmt.msc to create a separate partition. I didn't format the partition because the Linux install doesn't want that, it creates and formats the partitions in the unallocated partition
Q2)
*[asmirnov]* You use GRUB (not GRUB2)?
*[2001]* I'm not sure where you were asking about, so I hope my answer here covers all possibilities you may have meant.
I was using the windows 8 boot. I wanted to chain load to the boot loader in the Linux Partition. It is interesting what the Linux install did with my partition, it created 2 partitions in the unformatted partition. 1 was a bootable partition and the other was the Linux partition. The details were:
2 sda’s (a boot / ext4 and a VolGroup (vg_linuxlocalhost)/ physical volume (LVM) ). In the VolGroup it created 3 lv’s, lv_root, lv_home and lv_swap. I understand that this is all normal.
I followed the documentation note which said "To configure the Red Hat Enterprise Linux boot loader to chain load from a different boot loader, you must specify the boot drive manually. If you chose any of the automatic partitioning options, you must now select the Review and modify partitioning layout option before you click Next or you cannot specify the correct boot drive"
So there was also the note in the documentation that said "Note that the version of GRUB in Red Hat Enterprise Linux 6 is an old and stable version now known as "GRUB Legacy" since upstream development moved to GRUB 2.3 Red Hat remains committed to maintaining the version of GRUB that we ship with Red Hat Enterprise Linux 6, just as we do with all packages that we ship." I didn't install any bootloaders manually (either the windows 8 OOTB default that came with my machine or the Linux one), I just took the defaults. I'm wasn't sure how to access the Linux partitions once it is installed, so I can't confirm it was the legacy GRUB in the Linux boot partition, but I believe this note is saying that it OL6 does use the legacy grub. I believe GRUB Legacy is version .97.
Q3)
*[asmirnov]* Which version of Linux exactly did you use, was that Oracle Linux or you used one from RedHat directly? What is the kernal version?
*[2001]* I used "OracleLinux-R6-U3-Server-x86_64-dvd.iso.sha1sum" from the mirror site http://mirror.aarnet.edu.au/pub/oraclelinux/OL6/U3/x86_64/. According to the release notes at: https://oss.oracle.com/ol6/docs/RELEASE-NOTES-U3-en.html the kernel is
- Unbreakable Enterprise Kernel Release 2 [kernel-uek-2.6.39-200.24.1.el6uek]. Installed and booted by default
- Red Hat compatible Kernel [kernel-2.6.32-279.el6]. Installed by default
Note: By default, both the Unbreakable Enterprise Kernel and the Red Hat Compatible Kernel for the specific architecture (i386 or x86_64) are installed, and the system boots the Unbreakable Enterprise Kernel by default. If needed, /etc/grub.conf and /etc/sysconfig/kernel can be modified to make the system boot with the Red Hat Compatible Kernel by default.
Regarding your follow-up point that "Microsoft blocks 3rd party chainloaders from the BCD menu for UEFI machines. We are researching workarounds, none have presented themselves as of yet.", I'm not sure it actually blocks it, but it certainly isn't a straight forward process.
I have actually abandoned my attempt to get the dual boot working. It is a real shame because I wanted to do it for my own satisfaction.
I am now using Oracle Virtual Box as suggested by others, include Dude earlier in this thread. This has given me confidence that I was doing all the right things because the install worked first time without any problems. The virtualization is much simpler and I have had no problems so far.
Fusion
As for your point about the fusion middleware and OL5. I am looking at Oracle SOA with is part of the Fusion brand. I think that the latest SOA components will work on OL6 - but I have yet to try it. Following the certification matrix can be a little difficult. So as I indicated above, my current thoughts are to use the Oracle Virtual Box with Linux r6 u3 and to install the SOA components on that when I get chance. The alternative is using the pre-built virtual machine it has Linux and SOA (it might cover your stack too, or there may be another one that suits you better on the site) http://www.oracle.com/technetwork/middleware/soasuite/learnmore/vmsoa-172279.html. Note that this is still on OL5.
I hope this helps.

Cant open boot archive after copying Solaris 10 from one machine to another

We are running "Solaris 10 3/05 s10_74L2a" on a Sun Fire 480R.
I tried to, using ufsdump to copy the filesysem to a T5220 which has 4 disks, the first 2 disks are a mirrored os of a Solaris 10 version already there.
So I restored the ufs inages to the 3rd disk, ran installboot with the bootblock from the restored image for s sun Fire 480R as there did not appear to be a bootblock for a T5220 , as its a more recent server.
ie:
installboot /mnt/usr/platform/`uname -i`/lib/fs/ufs/bootblk /dev/rdsk/c1t2d0s0
/mnt/usr/platform/SUNW,SPARC-Enterprise-T5220/lib/fs/ufs/bootblk: File not found
so I do this instead :
installboot /mnt/usr/platform/SUNW,Sun-Fire-480R/lib/fs/ufs/bootblk /dev/rdsk/c1t2d0s0
Now then I try to boot I get :
Boot device: /pci@0/pci@0/pci@2/scsi@0/disk@2 File and args:
ufs-file-system
Loading: /platform/sun4v/boot_archive
Loading: /platform/sun4v/boot_archive
Can't open boot_archive
Evaluating:
The file just loaded does not appear to be executable.
but, as far as I know this old version of Solaris did not use a boot archive and there is no directory /platform/sun4v/boot_archive in the restored files, nor on the original server.
So, my question is, if the old version of os did not support a boot-archive, why is this restored image, when I boot , giving this error.
Surely all the data on the 3rd disk should be the same as on the old server.!!
What am I missing here ??
George

Well, you can't just copy an OS from one type of system to another and expect it to work. For one thing the OS communicates with its hardware through the /dev/ and /devices layer, and that layer will be completely different when you transfer it to another system.
Second of all the lack of boot block for the T5220 in your installation indicates that your version of Solaris 10 does not support the T5220 platform, which probably means that it will be impossible to boot completely on it anyway..
I'm not sure when the SPARC systems started to use the boot-archive..
Anyway, the two things you have missed is to create the boot-archive (with bootadm update-archive -R /mnt), and to run devfsadm on the new platform (devfsadm -r /mnt ).
Even so, there is no guarantee that your version of Solaris actually supports your hardware.. But i guess that's documented in the Sun System Hardware Handbook..
.7/M.

HT201364 I have a 2013 iMac, with OS X version 10.8.5. Have been trying to download OS X Mavericks without success; error message "we could not complete your purchase, the product distribution file could not be verified, etc". Please help; TQ

I have a 2013 iMac, with OS X version 10.8.5. Have been trying to download OS X version 10.9 (OS X Mavericks) without success; error message "we could not complete your purchase, the product distribution file could not be verified, etc". Please help; TQ

Please read this whole message before doing anything.
This procedure is a diagnostic test. It’s unlikely to solve your problem. Don’t be disappointed when you find that nothing has changed after you complete it.
The purpose of the test is to determine whether the problem is caused by third-party software that loads automatically at startup or login, by a peripheral device, by a font conflict, or by corruption of the file system or of certain system caches.
Disconnect all wired peripherals except those needed for the test, and remove all aftermarket expansion cards, if applicable. Start up in safe mode and log in to the account with the problem. You must hold down the shift key twice: once when you boot, and again when you log in.
Note: If FileVault is enabled, or if a firmware password is set, or if the boot volume is a software RAID, you can’t do this. Ask for further instructions.
Safe mode is much slower to boot and run than normal, with limited graphics performance, and some things won’t work at all, including sound output and Wi-Fi on certain models. The next normal boot may also be somewhat slow.
The login screen appears even if you usually login automatically. You must know your login password in order to log in. If you’ve forgotten the password, you will need to reset it before you begin.
Test while in safe mode. Same problem?
After testing, reboot as usual (not in safe mode) and verify that you still have the problem. Post the results of the test.

I have a MAC Pro from 2011 currently running MAC OS 10.9.5. This weekend I cloned the MAC HD drive to a new SSD drive for improved performance. The clone was completed successfully with no errors. After the clone completed I successfull restarted my sy

I have a MAC Pro from 2011 currently running MAC OS 10.9.5. This weekend I cloned the MAC HD drive to a new SSD drive for improved performance. The clone was completed successfully with no errors. After the clone completed I successfully restarted my system using the SSD as the boot device. I then successfully tested all of my products, including Photoshop CS6 and all of its plug-ins. I successfully tested the key features that I frequently use. Today while attempting to launch Photoshop CS6 a message is being displayed indicating that a scratch disk cannot be found. All drives are available on the system via the Finder and Disk Utility. I can access all drives including the old MAC HD which is no longer the boot device. I've even attempted to launch Photoshop from the old device yet the same error persist. Is there a way to review/edit/change Photoshop preferences if Photoshop doesn't launch? I've even restarted my system several times to see if that would resolve the issues. Does anyone have any recommendations for this issue? Have you previously address this issue?
Thank you Gregg Williams

Boilerplate text:
Reset Preferences
http://forums.adobe.com/thread/375776
1) Close the program and press Ctrl+Alt+Shift/Cmd+Option+Shift during startup (not reversible)
or
2) Move the Folder. See:
http://www.bugge.com/Family-and-friends/Illy/illy.html
--OB

Error with boot-archive - Machine completely corrupted

Similar Messages

Maybe you are looking for