search for: partiitons

hello. had a bad day yesterday: accidentally, the first 0.5% to 1% of my ext3 partition got overwritten, can't gauge it more exactly. Geography of the partition is: size ~100 GB. block size should be 4096. => deleted are averages to 500mb - 1gb still. I don't think it is relevant, but the device itself is /dev/loop0, because there is a cryptoloop layer between the device and the

...4 MB/s bs=512 164 MB/s (dd's default bs size) bs=1k 276 MB/s bs=2k 567 MB/s bs=4k 717 MB/s bs=8k 938 MB/s bs=16k 988 MB/s bs=32k 1.1 GB/s bs=64k 1.1 GB/s bs=128k 1.2 GB/s <-- we want to be here bs=256K 1.2 GB/s bs=512K 1.2 GB/s Test 5: Finally, a dd write of the iso to the raid partiitons from a ram drive to show the raids can write at gigabyte speeds: dd if=/tmp/ram1/Fedora-Live-Desktop.iso of=/data1/iso bs=<value> bs=512 70.6 MB/s bs=1K 137 MB/s bs=2K 271 MB/s bs=4K 472 MB/s bs=8K 804 MB/s bs=16K 1.2 GB/s bs=32K 1.7 GB/s bs=64K 2.0 GB/s bs=128k 2.9 GB/s bs=256K...

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)