Discuss November 2020

discuss@lists.centos.org

71 participants
57 discussions

CentOS-announce Digest, Vol 188, Issue 4
by centos-announce-request＠centos.org 20 Nov '20

20 Nov '20

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. CEBA-2020:5154 CentOS 7 gnome-shell BugFix Update (Johnny Hughes) 2. CEBA-2020:5154 CentOS 7 mutter BugFix Update (Johnny Hughes) 3. CEBA-2020:5154 CentOS 7 gdm BugFix Update (Johnny Hughes) 4. CESA-2020:5083 Moderate CentOS 7 microcode_ctl Security Update (Johnny Hughes) 5. CESA-2020:5099 Critical CentOS 7 firefox Security Update (Johnny Hughes) ---------------------------------------------------------------------- Message: 1 Date: Thu, 19 Nov 2020 13:47:14 +0000 From: Johnny Hughes <johnny(a)centos.org> To: centos-announce(a)centos.org Subject: [CentOS-announce] CEBA-2020:5154 CentOS 7 gnome-shell BugFix Update Message-ID: <20201119134714.GA25005(a)bstore1.rdu2.centos.org> Content-Type: text/plain; charset=us-ascii CentOS Errata and Bugfix Advisory 2020:5154 Upstream details at : https://access.redhat.com/errata/RHBA-2020:5154 The following updated files have been uploaded and are currently syncing to the mirrors: ( sha256sum Filename ) x86_64: 68b19039b1e53465dc3f08f0e56e24f7e1672b449a51dd05f8ae10ff49416b66 gnome-shell-3.28.3-32.el7.x86_64.rpm Source: 09eaee6b53a8debe898a03e6cbb1a0af1167a5e73d999abb4e5e8cc4de21829a gnome-shell-3.28.3-32.el7.src.rpm -- Johnny Hughes CentOS Project { http://www.centos.org/ } irc: hughesjr, #centos(a)irc.freenode.net Twitter: @JohnnyCentOS ------------------------------ Message: 2 Date: Thu, 19 Nov 2020 13:47:26 +0000 From: Johnny Hughes <johnny(a)centos.org> To: centos-announce(a)centos.org Subject: [CentOS-announce] CEBA-2020:5154 CentOS 7 mutter BugFix Update Message-ID: <20201119134726.GA25114(a)bstore1.rdu2.centos.org> Content-Type: text/plain; charset=us-ascii CentOS Errata and Bugfix Advisory 2020:5154 Upstream details at : https://access.redhat.com/errata/RHBA-2020:5154 The following updated files have been uploaded and are currently syncing to the mirrors: ( sha256sum Filename ) x86_64: eb48815ca014d65a115c0ac9dba6f0c28dc765fbc161fc9ac11d3573786c6b4a mutter-3.28.3-30.el7.i686.rpm 42bfea454da2eacfb32d84a41908a2e6d89c8e46d04ea6a5ccefa5e251b3f3f9 mutter-3.28.3-30.el7.x86_64.rpm ca6edad606ed1ae0aad8a9ae177f501264d15718f85d304957942d0ed5768647 mutter-devel-3.28.3-30.el7.i686.rpm 2b4e66ff61ba4a7722ed44b9ca9487b146ddcbe7bc27c08a8b07be8049b546e7 mutter-devel-3.28.3-30.el7.x86_64.rpm Source: 82a4e302b32ea01c09871d4ecca9b3c7a43c555ad56b6805d4bb3f9699c0178f mutter-3.28.3-30.el7.src.rpm -- Johnny Hughes CentOS Project { http://www.centos.org/ } irc: hughesjr, #centos(a)irc.freenode.net Twitter: @JohnnyCentOS ------------------------------ Message: 3 Date: Thu, 19 Nov 2020 13:47:40 +0000 From: Johnny Hughes <johnny(a)centos.org> To: centos-announce(a)centos.org Subject: [CentOS-announce] CEBA-2020:5154 CentOS 7 gdm BugFix Update Message-ID: <20201119134740.GA25234(a)bstore1.rdu2.centos.org> Content-Type: text/plain; charset=us-ascii CentOS Errata and Bugfix Advisory 2020:5154 Upstream details at : https://access.redhat.com/errata/RHBA-2020:5154 The following updated files have been uploaded and are currently syncing to the mirrors: ( sha256sum Filename ) x86_64: aa4d5c25ee0ab0c6200041d7babcc2186123b17af2126662b27bed0013787faa gdm-3.28.2-26.el7.i686.rpm d9df089dfd6da09a0d335f5f7217eb49fb786af4bc6bdc86f8f5780e9588cb54 gdm-3.28.2-26.el7.x86_64.rpm b3523f6bd479abca1bc4c70f870af2423e9747ad2cb185692334588138742f50 gdm-devel-3.28.2-26.el7.i686.rpm 9a97f6e2d20a2e98ad20844706c47bf2fc689c6975c67067aa46d4ab03c1e47a gdm-devel-3.28.2-26.el7.x86_64.rpm 570aef75009a72d1f785eeeb0cf1e9b1c5113c73c46a3a7c2eebe0f87a44655b gdm-pam-extensions-devel-3.28.2-26.el7.i686.rpm 9b205c9658e9caf5ecd6d928179b7e7b36aa629b18e33540805f21a0d0b9f939 gdm-pam-extensions-devel-3.28.2-26.el7.x86_64.rpm Source: 7299b27241d70ab051693e3987cc595e044eb8061493cd6809befd2e25892119 gdm-3.28.2-26.el7.src.rpm -- Johnny Hughes CentOS Project { http://www.centos.org/ } irc: hughesjr, #centos(a)irc.freenode.net Twitter: @JohnnyCentOS ------------------------------ Message: 4 Date: Thu, 19 Nov 2020 13:47:47 +0000 From: Johnny Hughes <johnny(a)centos.org> To: centos-announce(a)centos.org Subject: [CentOS-announce] CESA-2020:5083 Moderate CentOS 7 microcode_ctl Security Update Message-ID: <20201119134747.GA25323(a)bstore1.rdu2.centos.org> Content-Type: text/plain; charset=us-ascii CentOS Errata and Security Advisory 2020:5083 Moderate Upstream details at : https://access.redhat.com/errata/RHSA-2020:5083 The following updated files have been uploaded and are currently syncing to the mirrors: ( sha256sum Filename ) x86_64: 09b0a412ef431cf5907e6d41f5bf960d051927c73b0a292dea9a52585f306e01 microcode_ctl-2.1-73.2.el7_9.x86_64.rpm Source: d7e8ae266d767b1645e22f0b18f229df0ef8289c742b7b3e7b434047a1270a7c microcode_ctl-2.1-73.2.el7_9.src.rpm -- Johnny Hughes CentOS Project { http://www.centos.org/ } irc: hughesjr, #centos(a)irc.freenode.net Twitter: @JohnnyCentOS ------------------------------ Message: 5 Date: Thu, 19 Nov 2020 13:49:09 +0000 From: Johnny Hughes <johnny(a)centos.org> To: centos-announce(a)centos.org Subject: [CentOS-announce] CESA-2020:5099 Critical CentOS 7 firefox Security Update Message-ID: <20201119134909.GA25485(a)bstore1.rdu2.centos.org> Content-Type: text/plain; charset=us-ascii CentOS Errata and Security Advisory 2020:5099 Critical Upstream details at : https://access.redhat.com/errata/RHSA-2020:5099 The following updated files have been uploaded and are currently syncing to the mirrors: ( sha256sum Filename ) x86_64: 54c6e6aa53fe175c25dc35fe3f6476d9b195d85a4fc5e64d5625d1731cc5b1ce firefox-78.4.1-1.el7.centos.i686.rpm d8f95fca6716286e91c7ab7b9be9bd359800c870cc0bdb90128bf93397e9352d firefox-78.4.1-1.el7.centos.x86_64.rpm Source: 48cf4a93202542b3895382c41bdb9659a38b32186aca558fd35b15d62ddafafe firefox-78.4.1-1.el7.centos.src.rpm -- Johnny Hughes CentOS Project { http://www.centos.org/ } irc: hughesjr, #centos(a)irc.freenode.net 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 188, Issue 4 ***********************************************

1 0

server rebooted email
by Kenneth Porter 19 Nov '20

19 Nov '20

I used to put a line in rc.local to email root that my server rebooted. Does anyone have a nice systemd unit file to do the same? Also useful would be a shutdown email with the output of uptime. (I usually do that manually when rebooting for a kernel update.)

3 2

Help with VirtualBox on CentOS 7
by Jerry Geis 19 Nov '20

19 Nov '20

Any Virtualbox on CentOS guru's out there? I only have 1 VM on my linux host. in the update process to virtualbox 6.1.16 my config was lost. When I run Virtualbox my VM does not show. So I desire to add it back. My structure is this. ls -l /home/silentm/vmware/CentOS\ 64-bit\ LSI/ -rw------- 1 silentm silentm 8684 Aug 13 08:31 CentOS 64-bit LSI.nvram -rw-r--r-- 1 silentm silentm 0 Feb 27 2017 CentOS 64-bit LSI.vmsd -rwxr-xr-x 1 silentm silentm 2735 Aug 13 08:31 CentOS 64-bit LSI.vmx -rw-r--r-- 1 silentm silentm 272 Feb 27 2017 CentOS 64-bit LSI.vmxf -rw-r--r-- 1 silentm silentm 32796639232 Nov 17 08:34 CentOS 7-64bit LSI.vmdk -rw-r--r-- 1 silentm silentm 107382571008 Aug 13 09:05 CentOS 7.vhdx -rw-r--r-- 1 silentm silentm 323155 Aug 5 08:39 vmware-0.log -rw-r--r-- 1 silentm silentm 323085 Jun 30 14:14 vmware-1.log -rw-r--r-- 1 silentm silentm 256013 May 31 10:09 vmware-2.log -rw-r--r-- 1 silentm silentm 322239 Aug 13 08:31 vmware.log When I click add and goto the directory above - IT ONLY wants to add *.xml and *.vbox. So that is no good. When I click New and Enter my name, and use existing disk - it does not like that either. How can I get this same VM to be in my menu and run again ? Thanks, Jerry

3 3

(C8) root on mdraid
by Łukasz Posadowski 18 Nov '20

18 Nov '20

Hello everyone. I'm trying to install CentOS 8 with root and swap partitions on software raid. The plan is: - create md0 raid level 1 with 2 hard drives: /dev/sda and /dev/sdb, using Linux Rscue CD, - install CentOS 8 with Virtual Box on my laptop, - rsync CentOS 8 root partition on /dev/md0p1, - chroot in CentOS 8 root partition, - configure /etc/mdadm.conf, grub.cfg, initramfs, install bootloader on both sda and sdb drives. I think I can do first four of the above, but my CentOS installation acts strange after rebooting the server. It recognizes the raid, but boots randomly with root on /dev/sda1 (and recognizes raid with /dev/sdb disk), or with root on /dev/sdb1 (and recognizes raid with /dev/sda disk). When booting from Linux Rescue CD, the raid with two disk is recognized. Creating md0 wth Linux Rescue CD. # lsblk NAME MAJ:MIN RM SIZE RO TYPE MOUNTPOINT loop0 7:0 0 819.5M 1 loop /run/archiso/sfs/airootfs sda 8:0 0 232.9G 0 disk sdb 8:16 0 232.9G 0 disk sr0 11:0 1 871M 0 rom # mdadm --create /dev/md0 --level=1 --raid-devices=2 --metadata=0.9 /dev/sda /dev/sdb mdadm: array /dev/md0 started. # mdadm --detail --scan --verbose ARRAY /dev/md0 level=raid1 num-devices=2 metadata=0.90 UUID=fef2f68b: 1a462c80:c44c77eb:7ee19756 devices=/dev/sda,/dev/sdb # cat /proc/mdstat Personalities : [raid1] md0 : active raid1 sdb[1] sda[0] 244198464 blocks [2/2] [UU] [>....................] resync = 1.9% (4682944/244198464) finish=52.2min speed=76356K/sec bitmap: 2/2 pages [8KB], 65536KB chunk unused devices: <none> (1 hour later) # cat /proc/mdstat Personalities : [raid1] md0 : active raid1 sdb[1] sda[0] 244198464 blocks [2/2] [UU] bitmap: 0/2 pages [0KB], 65536KB chunk unused devices: <none> # lsblk NAME MAJ:MIN RM SIZE RO TYPE MOUNTPOINT loop0 7:0 0 819.5M 1 loop /run/archiso/sfs/airootfs sda 8:0 0 232.9G 0 disk └─md0 9:0 0 232.9G 0 raid1 sdb 8:16 0 232.9G 0 disk └─md0 9:0 0 232.9G 0 raid1 sr0 11:0 1 871M 0 rom --------------------------------- So far so good. Now partitions: # fdisk /dev/md0 Welcome to fdisk (util-linux 2.33.1). Changes will remain in memory only, until you decide to write them. Be careful before using the write command. Device does not contain a recognized partition table. Created a new DOS disklabel with disk identifier 0x64998720. Command (m for help): o Created a new DOS disklabel with disk identifier 0xfe784f57. Command (m for help): n Partition type p primary (0 primary, 0 extended, 4 free) e extended (container for logical partitions) Select (default p): p Partition number (1-4, default 1): First sector (2048-488396927, default 2048): Last sector, +/-sectors or +/-size{K,M,G,T,P} (2048-488396927, default 488396927): +220G Created a new partition 1 of type 'Linux' and of size 220 GiB. Command (m for help): n Partition type p primary (1 primary, 0 extended, 3 free) e extended (container for logical partitions) Select (default p): p Partition number (2-4, default 2): First sector (461375488-488396927, default 461375488): Last sector, +/-sectors or +/-size{K,M,G,T,P} (461375488-488396927, default 488396927): +4G Created a new partition 2 of type 'Linux' and of size 4 GiB. Command (m for help): w The partition table has been altered. Calling ioctl() to re-read partition table. Syncing disks. # lsblk NAME MAJ:MIN RM SIZE RO TYPE MOUNTPOINT loop0 7:0 0 819.5M 1 loop /run/archiso/sfs/airootfs sda 8:0 0 232.9G 0 disk └─md0 9:0 0 232.9G 0 raid1 ├─md0p1 259:0 0 220G 0 part └─md0p2 259:1 0 4G 0 part sdb 8:16 0 232.9G 0 disk └─md0 9:0 0 232.9G 0 raid1 ├─md0p1 259:0 0 220G 0 part └─md0p2 259:1 0 4G 0 part sr0 11:0 1 871M 0 rom # mkfs -t ext4 /dev/md0p1 mke2fs 1.44.5 (15-Dec-2018) Creating filesystem with 57671680 4k blocks and 14417920 inodes Filesystem UUID: 511d0d07-4d55-4b6c-939e-d23ae2da1ce0 Superblock backups stored on blocks: 32768, 98304, 163840, 229376, 294912, 819200, 884736, 1605632, 2654208, 4096000, 7962624, 11239424, 20480000, 23887872 Allocating group tables: done Writing inode tables: done Creating journal (262144 blocks): done Writing superblocks and filesystem accounting information: done # mkswap /dev/md0p2 Setting up swapspace version 1, size = 4 GiB (4294963200 bytes) no label, UUID=5667d007-0d3e-4b54-8a72-6ade52609adc -------------------------------------- Mount would be root partition: # mkdir /mnt/centos8 # mount -t ext4 /dev/md0p1 /mnt/centos8/ -------------------------------------- OK, I have what I need. Now log into virtualised CentOS 8 in Virtual Box. # rpm -q rsync rsync-3.1.3-7.el8.x86_64 # rpm -q mdadm mdadm-4.1-13.el8.x86_64 # rsync -vaxAXHSz --delete / 192.168.111.167:/mnt/centos8/ The authenticity of host '192.168.111.167 (192.168.111.167)' can't be established. ECDSA key fingerprint is SHA256:HukswAQlarthYqbpVHIHm80JaWHKX12AxgOn8UuKQxk. Are you sure you want to continue connecting (yes/no/[fingerprint])? yes Warning: Permanently added '192.168.111.167' (ECDSA) to the list of known hosts. root(a)192.168.111.167's password: sending incremental file list ./ bin -> usr/bin lib -> usr/lib lib64 -> usr/lib64 sbin -> usr/sbin [lots and lots of files...] var/yp/ sent 694,980,592 bytes received 745,802 bytes 1,795,422.95 bytes/sec total size is 1,558,934,091 speedup is 2.24 -------------------------------------- Chrooting time: # mount --types proc /proc /mnt/centos8/proc # mount --rbind /sys /mnt/centos8/sys # mount --make-rslave /mnt/centos8/sys # mount --rbind /dev /mnt/centos8/dev # mount --make-rslave /mnt/centos8/dev # chroot /mnt/centos8 /usr/bin/bash # source /etc/profile Configure raid: # mdadm --detail --scan --verbose ARRAY /dev/md0 level=raid1 num-devices=2 metadata=0.90 UUID=fef2f68b: 1a462c80:c44c77eb:7ee19756 devices=/dev/sda,/dev/sdb # mdadm --detail --scan --verbose > /etc/mdadm.conf Edit /etc/fstab: # cat /etc/fstab # # /etc/fstab # Created by anaconda on Sun Nov 8 10:05:31 2020 # # Accessible filesystems, by reference, are maintained under # '/dev/disk/'. See man pages fstab(5), findfs(8), mount(8) and/or # blkid(8) for more info. # # After editing this file, run 'systemctl daemon-reload' to update # systemd units generated from this file. # #UUID=36c5a887-79c3-4b6a-b433-0e4d7574b1e4 / #ext4 defaults 1 1 /dev/md0p1 / ext4 defaults 1 1 Configure and install bootloader: # cat /etc/default/grub GRUB_TIMEOUT=8 GRUB_DISTRIBUTOR="$(sed 's, release .*$,,g' /etc/system-release)" GRUB_DEFAULT=saved GRUB_DISABLE_SUBMENU=true GRUB_TERMINAL_OUTPUT="console" GRUB_CMDLINE_LINUX="rhgb quiet" GRUB_DISABLE_RECOVERY="true" GRUB_ENABLE_BLSCFG=true # grub2-mkconfig -o /boot/grub2/grub.cfg Generating grub configuration file ... done # grub2-install /dev/sda Installing for i386-pc platform. Installation finished. No error reported. # grub2-install /dev/sdb Installing for i386-pc platform. Installation finished. No error reported. Configure initramfs: # dracut -f /boot/initramfs-4.18.0-193.28.1.el8_2.x86_64.img # 4.18.0-193.28.1.el8_2.x86_64 -------------------------------- Reboot and login to my new CentOS 8 installation: # lsblk NAME MAJ:MIN RM SIZE RO TYPE MOUNTPOINT sda 8:0 0 232.9G 0 disk sdb 8:16 0 232.9G 0 disk ├─sdb1 8:17 0 220G 0 part / └─sdb2 8:18 0 4G 0 part sr0 11:0 1 871M 0 rom # mdadm --detail --scan --verbose INACTIVE-ARRAY /dev/md127 num-devices=1 metadata=0.90 UUID=fef2f68b: 1a462c80:c44c77eb:7ee19756 devices=/dev/sda # cat /proc/mdstat Personalities : md127 : inactive sda[0](S) 244198464 blocks unused devices: <none> I can live with md127, because it happens constantly on multiple distributions, but why root is on /dev/sdb1 (and sometimes it's /dev/sda1)? I'm running out of spells now. :) Do anyone can suggest what else I forgot to do? thanks -- Łukasz Posadowski

5 8

Intel RST RAID 1, partition tables and UUIDs
by H 18 Nov '20

18 Nov '20

I have been having some problems with hardware RAID 1 on the motherboard that I am running CentOS 7 on. After a BIOS upgrade of the system, I lost the RAID 1 setup and was no longer able to boot the system. Testdisk revealed that the partition tables had been damaged and because I had earlier saved information from fdisk, I was able to recreate the partitions. However, booting into the BIOS and recreating/synchronizing the RAID from one of the disks (took around 20 hours for 256 GB disks), I again lost the ability the boot and the partition tables were similarly damaged. Eventually I was able to boot the system again from one of the two disks and it is now up and running, now running without RAID. - Should I expect that the Intel RAID 1 setup changes the partition tables? I should add that the disks were originally created after the RAID 1 was setup. - After fooling around with testdisk (and prior to that, parted), it turned out that I had lost the disk UUID for both disks, they were both set to 000... Partition UUIDs seemed unchanged from before, including the LUKS partitions. Are disk UUIDs (not partition UUIDs) not used by Linux since I have not - yet - seen any effects of the missing disk UUIDs? Because there seems to be a couple of other issues with the motherboard, I expect to have it replaced early this week but I am still interested in learning more. Thanks.

5 8

Best practice preparing for disk restoring system
by H 18 Nov '20

18 Nov '20

Short of backing up entire disks using dd, I'd like to collect all required information to make sure I can restore partitions, disk information, UUIDs and anything else required in the event of losing a disk. So far I am collecting information from: - fdisk -l - blkid - lsblk - grub2-efi.cfg - grub - fstab Hoping that this would supply me with /all/ information to restore a system - with the exception of installed operating system, apps and data. I would appreciate any and all thoughts on the above!

6 9

why does virtual console start affect graphical start up?
by Kay Schenk 17 Nov '20

17 Nov '20

Hello all-- I have 3 CentOs 8 kernels insalled on my new machine -- 1. 4.18.0-193.14.2.el8_2.x86_6 2. 4.18.0-193.19.1.el8_2.x86_64 << using this one for this graphical boot 3. 4.18.0-193.28.1.el8_2.x86_64 Only #3 will boot without a *Virtual console can not start *error message but it hangs up trying to get into graphical mode, although it will boot to multi-user. The first 2 seem to work reaosnably well in either graphical or multi-user but I get a *Virtual console can not start *in boot messages with both of these. Does anyone know anything about this? Having a heck of a time trying to prevent lock ups. Thanks. **

1 1

Apologies - possible hardware problem?
by Jeffrey Layton 16 Nov '20

16 Nov '20

Good afternoon, I have a home workstation with an AMD CPU, Titan V GPU, 32 GB of memory, and a root SSD and /home on spinning disks. Right now it has xubuntu 18.04 on it and it would boot fine. I shut it down and restarted it to get an inventory before I put CentOS 8.2 on it. It won't boot now. It gets to the grub menu and freezes. I can't use the keyboard to select an item in the menu and I can't press enter to make it boot or press "e" to edit the boot line. It just sits there (seemingly forever). Here's what I've tred: 1. New keyboard/mouse - no change 2. Different monitor - no change 3. Booting from the CentOS 8.2 iso on a USB stick - no change 4. Replacing the TItan V card with a GT 1030 NV card - no change When booting from a USB stick, I get the BIOS splash screen and press "DEL" to get to the menu, but the menu never shows up. It just freezes. This one has me stumped. Not being able to boot from a USB stick is really puzzling. I've never seen that before. Possible bad MB? My apologies for using the list to help debug problems but since I'm moving to CentOS 8.2 I thought people might have some ideas. TIA! Jeff

4 6

mdadm raid-check
by hw 16 Nov '20

16 Nov '20

Hi, is it required to run /usr/sbin/raid-check once per week? Centos 7 does this. Maybe it's sufficient to run it monthly? IIRC Debian did it monthly. I just checked on Fedora 32. It does not run raid-check at all, at least not via a cron entry. /usr/sbin/raid-check is available, though. Is that an oversight? (I started it manually now and will check if it's run once I update to 33.)

3 4

ssacli start rebuild?
by hw 15 Nov '20

15 Nov '20

Hi, is there a way to rebuild an array using ssacli with a P410? A failed disk has been replaced and now the array is not rebuilding like it should: Array A (SATA, Unused Space: 1 MB) logicaldrive 1 (14.55 TB, RAID 1+0, Ready for Rebuild) physicaldrive 1I:0:1 (port 1I:box 0:bay 1, SATA HDD, 4 TB, OK) physicaldrive 1I:0:2 (port 1I:box 0:bay 2, SATA HDD, 4 TB, OK) physicaldrive 1I:0:3 (port 1I:box 0:bay 3, SATA HDD, 4 TB, OK) physicaldrive 1I:0:4 (port 1I:box 0:bay 4, SATA HDD, 8 TB, OK) physicaldrive 2I:0:5 (port 2I:box 0:bay 5, SATA HDD, 4 TB, OK) physicaldrive 2I:0:6 (port 2I:box 0:bay 6, SATA HDD, 4 TB, OK) physicaldrive 2I:0:7 (port 2I:box 0:bay 7, SATA HDD, 4 TB, OK) physicaldrive 2I:0:8 (port 2I:box 0:bay 8, SATA HDD, 4 TB, OK) I'd expect the rebuild to start automatically after 1I:0:4 was replaced. Is the new drive being larger than the old one (4-->8) causing issues?

6 27

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

2005

2004

Discuss November 2020