I have installed both b74 (snv_74) and b55 (snv_55) on an HP DL385/G2. 4GB RAM + 3 SAS 147GB disk. The 385 uses a p400 SATA raid controller. The Solaris driver "CPQary3-1.71-solaris10-i386" is loaded at the "update drivers" prompt via USB diskette at the first stage of install.
I have attempted install about 12 times using snv_74 and a couple times with snv_55. Doing a full package install, I generally do not get a boot at all after install I get the GRUB screen, but when snv_74 is entered, - GRUB just restarts the server, and GRUB failsafe indicates "searching for installed OS instances...No installed OS instance found" and trying "format -e" gets "NO DISK FOUND". Usually in those installs, I would see errors at completion that say logging bootadm failed due to no space or somesuch. Using a core install, no networking, it will boot, but I get this: checking ufs filesystems /dev/rdsk/c2t0d0s7: is logging. Oct 18 21:29:32 svc.startd[7]: svc:/network/shares/group:default: Method "/usr/sbin/sharemgr start default" failed due to signal KILL. Oct 18 21:29:32 svc.startd[7]: svc:/network/shares/group:default: Method "/usr/sbin/sharemgr start default" failed due to signal KILL. Oct 18 21:29:32 svc.startd[7]: svc:/network/shares/group:default: Method "/usr/sbin/sharemgr start default" failed due to signal KILL. Oct 18 21:29:32 svc.startd[7]: svc:/network/shares/group:default: failed: transitioned to maintenance (see 'svcs -xv' for details) syslogd: line 45: WARNING: loghost could not be resolved [b][i]---- ***2 hours later*** ----[/i][/b] SolarisMassive console login: root Password: (password entered) [b][i]---- ***1.5 hours later*** ----[/i][/b] Oct 19 00:29:35 SolarisMassive svc.startd[7]: system/boot-archive-update:default failed: transitioned to maintenance (see 'svcs -xv' for details) [b][i]---- ***38 minutes later*** ----[/i][/b] Oct 19 01:08:49 SolarisMassive login: ROOT LOGIN /dev/console couldn't set locale correctly Sun Microsystems Inc. SunOS 5.11 snv_55 October 2007 # syslogd: line 45: WARNING: loghost could not be resolved With no prompt. This happens with both snv_55 and snv_74. Me thinks, after reading as much as I could find, this as something to do with the controller driver not being saved/written in 2 places...or/and appending loghost to /etc/hosts file (which I can not get seem to get to as I can not navigate vi in GRUB) All ideas are welcome at this point. This message posted from opensolaris.org
