From anders.blomdell at control.lth.se Mon Jan 12 11:01:28 2015 From: anders.blomdell at control.lth.se (Anders Blomdell) Date: Mon, 12 Jan 2015 12:01:28 +0100 Subject: What is the way to specify a RAID by uuid in Fedora-21? Message-ID: <54B3A988.5080300@control.lth.se> In previous versions, I could specify it with: raid /boot --device=UUID=34206d90:7e6a035e:8660b1b3:62cca315 --fstype=ext4 --label=/boot --useexisting that does not work in F-21, neither does: raid /boot --device=/dev/disk/by-id/md-uuid-34206d90:7e6a035e:8660b1b3:62cca315 --fstype=ext4 --label=/boot --useexisting which fails with: RAID volume "/dev/disk/by-id/md-uuid-34206d90:7e6a035e:8660b1b3:62cca315" specified with --useexisting does not exist. even though storage.log contains: 10:43:01,654 DEBUG blivet: DeviceTree.addUdevDevice: info: {'DEVLINKS': '/dev/disk/by-id/md-uuid-34206d90:7e6a035e:8660b1b3:62cca315 /dev/disk/by-label/\\x2fboot /dev/disk/by-uuid/2b1ad073-26ff-44ae-8adf-1a13990d0dbc /dev/md/0', 'DEVNAME': 'md0', 'DEVPATH': '/devices/virtual/block/md0', 'DEVTYPE': 'disk', 'DM_MULTIPATH_TIMESTAMP': '1421059320', 'ID_FS_LABEL': '/boot', 'ID_FS_LABEL_ENC': '\\x2fboot', 'ID_FS_TYPE': 'ext4', 'ID_FS_USAGE': 'filesystem', 'ID_FS_UUID': '2b1ad073-26ff-44ae-8adf-1a13990d0dbc', 'ID_FS_UUID_ENC': '2b1ad073-26ff-44ae-8adf-1a13990d0dbc', 'ID_FS_VERSION': '1.0', 'MAJOR': '9', 'MD_DEVICES': '2', 'MD_DEVICE_vda1_DEV': '/dev/vda1', 'MD_DEVICE_vda1_ROLE': '0', 'MD_DEVICE_vdb1_DEV': '/dev/vdb1', 'MD_DEVICE_vdb1_ROLE': '1', 'MD_DEVNAME': '0', 'MD_LEVEL': 'raid1', 'MD_METADATA': '0.90', 'MD_UUID': '34206d90:7e6a035e:8660b1b3:62cca315', 'MINOR': '0', 'MPATH_SBIN_PATH': '/sbin', 'SUBSYSTEM': 'block', 'SYSTEMD_WANTS': 'mdmonitor.service', 'TAGS': ':systemd:', 'USEC_INITIALIZED': '16422', 'name': 'md0', 'symlinks': ['/dev/disk/by-id/md-uuid-34206d90:7e6a035e:8660b1b3:62cca315', '/dev/disk/by-label/\\x2fboot', '/dev/disk/by-uuid/2b1ad073-26ff-44ae-8adf-1a13990d0dbc', '/dev/md/0'], 'sysfs_path': '/devices/virtual/block/md0'} ; name: md0 ; 10:43:01,655 INFO blivet: scanning md0 (/devices/virtual/block/md0)... 10:43:01,656 DEBUG blivet: DeviceTree.getDeviceByName: hidden: False ; name: md0 ; incomplete: False ; 10:43:01,657 DEBUG blivet: DeviceTree.getDeviceByName returned None 10:43:01,658 DEBUG blivet: DeviceTree.getDeviceByName: hidden: False ; name: 0 ; incomplete: False ; 10:43:01,660 DEBUG blivet: existing RAID raid1 size == 1023.94 MiB 10:43:01,659 DEBUG blivet: DeviceTree.getDeviceByName returned existing 1023.94 MiB mdarray 0 (10) 10:43:01,675 DEBUG blivet: existing RAID raid1 size == 1023.94 MiB 10:43:01,690 DEBUG blivet: existing RAID raid1 size == 1023.94 MiB 10:43:01,714 DEBUG blivet: existing RAID raid1 size == 1023.94 MiB 10:43:01,705 INFO blivet: got device: MDRaidArrayDevice instance (0x7f125366fe10) -- name = 0 status = True kids = 0 id = 10 parents = ['existing 1024 MiB partition vda1 (6) with existing mdmember', 'existing 1024 MiB partition vdb1 (27) with existing mdmember'] uuid = 34206d90-7e6a-035e-8660-b1b362cca315 size = 1023.94 MiB format = existing None major = 0 minor = 0 exists = True protected = False sysfs path = /devices/virtual/block/md0 partedDevice = parted.Device instance -- model: Linux Software RAID Array path: /dev/md/0 type: 17 sectorSize: 512 physicalSectorSize: 512 length: 2097024 openCount: 0 readOnly: False externalMode: False dirty: False bootDirty: False host: 13107 did: 13107 busy: False hardwareGeometry: (262128, 2, 4) biosGeometry: (130, 255, 63) PedDevice: <_ped.Device object at 0x7f1258a907a0> target size = 0 B path = /dev/md/0 format args = [] originalFormat = None level = raid1 spares = 0 members = 2 total devices = 2 metadata version = 0.90 10:43:01,738 DEBUG blivet: existing RAID raid1 size == 1023.94 MiB 10:43:01,762 DEBUG blivet: existing RAID raid1 size == 1023.94 MiB 10:43:01,786 DEBUG blivet: existing RAID raid1 size == 1023.94 MiB Anybody that could give some useful pointers? Regards Anders Blomdell -- Anders Blomdell Email: anders.blomdell at control.lth.se Department of Automatic Control Lund University Phone: +46 46 222 4625 P.O. Box 118 Fax: +46 46 138118 SE-221 00 Lund, Sweden From adam.huffman at gmail.com Mon Jan 12 15:05:10 2015 From: adam.huffman at gmail.com (Adam Huffman) Date: Mon, 12 Jan 2015 15:05:10 +0000 Subject: Disable user creation? Message-ID: I'm testing RHEL 7 kickstart, and it's forcing me to create a user account. Is there a way of disabling that behaviour? Best Wishes, Adam From dshea at redhat.com Mon Jan 12 15:29:14 2015 From: dshea at redhat.com (David Shea) Date: Mon, 12 Jan 2015 10:29:14 -0500 Subject: Disable user creation? In-Reply-To: References: Message-ID: <54B3E84A.6040705@redhat.com> On 01/12/2015 10:05 AM, Adam Huffman wrote: > I'm testing RHEL 7 kickstart, and it's forcing me to create a user account. > > Is there a way of disabling that behaviour? > > Best Wishes, > Adam > > _______________________________________________ > Kickstart-list mailing list > Kickstart-list at redhat.com > https://www.redhat.com/mailman/listinfo/kickstart-list Set a (unlocked) root password with rootpw. This is understandably an issue for situations where you want neither root nor a user, such as cloud images, but it can be fixed by running 'passwd -l root' in %post. From anders.blomdell at control.lth.se Mon Jan 12 15:32:54 2015 From: anders.blomdell at control.lth.se (Anders Blomdell) Date: Mon, 12 Jan 2015 16:32:54 +0100 Subject: What is the way to specify a RAID by uuid in Fedora-21? In-Reply-To: <54B3A988.5080300@control.lth.se> References: <54B3A988.5080300@control.lth.se> Message-ID: <54B3E926.4000706@control.lth.se> On 2015-01-12 12:01, Anders Blomdell wrote: > In previous versions, I could specify it with: > > raid /boot --device=UUID=34206d90:7e6a035e:8660b1b3:62cca315 --fstype=ext4 --label=/boot --useexisting after some digging around with blivet/devictree.py, changing the UUID to: raid /boot --device=UUID=34206d90-7e6a-035e-8660-b1b362cca315 --fstype=ext4 --label=/boot --useexisting seems to fix that issue... Regards Anders -- Anders Blomdell Email: anders.blomdell at control.lth.se Department of Automatic Control Lund University Phone: +46 46 222 4625 P.O. Box 118 Fax: +46 46 138118 SE-221 00 Lund, Sweden From adam.huffman at gmail.com Mon Jan 12 15:51:22 2015 From: adam.huffman at gmail.com (Adam Huffman) Date: Mon, 12 Jan 2015 15:51:22 +0000 Subject: Disable user creation? In-Reply-To: <54B3E84A.6040705@redhat.com> References: <54B3E84A.6040705@redhat.com> Message-ID: Yes, I've found an equivalent workaround by setting a root password beginning with *. Thanks, Adam On Mon, Jan 12, 2015 at 3:29 PM, David Shea wrote: > On 01/12/2015 10:05 AM, Adam Huffman wrote: >> >> I'm testing RHEL 7 kickstart, and it's forcing me to create a user >> account. >> >> Is there a way of disabling that behaviour? >> >> Best Wishes, >> Adam >> >> _______________________________________________ >> Kickstart-list mailing list >> Kickstart-list at redhat.com >> https://www.redhat.com/mailman/listinfo/kickstart-list > > > Set a (unlocked) root password with rootpw. This is understandably an issue > for situations where you want neither root nor a user, such as cloud images, > but it can be fixed by running 'passwd -l root' in %post. > > _______________________________________________ > Kickstart-list mailing list > Kickstart-list at redhat.com > https://www.redhat.com/mailman/listinfo/kickstart-list From simpsonar77 at gmail.com Thu Jan 29 13:48:04 2015 From: simpsonar77 at gmail.com (Andrew Simpson) Date: Thu, 29 Jan 2015 08:48:04 -0500 Subject: help with creating USB kickstart drive RHEL 6.5 Message-ID: I have a complicated kickstart based install that I have been using with DVDs. I Would like to use USB drives, but I have a few questions that I haven't gotten answers to yet. 1. what's the best way to create a bootable USB key/drive? I have been using dd to put the ISO onto the device, but that makes the usb drive a read only filesystem (iso9660). I would really like it to be writable. So I'm assuming I will need to format the drive, put an mbr on there, etc...? 2. what kickstart install option should I be using? normally, I put "cdrom" in. Do I have to change that to the "harddrive" option? 3. Is there a good reference for turning a dvd image into a live image? thanks in advance, the information on these topics is all over the place and I'm not finding exactly what I need. Drew -------------- next part -------------- An HTML attachment was scrubbed... URL: From spikewhitetx at gmail.com Fri Jan 30 01:15:32 2015 From: spikewhitetx at gmail.com (Spike White) Date: Thu, 29 Jan 2015 19:15:32 -0600 Subject: help with creating USB kickstart drive RHEL 6.5 (Andrew Simpson) Message-ID: > > From: Andrew Simpson > To: kickstart-list at redhat.com > Cc: > Date: Thu, 29 Jan 2015 08:48:04 -0500 > Subject: help with creating USB kickstart drive RHEL 6.5 > I have a complicated kickstart based install that I have been using with DVDs. I Would like to use USB drives, but I have a few questions that I haven't gotten answers to yet. > > 1. what's the best way to create a bootable USB key/drive? I have been using dd to put the ISO onto the device, but that makes the usb drive a read only filesystem (iso9660). I would really like it to be writable. So I'm assuming I will need to format the drive, put an mbr on there, etc...? > > 2. what kickstart install option should I be using? normally, I put "cdrom" in. Do I have to change that to the "harddrive" option? > > 3. Is there a good reference for turning a dvd image into a live image? > > thanks in advance, the information on these topics is all over the place and I'm not finding exactly what I need. > > Drew Drew, it really depends on what you want to do. What I do is stage all my build content on the network. So my USB image has syslinux, vmlinuz, initramfs and my ks.cfg. I reference all I want to do via my ks.cfg. If I'm doing a generic DHCP build, even my (generic) ks.cfg will be on the network. Because boot media size is of great concern for us, we have a minimal boot USB media. It's 39 MB for OL6.5. We have a larger boot media, that will allow you to install anything from RHEL 5.4 up to RHEL 6.5. If this is of interest to you, drop me a note and I'll send doc with full instructions. Spike White PS For RHEL7 static builds, while good in other ways -- the new anaconda results on the squashfs.img having to be on USB. So the absolute min-sized USB boot media is ~250 MB. Ouch! -------------- next part -------------- An HTML attachment was scrubbed... URL: From simpsonar77 at gmail.com Fri Jan 30 04:14:13 2015 From: simpsonar77 at gmail.com (Andrew Simpson) Date: Thu, 29 Jan 2015 23:14:13 -0500 Subject: help with creating USB kickstart drive RHEL 6.5 (Andrew Simpson) In-Reply-To: References: Message-ID: Spike, Thanks for the reply. I am always interested in hearing what other people do as it gives me new ideas, so I'd love to see your doc. My needs are pretty different. I don't really care about minimal sizes, etc... I package up an entirely customized version of RHEL 6 onto dvd. This install goes on multiple machines, etc... I have an entire build system that uses templating (jinja) to construct the kickstart files based on ks snippets. I am constantly making tweaks, updates, etc... and using CDs is extremely cumbersome especially given how long it takes to burn a dvd and then install from it. Thus why I want to use USB drives. much faster to install and easier to test changes. Also, for a few of the systems I install to, the image exceeds dvd size and I either have to use dual layer or make two separate install discs. USB drives would make that a smoother install. I also do pxe boot installs. Actually, my build script not only builds the disk, it auto-generates the isolinux.cfg files for the pxe server and then pushes the image/files to the tftp server. 250mb minimum! that's not very... minimal lol. We are planning a transition to RHEL 7 soon, but the core application is not happy about running on 7 yet, so I have to wait. At least I should be able to get the build system updated to support RHEL 7 in preparation. much better than trying to play catch up. Andrew Simpson On Thu, Jan 29, 2015 at 8:15 PM, Spike White wrote: > > > > From: Andrew Simpson > > To: kickstart-list at redhat.com > > Cc: > > Date: Thu, 29 Jan 2015 08:48:04 -0500 > > Subject: help with creating USB kickstart drive RHEL 6.5 > > I have a complicated kickstart based install that I have been using with > DVDs. I Would like to use USB drives, but I have a few questions that I > haven't gotten answers to yet. > > > > 1. what's the best way to create a bootable USB key/drive? I have been > using dd to put the ISO onto the device, but that makes the usb drive a > read only filesystem (iso9660). I would really like it to be writable. So > I'm assuming I will need to format the drive, put an mbr on there, etc...? > > > > 2. what kickstart install option should I be using? normally, I put > "cdrom" in. Do I have to change that to the "harddrive" option? > > > > 3. Is there a good reference for turning a dvd image into a live image? > > > > thanks in advance, the information on these topics is all over the place > and I'm not finding exactly what I need. > > > > Drew > > Drew, it really depends on what you want to do. What I do is stage all my > build content on the network. So my USB image has syslinux, vmlinuz, > initramfs and my ks.cfg. > > I reference all I want to do via my ks.cfg. > > If I'm doing a generic DHCP build, even my (generic) ks.cfg will be on the > network. > > Because boot media size is of great concern for us, we have a minimal boot > USB media. It's > 39 MB for OL6.5. We have a larger boot media, that will allow you to > install anything from RHEL 5.4 up to RHEL 6.5. > > If this is of interest to you, drop me a note and I'll send doc with full > instructions. > > Spike White > PS For RHEL7 static builds, while good in other ways -- the new anaconda > results on the squashfs.img having to be on USB. So the absolute min-sized > USB boot media is ~250 MB. > Ouch! > > > _______________________________________________ > Kickstart-list mailing list > Kickstart-list at redhat.com > https://www.redhat.com/mailman/listinfo/kickstart-list > -------------- next part -------------- An HTML attachment was scrubbed... URL: From abraxislists at gmail.com Fri Jan 30 05:46:46 2015 From: abraxislists at gmail.com (Neil Thompson) Date: Fri, 30 Jan 2015 07:46:46 +0200 Subject: help with creating USB kickstart drive RHEL 6.5 (Andrew Simpson) In-Reply-To: References: Message-ID: <20150130054646.GA10092@wol2.32.boerneef.vornavalley> On Thu, Jan 29, 2015 at 07:15:32PM -0600, Spike White wrote: ..... > 39 MB for OL6.5.? We have a larger boot media, that will allow you to > install anything from RHEL 5.4 up to RHEL 6.5. > If this is of interest to you, drop me a note and I'll send doc with full > instructions. > Spike White Hi Spike, Apologies for butting in here, but I'd be interested in seeing your doc as well. TIA -- Cheers! (Relax...have a homebrew) Neil ...aliquando et insanire iucundum est. -- Lucius Annaeus Seneca From oliver at redhat.com Fri Jan 30 10:20:22 2015 From: oliver at redhat.com (Oliver Haessler) Date: Fri, 30 Jan 2015 05:20:22 -0500 (EST) Subject: help with creating USB kickstart drive RHEL 6.5 (Andrew Simpson) In-Reply-To: <20150130054646.GA10092@wol2.32.boerneef.vornavalley> References: <20150130054646.GA10092@wol2.32.boerneef.vornavalley> Message-ID: <12471988.933.1422613220614.JavaMail.ohaessle@ohaessle.csb> same here for the doc please. Thanks Oliver ----- Original Message ----- From: "Neil Thompson" To: "Discussion list about Kickstart" Sent: Friday, January 30, 2015 6:46:46 AM Subject: Re: help with creating USB kickstart drive RHEL 6.5 (Andrew Simpson) On Thu, Jan 29, 2015 at 07:15:32PM -0600, Spike White wrote: ..... > 39 MB for OL6.5.? We have a larger boot media, that will allow you to > install anything from RHEL 5.4 up to RHEL 6.5. > If this is of interest to you, drop me a note and I'll send doc with full > instructions. > Spike White Hi Spike, Apologies for butting in here, but I'd be interested in seeing your doc as well. TIA -- Cheers! (Relax...have a homebrew) Neil ...aliquando et insanire iucundum est. -- Lucius Annaeus Seneca _______________________________________________ Kickstart-list mailing list Kickstart-list at redhat.com https://www.redhat.com/mailman/listinfo/kickstart-list