Tag Info

New answers tagged

0

If a device is missing from an mdadm RAID5, I "create" the RAID device again with the old settings and missing as the missing device, e.g. in your situation it should be: mdadm --create --level=5 --layout=ls --chunk=512 --raid-devices=3 /dev/md0 missing /dev/sdd1 /dev/sdc1 Note: I'm assuming the "Device role" is 0-based, I'm used to a somewhat older mdadm ...


0

So I don't know if it can help someone but I could find a way to make the installation worked ! To explain it briefly, you need to create your partition by using mdadm and gdisk. In my situation, both were not installed on my live USB key. One this is done, I create 2 newt gpt partition table on both disk (sda and sdb). Then I start to create partition on ...


0

If I understand you right, you want to make one virtual HDD out for more HDD's of different size. Then it is a JBOD, not a RAID-0! So you can not use the stripe set settings, like you would with two disks of the same size. Say, gstripe. Instead you use a concatenated disk driver. Available under http://en.wikipedia.org/wiki/Vinum_volume_manager in Freebsd. ...


0

The cause was an erroneous spares=1 option in the mdadm.conf: # definitions of existing MD arrays ARRAY /dev/md0 UUID=621d5f15:cce75825:60273c48:78a7dac7 spares=1 I'm not sure how this ended up there, but I suppose it happened when a device failed and was replaced. Removing the spares=1 option or just recreating the mdadm.conf from scratch fixes the ...


0

I figured it out myself! I discovered mhddfs and it seems to do exactly what I want. I'm about to test with a VirtualBox, but I believe I will be using SnapRAID with mhddfs (probably all running on Lubuntu) and it solves my problem.


0

There is a high risk of data loss but it should work if you have enough free space to work around segments of data first. First format a empty drive, add it to a new LVM array, and then move over the data from disk two to the new lvm aray of one disk. Format and add the second disk, then move data from disk 3 to the LVM array (that now is disks 1 and 2). ...


0

This also worked for me. vgchange -a y -name of volume group- Following a kernel patch my RHEL system failed to reboot. Complaining of a missing /dev/mapper/VG-lv file. Booted to single-user and commented out of /etc/fstab. Once online I found my encrypted disk was showing as "unkown device" using pvs. Fixed this but still no device files for the ...



Top 50 recent answers are included