Date: Mon, 17 Apr 2017 19:28:57 +0100 From: Shamim Shahriar <shamim.shahriar@gmail.com> To: Manish Jain <bourne.identity@hotmail.com> Cc: "freebsd-questions@FreeBSD.org" <freebsd-questions@freebsd.org>, Polytropon <freebsd@edvax.de> Subject: Re: Is it possible to fix slice order with gpart/any other tool ? Message-ID: <CAOyJeZT4js8UhHXVTjCpjXqRWewGQTtEC-td=Lb%2BowCH1%2B34Ow@mail.gmail.com> In-Reply-To: <VI1PR02MB1200105F68383363B35D0DE9F6060@VI1PR02MB1200.eurprd02.prod.outlook.com> References: <VI1PR02MB1200105F68383363B35D0DE9F6060@VI1PR02MB1200.eurprd02.prod.outlook.com>
next in thread | previous in thread | raw e-mail | index | archive | help
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" <bourne.identity@hotmail.com> 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" >
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?CAOyJeZT4js8UhHXVTjCpjXqRWewGQTtEC-td=Lb%2BowCH1%2B34Ow>