Jump to content

cat /dev/hdd > cd.iso not possible anymore, why?


Recommended Posts

I have always in the past made copies of data cds by doing: cat /dev/hdd > cd.iso where /dev/hdd is my CD/DVD drive.

Since I started using Mandriva 2008.1 this doesn't seem to work anymore, the cd.iso file is always a few bytes short and I get the following error at the end:

 

Sep 22 14:29:37 yampee kernel: hdd: command error: status=0x51 { DriveReady SeekComplete Error }
Sep 22 14:29:37 yampee kernel: hdd: command error: error=0x54 { AbortedCommand LastFailedSense=0x05 }
Sep 22 14:29:37 yampee kernel: ide: failed opcode was: unknown
Sep 22 14:29:37 yampee kernel: ATAPI device hdd:
Sep 22 14:29:37 yampee kernel:   Error: Illegal request -- (Sense key=0x05)
Sep 22 14:29:37 yampee kernel:   Illegal mode for this track or incompatible medium -- (asc=0x64, ascq=0x00)
Sep 22 14:29:37 yampee kernel:   The failed "Read 10" packet command was:
Sep 22 14:29:37 yampee kernel:   "28 00 00 05 13 f8 00 00 3a 00 00 00 00 00 00 00 "
Sep 22 14:29:37 yampee kernel: end_request: I/O error, dev hdd, sector 1331168
Sep 22 14:29:37 yampee kernel: Buffer I/O error on device hdd, logical block 166396
Sep 22 14:29:37 yampee kernel: Buffer I/O error on device hdd, logical block 166397
Sep 22 14:29:37 yampee kernel: Buffer I/O error on device hdd, logical block 166398
Sep 22 14:29:37 yampee kernel: Buffer I/O error on device hdd, logical block 166399
Sep 22 14:29:37 yampee kernel: Buffer I/O error on device hdd, logical block 166400
Sep 22 14:29:37 yampee kernel: Buffer I/O error on device hdd, logical block 166401
Sep 22 14:29:37 yampee kernel: Buffer I/O error on device hdd, logical block 166402
Sep 22 14:29:37 yampee kernel: Buffer I/O error on device hdd, logical block 166403
Sep 22 14:29:37 yampee kernel: Buffer I/O error on device hdd, logical block 166404
Sep 22 14:29:37 yampee kernel: Buffer I/O error on device hdd, logical block 166405

 

If I do the same command on the same physical machine with Mandrake 9.2 (old install on a different partition still bootable with dual boot) it works fine.

 

also md5sum /dev/hdd to verify freshly burned CDs gives the same error while it works fine under Mandrake 9.2 (md5sum matches the downloaded source image).

 

As I'm testing this on the same identical PC with the same CDs, the only difference is Mandrake 9.2 instead of Mandriva 2008.1 there must be something that has changed in the kernel breaking this.

 

Does anyone know a solution to this?

 

 

[moved from Software by spinynorman]

Link to comment
Share on other sites

The easiest way to do this:

 

dd if=/dev/hdd of=mynewcd.iso

 

will make a copy of the CD to the file named mynewcd.iso - of course, rename this to whatever you want it to be where appropriate.

Link to comment
Share on other sites

Thanks for the suggestion but the same thing happens:

 

[root@yampee data]# dd if=/dev/hdd of=mynewcd.iso

dd: reading `/dev/hdd': Input/output error

1331168+0 records in

1331168+0 records out

681558016 bytes (682 MB) copied, 162.807 s, 4.2 MB/s

 

And also the same errors as above in /var/log/messages, I have tried this with several CDs and it works fine for all of them under Mandrake 9.2 but always gives these erros under Mandriva 2008.1.

 

What could be causing this? Has anyone else seen this?

Link to comment
Share on other sites

Yes, I've also just seen it on my laptop also, both as regular user and as root. Using either dd or cat, I also have the same problem. However, when I used brasero, which is the CD/DVD creating program on my system under Gnome/Sound & Video, it made a copy, and when I checked /var/log/messages or dmesg, I didn't have any errors this time.

 

Not found a way as of yet to get it working as regular user or root though from command line.

Link to comment
Share on other sites

Thanks this confirms my suspicion that this appears to be something that has been broken/changed in the kernel somewhere between the 2.4.22 that Mandrake 9.2 uses and 2.6,24 that Mandriva 2008.1 uses.

I'm glad Brasero works, but I really don't want to have to start using GUI tools for this, the command line is much quicker and more flexible.

Where do you think I can report this?

As you have several different distros installed, could you test if you see this with Gentoo and Centos 5 too, so we know the problem not Mandriva specific?

Link to comment
Share on other sites

Currently, Gentoo 2008.0 has the same problem with kernel 2.6.24-r8 on the system I just tested.

 

I've also ruled out that it's nothing to do with copy protection, because I'm using a CD that I made that of course is without copy-protection. My CentOS install I'll have to check when I get home. The only fundamental differences between them, is CentOS is a 2.6.18.x kernel, whereas Gentoo/Mandriva are 2.6.24.x kernels.

Link to comment
Share on other sites

Thanks, actually I just tested it under MDV 2008.1 with a manufactured (not CD-R) CD-ROM (a Logitech driver CD) and I did not get any errors!

 

The CD-Rs I tried before are all single session and finalised (and they can be dd'ed or cat'ed fine under Mandrake 9.2) so this still doesn't change that there is something not working as it should.

Link to comment
Share on other sites

Can also confirm in CentOS that the CD I made also doesn't want to dd/cat either. It could therefore only be due to the media as I also saw that dd type command prefers media to be very clean and readable. That said, the CD is clean, but maybe because it's not good quality media eg: cheap.

 

I don't know any other reason why. I have used dd successfully in the past when creating an ISO from an original CD that I wanted to use in VMware.

Link to comment
Share on other sites

Thanks, I would exclude that it's a bad/cheap/dirty media issue as the sames CDs I tried don't give any errors in Mandrake 9.2.

 

I'm convinced something has changed in the 2.6 kernel that breaks reading the /dev/hdx device of a CD-R directly, the apps like Brasero (which you tried) or K3b (I tried this one with 2008.1, it reads the CDs that dd/cat don't like, without errors) must use a different technique to read CDs, that's why they don't have problems.

Link to comment
Share on other sites

Here's a procedure using the command line that works for me using mdv2008.1:

 

1. Insert the cd you want to make an iso of but do not mount the cd drive when the window pops up. Just hit the cancell button;

 

2. Run:

# isoinfo -d -i /dev/hdd

In the output note the blocksize(should be 2048) and the volume size which will depend on the amount of data on the cd;

 

3. Using the above information run:

# dd if=/dev/hdd of=my.iso bs=2048 count=<volume size> conv=notrunc,noerror

 

If that doesn't help, then I would suspect that this is a kernel problem with your particular hardware, in particular with the way the ide controller is being handled. I note that your cd drive is designated hdd whereas both my sata and ide optical drives are designated sr0 and sr1 respectively. That would indicate to me that a different driver module is being used for your ide controller.

Link to comment
Share on other sites

No that doesn't work for me. If I do that, I get loads of these:

 

dd: reading `/dev/sr0': Input/output error
376+0 records in
376+0 records out
770048 bytes (770 kB) copied, 3.75001 s, 205 kB/s
dd: reading `/dev/sr0': Input/output error
376+0 records in
376+0 records out
770048 bytes (770 kB) copied, 3.75286 s, 205 kB/s
dd: reading `/dev/sr0': Input/output error
376+0 records in
376+0 records out
770048 bytes (770 kB) copied, 3.75575 s, 205 kB/s
dd: reading `/dev/sr0': Input/output error
376+0 records in
376+0 records out
770048 bytes (770 kB) copied, 3.75954 s, 205 kB/s
dd: reading `/dev/sr0': Input/output error
376+0 records in
376+0 records out
770048 bytes (770 kB) copied, 3.76226 s, 205 kB/s
dd: reading `/dev/sr0': Input/output error
376+0 records in
376+0 records out

 

continually being shown on the screen. Info from the first command:

 

CD-ROM is in ISO 9660 format
System id: LINUX
Volume id: aar81xx
Volume set id: 
Publisher id: 
Data preparer id: 
Application id: K3B THE CD KREATOR (C) 1998-2005 SEBASTIAN TRUEG AND THE K3B TEAM
Copyright File id: 
Abstract File id: 
Bibliographic File id: 
Volume set size is: 1
Volume set sequence number is: 1
Logical block size is: 2048
Volume size is: 403
Joliet with UCS level 3 found
Rock Ridge signatures version 1 found

 

so I know I got the block and volume size correct. If I try without those conv parameters, it's just like it is normally listing the original error as posted here by the original poster.

Link to comment
Share on other sites

Join the conversation

You can post now and register later. If you have an account, sign in now to post with your account.
Note: Your post will require moderator approval before it will be visible.

Guest
Reply to this topic...

×   Pasted as rich text.   Paste as plain text instead

  Only 75 emoji are allowed.

×   Your link has been automatically embedded.   Display as a link instead

×   Your previous content has been restored.   Clear editor

×   You cannot paste images directly. Upload or insert images from URL.

Loading...
 Share

×
×
  • Create New...