Discuss October 2020

discuss@lists.centos.org

71 participants
51 discussions

SSD for Centos SWAP /tmp & /var/ partition
by Keith Roberts 03 Sep '25

03 Sep '25

Has anyone actually used a SSD in a Centos setup? My little experiment with a s/h WD drive for /tmp and SWAP partitions kicked the bucket on Wednesday, when the poor WD drive caught the click-of-death. It was a s/h drive to start with and lasted about 4 months. But that was without the /var/log/ partition being written to it, as I mounted that back onto /var/log from the original drive. So I had to install another (WD) drive, and repartion it and rebuild my RPM package database, from the backed-up Packages file. That seems to be all OK now. I'm wondering if it would be a good idea to use a new SSD for moving all the disk i/o to, that Linux likes to do so often. Plus putting SWAP onto a decent SSD should speed things up somewhat. Here's a short video of a laptop fitted with a SSD drive booting macOS, compared to a similar laptop booting from the standard HDD. The laptop with the SSD boots and loads some apps in 28 seconds. The other one takes twice as long. http://eshop.macsales.com/shop/SSD/OWC/Mercury_Extreme_Pro_6G/?utm_source=t… Kind Regards, Keith Roberts ----------------------------------------------------------------- Websites: http://www.karsites.net http://www.php-debuggers.net http://www.raised-from-the-dead.org.uk All email addresses are challenge-response protected with TMDA [http://tmda.net] -----------------------------------------------------------------

33 96

Issues booting centos7 [dracut is failing to enable centos/root, centos/swap LVs]
by Yannis Milios 01 Feb '25

01 Feb '25

Hello, I'm having a strange problem booting a new centos7 installation. Below some background on this. [I have attached the tech details at the bottom of this message] I started a new CentOS7 installation on a VM, so far all good, o/s boots fine. Then I decided to increase VM disk size (initially was 10G) to 13G. Powered off the VM, increased the vhd via the hypervisor, booted from CentOS livecd, selected "recover my centos installation". Then I used the following sequence of commands to make the new vhd size "visible" to the o/s ... - ran fdisk /dev/sda and deleted partition 2. (This is the LVM partition where the o/s is stored. The first partition is /boot [xfs] partition *non lvm*.) - created a new partition with same starting sector as before deleting it, but a different ending sector (to reflect to the increased space). - set partition type to 8e (lvm), saved settings and exit. - ran pvresize and lvresize to make new space visible to the o/s.All good, I can see the space increase on 'lvdisplay centos/root'. - ran 'mount /dev/mapper/centos-root /mnt/root' to temporarily mount the o/s partition. - ran 'xfs_growfs /mnt/root' to resize the o/s fs to the new size. It was successful and I could actually chroot to the o/s and verify new disk size. - rebooted and tried to boot from hdd this time. Grub menu shows up and loads default kernel (3.10.0-862.9.1.el7.x86_64). - after initial kernel boot up process, booting continues to initrd and then it's where the problem starts... - looks like dracut has issues locating/enabling /dev/mapper/centos-root (lv) and as a result it cannot boot to the 'real' root fs (/). - while in dracut shell, I execute the following command sequence: 1. lvm lvchange -ay /dev/centos/root 2. lvm lvchange -ay /dev/centos/swap 3. ln -s /dev/mapper/centos-root /dev/root 4. exit ...and the o/s boots fine...so looks like the pv,vg,lv is detected properly while in initrd, but somehow dracut has difficulties enabling the root,swap LVs ? - While in o/s, I rebuild initrd by using: 'dracut -f -v -a lvm' Note, I have to use '-a lvm' as for some reason, if don't, the lvm utils (lvm,lvm_scan) are not being included to the initrd, not sure why this happens. After rebooting, same thing happens, I have to manually boot the system via dracut shell. I'm a bit stuck at this point, any clues what I'm doing wrong in here ? As I previously said, this is a new installation, so I could simply reinstall the whole thing, but I would rather try to find out some answer to why is this happening ... :-) [curiosity] Some additional details: ================== I've attached /run/initramfs/rdsosreport.txt file [generated while in inird] here: https://privatebin.net/?fdc4052c0c402884#gdB/QYR3IeR55SxUbjfrkZPQfJ7jMxiUxq… o/s ver=CentOS Linux release 7.5.1804 (Core) [root@localhost ~]# lsblk NAME MAJ:MIN RM SIZE RO TYPE MOUNTPOINT sda 8:0 0 13G 0 disk ├─sda1 8:1 0 500M 0 part /boot └─sda2 8:2 0 12.5G 0 part ├─centos-root 253:0 0 11.5G 0 lvm / └─centos-swap 253:1 0 1G 0 lvm [SWAP] [root@localhost ~]# cat /etc/default/grub GRUB_TIMEOUT=5 GRUB_DISTRIBUTOR="$(sed 's, release .*$,,g' /etc/system-release)" GRUB_DEFAULT=saved GRUB_DISABLE_SUBMENU=true GRUB_TERMINAL_OUTPUT="console" GRUB_CMDLINE_LINUX="rd.lvm.lv=centos/root rd.lvm.lv=centos/swap rd.shell rhgb" GRUB_DISABLE_RECOVERY="true"

4 11

MATE 1.20 test build for CentOS 7 available
by Greg Bailey 14 Oct '21

14 Oct '21

Hi everyone, There's been discussions in the past about updating MATE RPMs in EPEL-7: https://bugzilla.redhat.com/show_bug.cgi?id=1436260 https://lists.centos.org/pipermail/centos/2019-August/173154.html (and lots of others...) As a proof-of-concept, I've written some scripts that clone specific commits from the Fedora master branches, and then runs a tool to re-apply RPM scriptlets that are required by EL7 but removed from the Fedora .spec files. The scripts are available at: https://github.com/gebailey/mate-rpms/tree/master/1.20/el7 There's also instructions there if you want to try upgrading to MATE 1.20 w/o rebuilding them yourself. If these packages work for others, perhaps we can revisit the idea of updating the epel7 branches of the Fedora git repos and submitting an official update. There's nothing here (yet) about building MATE 1.22 (which might require a newer gcc for EL7), or building anything on CentOS 8, but thought the CentOS 7 users might find this helpful. -Greg

6 17

CentOS advisories for 8 release
by Olivier Bonhomme 16 Dec '20

16 Dec '20

Hello dear CentOS community, I'm writing on this mailing list because I'm discovering CentOS 8 after several years of practice on CentOS 7. One of my main concern about a distribution is Bug Fixes and Security Fixes. For CentOS 7, all fixes where identified on CentOS-Announces lists with CESA, CEBA and CEEA which is a good thing in order to identify how a distribution can be broken, vulnerable. However, I didn't find any announcement for CentOS 8. I tried to investigate about any changes about announcement policies but I didn't find anything reliable. So I'm asking here what is exactly the status about announcements for CentOS 8 ? Is it a thing who totally disappeared replaced by Red Hat advisories or is it something different ? Or maybe it is just not planned yet ? Explanations would be very welcomed. Thanks for your answer Regards, Olivier Bonhomme

3 3

Logitech C922 webcam
by H 06 Dec '20

06 Dec '20

Just installed the above USB webcam but it is not recognized by dmesg | grep usb, nor does Zoom recognize it. I was under the understanding it should not require a driver, or? I am running CentOS 7. Thanks.

6 23

X defaults
by Michael Hennebry 23 Nov '20

23 Nov '20

I've been trying to move from Centos 7 to fedora. My monitor is 1440x900, but fedora only believes it's 640x480. Grrrr. xrandr has not helped. I've been trying to write X configuration files to tell fedora 1440x900, but no joy. Is there a way to get X to tell me its current beliefs, very preferably in configuration file format? According to the log file on Centos, everything was defaulted or probed. It contains no numbers. My guess is that fedora has different defaults and they are wrong for me. I've had problems like this before, so I'm unwilling to install until I know I can run a live version. That makes life clunky. I have to boot to non-graphics, do my editing and change the runlevel. -- Michael hennebry(a)web.cs.ndsu.NoDak.edu "Sorry but your password must contain an uppercase letter, a number, a haiku, a gang sign, a heiroglyph, and the blood of a virgin." -- someeecards

4 6

Unable to get dummy interfaces to persist across reboots in CentOS 8
by Frank Even 13 Nov '20

13 Nov '20

Hello all, hoping someone can help me out here. I cannot get dummy interfaces on a new Cent8 build to persist across reboots. On Cent7 - this is the process I use: Create Dummies: # cat /etc/modules-load.d/dummy.conf dummy # cat /etc/modprobe.d/dummyopts.conf options dummy numdummies=4 # ip link add dummy0 type dummy ## - repeating a/ ascending dummyN adapters for as many needed # service network start # dracut -f Now this was different than even how 6 handled it, forget how I finally dug that up (possible I even asked here). I've applied this same configuration to a Cent8 box I'm trying to stand up and it all appears to work fine, but unlike the Cent7 boxes, when the Cent8 box comes back up, all the dummy adapters are missing. I've been searching all over trying to find some documentation on this to no avail. I'm hoping someone has some suggestions here to help out. Thanks, Frank

3 8

LibreOffice locking up
by H 07 Nov '20

07 Nov '20

I am running LibreOffice 5.3.6.1 under the latest update of CentOS 7 and the Mate desktop. Not infrequently LibreOffice Calc locks up and I have to force close the application. Altough the spreadsheet is rather large I would not consider it complex. This has been going on for some time and I am curious if the bug might be in LibreOffice or if there is some interaction with the Mate desktop that might be responsible. Both CentOS, LibreOffice and Mate have been regularly updated from the standard repositories for a long time. Does anyone else have the same problem?

6 11

dnsmasq centos 7
by Jerry Geis 03 Nov '20

03 Nov '20

HI I setup dnsmasq on my computer. I tested with an entry in /etc/hosts for laptop.w530 I tested with "host laptop.w530" and I get unresolved (expected). If I add "nameserver 192.168.1.8" (my computer) to top of /etc/resolv.conf and do "host laptop.w530" I get 192.168.1.105 - so seems to be working. Then I goto another machine, add the "nameserver 192.168.1.8" to /etc/resolv.conf and do the same "host laptop.w530" and it does not resolve. I can "telnet 192.168.1.8 53" to my machine and I get a response. Am I missing something to have "other" machines ask my machine for name resolution ? Thanks, Jerry

5 7

ThinkStation with BIOS RAID and disk error messages in gparted
by H 03 Nov '20

03 Nov '20

My ThinkStation runs CentOS 7 which I installed on a BIOS RAID 0 setup with two identical 256 Gb SSDs after removing Windows. It runs fine but I just discovered in gparted something that does not seem right: - Launching gparted it complains "invalid argument during seek for red on /dev/md126" and when I click on Ignore I get another error "The backup GPT table is corrupt, but the primary appears OK, so that will be used." I then click on OK whereupon I again see the second error message. I then see "Not all of the space available to /dev/sdb appears to be used, you can fix the GPT to use all of the space (an extra 6832 blocks) or continue with the current setting? " I click on Fix but nothing seems to happen. I am not sure what /dev/md126 is but it is the exact same size as sda and sdb which I believe are the two RAID disks. I also have two other hard disks which seem to be fine, one using XFS, the other ZFS. Does this look familiar to anyone? Given the error messages it seems this is something I ought to fix sooner rather than later. Any idea what I should do? Thanks.

3 4

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

2005

2004

Discuss October 2020