From owner-freebsd-questions@freebsd.org Mon Apr 17 18:29:00 2017 Return-Path: Delivered-To: freebsd-questions@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 0EB0FD42212 for ; Mon, 17 Apr 2017 18:29:00 +0000 (UTC) (envelope-from shamim.shahriar@gmail.com) Received: from mail-wm0-x230.google.com (mail-wm0-x230.google.com [IPv6:2a00:1450:400c:c09::230]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (Client CN "smtp.gmail.com", Issuer "Google Internet Authority G2" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 9695F1A1E for ; Mon, 17 Apr 2017 18:28:59 +0000 (UTC) (envelope-from shamim.shahriar@gmail.com) Received: by mail-wm0-x230.google.com with SMTP id u2so37570429wmu.0 for ; Mon, 17 Apr 2017 11:28:59 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025; h=mime-version:in-reply-to:references:from:date:message-id:subject:to :cc; bh=8DK0XMvbeNkjJrPgTsyR87bdUPBc5++i37Ez2k8zrK0=; b=AVriMqKL574P8uubmMPFLGjGBH8ZZRr8KS6M7jhMYVt67rvHEvP/O3dSsIOPqSIZKC GEE0lUG2o1FJbePuvR49RILcgMTYgNddyHNc9HUpViGm1j4bnEWxkkxCuUbkXp2aI7oC I7Ev16aSGX/shotYIfpBmznE+LSX+yBE3QP+AuSMyUmIcCu1BvX5l5wdwt/W+Zaryuk8 dDZ2iYNwC20/tYMKIcmf393ZRniSh5eme3wF00YZt8se8t2PEROX4UsNmHi5lWSPj1ab VSUiEwiOOIrfAPEGUDkxIOwydUdCzrz/ZpHnO7hxQ7wS9uZr86MYmH8XiIIfM2+ykRpe bv8w== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:in-reply-to:references:from:date :message-id:subject:to:cc; bh=8DK0XMvbeNkjJrPgTsyR87bdUPBc5++i37Ez2k8zrK0=; b=uC/uEz5if5Xww9HR+9kWU25LjEsUYh0Xq2h5yXsIV5yeZpiG0l8X7PO+a735DHZHW3 XcgOhOpzCuLMrarvuca+qaouz7D5STC0T4F8T5Xp1Wl1bLJRU+YDUwYG+PHqJUk/giHU i21VeXhKrXw1U9V3o2xRCU45CLvAVPJDJoZgoPXg0aX96T+4k7qZtkvDv+qNJb9Q7ahZ M2fvTJXv1wfMJDgYhNIMKsct+MY+EXwiI1xLycHH9eBGfhfsZpJ9afM3tenaPIy9JJ0a 0cQ9ni10xN6Q53kyjSS9uggFpKyDCb+tIYGgN4+fJxcJ07CdYImzCfE3fpU0G8pDEyHz GGaA== X-Gm-Message-State: AN3rC/7fU7Q4jR/VT4m94/sRuUXDZWesROqMo1GscKKRcNEF5QoabSsB wDchXbWuQmKDadMRqZWZXywsGJK2SA== X-Received: by 10.28.93.65 with SMTP id r62mr1680271wmb.70.1492453738006; Mon, 17 Apr 2017 11:28:58 -0700 (PDT) MIME-Version: 1.0 Received: by 10.80.134.37 with HTTP; Mon, 17 Apr 2017 11:28:57 -0700 (PDT) Received: by 10.80.134.37 with HTTP; Mon, 17 Apr 2017 11:28:57 -0700 (PDT) In-Reply-To: References: From: Shamim Shahriar Date: Mon, 17 Apr 2017 19:28:57 +0100 Message-ID: Subject: Re: Is it possible to fix slice order with gpart/any other tool ? To: Manish Jain Cc: "freebsd-questions@FreeBSD.org" , Polytropon Content-Type: text/plain; charset=UTF-8 X-Content-Filtered-By: Mailman/MimeDel 2.1.23 X-BeenThere: freebsd-questions@freebsd.org X-Mailman-Version: 2.1.23 Precedence: list List-Id: User questions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 17 Apr 2017 18:29:00 -0000 Hello Just out of curiosity, did you try changing the vfs.root.mount option in the loader.conf? Also, I'm not sure what you mean by having to press F2 -- it can mean do many different things at various stages of booting, if refrain from using a guess. Hope this helps On 17 Apr 2017 2:26 pm, "Manish Jain" wrote: > Hi, > > > I am running FreeBSD CURRENT amd64 . As part of attempts to use ZFS on my > MBR disk, I have made a serious error which has resulted in the slice > order in the MBR being changed. > > > My attempt to use ZFS followed this strategy : > > > 1) installed FreeBSD CURRENT on ada0s2 (BSD+UFS) with a spare slice ada0s3 > available > > 2) set up a ZFS root at ada0s3a > > 2) migrated the installation using rsync to the ZFS tank > > > The migration was surprisingly painless and successful. In less than a day > of first-time efforts, my ZFS setup was up and fully running - with the KDE > plasma5 desktop (thanks area51) migrated as part of the venture. > > > But following this fairly spectacular effort, I blundered. I have a > Windows installation on ada0s1. After the migration, I booted that > installation to check whether it was okay. During the check, I mindlessly > used the Computer (Disk) Management console to delete ada0s2. Upon reboot I > realized that this has now become a serious issue : Windows has altered the > slice order in the MBR. Instead of just dropping slice 2, MS has dropped 2 > and changed 3 to 2. So when I boot the system, I have to use F2 to trigger > the FreeBSD installation. > > > This does not go well with me. Being obsessive (particularly about the > small things in life), I cannot bear the thought of being stuck with the > wrong slice arrangement in the MBR table. If necessary, I can delete the > whole system and reinstall everything afresh. But I do wonder if gpart has > the ability to fix the slice order. > > > If anyone can tell me possibilites and steps to fix to rearrange the MBR > table (ada0s2 -> ada0s3), that shall be very nice. Thanks for any help. > > > Manish Jain > > _______________________________________________ > freebsd-questions@freebsd.org mailing list > https://lists.freebsd.org/mailman/listinfo/freebsd-questions > To unsubscribe, send any mail to "freebsd-questions- > unsubscribe@freebsd.org" >