免费注册 查看新帖 |

Chinaunix

  平台 论坛 博客 文库
最近访问板块 发新帖
楼主: feng551
打印 上一主题 下一主题

系统启动到这一步卡住了,为什么? [复制链接]

论坛徽章:
0
11 [报告]
发表于 2006-10-10 10:01 |只看该作者
GSP Host Name:  a500
GSP> sl


SL

Select Chassis Code Buffer to be displayed:
Incoming, Activity, Error, Current boot or Last boot? (I/A/E/C/L) e
e

Set up filter options on this buffer? (Y/[N]) n
n

The first entry is the most recent Chassis Code
Type + CR and CR to go up (back in time),
Type - CR and CR to go down (forward in time),
Type Q/q CR to quit.


Log Entry #   0 :
SYSTEM NAME: a500
DATE: 10/10/2006 TIME: 01:45:44
ALERT LEVEL: 6 = Boot possible, pending failure - action required

SOURCE: 6 = platform
SOURCE DETAIL: 6 = service processor   SOURCE ID: 0
PROBLEM DETAIL: 0 = no problem detail

CALLER ACTIVITY: 0 = repair   STATUS: 0
CALLER SUBACTIVITY: 00 = unspecified
REPORTING ENTITY TYPE: 7 = customer engineer   REPORTING ENTITY ID: 00

0x4870026066000000 00000000 00000000 type  9 = ASCII Message        
0x58700A6066000000 00006A09 0A012D2C type 11 = Timestamp 10/10/2006 01:45:44
Type CR for next entry, Q CR to quit.



Log Entry #   1 :
SYSTEM NAME: a500
DATE: 10/08/2006 TIME: 03:40:37
ALERT LEVEL: 3 = System blocked waiting for operator input

SOURCE: 1 = processor
SOURCE DETAIL: 1 = processor general   SOURCE ID: 0
PROBLEM DETAIL: 0 = no problem detail

CALLER ACTIVITY: E = system warning   STATUS: F
CALLER SUBACTIVITY: FF = implementation dependent
REPORTING ENTITY TYPE: E = HP-UX   REPORTING ENTITY ID: 00

0xF8E000301100EFFF 00000000 0000EFFF type 31 = legacy PA HEX chassis-code
0x58E008301100EFFF 00006A09 08032825 type 11 = Timestamp 10/08/2006 03:40:37
Type CR for next entry, - CR for previous entry, Q CR to quit.
Log Entry #   2 :
SYSTEM NAME: a500
DATE: 10/08/2006 TIME: 03:40:35
ALERT LEVEL: 3 = System blocked waiting for operator input

SOURCE: 1 = processor
SOURCE DETAIL: 1 = processor general   SOURCE ID: 0
PROBLEM DETAIL: 0 = no problem detail

CALLER ACTIVITY: E = system warning   STATUS: 0
CALLER SUBACTIVITY: 00 = implementation dependent
REPORTING ENTITY TYPE: E = HP-UX   REPORTING ENTITY ID: 00

0xF8E000301100E000 00000000 0000E000 type 31 = legacy PA HEX chassis-code
0x58E008301100E000 00006A09 08032823 type 11 = Timestamp 10/08/2006 03:40:35
Type CR for next entry, - CR for previous entry, Q CR to quit.


Log Entry #   3 :
SYSTEM NAME: a500
DATE: 10/08/2006 TIME: 03:40:25
ALERT LEVEL: 2 = Non-Urgent operator attention required

SOURCE: 0 = unknown, no source stated
SOURCE DETAIL: 0 = unknown, no source stated   SOURCE ID: FF
PROBLEM DETAIL: 0 = no problem detail

CALLER ACTIVITY: 6 = machine check   STATUS: 2
CALLER SUBACTIVITY: 53 = implementation dependent
REPORTING ENTITY TYPE: 0 = system firmware   REPORTING ENTITY ID: 01

0x0000102000FF6532 00000000 00000000 type  0 = Data Field Unused
0x5800182000FF6532 00006A09 08032819 type 11 = Timestamp 10/08/2006 03:40:25
Type CR for next entry, - CR for previous entry, Q CR to quit.

论坛徽章:
0
12 [报告]
发表于 2006-10-10 10:10 |只看该作者
系统引导的问题,根盘有没损坏?系统有没损坏?LIF有没损坏?盘的路径跟系统中设置的启动路径是否一致?是否两块盘镜像,如是,启动盘数的仲裁机制是否取消?

论坛徽章:
0
13 [报告]
发表于 2006-10-10 10:56 |只看该作者
根盘没有损坏   系统没有损坏  LIF没损坏   系统是全新安装的,只有一块硬盘,回答完毕!
问:导致系统引导错误的原因是什么?

论坛徽章:
0
14 [报告]
发表于 2006-10-10 11:05 |只看该作者
你是在这个机器上新装的系统就起不来吗?

论坛徽章:
0
15 [报告]
发表于 2006-10-10 11:07 |只看该作者
系统引导问题一般来说无外乎上面几种原因

论坛徽章:
0
16 [报告]
发表于 2006-10-10 15:46 |只看该作者
打800吧..

论坛徽章:
0
17 [报告]
发表于 2006-10-10 16:40 |只看该作者
对 新装的系统起不来!!!!800打有何用?

论坛徽章:
0
18 [报告]
发表于 2006-10-10 16:42 |只看该作者
都过保的!

论坛徽章:
0
19 [报告]
发表于 2006-10-10 20:38 |只看该作者
我觉得是你的kernel有问题了,手工起vmunix.prev试试看吧

论坛徽章:
0
20 [报告]
发表于 2006-10-10 20:47 |只看该作者
reload kernel
您需要登录后才可以回帖 登录 | 注册

本版积分规则 发表回复

  

北京盛拓优讯信息技术有限公司. 版权所有 京ICP备16024965号-6 北京市公安局海淀分局网监中心备案编号:11010802020122 niuxiaotong@pcpop.com 17352615567
未成年举报专区
中国互联网协会会员  联系我们:huangweiwei@itpub.net
感谢所有关心和支持过ChinaUnix的朋友们 转载本站内容请注明原作者名及出处

清除 Cookies - ChinaUnix - Archiver - WAP - TOP