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

Bug#635854: marked as done ([rescue] Wheezy Rescue mode won't chroot to ext4)

Your message dated Mon, 3 Mar 2014 23:04:09 +0100
with message-id <20140303220409.GA30243@mraw.org>
and subject line Re: Bug#635854: [rescue] Wheezy Rescue mode won't chroot to ext4
has caused the Debian Bug report #635854,
regarding [rescue] Wheezy Rescue mode won't chroot to ext4
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.)


-- 
635854: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=635854
Debian Bug Tracking System
Contact owner@bugs.debian.org with problems
--- Begin Message --- 
Package: rescue
Version: Wheezy Installer
Severity: normal

--- Please enter the report below this line. ---
Running the Debian Wheezy Installer in Rescue mode and attempting the option 
to mount a hard disk partition (some kind of chroot) to an ext4 partition 
fails. Rescue mode appears unable to mount a ext4 partition using the ncurses 
interface.

--- System information. ---
Architecture: i386
Kernel:       Linux 2.6.39-2-686-pae

Debian Release: wheezy/sid
  500 testing         www.debian-multimedia.org 
  500 testing         security.debian.org 
  500 testing         ftp.us.debian.org 

--- Package information. ---
Package's Depends field is empty.

Package's Recommends field is empty.

Package's Suggests field is empty.

--- End Message ---
--- Begin Message --- 
Miguel Figueiredo <elmig@debianpt.org> (2011-07-30):
> i've just tried the businesscard images for amd64 and i386 under Virtualbox.
> amd64 works as expected, the console appears with the mounted filesystem. 
> i386 doesn't throw a shell to the mounted partition as expected, but the 
> filesystem is mounted in /target.
> 
> In both logs appears the following messages:
> 
> Jul 30 21:39:51 rescue-mode: selected root device '/dev/sda1'
> Jul 30 21:39:51 rescue: umount: can't umount /target: Invalid argument
> Jul 30 21:39:51 kernel: [   44.183793] EXT2-fs (sda1): error: couldn't mount 
> because of unsupported optional features (244)
> Jul 30 21:39:51 kernel: [   44.184494] EXT3-fs (sda1): error: couldn't mount 
> because of unsupported optional features (240)
> Jul 30 21:39:51 kernel: [   44.219889] EXT4-fs (sda1): recovery complete
> Jul 30 21:39:51 kernel: [   44.220081] EXT4-fs (sda1): mounted filesystem with 
> ordered data mode. Opts: (null)

I don't think this is an issue with the released wheezy images. I think I even
demonstrated recovering from a broken encrypted LVM installation using ext4,
during Mini-Debconf Paris 2012. So closing this bug report for the time being.

Mraw,
KiBi.

Attachment: signature.asc
Description: Digital signature


--- End Message ---
Reply to: