Re: [CentOS] CentOS 7 install on one RAID 1 [not-so-SOLVED]
> > If you are using RAID 1 kernel mirroring, you can do that with /boot too, > and Grub finds the kernel just fine. I've done it many times: > > Hmm, OK. I wonder why anaconda doesn't do it then. Reading various websites, it looks like grub2 can do it, but you have to make sure that various grub modules are installed first - i.e. do something like grub-install --modules='biosdisk ext2 msdos raid mdraid' /dev/xxx I don't know if they are added by default these days. The other gotcha is, of course, that the boot sectors aren't RAID'd - so if /dev/sda goes, replacing it will make the system unbootable since it doesn't contain the boot sectors. Hot swap will keep the system running but you have to remember to re-install the correct boot sector before reboot. If you have to bring the machine down to change the disk, then things could get interesting! P. ___ CentOS mailing list CentOS@centos.org https://lists.centos.org/mailman/listinfo/centos
[CentOS] centos-openshift-origin
?Hi, Would someone know when to expect to have package origin-master.1.4.0 in repo centos-openshift-origin? Right now the package is available in centos-openshift-origin-testing. -Vedran ___ CentOS mailing list CentOS@centos.org https://lists.centos.org/mailman/listinfo/centos
Re: [CentOS] CentOS 7 install on one RAID 1 [not-so-SOLVED]
On 26/01/17 05:46, Tony Mountifield wrote: In article <1485342377.3072.6.ca...@biggs.org.uk>, Pete Biggs wrote: On Tue, 2017-01-24 at 17:14 -0500, m.r...@5-cent.us wrote: So, it installed happily. Then wouldn't boot. No problem, I'll bring it up with pxe, then chroot and grub2-install. Um, nope. I edited the device map from hd0 and hd1 being the RAID to /dev/sda and /dev/sdb, then ran grup2-install. It now tells me can't identify the filesystem on hd0, and can't perform a safety check, and gives up. What am I missing? Google is not giving me any answers Surely, if you are using software RAID, then you should configure that RAID in anaconda, that will then cope with setting up the partitions to allow booting. Basically it needs a small non-RAID partition to hold /boot on the boot disk. Remember that the boot sequence is generally: BIOS reads MBR and executes it; MBR code reads kernel from /boot and executes it (yes, it's more complicated than that). If the MBR code doesn't know how to read a RAID partition, then it's going to fail, that's why you have a small non-RAID partition to hold /boot. Hardware RAID is different because it interfaces at the BIOS level so the MBR code doesn't need to know how to specifically read it. If you are using RAID 1 kernel mirroring, you can do that with /boot too, and Grub finds the kernel just fine. I've done it many times: 1. Primary partition 1 type FD, size 200M. /dev/sda1 and /dev/sdb1. I think it wiser to have /boot at 1Gb nowadays. 2. Create /dev/md0 as RAID 1 from /dev/sda1 and /dev/sdb1. 3. Assign /dev/md0 to /boot, ext3 format (presumably ext4 would work too?) 4. Make sure to setup both drives separately in grub. Typically I then go on to have /dev/sda2+/dev/sdb2 => /dev/md1 => swap, and /dev/sda3+/dev/sdb3 => /dev/md2 => / Cheers Tony ___ CentOS mailing list CentOS@centos.org https://lists.centos.org/mailman/listinfo/centos
Re: [CentOS] SELinux file permissions
> Did you define my_postfixauth_private_t yourself? And if so, why? > > All my sockets inside /var/spool/postfix/private/ have the type > postfix_private_t. I don't see why you think a non-standard type would fit. > And postfix_private_t gets automatically assigned and a custom fcontext > should not be necessary. > > Alexander > I just gave up in the end and did what you're (apparently) not supposed to do . fgrep dovecot_t /var/log/audit/audit.log | audit2allow The output moaned about base types, but googling that just led me into the murky depths of even more confusing selinux wizardry. So I gave up trying to fix that too by that point I had wasted three days trying to get Dovecot working and wasn't about to waste another three figuring how to get around the "base types" complaints. I love the concept of selinux but boy do I wish the developers wouldn't have made it quite so obscure and complicated to work with !! ___ CentOS mailing list CentOS@centos.org https://lists.centos.org/mailman/listinfo/centos
Re: [CentOS] CentOS 7 install on one RAID 1 [not-so-SOLVED]
Gordon Messmer wrote: > You didn't answer all of the questions I asked, but I'll answer as best > I can with the information you gave. > Manitu ate my email, *again*. > On 01/25/2017 04:47 AM, mark wrote: >> >> Made an md RAID 0 on the raw disks - /dev/sda /dev/sdb. No partitions, >> nothing. > > OK, so right off the bat we have to note that this is not a > configuration supported by Red Hat. It is possible to set such a system > up, but it may require advanced knowledge of grub2 and mdadm. Because > I sympathize. I wanted to use full disk RAID, too. I thought that Thank you. > >> However, when I bring it up, fdisk shows an MBR with no partitions. I >> can, however, mount /dev/md127p3 as /mnt/sysimage, and all is there. > > I assume you're booting with BIOS, then? Yup. > > One explanation for fdisk showing nothing is that you're using GPT > instead of MBR (I think). In order to boot on such a system, you'd need Nope. fdisk sees it as an MBR. The SSDs are only 128G. They just run the server, and the LSI card takes care of the 12 hot-swap drives (It's a storage server.) > a bios_boot partition at the beginning of the RAID volume to provide > enough room for grub2 not to stomp on the first partition with a > filesystem. > > The other explanation that comes to mind is that you're using an mdadm > metadata version stored at the beginning of the drive instead of the > end. Do you know what metadata version you used? I took CentOS 7's default for mdadm. > >> Did I need to make a single partition, on each drive, and then make >> the RAID 1 out of *those*? I don't think I need to have /boot not on a >> RAID. > > That's one option, but it still won't be a supported configuration. Yeah, I see. Well, time to go rebuild, and this time with three separate RAID 1 partitions mark ___ CentOS mailing list CentOS@centos.org https://lists.centos.org/mailman/listinfo/centos
Re: [CentOS] CentOS 7 install on one RAID 1 [not-so-SOLVED]
You didn't answer all of the questions I asked, but I'll answer as best I can with the information you gave. On 01/25/2017 04:47 AM, mark wrote: Made an md RAID 0 on the raw disks - /dev/sda /dev/sdb. No partitions, nothing. OK, so right off the bat we have to note that this is not a configuration supported by Red Hat. It is possible to set such a system up, but it may require advanced knowledge of grub2 and mdadm. Because the vendor doesn't support this configuration, and as you've seen, the tools don't always parse out the information they need, you'll forever be responsible for fixing any boot problems that come up. Do you really want that? I sympathize. I wanted to use full disk RAID, too. I thought that replacing disks would be much easier this way, since there'd just be one md RAID device to manage. That was an attractive option after working with hardware RAID controllers that were easy to manage but expensive, unreliable, and performed very poorly in some conditions. But after a thorough review, I found my earlier suggestion of partitioned RAID with the kickstart and RAID management script I provided was the least work for me, in the long term. However, when I bring it up, fdisk shows an MBR with no partitions. I can, however, mount /dev/md127p3 as /mnt/sysimage, and all is there. I assume you're booting with BIOS, then? One explanation for fdisk showing nothing is that you're using GPT instead of MBR (I think). In order to boot on such a system, you'd need a bios_boot partition at the beginning of the RAID volume to provide enough room for grub2 not to stomp on the first partition with a filesystem. The other explanation that comes to mind is that you're using an mdadm metadata version stored at the beginning of the drive instead of the end. Do you know what metadata version you used? Did I need to make a single partition, on each drive, and then make the RAID 1 out of *those*? I don't think I need to have /boot not on a RAID. That's one option, but it still won't be a supported configuration. ___ CentOS mailing list CentOS@centos.org https://lists.centos.org/mailman/listinfo/centos
Re: [CentOS] CentOS 7 install on one RAID 1 [not-so-SOLVED]
In article <1485342377.3072.6.ca...@biggs.org.uk>, Pete Biggs wrote: > On Tue, 2017-01-24 at 17:14 -0500, m.r...@5-cent.us wrote: > > So, it installed happily. > > > > Then wouldn't boot. No problem, I'll bring it up with pxe, then chroot and > > grub2-install. > > > > Um, nope. I edited the device map from hd0 and hd1 being the RAID to > > /dev/sda and /dev/sdb, then ran grup2-install. It now tells me can't > > identify the filesystem on hd0, and can't perform a safety check, and > > gives up. > > > > What am I missing? Google is not giving me any answers > > > > Surely, if you are using software RAID, then you should configure that > RAID in anaconda, that will then cope with setting up the partitions to > allow booting. Basically it needs a small non-RAID partition to hold > /boot on the boot disk. > > Remember that the boot sequence is generally: BIOS reads MBR and > executes it; MBR code reads kernel from /boot and executes it (yes, > it's more complicated than that). If the MBR code doesn't know how to > read a RAID partition, then it's going to fail, that's why you have a > small non-RAID partition to hold /boot. > > Hardware RAID is different because it interfaces at the BIOS level so > the MBR code doesn't need to know how to specifically read it. If you are using RAID 1 kernel mirroring, you can do that with /boot too, and Grub finds the kernel just fine. I've done it many times: 1. Primary partition 1 type FD, size 200M. /dev/sda1 and /dev/sdb1. 2. Create /dev/md0 as RAID 1 from /dev/sda1 and /dev/sdb1. 3. Assign /dev/md0 to /boot, ext3 format (presumably ext4 would work too?) 4. Make sure to setup both drives separately in grub. Typically I then go on to have /dev/sda2+/dev/sdb2 => /dev/md1 => swap, and /dev/sda3+/dev/sdb3 => /dev/md2 => / Cheers Tony -- Tony Mountifield Work: t...@softins.co.uk - http://www.softins.co.uk Play: t...@mountifield.org - http://tony.mountifield.org ___ CentOS mailing list CentOS@centos.org https://lists.centos.org/mailman/listinfo/centos
Re: [CentOS] CentOS 7 install on one RAID 1 [not-so-SOLVED]
On Wed, January 25, 2017 9:51 am, m.r...@5-cent.us wrote: > Let me see if I can, um, reboot this thread > > I made a RAID 1 of two raw disks, /dev/sda and /dev/sdb, *not* /dev/sdax > /dev/sdbx. Then I installed CentOS 7 on the RAID, with /boot, /, and swap > being partitions on the RAID. My problem is that grub2-install absolutely > and resolutely refuses to install on /dev/sda or /dev/sdb. > > I've currently got it up in a half-assed rescue mode, and have mount -o > bind /dev, /proc/ and /sys under /mnt/sysimage, and chrooted there. That's > where I'm trying to do my grub2-install. > > So: > 1. *Is* there space for grub2 to install the bootloader under where the > mdadm starts? To the best of my knowledge: no. To have mdadm started (md devices created) you already need kernel loaded, at this stage you don't have it, you will have it in memory after you load initramdrive, so initramdrive is useless on md devices which do not exist yet at the moment you load initramdrive. > Or do I have to partition the disks (/dev/sda1 100%, ditto > /dev/sdb1, then > create the RAID 1 with the partitions, and *then* grub2-install? Not necessarily, you can have software RAID/mirror of /dev/sda /dev/sdb (without those having disk labels). However, to boot you need regular drive partition present that hosts /boot (and bootloader somewhere on drive that does have disk label). You can have it all on separate tiny drive. Several years back it was done as I and one more poster described in the tread before the thread was "rebooted". Now it is possible grub progressed since, but I doubt that grub supports Linux software RAID devices, for which it would need appropriate Linux portion of code, which is rather large, and GRUB being used to boot other system as well then likely will need to have their implementations of the same... But that might be outdated, I hope someone with current knowledge will chime in. Valeri > 2. I *think* that one thing that grub2-install is complaining about is > that it can't >find /boot/grub2. I've tried doing it with > $ grub2-install --boot-directory=/boot /dev/sda >and > $ grub2-install --boot-directory=/dev/md127p1/ /dev/sda >and > $ grub2-install --boot-directory=/dev/md127pw/boot /dev/sda >and it tells me it cannot find the canonical path for the grub2 > directory. Is >there some way to specify where it should fund /boot/grub2 that > I've missed? > > mark > > ___ > CentOS mailing list > CentOS@centos.org > https://lists.centos.org/mailman/listinfo/centos > Valeri Galtsev Sr System Administrator Department of Astronomy and Astrophysics Kavli Institute for Cosmological Physics University of Chicago Phone: 773-702-4247 ___ CentOS mailing list CentOS@centos.org https://lists.centos.org/mailman/listinfo/centos
Re: [CentOS] CentOS 7 install on one RAID 1 [not-so-SOLVED]
Let me see if I can, um, reboot this thread I made a RAID 1 of two raw disks, /dev/sda and /dev/sdb, *not* /dev/sdax /dev/sdbx. Then I installed CentOS 7 on the RAID, with /boot, /, and swap being partitions on the RAID. My problem is that grub2-install absolutely and resolutely refuses to install on /dev/sda or /dev/sdb. I've currently got it up in a half-assed rescue mode, and have mount -o bind /dev, /proc/ and /sys under /mnt/sysimage, and chrooted there. That's where I'm trying to do my grub2-install. So: 1. *Is* there space for grub2 to install the bootloader under where the mdadm starts? Or do I have to partition the disks (/dev/sda1 100%, ditto /dev/sdb1, then create the RAID 1 with the partitions, and *then* grub2-install? 2. I *think* that one thing that grub2-install is complaining about is that it can't find /boot/grub2. I've tried doing it with $ grub2-install --boot-directory=/boot /dev/sda and $ grub2-install --boot-directory=/dev/md127p1/ /dev/sda and $ grub2-install --boot-directory=/dev/md127pw/boot /dev/sda and it tells me it cannot find the canonical path for the grub2 directory. Is there some way to specify where it should fund /boot/grub2 that I've missed? mark ___ CentOS mailing list CentOS@centos.org https://lists.centos.org/mailman/listinfo/centos
Re: [CentOS] samba rpm deps - with yum downgrade = kind of a mayhem
On Wed, Jan 25, 2017 at 11:32:16AM +, lejeczek wrote: > hi guys, gals > > do you see this: > > ~]$ yum downgrade samba > Resolving Dependencies > [...] > --> Processing Dependency: libtevent.so.0(TEVENT_0.9.9) for package: > samba-client-libs-4.4.4 > > ..and process fails. > chained are i686 arch? Is it only us(centos) or redhat's bugzilla should be > notified. > Samba downgrade used to work I remember. Most likely there are dependencies that aren't available in your current repos that are preventing the downgrade. Perhaps its due to the recent point release to 7.1611? The packages installed with a 'yum downgrade' are unlikely to be supported, so this is probably not really something that CentOS supports. -- Jonathan Billings ___ CentOS mailing list CentOS@centos.org https://lists.centos.org/mailman/listinfo/centos
Re: [CentOS] CentOS 7 install on one RAID 1 [not-so-SOLVED]
On 01/24/17 19:00, Gordon Messmer wrote: On 01/24/2017 02:14 PM, m.r...@5-cent.us wrote: So, it installed happily. Then wouldn't boot. What did the storage configuration look like, exactly? I'd guess that you put one partition on each disk, combined those in a RAID1 MD array, made than an LVM physical volume, and then created filesystems and swap on LVs. But that's a lot of guesses. Did you use MBR partitions or GPT? Are you booting under BIOS or UEFI? Where do your partitions start? Did you create a standard MD RAID volume and LVM or a partitionable RAID volume and partitions? No. Brand new machine, pulled it out of the box and racked it. NOTHING on the internal SSDs. Made an md RAID 0 on the raw disks - /dev/sda /dev/sdb. No partitions, nothing. However, when I bring it up, fdisk shows an MBR with no partitions. I can, however, mount /dev/md127p3 as /mnt/sysimage, and all is there. Did I need to make a single partition, on each drive, and then make the RAID 1 out of *those*? I don't think I need to have /boot not on a RAID. mark ___ CentOS mailing list CentOS@centos.org https://lists.centos.org/mailman/listinfo/centos
[CentOS] samba rpm deps - with yum downgrade = kind of a mayhem
hi guys, gals do you see this: ~]$ yum downgrade samba Resolving Dependencies --> Running transaction check ---> Package samba.x86_64 0:4.4.4-9.el7 will be a downgrade --> Processing Dependency: samba-libs = 4.4.4-9.el7 for package: samba-4.4.4-9.el7.x86_64 --> Processing Dependency: samba-common-tools = 4.4.4-9.el7 for package: samba-4.4.4-9.el7.x86_64 --> Processing Dependency: samba-common-libs = 4.4.4-9.el7 for package: samba-4.4.4-9.el7.x86_64 --> Processing Dependency: samba-common = 4.4.4-9.el7 for package: samba-4.4.4-9.el7.x86_64 --> Processing Dependency: samba-client-libs = 4.4.4-9.el7 for package: samba-4.4.4-9.el7.x86_64 --> Processing Dependency: libwbclient = 4.4.4-9.el7 for package: samba-4.4.4-9.el7.x86_64 ---> Package samba.x86_64 0:4.4.4-12.el7_3 will be erased --> Running transaction check ---> Package libwbclient.i686 0:4.4.4-9.el7 will be installed ---> Package samba.x86_64 0:4.4.4-9.el7 will be a downgrade --> Processing Dependency: samba-common-tools = 4.4.4-9.el7 for package: samba-4.4.4-9.el7.x86_64 --> Processing Dependency: samba-common-libs = 4.4.4-9.el7 for package: samba-4.4.4-9.el7.x86_64 --> Processing Dependency: samba-common = 4.4.4-9.el7 for package: samba-4.4.4-9.el7.x86_64 ---> Package samba.x86_64 0:4.4.4-12.el7_3 will be erased ---> Package samba-client-libs.i686 0:4.4.4-9.el7 will be installed --> Processing Dependency: samba-common = 4.4.4-9.el7 for package: samba-client-libs-4.4.4-9.el7.i686 --> Processing Dependency: libtevent.so.0(TEVENT_0.9.9) for package: samba-client-libs-4.4.4 ..and process fails. chained are i686 arch? Is it only us(centos) or redhat's bugzilla should be notified. Samba downgrade used to work I remember. bw. L. ___ CentOS mailing list CentOS@centos.org https://lists.centos.org/mailman/listinfo/centos
Re: [CentOS] CentOS 7 install on one RAID 1 [not-so-SOLVED]
On Tue, 2017-01-24 at 17:14 -0500, m.r...@5-cent.us wrote: > So, it installed happily. > > Then wouldn't boot. No problem, I'll bring it up with pxe, then chroot and > grub2-install. > > Um, nope. I edited the device map from hd0 and hd1 being the RAID to > /dev/sda and /dev/sdb, then ran grup2-install. It now tells me can't > identify the filesystem on hd0, and can't perform a safety check, and > gives up. > > What am I missing? Google is not giving me any answers > Surely, if you are using software RAID, then you should configure that RAID in anaconda, that will then cope with setting up the partitions to allow booting. Basically it needs a small non-RAID partition to hold /boot on the boot disk. Remember that the boot sequence is generally: BIOS reads MBR and executes it; MBR code reads kernel from /boot and executes it (yes, it's more complicated than that). If the MBR code doesn't know how to read a RAID partition, then it's going to fail, that's why you have a small non-RAID partition to hold /boot. Hardware RAID is different because it interfaces at the BIOS level so the MBR code doesn't need to know how to specifically read it. P. ___ CentOS mailing list CentOS@centos.org https://lists.centos.org/mailman/listinfo/centos
