Hot answers tagged

18

That link you posted looks like a very ugly hack type solution. However, according to the man page, gdisk, which is used to convert MBR -> GPT, also has an option in the "recovery & transformation" menu to convert GPT -> MBR; the g key will: Convert GPT into MBR and exit. This option converts as many partitions as possible into MBR form, ...


12

Partprobe calls the BLKRRPART ioctl, which is documented in, err, include/linux/fs.h, and beyond that the kernel source (the meat is in rescan_partitions()): #define BLKRRPART _IO(0x12,95) /* re-read partition table */ The easiest way to find this out is to run strace -e raw=ioctl -e open,ioctl partprobe /dev/sdb. I think what you tried with /sys/*/*...


11

Most of the previous respondents are correct when they say that you can usually do what you need with a GPT partition table layout, but since there are valid reasons for wanting to use MBR, I think I will just answer your question instead of assuming you are wrong for asking. To get rid of the GPT, you need to remember that with this format, there is a ...


8

You can do this like this : parted /dev/sdf --script -- mkpart primary 0 -1


7

Use fdisk for drives that are < 2TB and either parted or gdisk for disk > 2TB. The actual difference has to do with the partitioning formats that these tools are manipulating. For disks < 2TB you're often using MBR (Master Boot Record). For disks > 2TB you're using GPT (GUID Partitioning Table). Here's a good article that covers the differences as ...


6

The extended and logical partitions make sense only with msdos partition table. It's only purpose is to allow you to have more than 4 partitions. With GPT, there are only 'primary' partitions and their number is usually limited to 128 (however, in theory there is no upper limit implied by the disklabel format). Note that on GPT none of the partitions could ...


6

Use the command kpartx to create a loopback device that can then be formatted. kpartx -a /path/to/imagefile.img # Presents partitions from the image file mkfs.vfat /dev/mapper/loop0p1 # Format partition 1 mkfs.ext3 /dev/mapper/loop0p2 # Format partition 2 kpartx -d /path/to/imagefile.img # Unmaps the partitions from the image file Related kpartx ...


6

The primary reason to use gparted or parted is if the new disk is bigger than 2TB. But you probably will not be able to effectively set that up from a 32 bit system. If you want to run the new disk from your old system. Stay with a disk smaller than 2TB. You should be able to partition, format and run that from you old computer using fdisk for partitioning. ...


5

For some reason your kernel fails to read the partition table: [ 8775.030291] end_request: I/O error, dev sdb, sector 0 [ 8775.030300] quiet_error: 30 callbacks suppressed [ 8775.030306] Buffer I/O error on device sdb, logical block 0 [ 8775.033781] ldm_validate_partition_table(): Disk read failed. Thus, it can't create devices for partitions as it did ...


5

The real limitation is that the fdisk tool in the util-linux package doesn't support GPT-type partition tables, which you can find on any disk. However, they're commonly found on disks greater than 2 GiB, because the old MBR-type partition tables don't support sizes that large. The easiest fix is, as the error suggested, to just use the GNU Parted software ...


5

First, make sure you understand the difference between primary, extended and logical partitions. To create a logical partition, you first need to create the extended partition that will contain it. If there's only one partition on a drive, there's no point in not making it primary. Below I'll give instructions for a logical partition; creating a primary ...


5

Parted prompts and goes into an interactive mode when you do not provide enough information to create the partition with the command. The following will create a partition that spans the entire disk and will not prompt for filesystem type: mkpart primary 1 -1


4

I think parted only accepts absolutes, not x+y. You could do it like this: (+ interpreted by shell) # start=1 # size=512 # parted /dev/loop0 unit mib mkpart primary $start $(($start+$size)) # parted /dev/loop0 unit mib print free Model: Loopback device (loopback) Disk /dev/loop0: 1000MiB Sector size (logical/physical): 512B/512B Partition Table: gpt Disk ...


4

In my experience fdisk is more powerful (especially in the advanced mode), but it can leave your disk in a somewhat weird state. For example fdisk will allow your partitions to lie out of order unless you specifically tell it to reorder them, most other tools (and unless i'm very mistaken parted is one of them) will make assumptions that you want everything ...


3

You appear to have both a dos and mac partition table on the disk, and parted is recognizing the mac one. You should be able to zap the mac partition table with: sudo dd if=/dev/zero count=1 bs=2 of=/dev/sda


3

If you have a internet connected to you server, it is very easy: # yum -y install parted


3

This is easy using parted. The -s option is used for scripting. The following produces the same results as your fdisk line: parted -s /dev/sda mkpart primary NTFS 1 24G


3

parted can print free space. Example (I chose a complicated one on purpose): # parted /dev/sda unit s print free [...] Number Start End Size Type File system Flags 63s 2047s 1985s Free Space 1 2048s 4196351s 4194304s primary fat32 lba 4196352s 4198399s 2048s ...


3

You can use the same script logic for parted, but parted has to be invoked via parted -s (don't run interactively). Wheter you can use the exact same commands in your HEREDOC is unknown to me as I don't use parted. Try a manual dry run, note the commands, and put them in the HEREDOC part of your script.


3

You should partition the drive /dev/sda and not the partition /dev/sda1. The message is not really helpful to figure that out.


3

It turns out that I needed to run the following: sudo update-grub This updated my /boot/grub/grub.cfg file and got rid of the windows 7 option.


3

If resizepart does not work, you might have to resort to rm and mkpart to achieve the same thing. Of course, this would require you to parse the partition table first in order to determine partition type and start offset. Unless you already know the necessary values. After all you had to get the 166016512B from somewhere too. parted has the --machine ...


3

It's correct in principle but you might consider reducing it to a single parted call. parted --script /device \ mklabel gpt \ mkpart primary 1MiB 100MiB \ mkpart primary 100MiB 200MiB \ ... Your alignment issue is probably because you use MB instead of MiB. You should not need an actual align-check command when creating partitions on MiB ...


3

It looks at the data on the partition, similar to what file -s /dev/partition does. If you strace it you should see things like this: lseek(3, 1048576, SEEK_SET) = 1048576 read(3, "\353<\220mkfs.fat\0\2\10..., 512) = 512 A seek to position 1048576 (1 MiB or 2048 sectors) is outside the partition table (it's the start of the first partition), and it ...


3

Try to align to eMMC erasure block size. It usually equals 0.5, 1, 2, 4, 8 MiB depending on eMMC datasheet. If you find block size alignment too much memory wasting, then stick to the page size, generally found in the range of 4..16 KiB. Try to make partition sizes and borders a multiple of erasure block size, so when file system writes to the first or last ...


3

You need to print your partition table in parted to see the disk size and available space, then mkpart extended 14029 15564 will create an extended partition starting at 14029MB and ending at 15564MB (adjust both values to suit — I'm basing these on your 13.7GB and 1.5GB figures), and mkpart logical 14030 14542 will create a 512MB logical partition ...


2

Unfortunately, I think you are quite screwed. If you only messed with the partition table then TestDisk is your best shot, but since you have been resizing (which actually means copying and maybe even deleting), your data is, more or less, corrupted. If you have a backup from before performing the resize operation, this is a good time to use it. Else, I don'...


2

Depending in your parted version you can define sizes in percentage. End of your last partition is at 100%.


2

Recent versions of losetup gained -P option. Quote from man 8 losetup: -P, --partscan Force the kernel to scan the partition table on a newly created loop device. Doing losetup -f my_partitioned.img not only creates /dev/loop0, but also partition devices: $ ls -l /dev/loop0* brw-rw---- 1 root disk 7, 0 Oct 5 18:43 /dev/loop0 brw-rw---- 1 ...


2

The filesystem resize ability was long crufty and unmaintained in parted, which is why it was removed in the 3.0 release several years ago. If you update to the latest parted 3.2, it has a resizepart command that only resizes the partition, and you have to use another filesystem specific utility to resize the filesystem within the partition. In the case of ...



Only top voted, non community-wiki answers of a minimum length are eligible