Date: Wed, 19 Oct 2005 15:45:47 -0700 From: "Gayn Winters" <gayn.winters@bristolsystems.com> To: "'Ramakrishna Nalla'" <nallark@gmail.com>, "'Bob Ababurko'" <ababurko@adelphia.net> Cc: freebsd-questions@freebsd.org, 'Craig Deal' <craig@advantagecomputer.biz> Subject: RE: Replacing a failing HD Message-ID: <015401c5d4fe$f49bcc80$c901a8c0@workdog> In-Reply-To: <14f2d8380510182152j29088e0ake14df20f61154fff@mail.gmail.com>
next in thread | previous in thread | raw e-mail | index | archive | help
> -----Original Message----- > From: owner-freebsd-questions@freebsd.org > [mailto:owner-freebsd-questions@freebsd.org] On Behalf Of > Ramakrishna Nalla > Sent: Tuesday, October 18, 2005 9:52 PM > To: Bob Ababurko > Cc: freebsd-questions@freebsd.org; Craig Deal > Subject: Re: Replacing a failing HD > > > But, won't doing a dd between two disks with incompatible > sizes create a bad partition table on the destination drive? > > TIA, > Rama > Not really a "bad" partition table, if what you mean is bad=corrupted. Using dd you copy blocks, and this will correctly bring the partition table along. What you do not get initially is the full utilization of the larger drive. Thus if you dd a 40GB drive (or slice) to a 60GB one, you'll only get the image of the 40GB drive that is initially usable. You will have 20GB that is not - at least initially - usable. Nothing stops you from reorganizing the larger disk, however. I think the original problem in this thread was a quick save of a failing disk. dd is great for this. If you were simply going to utilize a larger disk, then you'd be better off using fdisk to slice it up, creating your bsd partitions and then using dump|restore to get things where you want them. I think the Handbook has a nice section on doing this. -gayn
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?015401c5d4fe$f49bcc80$c901a8c0>