similar to: fsck mdraid root partition

- Ahh OK now I see why I was confused. The originally posted partition map uses cylinders as units, not LBA. I missed that. Cylinder 1 is the same as LBA 63. And that is sufficiently large for a GRUB legacy stage 2. - OK this is screwy. Partitions 1 and 3 on both drives have the same number of sectors, but partitions 2 differ: /dev/hde2 401,625 975,691,709 975,290,085 fd Linux

Something seems to be wrong with my file systems, and I want to fsck everything. But I cannot. The setup consists of 2 hds, carrying 3 raid1 (ext3) file systems (boot, /, swap). OS is up-to-date CentOS 5. So I boot from CentOS 5.3 dvd in rescue mode, do not mount the file systems, and try to run fsck -y /dev/md0 fsck -y /dev/md1 fsck -y /dev/md2 For each try I get an error message:

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 8/5/2015 12:34 PM, Chris Murphy wrote: > On Wed, Aug 5, 2015 at 9:12 AM, Bowie Bailey <Bowie_Bailey at buc.com> wrote: >> I am trying to upgrade my system from 500GB drives to 1TB. > I'm going to guess that there are no IDE drives that have 4096 byte > physical sectors, but it's worth confirming you don't have such a > drive because the current partition

I am trying to upgrade my system from 500GB drives to 1TB. I was able to partition and sync the raid devices, but I cannot get the new drive to boot. This is an old system with only IDE ports. There is an added Highpoint raid card which is used only for the two extra IDE ports. I have upgraded it with a 1TB SATA drive and an IDE-SATA adapter. I did not have any problems with the system

Hey, I installed 2 new data servers with a big (12TB) RAID6 mdraid. I formated the whole arrays with bad blocks checks. One server is moderately used (nfs on one md), while the other not. One week later, after the raid-check from cron, I get on both servers a few block_mismatch... 1976162368 on the used one and a tiny bit less on the other...? That seems a tiny little bit high... I do the

Hi list, I'm new with UEFI and GPT. For several years I've used MBR partition table. I've installed my system on software raid1 (mdadm) using md0(sda1,sdb1) for swap, md1(sda2, sdb2) for /, md2 (sda3,sdb3) for /home. From several how-to concerning raid1 installation, I must put each partition on a different md devices. I've asked times ago if it's more correct create the

Hi. CENTOS 7.6.1810, fresh install - use this as a base to create/upgrade new/old machines. I was trying to setup two disks as a RAID1 array, using these lines mdadm --create --verbose /dev/md0 --level=0 --raid-devices=2 /dev/sdb1 /dev/sdc1 mdadm --create --verbose /dev/md1 --level=0 --raid-devices=2 /dev/sdb2 /dev/sdc2 mdadm --create --verbose /dev/md2 --level=0 --raid-devices=2

Hello, i have a little problem. Our server has an broken RAID. # cat /proc/mdstat Personalities : [raid1] md0 : active raid1 sda1[2](F) sdb1[1] 2096064 blocks [2/1] [_U] md2 : active raid1 sda3[2](F) sdb3[1] 1462516672 blocks [2/1] [_U] md1 : active raid1 sda2[0] sdb2[1] 524224 blocks [2/2] [UU] unused devices: <none> I have remove the partition: # mdadm --remove

I'm using Centos 4.5 right now, and I had a RAID 5 array stop because two drives became unavailable. After adjusting the cables on several occasions and shutting down and restarting, I was able to see the drives again. This is when I snatched defeat from the jaws of victory. Please, someone with vast knowledge of how RAID 5 with mdadm works, tell me if I have any chance at all

Hi All Currently i'm setting up a 5.4 server and try to create a 3rd raid device, when i run: $mdadm --create /dev/md2 -v --raid-devices=15 --chunk=32 --level=raid6 /dev/sdc /dev/sdd /dev/sde /dev/sdf /dev/sdg /dev/sdh /dev/sdi /dev/sdj /dev/sdk /dev/sdl /dev/sdm /dev/sdn /dev/sdo /dev/sdp /dev/sdq the device file "md2" is created and the raid is being configured. but somehow

I have a machine on CentOS 5 with two disks in RAID1 using Linux software RAID. /dev/md0 is a small boot partition, /dev/md1 spans the rest of the disk(s). /dev/md1 is managed by LVM and holds the system partition and several other partitions. I had to take out disk sda from the RAID and low level format it with the tool provided by Samsung. Now I put it back and want to reassemble the array.

Hi , currently i have 2 raid devices /dev/md0 and /dev/md1 , i have added 2 new disks, fdisked , created 2 primary partitions with type fd (linux raid autodetect) Now i want to create raid from them root at vmhost1 ~]# mdadm --create --verbose /dev/md2 --level=1 /dev/sdc1 /dev/sdd1 mdadm: error opening /dev/md2: No such file or directory will return that error, what shouldi do? Thanks!

So I'm trying to RAID-1 this system which has two identical disks installed in it, and it isn't working for some reason. I started by doing a CentOS-4 install on /dev/sda1 as root, and with /dev/sda2 as my swap. I finish the install, yum update, and then I want to make the mirrors. I copy the partition table from one disk to the other: # sfdisk -d /dev/sda | sfdisk /dev/sdb I create

I have a raid1 array which is somehow faulty. There is 1,5 TB of stuff, I would not want to lose it (though I have full backup). The array cannot be mounted on startup (error message was "missing superblock"). I had to boot from DVD with linux rescue and remove the array from fstab. Here is some info - I am a little dumbfounded. [root at a134-224 log]# cat /proc/mdstat (...) md5 :

Hi I have a degraded array /dev/md2 ===================================================================== $ mdadm -D /dev/md2 /dev/md2: Version : 00.90.01 Creation Time : Thu Oct 6 20:31:57 2005 Raid Level : raid5 Array Size : 221953536 (211.67 GiB 227.28 GB) Device Size : 110976768 (105.84 GiB 113.64 GB) Raid Devices : 3 Total Devices : 2 Preferred Minor : 2

I am running software RAID1 on a somewhat critical server. Today I noticed one drive is giving errors. Good thing I had RAID. I planned on upgrading this server in next month or so. Just wandering if there was an easy way to fix this to avoid rushing the upgrade? Having a single drive is slowing down reads as well, I think. Thanks. Feb 7 15:28:28 server smartd[2980]: Device: /dev/sdb

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

Dear fellow CentOS users, I have never experienced this problem with hard disk management before and cannot explain it to myself on any rational basis. The setup: I have a workstation for testing, running latest CentOS 7.3 AMD64. I am evaluating oVirt and a storage-ha as part of my bachelors thesis. I have already been running a RAID1 (mdraid, lvm2) for the system and some oVirt 4.1 testing.

I have a Centos 7 system with an mdraid array (raid 1).? I removed a drive from it a couple of months ago and replaced it with a new drive.? Now I want to recover some information from that old drive. I know how to mount the drive, and have done so on another system to confirm that the information I want is there. My question is this: What is going to happen when I try to mount a drive that