David
--
David Morrison
PO Box 105, Cardiff, NSW 2285, Australia
David_Morrison at internode.on.net
Ph +61 2 49546164
IT Consulting and Support
___
Bug-ddrescue mailing list
Bug-ddrescue@gnu.org
http://lists.gnu.org/mailman/listinfo/bug-ddrescue
uick
recovery of the good parts of the disk?
2. Is there a file or debug mode that says what it is doing at any
given time? (The log file seems to give an end summary of what has
happened, rather than an indication of what ddrescue is doing at any
given time.)
Thanks
David
--
David Mor
s too strange. Apart from
anything else, it would have been useful to know which blocks on the
disk were truly bad, so as to be able to identify whether specific
files had been damaged.
Thanks
David
--
David Morrison
PO Box 105, Cardiff, NSW 2285, Australia
David_Morrison at internode.on.net
Ph
I have a failing 1TB disk and have been using ddrescue to copy it to
another disk so I can recover the files. I am copying the whole disk
as it has several partitions (out of a NAS box so using ext3
filesystems). I am doing this on OS X. Both disks are connected by
USB directly to the ports on
At 17:47 +0200 18/10/16, Antonio Diaz Diaz wrote:
Hello,
David Morrison wrote:
So instead of getting non-split and bad sectors, I am getting
non-trimmed failures. I am unsure what this means, other than that I
have another 55 hours to go when I thought I had only about 8. :-(
It may be
\In fact, no -- while I am not The Man, it seems to me that at that point,
you have to worry about the *internals* of the filesystem, since the block
offsets are going to change, and the inodes must then also change.
It would seem to boost the complexity a *lot*, from my viewpoint.
I agree. I w
Hello
I am trying to copy a 500GB disk from an iMac that was damaged by a
lightning strike. I have it in a USB case connected to an iMac
running OS X 10.6 (Snow Leopard). (It is my disk recovery machine
which has all the tools set up and ready to go.) ddrescue is 1.23
It has been running for
0 0 [ 0 - 0] unused
4: 000 0 0 -0 0 0 [ 0 - 0] unused
The size looks right, and there should be three partitions. But it
looks like the partition table is damaged.
- Original Message - From: "David Morrison"
To:
Sen
I have a disk recovery under way. I used this command on a Mac:
sudo ddrescue -f -r3 /dev/disk2 /dev/disk1
However, I forgot to put a mapfile name. So, a few questions:
1. Where is the mapfile being written? Can I recover it?
2. Since mapfile is an essential argument to the command, could it b
At 17:19 -0500 14/2/19, Robert Trevellyan wrote:
Unfortunately, if you did not specify a mapfile, then there is no mapfile
being written, and if you have to quit ddrescue it will start over from
scratch.
Are there any circumstances when you would not want a mapfile
created? It just seems that
Hello, David!
>> 3. If I need to interrupt a ddrescue run, is it ok to CTRL/C it,
then start running it again later, assuming there is actually
a mapfile somewhere?
I think the mapfile is only in the memory of the ddrescue process,
so try dumping it from /proc
Maybe, Antonio, the author, can h
At 4:00 +0300 15/2/19, äÓÒÚËÌ ÑÏËÚËÈ wrote:
- Original Message -
From: "David Morrison"
I wonder if putting it to sleep would help, as that saves a copy of
memory for the restore?
Surely, hibernated system saves all the memory in a file.
That was very useful in Windo
One of the things I struggle with is knowing where ddrescue is up to.
The display shows quite a lot of information in the initial scan
(ipos/opos go up), and even in the first attempt to scrape the bad
blocks from the first pass (non-scraped counts down to zero, read
errors and bad areas go up)
At 11:18 +1000 15/2/19, Robert Backhaus wrote:
If the disk you are writing too was blank before you started - i.e. it was
either new or had been filled with zeros - you can use -G (--generate-mode)
to create an approximate mapfile.
ddrescue --generate-mode infile outfile mapfile
It will read th
I have a disk recovery under way. I used this command on a Mac:
sudo ddrescue -f -r3 /dev/disk2 /dev/disk1
However, I forgot to put a mapfile name. So, a few questions:
1. Where is the mapfile being written? Can I recover it?
2. Since mapfile is an essential argument to the command, could it
At 13:54 +0100 15/2/19, Antonio Diaz Diaz wrote:
Hi David,
David Morrison wrote:
I discovered this in the manual:
8 Saving the mapfile in case of trouble
Unfortunately, if you did not specify a mapfile, then there is
nothing that can be currently done to get a mapfile except
extracting it
One of the things I struggle with is knowing where ddrescue is up
to. The display shows quite a lot of information in the initial scan
(ipos/opos go up), and even in the first attempt to scrape the bad
blocks from the first pass (non-scraped counts down to zero, read
errors and bad areas go up)
Hello David!
This is expected behavior, when ddrescue can't figure out the input
file's size in advance.
The behavior is normal on macOS, because ddrescue being (mostly)
strictly POSIX figures the size of the drive by using lseek( input,
0, SEEK_END ), which unfortunately returns zero for both
Oh dear.
I started copying a disk to another disk. After a minute or so, I
realised I had forgotten an argument so hit CTRL/C to stop ddrescue.
A kernel panic occurred.
I shut down the machine and restarted it. Halfway through the boot
process, another kernel panic.
I removed the disk
Any suggestions to recover the disk? This is Mac OS 10.6 on a Mac
Pro. Would other operating systems be able to cope with this, maybe
reformat it?
Windows was able to format it. OS X must be fussy.
Thanks
David
___
Bug-ddrescue mailing list
Bug-ddr
Just as a data point in copying speed, I copied a 1TB disk twice on a
Mac Pro with the disks internal to the case.
With -c 128 and block devices (/dev/disk), transfer speed was 37MB/sec.
With -c 256 and raw devices (/dev/rdisk), transfer speed was 110MB/sec.
So definitely worth it to cut copy
I have been given a WD Thunderbolt Duo device which has intermittent
problems. From what I can see, it connects two SATA disks (3TB each)
to a Mac using Thunderbolt.
However, OS X allows multiple disks connected to a Mac to be set up
using software RAID. The owner was told this one had been se
I am just copying a disk with a number of bad blocks near the end.
Initially, the Remaining time estimate was 9 hours, but once it hit
the bad block, the estimate is all over the place, from 1 hour to 15
days. I guess it is based on an average of how much has been
transferred in the last x seco
https://twocanoes.com/winclone-image-compatibility-with-512-and-4k-block/
I came across this article which describes some in-depth behaviour of
disks, and how it has changed in 2015 and later Macs. The same may
well apply to other operating systems. I wonder if this will affect
how ddrescue op
Due to a silly accident with a disk, I have had to resetup my disk
recovery machine, meaning reinstalling everything including ddrescue.
It has been a complicated process, but more on that later.
The uncompressing, configure and make were successful, but make
check failed as shown below. I ma
I did use unix a fair bit 40 years ago, but now I hardly ever have to
use the command line. This means that when I do, I have to go through
and work out what I need to do. Memory is not as good as it once was.
:-(
So when I had to reinstall my disk recovery machine, I struggled. I
suspect man
I was not aware there was a precompiled version of lzip. Is this for all
platforms?
I think so. A version for Mac can be found at
http://pdb.finkproject.org/pdb/package.php/lzip
A bit limited. You have to install the Fink installation system. They
also only offer a limited range of installat
Having just been given my first SSD to recover, I wondered whether
ddrescue uses any different techniques than it would use for a
magnetic disk?
For example, on a magnetic disk, ddrescue skips forward whenever it
strikes an error to avoid further damage to the disk surface and/or
heads which
Most of the time I can just run ddrescue and it copies the disk or
partition which I then can work on. Just occasionally, I have to get
into the nitty-gritty and try to recover bits of the disk. At that
point, I have to go and read the manual to refresh my memory.
One of the things I struggle
At 1:27 +0200 29/4/21, Radomir Tomis wrote:
The free space on the drive holding the mapfile was only ~44 kB (copying 1
TB *disk device* to 1 TB *file system*, you know ...), the mapfile itself
was ~134 kB.
But there was no "Error writing mapfile 'mapfile': No space left on device"
Disk recovery
A friend bought a WD Elements 2TB external portable disk, ie, USB powered. It
worked ok for a day or two, then she could not get some files off it. She asked
me to help.
When I first plugged it in, it would mount. However, trying to copy files off
it would start, and sometimes copy some files.
data which are only on this disk, I
suggest that you open the USB enclosure and connect the disk directly to the
computer. The USB controllers are usually not the best to handle defective
disks.
Cheers,
Adrien
Le ven. 25 août 2023 à 10:56, David Morrison a
écrit :
A friend bought a WD
I have just been installing ddrescue on MacOS on M1 Mac.
The documentation says:
/5. Type 'make install' to install the programs and any data files and//
// documentation.//
//
// Or type 'make install-compress', which additionally compresses the//
// info manual and the man pages after in
33 matches
Mail list logo
