Sean Finney on Wed, 10 Jul 2002 11:40:20 -0400 |
On Wed, Jul 10, 2002 at 06:06:46AM -0400, dwild+plug@starforce.com wrote: > use /dev/hdd instead of /dev/hdd1 to make sure you get the entire disk > (you will end up with an unmountable full-disk image once the unmountable? it should be perfectly mountable using the loopback device, right? root# losetup /dev/loop0 filesystem.img root# mount /dev/loop0 /mnt ...(do stuff)... root# umount /dev/loop0 root# losetup -d /dev/loop0 > > I want to dd the entire hard drive (hdd not hdd1), not just the space > > containing a file system. And, mount is used to mount a 'file system' to a > > mount point on my machine. Wouldn't that make the free space not associated > > with a file system unreachable? If there is any? Do I have to mount the > > actual device (hdd) in order to use dd? If so, I can only mount hdd1 because > > that's the partition that contains the file system. I can't mount hdd (or > > can I?). Will dd image a device that isn't mounted to a file system on my > > machine? > > you don't need to mount anything to use dd ... dd works off the device and > doesn't need the kernel's filesystem support to work. yeah, and actually it could possibly mess stuff up if the filesystem is active and changing while you're in the middle of doing dd... hope you get your data--I'd be interested to hear what you use to get it back (because i've got my own fat32 filesystem image waiting for data recovery too... heh) --sean ______________________________________________________________________ Philadelphia Linux Users Group - http://www.phillylinux.org Announcements-http://lists.phillylinux.org/mail/listinfo/plug-announce General Discussion - http://lists.phillylinux.org/mail/listinfo/plug
|
|