Linux - HardwareThis forum is for Hardware issues.
Having trouble installing a piece of hardware? Want to know if that peripheral is compatible with Linux?
Notices
Welcome to LinuxQuestions.org, a friendly and active Linux Community.
You are currently viewing LQ as a guest. By joining our community you will have the ability to post topics, receive our newsletter, use the advanced search, subscribe to threads and access many other special features. Registration is quick, simple and absolutely free. Join our community today!
Note that registered members see fewer ads, and ContentLink is completely disabled once you log in.
If you have any problems with the registration process or your account login, please contact us. If you need to reset your password, click here.
Having a problem logging in? Please visit this page to clear all LQ-related cookies.
Get a virtual cloud desktop with the Linux distro that you want in less than five minutes with Shells! With over 10 pre-installed distros to choose from, the worry-free installation life is here! Whether you are a digital nomad or just looking for flexibility, Shells can put your Linux machine on the device that you want to use.
Exclusive for LQ members, get up to 45% off per month. Click here for more info.
root@morhouse:~# mount /dev/cdrom /mnt/cdrom/
mount: block device /dev/cdrom is write-protected, mounting read-only
mount: /dev/cdrom: can't read superblock
/var/log/debug:
Jul 13 01:47:00 morhouse kernel: hdc: command error: status=0x51 { DriveReady SeekComplete Error }
Jul 13 01:47:00 morhouse kernel: hdc: command error: error=0x54 { AbortedCommand LastFailedSense=0x05 }
Jul 13 01:47:00 morhouse kernel: ide: failed opcode was: unknown
Jul 13 01:47:00 morhouse kernel: ATAPI device hdc:
Jul 13 01:47:00 morhouse kernel: Error: Illegal request -- (Sense key=0x05)
Jul 13 01:47:00 morhouse kernel: Illegal mode for this track or incompatible medium -- (asc=0x64, ascq=0x00)
Jul 13 01:47:00 morhouse kernel: The failed "Read 10" packet command was:
Jul 13 01:47:00 morhouse kernel: "28 00 00 00 00 10 00 00 02 00 00 00 00 00 00 00 "
Jul 13 01:47:00 morhouse kernel: end_request: I/O error, dev hdc, sector 64
Jul 13 01:47:00 morhouse kernel: Buffer I/O error on device hdc, logical block 16
Jul 13 01:47:00 morhouse kernel: Buffer I/O error on device hdc, logical block 17
root@morhouse:/# ls -la /dev/cdrom
lrwxrwxrwx 1 root root 3 Jul 13 2009 /dev/cdrom -> hdc
root@morhouse:/# ls -la /dev/hd*
brw-rw---- 1 root disk 3, 0 Jun 22 2007 /dev/hda
brw-rw---- 1 root disk 3, 1 Jun 9 2002 /dev/hda1
brw-rw---- 1 root disk 3, 2 Jun 9 2002 /dev/hda2
brw-rw---- 1 root disk 3, 3 Jul 13 10:53 /dev/hda3
brw-rw---- 1 root disk 3, 64 Jul 13 2009 /dev/hdb
brw-rw---- 1 root disk 3, 65 Jul 13 2009 /dev/hdb1
brw-rw---- 1 root cdrom 22, 0 Jul 13 2009 /dev/hdc
Jul 13 10:53:14 morhouse kernel: Uniform Multi-Platform E-IDE driver Revision: 7.00alpha2
Jul 13 10:53:14 morhouse kernel: ide: Assuming 33MHz system bus speed for PIO modes; override with idebus=xx
Jul 13 10:53:14 morhouse kernel: VP_IDE: IDE controller at PCI slot 0000:00:07.1
Jul 13 10:53:14 morhouse kernel: VP_IDE: chipset revision 6
Jul 13 10:53:14 morhouse kernel: VP_IDE: not 100%% native mode: will probe irqs later
Jul 13 10:53:14 morhouse kernel: VP_IDE: VIA vt82c686b (rev 40) IDE UDMA100 controller on pci0000:00:07.1
Jul 13 10:53:14 morhouse kernel: ide0: BM-DMA at 0xc000-0xc007, BIOS settings: hdaMA, hdbMA
Jul 13 10:53:14 morhouse kernel: ide1: BM-DMA at 0xc008-0xc00f, BIOS settings: hdcMA, hddio
Jul 13 10:53:14 morhouse kernel: Probing IDE interface ide0...
Jul 13 10:53:14 morhouse kernel: hda: SAMSUNG SV1021H, ATA DISK drive
Jul 13 10:53:14 morhouse kernel: hdb: ST34311A, ATA DISK drive
Jul 13 10:53:14 morhouse kernel: ide0 at 0x1f0-0x1f7,0x3f6 on irq 14
Jul 13 10:53:14 morhouse kernel: Probing IDE interface ide1...
Jul 13 10:53:14 morhouse kernel: hdc: ATAPI-CD ROM-DRIVE-52MAX, ATAPI CD/DVD-ROM drive
Jul 13 10:53:14 morhouse kernel: ide1 at 0x170-0x177,0x376 on irq 15
Jul 13 10:53:14 morhouse kernel: hda: max request size: 128KiB
Jul 13 10:53:14 morhouse kernel: hda: 19932192 sectors (10205 MB) w/426KiB Cache, CHS=19774/16/63, UDMA(100)
Jul 13 10:53:14 morhouse kernel: hda: cache flushes not supported
Jul 13 10:53:14 morhouse kernel: hda: hda1 hda2 hda3
Jul 13 10:53:14 morhouse kernel: hdb: max request size: 128KiB
Jul 13 10:53:14 morhouse kernel: hdb: 8452080 sectors (4327 MB) w/256KiB Cache, CHS=8944/15/63, UDMA(33)
Jul 13 10:53:14 morhouse kernel: hdb: cache flushes not supported
Jul 13 10:53:14 morhouse kernel: hdb: hdb1
Jul 13 10:53:14 morhouse kernel: hdc: ATAPI 52X CD-ROM drive, 128kB Cache, UDMA(33)
Jul 13 10:53:14 morhouse kernel: Uniform CD-ROM driver Revision: 3.20
root@morhouse:/# cat /dev/cdrom | od | more
cat: /dev/cdrom: Input/output error
0000000
root@morhouse:/# cat /proc/filesystems | grep iso
iso9660
root@morhouse:/# uname -a
Linux morhouse 2.6.21.5 #2 Tue Jun 12 15:48:07 CDT 2007 i686 AMD Duron(tm) processor AuthenticAMD GNU/Linux
root@morhouse:~# lspci -vvv
..
00:07.1 IDE interface: VIA Technologies, Inc. VT82C586A/B/VT82C686/A/B/VT823x/A/C PIPC Bus Master IDE (rev 06)
(prog-if 8a [Master SecP PriP])
Control: I/O+ Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR- FastB2B-
Status: Cap+ 66MHz- UDF- FastB2B+ ParErr- DEVSEL=medium >TAbort- <TAbort- <MAbort- >SERR- <PERR-
Latency: 32
Region 0: [virtual] Memory at 000001f0 (32-bit, non-prefetchable) [size=8]
Region 1: [virtual] Memory at 000003f0 (type 3, non-prefetchable) [size=1]
Region 2: [virtual] Memory at 00000170 (32-bit, non-prefetchable) [size=8]
Region 3: [virtual] Memory at 00000370 (type 3, non-prefetchable) [size=1]
Region 4: I/O ports at c000 [size=16]
Capabilities: [c0] Power Management version 2
Flags: PMEClk- DSI- D1- D2- AuxCurrent=0mA PME(D0-,D1-,D2-,D3hot-,D3cold-)
Status: D0 PME-Enable- DSel=0 DScale=0 PME-
root@morhouse:~# less /var/log/debug | wc -l
12019
root@morhouse:~# mount -t iso9660 /dev/cdrom /mnt/cdrom/ -o default
mount: block device /dev/cdrom is write-protected, mounting read-only
mount: wrong fs type, bad option, bad superblock on /dev/cdrom,
missing codepage or other error
In some cases useful info is found in syslog - try
dmesg | tail or so
root@morhouse:~# less /var/log/debug | wc -l
12019
root@morhouse:~# mount -t iso9660 /dev/cdrom /mnt/cdrom
mount: block device /dev/cdrom is write-protected, mounting read-only
mount: wrong fs type, bad option, bad superblock on /dev/cdrom,
missing codepage or other error
In some cases useful info is found in syslog - try
dmesg | tail or so
Jul 14 10:40:40 morhouse kernel: hdc: command error: status=0x51 { DriveReady SeekComplete Error }
Jul 14 10:40:40 morhouse kernel: hdc: command error: error=0x54 { AbortedCommand LastFailedSense=0x05 }
Jul 14 10:40:40 morhouse kernel: ide: failed opcode was: unknown
Jul 14 10:40:40 morhouse kernel: ATAPI device hdc:
Jul 14 10:40:40 morhouse kernel: Error: Illegal request -- (Sense key=0x05)
Jul 14 10:40:40 morhouse kernel: Illegal mode for this track or incompatible medium -- (asc=0x64, ascq=0x00)
Jul 14 10:40:40 morhouse kernel: The failed "Read 10" packet command was:
Jul 14 10:40:40 morhouse kernel: "28 00 00 00 00 10 00 00 01 00 00 00 00 00 00 00 "
Jul 14 10:40:40 morhouse kernel: end_request: I/O error, dev hdc, sector 64
Jul 14 10:40:40 morhouse kernel: isofs_fill_super: bread failed, dev=hdc, iso_blknum=16, block=16
in the cd-rom usual cd =)I tried the differen.. cd or cd-rw - Without a difference.. These are usual cd with the data. In windows they open without problems.
livecd too do not work. Cannot be loaded up to the end (slax, centos or freebsd bootonly cd.)
You should not have dups of a problem that you post in another forum.
Btw, you have not stated other than that a 'windows data' is contained on the cd disc.
You say that you can't mount. Since you are just 'mount /dev/somedev /mnt/somemount_point' then the default ext2 filesystem will be used. This was mention in the other post along with the reason. SO I hope you understand the reason not to dup a post.
Hi,
Since you are just 'mount /dev/somedev /mnt/somemount_point' then the default ext2 filesystem will be used.
This post has been reported.
mount autodetects filesystems. 'mount /some/dev /some/mount/point' should be fine (I use that for e.g. FAT partitions or CD images ['-o loop' option needed].
This seems to be an issue with the Linux drivers for the drive because different media and distroes show a similar behavior.
You should not have dups of a problem that you post in another forum.
Btw, you have not stated other than that a 'windows data' is contained on the cd disc.
You say that you can't mount. Since you are just 'mount /dev/somedev /mnt/somemount_point' then the default ext2 filesystem will be used. This was mention in the other post along with the reason. SO I hope you understand the reason not to dup a post.
This post has been reported.
The disk contains not "windows the data". this Usual disk with the data. usual iso9660 disk. I can try to open any another with the same success. I tried to use an "-t iso9660" option.
Code:
root@morhouse:~# mount -t iso9660 /dev/cdrom /mnt/cdrom
mount: block device /dev/cdrom is write-protected, mounting read-only
mount: wrong fs type, bad option, bad superblock on /dev/cdrom,
missing codepage or other error
In some cases useful info is found in syslog - try
dmesg | tail or so
Please post your thread in only one forum. Posting a single thread in the most relevant forum will make it easier for members to help you and will keep the discussion in one place. This thread is being closed because it is a duplicate.
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.
