Sponsored Content
Full Discussion: Hardware RAID
Operating Systems Solaris Hardware RAID Post 302157484 by DukeNuke2 on Friday 11th of January 2008 04:36:00 AM
Old 01-11-2008
Quote:
Originally Posted by moofoo
hello there,
there are a few sun sparc server which "allready" support hardware raids
for instance FireT1000, T2000, T5120 or T5220. (setup done with the raidctl command). Also as allready mentioned above raidz (zfs raid) is a good alternative to that.
cheers
but (afaik) this is not a real hardware raid! better use an external raid-box with fcal or scsi controller...
 

9 More Discussions You Might Find Interesting

1. Solaris

how to hardware RAID 1 on T5120

Hi, I have t5120 sparc and I have 2 146 G drives in the system. I will be installing solaris 10 and also want the system mirrored using Hardware RAID "1" The System did come preinstalled as it comes from sun. I did not do much on it. I booted system using boot cdrom -s gave format... (6 Replies)
Discussion started by: upengan78
6 Replies

2. Solaris

T2000 Hardware RAID

Hi, I have a root with hardware RAID on c0t0d0 and c0t2d0. I would like to set the boot device sequence in OBP for both hdds. I have checked in ls -l /dev/rdsk/ for the path of c0t2d0 but it does not exist. Can anyone shed some lights on this? AVAILABLE DISK SELECTIONS: 0.... (12 Replies)
Discussion started by: honmin
12 Replies

3. UNIX for Dummies Questions & Answers

RAID software vs hardware RAID

Hi Can someone tell me what are the differences between software and hardware raid ? thx for help. (2 Replies)
Discussion started by: presul
2 Replies

4. Solaris

Hardware Raid - LiveUpgrade

Hi, I have a question. Do LiveUpgrade supports hardware raid? How to choose the configuration of the system disk for Solaris 10 SPARC? 1st Hardware RAID-1 and UFS 2nd Hardware RAID-1 and ZFS 3rd SVM - UFS and RAID1 4th Software RAID-1 and ZFS I care about this in the future to take... (1 Reply)
Discussion started by: bieszczaders
1 Replies

5. Hardware

Sun T3-1 hardware RAID

Hi all I've just received my T3-1. It has 8 disks and I would like to configure RAID1 on the disks. The Sun documentation states that you can either use the OpenBoot PROMP utility called Fcode or you can use software via the Solaris OS. The documentation doesn't make it clear if: 1. The... (6 Replies)
Discussion started by: soliberus
6 Replies

6. HP-UX

Hardware RAID in HP Unix rp3440

Hi Gurus, Can anyone tell me the Hardware RAID configuration in HP Unix rp3440 model server containing HP UX B.11.11 OS version. Thanks in Advance. BR, Prasanth (3 Replies)
Discussion started by: prasanth438
3 Replies

7. Solaris

Software RAID on top of Hardware RAID

Server Model: T5120 with 146G x4 disks. OS: Solaris 10 - installed on c1t0d0. Plan to use software raid (veritas volume mgr) on c1t2d0 disk. After format and label the disk, still not able to detect using vxdiskadm. Question: Should I remove the hardware raid on c1t2d0 first? My... (4 Replies)
Discussion started by: KhawHL
4 Replies

8. Solaris

Hardware raid patching

Dear All , we have hardware raid 1 implemented on Solaris Disks. We need to patch the Servers. Kindly let me know how to patch hardware raid implemented Servers. Thanks... Rj (7 Replies)
Discussion started by: jegaraman
7 Replies

9. Solaris

Hardware RAID using three disks

Dear All , Pl find the below command , # raidctl -l Controller: 1 Volume:c1t0d0 Disk: 0.0.0 Disk: 0.1.0 Disk: 0.3.0 # raidctl -l c1t0d0 Volume Size Stripe Status Cache RAID Sub Size ... (10 Replies)
Discussion started by: jegaraman
10 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 02:05 AM.
Unix & Linux Forums Content Copyright 1993-2022. All Rights Reserved.
Privacy Policy