similar to: mdraid woes (missing superblock?)

Somewhere, mdadm is cacheing information. Here is my /etc/mdadm.conf file: more /etc/mdadm.conf # mdadm.conf written out by anaconda DEVICE partitions MAILADDR root ARRAY /dev/md0 level=raid1 num-devices=4 metadata=0.90 UUID=55ff58b2:0abb5bad:42911890:5950dfce ARRAY /dev/md1 level=raid1 num-devices=2 metadata=0.90 UUID=315eaf5c:776c85bd:5fa8189c:68a99382 ARRAY /dev/md2 level=raid1 num-devices=2

Hello, I have a RAID5 array on my CentOS 5.6 x86_64 workstation which "suddenly" failed to work (actually after the system could not resume from a suspend). I had recently issues after moving the workstation to another office, where one of the disks got accidently unplugged. But the RAID was working and it had reconstructed (as far as I can tell) the data. After I replugged the disk,

KVM virtualization is full of wonders. :-/ I would need to attach an USB disk to a vm, but how? The command "qemu" would provide a way: [root at a134-224 yum.repos.d]# man qemu-kvm > QEMU(1) > NAME > qemu-doc - QEMU Emulator User Documentation > > SYNOPSIS > usage: qemu [options] [disk_image] (...) > -usbdevice devname > Add the

I have 4 ST2000DL003-9VT166 (2Tbyte) disks in a RAID 5 array. Because of the size I built them as a GPT partitioned disk. They were originally built on a CentOS 5.x machine but more recently plugged into a CentOS 6.2 machine where they were detected just fine e.g. % parted /dev/sdj print Model: ATA ST2000DL003-9VT1 (scsi) Disk /dev/sdj: 2000GB Sector size (logical/physical): 512B/512B

Sorry, this is going to be a rather long post...Here's the situation; I have 4 IDE disks from an old snap server which fails to mount the raid array. We believe there is a controller error on the SNAP so we've put them in another box running CentOS 5 and can see the disks OK. hda thru hdd looks like this Disk /dev/hdd: 185.2 GB, 185283624960 bytes 255 heads, 63 sectors/track, 22526

I am sure this is really simple. I have a setup of 2 disks (sda, sdb) which are outwardly identical, and are mirrors of each other. Together they form 3 raid1 devices. Both disks can boot. Now sda has bad sectors, and I should replace it. But which one of the physical disks is sda?? The machine boots fine from either one of the disks, (and the booting disk of course is always called sda).

Guys, The other day while working on my old workstation it get frozen and after reboot I lost almost all data unexpectedly. I have a RAID1 configuration with LVM. 2 IDE HDDs. md0 .. store /boot (100MB) -------------------------- /dev/hda2 /dev/hdd1 md1 .. store / (26GB) /dev/hda3 /dev/hdd2 The only info that still rest in was that, that I restore after the fresh install. It seems that the

Hi I have a disk which two of the partitions are part of a RAID1 setup. I'm trying to rename the the second raided partition mdadm -E /dev/sdc4 /dev/sdc4: Magic : a92b4efc Version : 1.2 Feature Map : 0x1 Array UUID : 83d7657b:ebfddcb7:36b0fa14:d29a350c Name : oldname:2 Creation Time : Tue Aug 30 15:25:10 2016 Raid Level : raid1 Raid Devices : 2

Hi, I have 2 identical xSeries 346 with 2 identical IBM 72GB scsi drive. What i did is install the centos 4.2 serverCD on the first IBM and set the HDD to raid1 and raid0 for swap. Now what i did is get the 2nd HDD in the 1st Server swap it with the 1st HDD in the 2nd Server and rebuild the Raids. The 1st server rebuild the array fine. My problem is the Second server, after rebuilding it and

Guys, The other day while working on my old workstation it got frozen and after reboot I lost almost all data unexpectedly. I have a RAID1 configuration with LVM. 2 IDE HDDs. md0 .. store /boot (100MB) -------------------------- /dev/hda2 /dev/hdd1 md1 .. store / (26GB) -------------------------- /dev/hda3 /dev/hdd2 The only info that still rest in was that, that I restore after the fresh

OK, I have managed to get software RAID 1 running on my wonderful Proliant server but now have two challenges: 1) Fresh after an OS install and reboot, the RAID array starts to do its stuff but straight away (as part of the boot messages) I am told that the second disk is 'not ready for command' and the system hangs as soon as resyncing starts. I think this is fixed by adding an hdparm

Is it possible or will there be any problems with using mdraid on top of mdraid? specifically say mdraid 1/5 on top of mdraid multipath. e.g. 4 storage machines exporting iSCSI targets via two different physical network switches then use multipath to create md block devices then use mdraid on these md block devices The purpose being the storage array surviving a physical network switch

On 02/10/14 07:41, Thomas Schmitt wrote: > Hi, > > email at missionaccomplish.com wrote: >> We been trying to boot the image in vbox using efi emulation but it >> complains about kernel not supporting handover. > If it complains about a kernel then it should be past El Torito > or GPT. The job of xorriso is to point BIOS and EFI to their > boot images. Everything else

Can I combine VMWare ESXi (free version) virtualization and CentOS mdraid level 1? Any pointers how to do it? I never used VMWare before. - Jussi -- Jussi Hirvi * Green Spot Topeliuksenkatu 15 C * 00250 Helsinki * Finland Tel. +358 9 493 981 * Mobile +358 40 771 2098 (only sms) jussi.hirvi at greenspot.fi * http://www.greenspot.fi

Hi, I am trying to adapt my kickstart usb key to optionally auto-setup mdraid on two disks...? But I have one server that keeps attaching the usb key to sda instead of sdc... My kickstart creates the raid devices on sdb and sdc partitions; but then I expect it not to work once the key is unplugged and the disks fall back to sda and sdb... Can I just modify mdadm.conf at the end, just

On Sat, Feb 28, 2015 at 5:14 PM, Chris Murphy <lists at colorremedies.com> wrote: > "Drives, and hardware RAID cards are subject to firmware bugs, just as > we have software bugs in the kernel." makes no assessment of how > common such bugs are relative to each other. I don't want to underestimate the value of good hardware RAID with BBWC implementations when it comes

There are some errors on my root filesystem, so I need to fsck it. In order to do this while the filesystem is unmounted, I'm booting from the install disk. However, since the filesystem is on an mdraid device, I'm not sure of the right way to get it assembled so I can check it. If I do, mdadm --examine --scan, then I get this: ARRAY /dev/md/2 metadata=... (and others, but I'm

I am trying to use a kickstart to install CentOS 8.2 on a server with a pair of drives with Linux software RAID 1. The install completes, but the resulting system will not boot - I get "Booting from Hard drive C:" from the BIOS (Dell in legacy BIOS mode, not UEFI) and it stops. If I then start the installer in rescue mode and run grub2-install on the two drives, it boots okay. If I

On 11/15/20 3:32 AM, ?ukasz Posadowski wrote: > Do anyone can suggest what else I forgot to do? Use metadata version 1.2 instead of 0.9. You need for the filesystem to be not visible until after the RAID is assembled, and the easiest way to do that is to put the metadata at the beginning of the drive and the partition table inside the RAID volume. With metadata version 0.9, the partition

In article <20201115123245.db62b8248e1f248afe02844a at lukaszposadowski.pl>, Lukasz Posadowski <mail at lukaszposadowski.pl> wrote: > > Hello everyone. > > I'm trying to install CentOS 8 with root and swap partitions on > software raid. The plan is: > - create md0 raid level 1 with 2 hard drives: /dev/sda and /dev/sdb, > using Linux Rscue CD, > - install