Linux
Welcome to c/linux!
Welcome to our thriving Linux community! Whether you're a seasoned Linux enthusiast or just starting your journey, we're excited to have you here. Explore, learn, and collaborate with like-minded individuals who share a passion for open-source software and the endless possibilities it offers. Together, let's dive into the world of Linux and embrace the power of freedom, customization, and innovation. Enjoy your stay and feel free to join the vibrant discussions that await you!
Rules:
-
Stay on topic: Posts and discussions should be related to Linux, open source software, and related technologies.
-
Be respectful: Treat fellow community members with respect and courtesy.
-
Quality over quantity: Share informative and thought-provoking content.
-
No spam or self-promotion: Avoid excessive self-promotion or spamming.
-
No NSFW adult content
-
Follow general lemmy guidelines.
view the rest of the comments
If you'd bought a 2TB you could just
dd
image the windows disk to the new drive. If you can convince Windows to downsize its partition and then use a partition editor on a USB liveboot to identify the drive sectors you could maybe still image the windows disk. Big "if."As to the second question, use block IDs-- the filesystem's UUID. Grub is lazy and assumes a single root (the first found) partition so if you want a particular boot entry to use a specific root slice, you'll need to ensure each OS entry in grub uses the right UUID for its kernel
root
parameter. Loading the right root gets you the rigjt /etc/fstab to mount that root's expected partitionsHonestly you'd be better off running your stuff in VMs. Dual-boot is a nightmare.
Also, I'm very tired right now. I'll explain stuff better later when I wake up.
Thank you for the help! It's very much appreciated.
Back in the old days, it was enough to simply defrag a Windows drive - preferably from safe mode or using the DOS it ran on - and there'd be a strong chance that everything would be shunted to the start of the disk, which would be ideal here. It was how I was able to make room to create Linux partitions on my first PC back in the day.
Copying that Windows partition image would have a strong chance of working first time on the new disk (or partition).
These days (which I use very loosely, since XP might have been guilty of this) Windows likes to splat important things all over its partition and can require some convincing to move it. There may also be license problems if Windows thinks something screwy is going on.
Hopefully solidgrue (or others) can recommend something. Third party partition management software and/or boot USBs would be my bet, but I don't know what's good.
Worst case, you'll have to back up your important files and create a new installation on the new disk. It wouldn't hurt to get started on that backup in the meantime. Better to have one and not need it, etc.
I was planning to delete a bunch of stuff off of my old Windows drive anyways, so I'll just backup my important stuff that I wanna keep and then do a fresh reinstall on the new SSD so that I can wipe the old 2TB SSD Windows used to live on. Even 1TB is being generous but I'd rather have too much space than not enough!
There's nothing terribly important on there, it's mainly just my modded Bethesda games I've put a lot of effort into that I'm to lazy to recreate under Linux so I'd rather just keep a small Windows disk alive for when I feel like playing them and for any edge cases that pop up that require me to use Windows.
Thank you for the answer!