Updating platform sun4v bootarchive Pre web cam

bash-2.03# cat hostname.le0 #hostname.le0 Dupre1 bash-2.03# cat hostname.le1 #hostname.le1 Dupre2 bash-2.03#cat hosts localhost loghost Dupre Dupre1 Dupre2 bash-2.03# cat netmasks mtu 8232 index 1 inet... I followed this procedure: # metastat d2: Mirror Submirror 0: d20 State: Okay Submirror 1: d21 State: Okay Pass: 1 Read option: roundrobin (default) Write option: parallel (default) Size: 8401995 blocks (4.0 GB) d20: Submirror...: a warning to the curious: Solaris x86 miniroot, boot archives and mirrored /This is a slightly apocryphal story because I haven't read the relevant scripts in close enough detail and don't care to repeat the experience.Solaris 10 booting issues -- Error 22: No such partition Solaris 10 5/08 on Ultra 40 M2 It boots fine off primary disk but having issues booting off mirror disk. Mirror disk' root (hd1,0,a) Error 22: No such partition Press any key to continue... This applies to x86 machines using GRUB to boot, up to and including Solaris 10 11/06 with current (or nearly current) patches, which have root filesystems mirrored using SVM.Regards Stephan Stephan The error message you get on attempting to boot strongly suggests a hardware problem. I hope you have a backup of your disk from before you started tinkering!You may need that after you get your MMU problem straightened out.Corruption is corruption is corruption is corruption It was obvious before Bush went for Iraq that he was doing something illegal. Solaris 2.6 boot errors Hi, I often see this message while booting Solaris2.6 running on a ultra 440 Mhz CPU. Exit the shell when done to continue the boot process.Type Ctrl-d to proceed with normal startup, (or give root password for system maintenance): The system was shutdown properly using init 5.Alternately, to continue | booting at your own risk, you may clear the service by running: | "svcadm clear system/boot-archive" So I booted the machine into failsafe mode and used the instructions from 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.

Then | follow the prompts to update the boot archive.I have installed on a Sun Fire T1000 using the DHCP network option.When I now try and boot it I get an error of boot device not found when I try different combinations such as: boot-file=disk boot-device=/[email protected]/[email protected]/[email protected]/[email protected]/[email protected],0 I cannot figure out what to put in to get it to boot.The installation wen well except at the end it reported a warning.Installing boot information - Installing boot blocks (c0t1d0s0) - Installing boot blocks (/dev/rdsk/c0t1d0s0) - Updating system firmware for automatic rebooting WARNING: Could not update system firmware for automatic rebooting Suffice to say, I am at the "ok" prompt and cannot seem to figure out how to boot the server. ok show-disks a) /[email protected]/[email protected]/[email protected]/[email protected]/disk b) /[email protected]/[email protected]/[email protected]/[email protected]/disk q) NO SELECTION Enter Selection, q to quit: a /[email protected]/[email protected]/[email protected]/[email protected]/disk has been selected.

Search for updating platform sun4v bootarchive:

updating platform sun4v bootarchive-22updating platform sun4v bootarchive-15updating platform sun4v bootarchive-75updating platform sun4v bootarchive-11

Instead of booting correctly, I got this message: | WARNING: The following files in / differ from the boot archive: | | changed /kernel/drv/| | The recommended action is to reboot to the failsafe archive to correct | the above inconsistency.

Leave a Reply

Your email address will not be published. Required fields are marked *

One thought on “updating platform sun4v bootarchive”