similar to: CentOS or upstream bug in parted

Ken Smith wrote: > > Hi All, Slightly OT as this is on a Centos 6 system > Not at all OT. We started using parted when we started using 3TB drives a few years ago, since fdisk can't handle > 2TB. > I'm getting the fdisk message "partition does not start on a physical > sector boundary" on a 4096 sector disk. I understand why this has > happened. > > I

On 2/27/2015 3:06 PM, m.roth at 5-cent.us wrote: > Alignment's easy: using parted (the user-hostile program), if you do go in > with parted -a optimal /dev/drive, and do > mkpart pri ext4 0.0GB 100% (for non-root drives, for example), it's > aligned correctly. i found -a optimal to do weird things, and almost always complain. I just use -a none now, and specify partition

I swear I've done this dozens of times: a new server, going to install (CentOS 7, in this case), and I manually partition the disk before the install using parted, and do mkpart pri 0.0GB +1.0GB Except now it appears to be saying it doesn't like the +1.0GB, I *think* it's the plus sign. mark

Chris Murphy wrote: <snip> > The emulation implementations don't come into play if the alignment is > correct from the start. The better implementations have significantly > less pathological behavior if alignment is wrong, but that's > anecdotal, I don't have any empirical data available. But I'd say in > any case you want it properly aligned. You really,

OK todays problem. I have a HP N54L Microserver running centos 6.5. In this box I have a 3x2TB disk raid 5 array, which I am in the process of extending to a 4x2TB raid 5 array. I've added the new disk --> mdadm --add /dev/md0 /dev/sdb And grown the array --> mdadm --grow /dev/md0 --raid-devices=4 Now the problem the resync speed is v slow, it refuses to rise above 5MB, in general

[Following up on this thread: http://thread.gmane.org/gmane.linux.kernel.device-mapper.devel/14999] Alasdair G Kergon wrote: > Try > blkdev --flushbufs > after any cmd that writes to a dev to see if that makes any difference. Thanks for the work-around. Using "blockdev --flushbufs $dev" does indeed make parted behave the same with dm-backed storage as with other devices.

we have CENTOS 5.5 on X86. I tried to create a "raw partition" (NOT FS) on a disk and it continue to show "ext3". How can I get ride of it? === procedures===== # parted /dev/sde GNU Parted 1.8.1 Using /dev/sde Welcome to GNU Parted! Type 'help' to view a list of commands. (parted) p Model: DELL PERC

I don't know if this additional information helps. Looking at he efibootmgr output, is the centos entry pointing to the right place? Also, any idea why the update isn't being make permenant? [root at localhost boot]# parted GNU Parted 3.1 Using /dev/sda Welcome to GNU Parted! Type 'help' to view a list of commands. (parted) print

On 4/9/2015 5:22 PM, Chuck Campbell wrote: > Subject says it. > > I would like to find out if I have anything written on the MBR of a > disk in my system /dev/sda, or any other device. > If there is something there, is it readable, or recognizable to humans? the MBR contains both binary boot code, which is not human readable, and the master partiion table for the device. you can

Hi messmer, seems that anaconda supports partitioned RAID devices. Disk selection see one mdraid device and permits to create partition on it. Il 13/03/2016 01:04, Gordon Messmer ha scritto: > On 03/12/2016 08:22 AM, Alessandro Baggi wrote: >> From several how-to concerning raid1 installation, I must put each >> partition on a different md devices. > > Not necessarily. You

I have a large raid (lsi megaraid sas2 9261-8i card) and when I use parted to initialize it as the one big partition I want, it gives me a warning. # parted /dev/sda "mklabel gpt" Warning: The existing disk label on /dev/sda will be destroyed and all data on this disk will be lost. Do you want to continue? Yes/No? yes # parted -a optimal /dev/sda

On 03/12/2016 08:22 AM, Alessandro Baggi wrote: > From several how-to concerning raid1 installation, I must put each > partition on a different md devices. Not necessarily. You could put LVM on top of the RAID device, and create logical volumes. > I've asked times ago if it's more correct create the md device, > partitioning it and create fs on each partition created on

Hi list, I'm new with UEFI and GPT. For several years I've used MBR partition table. I've installed my system on software raid1 (mdadm) using md0(sda1,sdb1) for swap, md1(sda2, sdb2) for /, md2 (sda3,sdb3) for /home. From several how-to concerning raid1 installation, I must put each partition on a different md devices. I've asked times ago if it's more correct create the

Hi All, I have a Drobo, connected to a CentOS 6.4 box. The box sees it as /dev/sdg. I want to format it ext3 (as they dont support ext4) but when I try I get: # fdisk -u /dev/sdg WARNING: GPT (GUID Partition Table) detected on '/dev/sdg'! The util fdisk doesn't support GPT. Use GNU Parted. WARNING: The size of this disk is 17.6 TB (17592186044416 bytes). DOS partition table

--- scripts/ovirt-config-boot | 13 +++++- scripts/ovirt-config-storage | 111 ++++++++++++++++++++++++------------------ 2 files changed, 75 insertions(+), 49 deletions(-) diff --git a/scripts/ovirt-config-boot b/scripts/ovirt-config-boot index d545878..8cc127b 100755 --- a/scripts/ovirt-config-boot +++ b/scripts/ovirt-config-boot @@ -29,6 +29,12 @@ ovirt_boot_setup() { local disk2

On Tuesday 28 May 2019 19:52:02 Jonathan Billings wrote: > I suggest running 'blkid' and 'efibootmgr -v', and double-check that > the UUID for the CentOS boot entry matches the UUID of the EFI disk. > > You can delete and recreate the boot entry with 'efibootmgr', which > will likely solve the problem. > > It depends on the UEFI implementation, but

hi to the list, Hello everyone, I am new in the world of pxe booting and i try to use AOE to boot my linux debian lenny machines. I install the linux like this: parted -s /dev/etherd/e10.1 mklabel gpt parted -s /dev/etherd/e10.1 mklabel gpt parted -s /dev/etherd/e10.1 mkpart primary ext3 17408B 314590207B parted -s /dev/etherd/e10.1 mkpart primary ext3 314590208B 3535815679B parted -s

Hi All, Slightly OT as this is on a Centos 6 system I'm getting the fdisk message "partition does not start on a physical sector boundary" on a 4096 sector disk. I understand why this has happened. I just want to be sure of my parted syntax before I really mess things up. (before anyone says it - I know - do a backup) parted says that the offending partition 5 begins at 512 byte

This patch introduces the concept of an "Advanced Storage Configuration", specifically for automated installs (although it could be hooked into manual install), while preserving the original style of specifying LVs. It accomplishes the following: * Add an optional AppVG * Offer new optional LVs - Data2,Swap2 - as part of the new AppVG * Allows the specification of multiple disks, per VG

--- scripts/ovirt-config-boot | 13 +++++++- scripts/ovirt-config-storage | 73 +++++++++++++++++++++++++---------------- 2 files changed, 56 insertions(+), 30 deletions(-) diff --git a/scripts/ovirt-config-boot b/scripts/ovirt-config-boot index d545878..8cc127b 100755 --- a/scripts/ovirt-config-boot +++ b/scripts/ovirt-config-boot @@ -29,6 +29,12 @@ ovirt_boot_setup() { local disk2