🚀 go-pugleaf

In news:ceo4b9$7cc$1@spacebar.ucc.usyd.edu.au, D. Phan bitched and
moaned:
> hello there
>
> My old hard drive in which is running slackware 10.0 is now so noisy
> with high frequency. I now wanna move whole contents in the old to a
> new harddisk. Please tell me your experience about that
> much appreciated,
> regards
> d.phan
> my system: slackware 10 (ker-2.4.26/cpu 450mhz - 128MB ram) with no X
> and X apps, and managed by puTTY (ssh) from XP clients

1) cpio the entire drive to the new one.  Make sure the layout is the same,
if /dev/Xa1 is the swap on the old drive, then it is the same on the new.
2) Boot up either by bootdisk or through the CD with the new drive on the
same channel as the old
3) Mount the slice, and use chroot to set it to the root slice
4) Run lilo

You may need to edit your fstab if you add or remove mount points and
slices.

That should be enough though.

>> My old hard drive in which is running slackware 10.0 is now so noisy
>> with high frequency. I now wanna move whole contents in the old to a
>> new harddisk. Please tell me your experience about that
>> much appreciated,

First, excellent idea to move your data. If it sounds bad, there is a high 
likelihood of impending failure!

> 1) cpio the entire drive to the new one.  Make sure the layout is the
> same, if /dev/Xa1 is the swap on the old drive, then it is the same on
> the new. 2) Boot up either by bootdisk or through the CD with the new
> drive on the same channel as the old
> 3) Mount the slice, and use chroot to set it to the root slice
> 4) Run lilo
> 
> You may need to edit your fstab if you add or remove mount points and
> slices.

I would reiterate, make sure the physical layout looks the same after the 
data transfer. i.e. hda should be replaced by hda (not hdb).

This also makes me wonder, because I have considered using LVM (Logical 
Volume Management, for several physical disks)... am I correct in my 
understanding that under LVM, the provided tools can be used to move the 
data off the existing physical disk, and then back on to a new disk without 
risking corruption in the process?

-- 
Jem Berkes
http://www.sysdesign.ca/

D. Phan wrote :

>  I now wanna move whole contents in the old to a new harddisk.

Theres a howto that covers this issue here:
/usr/doc/Linux-HOWTOs/Hard-Disk-Upgrade
-- 
Thomas O.

This area is designed to become quite warm during normal operation.

On Tue, 3 Aug 2004, D. Phan wrote:
> My old hard drive in which is running slackware 10.0 is now so noisy
> with high frequency. I now wanna move whole contents in the old to a new
> harddisk. Please tell me your experience about that
> much appreciated,


i assume box has one old drive, hda;
i assume box has cabling to attach two drives;
i assume you have bootable floppy or cdrom ready.
test boot it to be certain.


(1) shutdown.  add the new drive into the box.
cable and jumper as needed.  for example i will call it hdb.
don't change anything else.

(2) reboot. use dmesg to verify that linux sees the new drive.

(3) fdisk, mkfs and mkswap on new drive as desired.
new partitioning scheme should resemble old scheme, but does
not need to be identical.  order of partitions should not be
altered (so as to keep procedure simple).
for example, if old drive has:
	hda1 as 256MB swap
	hda2 as 2GB /
	hda3 as 2GB /tmp
	hda4 as extended
	hda5 as 14GB /home
then new drive might have:
	hdb1 as 512MB swap
	hdb2 as 4GB /
	hdb3 as 4GB /tmp
	hdb4 as extended
	hdb5 as 32GB /home
if adding a larger drive, and uncertain about partitioning schemes,
then just leave additional space unused.  it can be added in later.

(4) mdir new mountpoints and mount partitions as needed.
for example:
	mkdir /mnt/hdb2
	mount /dev/hdb2 /mnt/hdb2
	mkdir /mnt/hdb3
	mount /dev/hdb3 /mnt/hdb3
	mkdir /mnt/hdb5
	mount /dev/hdb5 /mnt/hdb5

(5) use tar to copy live data from old mountpoints to new mountpoints.
for example:

	OLDMNT=/
	NEWMNT=hdb2
	cd ${OLDMNT}
	tar --one-file-system -cpvf - . | ( cd ${NEWMNT} ; tar -xpf - )

repeat as needed (eg., /tmp and hdb3, /home and hdb5, ...)
you can switch to another console and check progress using 'df'.


(6) shutdown.  disconnect old drive.  cable and jumper new drive
as hda.  save old drive until system is verified running new drive.
if procedure fails then system can be restored by replacing new
drive with old drive.


(7) say prayers.  boot from floppy or cdrom.
use lilo bootprompt to mount filesystem from new drive.
for example:
	boot: mount root=/dev/hda2

(8) run lilo to make new drive bootable.

(9) shutdown, remove cd or floppy, reboot using new drive.
verify everything is working.
fill new drive up with lots of new stuff until full.
buy bigger drive.
goto (1).









-- 
Fire the Liars - Impeach Bush and Cheney!
Prosecute the criminals - Indict Rumsfeld and Ashcroft!
Corruption starts at the top.

William Hunt, Portland Oregon USA

William Hunt wrote:

>verify everything is working.
>fill new drive up with lots of new stuff until full.
>buy bigger drive.
>goto (1).
>  
>
:-D

Should be published as Mini-HOWTO for *every* OS.

Having fun

Stanislaw
Slack user from Ulladulla.

In news:Pine.LNX.4.58.0408031001140.11811@worker.huntbros.net, William
Hunt bitched and moaned:
> (5) use tar to copy live data from old mountpoints to new mountpoints.
> for example:
>
> OLDMNT=/
> NEWMNT=hdb2
> cd ${OLDMNT}
> tar --one-file-system -cpvf - . | ( cd ${NEWMNT} ; tar -xpf - )

`tar` does not recreate /dev properly, the last time I looked.

|> tar --one-file-system -cpvf - . | ( cd ${NEWMNT} ; tar -xpf - )
|
|`tar` does not recreate /dev properly, the last time I looked.

GNU tar does. I've done complete network transfers of disk contents
using tar and netcat.
-- 

> GNU tar does. I've done complete network transfers of disk contents
> using tar and netcat.

Aren't there also some other things that could be happening with /proc and 
/dev, like dynamic content creation? I can't remember the details but I 
thought I'd throw that out there.

-- 
Jem Berkes
http://www.sysdesign.ca/

In news:Xns953AD15B1D605jbuserspc9org@205.200.16.73, Jem Berkes bitched
and moaned:
>> GNU tar does. I've done complete network transfers of disk contents
>> using tar and netcat.
>
> Aren't there also some other things that could be happening with
> /proc and /dev, like dynamic content creation? I can't remember the
> details but I thought I'd throw that out there.

tar cannot read the entire /proc tree, but that is mostly the pid's

|> GNU tar does. I've done complete network transfers of disk contents
|> using tar and netcat.
|
|Aren't there also some other things that could be happening with /proc and 
|/dev, like dynamic content creation? I can't remember the details but I 
|thought I'd throw that out there.

I normally exclude /proc from the tar since its contents are virtual.
/dev is ok to tar, GNU tar knows what to do with device files.
-- 

Jem Berkes wrote:

> Aren't there also some other things that could be happening with /proc
> and /dev, like dynamic content creation? I can't remember the details
> but I thought I'd throw that out there.

With /proc, just creating the directory should be sufficient since it's
dynamically created and altered as Linux runs.  /dev can change,
however unless udev is being used, the individual devices can be copied
and used quite easily.

D. Phan wrote:
> hello there
> 
> My old hard drive in which is running slackware 10.0 is now so noisy 
> with high frequency. I now wanna move whole contents in the old to a new 
> harddisk. Please tell me your experience about that
> much appreciated,
> regards
> d.phan
> my system: slackware 10 (ker-2.4.26/cpu 450mhz - 128MB ram) with no X 
> and X apps, and managed by puTTY (ssh) from XP clients
Thanks for all information and help
this weekends would be relaxed right at the box to move data to the new one.
cheers

On Wed, 4 Aug 2004 qyswmhk@ojdmyw.com wrote:

> |> GNU tar does. I've done complete network transfers of disk contents
> |> using tar and netcat.
> |
> |Aren't there also some other things that could be happening with /proc and
> |/dev, like dynamic content creation? I can't remember the details but I
> |thought I'd throw that out there.
>
> I normally exclude /proc from the tar since its contents are virtual.
> /dev is ok to tar, GNU tar knows what to do with device files.


/proc is a seperate filesystem.  if you give tar the --one-file-system,
it will be excluded.  tarring it up is kind of pointless anyway, since
only a snapshot of it's outputs is preserved, and restoring it does not
producce a functional proc filesystem.

note, just for giggles, that you can mount a proc filesystem anywhere.
eg., mkdir /tmp/foo && mount -t proc none /tmp/foo.

but above /dev, i just did a fast test, tar -cpf /tmp/dev.tgz /dev/,
and tar did bitch about socket /dev/log ... not sure if that's a
problem or not.  but i've never notied any negative results from
using the technique in practice.





-- 
Fire the Liars - Impeach Bush and Cheney!
Prosecute the criminals - Indict Rumsfeld and Ashcroft!
Corruption starts at the top.

William Hunt, Portland Oregon USA

On Tue, 3 Aug 2004, Stanislaw Flatto wrote:
> William Hunt wrote:
>
>> verify everything is working.
>> fill new drive up with lots of new stuff until full.
>> buy bigger drive.
>> goto (1).
>>
>>
> :-D
>
> Should be published as Mini-HOWTO for *every* OS.
> Having fun
> Stanislaw
> Slack user from Ulladulla.

but of course - what is the point of newer, bigger, and
faster if not to fill it up, tear it up, and wear it out ?



>

-- 
Fire the Liars - Impeach Bush and Cheney!
Prosecute the criminals - Indict Rumsfeld and Ashcroft!
Corruption starts at the top.

William Hunt, Portland Oregon USA

|> I normally exclude /proc from the tar since its contents are virtual.
|> /dev is ok to tar, GNU tar knows what to do with device files.
|
|but above /dev, i just did a fast test, tar -cpf /tmp/dev.tgz /dev/,
|and tar did bitch about socket /dev/log ... not sure if that's a
|problem or not.  but i've never notied any negative results from
|using the technique in practice.

Yes, that's the other little detail, tar doesn't grab Unix sockets but
that's ok since those will be created by the app that needs them on the
other side.
--