Rescue mode doesn't execute shell against proper partition

Bug #1040297 reported by Nicholas Skaggs
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
debian-installer (Ubuntu)
Expired
Low
Unassigned

Bug Description

When using rescue mode on the 12.04.1 images on a disk which contrained 2 seperate installations of ubuntu (both 64-bit, with the 64-bit alt image), executing a shell against the proper root filesytems always executed a shell against the first root filesystem.

The disk contained several partitions. /dev/sda1 contained precise. /dev/sda5 contained quantal.

For example, executing a shell against /dev/sda1 gave me a precise chroot. Executing a shell against /dev/sda5 still gave me the chroot of /dev/sda1. Executing a root shell and chroot'ing against /target also always resulted in chrooting into precise (/dev/sda1), even when I selected /dev/sda5.

Tags: iso-testing
Revision history for this message
Ubuntu QA Website (ubuntuqa) wrote :

This bug has been reported on the Ubuntu ISO testing tracker.

A list of all reports related to this bug can be found here:
http://iso.qa.ubuntu.com/qatracker/reports/bugs/1040297

tags: added: iso-testing
Revision history for this message
Nicholas Skaggs (nskaggs) wrote :

I have tried to rec-reate this and I'm unable to do so using 32-bit new installations.. Considering incomplete until can recreate.

Changed in debian-installer (Ubuntu):
status: New → Incomplete
summary: - Rescue mode doesn't execute shell agsint proper partition
+ Rescue mode doesn't execute shell against proper partition
Changed in debian-installer (Ubuntu):
importance: Undecided → Low
Revision history for this message
Launchpad Janitor (janitor) wrote :

[Expired for debian-installer (Ubuntu) because there has been no activity for 60 days.]

Changed in debian-installer (Ubuntu):
status: Incomplete → Expired
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.