12.10 to 13.04 upgrade failed - Read-only file system - system UNUSABLE

[potwash35]

Hello

I've searched many other posts about failed upgrades to 13.04 but haven't found any similar issues. If they are any which I've missed please point me in the right direction and accept my apologies.

I've upgraded from 12.10 to 13.04 and now have a completely unusable system!

I initially followed the reminder saying "new version 13.04 is available". The upgrade proceeded until shortly after it prompted me to restart services (ie dependencies of NSS), it then failed, leaving the system completely unusable!!!

I get a Python traceback and messages saying "read-only file system"???

When I reboot it fails to mount the root file system, and I get a kernel panic!!!

To check if I'd done anything wrong and to get more information I reloaded by installing a clean 12.10. I repeated the upgrade running update-manager from a shell. It failed in the same place, see below. I have since repeated the whole process again and get exactly the same failure.

Any help appreciated.

Thanks in advance.



test@server1t:~$ update-manager
Checking for a new Ubuntu release
authenticate 'raring.tar.gz' against 'raring.tar.gz.gpg'
extracting 'raring.tar.gz'

Traceback (most recent call last):
File "/usr/lib/python2.7/logging/__init__.py", line 874, in emit
stream.write(fs % msg.encode("UTF-8"))
File "/usr/lib/python2.7/logging/__init__.py", line 834, in flush
if self.stream and hasattr(self.stream, "flush"):
IOError: [Errno 30] Read-only file system
Logged from file DistUpgradeViewGtk3.py, line 343
Traceback (most recent call last):
File "/usr/lib/python2.7/logging/__init__.py", line 874, in emit
stream.write(fs % msg.encode("UTF-8"))
File "/usr/lib/python2.7/logging/__init__.py", line 834, in flush
if self.stream and hasattr(self.stream, "flush"):
IOError: [Errno 30] Read-only file system
Logged from file DistUpgradeViewGtk3.py, line 343
Traceback (most recent call last):
File "/usr/lib/python2.7/logging/__init__.py", line 874, in emit
stream.write(fs % msg.encode("UTF-8"))
File "/usr/lib/python2.7/logging/__init__.py", line 834, in flush
if self.stream and hasattr(self.stream, "flush"):
IOError: [Errno 30] Read-only file system
Logged from file DistUpgradeViewGtk3.py, line 503



Here's partial output at the time it fails from the terminal box in the Distribution Update window:




...

Setting up libxkbcommon0:amd64 (0.2.0-0ubuntu3) ...
Setting up libxtst6:amd64 (2:1.2.1-1ubuntu0.13.04.1) ...


unable to fsync updated status of `gvfs-common': Input/output error
touch: cannot touch ‘/var/lib/update-notifier/dpkg-run-stamp’: Read-only file system
sh: 1: cannot create /var/lib/update-notifier/updates-available: Read-only file system
Error in function:
Traceback (most recent call last):
File "/usr/lib/python2.7/logging/__init__.py", line 874, in emit
stream.write(fs % msg.encode("UTF-8"))
File "/usr/lib/python2.7/logging/__init__.py", line 834, in flush
if self.stream and hasattr(self.stream, "flush"):
IOError: [Errno 30] Read-only file system
Logged from file DistUpgradeViewGtk3.py, line 475
Traceback (most recent call last):
File "/usr/lib/python2.7/logging/__init__.py", line 874, in emit
stream.write(fs % msg.encode("UTF-8"))
File "/usr/lib/python2.7/logging/__init__.py", line 834, in flush
if self.stream and hasattr(self.stream, "flush"):
IOError: [Errno 30] Read-only file system
Logged from file DistUpgradeApport.py, line 43
Traceback (most recent call last):
File "/usr/lib/python2.7/logging/__init__.py", line 874, in emit
stream.write(fs % msg.encode("UTF-8"))
File "/usr/lib/python2.7/logging/__init__.py", line 834, in flush
if self.stream and hasattr(self.stream, "flush"):
IOError: [Errno 30] Read-only file system
Logged from file DistUpgradeApport.py, line 48


After it fails a crash report pop-up says:

The application Ubuntu Software Center has closed unexpectedly
Executable Path: /usr/share/software-center/update-software-center

When I close this a further pop-up reports:
Invalid problem report
The problem report is damaged and cannot be processed
OSError(30, 'Read-only file system')

which creates another problem report and we go round in circles.

Eventually I get a popup which says:
"Could not install the upgrades"
The upgrade has aborted. Your system could be in a unusable state. A recovery will run now (dpkg --configure -a).

This also fails, presumably because the file system is read-only.

When I reboot the system is COMPLETELY unusable!!!

[popaclay]

I am having a similar problem. I edam dual booting with w7.
When I first install xubuntu, no problem. When I update, a new kernel is add. Then Ii get either an unstable system or I get "attempt to read or write outside of disk hd0. Press any key to contine...." Then a kernel panic. Tried it three times.

Similar issue at this post- http://askubuntu.com/questions/299817/13-04-boot-error-after-update.

[popaclay]

I am having a similar problem. I edam dual booting with w7.
When I first install xubuntu, no problem. When I update, a new kernel is add. Then Ii get either an unstable system or I get "attempt to read or write outside of disk hd0. Press any key to contine...." Then a kernel panic. Tried it three times.

Similar issue at this post- http://askubuntu.com/questions/299817/13-04-boot-error-after-update.