Manuals / Lucent Technologies / Home Audio / Speaker

Lucent Technologies 585-210-940 manual Troubleshooting4, Excessively long resync

Models: 585-210-940

1 106

Download 106 pages 54.9 Kb

Page 87

Troubleshooting4

Troubleshooting	CentreVu CMS Release 3 Version 8 Disk-Mirrored Systems
Solstice DiskSuite problems	81

4

Troubleshooting4

This chapter contains procedures for troubleshooting problems you may experience while installing or maintaining systems that use disk mirroring.

Solstice DiskSuite problems

The root filesystem runs out of space during a system install

Excessively long resync

If you run out of space on the /(root) file system—while trying to install Solaris patches, for example—you probably installed your /cms swap file on root. Do the following to recover:

1.Unmount /cms: umount /cms

2. Enter the command: ls -l /cms

If the output of that command lists a swap file, do the following:

a. Enter: mount /cms Remounts /cms.

b. Enter: df -k

Verifies that space is available.

When using metadetach and metattach to detach and then reattach a submirror, it may take a long time—sometimes hours—for resync to complete. You cannot do any maintenance (adding or replacing disks and so on) while the resync is in progress. That behavior is normal. Try again later.

Image 87

Lucent Technologies 585-210-940 manual Troubleshooting4, Excessively long resync, Solstice DiskSuite problems

Contents

585-210-940Comcode 108502352 Issue 1 December CentreVu Call Management SystemRelease 3 Version Disk-MirroredSystems Copyright  1999 Lucent Technologies Table of Contents Page Index Page Introduction to Disk Mirroring1 Disk mirroring definedMetadevices Concatenated metadevicesIntroduction to Disk Mirroring State databases MirrorsSolstice DiskSuite Introduction to Disk MirroringHow CMS implements disk mirroring Introduction to Disk Mirroringd21 d20 swap Introduction to Disk Mirroringd13 d12 d17 d16Mirror layouts Enterprisecomputer Enterprise computerIntroduction to Disk Mirroring Additional references Required softwareHow CMS implements disk mirroring Introduction to Disk MirroringDisk drive slots Installing Mirrored SystemsIncreasing system capacity Step 1 Identify mirror devicesInstalling Mirrored Systems Installing Mirrored Systems Step 2 Install the mirror disks on an systemEnterprise Installing Mirrored Systems Installing Mirrored Systems Step 4 Partition the mirror disksInstalling Mirrored Systems Step 5 Create the state database replicas Step 6 Create the md.tab table entriesInstalling Mirrored Systems Installing Mirrored Systems d x y 1 deviceInstalling Mirrored Systems # /usr/sbin/shutdown -i6 -g0 -y hostname login rootPassword password # #metaroot d13Installing Mirrored Systems Step 8 Set up the mirrors for the swap spaceInstalling Mirrored Systems Installing Mirrored Systems Step 9 Set up the /cms mirrorStep 10 Verify disk space Installing Mirrored SystemsDisk Space Verification Installing Mirrored Systems Step 11 Create an alternate boot deviceInstalling Mirrored Systems Enterprise Step 1 Install the hardwareStep 2 Install the operating system EnterpriseStep 3 Install the application software Installing Mirrored Systems Step 4 Check the disk.type fileInstalling Mirrored Systems Installing Mirrored Systems Step 6 Run the setup scriptsInstalling Mirrored Systems Step 7 Verify disk spaceDisk Space Verification Installing Mirrored SystemsStep 8 Install the CMS software Step 9 Create an alternate boot deviceInstalling Mirrored Systems Installing Mirrored Systems Installing Mirrored Systems Maintaining Mirrored Systems Using the alternate boot deviceChanging the scheduled run time Canceling chkDisksMaintaining the chkDisks crontab Activating chkDisks Verifying chkDiskshostname login root Doing a CMSADM backup on a mirrored systemStep 2 Run the backup Step 1 Print the vfstab fileMaintaining Mirrored Systems Step 3 Label and store the tapesMaintaining Mirrored Systems Restoring from a CMSADM BackupMaintaining Mirrored Systems Restoring from a CMSADM BackupRepairing /cms Repairing or rebuilding the /cms file systemRebuilding /cms Maintaining Mirrored Systems Maintaining Mirrored Systems Restoring a mirrored system from a CMSADM backup Step 1 Power off the systemStep 2 Install the new drives Action Step 3 Boot the system from the compact diskMaintaining Mirrored Systems TaskAction Step 4 Identify the systemMaintaining Mirrored Systems TaskAction Step 5 Set the Name Service optionsMaintaining Mirrored Systems TaskAction Step 6 Set the date and timeMaintaining Mirrored Systems TaskResult Maintaining Mirrored SystemsTask ActionStep 8 Select the hard disks Step 9 Set up the disk partitionsthis column Slice numbersNames in Sizes inAction Step 10 Install the operating systemMaintaining Mirrored Systems TaskAction Step 11 Complete the OS installationMaintaining Mirrored Systems TaskStep 13 Restore the backup Step 14: Reestablish the disk mirrorshostname login root 5.Create md.tab.new 8.Set up the root mirror9. Get to the boot prompt Maintaining Mirrored SystemsMaintaining Mirrored Systems hostname login root Password root passwordMaintaining Mirrored Systems Restoring specific files from a CMSADM backupAdding new disks to a standard mirrored system Maintaining Mirrored Systems hostname login rootMaintaining Mirrored Systems Maintaining Mirrored Systems Adding new disks to a nonstandard mirrored systemMaintaining Mirrored Systems Maintaining Mirrored Systems Step 1 Identify the faulty disk Replacing a faulty diskMaintaining Mirrored Systems Step 2 Identify the submirrorsmetadetach metamirror submirror Step 3 Detach the submirrorsMaintaining Mirrored Systems Step 5 Replace the faulty disk driveMaintaining Mirrored Systems Step 6: Recreate the state database replicasStep 7 Reattach the submirrors Step 8 Reboot the system boot disks onlyState Database Replicas Setting up replicas Replacing replicasPartitioning disks with the format command Maintaining Mirrored Systems Metadevice Maintaining Mirrored Systemsb.Edit the /etc/opt/SUNWmd/md.tab file Root Metadevice Device NamesValid vfstab files Examples of valid system filesValid md.tab files Troubleshooting4 Excessively long resyncSolstice DiskSuite problems probe-fcal-all The system fails to recognize all disk drivesTroubleshooting probe-scsi-allUnit 0 Disk SEAGATE ST34371W SUN4.2G74629737K6748 ok setenv auto-boot?trueok boot -r console login root PasswordTroubleshooting Fixing “needs maintenance” messagesBoot problems Primary boot device is not availableTrying to boot from the wrong device Troubleshooting Excessive reboot timeDescription Log filesTroubleshooting File NameMessage Explanation Response Error messagesTroubleshooting Error MessagesMessage Explanation Response TroubleshootingError Messages Continued Message Explanation ResponseTroubleshooting Troubleshooting Troubleshooting filename restored from filebackupMessage Response TroubleshootingError Messages Continued Message ResponseMessage Response TroubleshootingError Messages Continued Message Explanation ResponseMessage Explanation Response TroubleshootingError Messages Continued Message ResponseTroubleshooting Index Symbolsand increasing system capacity partitioningtape drives upgradingHow Are We Doing?