I have a recently purchased, (used) NP-9860-S / Clevo D900T which arrived with a single drive. I used killdisk to scrub that drive; purchased an identical WD drive to match it; and jumpered the drives according to Clevo's / WD's specs to create a RAID (O / Stripe):
Clevo specs:
(set) the jumper on the slave hard disk to the cable select option in order
for the system to recognize the disks.
The slave disk will automatically be in the upper slot of the hard disk case, the master will be in the lower slot (as defined by the hard disk cable).
WD:
for Western Digital 2.5" EIDE hard drives;
Cable Select Configuration Options for PC Systems;
Installing the new drive as the secondary (Slave) drive:
If you are connecting your drive as the secondary (Slave) drive on the cable with another IDE drive, please ensure that a jumper is connected to pins B-D on the 2.5" drive. Connect the 2.5" drive to the middle of the cable and other (Master) drive to the end of the cable.
(Getting finally to the problem): these two set-ups are in conflict, as the upper drive is also the end of the cable - or the typical master position on an IDE cable.
In any case i tried this set-up (after installing the RIAD driver) and attempted to build the RAID. BIOS / the raid controller could not see either of the drives so I used every other jumper config possible until Master=open and Slave=Slave and then it could see the drives.
I built the RAID, installed the OS, installed drivers in order, (with various hassles along the way); updated the scsi processing device and other drivers.
All along the way though i had varied success in getting through POST and/or the system would simply hang at the desktop - and at reboot would be "Unable to find operating system".
And this where i am now. I cannot determine if this is a problem related to the initial jumpering of the drives, a driver conflict, or a hardware failure: controller card, drive cable, or old/new HD.
Any suggestions?
Apologies for the wordy post / thanks for reading.
-d9t
Clevo specs:
(set) the jumper on the slave hard disk to the cable select option in order
for the system to recognize the disks.
The slave disk will automatically be in the upper slot of the hard disk case, the master will be in the lower slot (as defined by the hard disk cable).
WD:
for Western Digital 2.5" EIDE hard drives;
Cable Select Configuration Options for PC Systems;
Installing the new drive as the secondary (Slave) drive:
If you are connecting your drive as the secondary (Slave) drive on the cable with another IDE drive, please ensure that a jumper is connected to pins B-D on the 2.5" drive. Connect the 2.5" drive to the middle of the cable and other (Master) drive to the end of the cable.
(Getting finally to the problem): these two set-ups are in conflict, as the upper drive is also the end of the cable - or the typical master position on an IDE cable.
In any case i tried this set-up (after installing the RIAD driver) and attempted to build the RAID. BIOS / the raid controller could not see either of the drives so I used every other jumper config possible until Master=open and Slave=Slave and then it could see the drives.
I built the RAID, installed the OS, installed drivers in order, (with various hassles along the way); updated the scsi processing device and other drivers.
All along the way though i had varied success in getting through POST and/or the system would simply hang at the desktop - and at reboot would be "Unable to find operating system".
And this where i am now. I cannot determine if this is a problem related to the initial jumpering of the drives, a driver conflict, or a hardware failure: controller card, drive cable, or old/new HD.
Any suggestions?
Apologies for the wordy post / thanks for reading.
-d9t
