Updating platform sun4u bootarchive
false reset-all and then try to boot off the local disk with -F failsafe option (I would try from both disks), if it doesn't work - boot off cdrom or net (if you have JS server) if you still have MMU Miss - log the call to Sun Cheers, Nikolai Boot archive corruption Solaris 10 u7: I had booted off DVD, mounted my root drive as /a, and wanted to update my boot_archive: bash-3.00# /a/sbin/bootadm update-archive -R /a Creating boot_archive for /a Could not seek to offset -1 in /tmp/create_ramdisk.164.tmp/32: Invalid argument updating /a/platform/sun4v/boot_archive mount: I/O error mount: Cannot mount /dev/lofi/1 umount: warning: /tmp/create_ramdisk.164.tmp/rd.mount.32 not in mnttab umount: /tmp/create_ramdisk.164.tmp/rd.mount.32 not mounted write: No such device or address 1 0 records in 1 0 records out update of /a/platform/sun4v/boot_archive faile... The error message shown during boot is as follows: ******************************************************************** Enter filename [kernel/sparcv9/unix]: Enter default directory for modules [/platform/SUNW, Sun-ULTRA_5-10/kernel /platform /sun4u/kernel ] /kerbel /usr/kernel] boot: cannot find misc/sparcv9/krtld boot: error loading interpreter [misc/sparcv9/krtld] Elf64 read error.Solaris Boot Error I am having a problem when booting my Sun V445 machine with Solaris 10 installed on it. boot failed Enter filename [/platform/sun4u/kernel/sparcv9/unix]: Alloc of 0x400000 bytes at 0x100000 refused. boot failed Enter filename [/platf...error booting solaris 10Hello experts, I have installed solaris 10 on x86. Any guidance advice will be highly appreciated Thanks, Dave On Tue, , [email protected]: nicely before what did I do wrong?
Example to update the boot archive via failsafe boot on sparc systems with conf igured SVM root mirror. To manually recover the boot archive on a root mirror,mount the first side (the one that the system boots from) and run: bootadm update-archive -R Multiple OS instances were found. Maybe the displayed the boot devices are NOT the boot devices from the used root mirror.
1.) Start failsafe boot: o boot -F failsafe Boot device: /[email protected],700000/[email protected]/dis @0,0:a File and args: -F failsafe Sun OS Release 5.10 Version Generic_137137-09 64-bit Copyright 1983-2008 Sun Microsystems, Inc. To chec and mount one of them read-write under /a, select it from the following list. 1 /dev/ds /c0t256000C0FFC048BDd0s0 2 /dev/ds /c1t216000C0FF8048BDd0s0 Please select a device to be mounted (q for none) [? The output of the failsafe boot can be confusing at this state. (use format if not now the root driv e) AVAILABLE DISK SELECTIONS: ... c1t216000C0FF8048BDd20 /[email protected],700000/SUNW,[email protected],1/[email protected],0/[email protected],14 Run format to find root dis # format Searching for dis s..if not already nown... c3t3d0 /[email protected],700000/[email protected]/[email protected],0 Specify dis (enter its number): ^D Mount one of the root drive read-only...
To manually recover the boot archive on a root mirror,mount the first side (the one that the system boots from) and run: bootadm update-archive -R /dev/ds /c3t2d0s0 is under md control, s ipping.
SUNW,qfe0: 100 Mbps full duplex lin up - internal transceiver SUNW,qfe1: 100 Mbps full duplex lin up - internal transceiver /dev/ds /c3t0d0s0 is under md control, s ipping.
For the first install I used ZFS, but that was incompatible with the cluster software.