9 More Discussions You Might Find Interesting
1. Solaris
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
2. Solaris
Dear All ,
We need to do patching on one Solaris Server , where we have raid 0 configured.
What is the process to patch a Server if RAID 0 (Concat/Stripe) is there.
Below is the sample output.
# metadb
flags first blk block count
a m pc luo 16 ... (1 Reply)
Discussion started by: jegaraman
1 Replies
3. Solaris
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
4. Hardware
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
5. Solaris
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
6. UNIX for Dummies Questions & Answers
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
7. Solaris
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
8. Solaris
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
9. Solaris
I don't understood why on SPARC-Platforms have not present RAID-Controller ? Sorry for my bad english, but it's crazy always setup software RAID !!! I whanna Hardware RAID and when i can find solution ? (7 Replies)
Discussion started by: jess_t03
7 Replies
LEARN ABOUT REDHAT
mkinitrd
MKINITRD(8) System Manager's Manual MKINITRD(8)
NAME
mkinitrd - creates initial ramdisk images for preloading modules
SYNOPSIS
mkinitrd [--version] [-v] [-f]
[--preload=module] [--omit-scsi-modules]
[--omit-raid-modules] [--omit-lvm-modules]
[--with=module] [--image-version]
[--fstab=fstab] [--nocompress]
[--builtin=module] [--nopivot]
image kernel-version
DESCRIPTION
mkinitrd creates filesystem images which are suitable for use as Linux initial ramdisk (initrd) images. Such images are often used for
preloading the block device modules (such as IDE, SCSI or RAID) which are needed to access the root filesystem. mkinitrd automatically
loads filesystem modules (such as ext3 and jbd), IDE modules, all scsi_hostadapter entries in /etc/modules.conf, and raid modules if the
system's root partition is on raid, which makes it simple to build and use kernels using modular device drivers.
Any module options specified in /etc/modules.conf are passed to the modules as they are loaded by the initial ramdisk.
If the root device is on a loop device (such as /dev/loop0), mkinitrd will build an initrd which sets up the loopback file properly. To do
this, the fstab must contain a comment of the form:
# LOOP0: /dev/hda1 vfat /linux/rootfs
LOOP0 must be the name of the loop device which needs to be configured, in all capital lettes. The parameters after the colon are the
device which contains the filesystem with the loopback image on it, the filesystem which is on the device, and the full path to the loop-
back image. If the filesystem is modular, initrd will automatically add the filesystem's modules to the initrd image.
The root filesystem used by the kernel is specified in the boot configuration file, as always. The traditional root=/dev/hda1 style device
specification is allowed. If a label is used, as in root=LABEL=rootPart the initrd will search all available devices for an ext2 or ext3
filesystem with the appropriate label, and mount that device as the root filesystem.
OPTIONS
--builtin=module
Act as if module is built into the kernel being used. mkinitrd will not look for this module, and will not emit an error if it does
not exist. This option may be used multiple times.
-f Allows mkinitrd to overwrite an existing image file.
--fstab=fstab
Use fstab to automatically determine what type of filesystem the root device is on. Normally, /etc/fstab is used.
--image-version
The kernel version number is appended to the initrd image path before the image is created.
--nocompress
Normally the created initrd image is compressed with gzip. If this option is specified, the compression is skipped.
--nopivot Do not use the pivot_root system call as part of the initrd. This lets mkinitrd build proper images for Linux 2.2 kernels
at the expense of some features. In particular, some filesystems (such as ext3) will not work properly and filesystem options will
not be used to mount root. This option is not recommended, and will be removed in future versions.
--omit-lvm-modules
Do not load any lvm modules, even if /etc/fstab expects them.
--omit-raid-modules
Do not load any raid modules, even if /etc/fstab and /etc/raidtab expect them.
--omit-scsi-modules
Do not load any scsi modules, including 'scsi_mod' and 'sd_mod' modules, even if they are present.
--preload=module
Load the module module in the initial ramdisk image. The module gets loaded before any SCSI modules which are specified in /etc/mod-
ules.conf. This option may be used as many times as necessary.
-v Prints out verbose information while creating the image (normally the mkinitrd runs silently).
--version
Prints the version of mkinitrd that's being used and then exits.
--with=module
Load the modules module in the initial ramdisk image. The module gets loaded after any SCSI modules which are specified in /etc/mod-
ules.conf. This option may be used as many times as necessary.
FILES
/dev/loop* A block loopback device is used to create the image, which makes this script useless on systems without block loopback
support available.
/etc/modules.conf Specified SCSI modules to be loaded and module options to be used.
SEE ALSO
fstab(5), insmod(1), kerneld(8), lilo(8)
AUTHOR
Erik Troan <ewt@redhat.com>
4th Berkeley Distribution Sat Mar 27 1999 MKINITRD(8)