[Lunar-bugs] [Lunar Linux 0000067]: unable to create software-RAID with 1.6.0

[Lunar bug reports list]

A NOTE has been added to this issue.
======================================================================
<http://bugs.lunar-linux.org/view.php?id=67> 
======================================================================
Reported By:                remsys
Assigned To:                sofar
======================================================================
Project:                    Lunar Linux
Issue ID:                   67
Category:                   ISO
Reproducibility:            always
Severity:                   minor
Priority:                   normal
Status:                     assigned
Moonbase Version:           20060131
Core Tools:                 Lunar
Core Tools Version:         20060129
======================================================================
Date Submitted:             02-22-2006 11:35 UTC
Last Modified:              02-23-2006 15:36 UTC
======================================================================
Summary:                    unable to create software-RAID with 1.6.0
Description: 
I can't get my machines to setup a software-RAID, not through the
installer, nor from the command line in a temporary shell.

Here's what goes wrong:

INSTALLER
=========
Partitioning:
-------------
The first thing that strikes me as odd is that I can's see /dev/hdc if I
try to partition my disks, although it's definitely there. So I have to
exit to a tempshell to partition /dev/hdc.

In regard to a software-RAID it would be nice/useful to have the
possibility to copy the partition-scheme of one drive to another.

Setup RAID:
-----------
First of all I'd like the installed to warn me if I'm not using FS-type fd
on the disks I'm trying to turn into an array.

Secondly the installer is unable to create and start a raid-device (i.e.
/dev/md0) if it already contains a superblock. it should use
--really-force or at least ask you if you'd like to do so.

If I try to start any other array than /dev/md0 (i.e. /dev/md1 having
members /dev/hda2 and /dev/hdc2, which have both been setup correctly) the
installer simply restarts all over again!

trying to setup&start all other arrays from the commandline in a
tempshell, as I have done many times before with the 2.4-based kernels,
doesn't work either, simply because there aren't any other /dev/md devices
than /dev/md0 -> /dev/md/0 (???????????). I haven't got a clue how to get
those, so I'll roll back to the 1.5.2 iso......
======================================================================

----------------------------------------------------------------------
 sofar - 02-23-06 15:31 
----------------------------------------------------------------------
> The first thing that strikes me as odd is that I can's see /dev/hdc if I
try to
> partition my disks, although it's definitely there. So I have to exit to
a
> tempshell to partition /dev/hdc.

this was fixed in SVN already as reported on the ML.

----------------------------------------------------------------------
 sofar - 02-23-06 15:32 
----------------------------------------------------------------------
> First of all I'd like the installed to warn me if I'm not using FS-type
fd on
> the disks I'm trying to turn into an array.

I'll consider this but it's not trivial to implement

----------------------------------------------------------------------
 sofar - 02-23-06 15:34 
----------------------------------------------------------------------
> If I try to start any other array than /dev/md0 (i.e. /dev/md1 having
members
> /dev/hda2 and /dev/hdc2, which have both been setup correctly) the
installer
> simply restarts all over again!

> trying to setup&start all other arrays from the commandline in a
tempshell, as
> I have done many times before with the 2.4-based kernels, doesn't work
either,
> simply because there aren't any other /dev/md devices than /dev/md0 ->
> /dev/md/0 (???????????). I haven't got a clue how to get those, so I'll
roll
> back to the 1.5.2 iso......

I can't reproduce this - the installer currently creates the /dev/md*
device nodes manually - I'll re-visit the code for testing for the next
release anyway, so this will get tested (again)

----------------------------------------------------------------------
 sofar - 02-23-06 15:36 
----------------------------------------------------------------------
> the installer is unable to create and start a raid-device (i.e. /dev/md0)
if it
> already contains a superblock. it should use --really-force or at least
ask you
> if you'd like to do so.

I don't agree with this - I'm not going to help people destroy their data
;^)

Issue History
Date Modified  Username       Field                    Change              
======================================================================
02-22-06 11:35 remsys         New Issue                                    
02-22-06 11:35 remsys         Moonbase Version          => 20060131        
02-22-06 11:35 remsys         Core Tools                => Lunar           
02-22-06 11:35 remsys         Core Tools Version        => 20060129        
02-23-06 15:31 sofar          Note Added: 0000118                          
02-23-06 15:31 sofar          Severity                 block => minor      
02-23-06 15:32 sofar          Note Added: 0000119                          
02-23-06 15:34 sofar          Note Added: 0000120                          
02-23-06 15:36 sofar          Note Added: 0000121                          
======================================================================