Sponsored Content
Operating Systems Linux Red Hat missing raid array after reboot Post 302528830 by sriniv666 on Wednesday 8th of June 2011 04:49:48 AM
Old 06-08-2011
missing raid array after reboot

Dear all ,

i ve configured raid 0 in redhat machine(VM ware), by following steps:

Code:
#mdadm -C /dev/md0 -l 0 -n 2 /dev/sdb1 /dev/sdc1 
#mkfs.ext3 /dev/md0 
#mdadm --detail --scan --config=mdadm.conf >/etc/mdadm.conf

then
mounted the/dev/md0 device and also added a entry in fstab.

how the isssue is when the system rebooted the raid array configuration is missing, there is no device as /dev/md0..
what's the solution for this??? any help !!!!

Last edited by pludi; 06-08-2011 at 07:06 AM.. Reason: content editing...
 

9 More Discussions You Might Find Interesting

1. UNIX for Advanced & Expert Users

Percent complete error while scanning RAID array during 5.0.6 load

Percent complete SCO 5.0.6 / No longer an issue (0 Replies)
Discussion started by: Henrys
0 Replies

2. AIX

RAID level of array = false?

I created a RAID 5 array and when I list out the attributes of the "hdisk" it reports back raid_level = 5 but the RAID level of the array = false. What does this actually indicate about my array? I've never paid much attention to this until now since I have a disk reporting failure I want to make... (0 Replies)
Discussion started by: scottsl
0 Replies

3. UNIX for Advanced & Expert Users

Create RAID - Smart Array Tool - ML370

Hi guys, i must install an old old old ml370 server... I must create a RAID 5 with my 4 SCSI disk. I need a SmartStart disk for create it or a Floppy Disk called "Array configuration Tool". I don't find it on the hp website...:mad::mad::mad: Anyone have it?? Thanks in advance. Zio (0 Replies)
Discussion started by: Zio Bill
0 Replies

4. Solaris

EFI Disk labels on 3510 raid array

Hi Peeps, Can anyone help me an EFI lablel on a 3510 raid array that I cannot get rid of, format -e and label just asks you if you want to label it. Want an SMI label writing to it. Anyone got any ideas on how to remove the EFI label? Thanks in advance Martin (2 Replies)
Discussion started by: callmebob
2 Replies

5. Emergency UNIX and Linux Support

Loading a RAID array after OS crash

One of my very old drive farm servers had an OS fault and can't boot now but I'd like to restore some files from it. I tried booting Ubuntu from a CD, but it couldn't see the drives -- possibly because they're RAIDed together. Is there a good way to get at my files? The data in question is a... (2 Replies)
Discussion started by: CRGreathouse
2 Replies

6. Solaris

How to find missing disks on Sun x4150 without reboot?

Hi, Here is the issue: There are 4 disks on this Sun x4150 system under Solaris 10, but only 1 disk can be seen by the OS. I've tried commands disks and devfsadm but not working. It's an important production server, so 'reboot -r' is not a choice. # format < /dev/null Searching for... (6 Replies)
Discussion started by: aixlover
6 Replies

7. Fedora

Missing entries in log files just before/after reboot

Hello world, One of the servers, a Fedora one,rebooted today (Luckily, a testbox). I tried to get the reason the server rebooted. After going through the messages, I think that the log entries just before and after reboot are missing. Please below: (****** is the server name, for privacy... (0 Replies)
Discussion started by: satish51392111
0 Replies

8. Solaris

Solaris 10 Installation - Disks missing, and Raid

Hey everyone. First, let me start by saying I'm primarily focused on linux boxes, and just happened to get pulled into building two T5220's. I'm not super educated on sun boxes. Both T5220's have 8 146GB 15k SAS drives. Inside the service processor, I can run SHOW /SYS/HDD{0-7} and they all come... (2 Replies)
Discussion started by: msarro
2 Replies

9. UNIX for Advanced & Expert Users

Revive RAID 0 Array From Buffalo Duo NAS

Thank you in advanced, I had a Buffalo DUO crap out on me that was setup as RAID 0. I dont belive it was the drives but rather the controller in the DUO unit. I bought another external HDD enclosure and was able to fireup the two older DUO drives in it and I think I resembled the RAID... (12 Replies)
Discussion started by: metallica1973
12 Replies
NASH(8) 						      System Manager's Manual							   NASH(8)

NAME
nash - script interpretor to interpret linuxrc images SYNOPSIS
nash [--quiet] [--force] script DESCRIPTION
nash is a very simple script interpretor designed to be as small as possible. It is primarily designed to run simple linuxrc scripts on an initrd image. Arguments to commands may be enclosed in either single or double quotes to allow spaces to be included in the arguments. Spa- ces outside of quotations always delineate arguments, and so backslash escaping is supported. Additionally, if nash is invoked as modprobe, it will immediately exit with a return code of zero. This is to allow initrd's to prevent some extraneous kernel error messages during startup. There are two types of commands, built in and external. External commands are run from the filesystem via execve(). If commands names are given without a path, nash will search it's builtin PATH, which is /usr/bin, /bin, /sbin, /usr/sbin. Currently, nash supports the following built in commands. access -[r][w][x][f] path Tells whether the current user has sufficient permissions to read, write, or execture path, or if the file exists (see access(2) for more information). echo [item]* [> filename] Echos the text strings given to a file, with a space in between each item. The output may be optionally redirected to a file. exec <command> The command given is execed, overlaying the nash process. find dir -name name Display the path to files named name in or below directory dir. This is a very limited implementation of find(1). findlodev Prints the full path to the first unused loopback block device on the system. If none is available, no output is displayed. losetup /dev/loopdev file Binds file to the loopback device /dev/loopdev. See losetup(8) for information on loopback devices. mkdevices path Creates device files for all of the block devices listed in /proc/partitions in the directory specfied by path. mkdir [-p] path Creates the directory path. If -p is specified, this command will not complain if the directory exists. Note this is a subset of the standard mkdir -p behavior. mknod path [c|b] major minor Creates a device inode for path. This is identical to mkdev(1) which the exceptions that it will not create named pipes and if the directories in path do not exist they will be automatically created. mkrootdev path Makes path a block inode for the device which should be mounted as root. To determine this device nash uses the device suggested by the root= kernel command line argument (if root=LABEL is used devices are probed to find one with that label). If no root= argument is available, /proc/sys/kernel/real-root-dev provides the device number. mount [--ro] -o opts -t type device mntpoint Mounts a filesystem. It does not support NFS, and it must be used in the form given above (arguments must go first). If device is of the form LABEL=foo the devices listed in /fB/proc/partitions will be searched, and the first device with a volume label of foo will be mounted. Normal mount(2) options are supported, and --ro will mount the filesystem read only for compatibility with older versions of nash. The defaults mount option is silently ignored. pivot_root newrootpath oldrootpath Makes the filesystem mounted at newrootpath the new root filesystem, and mounts the current root filesystem as oldrootpath. raidautorun mddevice Runs raid autodetection on all raid-typed partitions. mddevice must be a raid device (any will do). showlabels Display a table of devices, their filesystem labels, and their uuids. umount path Unmounts the filesystem mounted at path. RETURN VALUE
Returns 0 is the last command succeeded or 1 if it failed. OPTIONS
--force Allows force really execute the script, even though nash doesn't appear to be running from an initrd image. BUGS
Probably many. nash is not a shell, and it shouldn't be thought of as one. It isn't entirely different from a shell, but that's mostly by accident. AUTHOR
Erik Troan <ewt@redhat.com> 4th Berkeley Distribution Sat Mar 27 1999 NASH(8)
All times are GMT -4. The time now is 04:47 PM.
Unix & Linux Forums Content Copyright 1993-2022. All Rights Reserved.
Privacy Policy