similar to: Kernel panic after removing SW RAID1 partitions, setting up ZFS.

On 03/18/2020 09:19 AM, Jyrki Tikka wrote: > On Wed, 2020-03-18 at 07:31 -0400, Steve Clark wrote: >> Does anyone have access to the following that could help me with the >> issue I am having trying to >> use kdrc with vnc and emacs. >> VNC redraw issues with emacs on KDE >> https://access.redhat.com/solutions/1585893 >> > There is a workaround: > >

I agree with Liam. The good old tried and tested virt-manager will be obsoleted in the future but it is still available on RHEL/CentOS 8. Cockpit will replace it in the future but it still lacks a lot of essential features. Boxes is a tool that lacks even more functionality. As to why your computer freezes I have no clue. -- <(*) Jyrki On Sat, 2020-04-04 at 00:45 +0100, Liam O'Toole

On 2020-08-03 05:56, John Pierce wrote: > Legacy BIOS has its own set of issues, like no GPT support, MBR disks > are > max 2TB. I'm booting just fine on an old BIOS system from a pair (mdraid 1) of 3 TB GPT disks. The MBR compatibility on GPT disks allow the old machine to boot from a GPT disk and load GRUB. Then GRUB takes over and loads the kernel and the kernel has no

> In article <6566355.ijNRhnPfCt at tesla.schoolpathways.com>, > Benjamin Smith <lists at benjamindsmith.com> wrote: >> System is CentOS 6 all up to date, previously had two drives in MD RAID >> configuration. >> >> md0: sda1/sdb1, 20 GB, OS / Partition >> md1: sda2/sdb2, 1 TB, data mounted as /home >> >> Installed kmod ZFS via yum,

>I wanted to update my CentOS 7 install this morning and I started>getting the errors from below. >Any ideas on a fix? Certainly! >Error: Package: python34-xapps-overrides-1.0.4-13.el7.x86_64 (@epel) > Requires: xapps(x86-64) = 1.0.4-13.el7 > Removing: xapps-1.0.4-13.el7.x86_64 (@epel) > xapps(x86-64) = 1.0.4-13.el7 > Updated By:

System is CentOS 6 all up to date, previously had two drives in MD RAID configuration. md0: sda1/sdb1, 20 GB, OS / Partition md1: sda2/sdb2, 1 TB, data mounted as /home Installed kmod ZFS via yum, reboot, zpool works fine. Backed up the /home data 2x, then stopped the sd[ab]2 partition with: mdadm --stop /dev/md1; mdadm --zero-superblock /dev/sd[ab]1; Removed /home in /etc/fstab. Used

In article <6566355.ijNRhnPfCt at tesla.schoolpathways.com>, Benjamin Smith <lists at benjamindsmith.com> wrote: > System is CentOS 6 all up to date, previously had two drives in MD RAID > configuration. > > md0: sda1/sdb1, 20 GB, OS / Partition > md1: sda2/sdb2, 1 TB, data mounted as /home > > Installed kmod ZFS via yum, reboot, zpool works fine. Backed up

On Tuesday, April 9, 2019 2:53:55 AM PDT Simon Matter via CentOS wrote: > > I think it's because you clobbered md0 when you did --zero-superblock on > > sd[ab]1 > > instead of 2. As mentioned in another reply, this was a typo in the email, not on the machine. I drove to the site, picked up the machine, and last night found that the problem wasn't anything to do with

Does anyone have access to the following that could help me with the issue I am having trying to use kdrc with vnc and emacs. VNC redraw issues with emacs on KDE https://access.redhat.com/solutions/1585893 I can't access the portal since I am using CentOS. -- Stephen Clark Email Confidentiality Notice: The information contained in this transmission may contain privileged and confidential

On Sat, Apr 6, 2019 at 1:03 AM Jyrki Tikka <jyrki.tikka at iki.fi> wrote: > > >I wanted to update my CentOS 7 install this morning and I > started>getting the errors from below. > >Any ideas on a fix? > Certainly! > >Error: Package: python34-xapps-overrides-1.0.4-13.el7.x86_64 (@epel) > > Requires: xapps(x86-64) = 1.0.4-13.el7 > >

On Wed, 2020-03-18 at 09:28 -0400, Steve Clark wrote: > On 03/18/2020 09:19 AM, Jyrki Tikka wrote: > > On Wed, 2020-03-18 at 07:31 -0400, Steve Clark wrote: > > > Does anyone have access to the following that could help me with > > > the > > > issue I am having trying to > > > use kdrc with vnc and emacs. > > > VNC redraw issues with emacs on

(Resend: message didn't show, was my original message too big? Posted one of the output files to a website to see) The point of RAID1 is to allow for continued uptime in a failure scenario. When I assemble servers with RAID1, I set up two HDDs to mirror each other, and test by booting from each drive individually to verify that it works. For the OS partitions, I use simple partitions and

Greetings - Ok, I have my CentOS 7 KVM host system installed and I want to be able to boot the system from either installed drive if one of them fails. My objective is to have the following layout for the two 3 TB disks. sda1 /boot/efi sda2 /boot sda3 RAID1 with sdb3 sdb1 /boot/efi sdb2 /boot sdb3 RAID1 with sda3 The system is installed and boots from sda[1,2] and md127 (sda3 and

> Am 07.12.19 um 19:23 schrieb Kay Schenk: > > Hello all-- > > > > It seems using ctrl-alt-F1 to exit from GUI back to MY OWN > > SESSION'S > > command line does not work for me. It does nothing. > > > > Is this something that needs to be explicitly enabled? I start GUI > > using > > "startx". > > > > Also, any

Thanks Jyrki and Leroy. I tried to use cockpit but virt-manager seems easier. Is there a config file for cockpit? Where is it? On Sun, 2020-04-05 at 17:58 +0300, Jyrki Tikka wrote: > I agree with Liam. The good old tried and tested virt-manager will be > obsoleted in the future but it is still available on RHEL/CentOS 8. > Cockpit will replace it in the future but it still lacks a lot

Greetings, until yesterday I was running a btrfs filesystem across two 2.0 TiB disks in RAID1 mode for both metadata and data without any problems. As space was getting short I wanted to extend the filesystem by two additional drives lying around, which both are 1.0 TiB in size. Knowing little about the btrfs RAID implementation I thought I had to switch to RAID10 mode, which I was told is

I have a large disk full of data that I'd like to upgrade to SW RAID 1 with a minimum of downtime. Taking it offline for a day or more to rsync all the files over is a non-starter. Since I've mounted SW RAID1 drives directly with "mount -t ext3 /dev/sdX" it would seem possible to flip the process around, perhaps change the partition type with fdisk or parted, and remount as

On Wednesday, April 24, 2019 3:44:04 AM PDT Leon Fauster via CentOS wrote: > > Am 24.04.2019 um 08:37 schrieb Benjamin Smith <lists at benjamindsmith.com>: > > > > CentOS 7 server and Fedora 29 dev workstation, both with PHP 7.2, Apache > > 2.4, php-fpm, all updated. > > > > I have a web-based app I've been developing for some time, and recently >

On 12/5/18 11:55 AM, Benjamin Smith wrote: > The point of RAID1 is to allow for continued uptime in a failure scenario. > When I assemble servers with RAID1, I set up two HDDs to mirror each other, > and test by booting from each drive individually to verify that it works. For > the OS partitions, I use simple partitions and ext4 so it's as simple as > possible. I used my test

On 12/9/19 11:26 AM, Jyrki Tikka wrote: >> Am 07.12.19 um 19:23 schrieb Kay Schenk: >>> Hello all-- >>> >>> It seems using ctrl-alt-F1 to exit from GUI back to MY OWN >>> SESSION'S >>> command line does not work for me. It does nothing. >>> >>> Is this something that needs to be explicitly enabled? I start GUI >>>