9 More Discussions You Might Find Interesting
1. UNIX for Advanced & Expert Users
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
2. Solaris
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
3. Fedora
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
4. Solaris
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
5. Emergency UNIX and Linux Support
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
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
7. UNIX for Advanced & Expert Users
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
8. AIX
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
9. UNIX for Advanced & Expert Users
Percent complete SCO 5.0.6 / No longer an issue (0 Replies)
Discussion started by: Henrys
0 Replies
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)