Technical Support Pages

 

Title
RecoverEDGE fails to see the primary IDE drive, though it will recognize the SCSI secondary drive.
Keywords
IDE SCSI mixed Primary Secondary RecoverEDGE boot fdisk divvy dparam
Product Release(s)
BackupEDGE 01.01.0x / RecoverEDGE 2
Problem Description
My system uses an IDE hard drive as the primary and a SCSI as its secondary drive. I made my boot/filesystem disks and put them away. My primary drive failed and replaced it with a new one, but RecoverEDGE fails to see the IDE drive, although it does see the secondary SCSI.

Cause
This problem has been brought to the attention to the development department & will be addressed in a later release.

Solution

The IDE drive is still recognized by the kernel, it just isn't made available to the menu interface in RecoverEDGE. The drive can be restored, but the steps would need to be done manually through the RecoverEDGE shell.

Follow the instructions below to recover to perform a root only restore & recover your primary drive.

	  1.  Boot to your RecoverEDGE boot/filesystem floppies

2. Invoke the Utilities Menu > Shell. 3. From the shell prompt, type the following commands:

dparam -w

dparam /dev/rhd00 `dparam /dev/rhd00`

4. Perform an fdisk for your primary IDE drive. fdisk -f /dev/rdsk/0s0 Make sure this is the IDE drive being accessed, if this is the new IDE drive, you shouldn't see any partitions.

5. Create & activate your Unix partition, when complete, quit out of fdisk to save your partition info.

6. The next step would be to run divvy on your hard drive, being it is a new drive, run divvy in installation mode. divvy -i /dev/rdsk/0s0

Create your filesystems exactly as they were on the previous primary drive, keep in mind the size of the filesystems isn't as crucial as the locations of the filesystems.

Before exiting divvy, make any adjustments you require and install the filesystems as shown.

7. You may need to create a device node for RecoverEDGE to mount your root filesystem. Do this by typing the following:

mknod /dev/hd0root b 1 40 (Unix 3.2v4.x) or

mknod /dev/hd0root b 1 42 (Open Server 5) 8. Mount your root filesystem: mount /dev/hd0root /mnt If you are running Open Server 5 you would need to mount your /stand filesystem also by typing:

mount /dev/boot /mnt/stand (Open Server 5 ONLY!!) 9. Begin the restore of your root filesystem only. This example will assume you have a /u and a /u2 filesystem on the secondary drive. cd /mnt

/bin/edge -xVbkfEE a b /dev/tape ./u ./u2 NOTE: a would refer to the block factor of your tape. b would refer to the volume size of your data cartridge. /dev/tape would refer to the device name of your tape drive. This will restore the root filesystems and exclude the /u & /u2 filesystems.

10. When the restore is complete, change directory and umount your mounted filesystems umount /mnt/stand (Open Server 5 ONLY !!!)

umount /mnt (Unix 3.2v4.2 & Open Server 5) 11. Finally, to be safe and possibly save time later, force a boot track & master boot record. This too will need to be done from the shell. Type the following dparam -w

dd if=/etc/hdboot0 of=/dev/hd0a

dd if=/etc/hdboot1 of=/dev/hd0a bs=1k seek=1 12. Exit the shell, and select shut down from the RecoverEDGE menu. Remove the floppies and reboot your system.

Get a printer-friendly version of this document

 

 

Last Updated - 2018/05/16

 

Top
MENU