Perhaps the cpqary3 driver update was only done to the installer's ramdisk environment and not also to the installed pool?
On Thu, May 23, 2013 at 12:30 PM, Aleš Jagrič, Fora d.o.o. <ales.jag...@forum-racunalnistva.eu> wrote: > Thanks for the input but that did not help, I have tried something similar > before, the error message returned was the same. > > > > P.S. > > The rpool mounts perfectly fine with the live cd, this is a fresh install on > this hardware, it’s not ported from anywhere. > > > > Unless I’m missing something. > > > > From: Dale Ghent [mailto:da...@omniti.com] > Sent: Thursday, May 23, 2013 5:33 PM > To: Aleš Jagrič, Fora d.o.o. > Cc: omnios-discuss@lists.omniti.com > Subject: Re: [OmniOS-discuss] OmniOS install on HP DL360g8 > > > > > > The phys_path attribute in your disk label for your rpool needs to be > updated, as it sounds like the rpool was created on different hardware which > had different device paths than the machine you're trying to boot on here. > > > > A quick way to fix this is to boot off the install CD or USB image and: > > > > zpool import -R /a -f rpool > > > > That action alone will update the attribute and you should then be able to > boot normally. > > > > /dale > > > > > > On May 23, 2013, at 11:10 AM, Aleš Jagrič, Fora d.o.o. > <ales.jag...@forum-racunalnistva.eu> wrote: > > > > Hey, > > > > We're testing a new hardware deployment and we're having some trouble with > this server type. The cpqary3 driver included with the omnios stable is > obsolete, and I replaced it in the shell before the install. > > > > The server is a HP DL 360 g8 with a P420i Smart array. > > > > OmniOS installs just fine after replacing the driver but after the initial > reboot the kernel panics, with the error message (see attachment for > screenshot hopefully it’s visible) > > > > NOTICE: Can not read the pool label from '/pci@0,0/…./sd@0,0:a' > NOTICE: spa_import_rootpool: error 5 > > .. > > .. > > . > > > > I’ve googled for similar errors but the fixes mentioned there had no effect > (importing and exporting the pool from a live boot) > > > > I've tested with OmniOS OmniOS_Text_r151004, OmniOS_Text_r151006 and > OmniOS_Text_bloody_20130208. The same image and procedure to replace the > driver works just fine on a DL380g5 with a P400 controler. > > > > While the same procedure works just fine with openindiana 151a7. But I'm not > willing to put openindiana in production. > > > > > > Any pointers how to solve this or what might be causing this? > > > > ________________________________ > > This e-mail and any attachments may contain confidential and/or privileged > information and is intended solely for the addressee. If you are not the > intended recipient (or have received this e-mail in error) please notify the > sender immediately and destroy this e-mail. Any unauthorized copying, > disclosure or distribution of the material in this e-mail is strictly > forbidden. E-mail message is scanned by Anti-Virus Software. > <ilo.PNG>_______________________________________________ > OmniOS-discuss mailing list > OmniOS-discuss@lists.omniti.com > http://lists.omniti.com/mailman/listinfo/omnios-discuss > > > > > ________________________________ > This e-mail and any attachments may contain confidential and/or privileged > information and is intended solely for the addressee. If you are not the > intended recipient (or have received this e-mail in error) please notify the > sender immediately and destroy this e-mail. Any unauthorized copying, > disclosure or distribution of the material in this e-mail is strictly > forbidden. E-mail message is scanned by Anti-Virus Software. > > _______________________________________________ > OmniOS-discuss mailing list > OmniOS-discuss@lists.omniti.com > http://lists.omniti.com/mailman/listinfo/omnios-discuss > _______________________________________________ OmniOS-discuss mailing list OmniOS-discuss@lists.omniti.com http://lists.omniti.com/mailman/listinfo/omnios-discuss