Sponsored Content
Special Forums Hardware Filesystems, Disks and Memory MDADM Failure - where it came from? Post 302926584 by Sunghost on Tuesday 25th of November 2014 10:12:52 AM
Old 11-25-2014
Hi,
i got this everytime i want to add a disk to the array. Meanwhile i think its a problem with the marvel chipset on the sata controller and perhaps smart. this seems to crash the disks if they under heavy load.
 

10 More Discussions You Might Find Interesting

1. Programming

ld failure

Hi, I am using gmake to compile a c program with a makefile. The make file runs ld. I get the following error jsh1035c:/users/egate453/admegate/kapil/samples $ gmake -e -f GNUmakefile queue_c gmake -f ./GNUmakefile queue_c in_objdir=1 build_root=/users/egate453/admegate/kapil/samples... (2 Replies)
Discussion started by: handak9
2 Replies

2. Linux

mdadm - Swapping 500GB disks for 1TB

Hi, I have a three disk raid 5, with 500GB disks. This is close to being full, and whilst I can just add another disk and rebuild to add another 500GB, I would prefer to replace with 1TB disks. So i have some questions. Can I replace these disks one by one with bigger disks? I... (1 Reply)
Discussion started by: snoop2048
1 Replies

3. Virtualization and Cloud Computing

is mdadm --incremental --rebuild --run --scan destructive?

Hello Unix Community: My task to figure out how to add a 20G volume to an existing EBS Array (RAID0) at AWS. I haven't been told that growing the existing volumes isn't an option, or adding another larger volume to the existing array is the way to go. The client's existing data-store is... (0 Replies)
Discussion started by: Habitual
0 Replies

4. Emergency UNIX and Linux Support

mdadm unable to fail a resyncing drive?

Hi All I have a RAID 5 array consisting of 4 drives that had a partial drive failure in one of the drives. Rebooting shows the faulty drive as background rebuilding and mdadm /dev/ARRAYID shows three drives as in sync with the fourth drive as spare rebuilding. However the array won't come... (9 Replies)
Discussion started by: Bashingaway
9 Replies

5. UNIX for Advanced & Expert Users

mdadm question

Hello, I have 4 drives (500G each) in a raid 10, I got a power failior and this is the result? cat /proc/mdstat Personalities : md126 : inactive sdb sdc sdd sde 1953536528 blocks super external:-md127/0 md127 : inactive sdd(S) sde(S) sdb(S) sdc(S) 9028 blocks super... (3 Replies)
Discussion started by: rmokros
3 Replies

6. UNIX for Advanced & Expert Users

mdadm container! How does it work

Hi everyone, I am not sure if I understand how mdadm --create /dev/md0 --level=container works? A device called /dev/md0 appears in /proc/mdstat but I am not sure how to use that device? I have 2 blank drives with 1 500GB partition on each. I would like to setup mirroring, but not in the... (0 Replies)
Discussion started by: hytron
0 Replies

7. Red Hat

mdadm for / and /boot

had this RHEL 5 installation with /dev/sda1 and /dev/sda2 running.. created two more partitions /dev/sdj1 and /dev/sdj2 , the same sized partition as /dev/sda trying to use mdadm to create RAID1 .. I cannot even do it in "rescue" mode, I wonder if it can be done.. it kept... (2 Replies)
Discussion started by: ppchu99
2 Replies

8. UNIX for Dummies Questions & Answers

boot up failure unix sco after power failure

hi power went out. next day unix sco wont boot up error code 303. any help appreciated as we are clueless. (11 Replies)
Discussion started by: fredthayer
11 Replies

9. UNIX for Advanced & Expert Users

USB RAID 5 Problem on Joli OS 1.2 (Ubuntu) using mdadm

Hi All, I have been trying to create a USB RAID 5 using mdadm tool on Joli OS 1.2 (Ubuntu) but with no luck. I cannot even get pass the creation of array device (/dev/md0) and superblock. I am using 3 USB keys (2 16.4 GB kingston and 1 16GB sandisk). My steps are: ... (5 Replies)
Discussion started by: powelltallen
5 Replies

10. UNIX for Advanced & Expert Users

How to fix mistake on raid: mdadm create instead of assemble?

Hi guys, I'm new to RAID although I've had a server running raid5 for a while. It was delivered preinstalled like this and I never really wondered how to monitor and maintain it. This quick introduction just to let you understand why I'm such an idiot asking such a silly question. Now what... (0 Replies)
Discussion started by: chebarbudo
0 Replies
volreattach(8)						      System Manager's Manual						    volreattach(8)

NAME
volreattach - Reattaches disk drives that have once again become accessible SYNOPSIS
/usr/sbin/volreattach [-rb] [accessname...] /usr/sbin/volreattach -c accessname OPTIONS
The volreattach utility has the following options: Calls the volrecover utility to attempt to recover stale plexes of any volumes on the failed disk. Performs the reattach operation in the background. Checks whether a reattach is possible. No operation is performed, but the name of the disk group and disk media name at which the disk can be reattached is displayed. DESCRIPTION
The volreattach utility attempts to reattach disks using the same disk group and media names they had before detachment. This operation may be necessary if a disk has a transient failure, or if some disk drivers are unloaded or unloadable when the Logical Storage Manager is started, causing disks to enter the failed state. If the problem is fixed, the volreattach command can be used to reattach the disks without plexes being flagged as stale, as long as the reattach happens before any volumes on the disk are started. The volreattach command is called from the voldiskadm menus as part of disk recovery. The volreattach utility tries to find a disk with a disk group and disk ID matching that of the disk(s) being reattached. If the matching disk is found, the reattach operation may still fail if the original cause (or some other cause) for the disk failure still exists. EXIT CODES
A zero exit status is returned if it is possible to perform a reattach. Otherwise, non-zero is returned. SEE ALSO
volintro(8), voldiskadm(8), volrecover(8) volreattach(8)
All times are GMT -4. The time now is 02:55 PM.
Unix & Linux Forums Content Copyright 1993-2022. All Rights Reserved.
Privacy Policy