[Date Prev][Date Next] [Thread Prev][Thread Next] [Date Index] [Thread Index]

Bug#589923: marked as done (debian-installer: Rescue mode fails to determine codename for the release)



Your message dated Sun, 2 Mar 2014 04:46:37 +0100
with message-id <20140302034637.GA20596@mraw.org>
and subject line Re: Bug#589923: #589923 debian-installer: Rescue mode fails to determine codename for the release
has caused the Debian Bug report #589923,
regarding debian-installer: Rescue mode fails to determine codename for the release
to be marked as done.

This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.

(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact owner@bugs.debian.org
immediately.)


-- 
589923: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=589923
Debian Bug Tracking System
Contact owner@bugs.debian.org with problems
--- Begin Message ---
Package: debian-installer
Version: Lenny 5.0.5
Severity: normal

I am going booting into rescue mode from the Lenny minimal install business cd (point release 5.0.5).
After selecting to install grub from the menu the rescue mode takes me to the partitioner (this is normal).
In the partitioner I choose for automatic partitioning, use whole disk and seperate partitions for /home, /var etc.
The program continues normally until I get a red screen saying:
"[!!] Install the base system
Debootstrap Error
Failed to determine codename for the release.
"

In tty4 I see:
....
cat: can't open '/dev/md0/device': Not a directory
base-installer: error: exiting on error base-installer/no_codename

Full syslog is included with this bug report.

I think this happens because the kernel still thinks somehow it has to do something with the sw raid device that was there in the partition table before I started partitioning in rescue mode.
I have seen with other installations sometimes that the installer gets confused when there are raid devices from a previous installation attempt.

I have included fdisk -l with this bug report (generated after I got the error). 
Before partitioning both sda en sdb had the same partition table and there was a software raid md0 using sda2 and sdb2.

I filed this to debian-installer because I expect this to be not specific to rescue mode.



--- End Message ---
--- Begin Message ---
Miguel Figueiredo <elmig@debianpt.org> (2011-01-23):
> as lenny's installer is not supported anymore can you try latest debian
> installer release (squeeze rc2) rescue mode and report if you still
> experience the issue you reported?
> 
> http://cdimage.debian.org/cdimage/squeeze_di_rc2/

The submitter was pinged 3+ years ago, and we haven't heard back, so
closing this bug report.

Mraw,
KiBi.

Attachment: signature.asc
Description: Digital signature


--- End Message ---

Reply to: