search for: gdisk

I followed the instructions here for enabling EHEL: http://www.thegeekstuff.com/2012/06/enable-epel-repository/ And tried to do a yum gdisk install on a new CentOS 6.2 fully updated install. yum install gdisk Loaded plugins: fastestmirror, security Loading mirror speeds from cached hostfile * base: mirror.flhsi.com * epel: www.gtlib.gatech.edu * extras: mirror.us.leaseweb.net * rpmforge: mirror.us.leaseweb.net * updates: mirrors.final...

...le '/usr/share/syslinux/isohdpfx.bin' libisofs: NOTE : Aligned image size to cylinder size by 80 blocks xorriso : UPDATE : 40.00% done ISO image produced: 20480 sectors Written to medium : 20480 sectors at LBA 0 Writing to 'stdio:../image.iso' completed successfully. * output from gdisk -l image.iso showing both MBR and GPT layouts # gdisk -l ../image.iso GPT fdisk (gdisk) version 0.8.6 Partition table scan: MBR: MBR only BSD: not present APM: not present GPT: present Found valid MBR and GPT. Which do you want to use? 1 - MBR 2 - GPT 3 - Create blank GPT Your answer...

part-expand-gpt takes extreme cautions and doesn't proceed to writing to the disk if the preliminary dry run of sgdisk has generated any warnings on stdout. This blocks the use of part-expand-gpt on disk shrink (with disk resize being the main usecase for part-expand-gpt), because sgdisk dry run produces a warning in that case. So remove the excessive safety check, and leave it up to the caller. Signed-off-by: D...

...g to have type FD00 (Linux RAID) whereas EFI firmware >> expects >> type EF00 (EFI System Partition) to boot from. > > > I think you're referring to MBR partition types.? I'm not certain, but I > don't see those values in a GPT. No, it's GPT. What does "gdisk -l /dev/sda" show? That would be interesting to see. > > >> EFI then reads the GPT table directly and looks for a vfat filesystem to >> boot from. Default Linux software RAID1 on EL7 uses metadata 1.2 which >> located at the beginning of the partition. EFI won't re...

Hi, I have a 24TB RAID6 disk with a GPT partition table on it. I need to partition it into 2 partitions one of 16TB and 1 of 8TB to put ext4 filesystems on both. But I really need to do this remotely. ( if I can get to the site I could use gparted ) Now fdisk doesn't understand GPT partition tables and pat

I posted this on the bugzilla page but I figured that on the mailing list it would get more attention. Please see http://bugzilla.syslinux.org/show_bug.cgi?id=49 for a description of my current issue. -- Thank you, Fernando Reyes GPG BDD75DD7 Mission Accomplish, Inc. http://missionaccomplish.com Email:design at missionaccomplish.com Tel: 7187100008 Cell: 3479275477

Hi, I'm currently teaching Linux system administration to a class at the local "chambre de commerce". The course is based mainly on a minimal CentOS 7 installation. Usually my preferred tool for handling manual GPT partitioning is gdisk, which is not installed on a minimal install. I just gave the good old fdisk a spin, which enables GPT partition table creation with the 'g' shortcut. Here's what I get when listing a GPT-partitioned drive with fdisk: # fdisk -l /dev/sdb WARNING: fdisk GPT support is currently new, an...

...tition > labelled > > "xyz"". > > > > So nothing related to filesystem but gpt labels & disks. > > > > > For comparison - option "label" - GPT Partition name selection, > working as expected > > SeaBIOS / SYSLINUX > > # gdisk -l /dev/vdc > ... > Partition table scan: > MBR: protective > BSD: not present > APM: not present > GPT: present > > Found valid GPT with protective MBR; using GPT. > Disk /dev/vdc: ... > ... > Number Start (sector) End (sector) Size Code Name &g...

...; >>> the gpt partitions label. > >>> > >>> > >>> Please find below the commit : > >>> > https://github.com/ErwanAliasr1/syslinux/commit/ebf8cbfb8cef49517aa36b4a79998b4332289489 > >>> > >> > >> > >> # gdisk -l /dev/vda > >> ... > >> Partition table scan: > >> MBR: protective > >> BSD: not present > >> APM: not present > >> GPT: present > >> > >> Found valid GPT with protective MBR; using GPT. > >> ... > >&gt...

...t.img' , platform_id=0xEF Boot image : '/boot/macboot.img' , platform_id=0xEF TOC layout : Idx , sbsector , Size , Volume Id ISO session : 1 , 0 , 20992s , EUFI-TESTING Media summary: 1 session, 20992 data blocks, 41.0m data, 33.9g free Media nwa : 20992s # gdisk -l uefi-testing.iso GPT fdisk (gdisk) version 0.8.6 Partition table scan: MBR: MBR only BSD: not present APM: not present GPT: present Found valid MBR and GPT. Which do you want to use? 1 - MBR 2 - GPT 3 - Create blank GPT Your answer: 1 Entering GPTPart::SetName(const UnicodeString.....

...ce/packagelist.in | 13 ++++++++----- 1 file changed, 8 insertions(+), 5 deletions(-) diff --git a/appliance/packagelist.in b/appliance/packagelist.in index 8a4a5ea..a00a7ad 100644 --- a/appliance/packagelist.in +++ b/appliance/packagelist.in @@ -126,11 +126,9 @@ dosfstools file findutils gawk -gdisk grep gzip jfsutils -kmod less libxml2 lsof @@ -146,17 +144,14 @@ ocfs2-tools */ parted procps -procps-ng psmisc rsync -scrub sed strace syslinux tar udev util-linux -util-linux-ng #ifndef UBUNTU /* on Ubuntu contains a file in /lib64 which conflicts with libc6 that has * /lib64...

...do believe isohybrid --gpt --mac is buggy, and it should not be necessary to be applied to a xorriso generated image that used -isohybrid-mbr for the BIOS image, and -isohybrid-gpt-basdat -isohybrid-apm-hfsplus for the EFI and the MAC boot image. Just try to boot it as it comes out of xorriso. [gdisk GPT report after applying isohybrid --gpt --mac :] > 2 42552 52615 4.9 MiB 0700 [8-bit salad] > 3 2232 42551 19.7 MiB AF00 [8-bit salad] > ok, I don't know what that garble text is above. This is the most obvious one of the bu...

Ok, did some experiments. Here's the scoop. You will need a live USB key of CentOS 6 with a persistence layer (overlay) and the EPEL gdisk package installed to make this thing boot. On a system with Chameleon already installed, boot the CentOS 6 install media. Installing Chameleon without OSX is an adventure that I've not done, so a 'testing' OSX install (10.6) with the Chameleon bootloader installed was used; once Chame...

...way I can tell "please boot the disk that have one partition labelled > "xyz"". > > So nothing related to filesystem but gpt labels & disks. > For comparison - option "label" - GPT Partition name selection, working as expected SeaBIOS / SYSLINUX # gdisk -l /dev/vdc ... Partition table scan: MBR: protective BSD: not present APM: not present GPT: present Found valid GPT with protective MBR; using GPT. Disk /dev/vdc: ... ... Number Start (sector) End (sector) Size Code Name 1 2048 6143 2.0 MiB EF02...

...s my default and one of my submenu files: default: #Projekt PXE-Boot von Franz Lang www.franz-lang.com DEFAULT menu.c32 PROMPT 0 IMPLICIT 1 ALLOWOPTIONS 0 MENU TITLE Auswahlmenue LABEL dos MENU LABEL ^1: DOS Booten Menu DEFAULT KERNEL memdiskg append initrd=images/sonstiges/dos622.img LABEL gdisk MENU Label ^2: Gdisk starten kernel memdiskg append initrd=images/sonstiges/gdisk.img LABEL bootmenue MENU LABEL ^3: Bootmenue v3.3 KERNEL memdiskg append initrd=images/sonstiges/bootmenue.img LABEL biosmenue MENU Label ^4: BIOS Updates KERNEL menu.c32 append biosmenue.conf LABEL raidmenu MENU...

...... > <target dev='vdc' bus='virtio'/> > <boot order='3'/> > ... > ... > <target dev='vdd' bus='virtio'/> > <boot order='4'/> > ... > ... > > > # gdisk -l /dev/vdc > ... > Partition table scan: > MBR: protective > BSD: not present > APM: not present > GPT: present > > Found valid GPT with protective MBR; using GPT. > Disk /dev/vdc: ... > ... > Number Start (sector) End (sector) Size Code Name &...

...t;". >> > >> > So nothing related to filesystem but gpt labels & disks. >> > >> >> >> For comparison - option "label" - GPT Partition name selection, >> working as expected >> >> SeaBIOS / SYSLINUX >> >> # gdisk -l /dev/vdc >> ... >> Partition table scan: >> MBR: protective >> BSD: not present >> APM: not present >> GPT: present >> >> Found valid GPT with protective MBR; using GPT. >> Disk /dev/vdc: ... >> ... >> Number Start (secto...

...fail.mp4> How I fixed the problem by downgrading to Syslinux 4.06 and how booting should look like (6.5 MB): <https://www.dropbox.com/s/lt7cpgfm0qvqtba/boot-syslinux5-how-i-fixed-it.mp4> System configuration: ===================== The system has two disks. Partitioned like: testVM ~ # gdisk -l /dev/sda GPT fdisk (gdisk) version 0.8.5 Partition table scan: MBR: protective BSD: not present APM: not present GPT: present Found valid GPT with protective MBR; using GPT. Disk /dev/sda: 41943040 sectors, 20.0 GiB Logical sector size: 512 bytes Disk identifier (GUID): 63DE1BD4-4135-4...

...boot, kernel and initramfs correctly results in a ISO image that is bootable on BIOS and UEFI systems if booted from the optical drive. However, when I run isohybrid --uefi name-of.iso the resulting GPT entry for the EF00 partition is just 19MB. It should be around 53MB: root at barium:/tmp# gdisk -l lesslinux-search-and-rescue-uluru-20130312-110347.iso GPT fdisk (gdisk) version 0.8.5 Partition table scan: MBR: MBR only BSD: not present APM: not present GPT: present Found valid MBR and GPT. Which do you want to use? 1 - MBR 2 - GPT 3 - Create blank GPT Your answer: 2 Using GPT and creati...

Hello listmates, Here's I am, trying to install Centos 6.2 64-bit on a server with 24 TB of disk RAIDed as RAID 6. So I get this 18 TB disk (the RAID is recognized as one disk) where I am trying to put my OS. And I can create a couple of partitions - let us say I defiine a 150 GB swap, a 150 GB "/", a 100 GB "/var". So far so good. Then I try to define the next one, say, a