Tag Info

New answers tagged

1

Not sure where to start here. Gnome is a GUI user environment, not an OS. try lsb_release -a to see what version of Linux you're running. /dev/sda is the raid set and does not correspond to either physical disk. You do not have a master/slave relationship in raid 1 so saying "mirrored drive" and "normal drive" are meaningless. You can check what kind of ...


0

I rescued the bootloader using the following commands: Booted from linuxmint disc ISO Installed mdadm Added raids: mdadm -A -R /dev/md0 /dev/sdb1 mdadm -A -R /dev/md1 /dev/sdb2 I have separate boot partition on sdb1|md0 Unlock the encrypted partition (sdb1|md0 is not encrypted) cryptsetup -v luksOpen /dev/md1 rescuedata Mounted the volume groups ...


0

If you remove a disk from your RAID, but the RAID still works because the missing disk was covered by redundancy, and then you add a replacement disk, then that added disk will be overwritten. There is no data loss in that the data you see on the /dev/mdX device does not change. However if you had important data on that added disk, it is lost due to ...


2

The issue that /dev/md0 doesn't have a partition table is not relevent to your problem. You plainly stated that you created the filesystem on the raw device I have created an ext4 filesystem on it as a single partition using the whole array so it makes sense that you have no partition table, as you did not partition the space. Its not an issue, but ...


3

I've never tried with these specific RAID technologies but it's been my experience that it's best to operate at the filesystem level when attempting to migrate data from one physical implementation of RAID to another. What do I mean by this? I mean that I would get another set of disks and move my content from the 1st RAID to a intermediate location (some ...



Top 50 recent answers are included