Howdy All! I recently got a bitchin’ new SSD, a Samsung 990 EVO Plus 4TB and I am struggle bussing trying to make it my new boot drive on my computer while keeping all of my programs and settings and things just the way I like them. Specs are I7 13700K cpu and an RTX 4070 gpu plugged into an MSI MAG Z790 Tomahawk Wifi mobo all working harmoniously to run Opensuse Tumbleweed.
Things I have done so far:
-
Googled that shit, didn’t find much that helped me unfortunately. Found some forum where a guy was trying to move over to an SSD from a HDD and then remove the HDD, whereas I just want to change the boot drive to SSD and continue using both drives in the same rig. Someone else in that thread recommended clonezilla but then further down I read something about UUIDs(?) being copied as well and being unable to use both drives in the same computer or it can cause issues and corrupt data. That scared me off that.
-
Tried using the Yast Partitioner tool but the scary warning box it makes you click through and the general lack of any clue what I’m doing scared me off that.
-
Decided to just fresh install Opensuse Tumbleweed onto SSD with usb and then mount the HDD so that I can just copy everything over that way. Or so I thought. First I ran into the issue of the /home located in HDD not being viewable by my user on the SSD, I guess. Fixed that by unmounting the drive and remounting it with the following appended to the end of the mount command ‘-o subvol=/’ , I got that from google as well. Now I’m able to view things in /home on HDD from the user on SSD and I’ve even copied some things over. However I’m unable to access the .snapshots folder in the root directory of HDD which I intended to copy over the latest snapshot and use it on the SSD install to bring all of my non /home stuff over.
So I’m kinda stuck in the middle of transferring over now. I have an inclination toward being lazy so I don’t really want to spend time installing all of the flatpaks and configuring the OS again if I don’t have to. Mostly because I’ve already had one false start with Linux and went ahead and started fresh so this would be the third time having to set everything up again from scratch. Any help or suggestions are greatly appreciated!
From your post it sounds like you’re using btrfs subvolumes, did you use the same ‘-o subvol=/’ when mounting newboot in step 12? I’m pretty sure you should be able to see /etc/fstab if you do that
I tried that and for some reason it only had one directory in /etc and that was snapper. I unmounted and remounted without the -o subvol=/ and I checked in /etc for fstab again and this time I found it so I’m sure I just overlooked it the first time.
I was able to verify that the UUIDs were all the same but then when I attempted to boot from the SSD it went straight to what I think is the grub recovery screen? I just typed shutdown and booted back into the HDD. I guess I’m going to try and clone the drive again. If it doesn’t work again I’ll probably just bite the bullet and perform a fresh install on the SSD again and set everything up manually.
Do you have a screenshot of the error or recovery screen?
Also what do you get if you run sudo btrfs subvolume list /newboot ?
Screenshot of screen ssd boots to currently
spoiler
results of sudo btrfs subvolume list newboot:
spoiler
mint@mint:~$ sudo btrfs subvolume list newboot
ID 256 gen 16336 top level 5 path @
ID 257 gen 16344 top level 256 path @/var
ID 258 gen 16342 top level 256 path @/usr/local
ID 259 gen 16336 top level 256 path @/srv
ID 260 gen 16341 top level 256 path @/root
ID 261 gen 16336 top level 256 path @/opt
ID 262 gen 16344 top level 256 path @/home
ID 263 gen 16163 top level 256 path @/boot/grub2/x86_64-efi
ID 264 gen 16163 top level 256 path @/boot/grub2/i386-pc
ID 265 gen 16327 top level 256 path @/.snapshots
ID 266 gen 16345 top level 265 path @/.snapshots/1/snapshot
ID 267 gen 65 top level 265 path @/.snapshots/2/snapshot
ID 300 gen 13737 top level 265 path @/.snapshots/33/snapshot
ID 301 gen 13737 top level 265 path @/.snapshots/34/snapshot
ID 303 gen 13737 top level 265 path @/.snapshots/36/snapshot
ID 323 gen 13737 top level 265 path @/.snapshots/56/snapshot
ID 324 gen 13737 top level 265 path @/.snapshots/57/snapshot
ID 337 gen 15853 top level 265 path @/.snapshots/70/snapshot
ID 338 gen 15855 top level 265 path @/.snapshots/71/snapshot
ID 339 gen 15884 top level 265 path @/.snapshots/72/snapshot
ID 340 gen 15886 top level 265 path @/.snapshots/73/snapshot
ID 341 gen 15889 top level 265 path @/.snapshots/74/snapshot
ID 342 gen 15891 top level 265 path @/.snapshots/75/snapshot
ID 343 gen 15929 top level 265 path @/.snapshots/76/snapshot
ID 344 gen 15931 top level 265 path @/.snapshots/77/snapshot
ID 345 gen 16281 top level 265 path @/.snapshots/78/snapshot
ID 346 gen 16287 top level 265 path @/.snapshots/79/snapshot
ID 347 gen 16291 top level 265 path @/.snapshots/80/snapshot
ID 348 gen 16326 top level 265 path @/.snapshots/81/snapshot
I appreciate your help! I probably won’t have time to work on it again really until tomorrow, but I feel like I’m close.
Sorry I’m a little unfamiliar with how Opensuse does things so that wasnt as useful as i was hoping lol. Did you have the HDD and SSD connected at the same time when you booted? If you did then you’ll want to disconnect the HDD first.
Also when you get to the grub boot menu if you press e it will show you the config for the selected boot option, can you post a screenshot of that? You may also be able to tell if the root UUID listed there matches the one you expect from fstab. You can also remove splash=silent and quiet from the line beginning with linux and that may give you an actual error message, although it’s possible the boot process is failing before it even gets to that point. If you post the outputs here I can take a look
Edit: looking at your screenshot again I may have misunderstood what was happening, is it failing to even load the boot menu? Also do you know if it’s booting from BIOS or UEFI?
Edit 2: I’ve thought about this some more and its looking like it might be a grub error rather than anything to do with subvolumes. There’s a few things which are probably worth checking before going any further. First boot from your USB with both drives connected and run sudo blkid, assuming your SSD is /dev/sda and your HDD is /dev/sdb, do the UUIDs for the partitions on /dev/sda and /dev/sdb match?
Again assuming /dev/sda is the new SSD run sudo mount /dev/sda2 /mnt and sudo mount /dev/sda1 /mnt/boot/efi then check if the following 2 files exist: /mnt/boot/grub2/grub.cfg /mnt/boot/efi/EFI/opensuse/grub.cfg