I have never preformed a rebuild of an RAID array. I am collecting resources, which details how to build an RAID 5 array when one drive has failed. Does the BIOS on the RAID controller card start to rebuild the data on the new drive once it is installed?
So I have a system that is about 6 years old running Redhat 7.2 that is supporting a very old app that cannot be replaced at the moment. The jbod has 7 Raid1 arrays in it, 6 of which are for database storage and another for the OS storage. We've recently run into some bad slowdowns and drive failures causing nearly a week in downtime. Apparently none of the people involved, including the so-called hardware experts could really shed any light on the matter. Out of curiosity I ran iostat one day for a while and saw numbers similar to below:
[Code]...
Some of these kinda weird me out, especially the disk utilization and the corresponding low data transfer. I'm not a disk IO expert so if there are any gurus out there willing to help explain what it is I'm seeing here. As a side note, the system is back up and running it just runs sluggish and neither the database folks nor the hardware guys can make heads or tails of it. Ive sent them the same graphs from iostat but so far no response.
i want to remove the raid 1 arrays on our server centos and use standalone drive
View 3 Replies View RelatedI've got 2 hard disk drives of 250GB, with this partitions :
All partitions are with format "linux raid software". I made 3 raid1 with them like that :
I want to clone them to news hdd of 500Gb, to have this partitions :
My problem, how can I resize partitions, before resize the array md2 with the command mdadm --grow /dev/md1 --size=max ?
After, how can I rebuild /dev/md2 without lost any datas ?
I'm using ubuntu-server 10.04 64bits.
I am trying to create a RAID data drive for my system but I am having setting it up since I am a total linux noob.
The system has 3 physical HDD-s:
1. 320 GB (has functional Ubuntu 9.10 installation) attached to a PCI SATA card
2. 2TB on motherboard
3. 2TB on PCI SATA card
I want to create a software RAID1 of disks 2 and 3. So far I have used the Palimpsest Disk Utility:
- Created a GUID Partition table on both disks (2, 3)
- Used File -> New -> Software Array, made sure both my drives were included
- Once Palimpsest listed the RAID Drive as a Software RAID Array, I told it to create Ext3 filesystem on it
Well.. at least thats what I thought I did. At this point I have been able to mount the RAID drive and put files on it. However when I look at its information in Palimpsest, I am told that the drive is not partitioned. Both RAId components /dev/sda1 and /dev/sdc1 are reported to be in Sync, but the RAID Drive's own state is 'Running, Resyncing @ 45%' (and lowly growing).
My questions are: Is this a normal setup or did I do something incorrectly? Why is the drive reporting to have no partition? And howcome I can use it if it does not have a partition? I have found the command line based configurations to be a tad too confusing to follow, so I have tried to stick to graphical tools - is this a hopeless cause in Ubuntu or is it possible to achieve what I want to do without command line? I will list some info on my disks below - perhaps this offers more insight to those of you more familiar with Linux.
Code:
mindgamer@mind-server:~$ sudo lshw -C disk
[sudo] password for mindgamer:
*-disk:0
description: ATA Disk
product: WDC WD3200BEVT-0
vendor: Western Digital
[Code]...
I currently have a 1.5TB sata drive connected to my system, with data already on it. In the next few days I am planning to use mdadm to create a raid5 array with another 2 1.5TB drives along with the one I already have. Is it possible to create the raid without losing the data on my current hard drive? Obviously it will be backed up before hand just in case, but it would be nice not to have to restore nearly a TB of data after raid'ing the drives.
View 2 Replies View RelatedI had to recently reinstall ubuntu because 10.04 started acting up on me. I reinstalled 9.04 but I don't know how to mount my RAID drive without messing with the data that's already on there. I have the UUID for the RAID but fstab isn't able to find it. I also previously used RAID software but I don't remember which one I used. how to mount my drive so that ubuntu can see it?
View 5 Replies View RelatedI was using a Buffalo LinkStation Duo to store pictures and the OS in the unit failed. As far as I know, the data on the two 1 TB drives is fine, and since Buffalo uses a Linux kernel in their LinkStation and the format is xfs, it should be possible to get the data off if I can mount one of the drives on a Linux box. I've put one of the drives into an external USB enclosure and attached it to my Linux system, but I cannot get the drive to mount, probably because it is one element of a Raid 1 array.
Most of what I can find on the Web concerns setting up a new Raid array, not creating an array around a drive that already contains data. I have installed mdadm, and I'm running Mint Linux release 9 (Isadora) on an Intel box. When I run mdadm -D /dev/sdb or sdb6, the device and the partition where the data is located, it reports that the device does not appear to be an md device. I'm not sure what that means. Any help would be greatly appreciated, as I've got around 13,000 photos on these disks that have no backup (I figured what could go wrong with mirrored copies?).
I'm trying to setup a RAID 5 array of 3x2TB drives and noticed that, besides having a faulty drive listed, I keep getting what looks like two separate arrays defined. I've setup the array using the following :
sudo mdadm --create /dev/md01 --verbose --chunk=64 --level=5 --raid-devices=3 /dev/sdb /dev/sdc /dev/sde
So I've defined it as md01, or so I think. However, looking in the Disk Utility the array is listed as md1 (degraded) instead. Sure enough I get :cat /proc/mdstat
Personalities : [linear] [multipath] [raid0] [raid1] [raid6] [raid5] [raid4] [raid10]
md1 : active raid5 sde[3](F) sdc[1] sdb[0]
3907028992 blocks level 5, 64k chunk, algorithm 2 [3/2] [UU_]
So I tried getting info from mdadm on both md01 and md1 :user@al9000:~$ sudo mdadm --detail /dev/md1
/dev/md1:
Version : 00.90
Creation Time : Sun Jan 9 10:51:21 2011
Raid Level : raid5 ......
Is this normal? I've tried using mdadm to --stop then --remove both arrays and then start from scratch but I end up in the same place. I'm just getting my feet wet with this so perhaps I'm missing some fundamentals here. I think the drive fault is a separate issue, strange since the Disk Utility says the drive is healthy and I'm running the self test now. Perhaps a bad cable is my next check...
how to set up a boot partition on the first hard drive separate from two RAID 5 configurations on a Supermicro server with 1-750GB hard drive for the boot partition, and 15-1TB hard drives for data. The 15 hard drives are split into two RAID 5 configurations (7 -TB drives and 8 1-TB drives). I will be installing CentOS 5.2, and the 15 Terabytes of data will store data, and the 750GB hard drive(on port 0) will only have the 100MB boot file. I am using 3ware BIOS Manager to configure the first array of 7 hard drives, and the second array of 8 hard drives (1 drive with boot information will not be included in the array).
to recap, picture this: I want to load CentOS on this server. /dev/sda1 (on the bottom left drive) needs to house the boot partition set for 100MB. The remaining 7 drives (the left half, not counting the boot drive) need to be set up as a RAID 5 array. The eight drives on the right (right half) also need to be setup as a RAID 5 array. After I configure this in BIOS, I run the CentOS setup disk in graphical mode. I get to the portion after the Language and keyboard setup where it says "Installation requires partitioning of your hard drive. By default, a partitoning layout is chosen which is reasonable for most users. You can either choose to use this or create your own. Select the drive(s) to use for this installation". The drives listed are:
"sda 5721980 MB AMCC 9650-SE-8LP DISK"
"sdb 1020 MB AMCC 9650-SE-8LP DISK"
"sdc 714218 MB AMCC 9650-SE-8LP DISK"
"sdd" 6675643 MB AMCC 9650-SE-8LP DISK"
When I choose "Remove Linux partitions on the selected drives and create default layout." or any other option, I get different errors. I notice when configuring via text mode I get better options to install. I can't install the boot drive separate from the two RAID configurations?
With mdadm was only able to add a new drive to the using the --force function. I do not feel comfortable with using the function that way though. When I remove a disk in VMWare, it perfectly says that the drive is lost and the array is degraded (mdadm --detail /dev/md0). Although after re-adding the drive, it immediately shows device as busy for both mdadm and sfdisk when I don't use --force.
Recovery and repairation of degraded array worked fine with sfdisk --force, mdadm --add --force, it automatically started recovering and took not so long. What are best practises to manage software raid-1 arrays?
Have a customer who is due for a new system. AS they just renewed their RHEL entitlement, they plan on ordering a Dell server without a OS preload. Two questions:
- Will RH let them download RHEL6 just by maintaining the entitlement when their current version is RHEL 3?
- The server will have two RAID arrays - one intended for /home, one for "everything else". As I've never done a clean load with two arrays, how do I select what file systems go on which array?
I am in a situation where I am stuck with a LVM cleanup process. Although I know a lot about AIX LVM , but this is first time I am working with Linux LVM2. Problem is that I created two RAID arrays on storage, which appeared as mpath0 & mpath1 devices (multipath) on RHEL. I created logical volumes and volume groups and every thing was fine till I decided to clean the storage arrays and ran following script:
#!/bin/sh
cat /scripts/numbers | while read numbers
do
lvremove -f /dev/vg$numbers/lv_vg$numbers
vgremove -f vg$numbers
pvremove -f /dev/mapper/mpath$numbersp1
done
Please note that numbers was a file in same directory, having numbers 1 and 2 in separate line. Scripts worked well and i was able to delete definitions properly (however I now think I missed one parted command to remove the partition definition from mpath device. When I created three new arrays, I got devices from mpath2 to mpath5 on linux and then I created vg0 to vg2. By mistake, I ran above script again for cleanup purpose and now I got following error message
Cant remove physical volume /dev/mapper/mpath2p1 of volume group vg0 without ff[/B]
Now after doing mind search, I now realize that I have messed up (particularly because mpath devices did not map in sequence to vg devices and mapping was like mpath2 --- to ---- vg0 and onwards). Now how I can cleanup the lvm definitions? should i go for pvremove -ff flag or investigate further? I am not concerned about data, I just want to cleanup these pv/vg/lv/mpath definations so that lvm can be cleaned up properly and I can start over with new raid arrays from storage?
I have created software raid 5 configurations on the second harddrive its working fine and i have edited fstab file for auto mounting when it reboot but when i reboot the computer raid doesn't work i have to re-create the arrays by typing "mdadm --create" command again and mount again manually ,is there anywhere i can do this once without retyping the commands again after rebooting and i am also using redhat 5
View 1 Replies View Relatedwhat do I have:2x 150GB drives (sda) on a raid card (raid 1)for the OS (slack 13.37)2x 2TB drives (sdb) on that same raid card (raid 1, too)2x 1.5TB drives (sdc,sdd) directly attached to MoBo2x 750GB drives (sde,sdf) attached to MoBo too.if i got about it the normal way, i'd create softRAID 1 out of the the 1.5TB and the 750GB drives and LVM all the data arrays (2TB+1.5TB+750GB) to get a unified disk.If I use btrfs will I be able to do the same? mean I have read how to create raid arrays with mkfs.btrfs and that some lvm capability is incorporated in the filesystem. but will it understand what I want it to do, if i just say
Code:
mkfs.btrfs /dev/sdb1 /dev/sdc1 /dev/sdd1 /dev/sde1 /dev/sdf1
probably not, eh?
I've got a server running a software Raid for SATA disks on a P5E motherboard.
I had to had a lot of memory on thi sserver, then I have had to flash the bios. This has resetted the software raid on the disks, then when I boot, i got a Kernel Panic cause it doesn't find anything ...
how to rebuild the raid ? I can boot on a live cd, or anything else, but don't know how to do it without loosing my data.
I went to setup my linux box and found that the OS drive had finally died. It was an extremely old WD raptor drive in a hot box full of drives so it was really only a matter of time before it just quit on me. Normally this wouldn't be such a big deal however I had just recently constructed an md RAID5 array of 3 1TB disks to act as an NFS mount for basically all of my important files. Maybe 2-3 weeks before the failure I had finished moving all of my most important stuff onto that array. Now I know that the array is intact. All the required data is sitting on those disks. Since only the OS level disk failed on me I should be able to get a new disk in there, reinstall ubuntu and then rebuild that array. how exactly do I go about doing that with mdadm? Do I create the array from the /dev character devices like when I initially built the array?
View 2 Replies View RelatedMy home-backup server, with 8*2TB disks won't boot anymore. Two disks failed at the same time and i rebuilt the raid 6 array without any problem, but now i can't boot the os. I'm using ubuntu server, 10.10. I've made screens of the displays to don't copy everything here. The problem at the boot:
And the Grub config: It's not a production server, but i would like to have it online. I've tried for the lasts 2 days (just a couple hours a day) but without success. I was suggested to do "mount -o remount,rw /" and than edit /etc/fstab, but it get the file don't exist error.
With mdadm was only able to add a new drive to the using the --force function. I do not feel comfortable with using the function that way though.
When I remove a disk in VMWare, it perfectly says that the drive is lost and the array is degraded (mdadm --detail /dev/md0). Although after re-adding the drive, it immediately shows device as busy for both mdadm and sfdisk when I don't use --force.
Recovery and repairation of degraded array worked fine with sfdisk --force, mdadm --add --force, it automatically started recovering and took not so long.
What are best practises to manage software raid-1 arrays?
I've got a raid5 array of 4 disks with ubuntu 8.04 runing on it that is currently still working:
/dev/sda
/dev/sdb
/dev/sdc
/dev/sdd
Smartmontools for /dev/sdc tell that there are 9 sectors pending for reallocation:
Code:
197 Current_Pending_Sector 0x0012 100 100 000 Old_age Always - 9
198 Offline_Uncorrectable 0x0010 100 100 000 Old_age Offline - 9
And /dev/sdd has increasing number of reallocated sectors (about 1 every couple of minutes):
Code:
5 Reallocated_Sector_Ct 0x0033 100 100 036 Pre-fail Always - 1735
/dev/sdc has failed a coulple of times this week (but I have always sucessfully readded it to raid5) . But the increasing number of reallocated sectores on /dev/sdd concerns me even more.
I'm affraid that during removal of /dev/sdd and adding new /devs/sdd disk, raid might fall appart. That's why I would try to do it in Ubuntu Live CD:If the raid falls appart (/dev/sdc fails) during the readding of new /dev/sdd disk, I might still remove the new /dev/sdd and return the previous one and assemble the raid with:
/dev/sda
/dev/sdb
/dev/sdd (old one that was previously removed)
Does assembling Raid in Ubuntu Live and adding new disk for /dev/sdd write anything on /dev/sda, /dev/sdb and /dev/sdc in the process of adding /dev/sdd into raid5?
I have two SAS RAID controller cards in a Dell server in slots 2 & 3, both with an array hanging off them. I went to install a third card into slot 1, but then when it boots it says two of my sd's have bad magic number in the super-block and it wants me to create an alternative one, which I don't want to do. If i remove the new card, the server boots perfectly like it did before I added the new card. Is the new card trying to control stuff that isn't hooked up to it because its in slot 1, so its confusing RHEL?
View 5 Replies View RelatedI've cloned a machine by removing a HDD from a Raid mirror set putting it into another machine and powering on and fsck'ing a few times and everything is great apart from the ethernet port numbering has gone a bit wonky.
The cloned machine which must have a specific configuration using eth0,1,2,3 naming convention however when I boot the freshly cloned machine eth4,5,6,7 show up and eth0,1,2,3, are missing (as it detects the new machines ethernet ports)
Is there some configuration file I can delete, reboot the machine and then Fedora rebuilds the file using eth0,1,2,3, and populating with the correct hardware address.I need to clone this machine lots and lots and lots of times and the manual why I've figured out is a little long winded.
I have a 5 disk raid 5 array that is composed of SATA A:0,1; SATA B: 0,1, and SATA C:0, and one of the disks (SATA A:0) recently went bad on me. I have an ICP raid controller that is about 5 years old. I replaced SATA A:0. After rebooting, I went into the controller and verified that it saw the disk in the hard-disk info section...there I noticed that in the "status" section, that the SATA C:0, SATA B:1 disks were listed as being "in array", the SATA A disks were blank, and the SATA B:0 disk was listed as "fragment". When I go into the "repair array" section, the controller tells me that there are no arrays that are in failure, error, or need to be rebuilt.
This puzzles me, as I thought the controller would know that the array needs to be rebuilt after replacing the disk and I don't see a way to initiate a rebuild. If I just let the server boot after replacing the disk, then I get back that there are the correct number of disks in the raid 5 and that it is ready, however, the screen then goes blank and I get a blinking cursor and the system seems to hang. There are no activity lights on any of the drives associated with the raid 5, which makes me think that the system is not rebuilding the array at this point.
I have set up a software raid 5 and a software raid 1 on the same 3 disks.
But my problem is, every couple of days the software raid starts automatically resyncing. This resync is always succesful.
I do not know why this happens, any ideas to troubleshoot this further? I can not see an error in /var/log/messages
I have a problem with arrays in awk. What i want is to take some data from a file (ssh log) and print it to a html table. I have managed to print some stuff (user logged in and how many times they have logged in) What i want more is to take all the ip that each user logged in from and print it in a row next to the username and times (in the code i typed blabbla where i want the ip to be shown. How do you think i should approch that, multidimensional arrys maybe?
Code:
Its from a Synology Box with 3 disks, which one is damaged. But this disk wasnt in use.Take a look on the raid-size of 493 GB - and the both available disks with 250GB..)
On the others there were a linear raid. during this damaged disk the synology-device tells me, that the volume was crashed.But it look like, that this disk was not mounted into this volume.Quote:
DiskStation> mdadm --detail /dev/md2
/dev/md2:
Version : 00.90
[code]....
I have a server that has one drive with Ubuntu already loaded on it. I would like add another drive and then create a mirrored RAID between the two.
View 4 Replies View RelatedCould any RAID gurus kindly assist me on the following RAID-5 issue?I have an mdadm-created RAID5 array consisting of 4 discs. One of the discs was dropping out, so I decided to replace it. Somehow, this went terribly wrong and I succeeded in marking two of the drives as faulty, and the re-adding them as spare.
Now the array is (logically) no longer able to start:
mdadm: Not enough devices to start the array.Degraded and can't create RAID ,auto stop RAID [md1]
I was able to examine the disks though:
Code:
root@127.0.0.1:/etc# mdadm --examine /dev/sdb2
/dev/sdb2:
Magic : a92b4efc
Version : 00.90.00
code....
Code:
mdadm --create --assume-clean --level=5 --raid-devices=4 /dev/sda2 /dev/sdb2 /dev/sdc2 /dev/sdd2
As I don't want to ruin the maybe small chance I have left to rescue my data, I would like to hear the input of this wise community.
I was trying to update the drive for my adaptec raid controller. Unfortunately, Adaptec only provides RPM packages. So I converted the package using alien. After dpkg install, I then tried using dkms to build the module:
Code:
root@atulsatom# dkms add -m aacraid -v 1.1.5.26400
Adding driver was successful, but I got some error during the build
Code:
root@atulsatom# dkms build -m aacraid -v 1.1.5.26400
Kernel preparation unnecessary for this kernel. Skipping.
[Code]...
I have a ubuntu sever with a raid1 data drive formated in native linux ext3. I have searched for answers to my question but most likely I'm not asking it correctly. I want to use the data drive to store backups of files from various ubuntu and windows machines. Do I need to reformat the drive as ntfs to enable windows use or can it remain as ext3? For that matter can I reformat as ext4 as a soultion? Again, I wish to use the data drive as a backup storage.
View 3 Replies View Related