On 6/23/19 6:47 PM, Felix Miata wrote:

George from the tribe composed on 2019-06-23 15:52 (UTC-0500):

Useful, likely necessary, information not provided: /etc/fstab from /dev/sda1 output from blkid

cat /etc/fstab LABEL=root423 / ext4 acl,user_xattr 1 1 LABEL=swap swap swap defaults 0 0 LABEL=ESP /boot/efi vfat umask=0002,utf8=true 0 0 LABEL=data1 /home ext4 defaults 1 2 LABEL=OS /windows/C ntfs-3g uid=1000,gid=1000,dmask=027,fmask=137 0 0 LABEL=ntfsdata /mounters/ntfsdata ntfs-3g uid=1000,gid=1000,dmask=027,fmask=137 0 0

blkid /dev/sda1 /dev/sda1: LABEL="root423" UUID="05842869-174f-4231-970b-bb9b439fb29e" TYPE="ext4" PARTLABEL="rootxtra" PARTUUID="8817328e-d57b-4a4f-ad81-027bef10c8d4"

So on this partition, it should be known that it was running Leap 42.3 at one point. Then I upgraded it to tumbleweed, and then I downgraded it to Leap 15.0. I just never changed the label to reflect that it is now 15.0. Both system changes were done using zypper dup.

...

I have already copied /dev/sda1 to /dev/sdb1 using rsync, so now it is just a matter of setting up grub.

Not exactly.

...

I have successfully used the following procedure many times in the past, but this time it isn't working.

It appears from the partitioning on sdb that you are using UEFI. Grub plays a considerably different role using UEFI than when using legacy/MBR. Assuming your sda1 installation was in fact made in UEFI mode, efibootmgr should be employed to adjust how and whether Grub appears after POST.

What might enable you to fix Grub is to make the required fstab and /etc/default/grub adjustments on sdb8, then boot from sda1 substituting /dev/sdb8's UUID for /dev/sda1's UUID on the kernel cmdline's root= (or just type in root=/dev/sdb8 instead of root=UUID=foo). Once sdb8 is in command from this temporary hybrid boot configuration, use YaST to reconfigure booting from sdb1/sdb8.

When I have done this before, I have not had to reconfigure /etc/fstab in the new partition before trying to change root in order to get Grub to find everything and put the grub configuration together. I only had to do so afterwards. Nevertheless, I will try this, as it makes sense to work around the problem and get to my ultimate goal. Thanks. :)

If Windows is booting in UEFI and openSUSE on sda1 is not, then for openSUSE on sdb8 functionality you'll more likely need to create a new installation on sdb8.

I am pretty sure I am only booting in UEFI mode. My bios has a legacy bios option but I have never used it to my knowledge.

-- George Box: TW | Plasma 5 | AMD Phenom IIX4 | 64 | 32GB Laptop #1: 15.0 | Plasma 5 | AMD FX 7TH GEN | 64 | 32GB Laptop #2: 15.0 | Plasma 5 | Core i5 | 64 | 8GB -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org

On 6/24/19 10:07 AM, George from the tribe wrote:

On 6/24/19 9:21 AM, George from the tribe wrote:

...

On 6/23/19 6:47 PM, Felix Miata wrote:

...

...

...

I have already copied /dev/sda1 to /dev/sdb8 using rsync, so now it is just a matter of setting up grub.

Not exactly.

Problem solved.... I hope...

When you suggested I modify the fstab file on the new partition, I went to look at it, and noticed that it was not copied from the old partition. Then I compared and figured out several files on the new partition /dev/sdb8 were not copied.

So looking at the rsync manual, I saw this: -u, --update                skip files that are newer on the receiver

I was using -u as one of my rsync options when I copied /dev/sda1 to /dev/sdb8, and that is why several files didn't copy over. The partition /dev/sdb8 had a whole set of tumbleweed files that were newer than the leap 15.0 files, so they were not erased, hence not being able to find the proper library on calling chroot. So I re-ran my rsync copy, leaving out the -u option, and then ran my procedure.

Change root then worked fine, and I have updated grub. So now to reboot, and hopefully everything is set now.

Thanks.

Ok, I have confirmed it - booted into the new partition and sending this email from /dev/sdb8. It works now. -- George Box: TW | Plasma 5 | AMD Phenom IIX4 | 64 | 32GB Laptop #1: 15.0 | Plasma 5 | AMD FX 7TH GEN | 64 | 32GB Laptop #2: 15.0 | Plasma 5 | Core i5 | 64 | 8GB -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org

On 6/24/19 9:35 AM, Andrei Borzenkov wrote:

On Sun, Jun 23, 2019 at 11:53 PM George from the tribe wrote:

...

...

...

I have already copied /dev/sda1 to /dev/sdb1 using rsync, so now it is just a matter of setting up grub.

I have successfully used the following procedure many times in the past, but this time it isn't working.

root@tribetrekDellbig:/home/george> mount /dev/sdb8 /mnt

You copied it to /dev/sdb1 bit mount now /dev/sdb8?

Sorry that was a typo. I meant to write /dev/sdb8.

...

root@tribetrekDellbig:/home/george> mount -o bind /proc /mnt/proc/ root@tribetrekDellbig:/home/george> mount -o bind /sys /mnt/sys/ root@tribetrekDellbig:/home/george> mount -o bind /dev /mnt/dev/ root@tribetrekDellbig:/home/george> cd /mnt root@tribetrekDellbig:/mnt> chroot /mnt /bin/bash: error while loading shared libraries: libreadline.so.8: cannot open shared object file: No such file or directory

And is this file actually present?

-- George Box: TW | Plasma 5 | AMD Phenom IIX4 | 64 | 32GB Laptop #1: 15.0 | Plasma 5 | AMD FX 7TH GEN | 64 | 32GB Laptop #2: 15.0 | Plasma 5 | Core i5 | 64 | 8GB -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org