Also, Peter, do a boot -v.  If the boot fails or succeeds you should
    see a different set of CAM debug messages on the console and hopefully
    be able to track down which CAM device is having the problem and/or
    where.

                                                -Matt

Reply via email to