*** This bug is a duplicate of bug 48806 ***
https://bugs.launchpad.net/bugs/48806
Thank you for taking the time to report this bug and helping to make
Ubuntu better. This particular bug has already been reported and is a
duplicate of bug 48806, so it is being marked as such. Please look at
th
It was a fresh install on a different machine than before.
When setting up partitions during the installation, I chose to use the
preexisting FAT32 Windows partition as vfat, to be mounted on /windows.
Installer put it in fstab, with "1" in the sixth field, causing it to be
fscked (with the same p
I apologize for the misguided reply I must have been asleep when I read
that. Thanks for clarifying though it gave me a eye into the issue at
hand.
How did you go about setting up for Linux to read your windows partition?
What steps did you take?
Please be as detailed as possible.
I am assuming
Dear Anzenketh,
Thank you for replying to the bug report. Please read the first post. It
gives you the insight what is wrong, now, as well as 2.5 years ago.
To quote fstab(5) man page:
"The sixth field, (fs_passno), is used by the fsck(8) program to
determine the order in which filesystem check
** Changed in: base-installer (Ubuntu)
Status: New => Incomplete
--
vfat partition fscked on every boot
https://bugs.launchpad.net/bugs/125730
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs mailing list
ubuntu-bug
Thank you for taking time to report this issue.
Thank you for taking the time to report this bug and helping to make
Ubuntu better. Unfortunately, we cannot work on this bug because your
description didn't include enough information. You may find it helpful
to read "How to report bugs effectively"
Still happens, even with Ubuntu 9.10!
vfat partition was selected during installation to be mounted on
/windows. fsck on boot couldn't check it, causing mounting to "contain
errors", thus mounting root partition read-only... This scenario is even
worse than previous, which was reported 2.5 years a
We are closing this bug report because it lacks the information we need
to investigate the problem, as described in the previous comments.
Please reopen it if you can give us the missing information, and don't
hesitate to submit bug reports in the future. To reopen the bug report
you can click on t
Thank you for taking the time to report this bug and helping to make
Ubuntu better. You reported this bug a while ago and there hasn't been
any activity in it recently. We were wondering if this is still an issue
for you. Feisty is no longer supported, can you try with the latest
Ubuntu release? Th
