Results 1 to 6 of 6

Thread: Tumbleweed and Windows 10, dual boot

  1. #1

    Default Tumbleweed and Windows 10, dual boot

    Tumbleweed sometimes fails to boot and drops me to an emergency shell. Looking at the logs I realized that there seems to be a problem with one of the partitions called "data". It is nfts formated and I use it to store data which I want to access from both os's. The log says: "ntfs filesystem is in an unsafe state". The partition is listed in fstab and has the "nofail" option enabled. Shouldn't this cause Tumbleweed to ignore the "unsafe state" of the partition?

    The "data" partition was created from Win7 which I replaced with Win10 Preview last weekend. Ever since then I had problems booting into Tumbleweed. The "data" partition is only accessed from Win10 but wasn't created or formated by Win10.

    Maybe the 3g ntfs drivers aren't up-to-date concerning new ntfs specifications introduced by Win10.

  2. #2
    Join Date
    Jun 2008
    Location
    Netherlands
    Posts
    24,854

    Default Re: Tumbleweed and Windows 10, dual boot

    You most probably did not shutdown the Windows system correctly and then the NTFS filesystem is not in the correct state. We see this often on removable storage (like USB sticks) because people remove them "unsave", but I guess it is the same root cause here.
    Henk van Velden

  3. #3

    Default Re: Tumbleweed and Windows 10, dual boot

    Or Win10 doesn't shut down the way it should be...

  4. #4
    Join Date
    Aug 2010
    Location
    Chicago suburbs
    Posts
    12,353
    Blog Entries
    3

    Default Re: Tumbleweed and Windows 10, dual boot

    Quote Originally Posted by Wingonaut View Post
    Shouldn't this cause Tumbleweed to ignore the "unsafe state" of the partition?
    I think so. This is presumably a "systemd" problem. I seem to recall seeing a bug report on that. You might check.

    I have no experience with Windows 10. However, Windows 8 has a "fast boot" option which could cause this. With "fast boot" enabled (the Windows default), the file systems are not properly shutdown. If effect, a shutdown is a hibernation and a boot is a recovery from hibernation. This leaves the file system in an unstable state and recent linux kernels will at most mount it read-only if they detect this.

    The solution with Windows 8 is to turn off the "fast boot" option in Windows. I don't recall how to get there.

    Hmm, also for Windows 8, this is not supposed to happen on reboot. It is supposed to only happen on shutdown. So maybe try booting Windows first, then reboot to opensuse -- at least until you manage to turn off the fast-boot option.
    openSUSE Leap 15.1; KDE Plasma 5;

  5. #5
    Join Date
    Jun 2008
    Location
    Podunk
    Posts
    26,498
    Blog Entries
    15

    Default Re: Tumbleweed and Windows 10, dual boot

    On Wed 04 Feb 2015 02:36:01 PM CST, Wingonaut wrote:


    Or Win10 doesn't shut down the way it should be...


    Hi
    Make sure fast boot is disabled in the BIOS, I add a shortcut on Win
    10;
    Code:
    shutdown /s /t 5
    To ensure it's a full shutdown, else add the option to remove the
    hiber_file in you ntfs mount option...

    Or have a look at the man page for ntfs-3g under "Windows hibernation
    and fast restarting" for reasons and another option to use to shutdown
    windows.

    --
    Cheers Malcolm °¿° LFCS, SUSE Knowledge Partner (Linux Counter #276890)
    openSUSE 13.2 (Harlequin) (x86_64) GNOME 3.14.0 Kernel 3.16.7-7-desktop
    If you find this post helpful and are logged into the web interface,
    please show your appreciation and click on the star below... Thanks!


  6. #6
    Join Date
    Jun 2008
    Location
    Netherlands
    Posts
    24,854

    Default Re: Tumbleweed and Windows 10, dual boot

    Quote Originally Posted by Wingonaut View Post
    Or Win10 doesn't shut down the way it should be...

    Sorry, I hope this is a rethorical question.
    Henk van Velden

Posting Permissions

  • You may not post new threads
  • You may not post replies
  • You may not post attachments
  • You may not edit your posts
  •