public inbox for blinux-list@redhat.com
 help / color / mirror / Atom feed
From: Rafael Skodlar <raffi@linwin.com>
To: blinux-list@redhat.com
Subject: Re: Transfering linux system to a new hard drive
Date: Tue, 4 Dec 2001 10:52:50 -0800	[thread overview]
Message-ID: <20011204105250.D8088@linwin.com> (raw)
In-Reply-To: <20011204113241.K18429@nntp.AegisInfoSys.com>; from blinux-mail@AegisInfoSys.com on Tue, Dec 04, 2001 at 11:32:41AM -0500

On Tue, Dec 04, 2001 at 11:32:41AM -0500, Henry Yen wrote:
> On Mon, Dec 03, 2001 at 05:03:43AM -0600, Cheryl Homiak wrote:
.......
> if that is an issue, the new drive may also be incompatible with your bios,
> in which case you'll only be able to see the first 8 gig.

Can't tell not knowing what motherboard is in there.

> 
> > The plan is to have a dos partition on the sme hard drive as linux, though
> > if I could afford it I'd still rather have two separate hard drives.
> 
> if you can afford the space, it's probably better to have both on a single
> drive; dos can't use more than 2 gig, and 2 drives are more overall
> risk than a single, and also linux has no problem with non-linux
> partitions.

It's always better to have more than one drive, that's the whole idea of 
RAID systems. That means two drives is better than one. You can mirror the 
data which is a quick backup while tape or other removable media servers 
as archive.

.....
> it's a bad idea to hot-plug ide drives (although i've done it a few
> times without problems).  and if there's a stiction problem with the
> old drive, it's quite possible that hot-plugging would cause a
> power hiccup, which is even worse for a marginal drive.

You can do that with SCSI but ATA drives are not build for that kind of
operation. In any case, you need to plug the power in correctly, i.e.  
ground first which is not that easy to do, otherwise you'll damage the
drivers with reverse current or current loops through the motherboard
circuit.

...........
> > If anybody can think of a way I can transfer my current system or can tell
> > me how I can get my ethernet up and working so I can use that to do the
> > package installs, I would appreciate it.
> 
> when faced with a failing drive, my approach would be to get someone
> to lend a hand with another working system with a bunch of free
> space on it, and back the system up over ethernet.  then, swap out the
> old disk, do a minimal install onto the new disk (leaving room for
> partitions from the old disk), and then ethernet the old disk contents back.
> the trick in all this is to watch your partition structure carefully,
> but this is how i upgrade hard drives (note: i am sighted).
> 
> of course, if you can't another system, or you're unable to do a minimal
> install of the temporary "transfer" system, then i don't see a technical
> solution.  if you can do these things, then figuring out your ethernet
> issues should be the best immediate plan.  to start, what appears
> when you type: ifconfig eth0
> 
> -- 
> Henry Yen                                       Aegis Information Systems, Inc.
> Senior Systems Programmer                       Hicksville, New York

-- 
Rafael




  reply	other threads:[~ UTC|newest]

Thread overview: 24+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
 Cheryl Homiak
 ` Henry Yen
   ` Rafael Skodlar [this message]
 ` Rafael Skodlar
 ` Andor Demarteau
 ` James R. Van Zandt
   ` Vividata OCR Shop Ron Marriage
     ` Roger Butenuth
       ` John J. Boyer
   ` Ron Marriage
   ` Ron Marriage
     ` Henry Yen
     ` John J. Boyer
       ` Henry Yen
         ` John J. Boyer
           ` lobap
           ` Janina Sajka
     [not found]         ` <Pine.LNX.4.33.0112281403001.2919-100000@localhost.localdom ain>
           ` John G. Heim (26 2-9887)
       ` Janina Sajka
     ` Roger Butenuth
     ` Janina Sajka
       ` Ron Marriage
     [not found]     ` <Pine.LNX.4.43.0112291000490.537-100000@toccata.grg.afb.net >
       ` Brent Harding
         ` Janina Sajka

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=20011204105250.D8088@linwin.com \
    --to=raffi@linwin.com \
    --cc=blinux-list@redhat.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).