Date: Mon, 12 Aug 2002 11:01:09 -0700 From: richard childers <fscked@pacbell.net> To: pg@eth1.com Cc: freebsd-mobile@freebsd.org Subject: Re: dumping entire ide laptop disk Message-ID: <3D57F7E5.CB6B1834@pacbell.net> References: <20020812165411.9052.qmail@web9702.mail.yahoo.com>
next in thread | previous in thread | raw e-mail | index | archive | help
Peter Gatsoulis writes:
"i remove the drives and mount them in a desktop by
using a 2.5"-3.5" IDE adapter, the desktop boots fine
and reckognizes the new drive as ad3
"i now try;
dump 0f - /dev/ad3 |bzip2 -c>/somemountpoint/somefile
"i get, "bad sblock magic number" and entire dump
aborts."
I would try to mount the filesystem and run 'fsck -p' on it first before
I would dump it. This would insure that you had the correct device name,
if you were able to fsck or mount the filesystem.
That having been said, note that the first example you cite refers to a
"/", IE, dump(8) infers the device name from the mount point. If it is
not mounted, you need to supply the correct device explicitly, and
"/dev/ad3" is insufficient.
In the past when I have had to recover trashed UNIX boxes where the
/etc/fstab has been lost or mangled, I have found it useful to do
something like:
# /bin/csh
# foreach dev ( `ls /dev/*sd*` )
? echo "${dev}"
? echo ""
? fsck -n ${dev}
? echo ""
end
... and in this way, one can quickly identify which /dev entries
correspond to file systems (and perhaps even learn where they were last
mounted :-).
Hope this helps.
-- richard
c/o Peter Gatsoulis wrote:
> hello & pls Help .?
>
> In the past w/ help from this list's members the
> following has worked GREAT:
> (using FBSD 4.5 but works w/ all FBSD versions)
>
> dump -0 -f - /|bzip2 -c>/mnt/where-ever/foo.dump
>
> used this continuosly to backup filesystems, but NOW i
> have some laptop drives w/ mixed fs, ie: 1st partition
> can be MS DOS, 2nd partition can be NTFS, 3rd
> partition can be ufs w/ softupdates.
>
> i remove the drives and mount them in a desktop by
> using a 2.5"-3.5" IDE adapter, the desktop boots fine
> and reckognizes the new drive as ad3
>
> i now try;
> dump 0f - /dev/ad3 |bzip2 -c>/somemountpoint/somefile
>
> i get, "bad sblock magic number" and entire dump
> aborts.
>
> reading the FBSD handbook, dump manpage and searching
> the archives leads me to believe that dump can indeed
> backup entire disks, irrespective of which fs is on
> disk???
>
> i've tried specifying ad3s1, ad3s1a, rad3s1e etc, many
> variations of specifying device name BUT same
> results..
>
> how can i use dump to "snap" the entire disk image?
> don't want to use dd in case i have to restore to
> another diffrent laptop & drive ...
>
> __________________________________________________
> Do You Yahoo!?
> HotJobs - Search Thousands of New Jobs
> http://www.hotjobs.com
>
> To Unsubscribe: send mail to majordomo@FreeBSD.org
> with "unsubscribe freebsd-mobile" in the body of the message
--
Richard A Childers/KG6HAC -- Senor UNIX System & Network Administrator
"Dont forget nothing." Maj Rogers, standing orders, 1st Ranger Bn, 1759
To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-mobile" in the body of the message
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?3D57F7E5.CB6B1834>