filesystem readonly after 19Sep update to 10.10

[Peter T Hayward]

Today's update seriously broke my virtualbox build of 10.10.
Download of 93MB, including kernel 2.6.35-22.
During package processing samba-common failed with IO error. After that I had only read-only access to the whole filesystem and could not execute sudo.
Had to power off and on. Boot failed saying no /dev /sys /proc, /sbin/init

The first sign of a problem was when synaptic was replacing
samba-common 2:3.5.4 ... from ubuntu6 -> ubuntu7
"update-alternatives: unable to stat /var/lib/dpkg/alternative/builtins.7.gz"
"I/O error"
"unable to flush updated status of samba-common "... etc
Then nothing worked - saying read-only filesystem.

I've booted on the 10.10 beta live DVD and tried to mount the VB drive. Says it is mounted (not) or in use.
fsck also says mounted/in use
file /dev/sda1 tells me that a journal recovery is needed

Due to the nature of it I cannot retrieve anything more about this crash.

[atti (spamtub)]

same here.
i don't recall the details, but right after (or during) upgrade on 2010-10-10 filesystem became readonly.
upgrade was maverick->maverick.
i'm not sure what caused this, attaching dpkg.log.
after reboot it jumped to busybox prompt saying things like
===
mount: Mounting /dev on /root/dev failed: No such file or directory
===
i was unable to mount my Ubuntu partition from busybox prompt. but it mounted successfully from Ubuntu Live CD.
in dmesg error was (full dmesg attached):
===
[ 3.543155] EXT4-fs (sda6): mounted filesystem with ordered data mode. Opts: (null)
[ 3.559226] usb 3-1: device not accepting address 5, error -71
===
i've run 'e2fsck' command suggested by GParted. it found lots of errors (log attached).
now system doesn't boot saying something about init cannot find mountall. and then it hangs. i suppose some core system files were corrupted.

i can mount my ubuntu partition, so please let me know if i can provide more details to troubleshoot this.

also is there a way to 'repair' Ubuntu installation? do i just need to replace corrupted system files?

--
thanks, Vladimir

[Charlie Kravetz (cjkgeek)]

Thank you for taking the time to report this bug and helping to make Ubuntu better. We are sorry that we do not always have the capacity to look at all reported bugs in a timely manner. There have been many changes since you reported this issue in the Maverick Meerkat development version. Is there any way to determine if this was still an issue in the final release of Ubuntu 10.10? Thanks for helping improve Ubuntu. Testing before the final release is very important.

[Charlie Kravetz (cjkgeek)]

@atti : If you attempted an upgrade of Maverick Meerkat to Ubuntu 10.10 final release, that is not the same issue as was originally reported.

[atti (spamtub)]

hi,

Charlie, thank you for your reply. i've somehow managed to repair my installation. this issue didn't happen with further updates.

[Peter T Hayward (energonic)]

I have not had this problem with installing or updating later versions of 10.10, all running in a virtualbox vm, so I think it was a development glitch.

[Charlie Kravetz (cjkgeek)]

Thank you for your responses. I am marking this bug as fixed since it was fixed for the final release of Ubuntu 10.10. Please continue to report bugs you find. Your assistance in improving Ubuntu is greatly appreciated.