Recovering data from duff CDROM ?
in [Linux Help]
|
Prev: Xubuntu 9.10
Next: Peice of Linux Os...
From: bb on 4 Nov 2009 07:58 On 2009-11-04 12:14, Mike Jones wrote: > #-> dd if=/dev/hda of=/tmp/disk.out > dd: reading `/dev/hda': Input/output error > 0+0 records in > 0+0 records out > 0 bytes (0 B) copied, 1.39585 s, 0.0 kB/s > > ...is about as far as I've got with this disk. > That looks bad, just as the cdrom never load properly. If you have cdrdao installed you should get some good info with the command cdrdao disk-info I did the same test that you did with my rescue CD, and the result was: # dd if=/dev/cdrom of=/tmp/rescuecd.iso 332752+0 records in 332752+0 records out 170369024 bytes (170 MB) copied, 55.2196 s, 3.1 MB/s # mkdir /x # mount -o loop,ro /tmp/rescuecd.iso /x # ls -l /x total 130510 drwxr-xr-x 2 root root 2048 2007-11-25 19:04 bootdisk drwxr-xr-x 3 root root 4096 2007-11-30 19:51 isolinux drwxr-xr-x 2 root root 2048 2007-11-20 22:07 syslinux -rw-rw-rw- 1 root root 133632000 2007-11-25 19:12 sysrcd.dat -rw-r--r-- 1 root root 45 2007-11-25 19:12 sysrcd.md5 -rw-r--r-- 1 root root 876 2007-11-16 09:28 usbstick.htm # umount /x So that is what you should expect, but try with ddrescue instead. /bb
From: Doug Mitton on 4 Nov 2009 08:39 Pascal Hambourg <boite-a-spam(a)plouf.fr.eu.org> wrote: >Doug Mitton a �crit : >> >>>> http://users.elis.ugent.be/~mronsse/cdfs/ >> >> I use it to recover data from a muti-session data >> disk that has had a newer session write "junk" over a previous "good" >> session. > >Isn't it overkill for this purpose ? You can select the session number >in the mount options when mounting a multisession CD-ROM the usual way. Yes, it may well be overkill BUT when I did a search on the "problem", that was one of the solutions. It kept me entertained for awhile and actually worked. -- ------------------------------------------------- http://www3.sympatico.ca/dmitton SPAM Reduction: Remove ".invalid" from my domain. -------------------------------------------------
From: Mike Jones on 4 Nov 2009 16:39 Responding to Doug Mitton: > Pascal Hambourg <boite-a-spam(a)plouf.fr.eu.org> wrote: > >>Doug Mitton a écrit : >>> >>>>> http://users.elis.ugent.be/~mronsse/cdfs/ >>> >>> I use it to recover data from a muti-session data disk that has had a >>> newer session write "junk" over a previous "good" session. >> >>Isn't it overkill for this purpose ? You can select the session number >>in the mount options when mounting a multisession CD-ROM the usual way. > > Yes, it may well be overkill BUT when I did a search on the "problem", > that was one of the solutions. It kept me entertained for awhile and > actually worked. My problem is that I can't get anything to read the disk. mount -t iso9660 -o ro /dev/hda /mnt/tmp mount -t ext2 -o ro /dev/hda /mnt/tmp mount -t auto -o ro /dev/hda /mnt/tmp ....all bomb out with errors. From /var/log/syslog Nov 4 11:12:50 NAME kernel: hda: command error: status=0x51 { DriveReady SeekComplete Error } Nov 4 11:12:50 NAME kernel: hda: command error: error=0x51 { IllegalLengthIndication LastFailedSense=0x05 } Nov 4 11:12:50 NAME kernel: ide: failed opcode was: unknown Nov 4 11:12:50 NAME kernel: ATAPI device hda: Nov 4 11:12:50 NAME kernel: Error: Illegal request -- (Sense key=0x05) Nov 4 11:12:50 NAME kernel: Illegal mode for this track or incompatible medium -- (asc=0x64, ascq=0x00) Nov 4 11:12:50 NAME kernel: The failed "Read 10" packet command was: Nov 4 11:12:50 NAME kernel: "28 00 00 00 00 00 00 00 08 00 00 00 00 00 00 00 " Nov 4 11:12:50 NAME kernel: end_request: I/O error, dev hda, sector 0 Nov 4 11:12:50 NAME kernel: Buffer I/O error on device hda, logical block 0 Nov 4 11:12:50 NAME kernel: Buffer I/O error on device hda, logical block 1 Nov 4 11:12:50 NAME kernel: Buffer I/O error on device hda, logical block 2 Nov 4 11:12:50 NAME kernel: Buffer I/O error on device hda, logical block 3 Nov 4 11:12:50 NAME kernel: Buffer I/O error on device hda, logical block 4 Nov 4 11:12:50 NAME kernel: Buffer I/O error on device hda, logical block 5 Nov 4 11:12:50 NAME kernel: Buffer I/O error on device hda, logical block 6 Nov 4 11:12:50 NAME kernel: Buffer I/O error on device hda, logical block 7 Nov 4 21:22:42 NAME kernel: hda: media error (bad sector): status=0x51 { DriveReady SeekComplete Error } Nov 4 21:22:42 NAME kernel: hda: media error (bad sector): error=0x30 { LastFailedSense=0x03 } Nov 4 21:22:42 NAME kernel: ide: failed opcode was: unknown Nov 4 21:22:42 NAME kernel: ATAPI device hda: Nov 4 21:22:42 NAME kernel: Error: Medium error -- (Sense key=0x03) Nov 4 21:22:42 NAME kernel: CIRC unrecovered error -- (asc=0x11, ascq=0x06) Nov 4 21:22:42 NAME kernel: The failed "Read 10" packet command was: Nov 4 21:22:42 NAME kernel: "28 00 00 00 00 10 00 00 01 00 00 00 00 00 00 00 " Nov 4 21:22:42 NAME kernel: end_request: I/O error, dev hda, sector 64 Nov 4 21:22:42 NAME kernel: isofs_fill_super: bread failed, dev=hda, iso_blknum=16, block=16 Nov 4 21:23:02 NAME kernel: hda: command error: status=0x51 { DriveReady SeekComplete Error } Nov 4 21:23:02 NAME kernel: hda: command error: error=0x51 { IllegalLengthIndication LastFailedSense=0x05 } Nov 4 21:23:02 NAME kernel: ide: failed opcode was: unknown Nov 4 21:23:02 NAME kernel: ATAPI device hda: Nov 4 21:23:02 NAME kernel: Error: Illegal request -- (Sense key=0x05) Nov 4 21:23:02 NAME kernel: Illegal mode for this track or incompatible medium -- (asc=0x64, ascq=0x00) Nov 4 21:23:02 NAME kernel: The failed "Read 10" packet command was: Nov 4 21:23:02 NAME kernel: "28 00 00 00 00 01 00 00 21 00 00 00 00 00 00 00 " Nov 4 21:23:02 NAME kernel: end_request: I/O error, dev hda, sector 4 Nov 4 21:23:02 NAME kernel: Buffer I/O error on device hda, logical block 1 Nov 4 21:23:02 NAME kernel: Buffer I/O error on device hda, logical block 2 Nov 4 21:23:02 NAME kernel: Buffer I/O error on device hda, logical block 3 Nov 4 21:23:02 NAME kernel: Buffer I/O error on device hda, logical block 4 Nov 4 21:23:02 NAME kernel: Buffer I/O error on device hda, logical block 5 Nov 4 21:23:02 NAME kernel: Buffer I/O error on device hda, logical block 6 Nov 4 21:23:02 NAME kernel: Buffer I/O error on device hda, logical block 7 Nov 4 21:23:02 NAME kernel: Buffer I/O error on device hda, logical block 8 Nov 4 21:23:02 NAME kernel: Buffer I/O error on device hda, logical block 9 Nov 4 21:23:02 NAME kernel: Buffer I/O error on device hda, logical block 10 Nov 4 21:23:03 NAME kernel: FAT: bogus number of reserved sectors Nov 4 21:23:03 NAME kernel: GFS2: Unrecognized block device or mount point /dev/hda Nov 4 21:23:03 NAME kernel: GFS2: gfs2 mount does not exist Nov 4 21:23:14 NAME kernel: VFS: Can't find an ext2 filesystem on dev hda. Nov 4 21:27:10 NAME kernel: FAT: bogus number of reserved sectors Nov 4 21:27:58 NAME kernel: hda: media error (bad sector): status=0x51 { DriveReady SeekComplete Error } Nov 4 21:27:58 NAME kernel: hda: media error (bad sector): error=0x30 { LastFailedSense=0x03 } Nov 4 21:27:58 NAME kernel: ide: failed opcode was: unknown Nov 4 21:27:58 NAME kernel: ATAPI device hda: Nov 4 21:27:58 NAME kernel: Error: Medium error -- (Sense key=0x03) Nov 4 21:27:58 NAME kernel: CIRC unrecovered error -- (asc=0x11, ascq=0x06) Nov 4 21:27:58 NAME kernel: The failed "Read 10" packet command was: Nov 4 21:27:58 NAME kernel: "28 00 00 00 00 10 00 00 01 00 00 00 00 00 00 00 " Nov 4 21:27:58 NAME kernel: end_request: I/O error, dev hda, sector 64 Nov 4 21:27:58 NAME kernel: isofs_fill_super: bread failed, dev=hda, iso_blknum=16, block=16 -- *===( http://www.400monkeys.com/God/ *===( http://principiadiscordia.com/ *===( http://www.slackware.com/
From: Vahis on 5 Nov 2009 02:33 On 2009-11-04, Mike Jones <Not(a)Arizona.Bay> wrote: > > My problem is that I can't get anything to read the disk. > > > mount -t iso9660 -o ro /dev/hda /mnt/tmp > > mount -t ext2 -o ro /dev/hda /mnt/tmp > > mount -t auto -o ro /dev/hda /mnt/tmp > > ...all bomb out with errors. > Why do you keep trying to mount it? It's been said before:_Don't_ mount it. Use ddrescue. Even better: Make it a raw device, that's helped me sometimes when ddrescue can't even read normal /dev, I've made it a raw device. You'll get whatever bits and bytes there are left to recover. Vahis -- "Sunrise 7:56am (EET), sunset 4:11pm (EET) at Espoo, Finland (8:15 hours daylight)" http://waxborg.servepics.com Linux 2.6.25.20-0.5-default #1 SMP 2009-08-14 01:48:11 +0200 x86_64 9:26am up 5 days 14:27, 12 users, load average: 0.10, 0.08, 0.08
From: jellybean stonerfish on 5 Nov 2009 09:43
On Thu, 05 Nov 2009 07:33:21 +0000, Vahis wrote: > On 2009-11-04, Mike Jones <Not(a)Arizona.Bay> wrote: >> >> My problem is that I can't get anything to read the disk. >> >> >> mount -t iso9660 -o ro /dev/hda /mnt/tmp >> >> mount -t ext2 -o ro /dev/hda /mnt/tmp >> >> mount -t auto -o ro /dev/hda /mnt/tmp >> >> ...all bomb out with errors. >> >> > Why do you keep trying to mount it? > > It's been said before:_Don't_ mount it. Use ddrescue. He says he hasn't tried ddrescue yet. Why, I don't know. > > Even better: Make it a raw device, that's helped me sometimes when > ddrescue can't even read normal /dev, I've made it a raw device. What do you mean by making it a raw device, and how do you do so? > > You'll get whatever bits and bytes there are left to recover. > > Vahis |