setup-storage for raid5 + lvm

[Michael Tautschnig]

> 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 aborts, do
>>>>
>>>> parted -s /dev/sda print
>>>>
>>>>         
>>> This looks ok:
>>>
>>> # parted -s /dev/sda print
>>> [...]
>>> Number  Start   End     Size    Type     File system  Flags
>>> 1      32.3kB  535MB   535MB   primary  ext2         raid
>>> 2      535MB   1604MB  1069MB  primary  linux-swap       3      
>>> 1604MB  320GB   318GB   primary               raid
>>>
>>>
>>> No raid on sda2, but vol_id disagrees:
>>>
>>> # /lib/udev/vol_id --export /dev/sda2
>>> ID_FS_USAGE=raid
>>> ID_FS_TYPE=linux_raid_member
>>> [...]
>>>
>>>     
>>
>> Did /dev/sda2 ever belong to a RAID array? Could you please try
>> - parted -s /dev/sda set 2 raid off
>> - run vol_id
>> - mkswap /dev/sda2
>> - run vol_id
>>   
>
> Nothing interesting happens... The disk has been in a raid 1 array a  
> while ago, but the partitioning was different, and has been cleaned up  
> by the new installation.
>

Ok, maybe mdadm helps, but I don't know for sure how to apply it:

- Does mdadm --zero-superblock /dev/sda2 work? If not, you might need to run
  mdadm --zero-superblock /dev/sda.
- Does running vol_id work afterwards?

Thanks,
Michael

-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: application/pgp-signature
Size: 194 bytes
Desc: not available
Url : http://lists.uni-koeln.de/pipermail/linux-fai/attachments/20090428/3e72340e/attachment.bin