From owner-freebsd-questions@freebsd.org Mon Apr 17 19:14:49 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 E51EDD41862 for ; Mon, 17 Apr 2017 19:14:49 +0000 (UTC) (envelope-from bourne.identity@hotmail.com) Received: from EUR03-DB5-obe.outbound.protection.outlook.com (mail-oln040092071023.outbound.protection.outlook.com [40.92.71.23]) (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 736F4931 for ; Mon, 17 Apr 2017 19:14:48 +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=+Lyrvs82JbEkPqjPl+Cm1Qs3J/swBZL6oAAOKCPzNvs=; b=h4oTLWDnMr168r4ibaNVGlW4OwVXQvaczcp6Cr/OzaWH/gqNMaLcv+MvqO+p8l7n1k9y3BZ9ybeQBVg6PSz5om4CH/vS6yTta7Eo9XxYdCyMxEMrRyXVqZrURAiaqNVU3cHK2VlvJMCOnxdSj3blGJ5Fy62HWZ62h1Oe1PyjM9WdYEWX079qEQKsiXXShVmjynQie9+SaPyrMw9rvmx5B5jm+odThzsx5WrsdX9gbKQejFJcCzT6csAKkGzKpRT+D97MgE2x7q53EbOv9e4jo/k0oiLYyirnJT6QJ8lw6lDEPmCvnHO7p4DKRQ9Q6wAHTmdXhO3RF7t1gBjQBwb1iQ== Received: from DB5EUR03FT020.eop-EUR03.prod.protection.outlook.com (10.152.20.52) by DB5EUR03HT196.eop-EUR03.prod.protection.outlook.com (10.152.20.188) 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 19:14:46 +0000 Received: from VI1PR02MB1200.eurprd02.prod.outlook.com (10.152.20.51) by DB5EUR03FT020.mail.protection.outlook.com (10.152.20.134) 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 19:14:46 +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 19:14:46 +0000 From: Manish Jain To: Shamim Shahriar CC: "freebsd-questions@FreeBSD.org" Subject: Re: 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+6HJ4faAgAAMwIA= Date: Mon, 17 Apr 2017 19:14:46 +0000 Message-ID: References: In-Reply-To: Accept-Language: en-GB, en-US Content-Language: en-US X-MS-Has-Attach: X-MS-TNEF-Correlator: authentication-results: gmail.com; dkim=none (message not signed) header.d=none;gmail.com; dmarc=none action=none header.from=hotmail.com; x-incomingtopheadermarker: OriginalChecksum:D0B7FE124B312A2225E6103D7C42FBC861387D70FA3DFA10D4E39F09A6F25844; UpperCasedChecksum:02CAD12559A46B0E646F5DC1693D7A303818EA8AB4826A4B9601AACBBAE0B7A5; SizeAsReceived:8076; Count:40 x-ms-exchange-messagesentrepresentingtype: 1 x-microsoft-exchange-diagnostics: 1; DB5EUR03HT196; 5:qgfoYV3TzMD5VzWOai5SM9GT3bLNQElWGBtoMFA45FQ2nHDGskLbvGw/UZVA4tcYdT9QA1yKAl1j15jBQqBhd4Hps8rF6GLP513Kbgl/WDBBL91a6FkVCuYRikRL2ZRHjeOrzWgy6jeiHD2qdbNCzQ==; 24:yyh/qsDdY9gBco2Gheus+n4pR5kJ+1QfenTSPaLnpZphDQfMlcmI0Rn2jlTLjyFKy4Iuk6vOg8n+r2AdES/OSCKdcfh/ylobEWOYqv+p4CM=; 7:qSsI8n/uFgtpWjf/7smg83GcX5SbZ/wwzS/7KG4dg9W9a76rcTn0efh7HGLW2xaBOdYPaACP4vEjtskYoJfayjT+/L4m1lncSCPsw/bzJtSeU2daPo+jhABifrwoKr5++ypG2gTyIID1NyC2w7yWkpqlVpSuo2Z/VAGFrd6iZ4HtVSKX3PsfcsyD1Pu26FEpXpm1bnLvVNoENvtY1O/GzpyulmarfGQ9pYN8Y1lRxvM59u8mskmluZGC+SHAYNVA2GD8DxGlryPWc/DpUzMYtvCjXH2EQFInqFSVW4m01wj5OVrHRGs5dw/WpKd574mb x-incomingheadercount: 40 x-eopattributedmessage: 0 x-forefront-antispam-report: EFV:NLI; SFV:NSPM; SFS:(7070007)(98901004); DIR:OUT; SFP:1901; SCL:1; SRVR:DB5EUR03HT196; H:VI1PR02MB1200.eurprd02.prod.outlook.com; FPR:; SPF:None; LANG:en; x-ms-office365-filtering-correlation-id: 4ab53674-01b2-45fa-fbb1-08d485c60203 x-microsoft-antispam: UriScan:; BCL:0; PCL:0; RULEID:(22001)(201702061074)(5061506573)(5061507331)(1603103135)(2017031320274)(2017031324274)(2017031323274)(2017031322274)(1603101448)(1601125374)(1701031045); SRVR:DB5EUR03HT196; x-exchange-antispam-report-cfa-test: BCL:0; PCL:0; RULEID:(444000031); SRVR:DB5EUR03HT196; BCL:0; PCL:0; RULEID:; SRVR:DB5EUR03HT196; x-forefront-prvs: 02801ACE41 spamdiagnosticoutput: 1:99 spamdiagnosticmetadata: NSPM Content-Type: text/plain; charset="Windows-1252" Content-ID: <5871D8C200830D4082A79EF03E99691A@eurprd02.prod.outlook.com> Content-Transfer-Encoding: quoted-printable MIME-Version: 1.0 X-OriginatorOrg: hotmail.com X-MS-Exchange-CrossTenant-originalarrivaltime: 17 Apr 2017 19:14:46.3667 (UTC) X-MS-Exchange-CrossTenant-fromentityheader: Internet X-MS-Exchange-CrossTenant-id: 84df9e7f-e9f6-40af-b435-aaaaaaaaaaaa X-MS-Exchange-Transport-CrossTenantHeadersStamped: DB5EUR03HT196 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 19:14:50 -0000 On Monday 17 April 2017 11:58 PM, Shamim Shahriar wrote: > Hello > > Just out of curiosity, did you try changing the vfs.root.mount option=20 > in the loader.conf? Also, I'm not sure what you mean by having to=20 > press F2 -- it can mean do many different things at various stages of=20 > booting, if refrain from using a guess. > > Hope this helps > Hi Shamim, Thanks for responding. Your tip would probably have been more useful had=20 the FreeBSD installation been rendered unbootable - which is not the=20 case here. It is just that I was having to press F2 instead of F3 to=20 boot FreeBSD. BTW, F is the function key methodology that the Boot Easy manager=20 installed via boot0cfg uses to boot operating systems on an MBR disk. If=20 I were to list the things in FreeBSD which make it better than anything=20 else on this planet, my list would begin with : No-Blink Cursor;=20 Beastie; the inbuilt ports+pkg combination; and - last but surely not=20 the least - Boot Easy. Returning to my problem, I ran into some seriously good luck. A google=20 search got me to locate there there are commercial tools on the internet=20 which can alter slice indexes in the MBR table. But there is no way I am=20 ever to going to pay for commercial software. Software must either be=20 open-source or free - even pirated software seems a better option to me=20 than commercial goodies : -) But since there are tools available that claim to do be able to do this,=20 I opined that it would be worth a shot to see the effects of recreating=20 the slice from within Windows. (I was anyway ready the delete all slices=20 and install FreeBSD afresh with the right MBR indexes for slices). So I booted Windows again, and used CompMgmt.msc to create a slice in=20 the 'hole' at ada0s2. (As per the correct/normal geometry : ada0s3 is=20 FreeBSD and ada0s4 is already occupied with an EBR slice). To my pleasant surprise, MS did a darned good thing : it created the=20 slice; and simultaneously shuffled the slice order yet again to=20 normalize them with 2 after 1; 3 after 2; and 4 after 3. So it ends pleasantly for me. When I rebooted the system, Boot Easy=20 prompted me with F3 for FreeBSD. And the installation boots normally=20 when I press F3 - as if nothing ever happened. But I do wish folks reading this message to draw a lesson : never use=20 Windows for management of non-native slices. As far as possible, use=20 gpart Or Linux fdisk. Regards Manish Jain