fstab mistake after upgrade from 11.10

Bug #990499 reported by ivan
8
This bug affects 1 person
Affects Status Importance Assigned to Milestone
os-prober (Ubuntu)
New
Undecided
Unassigned

Bug Description

After i upgrade from 11.10 to 12.04 LTS, and finished the upgrade.
But when startup ubuntu, i can't sign in.
after that, i went to the terminal, i found the /etc/fstab has a mistake.
before upgrade /etc/fstab was
proc /proc proc nodev,noexec,nosuid 0 0
/dev/sdb1 /home ext4 errors=remount-ro 0 1
/dev/sdb2 / ext4 errors=remount-ro 0 1

after upgrade it change to
proc /proc proc nodev,noexec,nosuid 0 0
/dev/sda1 /home ext4 errors=remount-ro 0 1
/dev/sda2 / ext4 errors=remount-ro 0 1

because my laptop has two hadrdisk, sda is my winodws install on, and sdb is my ubuntu.

i correct the fstab, and sign in again. i found that is ok.

Tags: bot-comment
Revision history for this message
Ubuntu Foundations Team Bug Bot (crichton) wrote :

Thank you for taking the time to report this bug and helping to make Ubuntu better. It seems that your bug report is not filed about a specific source package though, rather it is just filed against Ubuntu in general. It is important that bug reports be filed about source packages so that people interested in the package can find the bugs about it. You can find some hints about determining what package your bug might be about at https://wiki.ubuntu.com/Bugs/FindRightPackage. You might also ask for help in the #ubuntu-bugs irc channel on Freenode.

To change the source package that this bug is filed about visit https://bugs.launchpad.net/ubuntu/+bug/990499/+editstatus and add the package name in the text box next to the word Package.

[This is an automated message. I apologize if it reached you inappropriately; please just reply to this message indicating so.]

tags: added: bot-comment
affects: ubuntu → os-prober (Ubuntu)
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.