how-to block ads
|
|
Share Topic
 |
 |
|
|
|
Reviews:
 ·linode
| reply to koitsu
Re: Motherboard suddenly stopped booting? Thanks for your reply!
When I cloned the drives, I copied, bit-for-bit, from the beginning of the drive until the beginning of the first partition (which copied the MBR table and stuff), so I figured that would work. When it didn't, I nuked all those bytes, reconstructed the partition table and re-installed the bootloader from scratch, so I was somewhat surprised when even that didn't work. The part I find odd is that it's having trouble booting but I can access every LBA on the drive without issue, and everything seems to be in the proper place. I suppose I could give the boot repair CD a try and see if that works, but if it doesn't, I guess I'll have to take a look at the BIOS.
FWIW, they're both Seagate Barracuda 7200.10 drives, they just differ in capacity. Of course, the logical part of me is thinking they can't be that different, but I may be wrong and it may be #1 after all.
And I totally agree with you that IDE/PATA sucks; I just wish I had more ports (and drives) so I could boot from SATA and be done with it.
I'll investigate further and let you know!  | |
 koitsuPremium,MVM
join:2002-07-16
Mountain View, CA
kudos:19 | The drives having the same series number (7200.10) does not mean "they're pretty much identical". The capacity increasing means the platter count may have changed (though the platter itself definitely has), which also means the total LBA count has increased. LBA count directly affects a BIOS's decision to use CHS vs. Large (ECHS) vs. LBA mode. That addressing mode choice also affects how a bootloader makes its decisions; i.e. when you write the boot blocks, it may have been when using CHS addressing, so it may have decided to write things to C=839, H=255, S=0, while on the new drive it may be using LBA which would use a totally different location. On the bright side, at least sector size didn't change.
I would suggest examining the addressing modes in the BIOS first, as that's the most likely explanation for a non-bootable PATA system (in your situation) that I can think of.
--
Making life hard for others since 1977.
I speak for myself and not my employer/affiliates of my employer. | |
|
