Updating platform sun4v bootarchive
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.bash-2.03# cat hostname.le0 #hostname.le0 Dupre1 bash-2.03# cat hostname.le1 #hostname.le1 Dupre2 bash-2.03#cat hosts 127.0.0.1 localhost loghost Dupre 10.0.0.1 Dupre1 10.0.0.2 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.
During boot I see: configuring IPv4 interfaces:ifconfig: #hostname.le0: bad address le0ifconfig: #hostname.le1: bad address le1.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.Type ^Y ( Control-Y ) to insert it in the command line. ok nvalias mydev ^Y for creating devalias mydev for /[email protected]/[email protected]/[email protected]/[email protected]/disk ok probe-scsi MPT Version 1.05, Firmware Version 1. Target 1 Unit 0 Disk ATA HITACHI HDS7216SAB8A 312581808 Blocks, 160 GB SATA device Phy Num 1 If I boot the system single user mode over the network (boot net1:dhcp -s) I can mount the disks: /dev/dsk/c0t1d0s0 6.8G 4.7G 2.0G 70% /tmp/dd /dev/dsk/c0t1d0s7 139G 64M 138G 1% /tmp/d1 and # ls /tmp/dd bin etc lib platform system boot export lost found proc tmp dev home mnt reconfigure usr devices kernel opt sbin var # ls /tmp/dd/boot/solaris bin filelist.ramdisk filestat.ramdisk Edited by: robert...on Sep 14, 2010 PM And also, the install log shows a link error reporting sun4us.