Date: Tue, 12 Feb 2008 19:35:24 -0600 From: Damian Wiest <dwiest@vailsys.com> To: freebsd-geom@freebsd.org Subject: GEOM related panic during install Message-ID: <20080213013524.GE82589@dfwdamian.vail>
next in thread | raw e-mail | index | archive | help
I recently tried to install FreeBSD 6.3 on an Intel based server and encountered a geom related panic during the boot process. The symptoms are very similar to those reported here, http://www.nabble.com/bypassing-gmirror-to-recover-filesystems-to9302550.html#a9302550 Here's the relevant output from the boot process: ad4: 476940MB <WDC WD5000YS-01MPB1 09.02E09> at ata2-master SATA150 ad4: 976773168 sectors [969021C/16H/63S] 16 sectors/interrupt 1 depth queue GEOM: new disk ad4 ad4: Intel check1 failed ad4: Adaptec check1 failed ad4: LSI (v3) check1 failed ad4: LSI (v2) check1 failed ad4: FreeBSD check1 failed ata3-master: pio=PIO4 wdma=WDMA2 udma=UDMA133 cable=40 wire ad6: 476940MB <WDC WD5000YS-01MPB1 09.02E09> at ata3-master SATA150 ad6: 976773168 sectors [969021C/16H/63S] 16 sectors/interrupt 1 depth queue GEOM: new disk ad6 ad6: Intel check1 failed ad6: Adaptec check1 failed ad6: LSI (v3) check1 failed ad6: LSI (v2) check1 failed ad6: FreeBSD check1 failed WARNING: Device name truncated! (ad6p57p57p57p57p57p57p57p57p57p57p57p57p57p57p57p57p57p57p57p57) WARNING: Device name truncated! (ad6p57p57p57p57p57p57p57p57p57p57p57p57p57p57p57p57p57p57p57p57) ... [warning repeats many, many times] ... Fatal double fault rip = 0xffffffff803ee5d0 rsp = 0xffffffffb2162fc0 rbp = 0xffffff0076a74680 panic: double fault Uptime: 54s Cannot dump. No dump device defined. Automatic reboot in 15 seconds - press a key on the console to abort --> Press a key on the console to reboot, --> or switch off the system now. I believe that the panic occurs while geom is tasting the system's disks. 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. What's the proper way of recovering from this situation? I can't simply 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 disk. I ended up using a Solaris install CD to write a new label to each 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? -Damian
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20080213013524.GE82589>