cdrom_pc_intr The drive appears confused (故障解决)
来源:互联网 发布:windows xp 桌面位置 编辑:程序博客网 时间:2024/05/04 18:15
在ESX管理过程中,安装VMware tools 引起的guest OS死锁。
http://www.vmwarewolf.com/cdrom_pc_intr-the-drive-appears-confused/
内容:
Had an interesting case today where the customer reported the following error message in /var/log/messages every ten seconds on an ESX server:
Dec 5 09:42:36 esx3 kernel: hda: lost interruptDec 5 09:42:36 esx3 kernel: hda: cdrom_pc_intr: The drive appears confused (ireason = 0x 1)Dec 5 09:42:46 esx3 kernel: hda: lost interruptDec 5 09:42:46 esx3 kernel: hda: cdrom_pc_intr: The drive appears confused (ireason = 0x 1)Dec 5 09:42:56 esx3 kernel: hda: lost interruptDec 5 09:42:56 esx3 kernel: hda: cdrom_pc_intr: The drive appears confused (ireason = 0x 1)
The weird thing is, we checked all of the VMs and none of them were configured to use any cdrom devices!
I saw something like this once after a vmware tools install. Currently, the system ejects the CD at the end of the tools installation without checking the locks held by the guest operating system. After this occurs, the guest operating system might not recognize the state of the drive.
If the guest operating system doesn’t recognize the CD-ROM state, either by showing old CD-ROM contents or giving I/O errors, you can resolve the issue by rebooting the guest operating system after the tools installation. The trouble is, this VM had some ’issues’ from the get-go so the customer had tried to delete it.
The clue came when he tried to delete the files from the VM.
rm: cannot remove : Device or resource busy
This sounded like remnants of that VM were still around. If you login as root and do this:
# esxtop
This will display a list of running VMs (and other stuff). Now,
# ps -ef | grep -ir <name of VM>
where <name of VM> is your defunct VM. We got something like this:
root1209710 Dec04 ?00:00:02 /usr/lib/vmware/bin/vmkload_app /usr/lib/vmware/bin/vmware-vmx -ssched.group=host/user -@ pipe=/tmp/vmhsdaemon-0/vmx7b99e7aa583e4b1b;vm=7b99e7aa583e4b1b /vmfs/volumes/45b5eb1a-808343db-ecab-00114335854b/dfsd/dfsd.vmx
root28974 287700 13:12 pts/400:00:00 grep -ir dfsd
What we needed to do was kill this vm. Do this by executing:
# kill -9 12097<– substitute the PID from your output.
***** These steps are not for the faint of heart or linux newbie. If in doubt, call tech support!
Sure enough there was a PID that could not be killed for that VM. A sure sign something went very wrong with that VM.
A reboot of the ESX hosts is the only recourse once you have a process that can’t be killed.
The drive appears confused…. indeed!
我最后是用restart解决,看不到哪个vm异常。真是奇怪
- cdrom_pc_intr The drive appears confused (故障解决)
- the greeter application appears to be crashing的解决
- confused
- Confused
- Identifying the replacement drive
- 如何解决 It appears that the Web Project,“”,has no Web Root directory setup 问题
- MAC os, Google drive 登录故障排除 (There was a problem signing in)
- Google drive 不能登录解决(和SS配合)
- Win7系统下 解决安装虚拟机出错提示:the msi failed invalid Drive: D\
- It is confused that the difference of JSP with Servlet
- Find the element that appears once
- Find the element that appears once
- The web application [] appears to have started ...
- ubuntu 开机出现“ the disk drive for /media/XXXX is not ready yet or not present“解决
- VSS使用故障及解决(1)
- 【原创】Windows故障解决(一)
- ORA-600 kcratr_nab_less_than_odr故障解决(转载)
- 日常工作总结(只读文件系统故障解决)
- 一个异或加密解密函数
- 使用jw palyer播放web中的flv视频
- linux 更改shell
- THINKPAD SL400 重装XP系统的经历
- Objective-C入门解读与内存管理方式
- cdrom_pc_intr The drive appears confused (故障解决)
- LAMP开发中的一些知识点
- C 内联汇编
- TValueListEditor 控件使用方法
- clob转换成String
- 算法和算法分析基础
- 名词解释:归档
- Android修改Framework-res.apk使状态栏背景颜色为黑色或透明
- Monitor 小见解