Re: [Bug-ddrescue] partition size for ddrescue direct to device

[peter]

hi again ariel

thank you so much for your help. when somethign terrible happens it is always
nice to get free answers and so quick! i understand if you can't keep
responding to my Qs...

mac os x is pretty good about being able to build std linux tools. there's even
a lot of stuff ported (see http://fink.sourceforge.net/pdb/) i have pretty good
debian linux experience and mac os x too but this is my first HD failure and i
am not good with disk stuff, stupidly...

now i am seeing i failed to copy the whole device.. i missed the partition
table?

kidstuff-10-3:/usr/sbin peter$ diskutil list

/dev/disk0
   #:                   type name               size      identifier
   0: Apple_partition_scheme                    *74.5 GB  disk0
   1:    Apple_partition_map                    31.5 KB   disk0s1
   2:              Apple_HFS kidstuff           74.4 GB   disk0s3
/dev/disk2
   #:                   type name               size      identifier
   0: Apple_partition_scheme                    *232.9 GB disk2
   1:    Apple_partition_map                    31.5 KB   disk2s1
   2:         Apple_Driver43                    28.0 KB   disk2s2
   3:         Apple_Driver43                    28.0 KB   disk2s3
   4:       Apple_Driver_ATA                    28.0 KB   disk2s4
   5:       Apple_Driver_ATA                    28.0 KB   disk2s5
   6:         Apple_FWDriver                    256.0 KB  disk2s6
   7:     Apple_Driver_IOKit                    256.0 KB  disk2s7
   8:          Apple_Patches                    256.0 KB  disk2s8
   9:              Apple_HFS System             77.5 GB   disk2s10
  10:              Apple_HFS kidsafe            77.5 GB   disk2s12
  11:              Apple_HFS Media2             77.5 GB   disk2s14

i am copying disk0s3 -> disk2s12

should i have copied disk0 -> a new drive with no pre-existing partition table?

nuts.. i wish i just made an image.

maybe i will try to insert a new disk, partition it with exactly the same setup
as disk0, then...

dd if=/dev/disk0s1 of=/dev/disk3s1
dd if=/dev/disk2s12 /dev/disk3s2

if i understand what you're saying i can use dd to copy data off disk0s3 while
ddrescue is currently running?

-peter

Quoting Ariel <address@hidden>:

>
> On Fri, 23 Sep 2005 address@hidden wrote:
>
> > thanks so much for the info. the partition type is apple HFS and the
> filesystem
> > is "mac os extended (journaled)"
>
> Hmm, don't know much about this fs.
>
> > i do have another firewire 800 drive ready to go so i can just parititon it
> > smaller and copy the data straight off the current target. can you tell me
> some
> > commands to do this or a place to look? i have searched google ...
>
> If this was linux I could help you, but I don't know the commands on macs.
>
> Basically partition the new drive to EXACTLY (to the byte, or sector) the
> same size as the old one.
>
> First you need to find out the old size, second how to create a new
> partition to match it. (Probably the same partition tool will do both, but
> only if it reports data on partition sizes exactly - some tools round it
> to the nearest MB.) It's called cfdisk on linux.
>
> Then copy the data from the first drive to the second. When it fills the
> new drive it will complain that it is out of space (because the source is
> larger), but don't worry about that. If the new partition is exactly the
> same size as the old, it will have copied everything.
>
> I don't even know what tool to use for the copying. I'd use dd with a
> large bs (blocksize, the default one will take forever) on linux. Plain
> old cp should work fine.
>
> > at this point ddrescue has slowed to a crawl and pulls mostly junk... it
> should
> > be done any time now, the drive was 80gb and its at 76-something
>
> 31MB to go. (80000000000 bytes = 76293MB).
>
>       -Ariel
>
> PS. Do not delete the temporary partition until you have finished the
> recovery using your firewire 800 drive. You may find that a critical block
> is missing and the recovery found nothing, or other possibilities. So save
> the recovered version untouched, while you work on a copy of it.
>
> PPS. You can copy the data now (while ddrescue is running) and do a
> recovery on the firewire 800 drive to see what you get (help you decide if
> to let ddrescue keep working or not).
>
> Sorry I can't help more then this.
>
>