ase.
> >
> > 1. Partition and format new 500GB SATA III drive. No LVM, RAID or
> > GPT. [Note i]
> >
> > 2. Is 'rsync -axH > destination partition>' sufficient to copy ALL files with
> > permissions, etc?
> >
> > 3. Move the old g
t; 2. Is 'rsync -axH partition>' sufficient to copy ALL files with permissions, etc?
>
> 3. Move the old grub.cfg out of the new /boot/grub/.
>
> 4. Ditto for old device.map.[Note ii]
>
> 5. Shutdown, remove old drive, reboot with LiveCD.
>
> 6. Chroot to new
/grub/.
4. Ditto for old device.map.[Note ii]
5. Shutdown, remove old drive, reboot with LiveCD.
6. Chroot to new drive / partition: chroot
7. Create new grub.cfg: 'grub-mkconfig -o /boot/grub/grub.cfg'
8. Install grub on new drive's MBR: 'grub-install '
9. Shutd
On 08/19/2011 06:39 AM, Scott Ferguson wrote:
On 19/08/11 19:34, Lisi wrote:
On Friday 19 August 2011 01:38:58 Scott Ferguson wrote:
For me the biggest problem is CD labels - my writing makes the reading
even harder. Now if someone created a simple system that announced the
title of any cd plac
On Friday 19 August 2011 11:34:01 Scott Ferguson wrote:
> > Vinux is virtually useless [snip] In fact, I
> > agree with you that it is unusable.
>
> I was over-dramatising - it has some uses:-
> ;drink coaster
> ;memory aid for recalling slavic words that end in hard consonants.
> ;decongestant (i
On 19/08/11 19:34, Lisi wrote:
> On Friday 19 August 2011 01:38:58 Scott Ferguson wrote:
>> For me the biggest problem is CD labels - my writing makes the reading
>> even harder. Now if someone created a simple system that announced the
>> title of any cd placed in the drive based on information bu
On 19/08/11 19:33, Lisi wrote:
> On Friday 19 August 2011 01:38:58 Scott Ferguson wrote:
>> But most of the recommendations I get are from sighted people ie.
>> Vinux is "supposed" to be good
>
> You will have noticed that I didn't mention it!
I did, the significance escaped me. Now I know better
On Friday 19 August 2011 01:38:58 Scott Ferguson wrote:
> For me the biggest problem is CD labels - my writing makes the reading
> even harder. Now if someone created a simple system that announced the
> title of any cd placed in the drive based on information burned to the
> CD
Can you read B
On Friday 19 August 2011 01:38:58 Scott Ferguson wrote:
> But most of the recommendations I get are from
> sighted people ie. Vinux is "supposed" to be good
You will have noticed that I didn't mention it! (The Adriane version of
Knoppix is, of course, good because Adriane Knopper helped to desi
On 19/08/11 14:29, Karl O. Pinc wrote:
> On 08/18/2011 07:38:58 PM, Scott Ferguson wrote:
>
>> For me the biggest problem is CD labels - my writing makes the
>> reading
>> even harder. Now if someone created a simple system that announced
>> the
>> title of any cd placed in the drive based on in
On 08/18/2011 07:38:58 PM, Scott Ferguson wrote:
> For me the biggest problem is CD labels - my writing makes the
> reading
> even harder. Now if someone created a simple system that announced
> the
> title of any cd placed in the drive based on information burned to
> the
> CD
See http://
On 19/08/11 06:39, Lisi wrote:
> On Thursday 18 August 2011 03:55:30 Scott Ferguson wrote:
>> As Martin isn't going to
>> use a Live CD approach - it's a moot point. (though Knoppix Adriane will
>> probably do the job, and includes parted)
>
> I understood (possibly erroneously) that Martin's prob
On Thursday 18 August 2011 03:55:30 Scott Ferguson wrote:
> As Martin isn't going to
> use a Live CD approach - it's a moot point. (though Knoppix Adriane will
> probably do the job, and includes parted)
I understood (possibly erroneously) that Martin's problem wasn't that he
doesn't know about a
Arno Schuring writes:
> There might be. Try umount -f
>
> The information about current mounts is recorded in /etc/mtab
> (basically an old relic, but sadly still not put down). The real
> (kernel) information about mounts is in /proc/mounts. When copying root
> filesystems or working on a read-on
On Wed, Aug 17, 2011 at 10:55 PM, Scott Ferguson
wrote:
> On 17/08/11 12:15, Nico Kadel-Garcia wrote:
>> and you need to use the "-x" setting to avoid descending to other
>> partitions.
>
> What do you mean??
>
> That sounds very bad - how come I've never noticed this happening?
You probably don
On 17/08/11 12:15, Nico Kadel-Garcia wrote:
> On Sun, Aug 14, 2011 at 11:28 PM, Scott Ferguson
> wrote:
>
>> 4. use rsync to copy the files. eg.:- # rsync -azr /media/source0/
>> /media/dest0 [rinse and repeat until all partitions copied]
>
> Rsync does not replicate SELinux settings.
-X, --xat
Martin McCormick (mar...@x.it.okstate.edu on 2011-08-16 06:30 -0500):
>
> Is there a way to convince fdisk that hdb1 is not
> mounted?
There might be. Try umount -f
The information about current mounts is recorded in /etc/mtab
(basically an old relic, but sadly still not put down). The real
remendously faster, especially if you old disk had swap partitions,
funky partition layouts, or was only sparsely occupied, it can be used
again after partial replication, and it's vastly superior for backing
up live file systems than disk based operations like 'dd' and 'dump&
you write:
> Have you tried with "gparted" or "cfdisk"? The first it's a GUI based
> tool which usually manages very well these situations and the latter is a
> more convenient tool (text based) when it comes to manage partitions from
> command line.
I haven't tried cfdisk yet so I will give it a
On Tue, 16 Aug 2011 10:21:05 -0500, Martin McCormick wrote:
> You write:
>> I'm not sure in what stage of the migration are you right now (I did
>> not follow the full thread), but have you tried to boot from a LiveCD
>> and work from there?
>
> I have been avoiding that. I don't know if th
You write:
> I'm not sure in what stage of the migration are you right now (I did not
> follow the full thread), but have you tried to boot from a LiveCD and
> work from there?
I have been avoiding that. I don't know if this is
peculiar to Dell mother boards, but every so often, my CMOS
bo
han the old from where you are
copying the data, you can adjust some options when restoring the cloned
image to avoid missing hard disk space.
> The new drive is about half again as big as the old drive and research
> plus several previous answers from this list has lead me to try the
>
After using dd if=/dev/hda of=/dev/hdb bs=10M, I got a copy of a
boot drive's image on what will eventually be the new boot
drive. The new drive is about half again as big as the old drive
and research plus several previous answers from this list has
lead me to try the following strategy:
> Rob Owens writes:
> On Mon, Aug 15, 2011 at 06:12:24PM +0700, Ivan Shmakov wrote:
> Martin McCormick writes:
> Ivan Shmakov writes:
It's possible to dd(1) just the filesystem (partition) instead of
the whole disk.
Moreover, the filesystem can be downsized pri
a little too old to handle a large
> drive.
>
> If I use dd to copy the 10-gig drive over to the new
> drive as in:
>
> dd if=/dev/hda of=/dev/hdb bs=20M
>
> it works when I remove the old screamer drive, change the jumper
> on the new drive to Master and boot
On Mon, Aug 15, 2011 at 06:12:24PM +0700, Ivan Shmakov wrote:
> > Martin McCormick writes:
> > Ivan Shmakov writes:
>
> >> It's possible to dd(1) just the filesystem (partition) instead of
> >> the whole disk.
>
> >> Moreover, the filesystem can be downsized prior to that with
> >> r
disks, because of their limited erase cycles. You're
probably better off creating a new partition table. Then again, the
jury's still out on whether drive longevity is a real issue.
>
> If I use dd to copy the 10-gig drive over to the new
> drive as in:
>
> dd if=/d
Ivan Shmakov writes:
> resize2fs(8) after dd(1) on the destination partition ? it'll
> make the additional space available to the filesystem.
That may be the easiest approach to not get wrong if
that is the case. The old drive is the master boot drive on
/dev/h
> Martin McCormick writes:
> Ivan Shmakov writes:
>> It's possible to dd(1) just the filesystem (partition) instead of
>> the whole disk.
>> Moreover, the filesystem can be downsized prior to that with
>> resize2fs(8), thus the destination partition may be smaller than the
>> source
Ivan Shmakov writes:
> It's possible to dd(1) just the filesystem (partition) instead
> of the whole disk.
>
> Moreover, the filesystem can be downsized prior to that with
> resize2fs(8), thus the destination partition may be smaller than
> the source one.
Scott Ferguson writes:
> That's part of the problem... of course all the UUIDs in fstab and
> grub.cfg
> will refer to your old drive... ;-p
> Probably *not* the recommended way to do it, but...
Of course! I will not quote any more, here, but that
sounds like a plan. Many thanks.
With the rsync command you should use an exclude-file (see --exclude option)
containing a list of directories and files not to be transferred like
./lost+found**
./run**
./dev/**
./sys/**
./tmp/**
etc (see rsync manual).
After transferring the files you may have to adapt files like /etc/fstab and
>>>>> Martin McCormick writes:
[…]
> If I use dd to copy the 10-gig drive over to the new drive as in:
> dd if=/dev/hda of=/dev/hdb bs=20M
> it works when I remove the old screamer drive, change the jumper on
> the new drive to Master and boot but this
little too old to handle a large
drive.
Sorry - addendum to my previous post...
You'll need to run mkswap on the new drive while still mounted under the
Live CD. Though it will still run anyway..
Cheers
--
“We gotta come to some new ideas about life folks ok? I'm not being
blase abou
.
If I use dd to copy the 10-gig drive over to the new
drive as in:
dd if=/dev/hda of=/dev/hdb bs=20M
it works when I remove the old screamer drive, change the jumper
on the new drive to Master and boot but this is not very
efficient as it wastes almost 6 gigs of drive.
What I
drive over to the new
drive as in:
dd if=/dev/hda of=/dev/hdb bs=20M
it works when I remove the old screamer drive, change the jumper
on the new drive to Master and boot but this is not very
efficient as it wastes almost 6 gigs of drive.
What I tried to do was to format /dev/hdb with hdb1
* David A. <[EMAIL PROTECTED]> 2007-08-29
> > > What is common practice when migrating a system from one drive to
> > > another. Should I reinstall from scratch or partition the new drive
> > > and "copy everything" from the old one?
> >
> &g
> > What is common practice when migrating a system from one drive to
> > another. Should I reinstall from scratch or partition the new drive
> > and "copy everything" from the old one?
>
> Reinstallation is not necessary. There are plenty of HOWTOs available,
David A.:
>
> What is common practice when migrating a system from one drive to
> another. Should I reinstall from scratch or partition the new drive
> and "copy everything" from the old one?
Reinstallation is not necessary. There are plenty of HOWTOs available,
one being
Hi,
I've bought a samsung solid state drive, 8gb, to replace my HD in my
"silent home server".
What is common practice when migrating a system from one drive to
another. Should I reinstall from scratch or partition the new drive
and "copy everything" from the old on
point it was getting
> memory errors on boot. We installed a new drive in, and put the old drive
> as master.
>
> Installed Debian on the new drive, no problems, and during the
> partitioning process, it showed both drives (though I didn't partition the
> old drive, b
Critical info:
Debian with 2.22 Kernel
I386 infrastructure
2 120 GB hard drives
We were having problems with the old drive, to the point it was getting
memory errors on boot. We installed a new drive in, and put the old drive
as master.
Installed Debian on the new drive, no problems, and
* Jeff Hahn ([EMAIL PROTECTED]) [030531 05:42]:
> I'm clearly missing a step here, any help would be appreciated...
>
> copy drive to new partition, edit /etc/fstab.
>
> Once I copy drive contents to a new partition, I am unable to get a clean
> boot using the new partition as root even when boot
Jeff Hahn wrote:
I'm clearly missing a step here, any help would be appreciated...
copy drive to new partition, edit /etc/fstab.
Once I copy drive contents to a new partition, I am unable to get a clean
boot using the new partition as root even when booting from the install cd
in rescue mode.
Ap
I'm clearly missing a step here, any help would be appreciated...
copy drive to new partition, edit /etc/fstab.
Once I copy drive contents to a new partition, I am unable to get a clean
boot using the new partition as root even when booting from the install cd
in rescue mode.
Apparently there is
I installed a new harddrive and copied all directories
via cp -a home usr etc ...
Now X won't start as a user. X WILL start as root.
I checked the Xwrapper and it has the allowed-users=console
line in it.
I can rescue root=/dev/hdb1 to the old drive and start X fine
as a user.
The permissions
hi ya...
am assuming that /dev/md0 is mounted as / and /dev/md1 is mounted
as /mnt/raid/xxx and /dev/md2 is mounted as /mnt/raid/something
and while copying, dont bother to copy /tmp either...
- and you need to run lilo to put an mbr onto the cloned disks
lilo -C /etc/lilo.Clone.conf
On Tue, 31 Jul 2001, Willi Dyck wrote:
> I would like to know if tar handels the device files right!
It looks like it. I am making a root-raid system. I have created my
raid arrays, formatted and mounted them under /mnt/raid in the same
hierarchy as they will be mounted once the system is comp
On Tue, Jul 31, 2001 at 02:24:27PM +0300, George Karaolides wrote:
> On Mon, 30 Jul 2001, Willi Dyck wrote:
> > $ find . -xdev -print0 | cpio -pvdn0 /dev/[destination]
>
> This is a question I've been curious about for some time. Why not just do
> a tar? tar copies links by default (no
On Mon, 30 Jul 2001, Willi Dyck wrote:
> $ find . -print0 | cpio -pvdn0 /dev/[destination]
>
> This should copy everything to the defined destination. Even
> other mountpoints. If you only want to copy the mountpoint your are in,
> try this:
>
> $ find . -xdev -pr
On Sun, Jul 29, 2001 at 05:47:03PM -0700, Santiago del Roi wrote:
> How does one copy a complete Linux install from one hard drive to another?
> I've tried using the cp command with various parameters, but to no avail.
> There seems to be lots of special files and directories (/proc for
> example)
Title: Re: Copying Linux to a new drive
How does one copy a complete Linux install from one hard drive to another? I've tried using the cp command with various parameters, but to no avail. There seems to be lots of special files and directories (/proc for example) that cp can't ha
On 07/29/01 17:47:03 -0700, Santiago del Roi wrote:
> How does one copy a complete Linux install from one hard drive to
> another? I've tried using the cp command with various parameters,
> but to no avail. There seems to be lots of special files and
> directories (/proc for example) that cp can'
How does one copy a complete Linux
install from one hard drive to another? I've tried using the cp command
with various parameters, but to no avail. There seems to be lots of
special files and directories (/proc for example) that cp can't handle.
Any suggestions?
~
On Wed, Nov 29, 2000 at 11:01:31AM -0500, mikpolniak wrote:
> Last week after i installed potato on a new system i ran
> hdparm to test the new ibm ata66 drive and it showed reads of
> 32mb/sec. Since then the only changes i've made have been
> apt-get installs which have increased my dis
mikpolniak wrote:
>
> Last week after i installed potato on a new system i ran
> hdparm to test the new ibm ata66 drive and it showed reads of
> 32mb/sec. Since then the only changes i've made have been
> apt-get installs which have increased my disk usage to 895mb.
> Now hdparm c
Last week after i installed potato on a new system i ran
hdparm to test the new ibm ata66 drive and it showed reads of
32mb/sec. Since then the only changes i've made have been
apt-get installs which have increased my disk usage to 895mb.
Now hdparm consistently tests reads at aro
A long time ago, in a galaxy far, far way, someone said...
> Hi,
>
> On Wed, 19 Jan, 2000 ? 10:17:54AM +1100, Peter Ross wrote:
> > well. AFAIK the only directories that need to be on the / partition are
> > /bin, /sbin, and /etc.
> >
> Are you sure you don't need /lib and /dev ?
You're right;
Hi,
On Wed, 19 Jan, 2000 à 10:17:54AM +1100, Peter Ross wrote:
> well. AFAIK the only directories that need to be on the / partition are
> /bin, /sbin, and /etc.
>
Are you sure you don't need /lib and /dev ?
--
( >- Laurent PICOULEAU -< )
/~\ [EMA
Hmmm, does incremental backups sound good in this situation?
Anyone?
Regards,
Onno
At 07:44 PM 1/18/00 +, John Gay wrote:
>
>
>I've got some good suggestions, and apparently raised a few questions as well.
>Let me outline my reasons for asking and what I hope to do:
>
>I've got a CD-RW. I pl
On 18-Jan-2000, Ron Rademaker <[EMAIL PROTECTED]> wrote:
> On Wed, 19 Jan 2000, Peter Ross wrote:
>
> > Currently I have two partitions.
> >
> > 1. /
> > 2. /mnt/wally/hdc2 which contains my /usr/local and /home setup by using
> >symlinks.
> >
> > The advantage for me, is that I can trash t
another read of the FHS documents and a
good think.
aphro <[EMAIL PROTECTED]> on 18/01/2000 17:11:52
Sent by: aphro <[EMAIL PROTECTED]>
To: Onno Ebbinge <[EMAIL PROTECTED]>
cc: Ron Rademaker <[EMAIL PROTECTED]>, John Gay/IE/[EMAIL PROTECTED],
debian-user@lists.
i do stuff along those lines as well ..i dont understand when i installed
freebsd it reccomended a 20MB /var partition/slice even though i gave it
6.1GB of space. it doesnt make sense to have such small partitions even if
there is nothing on them to me anyways.
nate
On Tue, 18 Jan 2000, Onno Ebbi
On Tue, Jan 18, 2000 at 02:01:07PM +0100, Onno Ebbinge wrote:
> Sometimes I don't understand the stratagies used in disk partitioning.
Me neither, why are we making things so complicated and inflexible?
My partition scheme is as follows:
1.5 GB /
Rest/vol/0
/home is a link to /vol/0/_home.
On Wed, 19 Jan 2000, Peter Ross wrote:
> Currently I have two partitions.
>
> 1. /
> 2. /mnt/wally/hdc2 which contains my /usr/local and /home setup by using
>symlinks.
>
> The advantage for me, is that I can trash the root partition any time I
> want and still have all my important stuff.
Currently I have two partitions.
1. /
2. /mnt/wally/hdc2 which contains my /usr/local and /home setup by using
symlinks.
The advantage for me, is that I can trash the root partition any time I
want and still have all my important stuff.
Pete
Sometimes I don't understand the stratagies used in disk partitioning.
Please correct me if I'm wrong but I always thought that you split
the partitions by long term usage:
1- 2 GB /
1- 2 GB /var
1- 4 GB /var/spool
rest on /home
Then I link /tmp
> I recently got a new 13G hard drive. I've installed it as hdb, and moved my
> CD-RW to hdc. At the moment I've got a 6G drive with 2G for WindowsNT, 100M
> for
> /, 1G for /home and 2G for /usr. I really need more room for both /home AND
> /usr, but I also need more space for /var and /opt and
I recently got a new 13G hard drive. I've installed it as hdb, and moved my
CD-RW to hdc. At the moment I've got a 6G drive with 2G for WindowsNT, 100M for
/, 1G for /home and 2G for /usr. I really need more room for both /home AND
/usr, but I also need more space for /var and /opt and some other
Stephan A Suerken wrote:
>
> Nils Rennebarth <[EMAIL PROTECTED]> writes:
>
> > You should not 'copy the partitions'. Don't know what ghost is, but I doubt
> > it supports the ext2 filesystem.
>
> With GNU cp, copying whole partitions is ok via "cp -a", so tar
> is not needed (if one can mount b
Nils Rennebarth <[EMAIL PROTECTED]> writes:
> You should not 'copy the partitions'. Don't know what ghost is, but I doubt
> it supports the ext2 filesystem.
With GNU cp, copying whole partitions is ok via "cp -a", so tar
is not needed (if one can mount both partitions simultaneously).
There i
"Ghost" is a drive imaging software. What it does, it copies your disk or
partition
byte for byte, formatting it on-the-fly. It works with ext2 filesystem, the
only
limitation is that, compared to the other filesystems, it won't resize the
image, meaning
that you can't take a partition created
On Wed, Jun 30, 1999 at 12:51:50PM +0200, Rudy Broersma wrote:
> At the moment I have a 810 MB harddisk in my Linux box. I'm going to replace
> it with a 12 GB Bigfoot. Can I just 'copy' the partitions? (Using ghost). Or
> do I need to reinstall Linux (hate that. When I reinstall something I always
Hi,
At the moment I have a 810 MB harddisk in my Linux box. I'm going to replace
it with a 12 GB Bigfoot. Can I just 'copy' the partitions? (Using ghost). Or
do I need to reinstall Linux (hate that. When I reinstall something I always
think of Windows)
Bye,
Rudy
Ian Keith Setford wrote:
>
> Yo-
>
> I have had my sytem running on a WD 2.1G for over a year but I just bought
> a Mylex SCSI card and a WD Enterprise drive. I have everything working
> fine but now I want to mount /home on its own partition on the new faster
> drive. What is the best way to a
This should be relatively easy...
Partition the drive with fdisk (cfdisk or whatever) under linux.
'fdisk /dev/sda' probably
You might want to think about putting a swap partition on this
new drive also. It _should_ be a noticable improvement if you
swap much. You probably do not
on on the new faster
> drive. What is the best way to accomplish this? Is it even advisable?
>
Sure, this is easy. Create the partition on the new drive where you want
/home to live and create the ext2 filesystem on that partition. Then
mount this partition on /mnt or something and copy y
Yo-
I have had my sytem running on a WD 2.1G for over a year but I just bought
a Mylex SCSI card and a WD Enterprise drive. I have everything working
fine but now I want to mount /home on its own partition on the new faster
drive. What is the best way to accomplish this? Is it even advisable?
> Re-arrange your drives like this and let me know if it fixes the situation:
>
> HDA - ok
> HDC - Set as HDB
> HDB - Set as HDC (Linux does not care where additional partitions are)
I did almost this, except instead of swapping hdb and hdc, I simply
detached hdb temporarily. Low and behold it
Mark Phillips writes:
[snip]
> > Why have two "DOS" bootable drives? In my experience, "DOS" only likes to
> > see
> > one main bootable drive.
[snip]
One other item which I did not mention: The bootable "DOS" drive _must_ be the
first one detectable by "DOS".
>
> This is the setup of my three
On Thu, Apr 16, 1998 at 11:01:34AM +0930, Mark Phillips wrote:
>
> > > I have just installed a third IDE hard drive (my board supports up
> > > to 4). I have configured the BIOS. Now I want to use lilo to make it
> > > possible to boot from it (it currently has DOS on it), but when I try,
> > >
On Wed, 15 Apr 1998 [EMAIL PROTECTED] wrote:
> Mark Phillips writes:
> [snip]
> > I tried booting anyway but it failed, complaining that it wasn't a system
> > disk. However my Dad (whose disk it was before giving it to me) swears it
> > was bootable.
> >
> > So what's wrong? On my father's com
Mark Phillips writes:
[snip]
> I tried booting anyway but it failed, complaining that it wasn't a system
> disk. However my Dad (whose disk it was before giving it to me) swears it
> was bootable.
>
> So what's wrong? On my father's computer the disk was disk C: where as
> now it is /dev/hdc (th
> > I have just installed a third IDE hard drive (my board supports up
> > to 4). I have configured the BIOS. Now I want to use lilo to make it
> > possible to boot from it (it currently has DOS on it), but when I try,
> > it comes up with:
> >
> > # lilo
> > Added linux *
> > Added dos
> > ide
Mark Phillips writes:
>
>
> Hi,
>
> I have just installed a third IDE hard drive (my board supports up to 4).
> I have configured the BIOS. Now I want to use lilo to make it possible to
> boot from it (it currently has DOS on it), but when I try, it comes up
> with:
>
> # lilo
> Added linux
Hi,
I have just installed a third IDE hard drive (my board supports up to 4).
I have configured the BIOS. Now I want to use lilo to make it possible to
boot from it (it currently has DOS on it), but when I try, it comes up
with:
# lilo
Added linux *
Added dos
ide: probable bad entry for /dev/
86 matches
Mail list logo
