On Mon, Oct 12, 2015 at 10:34 AM, Nico Kadel-Garcia <[log in to unmask]> wrote: > On Mon, Oct 12, 2015 at 10:14 AM, Ken Teh <[log in to unmask]> wrote: >> >> I'm having problems with an 6.7 install. Here are the relevant lines: >> >> # partitions >> >> # clearpart --drives=disk/by-id/ata-SATA_SSD_96D70756062400160297 >> part /boot --fstype=ext4 --size=1024 --asprimary >> --ondisk=disk/by-id/ata-SATA_SSD_96D70756062400160297 >> part pv.01 --size=1 --grow --asprimary >> --ondisk=disk/by-id/ata-SATA_SSD_96D70756062400160297 >> >> volgroup sysvg pv.01 >> logvol swap --fstype=swap --vgname=svsvg --size=12288 --name=swap >> logvol / --fstype=ext4 --vgname=sysvg --size=1 --grow --name=root > >> Kickstart stops trying to create the swap logical volume. Claims there is >> no such sysvg volume. I did an alt-F2 and ran parted on the disk. The >> 'part' command never created the partitions. This is my first time using >> the 'disk/by-id/...' syntax. Also, first time with an SSD disk. I checked >> /dev/disk/by-id and the disk is listed with the correct id. > > Don't hurt yourself. That "disk-by-id" or using UUID, is not stable. disk-by-id is based on a disk's model and serial so it's stable for a given disk. From my laptop: # ll /dev/disk/by-id/ total 0 lrwxrwxrwx 1 root root 9 2015-10-12 13:02 ata-SAMSUNG_MZMTE256HMHP-000L1_S1G4NYAF624379 -> ../../sda lrwxrwxrwx 1 root root 10 2015-10-12 13:02 ata-SAMSUNG_MZMTE256HMHP-000L1_S1G4NYAF624379-part1 -> ../../sda1 lrwxrwxrwx 1 root root 10 2015-10-12 13:02 ata-SAMSUNG_MZMTE256HMHP-000L1_S1G4NYAF624379-part2 -> ../../sda2 lrwxrwxrwx 1 root root 9 2015-10-12 13:02 wwn-0x5002538844584d30 -> ../../sda lrwxrwxrwx 1 root root 10 2015-10-12 13:02 wwn-0x5002538844584d30-part1 -> ../../sda1 lrwxrwxrwx 1 root root 10 2015-10-12 13:02 wwn-0x5002538844584d30-part2 -> ../../sda2 # lsblk -l -o NAME,FSTYPE,MODEL,SERIAL,WWN,MOUNTPOINT /dev/sda NAME FSTYPE MODEL SERIAL WWN MOUNTPOINT sda SAMSUNG MZMTE256 S1G4NYAF624379 0x5002538844584d30 sda1 vfat 0x5002538844584d30 sda2 ext4 0x5002538844584d30 /