this post was submitted on 05 Jan 2025
19 points (100.0% liked)
technology
23417 readers
285 users here now
On the road to fully automated luxury gay space communism.
Spreading Linux propaganda since 2020
- Ways to run Microsoft/Adobe and more on Linux
- The Ultimate FOSS Guide For Android
- Great libre software on Windows
- Hey you, the lib still using Chrome. Read this post!
Rules:
- 1. Obviously abide by the sitewide code of conduct. Bigotry will be met with an immediate ban
- 2. This community is about technology. Offtopic is permitted as long as it is kept in the comment sections
- 3. Although this is not /c/libre, FOSS related posting is tolerated, and even welcome in the case of effort posts
- 4. We believe technology should be liberating. As such, avoid promoting proprietary and/or bourgeois technology
- 5. Explanatory posts to correct the potential mistakes a comrade made in a post of their own are allowed, as long as they remain respectful
- 6. No crypto (Bitcoin, NFT, etc.) speculation, unless it is purely informative and not too cringe
- 7. Absolutely no tech bro shit. If you have a good opinion of Silicon Valley billionaires please manifest yourself so we can ban you.
founded 4 years ago
MODERATORS
you are viewing a single comment's thread
view the rest of the comments
view the rest of the comments
That partition layout looks fine.
If you use tools like gparted to copy the partitions whole please follow the same order for Windows (that is ensure the recovery is last or after the Windows main data one at least). If using gparted also be careful that you manually set the flags on the copied partitions (you can view the flags set per partition on the source drive then set them the same on the destination).
You'd want to back up valuable files from the NTFS largest partition. Shrinking partitions doesn't typically incur any data loss, it's not a high risk operation but technically all partition operations carry some degree of risk for data loss due to what you're mucking about with. The important thing is not to delete the original source data/disk and its partitions until you're sure you've had a successful copy (say mount the main windows partition, check the files, open a few things to make sure they work and were not completely corrupted). Double check everything before initiating any kind of delete or disk formatting operation. Especially check what disk you're applying operations to and that it is the correct disk and not the wrong one (say you meant to apply to destination but apply to source instead by accident, this is why double-checking what you're working on is important).
I'm not the person who originally replied to you but I do think keeping separate EFI boot partitions for Windows and Linux makes sense, that way if Windows mucks around it won't break your Linux install. So I'd keep them on their relevant disks, let Windows have exclusive control of its EFI partition and Linux control its and make sure that your EFI settings point to your Linux install disk at the end of this.
In other words I'd be in favor of copying all the partitions on the Windows disk in order to their new home. I'd check the flags are correctly set (EFI partition needs boot and one other flag to not show as mountable set). You'll need to shrink your primary Windows NTFS data partition, not sure if gparted supports doing this in the copy operation itself or if you'd need to shrink the partition on the source disk then copy it.
Honestly a Windows based tool from a drive manufacturer doing this would probably yield better results as the start position of the Windows recovery partition is going to be shifted and Windows will not be able to find it if it needs it without running through some commands (something like "fix windows recovery partition location commands" as a search) though this won't stop Windows from booting it'll just mean if it breaks completely you'll need a Windows install disk or iso image on a bootable flash drive to go through boot recovery.