[SOLVED] SystemD NTFS partition issue's

Hey archers,
hope someone here can help me
recently began testing systemd & I am facing a problem where I have to ctrl+d or give root password during every boot up due to systemd having problems with my ntfs partition ( i mount at boot as I have symlinks to that partition for documents & programs which run in wine)
I have not enabled anything to do with mounting or even added the fuse module to load as it has already picked that up!
here are the entries I think are related to this from journalctl:
Aug 29 07:57:37 b0x ntfs-3g[568]: Version 2012.1.15 external FUSE 29
Aug 29 07:57:37 b0x ntfs-3g[568]: Mounted /dev/sdb1 (Read-Write, label "Win7-sys", NTFS 3.1)
Aug 29 07:57:37 b0x ntfs-3g[568]: Cmdline options: rw,noatime,sync,gid=100,umask=002
Aug 29 07:57:37 b0x ntfs-3g[568]: Mount options: rw,sync,allow_other,nonempty,noatime,fsname=/dev/sdb1,blkdev,blksize=4096,default_permissions
Aug 29 07:57:37 b0x ntfs-3g[568]: Global ownership and permissions enforced, configuration type 7
Aug 29 07:57:37 b0x ntfs-3g[568]: Warning : using problematic uid==0 and gid!=0
Aug 29 07:57:37 b0x mount[572]: Mount is denied because the NTFS volume is already exclusively opened.
Aug 29 07:57:37 b0x mount[572]: The volume may be already mounted, or another software may use it which
Aug 29 07:57:37 b0x mount[572]: could be identified for example by the help of the 'fuser' command.
Aug 29 07:57:37 b0x systemd[1]: media-Win7.mount mount process exited, code=exited status=16
Aug 29 07:57:37 b0x systemd[1]: Job local-fs.target/start failed with result 'dependency'.
Aug 29 07:57:37 b0x systemd[1]: Triggering OnFailure= dependencies of local-fs.target.
Aug 29 07:57:37 b0x systemd[1]: Job systemd-user-sessions.service/start failed with result 'dependency'.
Aug 29 07:57:37 b0x systemd[1]: Job lightdm.service/start failed with result 'dependency'.
Aug 29 07:57:37 b0x systemd[1]: Job graphical.target/start failed with result 'dependency'.
Aug 29 07:57:37 b0x systemd[1]: Job multi-user.target/start failed with result 'dependency'.
Aug 29 07:57:37 b0x systemd[1]: Job systemd-logind.service/start failed with result 'dependency'.
Aug 29 07:57:37 b0x systemd[1]: Job dbus.service/start failed with result 'dependency'.
Aug 29 07:57:37 b0x systemd[1]: Job [email protected]/start failed with result 'dependency'.
Aug 29 07:57:37 b0x systemd[1]: Job hwclock.service/start failed with result 'dependency'.
Aug 29 07:57:37 b0x systemd[1]: Job syslog-ng.service/start failed with result 'dependency'.
Aug 29 07:57:37 b0x systemd[1]: Job network.service/start failed with result 'dependency'.
Aug 29 07:57:37 b0x systemd[1]: Job cronie.service/start failed with result 'dependency'.
Aug 29 07:57:37 b0x systemd[1]: Job snmpd.service/start failed with result 'dependency'.
Aug 29 07:57:37 b0x systemd[1]: Job samba.service/start failed with result 'dependency'.
Aug 29 07:57:37 b0x systemd[1]: Job webmin.service/start failed with result 'dependency'.
Aug 29 07:57:37 b0x systemd[1]: Job systemd-tmpfiles-clean.timer/start failed with result 'dependency'.
Aug 29 07:57:37 b0x systemd-journal[181]: Journal stopped
Aug 29 07:57:37 b0x systemd-journal[584]: Journal started
Aug 29 07:57:37 b0x ntfs-3g[568]: Unmounting /dev/sdb1 (Win7-sys)
Aug 29 07:57:37 b0x systemd-udevd[224]: '/usr/sbin/alsactl restore 0' [500] terminated by signal 15 (Terminated)
Aug 29 07:57:38 b0x systemd[1]: Startup finished in 3s 111ms 648us (kernel) + 6s 425ms 155us (userspace) = 9s 536ms 803us.
Aug 29 07:57:38 b0x systemd[582]: Failed at step EXEC spawning /bin/plymouth: No such file or directory
Aug 29 07:58:25 b0x systemd[1]: Cannot add dependency job for unit avani-dnsconfd.service, ignoring: Unit avani-dnsconfd.service failed to load: No such file or directory. See system lo...e' for details.
Aug 29 07:58:25 b0x systemd[1]: Socket service syslog.service not loaded, refusing.
Aug 29 07:58:26 b0x arch-modules-load[609]: mkdir: cannot create directory ‘/run/modules-load.d’: File exists
Aug 29 07:58:26 b0x systemd-modules-load[706]: Module 'vhba' is already loaded
Aug 29 07:58:26 b0x systemd-modules-load[706]: Module 'fuse' is already loaded
Aug 29 07:58:26 b0x systemd-fsck[646]: public: clean, 385878/2039808 files, 5060668/8159011 blocks
Aug 29 07:58:26 b0x systemd-fsck[653]: VM: clean, 228/5677056 files, 5637221/22680575 blocks
Aug 29 07:58:26 b0x systemd-fsck[644]: Home: clean, 90204/1327104 files, 984778/5305458 blocks
Aug 29 07:58:26 b0x ntfs-3g[871]: Version 2012.1.15 external FUSE 29
Aug 29 07:58:26 b0x ntfs-3g[871]: Mounted /dev/sdb1 (Read-Write, label "Win7-sys", NTFS 3.1)
Aug 29 07:58:26 b0x ntfs-3g[871]: Cmdline options: rw,gid=100,fmask=113,dmask=002
Aug 29 07:58:26 b0x ntfs-3g[871]: Mount options: rw,allow_other,nonempty,relatime,fsname=/dev/sdb1,blkdev,blksize=4096,default_permissions
Aug 29 07:58:26 b0x ntfs-3g[871]: Global ownership and permissions enforced, configuration type 7
Aug 29 07:58:26 b0x ntfs-3g[871]: Warning : using problematic uid==0 and gid!=0
Here is the entry in /etc/fstab for this partition:
## Entry for /dev/sdb1 SYSTEM:(Win7)
UUID=44083B9668A3E0CC /media/Win7 ntfs-3g gid=users,fmask=113,dmask=002 0 0
I have been all over goggle & am unable to find out anything which can help.
As stated before I have links to this partition & so really want/need this partition to be mounted at boot.
Any help on this will be greatly appreciated
Thanks in advance
EDIT #1
rebooted again, still the same happening
ran:
$ sudo mount -l
proc on /proc type proc (rw,nosuid,nodev,noexec,relatime)
sys on /sys type sysfs (rw,nosuid,nodev,noexec,relatime)
dev on /dev type devtmpfs (rw,nosuid,relatime,size=3022708k,nr_inodes=755677,mode=755)
run on /run type tmpfs (rw,nosuid,nodev,relatime,mode=755)
/dev/sda1 on / type ext4 (rw,relatime,data=ordered) [Arch-sys]
securityfs on /sys/kernel/security type securityfs (rw,nosuid,nodev,noexec,relatime)
tmpfs on /dev/shm type tmpfs (rw,nosuid,nodev)
devpts on /dev/pts type devpts (rw,nosuid,noexec,relatime,gid=5,mode=620,ptmxmode=000)
tmpfs on /sys/fs/cgroup type tmpfs (rw,nosuid,nodev,noexec,mode=755)
cgroup on /sys/fs/cgroup/systemd type cgroup (rw,nosuid,nodev,noexec,relatime,release_agent=/usr/lib/systemd/systemd-cgroups-agent,name=systemd)
cgroup on /sys/fs/cgroup/cpuset type cgroup (rw,nosuid,nodev,noexec,relatime,cpuset)
cgroup on /sys/fs/cgroup/cpu,cpuacct type cgroup (rw,nosuid,nodev,noexec,relatime,cpuacct,cpu)
cgroup on /sys/fs/cgroup/memory type cgroup (rw,nosuid,nodev,noexec,relatime,memory)
cgroup on /sys/fs/cgroup/devices type cgroup (rw,nosuid,nodev,noexec,relatime,devices)
cgroup on /sys/fs/cgroup/freezer type cgroup (rw,nosuid,nodev,noexec,relatime,freezer)
cgroup on /sys/fs/cgroup/net_cls type cgroup (rw,nosuid,nodev,noexec,relatime,net_cls)
cgroup on /sys/fs/cgroup/blkio type cgroup (rw,nosuid,nodev,noexec,relatime,blkio)
systemd-1 on /proc/sys/fs/binfmt_misc type autofs (rw,relatime,fd=30,pgrp=1,timeout=300,minproto=5,maxproto=5,direct)
debugfs on /sys/kernel/debug type debugfs (rw,relatime)
mqueue on /dev/mqueue type mqueue (rw,relatime)
hugetlbfs on /dev/hugepages type hugetlbfs (rw,relatime)
fusectl on /sys/fs/fuse/connections type fusectl (rw,relatime)
tmpfs on /tmp type tmpfs (rw,nosuid,nodev,relatime)
/dev/sdb3 on /media/wine type ext4 (rw,noatime,errors=remount-ro,data=ordered) [wine] <<<THIS SHOULD NOT BE HERE!<<<<<<<<<
/dev/sdd1 on /media/spare2 type ext4 (rw,noatime,errors=remount-ro,data=ordered) [spare2] <<<THIS SHOULD NOT BE HERE!<<<<<<<<<<
/dev/sdc1 on /media/spare type ext4 (rw,noatime,errors=remount-ro,data=ordered) [spare] <<<THIS SHOULD NOT BE HERE!<<<<<<<<<<<
/dev/sde1 on /media/USB-HDD2 type vfat (rw,noatime,sync,gid=100,fmask=0002,dmask=0002,allow_utime=0020,codepage=cp437,iocharset=iso8859-1,shortname=mixed,errors=remount-ro) [USB-HDD2] <<<<<THIS IS NORMAL
/dev/sdb4 on /media/pac type ext4 (rw,noatime,errors=remount-ro,data=ordered) [pac] <<<THIS SHOULD NOT BE HERE!
/dev/sdd1 on /media/Spare2 type ext4 (rw,relatime,errors=remount-ro,data=ordered) [spare2] <<<<<THIS IS NORMAL
/dev/sdc1 on /media/Spare type ext4 (rw,relatime,errors=remount-ro,data=ordered) [spare] <<<<<THIS IS NORMAL
/dev/sdb2 on /media/VM type ext4 (rw,relatime,errors=remount-ro,data=ordered) [VM] <<<<<THIS IS NORMAL
/dev/sdb3 on /var/wine type ext4 (rw,relatime,errors=remount-ro,data=ordered) [wine] <<<<<THIS IS NORMAL
/dev/sdb4 on /var/cache/pacman type ext4 (rw,relatime,errors=remount-ro,data=ordered) [pac] <<<<<THIS IS NORMAL
/dev/sdb1 on /media/Win7 type fuseblk (rw,nosuid,nodev,relatime,user_id=0,group_id=0,default_permissions,allow_other,blksize=4096) [Win7-sys] <<<<<THIS IS NORMAL
/dev/sda3 on /public type ext4 (rw,relatime,errors=remount-ro,data=ordered) [public] <<<<<THIS IS NORMAL
/dev/sda5 on /home type ext4 (rw,relatime,errors=remount-ro,data=ordered) [Home] <<<<<THIS IS NORMAL
gvfs-fuse-daemon on /run/user/1000/gvfs type fuse.gvfs-fuse-daemon (rw,nosuid,nodev,relatime,user_id=1000,group_id=100)
binfmt_misc on /proc/sys/fs/binfmt_misc type binfmt_misc (rw,relatime)
gvfs-fuse-daemon on /root/.gvfs type fuse.gvfs-fuse-daemon (rw,nosuid,nodev,relatime,user_id=0,group_id=0)
as you can see my partitions are being mounted TWICE which is not what I want or expected!
is there more documentation on what systemd does with mounts that could explain why i have multiple mount points for partitions or is this due to systemd discovering my partitions & mounting them at points based on label names & then parsing my FSTAB as well!
I have read the wikki but there is very small info there & the links have not provided an explanation for this unwanted behaviour
EDIT #2
>>>>>>>>>>>SOLVED<<<<<<<<<<<<<<
not an NTFS or FUSE issue
I had previously installed mnttools!
removed & now all is well
sorry
Last edited by t0m5k1 (2012-08-29 08:30:11)

OK,
After being spurred on to try to do this thing properly, this is what I came up with today.
My fstab line (for a USB NTFS disk):
/dev/sdb1 /media/samsung ntfs-3g noauto,users,rw,nodev 0 0
Then I created the /media/samsung folder and gave the audio group read/write permissions.
It seems that non-root users can only mount an ntfs partition if they use a version of ntfs-3g with fuse included, so I replaced ntfs-3g with the version from AUR, having removed from the PKGBUILD file the option "-with-fuse=external" (see this thread: http://bbs.archlinux.org/viewtopic.php?id=44844 ). I also had to set
the ntfs-3g binary to setuid-root, dealt with here: http://www.tuxera.com/community/ntfs-3g … privileged (note- the instructions say this is discouraged, but it seems using ntfs partitions in linux requires some compromises).
I can now mount the drive as an ordinary user.
Then I set mpd back to run as user mpd, checked the audio group had access to all the mpd folders, and all was well.
One hiccup which you might not have: mpd was unable to access my (external) sound card at first. To solve this one, I used
chmod 770 /dev/snd -R && chgrp audio /dev/snd -R
As far as I can remember, that's everything.
Last edited by Henry Flower (2010-04-20 12:54:26)

Similar Messages

Solved! NTFS-3G Issue on Mac Maverick when plugging a hard drive via USB

This issue can be solved in less than 5 minutes, but it is not free. if you are willing to sort it out once and for good, read on, it’s well worth it!
“I love my Mac!”, that is a common expression you might hear everyday, but not many people are willing to admit that Macs really suck and become a nightmare the moment you plug a hard drive, new or filled with those important files, via USB. Apparently most commercial backup hard drives are formatted with Windows file systems by default and Macs will only be able to read the contents of these discs after properly formatting them on Mac.
I have 3 external hard drives filled with mp4 movies and uni files, and formatting is absolutely a no-no here. So I was forced to open those files using the Windows virtual machine (via Parallel) in my Mac, which really ***** too. According to the many websites I visited for solution, you either had to buy some apps or die with that NTFS-#G error message when plugging a USB hard drive. There is also an encouragement to either format the drives on Mac before you can use, and again, in my case, this is impossible.
“NTFS-3G could not mount /dev/disk1s1 at /Volumes/Vuakalevu because the following problem occurred: dyld:
Library not loaded: /usr/local/lib/libfuse.2.dylib Referenced from: /usr/local/bin/ntfs-3g
Reason: image not found”
I think I just solved that issue once and for all, but nothing comes for free, as in anything with Mac computers. The “Paragon NTFS for Mac OSX”, which cost me $19.99 from their official website seems to have sorted me out, now I can plug any hard drive, no matter the format, and Maverick will read it as it should (read and write). Well worth it, and i do recommend it.
This was originally posted in my website, so feel free to come around if you like.
http://journalsfromoceania.com/solved-ntfs-3g-external-drive-issue-solved-for-19 -99/

Hi Linc Davis, yep! i did everything according to read me, tried all free ones, only made it worse. uninstalled the whole lot, didnt work either. I read around in forums the same thing "simply remove the app causing this issue and it will be sorted" didnt work for me. this Paragon sorted me out after 2 years of external hard drive issues. Im not sure if your reply was an assertion or a question though. cheers

NTFS Partition Issues not allowing install on MBA 2012, Win 8.1

MacBook Air 2012, Mavericks & Windows 8.1 install
Hi there,
I am going mad trying to install Windows 8.1 from a USB drive via BootCamp. I have made the ISO Windows 8.1 installation disk. I have downloaded the appropriate driver files & seem to be doing everything right. However when I get part way through the process after selecting the Window partition size (40GB) I am running into problems.
When I go to install Windows to the BootCamp partition I get the error message that "Windows cannot be installed to this hard disk space. Windows must be installed to a partition formatted as NTSC". Formatting it does not help & when I refresh it still gives the same message. I have deleted the partition & created a new one but still cant proceed.
In disk utility, I can see that it is formatted in NTFS but no matter what I do it will not proceed & gives me an error message. The other error message that I get is "We couldn't create a new partition or locate an existing one. For more information see the setup log files".
I have searched the net but not found an answer to this problem. I am desperate to get this fixed. Thanks in advance.

I got stuck at the same spot. Once I removed my USB flash drive, it let me continue

KDE's Dolphin can't mount NTFS partitions after upgrade to systemd

Hi, I just finished to migrate my system to a pure systemd setup. Everithing seems to work fine, except that Dolphin can't mount NTFS partitions anymore, as it was able to do before. I'm not 100% sure that systemd is the culprit, but nevertheless it is a big change in my system so I assume that it may be the problem.
Trying to mount with Dolphin I get this error message:
An error occurred while accessing 'sATA-a', the system responded: The requested operation has failed.: Error mounting: mount exited with exit code 1: helper failed with:
Error opening '/dev/sdb1': Permesso negato
Failed to mount '/dev/sdb1': Permesso negato
Please check '/dev/sdb1' and the ntfs-3g binary permissions,
and the mounting user ID. More explanation is provided at
http://tuxera.com/community/ntfs-3g-faq/#unprivileged
I used to get this kind of error aeons ago when trying to mount from CL; puzzling enough, mounting from CL now works:
$ mount /media/disks/sATA-a
$ ls /media/disks/sATA-a
Documenti Download $RECYCLE.BIN RECYCLER sATA-b System Volume Information Temp Video
This is the relevant entry in my fstab (I don't know if Dolphin cares about it...):
#sATA-a
UUID=D6789B21789B0003 /media/disks/sATA-a ntfs-3g noauto,users 0 0
And finally:
$ ll `which ntfs-3g`
-rwsr-xr-x 1 root root 125K 21 apr 12.13 /bin/ntfs-3g
Can anybody give me a hint? Thanks.

OK, the mess is growing up. Today I switched my laptop to systemd, and the mount problem has appeared on this system as well. So I am confident that this is a systemd-related issue, and maybe some stock Arch config file is broken. I have this entry on my /etc/fstab for the ntfs-3g drive:
UUID=88705BA9705B9D2E /media/vista ntfs-3g noauto,users,exec 0 0
I compiled ntfs-3g with internal fuse support and did the setuid trick:
$ ls -l `which ntfs-3g`
-rwsr-xr-x 1 root root 125K 16 apr 2012 /bin/ntfs-3g
I can mount the disk using the command:
$ mount /media/vista/
$
It works flawlessly, so ntfs-3g works. If I try to mount it with udisks I get:
$ /usr/bin/udisks --mount /dev/sda2 --mount-options users,exec
Mount failed: Error mounting: mount exited with exit code 1: helper failed with:
Error opening '/dev/sda2': Permesso negato
Failed to mount '/dev/sda2': Permesso negato
Please check '/dev/sda2' and the ntfs-3g binary permissions,
and the mounting user ID. More explanation is provided at
http://tuxera.com/community/ntfs-3g-faq/#unprivileged
It sounds to me that udisks is trying to mount the disk as a different user, but I'm not an expert so I might be wrong. If I remove the entry in /etc/fstab then udisks will ask for the password. Repeating the same steps but for an ext3 partition, I am able to mount with udisks when there is a proper fstab entry, and I'm asked for a password when that entry is commented out.
Based on these findings, I strongly suspect that there is some problem with logind configuration in my system. I have been going round and round for hours, serching the web and the wiki (which BTW is in a very bad shape, containing outdated or no informations about mount policies in the polkit and udev sections), and now I feel I need some help to go through it... thanks.

OMG Please help with Win XP partition issue FAT32 NTFS

I know that there are other posts about this, but I have not been able to find the answers to my problems
I had the issue that others had with not getting the option to format the bootcamp partition during my XP Pro install. I used the FreeDOS solution to format the drive, but I am now left with an 80gb FAT32 partition which is not really what I wanted.
Reading other posts, resizing the partition does not seem to be an option. I guess that I use Winclone to backup my XP partition, wipe out the partition using Bootcamp, but where do I go from here????
A couple of questions:
1) Can a backup of a FAT32 partition be restored to an NTFS partition?
2) How the bl**dy **** do I format the bootcamp partition as NTFS if I do not get the option of formatting during the XP install and FreeDOS wants to format as FAT32.
By the way if anyone has the answer that involves not having to wipe the FAT32 partition but shrink / reduce it to say 15gb and allow me to create a 65gb NTFS partition - there is a big sloppy kiss waiting!!!!
I was hoping that I could just use something like Partition Magic within my 80gb bootcamp partition to resize the FAT32 then create and format the NTFS partition?
Sorry for babbling and thanks for reading and hopfully ending my pain.
Ian.

I have found this http://support.microsoft.com/kb/307881 that allows the conversion of a FAT32 partition to NTFS. . . . looks like I will give this a go tonight.
Ian.

NTFS partition: Files auto deleted by Windows [SOLVED]

I am dual booting with Win7. I copy some files to NTFS partition so that I can access them from Windows. But what I see after I boot into Windows, those files are either deleted or are corrupted (a few hundred megs file is just a few kB now) !!!
This is really frustrating as I lost several files, though not all as some files remain as they were in Arch. I have NTFS-3G installed, and use HAL hot-plug mounting to access the NTFS drive.
Any ideas what is going wrong here ? Thanks.
Last edited by shemz (2010-05-04 21:45:30)

Its just another partition on the same drive where my arch ext4 partition exists. For a moment I thought its a problem with hibernation. So this time I copied a file to the NTFS partition and did a complete shutdown from linux. Now both windows and linux are in shutdown state, none in hibernation. I booted into windows, the file is again gone.
Then I checked into this folder Found.000. And one of my missing files is here. This prompted me to check if M$ has found a new way to keep (force) people away from linux. I found somewhere on the web that by default in Win7 the check disk utility checks for file system consistency at each boot (I think it would just check for either time stamps or directory structure).
So for now I have disabled automatic disk checking in Windows. Will do a few more test boots to see it solves the problem. Thanks again.
Edit: Few test reboots and all seems fine. Its a windows problem.
Last edited by shemz (2010-05-04 21:43:29)

[SOLVED] NTFS partition unmounted after suspend to ram

I recently did a from-scratch installation after I bought an SSD to replace of my old harddrive. Since this fresh install I have been having a problem with an NTFS partition that is mounted by way of fstab (it's not _the_ windows partition just a bit of shared space on a dual-boot setup): Whenever I suspend the computer and bring it back up, the NTFS partition is invariably unmounted.
The mount point is empty and the mount command makes no mention of the mount. A simple "sudo mount /mnt/SAND" will bring the partition back up again although sometimes it needs to be umounted first (the mount point is still empty despite the 'mount'). Here is the fstab line:
/dev/sda3 /mnt/SAND ntfs-3g defaults,noatime,uid=1000,gid=100 0 0
Testing and screwing around I've noticed that if the WINDOWS partition is mounted using nautilus (as it is not mentioned in fstab) that too will be unmounted while a non-root ext4 partition (UBUNTU) is not.
So my hypothesis is that these NTFS partitions are singled out for unmounting when suspending (but apparently not mounting when reawakening?) -- maybe because they are assumed to be external drives? Given that it happens across mounting solutions (fstab/nautilus) I'm inclined to think it's not a bug?
At any rate I'm looking for a solution that will allow me to stop the unmounting when suspending -- ideally for all internal drives, secondarily for these specific partitions. I have checked the suspend to ram article on the wiki but it doesn't seem to mention anything about unmounting...
EDIT: After the Great Big Arch Switch To Systemd this problem no longers occurs on so I'm closing it. Not necessarily much of a solution to anyone who happens on this from google, sorry.
Last edited by madchine (2012-10-13 12:58:54)

Hi all,
It seems that most freezes are gone with:
- 270.29 beta driver
- MTRR enabled by appending enable_mtrr_cleanup mtrr_spare_reg_nr=1 to the list of kernel options (see http://www.nvnews.net/vbulletin/showpos … tcount=39)
I didn't investigate further to know if both the driver and the MTRR trick are required.
Thanks a lot,
Aurel.

(solved) gparted refuses to shorten ntfs partition

Hi everybody. I am trying to shorten the /dev/sda1 ntfs partition with gparted but it does not work. there is an error message and I cannot apply the change. thanks.
Last edited by cezarrangel (2013-02-12 12:58:22)

thank you so much Jasonwryan. I apologyze on my knees. the problem is that I want to shorten this ntfs partition /dev/sda1 to have enough space for an Arch partition. Unfortunately I cannot get rid of this ntfs partition permanentely. that is why I wrongly (sorry again for the mess on the forum) considered it an installation issue. and, sorry again, of course you could not guess the error message.
In fact, when the gparted windown opens, the option to resize/move the ntfs partition is there available. but when I try to choose the new size of the ntfs partition it does not go anyhere. I try to move the reference to the ntfs partition with the mouse cursor to the size I want but this action is not available. I have already tried defragmenting the ntfs partition. the operation seems to end successful. but when I try gparted again it is no use. I do not succeed resize/move the ntfs partition.
I thank you once more for your most kind answer and apologize for the hasty issue.
Last edited by cezarrangel (2013-02-11 12:38:02)

[SOLVED] Systemd has problems with ntfs-3g

Hi!
I created a custom daemon.
It's very simple.
[Unit]
Description=Mounting partitions if Im at home
[Service]
Type=simple
ExecStart=/home/skitter/homemount.sh
[Install]
WantedBy=multi-user.target
And the content of a script:
#!/bin/bash
device0="/dev/disk/by-uuid/e2b0e86b-d377-4699-9407-48d56eb439d0"
if [ -b "$device0" ]
then
mount UUID=01CECC33AEE58980 /mnt/WINDOWS
mount UUID=ff2d44b5-bdd0-4524-89bf-6ac3bc005887 /mnt/Other
mount UUID=599D77CD384A8B00 /mnt/Files
fi
Unfortunately for some reason the ntfs partitions are being automatically unmounted.
The ext4 partition is not causing any problems.
$sudo systemctl status homemount
homemount.service - Mounting disk if Im at home
Loaded: loaded (/usr/lib/systemd/system/homemount.service; enabled)
Active: inactive (dead) since Sun 2013-10-27 21:56:23 CET; 1s ago
Process: 3202 ExecStart=/home/skitter/homemount.sh (code=exited, status=0/SUCCESS)
Main PID: 3202 (code=exited, status=0/SUCCESS)
Oct 27 21:56:22 archer ntfs-3g[3206]: Mounted /dev/sdb1 (Read-Write, label "", NTFS 3.1)
Oct 27 21:56:22 archer ntfs-3g[3206]: Cmdline options: rw
Oct 27 21:56:22 archer ntfs-3g[3206]: Mount options: rw,allow_other,nonempty,relatime,fsname=/dev/sdb1,blkdev,blksize=4096
Oct 27 21:56:22 archer ntfs-3g[3206]: Ownership and permissions disabled, configuration type 7
Oct 27 21:56:23 archer ntfs-3g[3213]: Version 2013.1.13 external FUSE 29
Oct 27 21:56:23 archer ntfs-3g[3213]: Mounted /dev/sda1 (Read-Write, label "Files", NTFS 3.1)
Oct 27 21:56:23 archer ntfs-3g[3213]: Cmdline options: rw
Oct 27 21:56:23 archer ntfs-3g[3213]: Mount options: rw,allow_other,nonempty,relatime,fsname=/dev/sda1,blkdev,blksize=4096
Oct 27 21:56:23 archer ntfs-3g[3213]: Ownership and permissions disabled, configuration type 7
Oct 27 21:56:23 archer ntfs-3g[3206]: Unmounting /dev/sdb1 ()
Last edited by Skitter (2013-10-27 21:43:32)

I think this is because the mount command exits, so the daemon is then considered dead (or completed). But I am not entirely sure about this.
A better solution would be to simply make an entry in your fstab with the noauto,x-systemd.automount,nofail options. This would essentially achieve what you are after I think. You could also make actualy systemd.mount and systemd.automount units as well, though these would automagically be generated by an entry in your fstab.
If you are unsure of what exactly to put in native systemd units, you can always see what systemd does in /run/systemd/generators. In fact, if you put a fstab entry for this ntfs-3g mount, let it generate (ie reboot, or run the generator) then check out that directory, you can simply pull those units out of there, give them an [Install] section, and enable them.

[SOLVED] Error to access Windows NTFS Partitions

hi
I'm getting this message error when trying to access a NTFS windows partition
Cannot mount volume.
Error org.freedesktop.DBus.Error.AccessDenied
both partitions C: and D: are listed in Places menubar... but i cant access them
do i have to add a permission to myself user ?
tks
Last edited by almondega (2008-06-22 00:49:26)

solved
from http://www.jefferyfernandez.id.au
how to:
1- Edit the hal daemons security policy
# gedit /etc/dbus-1/system.d/hal.conf
2- Search for <policy context="default">, and change all they itens from "deny" to "allow"
3- reboot, and try to open a NTFS partition, if u get a error message about ntfs-3g, just download from pacman -S ntfs-3g (or search for one pacman -Ss ntfs)
=]

[SOLVED] How to defragment an NTFS partition in Linux?

Hello, I want to defragment an NTFS partition (which contains Windows XP) from Linux especially because when doing that under Windows is not possible to move system files, so I guess from Linux it will offer better results.
Is there any tool that could do it, like fsck?
I've tried this command:
fsck -t ntfs --kerneldefrag /dev/sda1
but it does nothing, it only shows this message:
fsck de util-linux 2.20
Is there any way to do it?
Thanks in advance!
Last edited by ILoveJapaneseGirls (2011-12-28 06:25:30)

jakobm wrote:Please be sure to use the bbs search: Defragment a NTFS partition from LINUX
That thread has absolutely no information other than a list of motivations to use Windows to defrag it... and a link to a buggy Python defragger.
Here's the only bulletproof way to defrag NTFS under Linux:
Make a new partition of the same size (or bigger), and format it to NTFS and mount it at /defragged
Mount your fragged partition at /fragged
rsync -av /fragged /defragged
Wha-la. /defragged is now your fragged partition, defragged. Reformat /fragged and rsync it back if you really must.
Drives get fragmented if you do multiple copies at the same time, so don't do anything else on the drive while it's syninc.
Last edited by dagelf (2014-08-28 07:21:54)

Deleted ntfs partition accidentally using cfdisk, how to restor SOLVED

Hello, please help me with my major prob...I was installing arch that time and I was on the cfdisk to format partitions, unnoticably I had deleted the ntfs partitions on my sata 160gb and replaced them with linux partitions. Is there any means of restoring the files of the ntfs partitions? Please I need your help. THanks
Last edited by kaola_linux (2008-10-13 02:24:16)

http://www.google.com/search?hl=en&q=re … store+ntfs
Last edited by SkonesMickLoud (2008-10-07 06:51:29)

[SOLVED] Shared Firefox Profile on ntfs partition "in use"

After failing to install arch on an ancient computer a year ago, I've successfully installed arch with lightdm and openbox on my current desktop.
Everything works fine except for the firefox profile I share across my partitions. When I run firefox -p and try to use the profile, I get a message that Firefox cannot use the profile because it is in use, even though I've checked that firefox is not running.
I am aware that using openbox without a DE means other partitions aren't auto mounted in filemanagers (I'm using xfe), and I edited the /etc/fstab to mount the ntfs partition:
# /dev/sdb2 LABEL=Data
UUID=(the UUID is correct, I checked) /media/user/Data ntfs rw,auto,user,exec,suid,async,dev,umask=000 0 0
The drive now auto mounts without needing root, but I cannot create new folders even as root (Operation not permitted). Perhaps I've forgotten an option in the fstab?
Last edited by :hovercraft (2014-02-08 00:26:44)

Thanks! That worked perfectly!
I installed ntfs-3g and changed the fstab to the default on that page, and now firefox loads exactly like in my other partitions.

Arch and Win7 cannot open an NTFS partition created by the other

This is almost certainly related to another post where I was struggling to create logical partitions from Windows. Basically, Linux and Minitool Partition Wizard agreed that there were no logical partitions, but the built-in Windows disk utility said there was. I ended up using fdisk from Arch install media, and Minitool and Arch now both saw the logical partitions (Windows shows a big extended partition of free space). I installed Arch just fine, can boot to it and win7... life is good.
Not so much. A key to my setup is having an encrypted partition to share data between OS's. I used TrueCrypt with great success on my former laptop and am now having great difficulty!
Some preliminary information:
# fdisk -l /dev/sda
Disk /dev/sda: 238.5 GiB, 256060514304 bytes, 500118192 sectors
Units: sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 512 bytes
I/O size (minimum/optimal): 512 bytes / 512 bytes
Disklabel type: dos
Disk identifier: 0x1e6513b3
Device Boot Start End Sectors Size Id Type
/dev/sda1 * 2048 2101247 2099200 1G 7 HPFS/NTFS/exFAT
/dev/sda2 2101248 172433407 170332160 81.2G 7 HPFS/NTFS/exFAT
/dev/sda3 172433408 390537215 218103808 104G 7 HPFS/NTFS/exFAT
/dev/sda4 390537216 500118191 109580976 52.3G 5 Extended
/dev/sda5 390539264 391587839 1048576 512M 83 Linux
/dev/sda6 391589888 500118191 108528304 51.8G 83 Linux
I also went partition by partition to check Minitool's agreement on sectors (they match perfectly with the exception that it doesn't show the extended /dev/sda4 container). I triple checked the Minitool partition info properties as you can't copy and paste from it's window, and pasted the fdisk output to minimize errors. I'm showing a column for mini/Arch for both start/stop sectors, and just subtracted them to make sure I got 0. Appears to be perfect alignment:
| part | start (mini) | start (arch) | diff | | end (mini) | end (arch) | diff |
|------+--------------+--------------+------+---+------------+------------+------|
| sda1 | 2048 | 2048 | 0 | | 2101247 | 2101247 | 0 |
| sda2 | 2101248 | 2101248 | 0 | | 172433407 | 172433407 | 0 |
| sda3 | 172433408 | 172433408 | 0 | | 390537215 | 390537215 | 0 |
| sda4 | 390539264 | 390539264 | 0 | | 391587839 | 391587839 | 0 |
| sda5 | 391589888 | 391589888 | 0 | | 500118191 | 500118191 | 0 |
- Screenshot of how Minitool sees my disk
- Screenshot of how Windows disk utility sees my disk
I used TrueCrypt 7.1a on both OS's. I created a non-system encrypted partition using the GUI on Arch with the AES cipher/sha-512 hash, with filesystem as "none." Once created I did:
$ sudo cryptesetup --type tcrypt open /dev/sda3 vault
That worked fine, which I followed with:
$ sudo mkfs.ntfs /dev/mapper/vault
It initialized the device with zero's and then gave me the success/have a nice day message. Closed the volume and rebooted. When I tried to open the device from win7, I got "Incorrect password or not a TrueCrypt volume." Hmmm. I guess I'll try in reverse. I duplicated the procedure exactly as above from win7, this time having TrueCrypt automatically format with NTFS. All succeeds and I can open the device. Reboot into Arch and I get the same message from TrueCrypt! If I try with cryptsetup, it's "No device header detected with this passphrase."
Next, I tried just doing NTFS with no encryption. From Arch:
$ sudo mkfs.ntfs /dev/sda3
All goes well and I can mount it. I boot into Windows and it's not even listed! I used Minitool to issue it a drive letter, at which point clicking that pops up a windows dialog box asking me if I want to format the disk. Format the partition with NTFS in Windows, reboot into Arch and I get:
[jwhendy@arch_zbook ~]$ sudo mount /dev/sda3 /mnt/scratch/
NTFS signature is missing.
Failed to mount '/dev/sda3': Invalid argument
The device '/dev/sda3' doesn't seem to have a valid NTFS.
Maybe the wrong device is used? Or the whole disk instead of a
partition (e.g. /dev/sda, not /dev/sda1)? Or the other way around?
Doesn't matter if I add "-t ntfs" or "-t ntfs-3g." I get the same result.
Just to add a couple more oddities... when I created the NTFS partition in Arch, I also created a file called vault.tc as a TrueCrypt file-based encrypted container. My thinking was that the issue was with TrueCrypt full-partitions and that I could get around it with a plain partition containing an encrypted file. Reboot into windows and the partition isn't shown (as stated above). From Minitool, if I right click the partition and choose "Explore," it lists the partition contents and there is my vault.tc file. Windows thinks it's unformatted!
I noticed the option to backup/restore a TrueCrypt header, and gave a shot at backing up the working TrueCrypt setup on windows to a flash drive, booting to Arch, and then restoring the /dev/sda3 header from the flash drive file. Arch still couldn't open it.
Lastly, I noticed when I go to select a device to encrypt in TrueCrypt, my logical partitions aren't showing up (just like Windows only sees the end of the disk as free space). I just can't help but think something is tweaked in the partition table... basically:
- TrueCrypt sees what Windows sees
- Arch sees what Minitool sees
How could I go about diagnosing further or fixing the issue. This is driving me crazy!
I'd hate to do this given that I already setup my wm, configs, packages, etc... but my last resort attempt would be to wipe my logical partitions and see if I can at least get the win7 disk utility, minitool, arch, and truecrypt to like each other with respect to /dev/sda1-3... and then try to re-add the logicals afterward and re-install arch? I honestly don't know why this would be any different, but was just a thought. The issues from the other post seem to arise with logical partitions not being recognized the same between win/linux.
Or figure out how to just use primaries (like dedicated boot on a USB drive or something). Or fiddle with growing/shrinking windows to see if I can undo whatever is telling windows where/what things are? Really grasping at straws here.
Last edited by jwhendy (2015-06-10 23:32:22)

Hi Ramesh,
Please install the hotfix package and test the issue again:
http://support.microsoft.com/kb/2817576/en-us
In addition, try uncheck the option “confirm open after download” per:
http://jritmeijer.wordpress.com/2006/08/20/some-files-can-harm-your-computer-if-the-file-information-looks-suspicious-or-you-do-not-fully-trust-the-source-do-not-open-the-file/
Regards,
Rebecca Tu
TechNet Community Support

Renaming files with invalid characters in their names on NTFS partitions, introduced by operating systems other than Windows

Essentially, Linux created some files with colons (:) in the name on a NTFS partition where I have Windows installed. I have since uninstalled Linux, but now I can only view these files in Windows Explorer. I can't open them, I can't even rename them to
correct the problem. It's as if they don't exist, because of the invalid search paths.
If I try to rename them in Windows Explorer I get following message.
The file name you specified is no valid or too long.
Specify a different file name.
Well isnt' that something?... isn't that nice? Windows is able to display these files, but it doesn't allow me to open them and it certainly doesn't like me to rename them. So why is it whining about it then, when I'm trying to help? It says "try a different
file name". Yeah, right! Like I haven't tried that one already! It doesn't matter what file name I input it will never accept it.
So what am I supposed to do now? Ditch Windows and go back to Linux? Surely, Microsoft doesn't like the sound of that. Sure, I could reinstall Linux or run a Linux live system to correct the problem. But what good is Windows then? I might as well switch to
Linux altogether.
After doing some research I now know by fact that it's (kind of) possible to rename files from UNIX and UNIX-like operating systems to those compliant with Windows by using something called file name character translation. To some level this is essential and
necessary for Windows interoperability with other operating systems (Windows is not the only operating system in the world). But this seems to be very complicated and I can't get my head around it. My brain is in overload. I don't know where to start.
Once there was a...
There's the Windows Services for UNIX (SFU) 1.0, 2.0, 3.0, 3.5. The first two versions were based on MKS Toolkit, a package licensed by Microsoft from MKS Inc. The later versions were based on the similar Interix product, after Microsoft purchased the company
that made it.
Then there's the new Subsystem for UNIX-based Applications (SUA). These are services for UNIX components. They are supposed to have Client for NFS v3 included as well. But the server components from the SFU line is missing (e.g. Server for NFS). These are included
in Server editions of Windows.
Then there's the Microsoft Knowledge Base article
289627: "How to Enable File Name Character Translation". This article seems to describe exactly my situation.
Windows and UNIX operating systems have restrictions on valid characters that can be used in a file name. The list of illegal characters for each operating system, however, is different. For example, a UNIX file name can use a colon (:), but a Windows
file name cannot use a colon (:). If a UNIX user attempts to create a file with a Windows illegal character on a Windows Services for UNIX network file system (NFS) share, the attempt is unsuccessful and the UNIX client computer receives an input or output
error.
It goes further than that. At first glance, this KB article also seems to offer a solution to this exact problem, with examples as shown below.
For example, the following maps the UNIX colon (:) to a Windows dash (-):
0x3a : 0x2d ; replace client : with - on server
I checked these values in charmap.exe and they are correct. Except for 2D not being a "dash", it's rather a hyphen ("hyphen minus" to be exact), but these two have pretty much the same appearance and they get interchanged a lot, I'm sure
they are used to it by now. (Yes, the characters! They don't mind.)
Then there's this registry key.
HKEY_LOCAL_MACHINE\Software\Microsoft\Server For NFS\CurrentVersion\Mapping
Well, of course, I don't have Server for NFS. So this is a dead end. Well, actually, it was a dead end from the beginning...
1. First of all, I'm not working with a network share on a NAS or SAN storage. The files are on the local disk drive where Windows is installed, so that's a DAS for you.
2. I don't have SFU! Well obviously, I'm on Windows Vista! So that means SUA!
3. SUA are service components only. No server components. Can you guess what that means? Yeah... no "Server for NFS" since it's a server component.
4. Windows Vista is a client side operating system! Server for NFS is only offered for use with Windows Server systems.
5. Back to square one!
So there you have it. They all lived happy for the rest of their lives...
I'm stuck here. Can someone tell me what to do? I mean beyond the obvious option to use Linux to fixa a Windows problem? The NTFS file system itself supports colons in file names. It's Windows that doesn't, and so by default it proclaims it invalid character.
Surely, even a Windows client operating system like Windows Vista should be able to allow the user to at least rename files with invalid characters to something more sensible (from the system point of view) and valid, if not being able to open them as they
are. Just add some crazy voodoo code to it and it will work. If you can make it possible on Windows Server with UNIX user-mode subsystem on NT kernel, then what's stopping you from giving the Windows client system the same benefit?
So what now? Purchase a Windows Server 2012 R2 license, copy my invalid files to a NAS share with NFS on a UNIX or Linux system, and have a go at the Windows registry and Server for NFS? Yeah... you're right, it's probably a bit over the top...
On a second thought... I might as well install Linux again. There are countless situations where Linux has helped me solve problems related to, and more often than not caused by Windows.

Essentially, Linux created some files with colons (:) in the name on a NTFS partition where I have Windows installed. I have since uninstalled Linux, but now I can only view these files in Windows Explorer. I can't open them, I can't even rename them to
correct the problem. It's as if they don't exist, because of the invalid search paths.
If I try to rename them in Windows Explorer I get following message.
The file name you specified is no valid or too long.
Specify a different file name.
Well isnt' that something?... isn't that nice? Windows is able to display these files, but it doesn't allow me to open them and it certainly doesn't like me to rename them. So why is it whining about it then, when I'm trying to help? It says "try a different
file name". Yeah, right! Like I haven't tried that one already! It doesn't matter what file name I input it will never accept it.
So what am I supposed to do now? Ditch Windows and go back to Linux? Surely, Microsoft doesn't like the sound of that. Sure, I could reinstall Linux or run a Linux live system to correct the problem. But what good is Windows then? I might as well switch to
Linux altogether.
After doing some research I now know by fact that it's (kind of) possible to rename files from UNIX and UNIX-like operating systems to those compliant with Windows by using something called file name character translation. To some level this is essential and
necessary for Windows interoperability with other operating systems (Windows is not the only operating system in the world). But this seems to be very complicated and I can't get my head around it. My brain is in overload. I don't know where to start.
Once there was a...
There's the Windows Services for UNIX (SFU) 1.0, 2.0, 3.0, 3.5. The first two versions were based on MKS Toolkit, a package licensed by Microsoft from MKS Inc. The later versions were based on the similar Interix product, after Microsoft purchased the company
that made it.
Then there's the new Subsystem for UNIX-based Applications (SUA). These are services for UNIX components. They are supposed to have Client for NFS v3 included as well. But the server components from the SFU line is missing (e.g. Server for NFS). These are included
in Server editions of Windows.
Then there's the Microsoft Knowledge Base article
289627: "How to Enable File Name Character Translation". This article seems to describe exactly my situation.
Windows and UNIX operating systems have restrictions on valid characters that can be used in a file name. The list of illegal characters for each operating system, however, is different. For example, a UNIX file name can use a colon (:), but a Windows
file name cannot use a colon (:). If a UNIX user attempts to create a file with a Windows illegal character on a Windows Services for UNIX network file system (NFS) share, the attempt is unsuccessful and the UNIX client computer receives an input or output
error.
It goes further than that. At first glance, this KB article also seems to offer a solution to this exact problem, with examples as shown below.
For example, the following maps the UNIX colon (:) to a Windows dash (-):
0x3a : 0x2d ; replace client : with - on server
I checked these values in charmap.exe and they are correct. Except for 2D not being a "dash", it's rather a hyphen ("hyphen minus" to be exact), but these two have pretty much the same appearance and they get interchanged a lot, I'm sure
they are used to it by now. (Yes, the characters! They don't mind.)
Then there's this registry key.
HKEY_LOCAL_MACHINE\Software\Microsoft\Server For NFS\CurrentVersion\Mapping
Well, of course, I don't have Server for NFS. So this is a dead end. Well, actually, it was a dead end from the beginning...
1. First of all, I'm not working with a network share on a NAS or SAN storage. The files are on the local disk drive where Windows is installed, so that's a DAS for you.
2. I don't have SFU! Well obviously, I'm on Windows Vista! So that means SUA!
3. SUA are service components only. No server components. Can you guess what that means? Yeah... no "Server for NFS" since it's a server component.
4. Windows Vista is a client side operating system! Server for NFS is only offered for use with Windows Server systems.
5. Back to square one!
So there you have it. They all lived happy for the rest of their lives...
I'm stuck here. Can someone tell me what to do? I mean beyond the obvious option to use Linux to fixa a Windows problem? The NTFS file system itself supports colons in file names. It's Windows that doesn't, and so by default it proclaims it invalid character.
Surely, even a Windows client operating system like Windows Vista should be able to allow the user to at least rename files with invalid characters to something more sensible (from the system point of view) and valid, if not being able to open them as they
are. Just add some crazy voodoo code to it and it will work. If you can make it possible on Windows Server with UNIX user-mode subsystem on NT kernel, then what's stopping you from giving the Windows client system the same benefit?
So what now? Purchase a Windows Server 2012 R2 license, copy my invalid files to a NAS share with NFS on a UNIX or Linux system, and have a go at the Windows registry and Server for NFS? Yeah... you're right, it's probably a bit over the top...
On a second thought... I might as well install Linux again. There are countless situations where Linux has helped me solve problems related to, and more often than not caused by Windows.

[SOLVED] SystemD NTFS partition issue's

Similar Messages

Maybe you are looking for