From owner-freebsd-stable@FreeBSD.ORG Fri Aug 17 08:44:25 2012 Return-Path: Delivered-To: freebsd-stable@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [69.147.83.52]) by hub.freebsd.org (Postfix) with ESMTP id 15CCC106564A for ; Fri, 17 Aug 2012 08:44:25 +0000 (UTC) (envelope-from gabor.radnai@gmail.com) Received: from mail-ob0-f182.google.com (mail-ob0-f182.google.com [209.85.214.182]) by mx1.freebsd.org (Postfix) with ESMTP id D339B8FC0A for ; Fri, 17 Aug 2012 08:44:24 +0000 (UTC) Received: by obbun3 with SMTP id un3so6678630obb.13 for ; Fri, 17 Aug 2012 01:44:24 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:from:date:message-id:subject:to:content-type; bh=h3cXxyCIeuDmFIJWifgrY9iSkHUrPCk5a9m+7W90XUA=; b=E3J5nFsFeCec+/7UVtoMS1d9nhILX4qwMQGuA4RklPd67HDDPzI4deKr+6txnCIuWe dDcyeWWDkdr4GOh5xmuqMYOJGATg0fmu9HAQxpLKVNs4Th4MWC9aQ7zXSCNHWhHHcRYt ebvBzZUL4RxFISjAo7pQuYwUw6qLB/0Lwi6zXC1lgemlaYixQtyuWjKIKqcOjSd14iZb 1HWbOSRyixy1++71aRM748BcKAytITnI+0zFqxMFNu3eozYTHMoqzA+4W94Ng6CPWaay uhMVtXU1Hd6WrBIiJlXq1zqs71obZ0i/Dd9UiGG99kDgpCmRirkOTTiP6in192Tewgmh s/PQ== Received: by 10.50.186.196 with SMTP id fm4mr1069918igc.1.1345193064064; Fri, 17 Aug 2012 01:44:24 -0700 (PDT) MIME-Version: 1.0 Received: by 10.64.145.101 with HTTP; Fri, 17 Aug 2012 01:44:03 -0700 (PDT) From: Gabor Radnai Date: Fri, 17 Aug 2012 10:44:03 +0200 Message-ID: To: freebsd-stable@freebsd.org Content-Type: text/plain; charset=UTF-8 Subject: GEOM_RAID in GENERIC 9.1 X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 17 Aug 2012 08:44:25 -0000 Sorry the content of original mail I replied to was missed. For clarity here it is: >On 30.07.2012 11:04, Eugene M. Zheganin wrote: >> >> I am aware about how this thing works and what it does. However, every >> time I upgrade new server I got hit by it again and again, simply >> forgetting to remove it from the kernel's config. >> >> I'm afraid this thing will hit lots of FreeBSD installations after the >> release; it may be easily removed but still it will poison the life of >> many engineers and I really think it's a bomb, and should be removed >> from GENERIC. >> >Okay, I feel like I need to clarify this, as some decent guys pointed me >out that I'm very unclear and even rude (sorry for that, that's >unintentional). > >GEOM_RAID was inserted instead of ataraid, but ataraid wasn't messing >with zpooled disks: with GEOM_RAID the kernel takes both (in case of >mirrored pool) providers, and mountroot just fails, as it sees no zfs pool. > >Plus, it's even more. This time I have "disabled" the raid in it's >"BIOS" before installing FreeBSD. After mountroot failed, I booted 9.0-R >from usb flash, trying to avoid any surgery with kernel files, like >manual install from another machine. I was curious if I will be able to >resolve this issue using base utilities. So, I loaded geom_raid via >'graid load', kernel said like 'Doh... I have ada0/ada1 spare disks', >then I tried to remove the softraid label remains with 'graid remove' - >and it failed, because there's no array at all, only "spares". So, the >'graid status' is empty, 'graid list' is empty' and it's obvious that >some surgery is needed. > >And I'm not disappointed that it's happened to me, no, because I know >how to resolve this. >But the thing that I'm really afraid of is that this default option will >hit the less experienced engineers. > >Eugene. My reply again then: Unfortunately I am a less experienced user so no clue how to disable GEOM_RAID but i am hit by this issue. My zfs setup is totally messed up. Would appreciate if you could share the trick. Additionally: building a new kernel solves the issue naturally but is there anything more convenient solution? What is your trick? Thanks in advance, Gabor (and sorry for messing up the mail thread)