On 9/7/07, Sean Liu <[EMAIL PROTECTED]> wrote: > Hi there, > > I've got a few existing servers with SAN disks allcated/mapped, and I need to > reinstall them. Since Solaris 10 recognises SAN disks off the bat, the > controller numbers of the internal boot disks may change wildly. Is there a > way to exclude SAN disks upon system boot? I can modify the miniroot no > problem.
Assuming you are using a qlogic HBAs and you don't have FC boot disks, add: exclude: qlc To the miniroot's /etc/system. When I was first playing with SAN boot, I also noticed that having a devalias for rootdisk pointed to the path of the disk caused jumpstart to use that for profile rules like: filesys rootdisk.s0 8192 / I have since extended my jumpstart environment to have a begin script that will recognized jsroot1 and jsroot2 devaliases (d0, mounted at / is a mirror of those two devices). If those are found, the begin script will figure out the appropriate ctd name and create the custom profile appropriately. If no jsroot* entries are found, the begin script falls back on per-architecture rules that I've defined. Mike -- Mike Gerdts http://mgerdts.blogspot.com/ _______________________________________________ storage-discuss mailing list [email protected] http://mail.opensolaris.org/mailman/listinfo/storage-discuss
