Ubuntu
debian-installer package

Gutsy Alternate fails: Debootstrap Error

Bug #143963 reported by TJ
14
This bug affects 1 person
Affects Status Importance Assigned to Milestone
debian-installer (Ubuntu)
Invalid
Undecided
Unassigned

Bug Description

Binary package hint: linux-source-2.6.22

This is related to bug #143958 "Gutsy Alternate fails: cannot detect and mount CD-ROM" since after working around that bug, this one occurs later in the install. I'm not sure if they are related or stand-alone.

After entering user-name and password the installer reports:

[!!] Install the base system
Debootstrap Error
Failed to determine the codename for the release

I saved the install logs onto the local disk, rebooted into Feisty and transferred them over to my primary laptop. The log shows:

main-menu[3246]: INFO: Menu item 'base-installer' selected
base-installer: error: exiting on error base-installer/no_codename
main-menu[3246]: WARNING **: Configuring 'base-installer' failed with error code 1
main-menu[3246]: WARNING **: Menu item 'base-installer' failed.
main-menu[3246]: INFO: Modifying debconf priority limit from 'high' to 'medium'
debconf: Setting debconf/priority to medium

Revision history for this message
TJ (tj) wrote :

Gone through the same experience with an Acer Travelmate C104TCi. It also experiences bug #143958 starting from an external IEEE1394 DVD-ROM/CD-RW drive. I correct that bug using the workaround and installation continues until this point, where I've been unable to find a workaround.

Revision history for this message
Atis (ubuntu-atis) wrote :

I also experienced "Failed to determine the codename for the release" after sw RAID setup using 8.10 Alternate CD.

I found out that this was because cdrom device changed at some point of RAID setup. My solution was:

* Open terminal (F2)
#mount
  lists /dev/scd0 on /cdrom
#umount /cdrom
#mount /dev/scd1 /cdrom

scd1 was only one found after entering /dev/scd[TAB].

* Return to menu and select "Rescan cdrom"

Suggestion would be to re-mount cdrom after RAID setup is done.

Revision history for this message
xteejx (xteejx) wrote :

Thank you for reporting this bug and helping to make Ubuntu better. However, Gutsy is no longer supported, therefore we are marking this bug Incomplete and ask that you try with a supported release and report back.

Atis: The original problem reported here does not show a RAID setup, therefore if you have not already done so, you will need to file this as another bug report.

Thank you.

Changed in debian-installer (Ubuntu):
status: New → Incomplete
Revision history for this message
xteejx (xteejx) wrote :

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 debian-installer (Ubuntu):
status: Incomplete → Invalid
Revision history for this message
mike cain (mnmcain) wrote :

using lucid lucy alternate cd, I get a failure to install the base system with above error report. Cd integrity good, and tried 2 cd's. i did save a log if more info is needed.

mike cain (mnmcain)
Changed in debian-installer (Ubuntu):
status: Invalid → New
Revision history for this message
mike cain (mnmcain) wrote :

Sorry was a bad hard drive. :(

Revision history for this message
mike cain (mnmcain) wrote :

sorry bad hardware not software.

Changed in debian-installer (Ubuntu):
status: New → Invalid
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.
Subscribing...

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.