Re: Restored f33 on new drive from a tarball now a problem

On 5/10/21 8:58 PM, Robert McBroom via users wrote: On 5/4/21 12:43 AM, Samuel Sieb wrote: On 2021-05-03 9:33 p.m., Robert McBroom via users wrote: To happy to soon, Did an update to get current and on reboot and login the entire system is read only. Looking at directories with emacs and all p

Re: Restored f33 on new drive from a tarball now a problem

On 5/4/21 12:43 AM, Samuel Sieb wrote: On 2021-05-03 9:33 p.m., Robert McBroom via users wrote: To happy to soon, Did an update to get current and on reboot and login the entire system is read only. Looking at directories with emacs and all permissions look fine but any attempt to write fails.

Re: Restored f33 on new drive from a tarball now a problem

On 2021-05-03 9:33 p.m., Robert McBroom via users wrote: To happy to soon, Did an update to get current and on reboot and login the entire system is read only. Looking at directories with emacs and all permissions look fine but any attempt to write fails. Check the log to see why.

Re: Restored f33 on new drive from a tarball now a problem

On 5/1/21 9:59 AM, Robert McBroom via users wrote: On 4/29/21 6:16 PM, Ed Greshko wrote: On 30/04/2021 04:17, Robert McBroom via users wrote: On 4/26/21 12:23 AM, Robert McBroom via users wrote: On 4/25/21 7:23 PM, Ed Greshko wrote: I have never tried using a tar file to restore.  However usin

Re: Restored f33 on new drive from a tarball now a problem

On 2021-04-25 4:09 p.m., Robert McBroom via users wrote: I can get to the F33 from an f31 install on the same computer, mounted on /mnt/sysimage and doing the binds to /dev, /proc, and /sys followed by chroot gets me in to look at everything. Everything I look into looks correct. Short of idea

Re: Restored f33 on new drive from a tarball now a problem

On 4/29/21 6:16 PM, Ed Greshko wrote: On 30/04/2021 04:17, Robert McBroom via users wrote: On 4/26/21 12:23 AM, Robert McBroom via users wrote: On 4/25/21 7:23 PM, Ed Greshko wrote: I have never tried using a tar file to restore.  However using tar (both creating and restoring) without using

Re: Restored f33 on new drive from a tarball now a problem

On 30/04/2021 04:17, Robert McBroom via users wrote: On 4/26/21 12:23 AM, Robert McBroom via users wrote: On 4/25/21 7:23 PM, Ed Greshko wrote: I have never tried using a tar file to restore.  However using tar (both creating and restoring) without using the --selinux parameter won't preserve

Re: Restored f33 on new drive from a tarball now a problem

On 4/26/21 12:23 AM, Robert McBroom via users wrote: On 4/25/21 7:23 PM, Ed Greshko wrote: On 26/04/2021 07:09, Robert McBroom via users wrote: On 4/25/21 5:34 PM, George N. White III wrote: The drive was pulled out of the system to a usb external drive adapter on another system, mounted and e

Re: Restored f33 on new drive from a tarball now a problem

On Wed, 28 Apr 2021 16:20:23 -0400 Bill Shirley wrote: > Also note > the use of rsync instead of tar. I always install a new fedora at home by doing the install in a virtual machine, then doing a guestmout of the VM image and using rsync to copy everything to an empty partition on my "real" machi

Re: Restored f33 on new drive from a tarball now a problem

I recently migrated a fresh F33 install from a single drive installation to Raid-1.  My eyes and fingers that did the initial install is over 1,000 miles away. The initial install: / /dev/sda3 /boot /dev/sda2 /swap /dev/sda1 The following is the process I used to migrate the OS to /dev/sdb.

Re: Restored f33 on new drive from a tarball now a problem

On 4/25/21 8:32 PM, Michael D. Setzer II via users wrote: Just wondering how you copied the old drive to the new one? If you manually copied the data, the blkids are different, so the boot and fstab information will have to manually be updated, or you will have to use blkid to change the blkids t

Re: Restored f33 on new drive from a tarball now a problem

On 4/25/21 7:23 PM, Ed Greshko wrote: On 26/04/2021 07:09, Robert McBroom via users wrote: On 4/25/21 5:34 PM, George N. White III wrote: On Sun, 25 Apr 2021 at 17:04, Robert McBroom via users > wrote:     New drive has the same msdos partition structure

Re: Restored f33 on new drive from a tarball now a problem

Just wondering how you copied the old drive to the new one? If you manually copied the data, the blkids are different, so the boot and fstab information will have to manually be updated, or you will have to use blkid to change the blkids to match. I generally clone disks to the new one, which

Re: Restored f33 on new drive from a tarball now a problem

> On 26/04/2021 07:09, Robert McBroom via users wrote: >> On 4/25/21 5:34 PM, George N. White III wrote: >>> On Sun, 25 Apr 2021 at 17:04, Robert McBroom via users >>> mailto:users@lists.fedoraproject.org>> >>> wrote: >>> >>> New drive has the same msdos partition structure as the old. >>> Le

Re: Restored f33 on new drive from a tarball now a problem

On 26/04/2021 07:09, Robert McBroom via users wrote: On 4/25/21 5:34 PM, George N. White III wrote: On Sun, 25 Apr 2021 at 17:04, Robert McBroom via users mailto:users@lists.fedoraproject.org>> wrote: New drive has the same msdos partition structure as the old. Legacy system with boot p

Re: Restored f33 on new drive from a tarball now a problem

On 4/25/21 5:34 PM, George N. White III wrote: On Sun, 25 Apr 2021 at 17:04, Robert McBroom via users mailto:users@lists.fedoraproject.org>> wrote: New drive has the same msdos partition structure as the old. Legacy system with boot partition on a separate drive and from the root p

Re: Restored f33 on new drive from a tarball now a problem

On Sun, 25 Apr 2021 at 17:04, Robert McBroom via users < users@lists.fedoraproject.org> wrote: > New drive has the same msdos partition structure as the old. Legacy > system with boot partition on a separate drive and from the root > partition. System boots in mode 3 as specified but entering id a