I was attempting to install the program on a hard drive which is attached to the MoBo via a HighPoint Rocket 133SB IDE controller card. It showed up as /hdg

Bug #71728 reported by Mark Rich
4
Affects Status Importance Assigned to Milestone
ubiquity (Ubuntu)
Invalid
Medium
Unassigned

Bug Description

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/kde-ui.py", line 308, in run
    self.progress_loop()
  File "/usr/lib/python2.4/site-packages/ubiquity/frontend/kde-ui.py", line 538, in progress_loop
    raise RuntimeError, ("Install failed with exit code %s\n%s" %
RuntimeError: Install failed with exit code 1
Traceback (most recent call last):
  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 455, in copy_all
    os.mkdir(targetpath, mode)
OSError: [Errno 30] Read-only file system: '/target/usr/lib/openoffice/share/wordbook/en-US'

Revision history for this message
Mark Rich (mark-richimaging) wrote :
Revision history for this message
Mark Rich (mark-richimaging) wrote :
Revision history for this message
Mark Rich (mark-richimaging) wrote :
Revision history for this message
Henrik Nilsen Omma (henrik) wrote :

Hi Mark. Thank you for reporting and providing logs. It may the controller card that confuses the partition manager, which is claiming 'not a valid identifier'. It take it this is happening as you start the partitioning process?

Marking the bug as Confirmed and a developer will have a closer look.

Changed in ubiquity:
importance: Undecided → Medium
status: Unconfirmed → Confirmed
Revision history for this message
Colin Watson (cjwatson) wrote :

/lib/partman/recipes.sh: line 31: local: `-': not a valid identifier

Henrik, this is actually just a harmless difference between shell implementations; you can ignore it. The real problem is:

Nov 14 04:17:18 ubuntu kernel: [17180526.744000] hdg: dma_timer_expiry: dma status == 0x25
Nov 14 04:17:28 ubuntu kernel: [17180536.744000] hdg: DMA interrupt recovery
Nov 14 04:17:28 ubuntu kernel: [17180536.744000] hdg: lost interrupt
Nov 14 04:17:28 ubuntu kernel: [17180536.744000] attempt to access beyond end of device
Nov 14 04:17:28 ubuntu kernel: [17180536.744000] hdg3: rw=1, want=4073509578, limit=3727080
Nov 14 04:17:28 ubuntu kernel: [17180536.836000] attempt to access beyond end of device
Nov 14 04:17:28 ubuntu kernel: [17180536.836000] hdg3: rw=1, want=2830417410, limit=3727080
Nov 14 04:17:30 ubuntu kernel: [17180538.860000] Aborting journal on device hdg3.
Nov 14 04:17:31 ubuntu kernel: [17180539.484000] ext3_abort called.
Nov 14 04:17:31 ubuntu kernel: [17180539.484000] EXT3-fs error (device hdg3): ext3_journal_start_sb: Detected aborted journal
Nov 14 04:17:31 ubuntu kernel: [17180539.484000] Remounting filesystem read-only

... i.e. your disk drive starts to return errors at some point during the installation. More recent versions of the installer (Ubuntu 6.10 and later) will respond to this with a message along the following lines:

"This particular error 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."

Changed in ubiquity:
status: Confirmed → Rejected
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.