Sponsored Content
Special Forums Hardware Filesystems, Disks and Memory MDADM Failure - where it came from? Post 302926370 by achenle on Sunday 23rd of November 2014 06:07:49 PM
Old 11-23-2014
Looks like sdh2 failed, and you got a NULL pointer dereference immediately afterwards. So much for robustness in event of a disk failure...

Check all your disks.
 

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
voldiskadm(8)						      System Manager's Manual						     voldiskadm(8)

NAME
voldiskadm - Menu interface for LSM disk administration SYNOPSIS
/usr/sbin/voldiskadm DESCRIPTION
The voldiskadm script is an interactive tool that presents a menu of possible operations to the user. When an operation is selected, the script guides the user through the necessary steps, and prompts for data needed to complete the operation. The voldiskadm interface is intended mainly for beginning users and for those who prefer a simple method for doing common operations. The interface uses query-based prompts to gather input, with defaults supplied when possible. Context-sensitive help is available at every prompt by typing ?. Also, a list option can be used to get information on available target disks for an operation. For operations that require a device name, one or more names can be specified using a space-separated list. Names in the list can have the form dskn or rdskn (for an entire disk) or dsknp or rdsknp (for a specific disk partition). Disk names relate directly to device names in the /dev/disk and /dev/rdisk directories. The file, /etc/vol/disks.exclude, may be used to exclude disks from use by voldiskadm. Each line of the file specifies the name of a disk to exclude (for example, dsk5). The voldiskadm menu includes the following options: Add or initialize one or more disks This option prompts for one or more disk device addresses. The specified disks can be added to an existing disk group, added to a new disk group, added to a disk group as spares, or initialized but not added to a disk group (reserved for use as replacement disks). After specifying the disks, the user is prompted for a disk group (rootdg by default) and a disk name. If no name is specified, a default disk name is assigned (diskn for disks in the rootdg disk group and diskgroupn for disks in other disk groups). The disks are then checked to ensure that there is no information already on them. If there is, the user is given the option of encapsulating the disks. Encapsulate one or more disks This option prompts for one or more disk addresses. It then calls volencap to encapsulate the specified partitions. Remove a disk This option prompts for a disk, by disk media name. The disk is checked to ensure that no subdisks reside on the disk. If the disk is in use, the operation fails with a recommendation to first move all volumes off the disk. If this disk is the last disk in a disk group, the user is prompted for whether the disk group should be removed from the system, as well. The operation proceeds by calling voldg rmdisk to remove the disk from its disk group. If this is the last disk in its disk group, voldg deport is used, instead, to remove the disk group from use. Remove a disk for replacement This option prompts for a disk, by disk media name. The disk is checked for volumes that would lose all mirrors as a result of the operation. If such volumes exist, they are listed and the user is prompted to ensure that the operation should proceed. The operation proceeds by calling voldg -k rmdisk to dissociate the media record from the physical disk. If some formatted disks are under LSM control but not assigned to a disk group, the user is prompted for whether one of these disks should be used as a replacement. Replace a failed or removed disk This option prompts for a disk media name. The named media record must be dissociated from a disk. If the media record is not in the removed state, unused disks are scanned for matching disk IDs. If a disk with a matching disk ID is found, the user is prompted for whether that disk should be reattached. If a matching disk is not used, the user is prompted for a new disk, by device name. If the named replacement disk has a valid disk header, but is not allocated to a disk group, the user is prompted for whether the disk should be reinitialized. If the named replacement disk is listed as allocated to a disk group or to another host, the user is prompted to ensure that the operation should proceed. If the device is to be initialized, a new disk label is written to the disk to reflect its private and public regions. Given an initialized disk, the operation proceeds by replacing the disk in a disk group with voldg -k adddisk. Mirror volumes on a disk This option prompts for a disk, by disk media name. It then prompts for a destination disk within the same disk group, also by disk media name. Specifying no destination disks indicates that any disk is suitable. The operation proceeds by calling volmirror to mirror the volumes. Mirroring volumes from the boot disk will produce a disk that can be used as an alternate boot disk. This is done by calling the volrootmir command. Move volumes from a disk This option prompts for a disk, by disk media name. It then prompts for a possible list of destination disks, also by disk media name. Specifying no destination disks indicates that any disk is suitable. The operation proceeds by calling volevac to move sub- disks off the disk. Enable access to (import) a disk group This option prompts for a disk, by device address. The operation proceeds by calling voldg import to import the disk group stored on that disk. Disable access to (deport) a disk group This option prompts for a disk group name. The prompt display lists alternate disk groups and the disks (media name and access name) that they contain. The operation proceeds by calling voldg deport. Enable (online) a disk device This option prompts for a disk device. The prompt display allows for a display of disks on the system. The operation only func- tions for disks currently in an offline state. It then proceeds to make the disk accessible. Disable (offline) a disk device This option prompts for a disk device. The prompt display allows for a display of disks on the system. The operation only func- tions for disks currently in an online state but not part of any disk group. It then proceeds to mark the disk as offline such that the Logical Storage Manager makes no further attempt at accessing the disk. Mark a disk as a spare for a disk group This option sets up a disk to be used as a spare device for its disk group. A spare disk can be used to automatically replace a disk that has failed. No space can be used on a disk that is marked as a spare. Turn off the spare flag for a disk This option removes a disk from those that can be used as a spare and returns its space to the general pool of available space. Recover plexes and volumes after replacement This operation performs plex attachment, RAID-5 subdisk recovery, and resynchronize operations for the named volumes, or for volumes residing on the named disks (media name). If no media name or volume operands are specified, the operation applies to all volumes (or to all volumes in the specified disk group). ERRORS
See the voldiskadd(8) reference page for a description of errors related to the initialization operation. FILES
A list of disks to exclude from use by voldiskadm. SEE ALSO
disklabel(8), volintro(8), voldg(8), voldisk(8), voldiskadd(8), voldisksetup(8), volrootmir(8) voldiskadm(8)
All times are GMT -4. The time now is 10:07 PM.
Unix & Linux Forums Content Copyright 1993-2022. All Rights Reserved.
Privacy Policy