08-21-2008
As DukeNuke wrote, the siblings ufsdump/ufsrestore are your friends.
I don't know the commands by heart, and I haven't got a Solaris box in reach right now.
So I may be wrong.
But first after having plugged in the new drive (run devfsadm -c disk) you will have to copy the VTOC.
If I remember correctly the command for this is fmthard (a bit misleading as it only writes the volume table of contents and doesn't format).
Please look up man fmthard, because you can pipe output from prtvtoc of your moribund drive right into fmthard to the new drive.
Then you will have to write the boot header.
I think the command was installboot. Again look up its manpage
because you have to give it the correct image for your platform (e.g. Sparc vs. IA).
There are examples in the manpage.
Then you need to create filesystems on each mountable partition (or slice in BSD/SunOS jargon).
Use newfs for that.
Then create mount points (mkdir) and mount the new filesystems of the slices.
Before you run the ufsdump, especially on / and /var (if these are separate FS)
you would normaly have to init to single user mode.
But UFS can make filesystem snapshots (damn forgotten the command, google or see man -k snap if you have a whatis created)
Then you mount the snapshot of / and ufsdump from there.
Of course on SDS, SVM, VxVM managed devices the whole procedure is totally different.
Btw, I would suggest that you mirror your system disks with SDS or SVM which are free Solaris tools.
10 More Discussions You Might Find Interesting
1. UNIX for Dummies Questions & Answers
i.e configuration of C compiler :confused: (4 Replies)
Discussion started by: atiato
4 Replies
2. UNIX for Dummies Questions & Answers
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
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
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
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
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
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
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
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
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
HD(4) Linux Programmer's Manual HD(4)
NAME
hd - MFM/IDE hard disk devices
DESCRIPTION
The hd* devices are block devices to access MFM/IDE hard disk drives in raw mode. The master drive on the primary IDE controller (major
device number 3) is hda; the slave drive is hdb. The master drive of the second controller (major device number 22) is hdc and the slave
hdd.
General IDE block device names have the form hdX, or hdXP, where X is a letter denoting the physical drive, and P is a number denoting the
partition on that physical drive. The first form, hdX, is used to address the whole drive. Partition numbers are assigned in the order
the partitions are discovered, and only nonempty, nonextended partitions get a number. However, partition numbers 1-4 are given to the
four partitions described in the MBR (the "primary" partitions), regardless of whether they are unused or extended. Thus, the first logi-
cal partition will be hdX5. Both DOS-type partitioning and BSD-disklabel partitioning are supported. You can have at most 63 partitions
on an IDE disk.
For example, /dev/hda refers to all of the first IDE drive in the system; and /dev/hdb3 refers to the third DOS "primary" partition on the
second one.
They are typically created by:
mknod -m 660 /dev/hda b 3 0
mknod -m 660 /dev/hda1 b 3 1
mknod -m 660 /dev/hda2 b 3 2
...
mknod -m 660 /dev/hda8 b 3 8
mknod -m 660 /dev/hdb b 3 64
mknod -m 660 /dev/hdb1 b 3 65
mknod -m 660 /dev/hdb2 b 3 66
...
mknod -m 660 /dev/hdb8 b 3 72
chown root:disk /dev/hd*
FILES
/dev/hd*
SEE ALSO
chown(1), mknod(1), sd(4), mount(8)
COLOPHON
This page is part of release 3.44 of the Linux man-pages project. A description of the project, and information about reporting bugs, can
be found at http://www.kernel.org/doc/man-pages/.
Linux 1992-12-17 HD(4)