Arrghhh. I booted to DOS boot floppy and recreated the MBR (fdisk /mbr).
Still getting kernel panic. I also completely cleared the MBR via a linux boot CD, same thing. Is there a way to capture the kernel panic output during the boot up of the CD? The point of panic is difficult to judge because it scrolls off the screen too quickly. I have a suspicion it might be at the point Solaris is searching the HDD's for an existing install. Can this search be disabled? Does it search HDD's for an existing install during the CD boot? I might try disabling the ZFS module (and a few other things) and see what happens. If I disable a module from GRUB, can I load the module later (within a terminal window during the install). Or will the kernel prevent me from loading it? A "modload" of a disabled module doesn't appear to work. Thank you to everyone that has assisted thus far. Murray Blakeman wrote: > I think you're right on the money. After a bit of playing around I > disabled the "cmdk" driver during boot and now I can get into the > Solaris install. > > So it seems there is something about the RAID that cmdk doesn't like. > > Now without that driver I can't access the drives. :-( > > I might try boot to DOS and remove mbr with fdisk. > > Peter J. Cherny wrote: >> From past experience, the lack of a disc label often causes a crash <g> >> >> My Q&D in the past is to boot xBSD, and label the disc and create a >> partition table, any partition table. >> >> I might have a play tomorrow if I can resurrect some x86 h/w. >> I'm only running Solaris on SPARC at the moment, FreeBSD on the rest. >> >> pjc >> >> p.s. I now read that you're in single user, >> so devfsadm and format will work ! >> >> > _______________________________________________ > ug-msosug mailing list > ug-msosug at opensolaris.org > http://mail.opensolaris.org/mailman/listinfo/ug-msosug >
