From owner-freebsd-questions@freebsd.org Mon Apr 17 13:26:20 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 BCF3AD41B4E for ; Mon, 17 Apr 2017 13:26:20 +0000 (UTC) (envelope-from bourne.identity@hotmail.com) Received: from EUR02-VE1-obe.outbound.protection.outlook.com (mail-oln040092069038.outbound.protection.outlook.com [40.92.69.38]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-SHA384 (256/256 bits)) (Client CN "mail.protection.outlook.com", Issuer "Microsoft IT SSL SHA2" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 385CFB3B for ; Mon, 17 Apr 2017 13:26:19 +0000 (UTC) (envelope-from bourne.identity@hotmail.com) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=hotmail.com; s=selector1; h=From:Date:Subject:Message-ID:Content-Type:MIME-Version; bh=8PV4T/ag4xviSZPZPwXcXwizN7caTkgS6/XDCDAinB4=; b=s75XcImf5RZUnK990ZSpacfH5PXK91FxZaQvyFRRX8cR4eDyjt9QDlE/45nhUb6ZmFSQWPtiBfw8tv9OaE0QFu0Z0zkRJHvthTrDtsTE2k+JMh0OGgQ7T75kvg4YkOAiv9kBFCO6PYtLiIsYYiuGS6sxfNesZ++ZCScG0D8HFTEgcNX72vnuqKtZYI5IepMWUbdWCsL6METy5mYPhr7UGjT4vmjNpqx7YmLwHGe4RmFg2R3oxEtgj8J/55X98d4SoHnCZ6lWzGCLy2ymPZn9PwQzhvrx/HZqiS/25baJFtPgrNmMVnJsluHzYq7g5ds9ZlpzEiGXM09hlNBHih1uBg== Received: from AM5EUR02FT019.eop-EUR02.prod.protection.outlook.com (10.152.8.57) by AM5EUR02HT049.eop-EUR02.prod.protection.outlook.com (10.152.9.125) with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_256_CBC_SHA384_P384) id 15.1.1019.14; Mon, 17 Apr 2017 13:26:17 +0000 Received: from VI1PR02MB1200.eurprd02.prod.outlook.com (10.152.8.54) by AM5EUR02FT019.mail.protection.outlook.com (10.152.8.169) with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_128_CBC_SHA256_P256) id 15.1.1019.14 via Frontend Transport; Mon, 17 Apr 2017 13:26:17 +0000 Received: from VI1PR02MB1200.eurprd02.prod.outlook.com ([10.163.164.28]) by VI1PR02MB1200.eurprd02.prod.outlook.com ([10.163.164.28]) with mapi id 15.01.1034.011; Mon, 17 Apr 2017 13:26:17 +0000 From: Manish Jain To: "freebsd-questions@freebsd.org" , Polytropon Subject: Is it possible to fix slice order with gpart/any other tool ? Thread-Topic: Is it possible to fix slice order with gpart/any other tool ? Thread-Index: AQHSt34wDx1smCWmAUuXkEPp5Jhz+w== Date: Mon, 17 Apr 2017 13:26:17 +0000 Message-ID: Accept-Language: en-GB, en-US Content-Language: en-GB X-MS-Has-Attach: X-MS-TNEF-Correlator: authentication-results: freebsd.org; dkim=none (message not signed) header.d=none;freebsd.org; dmarc=none action=none header.from=hotmail.com; x-incomingtopheadermarker: OriginalChecksum:24C06732027D1539826F693291780C939E3E6FBD0AA36A42BD35E37B33A830C2; UpperCasedChecksum:73BC2608EA2E5BF42684B33BB4B6425B9428439F5DB9C2BFE0E373B97B013CD5; SizeAsReceived:7969; Count:40 x-ms-exchange-messagesentrepresentingtype: 1 x-tmn: [GCpqNTHwdm1WNi3yulzC5EOhRHmf99Aa] x-microsoft-exchange-diagnostics: 1; AM5EUR02HT049; 5:QbGdJaJcffCtBtD1CcN6q48XCJ5XOCh0YB7rMPpCkSqWDsbptBGjy2hsrvENarDd/fopAHx6jLV4V800yy++2gTujUXAKos3VTt6zxCZDjEALiB1nfAh0No0WVK//QAtSFCD6EZ5ObqXv3KhFhVawA==; 24:Fy1IUyUU9TwcCG9bxfAA2qXI+vdzyWi3Frech3of9lYVt1c/NhfDtXZ9NkgLaIy+Mq1n84rmqr+yzgmr/LnohDFT+FFp2BgC+wH3mccPmDA=; 7:Lfb/MMNx4qSC11Tr5cESTK2wc04HJgk/YfaE320wwKO+AOe29jLsaN2/In4KfrT+8Z7MFVc053IGSJyZA2n5tsqFgb9C6v5DZpwZdqgTxfKHRkk9/57Q9faHvdD7u1Q07PKj1HzXudyziP6BHqM0csP1TG3OENt4tRwgBiPQu7iuxsCvkyhi4MZ0UK2GPpZHyD01bjZGXo04Cpjn2erT8eQ1Wl2H5iwqKS6KAiVFQJ6WeK8JZbQgWh6ZH3AoKDtUJ+Asmc9/QOmXZ3QG0Z21Acr2hwjlcGe7Sy0/wzTsSaMC68ProV7I3vz+IDRcrdvR x-incomingheadercount: 40 x-eopattributedmessage: 0 x-forefront-antispam-report: EFV:NLI; SFV:NSPM; SFS:(7070007)(98901004); DIR:OUT; SFP:1901; SCL:1; SRVR:AM5EUR02HT049; H:VI1PR02MB1200.eurprd02.prod.outlook.com; FPR:; SPF:None; LANG:en; x-ms-office365-filtering-correlation-id: 06b36111-c050-41e3-3969-08d4859553f9 x-microsoft-antispam: UriScan:; BCL:0; PCL:0; RULEID:(22001)(201702061074)(5061506573)(5061507331)(1603103135)(2017031320274)(2017031324274)(2017031323274)(2017031322274)(1601125374)(1603101448)(1701031045); SRVR:AM5EUR02HT049; x-exchange-antispam-report-cfa-test: BCL:0; PCL:0; RULEID:(444000031); SRVR:AM5EUR02HT049; BCL:0; PCL:0; RULEID:; SRVR:AM5EUR02HT049; x-forefront-prvs: 02801ACE41 spamdiagnosticoutput: 1:99 spamdiagnosticmetadata: NSPM MIME-Version: 1.0 X-OriginatorOrg: hotmail.com X-MS-Exchange-CrossTenant-originalarrivaltime: 17 Apr 2017 13:26:17.0608 (UTC) X-MS-Exchange-CrossTenant-fromentityheader: Internet X-MS-Exchange-CrossTenant-id: 84df9e7f-e9f6-40af-b435-aaaaaaaaaaaa X-MS-Exchange-Transport-CrossTenantHeadersStamped: AM5EUR02HT049 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable 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 13:26:20 -0000 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 orde= r 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 Compute= r (Disk) Management console to delete ada0s2. Upon reboot I realized that t= his 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 in= stallation. This does not go well with me. Being obsessive (particularly about the smal= l 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 sy= stem and reinstall everything afresh. But I do wonder if gpart has the abil= ity to fix the slice order. If anyone can tell me possibilites and steps to fix to rearrange the MBR ta= ble (ada0s2 -> ada0s3), that shall be very nice. Thanks for any help. Manish Jain