search for: mdadm

From: Nikolay Ivanets <stenavin@gmail.com> Inspection code checks /etc/mdadm.conf to map MD device paths listed in mdadm.conf to MD device paths in the guestfs appliance. However on some operating systems (e.g. Ubuntu) mdadm.conf has alternative location: /etc/mdadm/mdadm.conf. This patch consider an alternative location of mdadm.conf as well. --- daemon/inspect_fs_unix_f...

Alessandro Baggi wrote: > Il 29/01/19 15:03, mark ha scritto: > >> I've no idea what happened, but the box I was working on last week has >> a *second* bad drive. Actually, I'm starting to wonder about that >> particulare hot-swap bay. >> >> Anyway, mdadm --detail shows /dev/sdb1 remove. I've added /dev/sdi1... >> but see both /dev/sdh1 and /dev/sdi1 as spare, and have yet to find a >> reliable way to make either one active. >> >> Actually, I would have expected the linux RAID to replace a failed one >> with a spare...

...5:03, mark ha scritto: >>> >>>> I've no idea what happened, but the box I was working on last week >>>> has a *second* bad drive. Actually, I'm starting to wonder about >>>> that particulare hot-swap bay. >>>> >>>> Anyway, mdadm --detail shows /dev/sdb1 remove. I've added >>>> /dev/sdi1... >>>> but see both /dev/sdh1 and /dev/sdi1 as spare, and have yet to find >>>> a reliable way to make either one active. >>>> >>>> Actually, I would have expected the linux R...

Hi, I lost my mdadm.conf (and /proc/mdadm shows nothing useful) and I'd like to mount the filesystem again. So I've booted using rescue but I was wondering if I can do a command like this safely (i.e without losing the data previously stored). mdadm -C /dev/md0 --level=raid0 --raid-devices=2 /dev/sda1 /dev/s...

...tter wrote: >> Hi, >> >> I want to replace my hard drives based SW RAID-1 with SSD's. >> >> What would be the recommended procedure? Can I just remove one drive, >> replace with SSD and rebuild, then repeat with the other drive? > > I suggest to "mdadm --fail" one drive, then "mdadm --remove" it. After > replacing the drive you can "mdadm --add" it. > > If you boot from the drives you also have to care for the boot loader. I > guess this depends on how exactly the system is configured. Thanks, that's wha...

...>>>>> I've no idea what happened, but the box I was working on last week >>>>>> has a *second* bad drive. Actually, I'm starting to wonder about >>>>>> that particulare hot-swap bay. >>>>>> >>>>>> Anyway, mdadm --detail shows /dev/sdb1 remove. I've added >>>>>> /dev/sdi1... >>>>>> but see both /dev/sdh1 and /dev/sdi1 as spare, and have yet to find >>>>>> a reliable way to make either one active. >>>>>> >>>>>> Act...

...idea what happened, but the box I was working on >>>>>>>> last week has a *second* bad drive. Actually, I'm starting >>>>>>>> to wonder about that particulare hot-swap bay. >>>>>>>> >>>>>>>> Anyway, mdadm --detail shows /dev/sdb1 remove. I've added >>>>>>>> /dev/sdi1... >>>>>>>> but see both /dev/sdh1 and /dev/sdi1 as spare, and have yet >>>>>>>> to find a reliable way to make either one active. >>>>>>>&...

md_create: mdadm: boot: mdadm: boot is not a block device. at /home/rjones/d/libguestfs/images/guest-aux/make-fedora-img.pl line 95. Looking into this, it appears the old version of mdadm shipped in Ubuntu (mdadm 2.6.7) doesn't support the notion of giving arbitrary names to devices. Thus you have to do: m...

...I was working >>>>>>>>>> on last week has a *second* bad drive. Actually, I'm >>>>>>>>>> starting to wonder about that particulare hot-swap bay. >>>>>>>>>> >>>>>>>>>> Anyway, mdadm --detail shows /dev/sdb1 remove. I've >>>>>>>>>> added /dev/sdi1... >>>>>>>>>> but see both /dev/sdh1 and /dev/sdi1 as spare, and have >>>>>>>>>> yet to find a reliable way to make either one active. >&...

Return a hash containing metadata about a specific Linux MD device, based on the output of 'mdadm -DY'. --- daemon/md.c | 78 ++++++++++++++++++++++++++++++++++++++++ generator/generator_actions.ml | 31 ++++++++++++++++ regressions/test-mdadm.sh | 60 ++++++++++++++++++++++++++++++- src/MAX_PROC_NR | 2 +- 4 files changed, 169 insertions(+),...

...: >> Il 29/01/19 15:03, mark ha scritto: >> >>> I've no idea what happened, but the box I was working on last week has >>> a *second* bad drive. Actually, I'm starting to wonder about that >>> particulare hot-swap bay. >>> >>> Anyway, mdadm --detail shows /dev/sdb1 remove. I've added /dev/sdi1... >>> but see both /dev/sdh1 and /dev/sdi1 as spare, and have yet to find a >>> reliable way to make either one active. >>> >>> Actually, I would have expected the linux RAID to replace a failed one >&...

This change renames the following 2 apis: * mdadm_create -> md_create * mdadm_detail -> md_detail This is more consistent with list_md_devices, and removes a reference to an implementation detail from the api. --- daemon/md.c | 24 ++++++++++++------------ generator/generator_actions.ml | 4 ++-- regress...

I just upgraded my home KVM server to CentOS 6.0 CR to make use of the latest libvirt and now my RAID array with my VM storage is missing. It seems that the upgrade to mdadm-3.2.2 is the culprit. This is the output from mdadm when scanning that array, # mdadm --detail --scan ARRAY /dev/md0 metadata=imsm UUID=734f79cf:22200a5a:73be2b52:3388006b ARRAY /dev/md126 metadata=imsm UUID=3d135942:f0fad0b0:33255f78:29c3f50a mdadm(IMSM): Unsupported attributes : 40000000 mdadm:...

I've no idea what happened, but the box I was working on last week has a *second* bad drive. Actually, I'm starting to wonder about that particulare hot-swap bay. Anyway, mdadm --detail shows /dev/sdb1 remove. I've added /dev/sdi1... but see both /dev/sdh1 and /dev/sdi1 as spare, and have yet to find a reliable way to make either one active. Actually, I would have expected the linux RAID to replace a failed one with a spare.... Clues for the poor? I *really* don'...

...gt;>>> >>>>> I've no idea what happened, but the box I was working on last week >>>>> has a *second* bad drive. Actually, I'm starting to wonder about >>>>> that particulare hot-swap bay. >>>>> >>>>> Anyway, mdadm --detail shows /dev/sdb1 remove. I've added >>>>> /dev/sdi1... >>>>> but see both /dev/sdh1 and /dev/sdi1 as spare, and have yet to find >>>>> a reliable way to make either one active. >>>>> >>>>> Actually, I would have...

Hi, what?s the proposed way of handling mdadm in Centos 7? I did not get any notification when a disk in a RAID1 failed, and now that the configuration has changed after resolving the problem, I might be supposed to somehow update /etc/mdadm.conf. Am I not supposed to be notified by default when something goes wrong with an array? How do I...

...; I want to replace my hard drives based SW RAID-1 with SSD's. >>>> >>>> What would be the recommended procedure? Can I just remove one drive, >>>> replace with SSD and rebuild, then repeat with the other drive? >>> >>> I suggest to "mdadm --fail" one drive, then "mdadm --remove" it. After >>> replacing the drive you can "mdadm --add" it. >>> >>> If you boot from the drives you also have to care for the boot loader. I >>> guess this depends on how exactly the system is con...

...want to move a device to another md array, we should stop the md device which contained this device first. Signed-off-by: Wanlong Gao <gaowanlong at cn.fujitsu.com> --- daemon/md.c | 16 ++++++++++++++++ generator/generator_actions.ml | 9 +++++++++ regressions/test-mdadm.sh | 14 ++++++++++++++ src/MAX_PROC_NR | 2 +- 4 files changed, 40 insertions(+), 1 deletions(-) diff --git a/daemon/md.c b/daemon/md.c index 82ddb82..9004a6f 100644 --- a/daemon/md.c +++ b/daemon/md.c @@ -310,3 +310,19 @@ error: return NULL; } + +int +do_mdadm_stop...

...itions on four separate disks (the third partition of each disk, 3 active, one spare) When booting, I get an error message similar to: raid5 failed: No md superblock detected on /dev/md0. and the LVM volume group does not come up. I then booted using the CentOS 5.6 LiveCD and tried to run a few mdadm command (see just below). It seems that there are some data still lying around, but I'm not very experienced with RAID and I thought that I would ask for advice before trying commands which may impact the data such as assemble, etc. Thanks in advance for any help! Mathieu [root at livecd ~]#...

...> I've no idea what happened, but the box I was working on last week >>>>>>> has a *second* bad drive. Actually, I'm starting to wonder about >>>>>>> that particulare hot-swap bay. >>>>>>> >>>>>>> Anyway, mdadm --detail shows /dev/sdb1 remove. I've added >>>>>>> /dev/sdi1... >>>>>>> but see both /dev/sdh1 and /dev/sdi1 as spare, and have yet to find >>>>>>> a reliable way to make either one active. >>>>>>> >>>...