Archived from groups: alt.comp.periphs.mainboard.abit (
More info?)
Yes the PATA was correctly jumpered; in the past I have used it as my boot
drive via a serillel converter on a SATA channel so I know it does/did work
in my setup that way. Seagate tech support have now suggested that perhaps
my replacement mobo has in some way affected the drives. Seems unlikely, but
it's possible I suppose.
As you say, perhaps I caused the problem. Certainly, I followed the same
procedure on handling etc that I have used frequently in the past without
problem. Still, who knows if that's the cause? I wasn't working with the
drives so the sata cables were simply unplugged from the original mobo,
plugged into replacement and then plugged back into original. All times with
power off.
C'est la vie.
Absolutely.
"TomG" <tgeery-NOSPAM-@cox.net> wrote in message
news:_cMjc.3413$pJ1.889@lakeread02...
> assuming you had the PATA drive correctly jumpered and such then I'd agree
> that it points to a mobo issue... however, I would look at what you did
> when you working on the system to see if there was anything you could have
> done to contribute to the problem... after all, it was working before you
> dug into it, right?
>
> --
>
> Thomas Geery
> Network+ certified
>
>
ftp://geerynet.d2g.com
>
ftp://68.98.180.8 Abit Mirror <----- Cable modem IP
> This IP is dynamic so it *could* change!...
> over 130,000 FTP users served!
> ^^^^^^^
>
>
>
>
> "anthonyi" <anthony.i67_xxx@ntlworld_xxx.com> wrote in message
> news:3KJjc.21$9H5.8@newsfe3-win.server.ntli.net...
> > Hi Tom
> >
> > No, all power was off. Seagate tech support tell me the symptoms are
> > indicative of
> >
> > 1. bad cables
> > 2. failed drive, or
> > 3. failing mobo
> >
> > I connected my working PATA drive to a SATA channel using a serillel
> > converter and got the same symptoms from a known working
> drive...reconnected
> > it to an IDE channel and it works just fine. I've already tried multiple
> > cables so I suppose I'm left with option #3 above. :-(
> >
> > BTW, kudos to the Seagate tech support team - it makes such a change not
> to
> > wait in vain for an answer to a manufactureres so-called tech support
> group.
> >
> > A
> >
> >
> > "TomG" <tgeery-NOSPAM-@cox.net> wrote in message
> > news:N7Ajc.336$pJ1.3@lakeread02...
> > > did you have all power removed from the system while you were working
on
> > it
> > > or could the stand by power still have been active? almost sounds
like
> > > somehow you blew the drives!
> > >
> > > --
> > >
> > > Thomas Geery
> > > Network+ certified
> > >
> > >
ftp://geerynet.d2g.com
> > >
ftp://68.98.180.8 Abit Mirror <----- Cable modem IP
> > > This IP is dynamic so it *could* change!...
> > > over 130,000 FTP users served!
> > > ^^^^^^^
> > >
> > >
> > >
> > >
> > > "anthonyi" <anthony.i67_xxx@ntlworld_xxx.com> wrote in message
> > > news:AIsjc.99$yA.77@newsfe1-win...
> > > > Tried a CMOS clear but it didn't change anything. If I disconnect
both
> > > > drives and leave the SATA RAID ROM enabled, the PC boots...if I
> connect
> > > > either or both drives it hangs at the stage that the SATA BIOS
should
> be
> > > > reporting the drive model numbers and I get the non-standard
> characters
> > > > displayed in place of the model name. If I boot with SATA enabled
and
> > not
> > > > RAID, then I get a long-ish period of blank screen (I imagine while
> the
> > > BIOS
> > > > attempts to identify the SATA drive(s)) and then a boot into XP as
> > normal.
> > > >
> > > > Very strange and frustrating - my two SATA drives are pretty new so
to
> > > lose
> > > > the use of them is a pain. I have all my data secure, thankfully. I
> > don't
> > > > have another PC available to try the SATA disks in or I would do
that.
> > > >
> > > > Thanks for the ideas - if you have any more please let me know!
> > > >
> > > > Cheers,
> > > > A
> > > >
> > > >
> > > >
> > > >
> > > > "TomG" <tgeery-NOSPAM-@cox.net> wrote in message
> > > > news:RWgjc.244$pJ1.214@lakeread02...
> > > > > any chance you accidentally shorted the CMOS so that the settings
> are
> > no
> > > > > longer correct and you need to clear the CMOS and reprogram the
> > > settings?
> > > > >
> > > > > --
> > > > >
> > > > > Thomas Geery
> > > > > Network+ certified
> > > > >
> > > > >
ftp://geerynet.d2g.com
> > > > >
ftp://68.98.180.8 Abit Mirror <----- Cable modem IP
> > > > > This IP is dynamic so it *could* change!...
> > > > > over 130,000 FTP users served!
> > > > > ^^^^^^^
> > > > >
> > > > >
> > > > >
> > > > >
> > > > > "anthonyi" <anthony.i67_xxx@ntlworld_xxx.com> wrote in message
> > > > > news:7Bdjc.170$fw5.51@newsfe1-win...
> > > > > > Triple checked before I posted, I'm afraid. Also tried a
> substitute
> > > > > cable...
> > > > > >
> > > > > > Thanks anyway.
> > > > > >
> > > > > > A
> > > > > >
> > > > > >
> > > > > > "Richard Hopkins" <richh@dsl.nospam.co.uk> wrote in message
> > > > > > news:408d647c$0$20509$cc9e4d1f@news-text.dial.pipex.com...
> > > > > > > "anthonyi" <anthony.i67_xxx@ntlworld_xxx.com> wrote in
> message...
> > > > > > > > Once back together (in the same state as before the
attempted
> > > > > > > > upgrade) I can no longer boot with SATA Raid enabled. If I
> > attempt
> > > > > > > > to, then instead of reporting the disk model numbers during
> the
> > > RAID
> > > > > > > > BIOS screen, I get random characters displayed where the
disk
> > name
> > > > > > > > should be and the boot goes no further.
> > > > > > >
> > > > > > > Somewhere along the line you've failed to completely insert
one
> of
> > > the
> > > > > > data
> > > > > > > cable plugs in one of the sockets. Make sure they're all fully
> > > > inserted
> > > > > > and
> > > > > > > try again.
> > > > > > > --
> > > > > > >
> > > > > > >
> > > > > > > Richard Hopkins
> > > > > > > Cardiff, Wales, United Kingdom
> > > > > > > (replace .nospam with .com in reply address)
> > > > > > >
> > > > > > > The UK's leading technology reseller www.dabs.com
> > > > > > > Get the most out of your digital photos www.dabsxpose.com
> > > > > > >
> > > > > > >
> > > > > >
> > > > > >
> > > > >
> > > > >
> > > >
> > > >
> > >
> > >
> >
> >
>
>
Facebook
Twitter
Instagram