On Wed, 11 Mar 2009 20:11:52 -0400 Paul Gress <pgress at optonline.net> wrote:
> I believe you may have trouble with package SUNWopensslr. The > paragraph's below only pertain if SUNWopensslr hasn't been installed > correctly previously. I have had difficulty with SUNWopensslr in the past, maybe with b105? > To get it to boot past 'Configuring Devices' boot into failsafe, then > go remove the "reconfigure" (located at /a/reconfigure) file. Then > look through all the directories /a/lib, /a/lib/64 & /a/lib/32, and > remove the "~11" from the ends of all files there. They are like > "libcrypto.so.0.9.8~11" renamed to "libcrypto.so.0.9.8". You should > be able to boot now. I booted into b109 failsafe and found no files in these directories with ~11 (I have seen similar files previously). I also checked the non-/a directories and there were no such files. > Now you need to install SUNWopensslr. Was already installed. > You can do this this by creating an empty directory > at /etc/sfw/openssl and then pkgadd'ing the b109 SUNWopensslr. > > Let me know if this helps. > > If this doesn't work, at least remove "reconfigure" (located at > /a/reconfigure) file. Solaris will then skip 'Configuring Devices' > and make it easier to troubleshoot. Removed said file and it actually did boot fine. However, there was this error given: fmd: [ID 441519 daemon.notice] SUNW-MSG-ID: FMD-8000-4M, TYPE: Repair, VER: 1, SEVERITY: Minor EVENT-TIME: Thu Feb 26 14:38:39 PST 2009 Mar 11 PLATFORM: Sun Ultra 20 Workstation, CSN: 0540FK400F, HOSTNAME: solenv SOURCE: fmd, REV: 1.2 Mar 11 EVENT-ID: 46a71498-47ce-4f16-d217-c19ce343b385 DESC: All faults associated with an event id have been addressed. Refer to http://sun.com/msg/FMD-8000-4M for more information. AUTO-RESPONSE: Some system components offlined because of the original fault may have been brought back online. IMPACT: Performance degradation of the system due to the original fault may have been recovered. REC-ACTION: Use fmdump -v -u <EVENT-ID> to identify the repaired components. which then yields fmdump -v -u 46a71498-47ce-4f16-d217-c19ce343b385 TIME UUID SUNW-MSG-ID Aug 02 2007 14:04:40 46a71498-47ce-4f16-d217-c19ce343b385 ZFS-8000-CS 100% fault.fs.zfs.pool Problem in: zfs://pool=63927ba16b1db570 Affects: zfs://pool=63927ba16b1db570 FRU: - Location: - Mar 11 19:33:46.9838 46a71498-47ce-4f16-d217-c19ce343b385 FMD-8000-4M Repaired 100% fault.fs.zfs.pool Removed Problem in: zfs://pool=63927ba16b1db570 Affects: zfs://pool=63927ba16b1db570 FRU: - Location: - Mar 11 19:33:47.0928 46a71498-47ce-4f16-d217-c19ce343b385 FMD-8000-6U Resolved 100% fault.fs.zfs.pool Removed Problem in: zfs://pool=63927ba16b1db570 Affects: zfs://pool=63927ba16b1db570 FRU: - Location: - Which I'm certain is my now missing zpool. This zpool was on a firewire drive that was experiencing problems due to bug with firewire. I thought it was fixed in b109, but perhaps not. Thanks, Aric
