Ubuntu
ubiquity package

  1. Bug #71728
  2. Activity log

Activity log for bug #71728

Date Who What changed Old value New value Message
2006-11-14 04:54:28 Mark Rich bug added bug
2006-11-14 04:59:05 Mark Rich bug added attachment 'partman' (I forgot to include this and the other requested files initially. (/var/log/installer/syslog, /var/log/syslog, & /var/log/parman).)
2006-11-14 05:00:17 Mark Rich bug added attachment 'syslog' (I forgot to include this and the other requested files initially. /var/log/syslog)
2006-11-14 05:00:48 Mark Rich bug added attachment 'syslog' (I forgot to include this and the other requested files initially. /var/log/installer/syslog)
2006-12-15 16:01:12 Henrik Nilsen Omma ubiquity: status Unconfirmed Confirmed
2006-12-15 16:01:12 Henrik Nilsen Omma ubiquity: importance Undecided Medium
2006-12-15 16:01:12 Henrik Nilsen Omma ubiquity: statusexplanation 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.
2007-01-02 17:09:48 Colin Watson ubiquity: status Confirmed Rejected
2007-01-02 17:09:48 Colin Watson ubiquity: statusexplanation 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. /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."