** Package changed: util-linux (Ubuntu) => ubiquity (Ubuntu)
** Changed in: ubiquity (Ubuntu)
Status: Invalid => Confirmed
** Summary changed:
- Boot sequence looks for nonexistent fsck.ntfs
+ Ubiquity generates bad fstab with NTFS partitions
--
Ubiquity generates bad fstab with NTFS pa
@scott: I agree with you. I filled this bug report as part of the new ubuntu
boot experience.
That wrong line of fstab was not written by me but generated by ubiquity at
install time. I suppose ubiquity developers should fix this little bug.
--
Boot sequence looks for nonexistent fsck.ntfs
http
The missing fsck.ntfs message is just a warning, it's otherwise ignored
and the filesystem will be mounted normally.
To suppress the warning, just fix your fstab
** Changed in: util-linux (Ubuntu)
Status: Confirmed => Invalid
--
Boot sequence looks for nonexistent fsck.ntfs
https://bugs.
@mniess: I agree with you, ubiquity should create the partition entry
with a "0".
--
Boot sequence looks for nonexistent fsck.ntfs
https://bugs.launchpad.net/bugs/441242
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs mai
At least until the fsck.ntfs becomes available and installed by default
in Ubuntu.
** Also affects: ubiquity
Importance: Undecided
Status: New
--
Boot sequence looks for nonexistent fsck.ntfs
https://bugs.launchpad.net/bugs/441242
You received this bug notification because you are a me
I am running into the same problem with fsck.ntfs not found on boot,
with a ntfs partition mounted at boot. A temporary fix, posted above was
to change the last 1, to a 0. But that doesn't seam like a great fix,
since there are days (very few mind you) that I do not need to transfer
files to that p
I have the same problem and I set up the ntfs partitions to be mounted
in a /media subdirectory during install. So the easiest fix is changing
the fstab entry ubiquity creates. Shall I open a new bug for this or can
this one just be assigned to ubiquity?
--
Boot sequence looks for nonexistent fsc
As a workaround you can change the number 1 at the end of the line into a 0 so
that i says
UUID=7260D4F760D4C2D1 /media/storage ntfs defaults,nls=utf8,umask=000,gid=46 0 0
the question would be now if util-linux should blacklist ntfs drives
since there is no fsck program for them yet if drive che
This is the line:
# /media/storage was on /dev/sdb1 during installation
UUID=7260D4F760D4C2D1 /media/storage ntfs
defaults,nls=utf8,umask=000,gid=46 0 1
--
Boot sequence looks for nonexistent fsck.ntfs
https://bugs.launchpad.net/bugs/441242
You received this bug notification because y
How have did you set up your system to mount the drive on boot?
If you added a line to the fstab file, please add this line to the bug report.
Thanks in advance.
** Changed in: util-linux (Ubuntu)
Status: New => Incomplete
--
Boot sequence looks for nonexistent fsck.ntfs
https://bugs.laun
Thanks.
** Changed in: ubuntu
Status: Incomplete => New
** Package changed: ubuntu => util-linux (Ubuntu)
--
Boot sequence looks for nonexistent fsck.ntfs
https://bugs.launchpad.net/bugs/441242
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribe
This is what i see at boot time (grabbed from TTY1):
fsck from util-linux-ng 2.1686d4e-7813-4b0f-8ab4-d0e5bf2551bf
fsck from util-linux-ng 2.16
fsck: fsck.ntfs: not found
fsck: Error 2 while executing fsck.ntfs for /dev/sdb1
/dev/sda2: clean, 332020/1835008 files, 3061327/7333672 blocks
* Setting
Can you provide the full error message you get?
** Changed in: ubuntu
Status: New => Incomplete
--
Boot sequence looks for nonexistent fsck.ntfs
https://bugs.launchpad.net/bugs/441242
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu
13 matches
Mail list logo
