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

Bug#593492: marked as done (debian-installer: Unable to install debian using RAID5, dm-crypt, LVM)



Your message dated Wed, 8 Sep 2010 00:04:32 +1000
with message-id <20100907140432.GA2284@debian.org>
and subject line Re: Bug#593492:
has caused the Debian Bug report #593492,
regarding debian-installer: Unable to install debian using RAID5, dm-crypt, LVM
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.)


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

I am unable to install lenny (5.0.5), i386 using RAID5, dm-crypt and LVM.

I got
/dev/sda (2TB)
/dev/sdb (2TB)
/dev/sdc (2TB)

and want to install the system unsing RAID5.

I use:
/dev/sda1 (256MB)
/dev/sdb1 (256MB)
/dev/sdc1 (256MB)

/dev/sda2 (about 4TB)
/dev/sdb2 (about 4TB)
/dev/sdc2 (about 4TB)

Configure Sofware-RAID
	New RAID1
		/dev/sda1, /dev/sdb1, /dev/sdc1

	New RAID5
		/dev/sda2, /dev/sdb2, /dev/sdc2

RAID5 #1
	physical Volume for encryption
	Erase data: No

Configure encrypted device
	Enter password 2 times

Encrypted device (md1_crypt)
	physical Volume for LVM

Configure Logical Volume Manager
	Add volume-group
		Name: volgroup
		Use md1_crypt

	Create logical volume
		root, 20GB
		swap, 2GB
		home, (remain)

LV home
	ext3
	/home

LV root
	ext3
	/

LV swap
	swap

RAID #0 (256 MB)
	ext3
	/boot


When I try to go on with the installation, I get the error
"The kernel was unable to re-read the partition table on /dev/md0 (Invalid argument).
This means Linux won't know anything about the modifications you made
until you reboot.  You should reboot your computer before doing
anything with /dev/md0."

The automatically provided system-information can be ignored.


-- System Information:
Debian Release: squeeze/sid
  APT prefers lucid-updates
  APT policy: (500, 'lucid-updates'), (500, 'lucid-security'), (500, 'lucid')
Architecture: amd64 (x86_64)

Kernel: Linux 2.6.32-24-generic (SMP w/8 CPU cores)
Locale: LANG=de_AT.utf8, LC_CTYPE=de_AT.utf8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash



--- End Message ---
--- Begin Message ---
On Tue, Sep 07, 2010 at 03:25:06PM +0200, Mathias Kub wrote:
> Please close the bug, one HDD was broken.

Closing this bug report accordingly.


--- End Message ---

Reply to: