Updating platform sun4u bootarchive

Rated 3.96/5 based on 500 customer reviews

Therefore, it's difficult to use the Mila X Live CD in these environments.

export exclusion lists, including, but not Sun Microsystems, Inc.

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.

| On an OBP-based platform, reboot then type "boot -F failsafe".

Then | follow the prompts to update the boot archive.

Not dumped tar: ./dev/.devname_lookup_door is not a file.

The syntax for the ufsinstall script is: umount: warning: /lib/1 not in mnttab umount: /lib/1 not mounted Warning: 1524 sector(s) in last cylinder unallocated /dev/rdsk/c2t3d0s4: 4194828 sectors in 683 cylinders of 48 tracks, 128 sectors 2048.3MB in 43 cyl groups (16 c/g, 48.00MB/g, 7744 i/g) fsck -F ufs -o b=#) at: 32, 98464, 196896, 295328, 393760, 492192, 590624, 689056, 787488, 885920, 3248288, 3346720, 3445152, 3543584, 3642016, 3740448, 3838880, 3937312, 4035744, 4134176 Starting to copy data from UFS root to /ufsroot - may take some time. 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.Hardware watchdog enabled Remounting root read/write Probing use Hostname: milax Done mounting live image from memory Configuring devices.The authenticity of host '192.168.1.180 (192.168.1.180)' can't be established.

Leave a Reply