similar to: Command line partition manipulation

Hi all, I am running fedora 11 with kernel 2.6.30.9-102.fc11.x86_64 #1 SMP Fri Dec 4 00:18:53 EST 2009 x86_64 x86_64 x86_64 GNU/Linux. I am noticing a partition on my drive is reporting incorrect size with "df", the partition is ext3 size 204GB with about 79GB actual usage, the "df" result show the partition size to be 111GB, 93GB is missing. Please advice on what

Does anyone know how anaconda partitioning enumerates disk partitions when specified in kickstart? I quickly browsed through the anaconda installer source on github but didn't see the relevant bits. I'm using the centOS 6.10 anaconda installer. Somehow I am ending up with my swap partition on sda1, /boot on sda2, and root on sda3. for $REASONS I want /boot to be the partition #1 (sda1)

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

Hello, sorry for the long email, it's a little hard to explain this issue. The gist of it is that the Ubuntu version of parted allowed me to do something which perhaps should not be allowed i.e. creating partitions on a 2.7TB drive when the partition table is not *gpt* but *msdos*. I am trying to configure 2 identical servers, both are Dell Poweredge 2970 machines with 6 disks in them

Hello, On a VM guest (running under KVM) with CentOS 5.8, I yesterday strangely got the following (see below). The server runs apache/php/squirrelmail/postfix/dovecot/openldap and it is a production server. Do you advise to do some particular file system checks or other settings? Any other advice? Such errors have not appeared in the past. Thanks, Nick System info:

As I understand anaconda uses parted to partition (starting from centos 6), using this as example (kickstart configuration file): clearpart --all --drives=sda --initlabel part /boot --asprimary --size=200 --fstype=ext2 --ondisk=sda part swap --asprimary --size=16384 --fstype=swap --ondisk=sda part / --asprimary --size=512000 --fstype=ext4 --ondisk=sda part /scratch --asprimary --size=1 --grow

Hello..I am not very proficient in Linux kernel stuffs although I know my basics. I have a question and all suggestions/solutions will be highly appreciated... I got to know that RHEL 5 has inbuilt Xen Support...So I tried to install a RHEL 5.0 Server on my P4 machine. On top of it I tried to install Xen specific RPMs and some other RPMs needed by Xen. The additinal RPMs added after base

Ok, I give up... I have to ask. This is CentOS 5. I switched one of my raid1 disks, and I already thought I had succeeded. But now it seems that something is very wrong with the first partition on the new disk. Luckily my system is fully bootable with the other disk. Here's some info. The new disk is sdb. // I removed all partitions with parted, and created the first one again. // parted

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

I have Windows 7 on /dev/sda and CentOS 6.4 on /dev/sdb. Here are the layouts: (parted) select /dev/sda Using /dev/sda (parted) print Model: ATA WDC WD10EZEX-00Z (scsi) Disk /dev/sda: 1000GB Sector size (logical/physical): 512B/4096B Partition Table: msdos Number Start End Size Type File system Flags 1 1049kB 374MB 373MB primary ntfs boot

I am experimenting with KVM and I wish to create a virtual machine image in a logical volume. I can create the new lv without problem but when I go to format its file system then I get these warnings: Warning: WARNING: the kernel failed to re-read the partition table on /dev/sda (Device or resource busy). As a result, it may not reflect all of your changes until after reboot. Warning: Unable to

Good day, Gparted is not available on my installation. Which patition tool is available in centos 5.5 please. Thanks Johan

(I've already sent this message to Ted Ts'o directly. I should have sent it to this list first but I didn't know about it until today. My apologies to Ted.) Last Friday a system that I just inherited refused to mount a file system that had been working fine for about 6 months. This is on a Scientific Linux 4.3 system using a 2.6.9 kernel. This is another Linux distribution based on

-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 I installed centos4 on a raid system with 7 400GB Hitachi SATA disks in RAID 5 on the 3Ware card. I set up a 2.2TB EXT3 Partition /opt. After the install I rebooted and the system went straight into maintenance mode....! The system reported a problem with /opt, but I was able to mount it manually and init 4 with no problems. However a reboot dropped

Hello. A couple of years ago I installed two file-servers using kickstart. The server has two 1TB sata disks with two software raid1 partitions as follows: # cat /proc/mdstat Personalities : [raid1] md1 : active raid1 sdb4[1] sda4[0] 933448704 blocks [2/2] [UU] md0 : active raid1 sdb1[1] sda2[2](F) 40957568 blocks [2/1] [_U] Now the drives are starting to be failing and next week

RHEL 5's old parted didn't have the -m option. A number of commands relied on this option and thus would break on RHEL 5: https://bugzilla.redhat.com/show_bug.cgi?id=598309 This rather large patch adds a second parsing path which allows us to parse the old text-based output (it preserves the code for parsing the output of the -m option too, since if supported, that is more accurate).

Hello,I receive strange error ><fs> part-init /dev/vda bsd ><fs> part-add /dev/vda primary 64 -1 libguestfs: error: part_add: do_part_add: parted: /dev/vda: parted: invalid token: primary Error: Expecting a file system type. but ><fs> part-init /dev/vda msdos ><fs> part-add /dev/vda primary 64 -1 runs ok Log attached. -- Nikita A Menkovich

On Thu, May 28, 2020 19:38, Robert Nichols wrote: > What output do you get from: > > file -s /dev/mapper/vg_voinet01-lv_log > lsblk -f /dev/mapper/vg_voinet01-lv_log > file -s /dev/mapper/vg_voinet01-lv_log /dev/mapper/vg_voinet01-lv_log: symbolic link TO '../DM-5' dm-f lsblk -f /dev/mapper/vg_voinet01-lv_log NAME FSTYPE LABEL UUID

Hi, altmbr.bin and its variants apparently always boot the first partition (in Syslinux 4.05, but this issue seems older than that). The following example uses parted 3.0: ---------- rm -f flat mkdir mnt truncate -s 20M flat parted -s flat mklabel msdos mkpart primary fat32 1MiB 10485759B mkpart primary ext2 11MiB 100% unit KiB print losetup -o 1048576 -s 9437184 /dev/loop7 flat mkdosfs

Hello, After repeated failing efforts to restore CentOS 7 backups (taken using mondorescue software), I have found that all my CentOS 7 installations (VMs under KVM) have the same /boot/grub2/device.map, which seemingly refers to two HDs, although the VMs in fact include only one (virtual) HD. For example: /boot/grub2/device.map # this device map was generated by anaconda (hd0)