05-27-2011
The problem is this: you made a 1:1 copy of a harddisk, and wrote that to a much smaller disk. dd doesn't care about that, and didn't say anything since you specified the noerror option. Everything that's in the final part of the image that didn't fit on the target disk was silently discarded, apparently including a lot of LVM and Ext4 information.
To get a better copy that can handle different disk sizes, take a look at
Clonezilla. They claim to be the Norton Ghost equivalent for Linux, but I haven't tested that claim yet.
This User Gave Thanks to pludi For This Post:
10 More Discussions You Might Find Interesting
1. UNIX for Advanced & Expert Users
Hi
does any body knows some usefull oneline ressources about systemp partitioning ?
A FaQ would be perfect...
thanks (0 Replies)
Discussion started by: pinguis
0 Replies
2. UNIX for Dummies Questions & Answers
Hi friends,
In my case, there are serveral PCs running Linux in a LAN.
I would like to to mount the directory /A_river of machine-A to the file system of another machine machine-B so that I can access files in that directory.
I do not know how to do this. The situation is complicated by... (2 Replies)
Discussion started by: cy163
2 Replies
3. Shell Programming and Scripting
Hi Experts...
Greetings for the day..!
I just want to FTP the files to mainframe system..
my code is not working..and also i need to put the files in a particular directory in a specific naming format...
ftp -i -n ${HOST_NAME} << END_FTP
user ${USER_NAME} ${PASSWORD}
put ${FILE_NAME}... (3 Replies)
Discussion started by: spkandy
3 Replies
4. Solaris
I get "mount: I/O error" when trying to mount an existing FAT32 iSCSI target. I also tried formatting the iSCSI target with fdisk and got
fdisk: "Error in ioctl DKIOCSMBOOT"
Details --
According to the format command, the whole disk is allocated to slice 6 and /dev/rdsk shows this as:... (0 Replies)
Discussion started by: ctafret
0 Replies
5. UNIX for Advanced & Expert Users
I get "mount: I/O error" when trying to mount an existing FAT32 iSCSI target. I also tried formatting the iSCSI target with fdisk and got
fdisk: "Error in ioctl DKIOCSMBOOT"
Details --
According to the format command, the whole disk is allocated to slice 6 and /dev/rdsk shows this as:... (1 Reply)
Discussion started by: ctafret
1 Replies
6. Solaris
Hello, I am having an issue with a SUN FIRE V440. First of all, lots of mirrors and submirrors needed maintenance, so I applied #metasync to fix all of them, but I still couldn't mount all the partitions
of the server .
I tried to mount manually all the partitions that appear in the /etc/vfstab... (4 Replies)
Discussion started by: feg
4 Replies
7. HP-UX
Hi all
I wonder if its possible to mount on a hp-ux server a file system that was previously mounted on a solaris 10 server. The LUN is on NetApp stoarge.
The problem on hp-ux I cannot do pvcreate on the lun (disk) because contains data.
Any help will be appreciated
FR (2 Replies)
Discussion started by: fretagi
2 Replies
8. UNIX for Advanced & Expert Users
I need to be able to move data around a disk that has mounted partitions. I am not touching the data on the mounted partition, the MBR or any other disk metadata, only the freespace and unmounted partitions. At the moment I am using libparted but it causes data corruption sometimes although there... (1 Reply)
Discussion started by: vstrom
1 Replies
9. AIX
Hi ,
We i try to mount aix filesystem i am getting the following error
mount: 0506-324 Cannot mount /dev/fslv11 on /testdir: A system call received a parameter that is not valid.
Please help me out (2 Replies)
Discussion started by: chidori
2 Replies
10. OS X (Apple)
Hello, fellow Unixers and Macers,
I'll run several OS X versions each on its own dedicated partition. Partitions won't be seeing each other (by editing fstab). Question: will I be able to copy files between those partitions? Partition #1: Mavericks. Partition #2: HighSierra (2 Replies)
Discussion started by: scrutinizerix
2 Replies
LEARN ABOUT HPUX
vxsplitlines
vxsplitlines(1M) vxsplitlines(1M)
NAME
vxsplitlines - show disks with conflicting configuration copies in a cluster
SYNOPSIS
vxsplitlines [-g diskgroup] [-c daname]
DESCRIPTION
If you import portions of a disk group on different systems, this can lead to conflicting configuration copies on the disks of the disk
group.
If the configuration information in a disk group is ambiguous, it may not be possible for Veritas Volume Manager to determine which config-
uration copy is most up-to-date. (This is usually termed a serial split brain (SSB) condition when it occurs in a cluster.) You cannot
import a disk group in this state unless you specify which disk's configuration copy to use.
You can use the vxsplitlines command to see which disks in a disk group have conflicting configuration copies, and use this information
together with your knowledge of the history of the disk groups' usage to determine which configuration copy is most valid.
The output from vxsplitlines displays the vxdg commands that you can run to import the disk group using the available configuration copies.
The -o selectcp option of the vxdg import command is used to select the configuration copy to use for the import.
OPTIONS
-c daname Display the SSB IDs for each disk that are stored in the configuration copy on the disk specified by its disk access name.
Note: Although the SSB IDs for some disks may match, this does not necessarily mean that those disks' configuration copies have
recorded all the configuration changes. When viewed from some other configuration copies, the SSB IDs of the same disks may not
match.
-g diskgroup
Specifies the disk group. If a disk group is not specified, the default disk group is used as determined from the rules on the
vxdg(1M) manual page.
EXAMPLES
Display the disks on each side of the split in the disk group newdg:
vxsplitlines -g newdg
Display the SSB IDs stored in the configuration copy on disk c2t4d0:
vxsplitlines -g newdg -c c2t4d0
NOTES
The vxsplitlines is primarily intended to be used with private disk groups, but it also works with shared disk groups.
The version number of the disk group must be 110 or greater.
SEE ALSO
vxdg(1M)
Veritas Volume Manager Administrator's Guide
VxVM 5.0.31.1 24 Mar 2008 vxsplitlines(1M)