From:https://www.xuebuyuan.com/zh-tw/1545031.html
Fault a
boot not found can not open Stage 1 boot failure:: error loading hd (40) / boot, and then turn on the computer after the crash, the following message appears on the console screen.
Analysis: This indicates Boot files in the root directory of the system is lost. Interactive Boot program is used to load and execute UNIX programs, mainly for core loading and execution of UNIX Caozuojitong. During boot Boot read / etc / default / boot, the boot process of displaying information, and perform load / unix. So when Boot file damage will cause the system fails to boot.
Solution: 1 Boot disk into the drive and power the machine again, this time from the start booting Boot disks;
Knock hd (40) 2. In the system boot prompt / unix, the command for the UNIX kernel is loaded from the hard disk. Root password and enter the single-user mode, appears superuser #;
3. Boot command to the disc mounted on the hard disk, mount / dev / fd0135ds18 / mnt, then use the command: cp / mnt / boot / resume Drive Boot file in the root directory;
4. command umount / dev / fd0135ds18 Boot tray to unload from the hard drive;
5. haltsys knock off the system, and then remove the disk Boot, the troubleshooting system may boot properly;
6. After the user enters the super normal system boot, the owner and group / boot files were converted to bin system originally defined.
Failure II
after the machine is powered on, the console screen displays the following information: unix not found, then crashes.
Analysis: This indicates UNIX core loss. Because / unix contains the core, unix file damage will cause the system can not be mounted parallel kernel, which freezes.
Solution: 1 Boot disk into the drive and power the machine again, this time from the start booting Boot disks;
Type 2. In the system boot prompt: fd (64) unix root = hd (40) swap = hd (41) pipe = hd (40) only or type fd (64) / unix also. This command is used from the UNIX kernel Boot disc loaded, and then enter the Root password into single-user mode, appears superuser #;
3. command mount / dev / fd0135ds18 / mnt Boot disc mounted on the hard disk, and then use the command: cp / mnt / unix / unix file recovery in the root directory of the hard disk;
4. command umount / dev / fd0135ds18 Boot tray to unload from the hard drive;
5. Type haltsys shut down the system, remove the Boot disk, the troubleshooting system may boot properly;
6. After the user enters the super normal system boot, bin, and to the owner and group mem / unix file system to originally defined.
Failure three
Symptom: The system at startup into multi-user systems, and displays the following information:
No user license were found on the machine,please boot signle-user and correct this situation, License software will not operated untill user license are installed.
The license policy manager Daemon(ifor_pmd) was unable to start,This is usually due to a read only root filesystem,lack of user license or a damaged program image file(/etc/ifor_pmd).
if this is not the case,please contact your sco service provider.
That is: The system can not find the User License at startup, go to single-user installation or maintenance mode to modify user License.
Analysis: boot the system into single-user maintenance mode, view with uname-X command system of the effective number of users is zero, execution scoadmin hypervisor, and select "License Manager" option to check for previously installed 15 users are present, but the License status have expired (expired). Exit scoadmin management system, check the operating system with the date command date 95.10.10. The current system date is set to the correct date, restart the machine, the system enters multi-user state.
Original, SCOUNIX's License with a valid time control functions, UNIX during startup called by the / etc / inittab command / etc / ifor_pmd command to check whether the system has a legitimate License, when the system date beyond the License validity period, the operating system will It is considered illegal and can not start, can only enter single-user maintenance mode.
Fault IV
Symptom: The system in normal operation, the screen suddenly displays the following error message and repeat display:
Warrning:wd0:Error fixed disk dev
1/42,block=5160,cmd=0x00000020
status=0x00005940,sector=122340,
cylinder/heah=477/0
Analysis: this phenomenon is generally of bad blocks causing the hard disk system alarm. Badtrk execution command, select "2, scan disk" option in the super-user, and then select the "1, Scanentire unix partition" options "1, quickscan" option, unix non-destructive scanning the entire partition, the hard disk to find the bad blocks s position. After the scan, the position (Cylinder / Head) note the hard bad blocks, select "3, Add entries to current bad track table by Cylinder / Head number" option, the location of the system according to the hint for the hard bad blocks (Cylinder / Head number). After all the bad blocks are input to exit by Q; screen:
Do you want to update this device with the new table(Y/N)?
Select the Y; screen:
Do you want to salvage any valid data on the bad tracks(Y/N)?
Select the Y; After completion, the system returns to the UNIX super user, the hard disk is no longer displayed on the screen of the alarm information.