Can anyone tell me how to capture a QNX4 drive image to either another drive
or (better) to a CD-R? When we ship our product (containing a PC with QNX +
our application installed on an EIDE drive) we need to be able to restore it
exactly in the case of a hard drive failure at some later time.
On a MS-Windows machine I can use Norton’s ghost utility to image a FAT
drive to CD-R or another disk drive. I have no been able to find any way or
product to do this for a QNX drive.
I usually just do a cp -V /dev/hd0.1 /path/to/backup/file and it works for
me (Just make sure your referencing the proper hard drive/paritition).
Someone may have a better method out there. And then with the file you can
write it to a CD-R if you like or what ever you want to do.
Can anyone tell me how to capture a QNX4 drive image to either another
drive
or (better) to a CD-R? When we ship our product (containing a PC with QNX
+
our application installed on an EIDE drive) we need to be able to restore
it
exactly in the case of a hard drive failure at some later time.
On a MS-Windows machine I can use Norton’s ghost utility to image a FAT
drive to CD-R or another disk drive. I have no been able to find any way
or
product to do this for a QNX drive.
I usually just do a cp -V /dev/hd0.1 /path/to/backup/file and it works for
me (Just make sure your referencing the proper hard drive/paritition).
Someone may have a better method out there. And then with the file you can
write it to a CD-R if you like or what ever you want to do.
Won’t writing this back to the new disk have a problem, because of
the (I assume) different geometry? Or will this be taken care of by chkfsys
before/after the 1st reboot?
I’m assuming you will be doing
cp -V /path/to/backup/file /dev/hd0.1 on the new drive
In addition to geometry, there is the issue of bad blocks.
Is they existed on the source drive then your wasting some space on the
target drive.
But if they exist on the target drive you will likely loose some data.
“Alex Cellarius” <acellarius@yahoo.com> wrote in message
news:1103_1027107820@pentium4…
I usually just do a cp -V /dev/hd0.1 /path/to/backup/file and it works
for
me (Just make sure your referencing the proper hard drive/paritition).
Someone may have a better method out there. And then with the file you
can
write it to a CD-R if you like or what ever you want to do.
Won’t writing this back to the new disk have a problem, because of
the (I assume) different geometry? Or will this be taken care of by
chkfsys
before/after the 1st reboot?
I’m assuming you will be doing
cp -V /path/to/backup/file /dev/hd0.1 on the new drive
In addition to geometry, there is the issue of bad blocks.
Is they existed on the source drive then your wasting some space on the
target drive.
But if they exist on the target drive you will likely loose some data.
“Alex Cellarius” <> acellarius@yahoo.com> > wrote in message
news:1103_1027107820@pentium4…
On Fri, 19 Jul 2002 14:43:14 -0400, “Eric Norton” <> enorton@fct.ca
wrote:
Jay,
I usually just do a cp -V /dev/hd0.1 /path/to/backup/file and it works
for
me (Just make sure your referencing the proper hard drive/paritition).
Someone may have a better method out there. And then with the file you
can
write it to a CD-R if you like or what ever you want to do.
Won’t writing this back to the new disk have a problem, because of
the (I assume) different geometry? Or will this be taken care of by
chkfsys
before/after the 1st reboot?
I’m assuming you will be doing
cp -V /path/to/backup/file /dev/hd0.1 on the new drive
\
Sure, but that won’t work if you try to copy the whole partition or drive.
i.e. /dev/hd0 or /dev/hd0t77. Then the entire block special device is
treated as a single file.
I am trying to the same thing. I have been working wih mkisofs but cannot
seem to get it to create a bootable CD (it SIGSEGs).
You can use "cp -rRp -P!src/.bitmap,!.src/inodes src dest
“Bill Caroselli (Q-TPS)” <> QTPS@EarthLink.net> > wrote in message
news:ah9thq$4bs$> 1@inn.qnx.com> …
In addition to geometry, there is the issue of bad blocks.
Is they existed on the source drive then your wasting some space on the
target drive.
But if they exist on the target drive you will likely loose some data.
“Alex Cellarius” <> acellarius@yahoo.com> > wrote in message
news:1103_1027107820@pentium4…
On Fri, 19 Jul 2002 14:43:14 -0400, “Eric Norton” <> enorton@fct.ca
wrote:
Jay,
I usually just do a cp -V /dev/hd0.1 /path/to/backup/file and it
works
for
me (Just make sure your referencing the proper hard
drive/paritition).
Someone may have a better method out there. And then with the file
you
can
write it to a CD-R if you like or what ever you want to do.
Won’t writing this back to the new disk have a problem, because of
the (I assume) different geometry? Or will this be taken care of by
chkfsys
before/after the 1st reboot?
I’m assuming you will be doing
cp -V /path/to/backup/file /dev/hd0.1 on the new drive
Can anyone tell me how to capture a QNX4 drive image to either another drive
or (better) to a CD-R? When we ship our product (containing a PC with QNX +
our application installed on an EIDE drive) we need to be able to restore it
exactly in the case of a hard drive failure at some later time.
On a MS-Windows machine I can use Norton’s ghost utility to image a FAT
drive to CD-R or another disk drive. I have no been able to find any way or
product to do this for a QNX drive.
Any help appreciated!!
Thanks,
Jay
We used for the purpose interaction-free installation of QNX and
backup of files like sysinit, netmap, … Works fine also with different
hard disk, but requires the same network card and VGA card.
you can also ghost the qnx drive, but with some limitations.
Colleague of mine tried hard. Sometimes it worked, somtimes not.
The new drive must have the same number of heads (I think also
sectors/track).
The copy machine should be the same as the target, because of different LBA
adressing with different bios.
Can anyone tell me how to capture a QNX4 drive image to either another
drive
or (better) to a CD-R? When we ship our product (containing a PC with QNX
+
our application installed on an EIDE drive) we need to be able to restore
it
exactly in the case of a hard drive failure at some later time.
On a MS-Windows machine I can use Norton’s ghost utility to image a FAT
drive to CD-R or another disk drive. I have no been able to find any way
or
product to do this for a QNX drive.
you can also ghost the qnx drive, but with some limitations.
Colleague of mine tried hard. Sometimes it worked, somtimes not.
The new drive must have the same number of heads (I think also
sectors/track).
No, only the same size partition. Of course, different CHS usually result
in different sector sizes.
With the right custom code to manipulate the partition table this could be
worked around.
The copy machine should be the same as the target, because of different
LBA
adressing with different bios.
In addition to geometry, there is the issue of bad blocks.
Is they existed on the source drive then your wasting some space on the
target drive.
But if they exist on the target drive you will likely loose some data.
Absolutely correct. However, assuming the partitions are the same size
(regardless of the underlying geometry) and the lack of bad blocks (probable
given the quality of modern drives, esp. when new) then copying the
block-special devices will work.
Trust me, I should know as anyone who recognizes my name can attest.
