Updating platform sun4u bootarchive
Not dumped tar: ./dev/.devname_lookup_door is not a file.
Unfortunately a lot of SPARC machines reside in data centers and there is no easy access to the CDROM drive of these machines.
Log in a as user alex (password alex) to Mila X, become root user (password root), copy the script ufsinstall (see The ufsinstall script for the UFS installation) to the /tmp directory, and make it executable with the chmod command: /tmp/maint1 updating /tmp/maint1/platform/sun4u/boot_archive 15 0 records in 15 0 records out Nov 1 v240 ufs: NOTICE: alloc: /tmp/maint1: file system full cat: write error: No space left on device syncing file systems...
milax console login: alex Password: Sun Microsystems Inc.
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.
Cheers, Nikolai Nikolai ops, sorry - I was wrong - as I see it must be Solaris10 U6 - so, the warnings to boot_archive can be met on this particular configuration after patching - due to the boot_archive file is not updated after patch has been applied.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.But there should not be any more zpool now, all partitions are UFS. The Open Boot prompt tells me this: | Rebooting with command: boot | Boot device: disk File and args: | ERROR: Last Trap: Fast Data Access MMU Miss | | ok boot | ERROR: /[email protected],600000: Last Trap: Fast Data Access MMU Miss | | ok I am unsure how to proceed from this point.The reboot did not work with c0t0d0s0 in the vfstab, so I rebooted once again into failsafe. 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.