On Saturday 30 August 2008, Giuseppe Iuculano wrote:
> after partitioning:
>
> ~ # ls -la /dev/mapper
> drwxr-xr-x    2 root     root          140 Aug 30 13:17 .
> drwxr-xr-x   10 root     root         2820 Aug 30 13:17 ..
> crw-rw----    1 root     root      10,  60 Aug 30 13:11 control
> brw-------    1 root     root     254,   0 Aug 30 13:17 sil_aiahbgbgaaaj
> brw-------    1 root     root     254,   1 Aug 30 13:17 sil_aiahbgbgaaajp1
> brw-------    1 root     root     254,   2 Aug 30 13:17 sil_aiahbgbgaaajp2
> brw-------    1 root     root     254,   3 Aug 30 13:17 sil_aiahbgbgaaajp5

OK, so it is the partitioning step that is causing the problem.

I suspect now that libparted is most likely to be the cause of the problem,
especially as after a reboot existing partitions are by dmraid detected
as you would expect (without the "p").
But another possibility is that you are just not following the correct
procedure. Support for dmraid is far from perfect and things will *only*
work if you follow the documented procedure.

How did you do the partitioning? Did you *exactly* follow the instructions
that are given in the "Partitioning" section of the SataRAID wiki page [1]?

Did the partman screens look like the examples that are given there?
Screenshots before and after doing the "Write changes in SATA RAID
partitioning to disk" step would be nice too.

Please send the /var/log/partman (gzipped!) after you do the partitioning.

> I selected the first ext3 entry, below serial ata raid (mirror), I had an
> out of memory:

The out of memory should not happen, but selecting the "first" partition
is *wrong*. It is not conform the procedure on the wiki page!

> Installation terminated, in the next reboot grub started, but there is
> an issue. Installer set root (sil_aiahbgbgaaaj).
>
> Replacing with root (hd0,0) fixes it.

We can look at this later. Let's concentrate first on the partitioning
problem.

Cheers,
FJP

[1] http://wiki.debian.org/DebianInstaller/SataRaid



-- 
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]

Reply via email to