Buffer I/O error on device sr0

Buffer I/O error on device sr0, logical block 0

I check today some old CDs, some of them were from ’90 so of course they didn’t work. With one of them was a problem with reading… and ejecting CD-ROM. My PC wasn’t able to eject the CD even calling this command from root:

eject sr0 -rm

didn’t work.

DMESG said:

[ 1067.416522] Buffer I/O error on device sr0, logical block 0
[ 1075.923084] sr 1:0:0:0: [sr0] Unhandled sense code
[ 1075.923088] sr 1:0:0:0: [sr0] Result: hostbyte=DID_OK driverbyte=DRIVER_SENSE
[ 1075.923097] sr 1:0:0:0: [sr0] Sense Key : Hardware Error [current]
[ 1075.923105] sr 1:0:0:0: [sr0] Add. Sense: Timeout on logical unit
[ 1075.923115] sr 1:0:0:0: [sr0] CDB: Read(10): 28 00 00 00 00 00 00 00 02 00
[ 1075.923130] end_request: I/O error, dev sr0, sector 0
[ 1075.923137] Buffer I/O error on device sr0, logical block

The CD wasn’t mounted, there was only a thread for the device, which wasn’t even mounted (I also wasn’t able to mount it from root):

umount: /dev/sr0: not mounted

Solution:

[email protected]:# lsof /dev/sr0
COMMAND PID USER FD TYPE DEVICE SIZE/OFF NODE NAME
blkid 4079 root 3r BLK 11,0 0t0 7203 /dev/sr0

[email protected]:# kill -s 9 4079 ; eject

Worked for me!

时间: 2024-11-05 04:35:54

Buffer I/O error on device sr0的相关文章

Buffer I/O error on device dm-0 . logical block 286846

# dmsetup ls live-osimg-min (253:1) live-rw (253:0) 内核为LVM建立映射关系 实际上是可以使用iostat检测到内存的使用状态的,因为内存被映射成dm-0.

Error: Selected device is not a touchscreen I understand

selected device is not a touchscreen I understand arm交叉编译工具中的头文件库中的linux/input.h中的EV_VERSION定义为 #define EV_VERSION 0x010000 而linux内核include/linux/input.h中的EV_VERSION定义为 #define EV_VERSION 0x010001 由此可见问题就出现在内核的输入子系统的版本号不匹配的问题 解决办法:     1.将内核源代码里的incl

WARNING: Re-reading the partition table failed with error 16: Device or resource busy.

在 mkfs.ext4 /dev/sda2 格式化硬盘空间时,可能出现这样的错误. had this situation at office where I was told to re-partition an already existing partition. The situation was to get the below schema /dev/sdb1 1 3040 24418768+ 83 Linux /dev/sdb2 3041 6080 24418800 83 Linux

DP备份报错 ORA-19554: error allocating device, device type: SBT_TAPE ORA-27211

环境:solaris 10,oracle 11.2.0.4  2nodes rac 症状:rman备份报错如下 RMAN-00571: =========================================================== RMAN-00569: =============== ERROR MESSAGE STACK FOLLOWS =============== RMAN-00571: ======================================

uiautomatorviewer 查看元素报错: Error taking device screenshot: null 原因

使用uiautomatorviewer 查看android某些页面元素,出现错误Error obtaining UI hierarchy  Reason: Error taking device screenshot: null 如图: 再网上找了很多解决办法依然没解决 总结了一下原因: 1.该app不支持该页面的截屏功能所以uiautomatorviewer捕捉不到 2.手机需要重启 3.非原装数据线 4.appium服务异常需要重新连接 以上为个人观点,不代表百分百解决,仅供参考! 声明:本

end_request: I/O error, dev mtdblock2, sector 0 Buffer I

内核移植时遇到这个错误: end_request: I/O error, dev mtdblock2, sector 0 Buffer I/O error on device mtdblock2, logical block 0 原因分析:由于内核是通过uboot烧写到nandflash中,因此uboot产生的ecc校验码与内核的ecc校验码不同,所以需要关闭内核的ecc校验. 解决方法: 打开内核目录中的s3c2410.c文件在内核源码中的drivers/mtd/nand目录中 在s3c241

磁盘 blk_update_request: I/O error

1.尝试1: 解决 blk_update_request: I/O error, dev fd0, sector 0 错误 参考文档: https://bbs.archlinux.org/viewtopic.php?pid=1166918#p1166918 http://www.cyberciti.biz/faq/linux-end_request-ioerror-dev-fd0-sector0/ 在开启了软驱驱动控制器的硬件上引导 Linux 时会出现如下提示:blk_update_reque

Linux 硬盘故障案例分享

本文主要分享下服务器中硬盘发生故障后/var/log/messages 和/var/log/mcelog中会出现的具体日志以及对应的修复方法,随着案例的不断增多和丰富,最后我会归纳形成自动化脚本. 当然其中会有很多硬盘有物理坏道,需要更换,这种就需要硬盘供应商去更换了,此处不在本文讨论范围. 服务器型号: HP SE1170s 硬盘型号: MB2000EAZNL 故障1: Jul 17 00:46:34 xxxxxxxxxxxxxx kernel: [8384801.159283] EXT4-f

u-boot支持yaffs映像烧写的补丁

u-boot的nand flash驱动有两个版本,似乎是以u-boot1.1.5为分界点的,之前的版本使用的是自己写的nand flash驱动,而后面的版本使用的是linux内核中nand flash的驱动.这两个版本有可能在同一个u-boot中存在,都存放在 driver目录下面,一个为nand,一个为nand_legacy,意思为传统的nand flash驱动.两者使用一个宏开关 CFG_NAND_LEGACY来打开,如果定义这个宏的话,将使用传统的nand flash驱动,否则使用最新的f