Date: Wed, 13 Feb 2008 11:19:56 +0100 From: Ivan Voras <ivoras@freebsd.org> To: freebsd-geom@freebsd.org Subject: Re: GEOM related panic during install Message-ID: <foug4s$9hf$1@ger.gmane.org> In-Reply-To: <20080213013524.GE82589@dfwdamian.vail> References: <20080213013524.GE82589@dfwdamian.vail>
next in thread | previous in thread | raw e-mail | index | archive | help
This is an OpenPGP/MIME signed message (RFC 2440 and 3156) --------------enigD945FF17E44D55F7D8106797 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: quoted-printable Damian Wiest wrote: > I believe that the panic occurs while geom is tasting the system's disk= s. > AFAIK, the disks were new, but someone here had configured the BIOS to = > use the onboard soft-RAID controller to mirror the drives. I disabled = > this setting before beginning the install, so I suspect that's how the = > label on ad6 got messed up. >=20 > What's the proper way of recovering from this situation? I can't simpl= y > pull the offending disk, boot into FreeBSD, reinsert the disk and then > use dd to zero the label because x86/amd64 servers won't notice the new= =20 > disk. I ended up using a Solaris install CD to write a new label to ea= ch > disk, but I suppose I could build a custom kernel that does not contain= > any of the geom modules and use that as a fixit disk. Do I just need > to use boot option 6 and then have the loader unload any modules? The problem here is that even if you do remove optional GEOM modules/classes from the kernel, you'll still be left with the GEOM framework which does the initial tasting, which you can't remove because it's the kernel's interface to the drives. Also, the "Intel check1 failed" messages are from the ATA driver, as it tries to recognize BIOS/soft-raid configurations, and you can't remove that. It (the ATA driver) is also the probable cause of the panic here. It would be useful if you tried to debug the problem in the driver - try and download a recent snapshot of 8-current, with debugging enabled, and see if you can get a backtrace on panic which would help fix the driver. Other than that, you'll probably have to boot another OS (Linux, Solaris, etc.) and use dd to clear the first few and the last few sectors of the drives. --------------enigD945FF17E44D55F7D8106797 Content-Type: application/pgp-signature; name="signature.asc" Content-Description: OpenPGP digital signature Content-Disposition: attachment; filename="signature.asc" -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.6 (GNU/Linux) iD8DBQFHssRNldnAQVacBcgRAnfvAKC7dQpMXCtnwhseUlrgCrvuCprsYQCcC8d1 DYykWGQhuLKaLw2k/XKQp5A= =exne -----END PGP SIGNATURE----- --------------enigD945FF17E44D55F7D8106797--
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?foug4s$9hf$1>