shutil.py", line 25 (Read-only system)

Bug #66102 reported by George Hill on 2006-10-14
2
Affects Status Importance Assigned to Milestone
ubiquity (Ubuntu)
Undecided
Unassigned

Bug Description

The error message is reproduced below: I was asked to attach 3 log files, which I have, but cannot see how to!!
George Hill

We’re sorry; the installer crashed. Please file a new bug report at https://launchpad.net/distros/ubuntu/+source/ubiquity/+filebug (do not attach details to any existing bug) and a developer will attend to the problem as soon as possible. To help developers understand what went wrong, include the following detail in your bug report, and attach the files /var/log/installer/syslog, /var/log/syslog and /var/log/partman:
Traceback (most recent call last):
  File “/usr/bin/ubiquity”, line 130, in?
    install(sys.argv[1])
  File “/usr/bin/ubiquity”, line 55, in install
    ret = wizard.run()
  File “/usr/lib/python2.4/site-packages/ubiquity/frontend/gtkui.py”, line 550, in progress_loop
    raise RuntimeError, (“Install failed with exit code %s\n%s” %
  RuntimeError: Install failed with exit code 1

Traceback (most recent calls)
  File “/usr/share/ubiquity/install.py”, line 1263, in?
    if install.run():
  File “/usr/share/ubiquity/install.py”, line 284, in run
    if not self.copy_all():
  File “/usr/share/ubiquity/install.py”, line 466, in copy_all
    shutil.copyfile(sourcepath, targetpath)
  File “/usr/lib/python2.4shutil.py” line 49 in copyfile
    copyfileobj(fsrc, fdst)
  File “/usr/lib/python2.4shutil.py” line 25 in copyfileobj
    fdst.write(buf)
  IOError: [Errno 30] Read-only file system

George Hill (georgebhill) wrote :

Now I understand the system, here are the three logs, zipped up.

Paul Dufresne (paulduf) wrote :

Attaching /var/log/installer/syslog to make it easier.

Paul Dufresne (paulduf) wrote :

I have extracted the files from the zip to make it easier. (partman)

Paul Dufresne (paulduf) wrote :

I have extracted the files from the zip to make it easier. (/var/log/syslog)

Paul Dufresne (paulduf) wrote :

Thanks for this bug contribution!

Colin Watson (cjwatson) wrote :

Oct 14 13:05:53 ubuntu kernel: [ 2630.033213] journal_bmap: journal block not found at offset 783 on hdb1
Oct 14 13:05:53 ubuntu kernel: [ 2630.033274] Aborting journal on device hdb1.
Oct 14 13:05:53 ubuntu kernel: [ 2630.048360] ext3_abort called.
Oct 14 13:05:53 ubuntu kernel: [ 2630.048764] EXT3-fs error (device hdb1): ext3_journal_start_sb: Detected aborted journal
Oct 14 13:05:53 ubuntu kernel: [ 2630.050216] Remounting filesystem read-only

Thanks for your report. This particular error (about which there's more detail in the above log messages, basically saying that the kernel gave up trying to handle a filesystem on the hard disk) is often due to a faulty hard disk. It may help to check whether the hard disk is old and in need of replacement, or to move the system to a cooler environment.

Edgy's installer will notice this error and display roughly the above message instead of a traceback.

Changed in ubiquity:
status: Unconfirmed → Rejected
To post a comment you must log in.
This report contains Public information  Edit
Everyone can see this information.

Other bug subscribers

Related questions