07-05-2005
Sorry about not making it clear but here is the detail..
I have a Dell poweredge 2650 and it has 5 SCSI drive. The orginal I have drive 0 and 1 mirror and dive 2 and 3 mirror and drive 4 is just a straight SCSI. I have a dump level 0 of dive 0 and drive 2, which I would like to recover completely. The new drive I have are a little smaller and the RAID I have configured is different. Drive 0 is a plain volume while drive 1 and 2 are strips and drive 4 is the backup drive I'm restoring the drives from. I have manually partition the drives with fdisk to reflect the orginal partition table of the system. During fdisk I have also toggle the boot flag and made a boot partition on drive 0 which is where the orginal was kept.
Then I manually restore the dump level 0 from dive 4. Which restore OK. Then I change the /etc/fstab to reflect my new partition table and removed all mount point that may have been in the mtab. I have made the /boot and / partition as close to the orginal as possible. Now when I exit from rescue mode. I system will not boot (It does not even load drivers). It looks like a machine with no OS. It seems to not see the boot partition or the boot image. I have checked the permission and everything, but I'm lost as to why it won't boot.
Running RedHat AS3
THANKS ALL
10 More Discussions You Might Find Interesting
1. UNIX for Advanced & Expert Users
I have a SCO Openserver 5.0.6 running Raid 5. and want to make a bootable disk but the boot image is 5MB ie unix file on root is around 5M and the size is obviously too large for a floppy diskette. Please help on how I can make any bootable device. The aim is to change the filesystem size.
... (6 Replies)
Discussion started by: sshokunbi
6 Replies
2. HP-UX
Hi
All of my unix forum friends. I mirrored my hp-ux o/s disk with the help of LVM on a disk array. Can any one tell me the procedure if the O/S disk fails then how could i recover the system disk from mirrored disk
Regards'
Alam (5 Replies)
Discussion started by: waqaralam
5 Replies
3. Solaris
The second disk that I'm trying to make bootable is to hold another version of Solaris (9).
I've created the partitions with format and labeled the disk - created the filesystems with newfs - created and mounted the directories.
...but I think I've missed something out like using fdisk to... (16 Replies)
Discussion started by: pondlife
16 Replies
4. Filesystems, Disks and Memory
In our HP/Unix system, our master scsi drive was bootable and our mirrored drive was non-bootable. Are any of these alternatives possible:
1) Make the non-bootable scsi drive bootable? How?
2) Create a bootable scsi drive, then copy the mirrored data to the newly created scsi drive?
I seek... (1 Reply)
Discussion started by: bfisk
1 Replies
5. HP-UX
I am trying to copy a HP-UX disk. Both the OS and H/W are quite old
HP-UX hpeval3 B.09.10 A 9000/382 080009789a46
I have a 1.5Gb disk and a new 2Gb disk. I have been using the following method to create the copy, which must be a bootable disk.
#mediainit /dev/rdsk/cEd1s0
(2Gb disk) cEd0s0... (9 Replies)
Discussion started by: malcqv
9 Replies
6. Red Hat
Hi To All,
I Have Unfortunately Deleted my Grub,Initrd,Vmlinuz files. And am adding these files By using Rescue Mode, But it is not properly working.
Give Me a Solution.
Iam looking forward from any one.
Thanks in Advance. (1 Reply)
Discussion started by: Sharath Kumar
1 Replies
7. Linux
Can anybody suggest me software to backup Linux server and to make them boot able (1 Reply)
Discussion started by: Vit0_Corleone
1 Replies
8. Fedora
I need to boot the ultimate boot cd from an usb stick. Do I just copy the iso image to the usb key?
How do I make the usb stick bootable? (4 Replies)
Discussion started by: locoroco
4 Replies
9. UNIX for Dummies Questions & Answers
hi,
i recently built a pxe file the problem is I don't know how to add it in the pxe server.
I was wondering if you guys know how to add my pxe file in the pxe server so that when I run the device we're using, I can go lan boot then at boot: I will just type a text and it will boot the built... (0 Replies)
Discussion started by: h0ujun
0 Replies
10. Solaris
trying to do this for a DR situation. I've cloned an iSCSI LUN to another server. I've created an LDOM on it. set the LDOM to auto-boot=false and exported the LUN as a raw disk to the new LDOM. After starting the LDOM and telnetting to it. I can get to the OK prompt and see the disk but when I try... (2 Replies)
Discussion started by: os2mac
2 Replies
LEARN ABOUT REDHAT
mpartition
mpartition(1) General Commands Manual mpartition(1)
Name
mpartition - partition an MSDOS hard disk
Note of warning
This manpage has been automatically generated from mtools's texinfo documentation, and may not be entirely accurate or complete. See the
end of this man page for details.
Description
The mpartition command is used to create MS-DOS filesystems as partitions. This is intended to be used on non-Linux systems, i.e. systems
where fdisk and easy access to Scsi devices are not available. This command only works on drives whose partition variable is set.
mpartition -p drive mpartition -r drive mpartition -I [-B bootSector] drive mpartition -a drive mpartition -d drive mpartition -c [-s sec-
tors] [-h heads] [-t cylinders] [-v [-T type] [-b begin] [-l length] [-f]
Mpartition supports the following operations:
p Prints a command line to recreate the partition for the drive. Nothing is printed if the partition for the drive is not defined, or
an inconsistency has been detected. If verbose (-v) is also set, prints the current partition table.
r Removes the partition described by drive.
I Initializes the partition table, and removes all partitions.
c Creates the partition described by drive.
a "Activates" the partition, i.e. makes it bootable. Only one partition can be bootable at a time.
d "Desactivates" the partition, i.e. makes it unbootable.
If no operation is given, the current settings are printed.
For partition creations, the following options are available:
s sectors
The number of sectors per track of the partition (which is also the number of sectors per track for the whole drive).
h heads
The number of heads of the partition (which is also the number of heads for the whole drive). By default, the geometry information
(number of sectors and heads) is figured out from neighbouring partition table entries, or guessed from the size.
t cylinders
The number of cylinders of the partition (not the number of cylinders of the whole drive.
b begin
The starting offset of the partition, expressed in sectors. If begin is not given, mpartition lets the partition begin at the start
of the disk (partition number 1), or immediately after the end of the previous partition.
l length
The size (length) of the partition, expressed in sectors. If end is not given, mpartition figures out the size from the number of
sectors, heads and cylinders. If these are not given either, it gives the partition the biggest possible size, considering disk
size and start of the next partition.
The following option is available for all operation which modify the partition table:
f Usually, before writing back any changes to the partition, mpartition performs certain consistenct checks, such as checking for
overlaps and proper alignment of the partitions. If any of these checks fails, the partition table is not changes. The -f allows
you to override these safeguards.
The following options are available for all operations:
v Together with -p prints the partition table as it is now (no change operation), or as it is after it is modified.
vv If the verbosity flag is given twice, mpartition will print out a hexdump of the partition table when reading it from and writing it
to the device.
The following option is available for partition table initialization:
B bootSector
Reads the template master boot record from file bootSector.
See Also
Mtools' texinfo doc
Viewing the texi doc
This manpage has been automatically generated from mtools's texinfo documentation. However, this process is only approximative, and some
items, such as crossreferences, footnotes and indices are lost in this translation process. Indeed, these items have no appropriate repre-
sentation in the manpage format. Moreover, not all information has been translated into the manpage version. Thus I strongly advise you
to use the original texinfo doc. See the end of this manpage for instructions how to view the texinfo doc.
* To generate a printable copy from the texinfo doc, run the following commands:
./configure; make dvi; dvips mtools.dvi
* To generate a html copy, run:
./configure; make html
A premade html can be found at: `http://mtools.linux.lu' and also at: `http://www.tux.org/pub/knaff/mtools'
* To generate an info copy (browsable using emacs' info mode), run:
./configure; make info
The texinfo doc looks most pretty when printed or as html. Indeed, in the info version certain examples are difficult to read due to the
quoting conventions used in info.
mtools-3.9.8 02Jun01 mpartition(1)