15k after patches: Cannot assemble drivers for root /pci@1c,700000/scsi@1/d

Question

All domains booted fine before patching through my local patch proxy on Thursday, June 15th. After running smpatch update, all domains went into the reboot loop with:
Cannot assemble drivers for root /pci@1c,700000/scsi@1/disk@0,0:b
Jun 15 20:42:57 2006 Cannot mount root on /pci@1c,700000/scsi@1/disk@0,0:b fstype ufs
I've reviewed other posts with similar error but there shouldn't be a driver completely missing, as it did boot fine many times before patching. From google search it looked as if /kernel/drv/sd.conf might have been effected by a patch, but that doesn't seem to be the case as a search through all /var/sadm/patch doesn't show any files with that string. Perhaps the scsi drivers were changed somehow?
If this is a patch, I would really like to narrow down which one it might be so I don't need to un-install all of them.
t

Answer 1

Thanks for the responses, I really do appreciate the help.
My goal was to install Solaris 8 onto 2 systems, a V880 and a V890.
Initially my problem was that I tried to install our existing Solaris 8 07/03 flash archive onto the V880 (and V890). But the V880 and V890 needed newer hardware links, I had to re-create our Solaris 8 flash archive with the 02/04 release of Solaris 8.
Now the V880 and V890 would boot from the network and the OS would install onto the local drives. But when the OS would boot from the local disk, I would received the error "Cannot assemble drivers for root /pci@8,600000/SUNW,qlc@2/fp@0,0/disk@w500000e01
1476eb1,0:a". The machine would panic and cycle - booting and panincing over and over again.
Since the net boot image recognized the disks but the flash archive installed image did not, I booted the V880 with "boot net -s" to view the loaded modules. I compared a V240 running Solaris 8 with the net booted V880 as I have no other V880s in the environment. I also compared the directories /kernel/drv/sparcv9/ to see which drivers were missing.
What I discovered is that since I create our flash archive on a scsi based system and I did not use the SUNWCXall package cluster in the profile, the drivers for the FC-AL drives do not get included on the system from which the flash archive is created. The V880 and V890 internal drives are FC-AL based. This was the root cause of my problem.
Thru the comparison described above, I learned that I needed to add the following packages to the install profile of the master system:
socal driver - SUNWluxl and SUNWluxlx
qlc driver - SUNWqlc and SUNWqlcx
usoc driver - SUNWusoc and SUNWusocx
Then I recreated the flash archive and re-jumped the V880 and V890. Both systems booted from their internal drives. And there was much rejoicing...