oops in sync_sb_inodes

Bug #64774 reported by Dave Wood
2
Affects Status Importance Assigned to Milestone
linux (Ubuntu)
Invalid
Undecided
Unassigned
linux-source-2.6.17 (Ubuntu)
Won't Fix
Undecided
Unassigned

Bug Description

This was a fresh install using the desktop ISO. At 94% got an error dialog about failing to install grub, and then an "Installer crashed" dialog:

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 264, in run
    self.progress_loop()
  File "/usr/lib/python2.4/site-packages/ubiquity/frontend/gtkui.py", line 553, in progress_loop
    raise RuntimeError, ("Install failed with exit code %s; see "
RuntimeError: Install failed with exit code 1; see /var/log/installer/syslog and /var/log/syslog

Revision history for this message
Dave Wood (dave-woodtopia) wrote :

Attachment #1...

Revision history for this message
Dave Wood (dave-woodtopia) wrote :
Revision history for this message
Dave Wood (dave-woodtopia) wrote :
description: updated
description: updated
description: updated
Revision history for this message
Colin Watson (cjwatson) wrote : Re: Installer crashed -- grub and/or python related?

Wow, /var/log/syslog displays a kernel oops in sync_sb_inodes that I've never seen before. This is a kernel bug. Ben?

Revision history for this message
Kjell Braden (afflux) wrote :

Hardy Heron 8.04 was recently released. It would be helpful if you could test the new release and verify if this is still an issue - http://www.ubuntu.com/getubuntu/download . You should be able to test your bug using the LiveCD. Please let us know your results. Thanks.

Changed in linux-source-2.6.17:
status: New → Won't Fix
Changed in linux:
status: New → Incomplete
Revision history for this message
Kjell Braden (afflux) wrote : expired

We are closing this bug report because it lacks the information we need to investigate the problem, as described in the previous comments. Please reopen it if you can give us the missing information, and don't hesitate to submit bug reports in the future. To reopen the bug report you can click on the current status, under the Status column, and change the Status back to "New". Thanks again!

Changed in linux:
status: Incomplete → Invalid
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.