I finished testing my new mobo and so i've just moved the hard drives over to the new build.

 

Now my parity drive isn't being recognised. It makes some odd noises whilst the BIOS hangs (looking for the drive) then eventually the board will continue to post but without the disk recognised.

 

The drive is a WD 10EARS drive but I also have a data 10EARS drive which is picked up fine.

 

At first I though the drive had died but I've just plugged the drive back into the previous mobo and it's picked up straight away by both the BIOS and unRAID.

 

I'm using the same sata cable and PSU with the drive in both machines and i've tried changing the port, cable etc in the new system with ones that work with the other drive but still no joy.

 

The only thing I can think of is either unRAID has written something to the drive that would cause it or (more likely) the old gigabyte mobo

 

Any ideas?

If the new BIOS does not see the drive, unRAID will not either.

 

Joe L.

The old motherboard detects the HDD fine as does unRAID if booted on the system.

The old motherboard detects the HDD fine as does unRAID if booted on the system.

It does not matter unless the NEW BIOS on the NEW motherboard recognizes the disk.

You might need a BIOS update.  You might need to set a BIOS option.  It all depends on the disk controller on the NEW motherboard and if it recognizes your disk.

The BIOS on the new mobo is the latest version and an identical disk is recognised with no probs.

 

The only difference I can see is that this disk was the parity drive and was installed in port 1 on the old gigabyte board

The BIOS on the new mobo is the latest version and an identical disk is recognised with no probs.

 

The only difference I can see is that this disk was the parity drive and was installed in port 1 on the old gigabyte board

Then the disk might be defective. Or a different firmware version.

Firmware is the same.

 

Running some diagnostics on the drive.

 

See what happens

Drive was defective. Failed the diagnostics