Discuss

discuss@lists.centos.org

34729 discussions

/bin/journalctl --flush hangs on CentOS Stream release 8
by Jelle de Jong 30 Mar '23

30 Mar '23

Hello everybody, Somehting is causing /bin/journalctl --flush to hang on some new and existing installations of on CentOS Stream release 8 # journalctl --disk-usage Archived and active journals take up 8.0M in the file system. # journalctl --verify PASS: /run/log/journal/48651cee389b4600bf559fb29d1c2066/system.journal # /usr/bin/journalctl --flush ^C Do other users have this as well and is there a fix or update pending? Kind regards, Jelle de Jong

1 0

CentOS-announce Digest, Vol 212, Issue 4
by centos-announce-request＠centos.org 23 Mar '23

23 Mar '23

Send CentOS-announce mailing list submissions to centos-announce(a)centos.org To subscribe or unsubscribe via the World Wide Web, visit https://lists.centos.org/mailman/listinfo/centos-announce or, via email, send a message with subject or body 'help' to centos-announce-request(a)centos.org You can reach the person managing the list at centos-announce-owner(a)centos.org When replying, please edit your Subject line so it is more specific than "Re: Contents of CentOS-announce digest..." Today's Topics: 1. CESA-2023:1333 Important CentOS 7 firefox Security Update (Johnny Hughes) 2. CESA-2023:1335 Important CentOS 7 openssl Security Update (Johnny Hughes) 3. CESA-2023:1332 Important CentOS 7 nss Security Update (Johnny Hughes) ---------------------------------------------------------------------- Message: 1 Date: Wed, 22 Mar 2023 14:00:31 +0000 From: Johnny Hughes <johnny(a)centos.org> To: centos-announce(a)centos.org Subject: [CentOS-announce] CESA-2023:1333 Important CentOS 7 firefox Security Update Message-ID: <20230322140031.GA6713(a)bstore1.rdu2.centos.org> Content-Type: text/plain; charset=us-ascii CentOS Errata and Security Advisory 2023:1333 Important Upstream details at : https://access.redhat.com/errata/RHSA-2023:1333 The following updated files have been uploaded and are currently syncing to the mirrors: ( sha256sum Filename ) x86_64: 158e955d20950ef61a38c645accc22bd6cf37c7f31e06cdd3313c2bc5b0d969f firefox-102.9.0-3.el7.centos.i686.rpm a83374c57cbdfe6fe09065ecf3df2781d4ed835b1b41143f2b4e74dde0e6a8cd firefox-102.9.0-3.el7.centos.x86_64.rpm Source: 4b1730e4811654a2dec4ccc990051f3212106208b6170c2546e74048d795b7e6 firefox-102.9.0-3.el7.centos.src.rpm -- Johnny Hughes CentOS Project { http://www.centos.org/ } irc: hughesjr, #centos(a)libera.chat Twitter: @JohnnyCentOS ------------------------------ Message: 2 Date: Wed, 22 Mar 2023 14:01:44 +0000 From: Johnny Hughes <johnny(a)centos.org> To: centos-announce(a)centos.org Subject: [CentOS-announce] CESA-2023:1335 Important CentOS 7 openssl Security Update Message-ID: <20230322140144.GA7355(a)bstore1.rdu2.centos.org> Content-Type: text/plain; charset=us-ascii CentOS Errata and Security Advisory 2023:1335 Important Upstream details at : https://access.redhat.com/errata/RHSA-2023:1335 The following updated files have been uploaded and are currently syncing to the mirrors: ( sha256sum Filename ) x86_64: 74be24de7bd01781535f8ae78fba77bf331f0afd97e69de054496dfa406689b1 openssl-1.0.2k-26.el7_9.x86_64.rpm 1771d7f870046fcd2d0c96d054f425f3032a0f4271dfb54c5e5bb22cd2f87d11 openssl-devel-1.0.2k-26.el7_9.i686.rpm a5f13a41cc54cc7e9bcaf76ee19fec24dd4c8b4f637c43a411f8fe4af310a88c openssl-devel-1.0.2k-26.el7_9.x86_64.rpm 49a7e87cdd6368571e9c30b74a1800f53df55d4cd91fc41ab8073e666edbda38 openssl-libs-1.0.2k-26.el7_9.i686.rpm 658486f1d946fc518624c59a2badf6990f524bb7d5d660d1e34420cc78dcfe62 openssl-libs-1.0.2k-26.el7_9.x86_64.rpm de13d1a20b6a077c828b91d64b7be5abb1b5809f45b27d389afd2811ffa6f9c1 openssl-perl-1.0.2k-26.el7_9.x86_64.rpm 62ee7eed9057a933f386601510a2ee1dbe6cee295c00a4e75c1d5ca32a0e17cd openssl-static-1.0.2k-26.el7_9.i686.rpm cc98e7151dca218503a6d908ee58257a7e7958347117c435c93746255a841c89 openssl-static-1.0.2k-26.el7_9.x86_64.rpm Source: ea29d3d1b0ef3088a40242c5ad90ef1597146edba7413229304d1568f5abc55e openssl-1.0.2k-26.el7_9.src.rpm -- Johnny Hughes CentOS Project { http://www.centos.org/ } irc: hughesjr, #centos(a)libera.chat Twitter: @JohnnyCentOS ------------------------------ Message: 3 Date: Wed, 22 Mar 2023 14:03:02 +0000 From: Johnny Hughes <johnny(a)centos.org> To: centos-announce(a)centos.org Subject: [CentOS-announce] CESA-2023:1332 Important CentOS 7 nss Security Update Message-ID: <20230322140302.GA7811(a)bstore1.rdu2.centos.org> Content-Type: text/plain; charset=us-ascii CentOS Errata and Security Advisory 2023:1332 Important Upstream details at : https://access.redhat.com/errata/RHSA-2023:1332 The following updated files have been uploaded and are currently syncing to the mirrors: ( sha256sum Filename ) x86_64: b53a6924f3594abaaeaa39917b0114b7f6f7dcf8df0ffe03ab3a8957ae3405c4 nss-3.79.0-5.el7_9.i686.rpm 2077a5a2df3692687ac9b3f892005ec2eabe97368eec05197fbf1f961f013442 nss-3.79.0-5.el7_9.x86_64.rpm 4b35cc37198ac1275db864e9be35ef4048337b891115e699165a85a519fdd7a2 nss-devel-3.79.0-5.el7_9.i686.rpm 78923c044dee6993ff55684229e266296bd04b772f4c47761a0e197bf8ddada6 nss-devel-3.79.0-5.el7_9.x86_64.rpm acd182fdbf43efaafafe21332a32ca669b688ad9760f5af2cbe33be296901606 nss-pkcs11-devel-3.79.0-5.el7_9.i686.rpm 458d8d0ed05bdaad8b13b09c5d860beda84b34bf0ab4c5673194584865a68103 nss-pkcs11-devel-3.79.0-5.el7_9.x86_64.rpm a687f0ccd9e74160f22533e305c5bb77d33023ba63729183e338ad27461a5494 nss-sysinit-3.79.0-5.el7_9.x86_64.rpm 1849014c019076934853ec6d7ad795b91829e59d3946c36ff4c13951f53c6a67 nss-tools-3.79.0-5.el7_9.x86_64.rpm Source: a404f20dff75b9a505258d5ea36399d8ba9c10d5d1cd355f4c26f0338c2f7bba nss-3.79.0-5.el7_9.src.rpm -- Johnny Hughes CentOS Project { http://www.centos.org/ } irc: hughesjr, #centos(a)libera.chat Twitter: @JohnnyCentOS ------------------------------ Subject: Digest Footer _______________________________________________ CentOS-announce mailing list CentOS-announce(a)centos.org https://lists.centos.org/mailman/listinfo/centos-announce ------------------------------ End of CentOS-announce Digest, Vol 212, Issue 4 ***********************************************

1 0

where is glib-devl x86-64?
by Fred 22 Mar '23

22 Mar '23

I have a brand new installation of Rocky Linux 9.1 (I know, this isn't a Rocky mailing list, but I can't find anything on this on Rocky forums, etc. so I figured I would ask here), and I installed Gimp, and would like to install the Resynthesizer plugin package. Trying to compile it from source, autogen.sh complains that I don't have the gimp development libraries installed. In fact, I can't find glib-devel anywhere in any of the configured repos (all the default Rocky repos, epel, rpmfusion). Rocky is shipping an unstable development version of Gimp, so maybe they haven't made glib-devel available yet ??? Thanks in advance for any help you can give! Fred

6 9

Re: [CentOS] PHP-LDAP RPM installed but not usable
by Gary Stainburn 21 Mar '23

21 Mar '23

I've also tried adding the pgsql and mysql RPM's and they're not available either. On 20/03/2023 12:58, Gary Stainburn wrote: > Apologies. This is the correct screen grab. > > The extra errors in the OP were because I had been experimenting, to > try to fix the issue. > > [root@testsvr ~]# ./ldapAuth.php gary.stainburn fake-password > PHP Fatal error: Uncaught Error: Call to undefined function > ldap_connect() in /root/ldapAuth.php:12 > > I suspect that the extension is not being loaded, and one post > suggested having to add an > > extension= > > line to php.ini, but I cannot find the library it's supposed to load. > > > > On 20/03/2023 12:52, Gary Stainburn wrote: >> Hi folks. >> >> I've installed PHP 8.0 on my server, and just installed php-ldap. All >> looks to have worked fine. >> >> php-common-8.0.28-1.el7.remi.x86_64 >> php-8.0.28-1.el7.remi.x86_64 >> php80-php-common-8.0.28-1.el7.remi.x86_64 >> php80-php-ldap-8.0.28-1.el7.remi.x86_64 >> php-cli-8.0.28-1.el7.remi.x86_64 >> php-sodium-8.0.28-1.el7.remi.x86_64 >> php80-runtime-1.0-3.el7.remi.x86_64 >> >> However, when I try to use LDAP in a script, it says the >> ldap_connect function is not available: >> >> [root@testsvr ~]# ./ldapAuth.php gary.stainburn fake-password >> PHP Warning: PHP Startup: Unable to load dynamic library 'ldap' >> (tried: /usr/lib64/php/modules/ldap (/usr/lib64/php/modules/ldap: >> cannot open shared object file: No such file or directory), >> /usr/lib64/php/modules/ldap.so (/usr/lib64/php/modules/ldap.so: >> cannot open shared object file: No such file or directory)) in >> Unknown on line 0 >> PHP Fatal error: Uncaught Error: Call to undefined function >> ldap_connect() in /root/ldapAuth.php:12 >> >> >> Can anyone see what I've missed? >> _______________________________________________ >> CentOS mailing list >> CentOS(a)centos.org >> https://lists.centos.org/mailman/listinfo/centos > > -- > > Kind regards > > Gary Stainburn > > *Group I.T. Manager - D.M.Keith Ford/Kia After-Sales* > > *Switchboard* 0113 2634 222 > > *Address:* D.M.Keith Ford/Kia Aftersales | Hales Road | Leeds | LS12 4TG > > > /*Branches throughout Yorkshire and North Lincolnshire.*/ > > *Ford Leeds *0113 263 4222 | *Transit Centre Leeds* 0113 2634222 | > *Skoda Leeds* 0113 2771777 | *KiaLeeds* 0113426 8111 | *Kia Doncaster* > 01302 384350 | *Skoda Bradford* 01274 741200 | *Skoda Wakefield* 01924 > 246900 | *Skoda Huddersfield*01484 435499 | *Skoda York* 01904 692921| > *SEAT York* 01904 692921 | *Cupra York* 01904 692921 | *Skoda Hull* > 01482 802000 | *Skoda Grimsby* 01472 803 545 | *SEAT Grimsby* 01472 > 348 348 | *Honda Grimsby* 01472 358 625 | *SEAT MO* 01472 348 348 | > *Trade Car Outlet Ossett* 01924 255476 | *Ringways Hire & Leasing Ltd* > 0344 4146789. > > /This email message is confidential and may contain legally privileged > information. It may be monitored (whether you are the sender or > recipient) and recorded and retained by D.M.Keith Ltd, Ringways > Garages (Leeds) Ltd, Ringways Garages (Doncaster) Ltd, Ringways Hire & > Leasing Limited and or its other Group Companies. Under the “Lawful > Business Practices Interception of Communication Regulations 2000” > email and telephone monitoring and or recording software may be used, > and email or telephone call content may be reviewed at any time. If > you are not the intended recipient you should not read, copy, > distribute, disclose or otherwise use the information in this e-mail. > Please also contact D.M.Keith Ltd by emailing _privacy(a)dmkeith.com_ or > fax us on 0113 2703641, immediately and delete the message from your > system. Copyright in this email belongs to D.M.Keith Ltd., ALL RIGHTS > RESERVED. Whilst every effort has been made to check for viruses, > D.M.Keith Ltd and its Group Companies does not warrant that it is free > of viruses. E-mail may be susceptible to data corruption, interception > and unauthorised amendment, and we do not accept liability for any > such corruption, interception or amendment or the consequences > thereof. D.M. Keith Ltd is registered under the Data Protection Act > 1998 registration No. Z7389610, Ringways Garages (Leeds) Ltd is > registered under the Data Protection Act 1998 registration No. > Z5414640 , Ringways Garages (Doncaster) Ltd is registered under the > Data Protection Act 1998 registration No. Z5414654. D.M.Keith Limited > and its other Group companies are an appointed representative of ITC > Compliance Limited which is authorised and regulated by the Financial > Conduct Authority (their registration number is 313486). Permitted > activities include advising on and arranging general insurance > contracts and acting as a credit broker not a lender. We can introduce > you to a limited number of finance providers. We do not charge fees > for our Consumer Credit services. We may receive a payment(s) or other > benefits from finance providers should you decide to enter into an > agreement with them, typically either a fixed fee or a fixed > percentage of the amount you borrow. The payment we receive may vary > between finance providers and product types. The payment received does > not impact the finance rate offered. All finance applications are > subject to status, terms and conditions apply, UK residents only, 18’s > or over, Guarantees may be required. D.M. Keith Ltd and its group > companies are as follows: - D M Keith Ltd, Company registration No. > 00749256 Registered office, Thwaite Gate, Leeds, LS10 1DY. Ringways > Garages (Leeds) Ltd, Company registration No. 00543323 trading as D M > Keith Kia Leeds and D M Keith Ford Leeds Registered office, Whitehall > Road, Leeds, LS12 5NL. Ringways Garages (Doncaster) Ltd, Company > registration No. 00282527 trading as D M Keith Kia Doncaster. > Registered office, Whitehall Road, Leeds, LS12 5NL, Ringways (HIRE & > LEASING) LTD, company registration No. 00470274, Registered Office, > Whitehall Road, Leeds, LS12 5NL. All group companies VAT registration > No. 169785889. All goods and services are sold subject to our > Conditions of Sale which can be found along with our; Data Protection > Policy, Security Policy, Privacy & Cookie Policy, Anti-Slavery > Human-Trafficking Statement, Job Applicant Privacy Notice, Gender Pay > Gap Statement, Treating Customers Fairly Policy & FCA Status > Disclosure. These can be found on the link > _https://www.dmkeith.com/website-privacy-and-legal-information_ E&O.E./ >

2 1

PHP-LDAP RPM installed but not usable
by Gary Stainburn 20 Mar '23

20 Mar '23

Hi folks. I've installed PHP 8.0 on my server, and just installed php-ldap. All looks to have worked fine. php-common-8.0.28-1.el7.remi.x86_64 php-8.0.28-1.el7.remi.x86_64 php80-php-common-8.0.28-1.el7.remi.x86_64 php80-php-ldap-8.0.28-1.el7.remi.x86_64 php-cli-8.0.28-1.el7.remi.x86_64 php-sodium-8.0.28-1.el7.remi.x86_64 php80-runtime-1.0-3.el7.remi.x86_64 However, when I try to use LDAP in a script, it says the ldap_connect function is not available: [root@testsvr ~]# ./ldapAuth.php gary.stainburn fake-password PHP Warning: PHP Startup: Unable to load dynamic library 'ldap' (tried: /usr/lib64/php/modules/ldap (/usr/lib64/php/modules/ldap: cannot open shared object file: No such file or directory), /usr/lib64/php/modules/ldap.so (/usr/lib64/php/modules/ldap.so: cannot open shared object file: No such file or directory)) in Unknown on line 0 PHP Fatal error: Uncaught Error: Call to undefined function ldap_connect() in /root/ldapAuth.php:12 Can anyone see what I've missed?

1 0

Kernel updates do not boot - always boots oldest kernel
by Rob Kampen 18 Mar '23

18 Mar '23

This issue has been around for some months, but other things keep crowding out a fix. uname give me 3.10.0-1160.36.2.el7.x86_64 #1 SMP Wed Jul 21 11:57:15 UTC 2021 yet I have 3.10.0-1160.76.1.el7.x86_64 3.10.0-1160.81.1.el7.x86_64 3.10.0-1160.83.1.el7.x86_64 3.10.0-1160.88.1.el7.x86_64 loaded. The system uses UEFI to boot. sudo ls -l /sys/firmware/efi gives: total 0 -r--r--r--. 1 root root 4096 Feb 19 16:47 config_table drwxr-xr-x. 2 root root 0 Feb 19 16:47 efivars -r--r--r--. 1 root root 4096 Mar 14 17:57 fw_platform_size -r--r--r--. 1 root root 4096 Feb 19 16:47 fw_vendor drwxr-xr-x. 2 root root 0 Mar 14 17:57 mok-variables -r--r--r--. 1 root root 4096 Feb 19 16:47 runtime drwxr-xr-x. 9 root root 0 Feb 19 16:47 runtime-map -r--------. 1 root root 4096 Feb 19 16:47 systab drwxr-xr-x. 65 root root 0 Mar 14 17:57 vars and sudo efibootmgr gives: BootCurrent: 000F BootOrder: 000F,000D,000B,000E,0008,0000,0002,0003,0004,0005,0006,0007 Boot0000* CD/DVD Rom Boot0002* PXE Network Boot0003 Enter Setup Boot0004 Boot Devices Boot0005 Boot Manager Boot0006 Setup Boot0007 Diagnostics Boot0008* Embedded Hypervisor Boot000B* CentOS Linux Boot000D* CentOS-AltDrv Boot000E* Hard Disk 3 Boot000F* CentOS-MainDrv This is a remote server, thus I need a sure fire fix. My previous attempts have either had no impact - the old kernel boots or machine hangs and I need to do a trip to the site. Now this issue could be a residual from my initial setup when I installed 2 by 3.x TB SSD and needed to manually change from bios/grub2 boot to UEFI. I have already spent 10's of hours on this system, just want to have it run the latest kernels - for obvious reasons. Some other items: sudo grep "^menuentry" /boot/grub2/grub.cfg | cut -d "'" -f2 gives: CentOS Linux (3.10.0-1160.88.1.el7.x86_64) 7 (Core) CentOS Linux (3.10.0-1160.83.1.el7.x86_64) 7 (Core) CentOS Linux (3.10.0-1160.81.1.el7.x86_64) 7 (Core) CentOS Linux (3.10.0-1160.76.1.el7.x86_64) 7 (Core) CentOS Linux (3.10.0-1160.36.2.el7.x86_64) 7 (Core) CentOS Linux (0-rescue-a39773847cf34651bc34d02222566f53) 7 (Core) indicating that .88.1 should boot. sudo grub2-editenv list gives: saved_entry=CentOS Linux (3.10.0-1160.88.1.el7.x86_64) 7 (Core) also as expected. /etc/default/grub exists and contains 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="crashkernel=auto rd.md.uuid=066ffecb:69137a0b:4e579b4f:dfbf1696 rd.md.uuid=bd87f682:e6df10e2:d2a6e247:834133f7 rhgb quiet" GRUB_DISABLE_RECOVERY="true" the /boot/grub2/grubenv contains # GRUB Environment Block saved_entry=CentOS Linux (3.10.0-1160.88.1.el7.x86_64) 7 (Core) ####################################################################################################################################################################################################################################################################################################################################################################################################################################################################################################################################################################################################################################################################################################################################################################################################################################################################################################################################################################### All these point to the correct version of the kernel but always boots the old .36.2 version. Just realized these files only relate to BIOS boot, and my system is UEFI boot. Now documentation seems to get scarce. seems like the boot files are now residing in /boot/efi/EFI/centos AND /boot/efi2/EFI/centos although looking at timestamps the latter directory is not being updated. /boot/efi/EFI/centos contains total 7028 -rwx------. 1 root root 134 Aug 1 2020 BOOT.CSV -rwx------. 1 root root 134 Aug 1 2020 BOOTX64.CSV drwx------. 2 root root 4096 Dec 23 22:01 fonts -rwx------. 1 root root 8589 Mar 14 17:51 grub.cfg -rwx------. 1 root root 1024 Aug 26 2021 grubenv -rwx------. 1 root root 1125704 Dec 17 06:13 grubx64.efi -rwx------. 1 root root 1154640 Aug 1 2020 mmx64.efi -rwx------. 1 root root 1154640 Aug 1 2020 MokManager.efi -rwx------. 1 root root 1243864 Aug 1 2020 shim.efi -rwx------. 1 root root 1237824 Aug 1 2020 shimx64-centos.efi -rwx------. 1 root root 1243864 Aug 1 2020 shimx64.efi and we see that the grub.cfg is being updated. However, here the grubenv file contains # GRUB Environment Block saved_entry=CentOS Linux (3.10.0-1160.36.2.el7.x86_64) 7 (Core) ####################################################################################################################################################################################################################################################################################################################################################################################################################################################################################################################################################################################################################################################################################################################################################################################################################################################################################################################################################################### So maybe I have the reason. Now how to cure?? I can obviously edit this file to point to the latest kernel, but this would likely need to be done each time I update the system and get a new kernel - not my preferred option. How come the BIOS boot files are updated each time, but not the UEFI based one?? Well grub.cfg is, but not grubenv Can I edit /etc/default/grub and change GRUB_DEFAULT=saved to something else? Stumped. I think I have some basic UEFI install stuff missing, but back when I manually changed the boot system from BIOS to UEFI I was told only anaconda does this at install time, and I was unwilling to do a complete reinstall on an already in production system. So after much trial, I did get it booting reliably, just this one issues remains. Any pointers appreciated. TIA Rob.

6 8

PHP error message when running yum update on CentOS 7
by H 17 Mar '23

17 Mar '23

Running yum update on a CentOS 7.9 server today I encountered the following error: PHP Warning: PHP Startup: Unable to load dynamic library 'imap.so' (tried: /usr/lib64/php/modules/imap.so (/usr/lib64/php/modules/imap.so: cannot open shared object file: No such file or directory), /usr/lib64/php/modules/imap.so.so (/usr/lib64/php/modules/imap.so.so: cannot open shared object file: No such file or directory)) in Unknown on line 0 How do I handle this error? Thank you.

2 1

Re: [CentOS] Mount removed raid disk back on same machine as? original raid
by Bowie Bailey 17 Mar '23

17 Mar '23

On 3/14/2023 10:03 AM, Robert Heller wrote: > At Tue, 14 Mar 2023 09:50:33 -0400 Bowie Bailey <Bowie_Bailey(a)BUC.com>,? CentOS mailing list <centos(a)centos.org> wrote: > >> I know I will have to bring the drive online as a broken array, but I've >> done that from other systems.Ã‚Â The only question there is can I simply >> rebuild it with a different name.Ã‚Â I assume I can just do "mdadm -A >> --run /dev/md0 /dev/sdc1" (possibly with "--force" due to the broken >> array) even if sdc1 was originally part of the existing md127 array? > This should work. Unfortunately, no. The system would not mount the drive without some other changes. Listing the process here for anyone else who comes across this thread. Trying to start the array (with or without --force), fails with the message: mdadm: Found some drive for an array that is already active: /dev/md127 mdadm: giving up I found with some digging that I needed to change the UUID of the drive to be able to mount it separately from the existing array. I used "sgdisk -G /dev/sdg1" to do this. It worked, but gave quite a few scary warning messages in the process. A better idea would have been to use uuidgen to generate a random uuid and then start the array like this: mdadm --assemble /dev/md99 --update=uuid --uuid=<newuuid> /dev/sdg1 (might require --force for a broken array, I'm not sure since I didn't actually do it this way) Once the array is running, there is another problem. Attempting to mount the array gives another error: mount: wrong fs type, bad option, bad superblock on /dev/md99, missing codepage or helper program, or other error Useless error message. You have to look in dmesg to see the actual problem: XFS (md99): Filesystem has duplicate UUID 7e237dbd-6c24-4781-98d1-a1ae80a3ed13 - can't mount I would assume you would have a similar issue with any other filesystem. In my case, since it is XFS, I used uuidgen to generate another random uuid and then updated it like this: xfs_admin -U <newuuid> /dev/md99 After that, the filesystem mounted normally. Hopefully that is helpful for anyone else who finds themselves in this situation. -- Bowie

1 0

vault.centos.org down ?
by James Pearson 14 Mar '23

14 Mar '23

I'm getting 'Forbidden You don't have permission to access this resource.' when accessing https://vault.centos.org/ Is it down ? Thanks James Pearson

3 2

Mount removed raid disk back on same machine as original raid
by Bowie Bailey 14 Mar '23

14 Mar '23

I have a Centos 7 system with an mdraid array (raid 1). I removed a drive from it a couple of months ago and replaced it with a new drive. Now I want to recover some information from that old drive. I know how to mount the drive, and have done so on another system to confirm that the information I want is there. My question is this: What is going to happen when I try to mount a drive that the system thinks is part of an existing array? To put it another way: I had two drives in md127. I removed one (call it drive1), and replaced it with a new drive. Some files were accidentally deleted from md127, so now I want to connect drive1 back to the same machine and mount it as a separate array from md127 so I can copy the files from drive1 back to md127. What do I need to do to make that happen? Thanks, Bowie

2 2

← Newer
1
...
8
9
10
11
12
13
14
...
3473
Older →

Jump to page:

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

2005

2004

Discuss