[SOLVED] NTFS volume unclean after Win 10 installation, Emergency Mode

Ps0ke · 2015-12-08 01:14:43

Hello there,

this was my setup:

I have two physical drives, one SSD and one HDD. The SSD, sda, has 3 primary partitions: sda1 is boot, sda2 contains 3 lvm partitions inside a luks crypt: the root file system main-root, a swap main-swap and another partition for /home, main-home, all ext4. sda4 is used for dual booting Windows 7, thus NTFS. The SSD, sdb, is one giant NTFS file storage partition, sdb1, because I want to access it using Linux and Windows. I usually mounted it to /attic via the following line in /etc/fstab:

# /dev/sdb1 LABEL=attic
UUID=0D8AE35A2662FA48 /attic ntfs-3g uid=ps0ke,gid=ps0ke,dmask=022,fmask=133,permissions 0 0

this is probably illustrated best by lsblk

# lsblk
NAME            MAJ:MIN RM   SIZE RO TYPE  MOUNTPOINT
sda               8:0    0 238,5G  0 disk  
├─sda1            8:1    0   512M  0 part  /boot
├─sda2            8:2    0 163,4G  0 part  
│ └─main        254:0    0 163,4G  0 crypt 
│   ├─main-root 254:1    0  42,4G  0 lvm   /
│   ├─main-swap 254:2    0     1G  0 lvm   [SWAP]
│   └─main-home 254:3    0   120G  0 lvm   /home
└─sda4            8:4    0  74,6G  0 part  
sdb               8:16   0 931,5G  0 disk  
└─sdb1            8:17   0 931,5G  0 part

Everything went smooth until I decided to (clean) install Windows 10 the other day (I need Visual Studio 2015). I booted from Windows 10 iso via USB, formated sda4 and installed Windows 10 to it, everything worked fine, I installed some software and created an Arch live USB drive (that really was an unnecessary hassle without dd, missed that before starting the upgrade), booted from it, opened the crypt, mounted the partitions, arch-chroot'ed into my system and ran grub-install. Then I booted into my arch, reran grub-mkconfig, It correctly changed the menuentry label to Windows 10 and I was happy.. I then booted the Windows again, and it somehow git fucked by the whole process and complained about not being able to boot, nor to repair itself. I booted arch again, did a bit of googling, nothing really turned up, so I wanted to check the logs. I tried to boot Windows 10 again and then just worked. whatever. I shut it down (no suspend or hibernate) and booted arch again only to find myself in Emergency Mode.

Dez 07 19:20:11 rechenschieber systemd[1]: Mounted /home.
Dez 07 19:20:11 rechenschieber kernel: snd_hda_codec_realtek hdaudioC0D0: autoconfig for ALC3202: line_outs=1 (0x14/0x0/0x0/0x0/0x0) type:speaker
Dez 07 19:20:11 rechenschieber kernel: snd_hda_codec_realtek hdaudioC0D0:    speaker_outs=0 (0x0/0x0/0x0/0x0/0x0)
Dez 07 19:20:11 rechenschieber kernel: snd_hda_codec_realtek hdaudioC0D0:    hp_outs=2 (0x15/0x1b/0x0/0x0/0x0)
Dez 07 19:20:11 rechenschieber kernel: snd_hda_codec_realtek hdaudioC0D0:    mono: mono_out=0x0
Dez 07 19:20:11 rechenschieber kernel: snd_hda_codec_realtek hdaudioC0D0:    inputs:
Dez 07 19:20:11 rechenschieber kernel: snd_hda_codec_realtek hdaudioC0D0:      Mic=0x18
Dez 07 19:20:11 rechenschieber kernel: snd_hda_codec_realtek hdaudioC0D0:      Dock Mic=0x19
Dez 07 19:20:11 rechenschieber kernel: snd_hda_codec_realtek hdaudioC0D0:      Internal Mic=0x12
Dez 07 19:20:11 rechenschieber systemd[1]: Reached target Sound Card.
Dez 07 19:20:11 rechenschieber kernel: input: HDA Digital PCBeep as /devices/pci0000:00/0000:00:1b.0/sound/card0/input10
Dez 07 19:20:11 rechenschieber kernel: input: HDA Intel PCH Mic as /devices/pci0000:00/0000:00:1b.0/sound/card0/input11
Dez 07 19:20:11 rechenschieber kernel: input: HDA Intel PCH Dock Mic as /devices/pci0000:00/0000:00:1b.0/sound/card0/input12
Dez 07 19:20:11 rechenschieber kernel: input: HDA Intel PCH Headphone as /devices/pci0000:00/0000:00:1b.0/sound/card0/input13
Dez 07 19:20:11 rechenschieber kernel: input: HDA Intel PCH Dock Headphone as /devices/pci0000:00/0000:00:1b.0/sound/card0/input14
Dez 07 19:20:11 rechenschieber mount[381]: The disk contains an unclean file system (0, 0).
Dez 07 19:20:11 rechenschieber mount[381]: Metadata kept in Windows cache, refused to mount.
Dez 07 19:20:11 rechenschieber lvm[403]: 3 logical volume(s) in volume group "main" now active
Dez 07 19:20:11 rechenschieber systemd[1]: Started LVM2 PV scan on device 254:0.
Dez 07 19:20:11 rechenschieber mount[381]: Failed to mount '/dev/sdb1': Operation not permitted
Dez 07 19:20:11 rechenschieber mount[381]: The NTFS partition is in an unsafe state. Please resume and shutdown
Dez 07 19:20:11 rechenschieber mount[381]: Windows fully (no hibernation or fast restarting), or mount the volume
Dez 07 19:20:11 rechenschieber mount[381]: read-only with the 'ro' mount option.
Dez 07 19:20:11 rechenschieber systemd[1]: attic.mount: Mount process exited, code=exited status=14
Dez 07 19:20:11 rechenschieber systemd[1]: Failed to mount /attic.
Dez 07 19:20:11 rechenschieber systemd[1]: Dependency failed for Local File Systems.
Dez 07 19:20:11 rechenschieber systemd[1]: local-fs.target: Job local-fs.target/start failed with result 'dependency'.
Dez 07 19:20:11 rechenschieber systemd[1]: local-fs.target: Triggering OnFailure= dependencies.
Dez 07 19:20:11 rechenschieber systemd[1]: attic.mount: Unit entered failed state.
Dez 07 19:20:11 rechenschieber systemd[1]: Stopped target Graphical Interface.
Dez 07 19:20:11 rechenschieber systemd[1]: Stopped target Multi-User System.
Dez 07 19:20:11 rechenschieber systemd[1]: Stopped D-Bus System Message Bus.
Dez 07 19:20:11 rechenschieber systemd[1]: Stopped Dropbox.
Dez 07 19:20:11 rechenschieber systemd[1]: Stopped Daily Cleanup of Temporary Directories.
Dez 07 19:20:11 rechenschieber systemd[1]: Stopped Make remote CUPS printers available locally.
Dez 07 19:20:11 rechenschieber systemd[1]: Stopped Daily rotation of log files.
Dez 07 19:20:11 rechenschieber systemd[1]: Stopped Network Manager.
Dez 07 19:20:11 rechenschieber systemd[1]: Stopped CUPS Scheduler.
Dez 07 19:20:11 rechenschieber systemd[1]: Stopped Daily verification of password and group files.
Dez 07 19:20:11 rechenschieber systemd[1]: Stopped Redshift display colour temperature adjustment.
Dez 07 19:20:11 rechenschieber systemd[1]: Stopped Avahi mDNS/DNS-SD Stack.
Dez 07 19:20:11 rechenschieber systemd[1]: Closed Avahi mDNS/DNS-SD Stack Activation Socket.
Dez 07 19:20:11 rechenschieber systemd[1]: Stopped GNOME Display Manager.
Dez 07 19:20:11 rechenschieber systemd[1]: Stopped Permit User Sessions.
Dez 07 19:20:11 rechenschieber systemd[1]: Stopped Login Service.
Dez 07 19:20:11 rechenschieber systemd[1]: Closed D-Bus System Message Bus Socket.
Dez 07 19:20:11 rechenschieber systemd[1]: Stopped Daily man-db cache update.
Dez 07 19:20:11 rechenschieber systemd[1]: Reached target Timers.
Dez 07 19:20:11 rechenschieber systemd[1]: Stopped Save/Restore Sound Card State.
Dez 07 19:20:11 rechenschieber systemd[1]: Stopped Manage Sound Card State (restore and store).
Dez 07 19:20:11 rechenschieber systemd[1]: Stopped Network Time Service.
Dez 07 19:20:11 rechenschieber systemd[1]: Reached target Network.
Dez 07 19:20:11 rechenschieber systemd[1]: Stopped Periodic Command Scheduler.
Dez 07 19:20:11 rechenschieber systemd[1]: Stopped target Basic System.
Dez 07 19:20:11 rechenschieber systemd[1]: Reached target Sockets.
Dez 07 19:20:11 rechenschieber kernel: psmouse serio1: synaptics: queried max coordinates: x [..5470], y [..4498]
Dez 07 19:20:11 rechenschieber systemd[1]: Stopped target System Initialization.
Dez 07 19:20:11 rechenschieber systemd[1]: Started Emergency Shell.
Dez 07 19:20:11 rechenschieber systemd[1]: Reached target Emergency Mode.
Dez 07 19:20:11 rechenschieber systemd[1]: Starting Create Volatile Files and Directories...
Dez 07 19:20:11 rechenschieber systemd[1]: Started Create Volatile Files and Directories.
Dez 07 19:20:11 rechenschieber systemd[1]: Starting Update UTMP about System Boot/Shutdown...
Dez 07 19:20:11 rechenschieber systemd[1]: Started Update UTMP about System Boot/Shutdown.
Dez 07 19:20:11 rechenschieber systemd[1]: Startup finished in 16.349s (kernel) + 1.148s (userspace) = 17.497s.
Dez 07 19:20:11 rechenschieber systemd[465]: emergency.service: Failed at step EXEC spawning /bin/plymouth: No such file or directory

After a bit of googling I just commented out the fstab-line for the sdb1 attic NTFS partition and then it worked again. I cannot really recall the order of events for the following, but iirc there was one point in time where I hat sdb1 enabled in the fstab and had used and shut down Windows and then booted arch and it worked. Right now it doesn't even work to mount the partition leater instead of during boot as mount complains about it being unclean. With Windows 7 I regularly suspended and hibernated the system and then just booted linux, returned to windows which just woke up from hibernation and this problem with the shared NTFS drive never occurred to me. My strong guess is that is has to do something with Windows 10. The drive works fine under Windows though.

Do you know any solution to this? I would really like to auto-mount the partition during boot and ensure the file system is clean. I could live with not hibernating windows, but this is apparently not the reason (as it worked with 7 and does not work even with full shut down). thanks :)

Last edited by Ps0ke (2015-12-19 18:47:13)

markasoftware · 2015-12-09 02:07:39

My guess is that you need to turn off windows fast startup. Instructions for disabling it

Soukyuu · 2015-12-12 09:22:26

Yes, having fast startup enabled usually leads to that issue. I have disabled the feature on my dualboot machines and my windows mounts use the "nofail" option so that I at least don't get dropped to emergency shell when an NTFS volume happens to be "unclean".

Ps0ke · 2015-12-17 18:19:43

Yes, that fixed it, thanks. This thread can be marked as [SOLVED]

Slithery · 2015-12-17 18:22:13

Ps0ke wrote:

Yes, that fixed it, thanks. This thread can be marked as [SOLVED]

Go on then, that's your job.
https://wiki.archlinux.org/index.php/Fo … ow_to_post

Arch Linux

#1 2015-12-08 01:14:43

[SOLVED] NTFS volume unclean after Win 10 installation, Emergency Mode

#2 2015-12-09 02:07:39

Re: [SOLVED] NTFS volume unclean after Win 10 installation, Emergency Mode

#3 2015-12-12 09:22:26

Re: [SOLVED] NTFS volume unclean after Win 10 installation, Emergency Mode

#4 2015-12-17 18:19:43

Re: [SOLVED] NTFS volume unclean after Win 10 installation, Emergency Mode

#5 2015-12-17 18:22:13

Re: [SOLVED] NTFS volume unclean after Win 10 installation, Emergency Mode

Board footer