*** This bug is a duplicate of bug 368959 ***
https://bugs.launchpad.net/bugs/368959
It seems to be a proper bug after all, and one that I suffer from myself
:)
I'll mark it as a duplicate of
https://bugs.launchpad.net/ubuntu/+bug/368959 and keep digging for a
solution.
** This bug has been
/etc/fstab now contains:
# /etc/fstab: static file system information.
#
#
proc /proc proc defaults
00
/dev/sda2
UUID=6120e91d-2f93-4d84-aa1a-0e78227a8bf0
/
Hi Rich,
apparently we need some more information to understand this problem.
To be honest, at the moment it seems rather more like a configuration problem
than a bug to me, but we'll try to work this out.
I missed something the first time: your fstab is still not entirely correct:
The lines
/de
** Changed in: linux-meta (Ubuntu)
Status: New => Incomplete
--
cannot mount usb sticks after upgrade
https://bugs.launchpad.net/bugs/372496
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs mailing list
ubuntu-bugs@
Per luca-ing, I changed all the instances of "nonauto" to "noauto" in
/etc/fstab. I rebooted, and this did NOT correct the problem. I am
changing the status back to new.
I still cannot see the mount the USB drives after the correction.
** Changed in: linux-meta (Ubuntu)
Status: Invalid =
After revision, my /etc/fstab file contains:
# /etc/fstab: static file system information.
#
#
proc /proc proc defaults
00
/dev/sda2
UUID=6120e91d-2f93-4d84-aa1a-0e782
--
cannot mount usb sticks after upgrade
https://bugs.launchpad.net/bugs/372496
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-b
Hi, thanks for taking the time to report problem.
It seems this is not a bug but simply a typo in your /etc/fstab
Instead of "nonauto", you need to use "noauto" (note: *no* instead of *non*).
Correcting this should solve your problem. If it doesn't please reopen this bug
report by clicking on the
