Hibernating and booting into another OS: will my filesystems be corrupted?
Problem
IMPORTANT If you came here looking for an answer to this question, please read all the answers below. There are some testimonials from people who have lost data doing this. If you plan to do this regularly, I highly recommend that you test for yourself. Original Question Suppose I have Windows and Linux installed on the same computer. If I hibernate Windows, can I boot into Linux without corrupting the Windows filesystem when I resume Windows? What about the other way around? What if I hibernate one, boot into the other, and mount the hibernated filesystem read/write? Read-only? If this is unsafe, is there any way to detect the hibernated state of the other OS and prevent mounting its filesystem? Basically, how far can I push this before it breaks, and how dangerous is it near the edge? I think I know the answers to some of the above questions, but for other ones, I have no idea, and for obvious reasons I have not tested this on my own computer. If someone has tested these, please enl…
Unverified for your environment
Select your OS to check compatibility.
1 Fix
Fix for: Hibernating and booting into another OS: will my filesystems be corrupted?
I always hibernate Windows before booting in anything else, Windows is just too slow to start from scratch. But it is dangerous to write to the partition of hibernated OS, because some of the FS tables are still in memory (well, in hibernation file but not in the FS), applications still have handles to some files and generally file system state is kind of unstable. But you can mount that partition read-only, this way it will stay exactly the same as before hibernation and Windows won't notice a…
Awaiting Verification
Be the first to verify this fix
Sign in to verify this fix