Linux - GeneralThis Linux forum is for general Linux questions and discussion.
If it is Linux Related and doesn't seem to fit in any other forum then this is the place.
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.
Well I don't know what is wrong with it, but have you made sure the IDE cable is plugged in and the master/slave setting is correct. Are you sure the drive works?
Since dmesg says that the CD is on hdd I suspect not, unless you have not followed our reccommendations and removed the potentially damaged samsung optical drive
Distribution: open SUSE 11.0, Fedora 7 and Mandriva 2007
Posts: 1,662
Original Poster
Rep:
Thanks Phll
My Samsung CD Burner works. It doesn't work for its full capacity. For example, I can't mount it. So I can't use my CDs. The BenQ is complely dead.
Now I must shut down the computer and look for the faulty cables. I will come back to you all soon.
IA32 = x86 processors. 486's, Pentiums (I-IV), Athlon, Athlon XP, Duron, Sempuron, ect.
IA64 = Itanium I & II processors
AMD64/x86_64 = Pentium IV w/ EMT64, Athlon 64/FX, Opterons, Xeons w/ EMT64
<edit=sorry, appears you are already tring this....>
Are those drive errors occuring with the Samsung drive? It sounds like it got damaged when the other equipment got damaged. Have you tried removing it completely and just using the benQ DVD drive and seeing if that will work by itself?
Not really that important, but I think you'll find its an i in Phil
Can you tell us if you have the Samsung on the Secondary Master or Secondary Slave or elsewhere, the errors in dmesg are for the slave device on the secondary IDE cable
Originally posted by phil.d.g
Can you tell us if you have the Samsung on the Secondary Master or Secondary Slave or elsewhere, the errors in dmesg are for the slave device on the secondary IDE cable
Unless he has swapped the cable from when he pasted parts of his dmesg it is on the secondary slave (/dev/hdd).
Distribution: open SUSE 11.0, Fedora 7 and Mandriva 2007
Posts: 1,662
Original Poster
Rep:
I thank everybody for helping me
I must find out which is Master and which is slave. This will take time. I will find this out and come back to you again.
I have a diskette called 'Hwinfo' . I must start the computer with the diskette inside. It will tell me the details. This diskette is 2 or 3 years old. I got it from a friend of mine. I hope it will work.
Please keep a good watch on this thread when time permits.
Distribution: open SUSE 11.0, Fedora 7 and Mandriva 2007
Posts: 1,662
Original Poster
Rep:
It was IDE Secondary Slave --- Samsung CD -R /RW SW 25
No more.
Then I changed the jumper of the BenQ DVD-ROM to Master.
Afterwards, the things have changed. Please read the following:
IDE Secondary Master is BenQ DVD-ROM 16X
IDE Secondary Slave is Samsung CD -R /RW SW-25
[When your computer starts, you press the 'Delete' button to have a look into the configuration. I got the above details from doing it.]
{ The harddrive is the Primary Master.}
However, I can't mount the CDs. I get the same old message.
--------------------------------------------------------------------------------------------------
--------------------------------------------------------------------------------------------------
[nissanka@c83-250-90-204 nissanka]$ dmesg | less
The above command gave me the following strange output.
tatus=0x59 { DriveReady SeekComplete DataRequest Error }
hdd: request sense failure: error=0x04Aborted Command
hdd: status error: status=0x59 { DriveReady SeekComplete DataRequest Error }
hdd: status error: error=0x04Aborted Command
hdd: drive not ready for command
hdd: status error: status=0x51 { DriveReady SeekComplete Error }
hdd: status error: error=0x04Aborted Command
hdd: status error: status=0x51 { DriveReady SeekComplete Error }
hdd: status error: error=0x04Aborted Command
hdd: status error: status=0x51 { DriveReady SeekComplete Error }
hdd: status error: error=0x04Aborted Command
hdd: ATAPI reset complete
hdd: request sense failure: status=0x51 { DriveReady SeekComplete Error }
hdd: request sense failure: error=0x64Aborted Command LastFailedSense 0x06
hdd: status error: status=0x59 { DriveReady SeekComplete DataRequest Error }
hdd: status error: error=0x04Aborted Command
hdd: drive not ready for command
hdd: status error: status=0x51 { DriveReady SeekComplete Error }
hdd: status error: error=0x04Aborted Command
hdd: status error: status=0x51 { DriveReady SeekComplete Error }
hdd: status error: error=0x04Aborted Command
hdd: status error: status=0x51 { DriveReady SeekComplete Error }
hdd: status error: error=0x04Aborted Command
hdd: ATAPI reset complete
hdd: request sense failure: status=0x59 { DriveReady SeekComplete DataRequest Error }
hdd: request sense failure: error=0x04Aborted Command
hdd: status error: status=0x59 { DriveReady SeekComplete DataRequest Error }
hdd: status error: error=0x04Aborted Command
hdd: drive not ready for command
hdd: status error: status=0x51 { DriveReady SeekComplete Error }
hdd: status error: error=0x04Aborted Command
hdd: status error: status=0x51 { DriveReady SeekComplete Error }
hdd: status error: error=0x04Aborted Command
hdd: status error: status=0x51 { DriveReady SeekComplete Error }
hdd: status error: error=0x04Aborted Command
hdd: ATAPI reset complete
hdd: status error: status=0x19 { SeekComplete DataRequest Error }
hdd: status error: error=0x04Aborted Command
hdd: drive not ready for command
hdd: status error: status=0x11 { SeekComplete Error }
hdd: status error: error=0x04Aborted Command
hdd: status error: status=0x11 { SeekComplete Error }
hdd: status error: error=0x04Aborted Command
hdd: status error: status=0x11 { SeekComplete Error }
hdd: status error: error=0x04Aborted Command
hdd: ATAPI reset complete
hdd: request sense failure: status=0x19 { SeekComplete DataRequest Error }
hdd: request sense failure: error=0x04Aborted Command
hdd: status error: status=0x19 { SeekComplete DataRequest Error }
hdd: status error: error=0x04Aborted Command
hdd: drive not ready for command
hdd: status error: status=0x11 { SeekComplete Error }
hdd: status error: error=0x04Aborted Command
hdd: status error: status=0x11 { SeekComplete Error }
hdd: status error: error=0x04Aborted Command
hdd: status error: status=0x11 { SeekComplete Error }
hdd: status error: error=0x04Aborted Command
hdd: ATAPI reset complete
hdd: request sense failure: status=0x59 { DriveReady SeekComplete DataRequest Error }
hdd: request sense failure: error=0x04Aborted Command
hdd: status error: status=0x59 { DriveReady SeekComplete DataRequest Error }
hdd: status error: error=0x04Aborted Command
hdd: drive not ready for command
hdd: status error: status=0x51 { DriveReady SeekComplete Error }
hdd: status error: error=0x04Aborted Command
hdd: status error: status=0x51 { DriveReady SeekComplete Error }
hdd: status error: error=0x04Aborted Command
hdd: status error: status=0x51 { DriveReady SeekComplete Error }
hdd: status error: error=0x04Aborted Command
hdd: ATAPI reset complete
hdd: packet command error: status=0x59 { DriveReady SeekComplete DataRequest Error }
hdd: packet command error: error=0x04
hdd: status error: status=0x59 { DriveReady SeekComplete DataRequest Error }
hdd: status error: error=0x04Aborted Command
hdd: drive not ready for command
hdd: status error: status=0x51 { DriveReady SeekComplete Error }
hdd: status error: error=0x04Aborted Command
hdd: status error: status=0x51 { DriveReady SeekComplete Error }
hdd: status error: error=0x04Aborted Command
hdd: status error: status=0x51 { DriveReady SeekComplete Error }
hdd: status error: error=0x04Aborted Command
hdd: ATAPI reset complete
hdd: request sense failure: status=0x19 { SeekComplete DataRequest Error }
hdd: request sense failure: error=0x04Aborted Command
hdd: status error: status=0x19 { SeekComplete DataRequest Error }
hdd: status error: error=0x04Aborted Command
hdd: drive not ready for command
hdd: status error: status=0x11 { SeekComplete Error }
hdd: status error: error=0x04Aborted Command
hdd: status error: status=0x11 { SeekComplete Error }
hdd: status error: error=0x04Aborted Command
hdd: status error: status=0x11 { SeekComplete Error }
hdd: status error: error=0x04Aborted Command
hdd: ATAPI reset complete
hdd: request sense failure: status=0x59 { DriveReady SeekComplete DataRequest Error }
hdd: request sense failure: error=0x04Aborted Command
hdd: status error: status=0x59 { DriveReady SeekComplete DataRequest Error }
hdd: status error: error=0x04Aborted Command
hdd: drive not ready for command
hdd: status error: status=0x51 { DriveReady SeekComplete Error }
hdd: status error: error=0x04Aborted Command
hdd: status error: status=0x51 { DriveReady SeekComplete Error }
hdd: status error: error=0x04Aborted Command
hdd: status error: status=0x51 { DriveReady SeekComplete Error }
hdd: status error: error=0x04Aborted Command
hdd: ATAPI reset complete
cdrom: This disc doesn't have any tracks I recognize!
hdd: packet command error: status=0x51 { DriveReady SeekComplete Error }
hdd: packet command error: error=0x04
hdd: request sense failure: status=0x59 { DriveReady SeekComplete DataRequest Error }
hdd: request sense failure: error=0x04Aborted Command
hdd: status error: status=0x59 { DriveReady SeekComplete DataRequest Error }
hdd: status error: error=0x04Aborted Command
hdd: drive not ready for command
hdd: status error: status=0x51 { DriveReady SeekComplete Error }
hdd: status error: error=0x04Aborted Command
hdd: status error: status=0x51 { DriveReady SeekComplete Error }
hdd: status error: error=0x04Aborted Command
hdd: status error: status=0x51 { DriveReady SeekComplete Error }
hdd: status error: error=0x04Aborted Command
hdd: ATAPI reset complete
hdd: request sense failure: status=0x59 { DriveReady SeekComplete DataRequest Error }
hdd: request sense failure: error=0x04Aborted Command
hdd: status error: status=0x59 { DriveReady SeekComplete DataRequest Error }
hdd: status error: error=0x04Aborted Command
hdd: drive not ready for command
hdd: status error: status=0x51 { DriveReady SeekComplete Error }
hdd: status error: error=0x04Aborted Command
hdd: status error: status=0x51 { DriveReady SeekComplete Error }
hdd: status error: error=0x04Aborted Command
hdd: status error: status=0x51 { DriveReady SeekComplete Error }
hdd: status error: error=0x04Aborted Command
hdd: ATAPI reset complete
hdd: status error: status=0x59 { DriveReady SeekComplete DataRequest Error }
hdd: status error: error=0x04Aborted Command
hdd: drive not ready for command
hdd: status error: status=0x51 { DriveReady SeekComplete Error }
hdd: status error: error=0x04Aborted Command
hdd: status error: status=0x51 { DriveReady SeekComplete Error }
hdd: status error: error=0x04Aborted Command
hdd: status error: status=0x51 { DriveReady SeekComplete Error }
hdd: status error: error=0x04Aborted Command
hdd: ATAPI reset complete
hdd: request sense failure: status=0x19 { SeekComplete DataRequest Error }
hdd: request sense failure: error=0x04Aborted Command
cdrom: This disc doesn't have any tracks I recognize!
hdd: status error: status=0x19 { SeekComplete DataRequest Error }
hdd: status error: error=0x04Aborted Command
hdd: drive not ready for command
hdd: status error: status=0x11 { SeekComplete Error }
hdd: status error: error=0x04Aborted Command
hdd: status error: status=0x11 { SeekComplete Error }
hdd: status error: error=0x04Aborted Command
hdd: status error: status=0x11 { SeekComplete Error }
hdd: status error: error=0x04Aborted Command
hdd: ATAPI reset complete
hdd: request sense failure: status=0x59 { DriveReady SeekComplete DataRequest Error }
hdd: request sense failure: error=0x04Aborted Command
hdd: status error: status=0x59 { DriveReady SeekComplete DataRequest Error }
hdd: status error: error=0x04Aborted Command
hdd: drive not ready for command
hdd: status error: status=0x51 { DriveReady SeekComplete Error }
hdd: status error: error=0x04Aborted Command
hdd: status error: status=0x51 { DriveReady SeekComplete Error }
hdd: status error: error=0x04Aborted Command
hdd: status error: status=0x51 { DriveReady SeekComplete Error }
hdd: status error: error=0x04Aborted Command
hdd: ATAPI reset complete
hdd: packet command error: status=0x59 { DriveReady SeekComplete DataRequest Error }
hdd: packet command error: error=0x04
hdd: status error: status=0x59 { DriveReady SeekComplete DataRequest Error }
hdd: status error: error=0x04Aborted Command
hdd: drive not ready for command
hdd: status error: status=0x51 { DriveReady SeekComplete Error }
hdd: status error: error=0x04Aborted Command
hdd: status error: status=0x51 { DriveReady SeekComplete Error }
hdd: status error: error=0x04Aborted Command
hdd: status error: status=0x51 { DriveReady SeekComplete Error }
hdd: status error: error=0x04Aborted Command
hdd: ATAPI reset complete
hdd: request sense failure: status=0x19 { SeekComplete DataRequest Error }
hdd: request sense failure: error=0x04Aborted Command
hdd: status error: status=0x19 { SeekComplete DataRequest Error }
hdd: status error: error=0x04Aborted Command
hdd: drive not ready for command
hdd: status error: status=0x11 { SeekComplete Error }
hdd: status error: error=0x04Aborted Command
hdd: status error: status=0x11 { SeekComplete Error }
hdd: status error: error=0x04Aborted Command
hdd: status error: status=0x11 { SeekComplete Error }
hdd: status error: error=0x04Aborted Command
hdd: ATAPI reset complete
hdd: packet command error: status=0x51 { DriveReady SeekComplete Error }
hdd: packet command error: error=0x04
hdd: request sense failure: status=0x59 { DriveReady SeekComplete DataRequest Error }
hdd: request sense failure: error=0x04Aborted Command
hdd: status error: status=0x59 { DriveReady SeekComplete DataRequest Error }
hdd: status error: error=0x04Aborted Command
hdd: drive not ready for command
hdd: status error: status=0x51 { DriveReady SeekComplete Error }
hdd: status error: error=0x04Aborted Command
hdd: status error: status=0x51 { DriveReady SeekComplete Error }
hdd: status error: error=0x04Aborted Command
hdd: status error: status=0x51 { DriveReady SeekComplete Error }
hdd: status error: error=0x04Aborted Command
hdd: ATAPI reset complete
hdd: request sense failure: status=0x59 { DriveReady SeekComplete DataRequest Error }
hdd: request sense failure: error=0x04Aborted Command
hdd: status error: status=0x59 { DriveReady SeekComplete DataRequest Error }
hdd: status error: error=0x04Aborted Command
hdd: drive not ready for command
hdd: status error: status=0x51 { DriveReady SeekComplete Error }
hdd: status error: error=0x04Aborted Command
hdd: status error: status=0x51 { DriveReady SeekComplete Error }
hdd: status error: error=0x04Aborted Command
hdd: status error: status=0x51 { DriveReady SeekComplete Error }
hdd: status error: error=0x04Aborted Command
hdd: ATAPI reset complete
hdd: status error: status=0x59 { DriveReady SeekComplete DataRequest Error }
hdd: status error: error=0x04Aborted Command
hdd: drive not ready for command
hdd: status error: status=0x51 { DriveReady SeekComplete Error }
hdd: status error: error=0x04Aborted Command
hdd: status error: status=0x51 { DriveReady SeekComplete Error }
hdd: status error: error=0x04Aborted Command
hdd: status error: status=0x51 { DriveReady SeekComplete Error }
hdd: status error: error=0x04Aborted Command
hdd: ATAPI reset complete
hdd: request sense failure: status=0x19 { SeekComplete DataRequest Error }
hdd: request sense failure: error=0x04Aborted Command
hdd: status error: status=0x19 { SeekComplete DataRequest Error }
hdd: status error: error=0x04Aborted Command
hdd: drive not ready for command
hdd: status error: status=0x11 { SeekComplete Error }
hdd: status error: error=0x04Aborted Command
hdd: status error: status=0x11 { SeekComplete Error }
hdd: status error: error=0x04Aborted Command
hdd: status error: status=0x11 { SeekComplete Error }
hdd: status error: error=0x04Aborted Command
hdd: ATAPI reset complete
hdd: request sense failure: status=0x59 { DriveReady SeekComplete DataRequest Error }
hdd: request sense failure: error=0x04Aborted Command
hdd: status error: status=0x59 { DriveReady SeekComplete DataRequest Error }
hdd: status error: error=0x04Aborted Command
hdd: drive not ready for command
hdd: status error: status=0x51 { DriveReady SeekComplete Error }
hdd: status error: error=0x04Aborted Command
hdd: status error: status=0x51 { DriveReady SeekComplete Error }
hdd: status error: error=0x04Aborted Command
hdd: status error: status=0x51 { DriveReady SeekComplete Error }
hdd: request sense failure: status=0x59 { DriveReady SeekComplete DataRequest Error }
hdd: request sense failure: error=0x04Aborted Command
hdd: status error: status=0x59 { DriveReady SeekComplete DataRequest Error }
hdd: status error: error=0x04Aborted Command
hdd: drive not ready for command
hdd: status error: status=0x51 { DriveReady SeekComplete Error }
hdd: status error: error=0x04Aborted Command
hdd: status error: status=0x51 { DriveReady SeekComplete Error }
hdd: status error: error=0x04Aborted Command
hdd: status error: status=0x51 { DriveReady SeekComplete Error }
hdd: status error: error=0x04Aborted Command
hdd: ATAPI reset complete
hdd: status error: status=0x19 { SeekComplete DataRequest Error }
hdd: status error: error=0x04Aborted Command
hdd: drive not ready for command
hdd: status error: status=0x11 { SeekComplete Error }
hdd: status error: error=0x04Aborted Command
hdd: status error: status=0x11 { SeekComplete Error }
hdd: status error: error=0x04Aborted Command
hdd: status error: status=0x11 { SeekComplete Error }
hdd: status error: error=0x04Aborted Command
hdd: ATAPI reset complete
hdd: request sense failure: status=0x19 { SeekComplete DataRequest Error }
hdd: request sense failure: error=0x04Aborted Command
hdd: status error: status=0x19 { SeekComplete DataRequest Error }
hdd: status error: error=0x04Aborted Command
hdd: drive not ready for command
hdd: status error: status=0x11 { SeekComplete Error }
hdd: status error: error=0x04Aborted Command
hdd: status error: status=0x11 { SeekComplete Error }
hdd: status error: error=0x04Aborted Command
hdd: status error: status=0x11 { SeekComplete Error }
hdd: status error: error=0x04Aborted Command
hdd: status error: status=0x59 { DriveReady SeekComplete DataRequest Error }
hdd: status error: error=0x04Aborted Command
hdd: drive not ready for command
hdd: status error: status=0x51 { DriveReady SeekComplete Error }
hdd: status error: error=0x04Aborted Command
hdd: status error: status=0x51 { DriveReady SeekComplete Error }
hdd: status error: error=0x04Aborted Command
hdd: status error: status=0x51 { DriveReady SeekComplete Error }
hdd: status error: error=0x04Aborted Command
hdd: ATAPI reset complete
hdd: request sense failure: status=0x19 { SeekComplete DataRequest Error }
hdd: request sense failure: error=0x04Aborted Command
hdd: status error: status=0x19 { SeekComplete DataRequest Error }
hdd: status error: error=0x04Aborted Command
hdd: drive not ready for command
hdd: status error: status=0x11 { SeekComplete Error }
hdd: status error: error=0x04Aborted Command
hdd: status error: status=0x11 { SeekComplete Error }
hdd: status error: error=0x04Aborted Command
hdd: status error: status=0x11 { SeekComplete Error }
hdd: status error: error=0x04Aborted Command
Distribution: open SUSE 11.0, Fedora 7 and Mandriva 2007
Posts: 1,662
Original Poster
Rep:
Thanks jtshaw for the reply. I really appreciate your help.
[root@c83-250-90-204 nissanka]# mount /dev/cdrom /mnt/cdrom
mount: block device /dev/cdrom is write-protected, mounting read-only
mount: No medium found
[root@c83-250-90-204 nissanka]#
The above is without the CD in the BenQ drive.
---------------------------------------------------------------------------------
[root@c83-250-90-204 nissanka]# mount /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,
or too many mounted file systems
[root@c83-250-90-204 nissanka]#
The above is with the CD in the BenQ drive.
[ It seems now the system doesn't recognize the Samung drive.]
How do I do the mounting you suggested. Please tell me the command.
----------------------------------------------------------------------------------------------------------------
I tried the following; it didn't work.
[root@c83-250-90-204 nissanka]# mount /dev/hdc/cdrom /mnt/hdc/cdrom
mount: mount point /mnt/hdc/cdrom does not exist
[root@c83-250-90-204 nissanka]#
-------------------------------------------------------------------------------------------------------------
[root@c83-250-90-204 nissanka]# mount /dev/hdc/cdrom /mnt/cdrom
mount: special device /dev/hdc/cdrom does not exist
(a path prefix is not a directory)
Distribution: open SUSE 11.0, Fedora 7 and Mandriva 2007
Posts: 1,662
Original Poster
Rep:
I got a boot CD called Hiren's Boot CD.
You could start the computer with it. I tried with it. Both of the drives recognized it. It has a program called 'HWinfo'. It tells you the details as to the computer.
So both of the drives recognize the Boot CD. I wouldn't think it is dead.
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.