Hi,
Nicolas Courtel wrote on 2009-04-30 11:11:46 +0200 [Re: setup-storage for raid5
+ lvm]:
# mdadm --zero-superblock /dev/sda2
# /lib/udev/vol_id -u /dev/sda2
6428a2d1-c30d-4916-ab6b-625117989651
[...]
Ok, good to know, thanks for testing this. I wonder whether we should do
something
# mdadm --zero-superblock /dev/sda2
# /lib/udev/vol_id -u /dev/sda2
6428a2d1-c30d-4916-ab6b-625117989651
#
I wonder how this mdadm data was still there, though...
Thanks for your help,
Ok, good to know, thanks for testing this. I wonder whether we should do
something about this in
[...]
The error message is the following (full log is at
http://paste.debian.net/34215/)
The uninitialized stuff warnings indicated some bugs that I need to look into,
but that doesn't seem to be the showstopper.
Executing: /lib/udev/vol_id -u /dev/sda2
Command /lib/udev/vol_id -u
Michael Tautschnig a écrit :
Executing: /lib/udev/vol_id -u /dev/sda2
Command /lib/udev/vol_id -u /dev/sda2 had exit code 4
Failed to obtain UUID for /dev/sda2
I originally wanted to have one swap slice on each disk, but in this
case the error is on the sdb swap partition:
Executing:
Michael Tautschnig a écrit :
[...]
So, mysteriously, that information is lost afterwards. Hmm, looking at the code
of vol_id it seems that parted might have overridden the volume id for
/dev/sda2 (instead of /dev/sda1 or /dev/sda3). Could you re-run that failing
installation and, once it
Michael Tautschnig a écrit :
[...]
So, mysteriously, that information is lost afterwards. Hmm, looking at the
code
of vol_id it seems that parted might have overridden the volume id for
/dev/sda2 (instead of /dev/sda1 or /dev/sda3). Could you re-run that
failing
installation and,
Hello,
With FAI 3.2.19, I'm trying to install on a host with 3 identical hard
disks a system on Raid5 + LVM. But installation keeps failing in
task_partition, and I can't figure out where my setup-storage config is
wrong:
disk_config sda
primary -512- -
