Sponsored Content
Operating Systems Solaris Cloning the root drive - Help Plz Post 302228401 by incredible on Sunday 24th of August 2008 09:50:27 AM
Old 08-24-2008
Thats why because of precautions, checks and measures to be taken, ufsdump is much faster, easier and safer. Smilie
 

10 More Discussions You Might Find Interesting

1. UNIX for Dummies Questions & Answers

plz Help How should I configure cc compiler output file plz help???

i.e configuration of C compiler :confused: (4 Replies)
Discussion started by: atiato
4 Replies

2. UNIX for Dummies Questions & Answers

Defining a fiber attached tape drive NEED HELP PLZ!

I am new to Unix and I need to install a LTO2 3580 drive that is attached to a 3584 library. How do I define this drive in AIX 5.2 I have already zoned the drive can anyone help me out with? Any help on this would be much appreciated. Thank You, PTALLY (0 Replies)
Discussion started by: ptally
0 Replies

3. Solaris

how to ufsrestore root drive then activate disksuite

I restored a backup of a root drive to a new disk on Solaris 8 which contained a fully functioning disksuite 4.2.1 mirror configuration. The backup is from an identical system and OS. I want to install a second identical disk and recover the mirror configuration. The root disk is up but... (2 Replies)
Discussion started by: csgonan
2 Replies

4. Solaris

safeguarding root drive

I have root drive which i want to guard against possible hard disk loss. How can backup and restore the all user created , filesystem , mount points , meta devices if at all there be hdd failure . Any pointer to good document would be good help . Ours is solaris 8 . (1 Reply)
Discussion started by: Hitesh Shah
1 Replies

5. Shell Programming and Scripting

Root owns removable drive and rsync won't work

I'm using rsync to back up to a usb key rsync -r -t -v -a /home/pc/AGS/ /media/DIESEL/pc/AGS/ It worked fine for a long time, and then not so good. Running from the command line there are a lot of complaints about 'can't chgrp ...'. It's formatted to fat32 so I can read it in all kinds of... (0 Replies)
Discussion started by: triplemaya
0 Replies

6. UNIX for Dummies Questions & Answers

cloning ATAPI drive, SunOs 5.7

I'm trying to image one hard drive to another using SunOs 5.7. I think I've read all of the forum entries that relate to my questions, but I do not find an effective solution to the problem. after I verified my drives had the same geometry and did my analyze to resolve original read errors on... (0 Replies)
Discussion started by: nix8me
0 Replies

7. Solaris

How to check at which drive root FS is?

Dear Gurus, Could you please help me? After problems with power supply, our server was done. While trying to boot it with "boot" command, I am getting message: {3} ok boot Boot device: /pci@8,600000/SUNW,qlc@2/fp@0,0/disk@w5000cca0043b59fd,0 File and args: Boot load failed. The file... (7 Replies)
Discussion started by: nypreH
7 Replies

8. Solaris

Migration of system having UFS root FS with zones root to ZFS root FS

Hi All After downloading ZFS documentation from oracle site, I am able to successfully migrate UFS root FS without zones to ZFS root FS. But in case of UFS root file system with zones , I am successfully able to migrate global zone to zfs root file system but zone are still in UFS root file... (2 Replies)
Discussion started by: sb200
2 Replies

9. Ubuntu

Cannot access or boot encrypted drive (gave up waiting for root device...)

I cannot access or boot from my C drive. I'm running Zorin 9 and the drive is a Samsung SSD. The disk was encrypted on install, and that has not given me any problems before. When I start the system it gets to the memory test page, and does not then load the password prompt, which it used to.... (1 Reply)
Discussion started by: David4321
1 Replies

10. Red Hat

Cloning an empty sever (except OS) onto a smaller drive?

Actually this is a Centos 6.x question, but I think it fits here. I have a client that has a pretty beefy server that will be running all sorts of VMs once I unleash it to the developers. For several reasons, they would like to do a complete clone of the server as is right now, that is with just... (2 Replies)
Discussion started by: xdawg
2 Replies
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)
All times are GMT -4. The time now is 05:08 PM.
Unix & Linux Forums Content Copyright 1993-2022. All Rights Reserved.
Privacy Policy