GusGF wrote:I have noticed that when Windows has been hibernated the Windows boot loader does not even come up and I am taken straight into Windows. The only way to then get back into Linux is to shut down windows fully.
rprego wrote:If you've got Mint installed, chances are that you've got GRUB as your bootloader (it is usually installed during the installation process for Mint).
As for hibernation, if you hibernate and shut down, then select Windows when you boot, everything should be okay (this sounds like the situation you're in already). If you hibernate, then boot into Linux, and restart and try to boot into Windows, Windows will complain and be unable to restore. To put that simply, what you're trying to do has nothing with GRUB, it won't work because of a restriction with Windows.
What?????????if you hibernate and shut down
........ eh thats what I'm trying to do and no it won't complain because other people have done it and done it using more than 2 OS. Please see hereIf you hibernate, then boot into Linux
srs5694 wrote:GusGF wrote:I have noticed that when Windows has been hibernated the Windows boot loader does not even come up and I am taken straight into Windows. The only way to then get back into Linux is to shut down windows fully.
Given the way most users implement cross-OS file access, this is probably for the best. The problem is that hibernating a computer usually leaves disk access in a "used" state -- that is, the data structures on the disk are not necessarily internally consistent. This is OK if the computer is booted straight back into the original hibernated OS, since the missing information is originally held in memory, then stored on disk for hibernation, and then restored. Thus, after hibernating and returning from hibernation, the OS can still manage the disk and shut it down correctly. If, on the other hand, you reboot into another OS, and if you then attempt to access any filesystems that the first OS had open, the disk will look as if the computer had crashed. Depending on the filesystems and OSes involved and the specific details of what files were being accessed, etc., this could result in an inability to access the disk, in a successful disk "repair" being performed, or even in damage to the filesystem. When the first OS is rebooted, it may end up being confused about the state of the disk, so there's further risk of damage at that point.
Of course, all of this is an issue only if you mount shared filesystems across your OSes. Most Linux users do this on dual-boot configurations, though, so chances are this isn't really an "out." OTOH, the last time I checked, Linux's NTFS drivers tended to refuse to mount an NTFS volume that wasn't properly unmounted, so the risk of damage to an NTFS volume is likely to be fairly low. Still, I prefer to play it safe when it comes to cross-OS filesystem access.
So in sum, if you hibernate, you really should plan on booting back to the original OS the next time you power on. If your boot loader enforces such an action, then that's a good thing, since it makes it less likely that you'll end up trashing your disk through an accidental boot into the wrong OS.
Users browsing this forum: Google Adsense [Bot], kc1di and 23 guests