Tag Info

New answers tagged

1

this is NOT raid, this is fakeraid, and you should never use it. Either get a proper raid controller, or disable the card, switch it to JBOD mode and use mdadm to create software raid.


0

You've got a rather scrambled-looking system there. The key elements from your mdadm --examine output: /dev/sdc1: Update Time : Sat Oct 11 09:20:36 2014 Events : 15084 Device Role : Active device 2 /dev/sdd1: Update Time : Wed Oct 15 08:09:37 2014 Events : 15196 Device Role : Active device 1 /dev/sde1: Update Time : ...


2

Yes, you need to stop the array before removing the disks. In general, the order of operations is this, where completing each step makes it possible to do the next step: Stop any programs using filesystems on the array. Unmount all filesystems on the array. Stop the array. Power down the array disks. If you're using LVM, there's a step 2.5 where you ...


0

I had a similar problem after upgrading my debian. During the reboot, this message appeared to me: Unable to find LVM Volume. /dev/mapper/debian-root does not exist. I found the solution here: cryptsetup luksOpen /dev/sda5 lvmsys lvm lvm> vgscan ## scan for volume groups lvm> vgchange -a y ## activates the volume groups And voilĂ , it ...


1

Answering only the second part (I noticed /dev/md/root in your question Raid devices are mounted with different UUID and mused on that but without an answer.) How is this relation (partition<->mount point) is set with raids in my situation md126 : active raid1 sdb2[1] sda2[0] 974711616 blocks super 1.0 [2/2] [UU] bitmap: 1/8 pages [4KB], ...



Top 50 recent answers are included