Re: Issues with external hard drives
- From: "Folkert Rienstra" <see_reply-to@xxxxxxxx>
- Date: Fri, 16 Dec 2005 20:32:31 +0100
"Jim" <null@xxxxxxxx> wrote in message news:Ezuof.542$Bx.448@xxxxxxxxxxxxx
>
> "PeteK" <YouHaveToBe@xxxxxxxxxx> wrote in message news:dnrnt0$f6f$1@xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
> > I have two internal EIDE HDs. My BIOS is set to AUTO mode for these,
> which
> > I believe defaults to LBA mode (Master is 40GB, Slave 120GB) for large
> > drives. I just bought another 160GB EIDE drive. All three drives live in
> > removable disk caddies. The intention of this set-up was to give me a bit
> of
> > flexibility, particularly for backing-up my boot drive.
> >
> > I successfully cloned my 12GB boot partition on the master (40GB) HD to
> the
> > External HD.
>
> Am I to assume the "External HD" is an enclosure that has the new 160GB HD??
> This reference to the "External HD" has just popped up out of nowhere.
"I have *two internal EIDE HDs*"
"I just bought *another 160GB EIDE drive*"
"I successfully cloned my 12GB boot partition on the master (40GB) HD to the
*External HD*".
"However, when I cloned the newly created 12GB partition from the 160GB HD
*(in its external USB drive)*"
How many clues do you need?
Reading is not your forte, is it, Jimmy. Ranting is more your thing.
Lots of ranting. No proofreading, bad quoting etc. etc.
You already start ranting before you have read the entire post and it wasn't
even so big. But, of course, it is now.
>
> > When I swap these drives, the new (160GB) drive boots OK.
>
> Ok, so now that you've cloned the boot partition to the 160GB (using an
> external enclosure?),
Wow, you're quick.
> you've removed it from the enclosure and installed is
> as the master, and it operates normally?? Good.
He must be so happy that he has your seal of approval now.
>
> > However, when I cloned the newly created 12GB partition from the 160GB HD
> > (in its exerenal USB drive) to the Slave IDE drive, the resulting
> partition
> > won't boot (it gets so far, then just hangs).
> >
>
> Ok, I'm lost again.
Already? Again?
> Now it sounds like the 160GB is back in the external enclosure.
Yup that's what he said.
> So what's the story here, are you booting the 12GB partition on the 160GB
> from the master IDE, or perhaps booting it from the external USB enclosure?
Nope, on the slave drive obviously, either connected as slave or swapped to master.
> Maybe it's not even germane, but is getting confusing.
Not if you refrain from making stupid assumptions.
>
> So you've cloned from the 160GB HD to old slave HD (120GB), and now it
> won't boot from there? That's the question?
Bloody obvious it is.
>
> First, if I've read this correctly, all this movement using the new 160GB HD
> sounds irrelevant. It sounds like you could have simply cloned the boot
> partition from the old master to the old slave
> and had the same problem.
But he didn't. It worked.
> Introduction of the 160GB is only confusing things
It answers the resulting question of what you just put above.
>(again, if I'm reading this correctly).
But you can't.
>
> In general, Windows does NOT like to boot from anything but the first HD.
Works fine from an installation standpoint.
What it may not like is if you change things around it it doesn't adapt so well
as that it should.
> So it's no surprise that it would fail to boot.
Yes it does. He did that on the other drive and that worked fine.
Obviously windows doesn't like what happened to "the other drive"
internal.
> At a minimum, you would still need boot files on the master HD, which
> in turn could boot the OS from the slave HD.
Nonsense.
> In fact, I use BootIt NG to sometimes boot from other than the first HD,
That's because you have no idea how to do it otherwise. We have been over
that already in another thread but obviously you didn't learn from that at all.
> and for this to wok, I have to use a special feature that
> logically changes the HD id from hd1 (the second HD) to hd0 (the first HD).
> When Windows sees anything but hd0, it will not boot it. So my boot manager
> manipulates the HD id so Windows will boot it anyway.
>
> Of course, all this is somewhat speculative since I'm not even sure I
> completely understand the config, I'm making a few
> logical
As if you understand logic.
> conclusions based on scant information.
No, you couldn't bother to properly read the post.
> But in general, booting the OS from anything but the first HD can be tricky.
That's not what you first said.
> You could perhaps update the boot.ini file on the first HD to include
> a boot option for the OS on the slave,
> which is part of the problem.
Only in your solution.
> BUT, this raises another problem.
> Your OS on the slave is probably still C:, but
> the boot partition on the old master is ALSO C:!
Bingo. Btw, it is the same in reverse.
If that is the problem then the master won't boot propely either anymore.
> In order to make the boot partition on the old master boot the cloned OS on the
> slave, the OS partition on the slave needs to be OTHER THAN C:, like D:, E:, etc.
Right. That is likely where Windows fails to adapt properly in particular instances.
> But you can't easily make that change since the registry on that slave
> partition is riddled w/ C: references.
Which is not a problem if you never intend to boot from that drive again (as is).
> IOW, it's probably a mess.
Depends on how you intend to use the drives. If you want them both bootable
and all drives visible you may have to intall on one of them from scratch with
the "other" drive visible to the install so that drive letters won't be doubled.
>
> The way to correct the problem is use a good boot manager, like BootIt NG.
> You can then use *it* to boot any OS partition, on ANY HD, and most
> importantly, HIDE other partitions so you can keep the OS on the slave HD
> still bootable as C:.
You can still keep the letter that it has so that the registry has no problems.
Bootable and C: are not connected by the hip.
>
> HTH
>
> Jim
>
>
> > Could I be hiting an issue with incompatible LBA modes ?
> >
> > I'm running windows XP2, using partition magic v7 to clone the drives.
> >
> > TIA,
> >
> > Pete K
> >
> >
>
>
.
- References:
- Issues with external hard drives
- From: PeteK
- Re: Issues with external hard drives
- From: Jim
- Issues with external hard drives
- Prev by Date: Re: New WD 160g stuck in PIO instead of Ultra DMA
- Next by Date: Re: SATA Question: Need RAID to benefit?
- Previous by thread: Re: Issues with external hard drives
- Next by thread: Re: Issues with external hard drives
- Index(es):
Relevant Pages
|
