So I’m having a few issues with Tumbleweed OS not going past the Grub bit despite the fact I had auto login-in enabled on my recent Tumbleweed install, so I may just have to reinstall it again and simply never fiddle about the SSD again as described here System is stuck on Grub unless of course some clever clog helps me figure this out.
Now luckily, I had a version of Leap 16 still on a separate drive and I obviously had a password for the recent Tumbleweed on the other drive but I’d just like to take a few important files and move it over to Leap temporarily in case I’m forced to reinstall Tumbleweed again on the drive where ironically Tumbleweed is giving me an issue, well technically the Grub, so I was wondering if someone could kindly give me some options on how I can go about this.
Hey @dcurtisfra so I obviously tried that before but I don’t know if it’s because you’re loading a Tumbleweed system onto Leap system as opposed to identical systems, it doesn’t seem to load the encryption prompt which is typically what it does from previous experience when you try to load and click on the drive of an OS from an enclosure, which is why I created this topic.
Right now following your steps just loads the drive like a typical USB stick folders and files similar to a bootable USB OS stick so basically with system files and folders but not the kind of files I’m looking for if you know what I mean.
You never mentioned you have encrypted he file system in your first post above. How do you think people can take that into account when trying to help you?
I moved from leap 15.6 to tumbleweed a few weeks ago using migration tool. I use timeshift and I kept a couple of timeshiift snapshots of leap 15.6; just in case. If you have any old timeshifts you could reload leap 15.6 temporarily and do what you need to your files and then go back to tumbleweed.
You can include the user directories in timeshift but they don’t recommend that. I use backintime (also is rsync based) for the /home files. I can thus restore all or a file or two as needed in root or /home.
I couldn’t tell from your words “Now luckily, I had a version of Leap 16 still on a separate drive” what you had.
Hello,
almost everything is file on a system : if you can access the files, you can save et move what you need. I’m not sure I understand well after reading your two subjects but if your old Leap run fine and the “enclosed” Tumbleweed system plugged in USB is encrypted, you can decrypt the partition you need and mount it in the master (Leap) system. One way for example (all operations in root or sudo) :
You need the UUID of the partition to decrypt : blkid or better blkid | grep <info> with ‘info’ that could be the name (hdax, sdax, …) or a label you used to identify the partition for example.
Decrypt it : cryptsetup open /dev/hdax UUID (adapt /dev/hdax and UUID to match with yours, seen in step 1).
Mount it : mount /dev/mapper/UUID /one/folder (adapt /dev/mapper if needed and UUID with info from step 1 or a new blkid ; choose an existing place on the running system and replace /one/folder by it).
As a result, the partition should be available at the /one/folder of your Leap.
It may well be that, we have two cats in this sack –
There’s at least one encrypted filesystem.
Fresh Tumbleweed install → SELinux …
With SELinux, one has to pay particular attention to the security contexts – one has trust the SUSE staff who prepare the default SUSE/openSUSE SELinux security contexts and, ensure that, all the non-system directory «user directories» security contexts have the default values.