Source: partman-auto
Version: 162
Severity: normal
Tags: d-i
Hello,
It took me some time to realize why I was not able to install Debian
with software RAID1 system. The reason is that when I was running the
Guided partitioning on the whole software RAID disk, partman-auto would
create an EFI
On Wed, Aug 3, 2022 at 1:44 AM Chris Hofstaedtler wrote:
> * Holger Wansing [220802 23:37]:
> > I have merged the merge requests filed by Chris (partman-base, partman-auto,
> > hw-detect, grub-installer).
> >
> > The packages build fine with those changings.
> > And a locally built mini.iso with
8,6 @@
Please read the documentation in /usr/share/doc/dmraid BEFORE attempting
any use of this software. Improper use can cause data loss!
-Package: dmraid-udeb
-Architecture: linux-any
-Section: debian-installer
-Package-Type: udeb
-Depends: ${shlibs:Depends}, dmsetup-udeb
-Description:
Hi,
Cyril Brulebois wrote (Sun, 31 Jul 2022 14:31:20 +0200):
> > I was digging around in the d-i code, and it appears for dmraid to
> > be invoked, one has to boot with disk-detect/dmraid/enable.
> >
> > I have opened merge requests to remove the dmraid/sataraid code from
> > d-i. The changes l
-support?
> > Please note dmraid upstream is dead for more than ten years. I might
> > find an old i386 hardware that needs it.
> > But yes, it's only on life-support.
>
> [..]
>
> > > I'm wondering if we should remove dmraid support from the d-i as a
> &g
ten years. I might
> find an old i386 hardware that needs it.
> But yes, it's only on life-support.
[..]
> > I'm wondering if we should remove dmraid support from the d-i as a
> > first step. AFAICT Intel Software RAID is supported by mdraid, not
> > sure if the other
at least?
> I'm wondering if we should remove dmraid support from the d-i as a
> first step. AFAICT Intel Software RAID is supported by mdraid, not
> sure if the other RAID platforms are still sold.
Sounds like a good idea. This will show users early Debian doesn't
plan to shi
ter.
I'm wondering if we should remove dmraid support from the d-i as a
first step. AFAICT Intel Software RAID is supported by mdraid, not
sure if the other RAID platforms are still sold.
If its gone from di-i, at least no new installs can spring into
existence "by accident", i.e. wher
Your message dated Sat, 30 Oct 2021 18:30:54 +0200
with message-id <20211030183054.906cb9aac22395d0f32a6...@mailbox.org>
and subject line Mass-closing old grub-installer bugs
has caused the Debian Bug report #292513,
regarding grub and software raid
to be marked as done.
This means that you
Your message dated Sat, 30 Oct 2021 18:30:54 +0200
with message-id <20211030183054.906cb9aac22395d0f32a6...@mailbox.org>
and subject line Mass-closing old grub-installer bugs
has caused the Debian Bug report #292513,
regarding debian-installer: After grub software raid installation, machine
Your message dated Tue, 4 Aug 2020 00:09:01 +0200
with message-id <20200804000901.ada4d3e7ac8e2e0050ab3...@mailbox.org>
and subject line Mass-closing old installation-report bugs
has caused the Debian Bug report #718451,
regarding installation-reports: comments about GRUB on LVM over softwar
Package: installation-reports
Severity: normal
Tags: d-i
Dear Maintainer,
*** Please consider answering these questions, where appropriate ***
* What led up to the situation?
* What exactly did you do (or not do) that was effective (or
ineffective)?
* What was the outcome of this ac
fake raid controller.
The only reason to use it instead of mdadm software raid is if you
must dual boot with Windows. If you don't do that, then mdadm is much
better supported and feature complete.
For what it's worth, you can choose to install grub to the /dev/mapper
device and it works
Hi,
i've made a (very) slight modification to Raphael's patch so it can be applied
against current grub-installer code.
So here it goes for review.
--
Melhores cumprimentos/Best regards,
Miguel Figueiredo
http://www.DebianPT.org
diff --git a/grub-installer b/grub-installer
index fe33471..784
Il giorno lun, 17/01/2011 alle 17.28 -0500, Lennart Sorensen ha scritto:
> On Mon, Jan 17, 2011 at 10:51:14PM +0100, Giuseppe Sacco wrote:
[...]
> > Reading the documentation I found that grub2 does not support this kind
> > of raid controller, nor lilo does. So, it seems Debian cannot be
> > insta
p: [O]
> User/password setup:[O]
> Install tasks: [O]
> Install boot loader:[E]
> Overall install:[E]
>
> Comments/Problems:
>
> this machine have two sata disks connected to a intel software raid
> controller. The two disks have been connfigured a
etect hard drives: [O]
Partition hard drives: [O]
Install base system:[O]
Clock/timezone setup: [O]
User/password setup:[O]
Install tasks: [O]
Install boot loader:[E]
Overall install:[E]
Comments/Problems:
this machine have two sata disks connected to a intel sof
On October 29, 2010 07:56:03 am Mario Kleinsasser wrote:
> Hello,
>
> I would love to, but from my googling it sounds like preseeding software
>
> > raid
> > + LVM is a black art of some sorts. Lots of chatter on google, but not
> > much
> > solid info. If a
On Thu, Oct 28, 2010 at 09:21:29PM +, Ryan Braun [ADS] wrote:
> On October 28, 2010 09:02:02 pm Lennart Sorensen wrote:
> > On Thu, Oct 28, 2010 at 08:42:11PM +, Ryan Braun [ADS] wrote:
> > > Looking over the preseed docs for setting up software raid, it looks
>
Hello,
I would love to, but from my googling it sounds like preseeding software
> raid
> + LVM is a black art of some sorts. Lots of chatter on google, but not
> much
> solid info. If anyone has any examples of this, I'd love to see them.
>
> TBH, I don't think t
On October 28, 2010 09:02:02 pm Lennart Sorensen wrote:
> On Thu, Oct 28, 2010 at 08:42:11PM +, Ryan Braun [ADS] wrote:
> > Looking over the preseed docs for setting up software raid, it looks
> > like you need to create a separate raid device for each partition? I'm a
&g
On Thu, Oct 28, 2010 at 08:42:11PM +, Ryan Braun [ADS] wrote:
> Looking over the preseed docs for setting up software raid, it looks like
> you
> need to create a separate raid device for each partition? I'm a software
> raid newb, and I've only set it up a couple t
Looking over the preseed docs for setting up software raid, it looks like you
need to create a separate raid device for each partition? I'm a software
raid newb, and I've only set it up a couple times going through d-i
manually.
What I'm looking to do is create one raid de
Your message dated Wed, 08 Sep 2010 03:58:32 +
with message-id
and subject line Closing old installation report #499934
has caused the Debian Bug report #499934,
regarding software-raid, full encrypted system, lvm
to be marked as done.
This means that you claim that the problem has been
Your message dated Wed, 08 Sep 2010 03:58:13 +
with message-id
and subject line Closing old installation report #367245
has caused the Debian Bug report #367245,
regarding software raid cannot be used for anything
to be marked as done.
This means that you claim that the problem has been
Your message dated Wed, 08 Sep 2010 03:58:04 +
with message-id
and subject line Closing old installation report #330560
has caused the Debian Bug report #330560,
regarding Partitioning fails when setting up software RAID during Sarge install
to be marked as done.
This means that you claim
Your message dated Wed, 08 Sep 2010 03:57:48 +
with message-id
and subject line Closing old installation report #283011
has caused the Debian Bug report #283011,
regarding Sarge Installer does not install GRUB into MBR on Software RAID
to be marked as done.
This means that you claim that the
Your message dated Wed, 08 Sep 2010 03:57:39 +
with message-id
and subject line Closing old installation report #272702
has caused the Debian Bug report #272702,
regarding Install Report Software RAID - XFS Failed, JFS Succeeded
to be marked as done.
This means that you claim that the
tag 489006 patch
thanks
On Thu, 18 Jun 2009, Raphael Hertzog wrote:
> I would suggest to force install grub-pc when boot partition is on RAID
> and replace (hd0) by (md0) for installation in MBR. Maybe we need a
> supplementary check that ensures that (hd0) is part of (md0).
>
> I might try to com
Processing commands for cont...@bugs.debian.org:
> tag 489006 patch
Bug#489006: debian-installer: After grub software raid installation, machine
fails to boot with first drive removed or blanked.
There were no tags set.
Tags added: patch
> thanks
Stopping processing here.
Please contact
On Wed, 17 Jun 2009, Felix Zielcke wrote:
> Am Mittwoch, den 17.06.2009, 15:43 +0200 schrieb Raphael Hertzog:
> > On Thu, 04 Jun 2009, Felix Zielcke wrote:
> > > I think this shouldn't anymore happen with grub2.
> > > It supports the Linux Software RAID.
> &g
Am Mittwoch, den 17.06.2009, 15:43 +0200 schrieb Raphael Hertzog:
> On Thu, 04 Jun 2009, Felix Zielcke wrote:
> > I think this shouldn't anymore happen with grub2.
> > It supports the Linux Software RAID.
> > Could you please try it? (grub-pc package)
>
> How are
On Thu, 04 Jun 2009, Felix Zielcke wrote:
> I think this shouldn't anymore happen with grub2.
> It supports the Linux Software RAID.
> Could you please try it? (grub-pc package)
How are we supposed to try it?
grub-install /dev/md0 ?
In any case, grub-installer still needs some mo
I think this shouldn't anymore happen with grub2.
It supports the Linux Software RAID.
Could you please try it? (grub-pc package)
--
Felix Zielcke
--
To UNSUBSCRIBE, email to debian-boot-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
I'd like to install Lenny into existing LVM volume group built top of
Software RAID-1 physical volumes like this:
pvs:
PV VG Fmt Attr PSize PFree
/dev/md0 LVM_VG_2 lvm2 a- 50,13G 0
/dev/md1 LVM_VG_2 lvm2 a- 14,80G 80,00M
/proc/mdstat:
Personalities : [raid1
install lenny onto that device.
Is the d-i RC2 an appropriate tool for this? In particular,
http://www.debian.org/devel/debian-installer/errata says
Auto-assembly of RAID arrays in rescue mode can corrupt data
Rescue mode should be used with great care when software RAID
arrays were in
A thought: The patch from #303914 might have to be partially undone in
order to (re)admit partitionable md devices.
signature.asc
Description: This is a digitally signed message part.
I just ran into this after, over a period of two days, trying to figure
out why D-I / partman doesn't allow me to partition /dev/md0, and why it
would not even recognize a manual partitioning created via `cfdisk`.
I think it would be very useful if partman supported partitionable md
devices. I
also sprach Matthias Köhne <[EMAIL PROTECTED]> [2008.09.23.2051 +0200]:
> Is it necessary to resync the new raid _at_ the installation? It
> took more than 12 hours to check my software-raid.
>
> Sep 20 20:41:43 mdcfg: mdadm: array /dev/md2 started.
> Sep 21 08:54:00 kern
ernel "2.6.25" i didn't get these messages.
I uploaded about 2 TB of data on this machine and I don't get a soft-reset
during the upload. I discover this only at the boot.
## 3) raid resync
Is it necessary to resync the new raid _at_ the installation? It took more than
12
Processing commands for [EMAIL PROTECTED]:
> reassign 499285 partman-md
Bug#499285: debian-installer: A reinstall of a machine that used LVM over
software RAID had partitioning problems
Bug reassigned from package `debian-installer' to `partman-md'.
> retitle 499285 partma
reassign 499285 partman-md
retitle 499285 partman-md: should use partman locking mechanism
thanks
On Sun, Sep 21, 2008 at 06:36:30AM +1000, Russell Coker wrote:
> On Saturday 20 September 2008 09:35, Jérémy Bobbio <[EMAIL PROTECTED]> wrote:
> > > But having LVM enabled it was unable to cease all k
On Saturday 20 September 2008 09:35, Jérémy Bobbio <[EMAIL PROTECTED]> wrote:
> > But having LVM enabled it was unable to cease all kernel access to the
> > partitions for the purpose of getting the kernel to recognise the new
> > partitions I created (I decided I wanted a slightly different RAID
>
On Wed, Sep 17, 2008 at 11:08:31PM +1000, Russell Coker wrote:
> I have a machine that had been used in a Linux Software RAID-1
> configuration with LVM running on top of the RAID. The Debian Installer
> recognised the LVM devices which in most cases is a good thing.
>
> But hav
Package: debian-installer
Version: daily build 16th Sep
Severity: normal
I have a machine that had been used in a Linux Software RAID-1
configuration with LVM running on top of the RAID. The Debian Installer
recognised the LVM devices which in most cases is a good thing.
But having LVM enabled
On Sunday 14 September 2008, Sebestyen Szabolcs wrote:
> Everything went well, the system installed without problems but when
> booting the fresh installed system GRUB gives the following error
> "Error 25" and the boot process stops.
> I cannot figure it out what is the problem, i have searched th
Hi,but
I have installed Debian Etch using the software raid setup from the installer.
As a guide i have used the following link:
http://andreas.scherbaum.la/blog/archives/54-Install-Debian-Etch-on-a-Software-Raid-1-with-S-ATA-disks.html
but instead of SATA disks I have used two IDE disks
Your message dated Mon, 1 Sep 2008 05:03:25 -0400
with message-id <[EMAIL PROTECTED]>
and subject line Reinvestigating
has caused the Debian Bug report #496866,
regarding installation-report: SCSI Software RAID: Module not included in
initramfs
to be marked as done.
This means that you
Package: installation-reports
Version: 2.35
Severity: normal
-- Package-specific info:
Boot method: network
Image version: 20080827-19:16
Date:
Machine: Generic PII, LSI Symbios 3c875 SCSI HBA
Partitions:
FilesystemType 1K-blocks Used Available Use% Mounted on
/dev/mapper/celidon-
Your message dated Tue, 05 Aug 2008 17:17:02 +
with message-id <[EMAIL PROTECTED]>
and subject line Bug#393728: fixed in partman-md 42
has caused the Debian Bug report #393728,
regarding debian-installer: Encryption on top of software RAID broken in daily
build
to be marked as done.
Package: debian-installer
Version: 20070308etch2
Severity: normal
I preseeded an Etch installtion with:
d-i grub-installer/bootdev string (hd0) (hd1)
but it didn't do what I expected with respect to software RAID, and
failed drives.
The current behaviour seems to be:
boot from sda if
Your message dated Tue, 1 Jul 2008 15:07:14 +0200
with message-id <[EMAIL PROTECTED]>
and subject line Re: Bug#488809: installation-reports: lenny installer beta 3
doesn't propose software raid configuration
has caused the Debian Bug report #488809,
regarding installation-rep
e system:[O]
Clock/timezone setup: [O]
User/password setup:[O]
Install tasks: [O]
Install boot loader:[O]
Overall install:[O]
Comments/Problems:
The installer doesn't propose software raid configuration.
Only Full disk usage, LVM support, LVM encrypted and Manual
Your message dated Thu, 29 May 2008 23:51:54 +0200
with message-id <[EMAIL PROTECTED]>
and subject line Preseeding of software RAID setup available since 2006
has caused the Debian Bug report #305543,
regarding d-i should support preseeding of software RAID setup
to be marked as done.
This
Processing commands for [EMAIL PROTECTED]:
> reassign 305543 partman-auto-raid 1
Bug#305543: need preseed support
Bug reassigned from package `partman-md' to `partman-auto-raid'.
> retitle 305543 d-i should support preseeding of software RAID setup
Bug#305543: need preseed sup
On Sun, Feb 10, 2008 at 07:51:35PM +0100, Jérémy Bobbio wrote:
> Attached is a patch against partman-auto-raid/5 (released with Etch)
> that allows the preseeding of RAID + LVM setup.
*ahem* Here it is.
--
Jérémy Bobbio.''`.
[EMAIL PROTECTED]: :Ⓐ :
> >
> > Since it doesn't seem to be supported directly by the d-i preseeding
> > system at this time (ie you can choose anly between "regular", "lvm",
> > "raid" and "crypto" for partman-auto/method), what would be the best
> > op
e you can choose anly between "regular", "lvm",
> "raid" and "crypto" for partman-auto/method), what would be the best
> option for me?
>
> Should I create a shell script that setup my partitioning and software
> raid devices first (a kind of early_s
nted a way to mix partman-auto-raid and partman-auto-lvm.
I read carefully the partman developper documentation, but I'm not yet
too confident to add my own partman-auto-lvm-on-raid module :-(
Hence my question: do I have other alternatives than adding this module
to achieve automated part
Op 18-01-2008 om 16:39 schreef Brice Figureau:
> I'm trying to setup a preseeding installation for a LVM over 3 software
> RAID1 partitions, I mean something akin to:
>
> /dev/sda1 + /dev/sdb1 -> /dev/md0 ext3 /boot
> /dev/sda2 + /dev/sdb2 -> /dev/md1 swap
> /dev/sda5 + /dev/sdb5 -> lvm VG, furthe
; for partman-auto/method), what would be the best
option for me?
Should I create a shell script that setup my partitioning and software
raid devices first (a kind of early_script), which then let
partman-auto-lvm do its job, or is there any other possibilities?
Thanks,
--
Brice Figureau <[EMAI
system administrator
(administrator, Debian Bugs database)
--- Begin Message ---
Package: debian-installer
Version: 20060806
Severity: wishlist
Hi,
I've just tried to the etch beta3 image as rescue CD. Everything seems
to be working properly. I'm using a software raid, and it's properl
p
hda2, ~64MB, ext3, /boot
hda3, extended partition
hda5, ~2GB, software RAID
hdb looks identical except that hdb2 isn't mounted.
hda5 + hdb5 = md0, RAID 0, root filesystem.
I've read that it's now possible to boot from RAID, and I can try that later.
The installer was a pleasure t
"[EMAIL PROTECTED]" <[EMAIL PROTECTED]> writes:
> When I finally reached the Boot-loader installation the Grub
> installation failed.
> I tried to install it manually. But as I have disks 6 discs connected
> to boot the nv_sata (4disks) and the sata_sil (2 disks) and the order
> of those contoller
Package: installation-reports
Version: 2.23
Severity: important
*** Please type your report below this line ***
-- Package-specific info:
Boot method: CD
Image version:
http://cdimage.debian.org/cdimage/daily-builds/daily/arch-latest/amd64/iso-cd/debian-testing-amd64-netinstall.iso
Date: 2006-N
On Fri, November 10, 2006 15:53, Mike Paul said:
> On Fri, 2006-11-10 at 09:09 +0100, David Härdeman wrote:
>> On Fri, November 10, 2006 8:25, Miroslav Kure said:
>> > On Thu, Nov 09, 2006 at 10:47:25PM -0500, Mike Paul wrote:
>> >> Problem description:
>> >>
>> >> The partitioner treats the re
On Fri, 2006-11-10 at 09:09 +0100, David Härdeman wrote:
> On Fri, November 10, 2006 8:25, Miroslav Kure said:
> > On Thu, Nov 09, 2006 at 10:47:25PM -0500, Mike Paul wrote:
> >> Problem description:
> >>
> >> The partitioner treats the resulting encrypted volume like a raw hard
> >> drive -- i
On Fri, November 10, 2006 8:25, Miroslav Kure said:
> On Thu, Nov 09, 2006 at 10:47:25PM -0500, Mike Paul wrote:
>> Problem description:
>>
>> The partitioner treats the resulting encrypted volume like a raw hard
>> drive -- it wants to put a partition table on it, and there's no way
>> to us
On Thu, Nov 09, 2006 at 10:47:25PM -0500, Mike Paul wrote:
>
> Steps to reproduce:
>
> * Boot D-I and select manual partitioning.
> * Create and activate a software RAID array.
> * Choose "Use as: physical volume for encryption" for the array.
>
Package: debian-installer
Severity: normal
Steps to reproduce:
* Boot D-I and select manual partitioning.
* Create and activate a software RAID array.
* Choose "Use as: physical volume for encryption" for the array.
* Activate the encrypted volume.
Problem descripti
Package: debian-installer
Severity: important
debian installer lets one setup a raid fairly easily. however, it gives
no indication that one can't partition an array, but one has to
partition the base disks and create the arrays out of the partitions.
In fact, the installer will go ahead an pa
Package: debian-installer
Version: 20060806
Severity: wishlist
Hi,
I've just tried to the etch beta3 image as rescue CD. Everything seems
to be working properly. I'm using a software raid, and it's properly
detecting that.
At a certain point, it asks what I want to mount as my
Package: installation-reports
Boot method: Daily i386 netinst CD
Image version: downloaded 2006 June 11
Date: 2006 June 12
Machine: Asus P2L-B
Processor: Celeron 500MHz
Memory: 384MB
Partitions:
hda1, ~128MB, swap
hda2, ~64MB, ext3, /boot
hda3, extended partition
hda5, ~2GB, software RAID
hdb
; > testing?
>
> Because I think there is a problem with the drivers that might be
> fixed in a later kernel. There is what appears as massive file
> corruption soon after an normal testing install. (my hunch is the SATA
> II drivers or in forcedeth). It could be jfs or software ra
On Tuesday 16 May 2006 23:21, Karl Schmidt wrote:
> using the debian-testing-amd64-netinst.iso from may 13
>
> Wiped disk and tried this one again -
> Dropped down into shell just before the grub install and
> chroot /target
>
> added backports to sources.list
> apt-get update
> apt-get install lin
using the debian-testing-amd64-netinst.iso from may 13
Wiped disk and tried this one again -
Dropped down into shell just before the grub install and
chroot /target
added backports to sources.list
apt-get update
apt-get install linux-image-2.6.15-1-amd64-k8
complained about hotplug - and remo
Package: installation-reports
Boot method: business card
Image version: May 13 2006
http://cdimage.debian.org/cdimage/daily-builds/daily/arch-latest/i386/iso-cd/debian-testing-i386-businesscard.iso
Date: May 14 2006
Machine: qemu
Processor:
Memory:
Partitions: 3 qemu images hda hdb and hdd. each
eboot: [E]
Comments/Problems:
Went through the Software RAID (1) setup and set: hdc1&hde1 to md0,
hdc5&hde5 to md1 and hdc6&hde6 to md2. Installation went fine, but after
reboot I'm dropped to a shell:
[snip]
Begin: Mounting root file system... ...
Begin: Running /scri
Processing commands for [EMAIL PROTECTED]:
> reassign 358153 initramfs-tools
Bug#358153: testing (etch): cannot boot on software raid
Bug reassigned from package `installation-reports' to `initramfs-tools'.
> thanks
Stopping processing here.
Please contact me if you need assista
On Tue, Jan 11, 2005 at 10:37:38PM +0100, Bj?rn Nilsson wrote:
> Thank you for looking into this issue.
>
> What you describe is what I was trying to do. Did not quite understand
> the basic concepts of RAID I guess, but now I think I get it.
>
> What I did:
> I marked the newly created RAID0 vol
On Tuesday 11 January 2005 11:59, [EMAIL PROTECTED] wrote:
> > Use the --initrd option with the make-kpkg command.
>
> Thanks, I finally got time to try that, but it wasn't the whole fix.
> Even though I selected everything in the lvm/raid section when
> configuring the kernel, dpkg (really mkinit
at worked fine
> > (impressive stuff with the hw autodetection btw!)
> >
> > I have tried with rc2 and nightly build from 2005-01-05, same result
> >
> > I read some problems with lilo or grub when using software raid, but
> > that seems unrelated becouse this
> Use the --initrd option with the make-kpkg command.
Thanks, I finally got time to try that, but it wasn't the whole fix. Even
though I selected everything in the lvm/raid section when configuring the
kernel, dpkg (really mkinitrd) would fail to create the initrd.img when
installing the kernel
have tried with rc2 and nightly build from 2005-01-05, same result
>
> I read some problems with lilo or grub when using software raid, but
> that seems unrelated becouse this is well before any bootloader is
> installed.
>
If you want to do what you've described, you'll n
roblems with lilo or grub when using software raid, but
that seems unrelated becouse this is well before any bootloader is
installed.
Regards
/Björn
On Wednesday 05 January 2005 16:41, David Bruce wrote:
> I am fairly confident from reading today that what I need to do is to
> make or copy a initrd.img file and set up initrd for my new kernel -
> new territory for me that I may explore when I get home tonight. Any
> pertinent suggestions would
I recently installed Sarge using D-I in a lvm-on-raid setup,
and everything worked perfectly. The 2.4-based kernel works fine.
Out of pure geekish compulsion, I decided to "upgrade" to 2.6.9. I
compiled a new kernel (using make-kpkg) with all of the lvm and raid options
built in and insta
Jin Zhao wrote:
> Where are instructions for that in preseed install? I searched email
> lists and installer manual but all examples found so far use physical
> disk as partman examples. I also tried manually install and set up
> software raid, but the 'debconf-get-selec
Where are instructions for that in preseed install? I searched email
lists and installer manual but all examples found so far use physical
disk as partman examples. I also tried manually install and set up
software raid, but the 'debconf-get-selections --installer' output
contains n
77148160 blocks [2/2] [UU]
unused devices:
--
So i have tow Software RAID devices: /dev/md0 (first partition of
/dev/hde and first partition of /dev/hdg) and /dev/md1 (second partition
of /dev/hde and second partition of /dev/hdg). On md0 is
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On Monday 22 November 2004 11:12, KiNG HoMaH wrote:
> I installed Debian Sarge with this partitions:
>
> /dev/hda1 - /boot - ext2
> /dev/md0 - / - ReiserFS (Software RAID 0)
>
> When I configured Software RAID, Debian Installer s
Hi,
I'm an Spanish Debian User and I think that one thing in Debian
Installer is incorrect.
I installed Debian Sarge with this partitions:
/dev/hda1 - /boot - ext2
/dev/md0 - / - ReiserFS (Software RAID 0)
When I configured Software RAID, Debian Installer showed a Dialog box
telling th
On Wed, 17 Nov 2004 16:08:26 +0100 Alexander A. Vlasov wrote:
> Recently I installed sarge on a few machines (~5), and I used a software
> raid as a root device. Installation progress was successfull until
> bootloader has to be installed.
> When I tried a "next step -- install b
Processing commands for [EMAIL PROTECTED]:
> reassign 281724 lilo-installer
Bug#281724: problem with root on software raid
Bug reassigned from package `installation-reports' to `lilo-installer'.
> merge 281724 278885
Bug#278885: xfs raid support
Bug#281724: problem with root
reassign 281724 lilo-installer
merge 281724 278885
thanks
-- Forwarded Message --
Subject: Re: Bug#281724: problem with root on software raid
Date: Wednesday 17 November 2004 16:45
From: "Alexander A. Vlasov" <[EMAIL PROTECTED]>
To: Frans Pop <[EMAIL PROTECTE
On Wednesday 17 November 2004 15:28, Alexander A. Vlasov wrote:
> So only way to install was select "do not make /dev/md0 active", get an
> error (during this step, file /etc/lilo.conf on /target was created),
> log in on second console, chroot to /target, manually edit
> /etc/lilo.conf, appending
Package: installation-reports
Debian-installer-version: pre-rc2
uname -a: various
Date: November 2004
Method: from CD (sarge-i386-businesscard)
Machine: various
Processor: various x86
Memory: various, 128M .. 1G
Root Device: software raid
Root Size/partition table: root on /dev/md0, consisting
Hi: I am having a problem getting to 2.6 with boot and root on raid 1
(and the rest of the system on lvm2). I have tried making initrd's with
various options, etc etc. IT seems that my hardware is getting detected
during the boot, but then all of a sudden comes: "md: md1 stopping".
What's going
On Sat, Oct 23, 2004 at 07:00:47PM +0300, Fabian Fagerholm wrote:
> On Sat, 2004-10-09 at 21:16 +0300, Fabian Fagerholm wrote:
> > I tried the following (3 x HDD):
> >
> > In partman, set up the three disks to have identical partition tables:
> >
> > * A small primary partition with boot fl
On Sat, 2004-10-09 at 21:16 +0300, Fabian Fagerholm wrote:
> I tried the following (3 x HDD):
>
> In partman, set up the three disks to have identical partition tables:
>
> * A small primary partition with boot flag set.
> * A large logical partition.
> * A small logical partiti
1 - 100 of 162 matches
Mail list logo
