So I replaced the 1tb parity drive with a 2tb and that all went fine.  Then I wanted to use the old 1tb as a data drive but had to add another Promise Sata card.  The card is in but the drive is not showing up in the Devices.  When the system boots, the drive light does flash but once the unRaid loads it does not see it or have any activity.  Any suggestion?

So I replaced the 1tb parity drive with a 2tb and that all went fine.  Then I wanted to use the old 1tb as a data drive but had to add another Promise Sata card.  The card is in but the drive is not showing up in the Devices.  When the system boots, the drive light does flash but once the unRaid loads it does not see it or have any activity.  Any suggestion?

Post a syslog...

 

Either

The additional promise card is not plugged in correctly

The additional promise case is not compatible

The additional promise cars has different firmware

There is a limit on the number of promise cards in a server

The SATA cable to the SATA drive is loose

The power cable to the SATA drive is loose

The power cable to the SATA drive is defective

The SATA cable to the SATA drive is defective

The disk was zapped by handling it.

 

Only the syslog will give the clues needed.

 

Does the disk show in the BIOS?  That would be a really good first step.

Here is the latest SysLog.  Hope this helps.

syslog.txt

Any suggestions?

I see you have at least one WD EARS drive (most likely your newest drive).  Did you install a jumper on pins 7-8?

Yes that is the new parity drive which is working but have not messed with pins at all.  The drive not being see is one of the original 1tb drives that was the old parity drive but plugged into the new Promise sata card.

 

Edit: From what I have read, this only applies to Win XP and not an issue for Linux.  Mine appears to be working fine as the parity.  I do have a second one I am trying to get up as a new data disk, along with the old 1tb WD parity both of which are on the new sata card.  Maybe someone can chime in???

You DO need the jumper when using the disk with unRAID.

 

It is not necessary to get the drive working but the speeds are severely hampered without it.

Right.  The first step you should take is to install a jumper onto pins 7-8 of your WD EARS drive and then recalculate parity.  Once you have finished that, we can start addressing the older 1 TB drive.

Will bring it down after everyone is off work tonight, install jumper and have rebuilt overnight.  Then will get back with y'all tomorrow.  Thanks for the help on this.

It is rebuilding the parity and is projecting like 36 hours to do.  Is that normal for a 2tb drive with 14 1tb data drives?  I do remember when it was a 1tb that it would take a good 12 to 14 hours when ever it needed to rebuild.

It is rebuilding the parity and is projecting like 36 hours to do.  Is that normal for a 2tb drive with 14 1tb data drives?  I do remember when it was a 1tb that it would take a good 12 to 14 hours when ever it needed to rebuild.

It will speed up once it gets past the 1TB drives.

 

But if you want, you can rejoice that your display does not look like this:

I know, PATIENTS YOUNG GRASSHOPPER.  Just hurry up so I can be patient........

Parity is rebuilt now.  When the computer reboots, the two drives hooked up to the new Promise card are read and flash the activity light.  So I know the machine is seeing them, but once the unRaid starts its process, no more activity on those two drives.  I have played with hooking up the 2 drives to another sata port on the initial 2 promise cards and they ARE found, so it has to be something with the new card and unRaid.  I have noticed that during boot before unRaid, these is a new FastBuild screen that it hesitates on giving me an option to do some settings.  I went in there and it shows these 2 drives.  I get the option to Define LD, Delete and Controller config.  The 1TB is defined and listed under the RaidMode as JBOD and the 2tb is listed but not defined.  I get the option to define as Raid 0, 1, 5, 10 or JBOD.  If I try to select any of the Raids, I get messages saying more drives, etc.  I assume these should be just set at JBOD.

Parity is rebuilt now.  When the computer reboots, the two drives hooked up to the new Promise card are read and flash the activity light.  So I know the machine is seeing them, but once the unRaid starts its process, no more activity on those two drives.  I have played with hooking up the 2 drives to another sata port on the initial 2 promise cards and they ARE found, so it has to be something with the new card and unRaid.  I have noticed that during boot before unRaid, these is a new FastBuild screen that it hesitates on giving me an option to do some settings.  I went in there and it shows these 2 drives.  I get the option to Define LD, Delete and Controller config.  The 1TB is defined and listed under the RaidMode as JBOD and the 2tb is listed but not defined.  I get the option to define as Raid 0, 1, 5, 10 or JBOD.  If I try to select any of the Raids, I get messages saying more drives, etc.  I assume these should be just set at JBOD.

Yes, set them all to JBOD. 

That's what I thought so it is but no find on unRaid.  The new card is a Promise FastTrak TX 4650.

That's what I thought so it is but no find on unRaid.  The new card is a Promise FastTrak TX 4650.

It might need a different firmware update, or else, it might not be compatible.

Still looking for help.