Ubuntu 9.10 says that the filesystem has been damaged

[Josema]

I installed Ubuntu 9.10 Alpha 5 Desktop in VirtualBox's virtual machine that he was executing under Ubuntu 9.04 Desktop and whenever he was installing some program or updates, on having restarted it was not starting the graphical environment and was putting his that the filesystem (ext4) had damaged, and a fsck was forced to realize to modify the filesystem and that was returning to the normality, but when he was installing another program or update, the same mistake goes out for me.

Thank you.

[Scott Testerman (scott-testerman)]

I'm having the same problem here, using Kubuntu 9.04 with VirtualBox 2.1.4-dfsg-1ubuntu3.

Kubuntu 9.10 running under VirtualBox frequently reports filesystem errors when starting. Running e2fsck doesn't really seem to find anything wrong, but then the virtual machine will restart properly.

About the virtual machine: Kubuntu 9.10 was installed with all default options from a Desktop CD.

[Scott Testerman (scott-testerman)]

After paying more attention to the reported error, it appears this was a UTC vs. local time issue. Changing "UTC=yes" to "UTC=no" in /etc/default/rcS has cured the issue.

[Scott Testerman (scott-testerman)]

Did a developer release a fix for this issue? I think the correct designation would be "Invalid," or possibly even "Won't fix" if this indeed was a user issue. "Fix released" indicates that VirtualBox or its packaging was updated.

Also, were you able to verify that the UTC issue was the problem? If so please document here so that future bug reports on this issue can be verified with this report. Thanks!

[Josema (jmvalbuenap)]

This problem is solved in the Alpha 5.

Thank you

[Scott Testerman (scott-testerman)]

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 the current status, under the Status column, and change the Status back to "New". Thanks again!

[Nicola Ferralis (feranick)]

According to these other reports, the problem is still there in alpha 5, when using VirtualBox. Those are possible duplicates:

https://bugs.launchpad.net/ubuntu/+bug/423925

https://bugs.launchpad.net/ubuntu/+bug/424291

[Josema (jmvalbuenap)]

The solution The solution is the one that Scott Testerman put in the fourth commentary. To modify the file they must execute it across the Terminus messing about on this: sudo gedit /etc/default/rcS

Thank you

[Josema (jmvalbuenap)]

The solution is the one that Scott Testerman put in the fourth commentary. To modify the file they must execute it across the Terminus messing about on this: sudo gedit /etc/default/rcS

Thank you

[Scott Testerman (scott-testerman)]

This appears to be an issue of user error at install time, specifically in regards to the installer asking if the clock is set to UTC. Many people who are installing in VirtualBox may be doing so on top of an existing Ubuntu install, where their computer clock may, indeed, be set to UTC. The passthrough to VB is a localtime passthrough AFAIK. Therefore, when the virtual install comes up, it's using local time and assuming that's UTC, but this can make for a disk that appears to have been edited in the future. The filesystem screams "error."

It would seem there are two ways to fix this: 1) an updated installer that checks to see if it's being installed in VirtualBox, or 2) the easiest solution: update the installer message to inform the user that virtual machines may need to be set to local time even if the machine is set to UTC.

[Nicola Ferralis (feranick)]

Another possible duplicate:

https://bugs.launchpad.net/ubuntu/+bug/424529

although this bug is present with a regular LiveCD installation (i.e. not through VBox).

[Brian Murray (brian-murray)]

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 '423247', so it is being marked as such. Please look at the other bug report to see if there is any missing information that you can provide, or to see if there is a workaround for the bug. Additionally, any further discussion regarding the bug should occur in the other report. Please continue to report any other bugs you may find.

[Scott Testerman (scott-testerman)]

This bug is not a duplicate of 423247. That bug applies to first boot only; this one does not.

[Josema (jmvalbuenap)]

Warning: This error not only happens in VirtualBox. Also it happens in instalations of Ubuntu 9.10 that are not virtual.

[Scott Testerman (scott-testerman)]

This bug report did not indicate that it was in relation to installations other than VirtualBox. Both the title and the description indicate that it is for VirtualBox only. If you are also experiencing this problem in installations that are not in VirtualBox, you may wish to follow progress in bug 423247.

Please note that Colin Watson has asked that no further reports be added to 423247.

[Scott Testerman (scott-testerman)]

I'm still unable to reproduce this using the Alternate (debian installer) CD, but it still appears to happen using the Ubiquity installer only. Debian installer asks for UTC vs. local time setting; Ubiquity does not.

Please try to verify the same behavior on your system.