search for: partiiton

...perly anyway, so it shouldn't matter (should it?). When i try to mount: EXT3-fs error: ext3_check_descriptors: block bitmap for group 0 not in group (block (block 152615462) EXT3-fs: group descriptors corrupted. of course i tried e2fsck (v 1.27), but it said it could not see an ext3 on the partiiton and suggested to try another superblock (here: 8193). hopes surging, but bad luck, because block 8193 is also within the deleted area. My question therefore is, if there are any (backup) superblocks on an arbitrary ext3 partiiton which i could access to recover some data at least. I tried the form...

...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=256...

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)