root@moon_gen_2:~# fsck /dev/hdd1
fsck 1.40 (29-Jun-2007)
fsck: fsck.ntfs-3g: not found
fsck: Error 2 while executing fsck.ntfs-3g for /dev/hdd1
root@moon_gen_2:~# file -s /dev/hdd1
/dev/hdd1: Linux rev 1.0 ext3 filesystem data (large files)
root@moon_gen_2:~# fsck.ext3 /dev/hdd1
e2fsck 1.40 (29-Jun-2007)
/dev/hdd1: clean, 1072522/14663680 files, 21521479/29304560 blocks
=> means fsck got in trouble because of sys-fs/ntfs3g
root@moon_gen_2:~# emerge -vp sys-fs/ntfs3g sys-fs/e2fsprogs
These are the packages that would be merged, in order:
Calculating dependencies... done!
[ebuild R ] sys-fs/ntfs3g-1.616-r2 USE="-suid" 0 kB
[ebuild R ] sys-fs/e2fsprogs-1.40 USE="nls -static" 0 kB
dhp@moon_gen_2:~$ equery b /sbin/fsck
[ Searching for file(s) /sbin/fsck in *... ]
dhp@moon_gen_2:~$ equery f sys-fs/ntfs3g |grep bin
Thats right, there are no fsck.ntfs-3g installed at all.
emerge -C ntfs3g
problem persists !!!
Re-merging ntfs3g then sys-fs/e2fsprogs does not help.
Created attachment 123801 [details]
emerge --info here:
Same problem with mount:
root@moon_gen_2:~# mount /dev/hdd1 /mnt/arch2
hangs, and shall be killed with
killall -9 mount
# mount -t ext3 /dev/hdd1 /mnt/arch2
My systems start fine because I do not have any auto-fs line in /etc/fstab
Created attachment 123803 [details]
First strace was for fsck. Here is mount attempt.
Kindly attach your fstab.
Created attachment 123815 [details]
Well, then change it to 0 0, not 0 2 - since there's no fsck anywhere in ntfs3g.
Do you have enough info to proceed bug ?
(In reply to comment #6)
> Well, then change it to 0 0, not 0 2 - since there's no fsck anywhere in
Fstab is not a problem. I was talinkg from the beginning about manual mount.
(In reply to comment #7)
> Fstab is not a problem. I was talinkg from the beginning about manual mount.
And? Why are you instructing the thing to fsck the filesystem if there's no such feature available?! Does it work w/ 0 0 or not?
(In reply to comment #8)
> Does it work w/ 0 0 or not?
(In reply to comment #2)
> My systems start fine because I do not have any auto-fs line in /etc/fstab
I said: despite of bug, box starts well because I specify exact FS on FSTAB; other friends who use autofs on every line would have encountour problems.
Fact is: it bugs on CLI, so please stop asking about fstab, since it is counter-indicative to this bug. "0 0" vs "0 2" is thus an off-topic debate.
Could you answer the damned simple question? AFA - it works just fine here unless I stick nonsense to fstab.