Sponsored Content
Special Forums Hardware Boot Loaders GPT/Protective MBR problem... Post 302470525 by fpmurphy on Wednesday 10th of November 2010 10:10:05 AM
Old 11-10-2010
Yes, that is the best plan. Glad you had a backup. It is my opinion that utilities such as gdisk should not attempt to automatically convert from MBR to GPT and visa versa. Too many edge cases where things can go wrong.

Last edited by fpmurphy; 11-10-2010 at 11:15 AM..
 

6 More Discussions You Might Find Interesting

1. UNIX for Dummies Questions & Answers

Delete gpt signatures

Hi Can anyone tell me how to delete GPT signatures in linux/unix. Thanks Tannu (3 Replies)
Discussion started by: tannu
3 Replies

2. Red Hat

RHEL4 easyRAID problem 2tb gpt xfs

hello community, i have problems with my redhat enterprise linux 4 nanhant 6 and my easyraid x8s (8x1tb) extern fibre channel raid extern raid configuration: raid level 5 (8x1tb) redhat system shows me four 2tb partitions and one 450gb partition from my raid :( why????? i have... (1 Reply)
Discussion started by: onkeldave
1 Replies

3. Fedora

Disk Paritioning Scheme--GPT or MBR

Hi, I just built myself a new machine which has an ASUS motherboard with is UEFI based. I noticed after I installed Fedora 17 that my sda is MBR and my sdb is GPT: sda is a ssd drive. Should the ssd drive be GPT or is MBR okay? sda is 60Gb drive. (3 Replies)
Discussion started by: mojoman
3 Replies

4. Windows & DOS: Issues & Discussions

Installing Windows 7 on a GPT drive

Hello, My hard drive was formatted with GPT. It is part of a volume group and has two logical volumes on it. Is it possible to convert the drive to MBR? If so, how would I got about doing it? I know there are programs out there that do it, but I have volume groups with LVM's so I am wondering if... (1 Reply)
Discussion started by: mojoman
1 Replies

5. Red Hat

GPT Partitions

(Don't you hate being on holiday and being the only IT person in the family?) Got a wonderful thanksgiving surprise .. dead windows-8 laptop with "important" unbacked-up data. No worries, I have my my fedora labtop and a magical SATA to USB converter. Plugged in the drive, and ... can't mount... (4 Replies)
Discussion started by: derekludwig
4 Replies

6. Emergency UNIX and Linux Support

2nd hdd is Linux_lvm can't mount MBR on BSD with GPT

rying it this way, because I can't handle the slices for the second hdd. If there is someone on this forum who can help me out of that misery, he would really save my digital life in this digital ocean. So not giving up, reading several times the manual of gpart. But the best hint in all that... (0 Replies)
Discussion started by: 1in10
0 Replies
GPTZFSBOOT(8)						    BSD System Manager's Manual 					     GPTZFSBOOT(8)

NAME
gptzfsboot -- GPT bootcode for ZFS on BIOS-based computers DESCRIPTION
gptzfsboot is used on BIOS-based computers to boot from a filesystem in a ZFS pool. gptzfsboot is installed in a freebsd-boot partition of a GPT-partitioned disk with gpart(8). IMPLEMENTATION NOTES
The GPT standard allows a variable number of partitions, but gptzfsboot only boots from tables with 128 partitions or less. BOOTING
gptzfsboot tries to find all ZFS pools that are composed of BIOS-visible hard disks or partitions on them. gptzfsboot looks for ZFS device labels on all visible disks and in discovered supported partitions for all supported partition scheme types. The search starts with the disk from which gptzfsboot itself was loaded. Other disks are probed in BIOS defined order. After a disk is probed and gptzfsboot determines that the whole disk is not a ZFS pool member, the individual partitions are probed in their partition table order. Currently GPT and MBR partition schemes are supported. With the GPT scheme, only partitions of type freebsd-zfs are probed. The first pool seen during probing is used as a default boot pool. The filesystem specified by the bootfs property of the pool is used as a default boot filesystem. If the bootfs property is not set, then the root filesystem of the pool is used as the default. zfsloader(8) is loaded from the boot filesystem. If /boot.config or /boot/config is present in the boot filesystem, boot options are read from it in the same way as boot(8). The ZFS GUIDs of the first successfully probed device and the first detected pool are made available to zfsloader(8) in the vfs.zfs.boot.primary_vdev and vfs.zfs.boot.primary_pool variables. USAGE
Normally gptzfsboot will boot in fully automatic mode. However, like boot(8), it is possible to interrupt the automatic boot process and interact with gptzfsboot through a prompt. gptzfsboot accepts all the options that boot(8) supports. The filesystem specification and the path to zfsloader(8) are different from boot(8). The format is [zfs:pool/filesystem:][/path/to/loader] Both the filesystem and the path can be specified. If only a path is specified, then the default filesystem is used. If only a pool and filesystem are specified, then /boot/zfsloader is used as a path. Additionally, the status command can be used to query information about discovered pools. The output format is similar to that of zpool status (see zpool(8)). The configured or automatically determined ZFS boot filesystem is stored in the zfsloader(8) loaddev variable, and also set as the initial value of the currdev variable. FILES
/boot/gptzfsboot boot code binary /boot.config parameters for the boot block (optional) /boot/config alternative parameters for the boot block (optional) EXAMPLES
gptzfsboot is typically installed in combination with a ``protective MBR'' (see gpart(8)). To install gptzfsboot on the ada0 drive: gpart bootcode -b /boot/pmbr -p /boot/gptzfsboot -i 1 ada0 gptzfsboot can also be installed without the PMBR: gpart bootcode -p /boot/gptzfsboot -i 1 ada0 SEE ALSO
boot.config(5), boot(8), gpart(8), loader(8), zfsloader(8), zpool(8) HISTORY
gptzfsboot appeared in FreeBSD 7.3. AUTHORS
This manual page was written by Andriy Gapon <avg@FreeBSD.org>. BUGS
gptzfsboot looks for ZFS meta-data only in MBR partitions (known on FreeBSD as slices). It does not look into BSD disklabel(8) partitions that are traditionally called partitions. If a disklabel partition happens to be placed so that ZFS meta-data can be found at the fixed off- sets relative to a slice, then gptzfsboot will recognize the partition as a part of a ZFS pool, but this is not guaranteed to happen. BSD
September 15, 2014 BSD
All times are GMT -4. The time now is 01:08 AM.
Unix & Linux Forums Content Copyright 1993-2022. All Rights Reserved.
Privacy Policy