cable select is always a bit dodgy, when i read up on it, i found that the standard was never accepted.
try setting the drives as master/slave.
Hello. I was wondering if anyone knew of a solution...
(C: Quantum 10 gig, D: West. Digital 30 gig / both ntfs and jumper settings on 'cable select' using cable select cable / mobo drivers updated)
A few days ago a condenser(I think) on my mobo blew up,
so I got a new mobo(Asrock K7 Upgrade-880). I wanted to
see if my hard drives were ok, so I just plugged it into
the new mobo without reinstalling Windows, and both
had no problems.
So I unplugged my D: hdd(pri slave), and formatted
and reinstalled Windows Xp sp1 with just my C hdd(pri master) plugged in.
Everything went ok, so I replugged in my D hdd, but the
problem is, I can't see it in Windows explorer.
In other words, the bios and windows device manager both
recognize it, but it doesn't appear in windows explorer,
and if I go into Device Management, it says that D: is a
'dynamic' disk, that it's unaccessable, and that 'status bar' doesn't
appear on the right side...
I also tried changing it to the secondary slave by connecting
it to the cd-rw(sec master), but it's still the same... And when I
run cmd in windows, D doesn't appear...
It seems that something went wrong during the reinstallation,
and that I have to convert it from a 'dynamic' to a 'basic' disk...
but that would mean that I would lose all my data...
So someone suggested that I use Knoppix to boot my computer,
access D:, and backup what I can...
But this is my first time using knoppix, so I was wondering,...
1) If I boot my comp with it, can I access D?
2) If I can, can I transfer files from it over to C, then reboot into
WinXp, and access the files?...
Any info would be appreciated... thanks in advance.
cable select is always a bit dodgy, when i read up on it, i found that the standard was never accepted.
try setting the drives as master/slave.
Actually, I originally had it as master/slave,
but I couldn't fix my problem, so that's why I changed it to
'cable select'...
Use all the smiley faces you want, but the advice was right. Make it work as master/slave. You need a special cable for cs (part of the cable is cut and twisted between the middle and last IDE connector) or it can never work right, which I'm betting you don't have.Originally Posted by yoyall
The thing is, it WON'T work whether I put it to 'cable select' OR
'master/slave'~
In other words, it's not a cable or mobo problem...
it's a problem with WinXp...
(D being a dynamic disk)
So that's why I was wondering if I would be able to
access my D hdd and transfer files over to my C hdd
if I booted my computer with Knoppix~
Yes, most likely you will be able to access the drive. As far as transferring the files over to C, it is considered risky to write files to an ntfs partition using the standard linux ntfs drivers. You should make sure to use the captive drivers if you move them over to your new winxp install. Or if you have more than one cd drives, with one being a cd-rw, you could just use knoppix to burn the important files onto a disc.Originally Posted by yoyall
So given that moving to cable select didn't fix anything, and others are telling you that cable select is a problem, why leave it on cable select?Originally Posted by yoyall
OK, you may have other problems, but you may have compounded them with the cs setting.Originally Posted by yoyall
This one I do not know the answer to. My expectation is low. But since you have the disk, why in the world not try? Knoppix will not write to the disk, will not hurt anything.Originally Posted by yoyall
You might try making it a normal basic disk again, there is a procedure to do so here: http://faq.arstechnica.com/link.php?i=1806 . But I would at least try looking at it with Knoppix first.
Actually, it can be done from a live CD even if you have only one CD drive (a writer obviously) and even if you don't have enough memory for the toram option. See the details in this thread: http://www.knoppix.net/forum/viewtopic.php?t=14781Originally Posted by champagnemojo
ah okay~ thanks to all for all the tips~
I'll try them out~
I had a similar problem with Windows not being able to find the primary slave. BIOS could find it. I re-pinned the slave drive and now BIOS and Windows XP finds it. I'd suggest looking for an alternate way of pinning the drive not being recognized.
IBM QRadar xx29 Server 4412Q2A
$170.00
IBM 8203 E4A p520 Server 8203-E4A 4.2GHz 2-Core POWER6 32GB RAM / NO HDD USED
$99.99
$16000.00
IBM Power S822 12-Bay Server System Power8 Core 3.42Ghz DVD-Rom Drive 64GB No HD
$399.99
IBM Power 720 POWER7 00E6516 3.6GHz CPU 64GB RAM Server
$209.98
IBM 7944AC1 System x3550 M3 Server 1*Intel Xeon X5650 2.67GHz 4GB SEE NOTES
$26.97
IBM Power 740 8205-E6C Express 8-SFF Power7 3.55GHz CPU 64GB RAM *No HDD* Server
$191.99
$100.00
1U IBM x3550 M5 4 Bay SFF SAS3 Server 2x E5-2683 V3 28 Core 128GB DDR4 2x Tray
$318.00
IBM X3650 M5 8871-AC1, 2 X E5-2620V4 2.1 GHZ,20M, 32 GB, DUAL 750W, 2 X 1TB HDD
$369.99