ColumbiaDiver
Technical User
Hi all,
I've got a really weird one. I ran across this a while back with an HP Netserver E60 and never found an answer, but since the server wasn't being used I went on to other things.
Here's the deal. I have a server that has two Western Digital WDE 18.3 gig SCSI-3 hard drives installed in it, model WDE18300. I originally set this up as a Linux box and one day when I decided to burn an image using Drive Image the software came up and said there were 3 hard drives, which of course there wasn't. Also, the system BIOS showed 3 drives even though the SCSI BIOS scan and SCSI utils on the card only saw two. So I contacted HP thinking it was an issue with the server, they blamed PowerQuest and back and forth. So I updated the server BIOS, problem was still there I then purchased the latest and greatest copy of Drive Image, problem was still there. So I gave up for the time being thinking it was some kind of issue between the server and the hard drives.
Fast forward to the present. I decided to build a low end server into to a desktop machine using a old Intel N440BX dual P3 MB. So that's when I decided to use my old friends the WD 18.3 gig drives. Low and behold the same issue. Drive Image, Partition Magic and the MB BIOS show two drives, (when I only have one installed) and 3 drives when I have two up and running. The BIOS shows the same. There are only two physical hard drives. No partitons on the drives. Really weird. Here's what I've done to try and troubleshoot the issue:
1. Searched the web and Western Digital's site looking for anything like phantom drives - No Luck
2. Updated the MB BIOS - No Luck
3. Tried different SCSI cards, Symbios Logic (Built on the MB) and an Adaptec 2940U2W - No luck
4. Changed jumpers on the drive to force SE and disabled Paralle Protocol Request, one at a time and both at the same time - No Luck.
5. Placed an active terminator on the end of SCSI cable - no luck.
6. Tried a different SCSI cable - no luck.
This one has really got me stumped and I rely upon drive image to create easily restored images for my system, but I can't use it if I don't know what drive is the real one.
Anybody ever seen this before?
Thanks
Gordon
I've got a really weird one. I ran across this a while back with an HP Netserver E60 and never found an answer, but since the server wasn't being used I went on to other things.
Here's the deal. I have a server that has two Western Digital WDE 18.3 gig SCSI-3 hard drives installed in it, model WDE18300. I originally set this up as a Linux box and one day when I decided to burn an image using Drive Image the software came up and said there were 3 hard drives, which of course there wasn't. Also, the system BIOS showed 3 drives even though the SCSI BIOS scan and SCSI utils on the card only saw two. So I contacted HP thinking it was an issue with the server, they blamed PowerQuest and back and forth. So I updated the server BIOS, problem was still there I then purchased the latest and greatest copy of Drive Image, problem was still there. So I gave up for the time being thinking it was some kind of issue between the server and the hard drives.
Fast forward to the present. I decided to build a low end server into to a desktop machine using a old Intel N440BX dual P3 MB. So that's when I decided to use my old friends the WD 18.3 gig drives. Low and behold the same issue. Drive Image, Partition Magic and the MB BIOS show two drives, (when I only have one installed) and 3 drives when I have two up and running. The BIOS shows the same. There are only two physical hard drives. No partitons on the drives. Really weird. Here's what I've done to try and troubleshoot the issue:
1. Searched the web and Western Digital's site looking for anything like phantom drives - No Luck
2. Updated the MB BIOS - No Luck
3. Tried different SCSI cards, Symbios Logic (Built on the MB) and an Adaptec 2940U2W - No luck
4. Changed jumpers on the drive to force SE and disabled Paralle Protocol Request, one at a time and both at the same time - No Luck.
5. Placed an active terminator on the end of SCSI cable - no luck.
6. Tried a different SCSI cable - no luck.
This one has really got me stumped and I rely upon drive image to create easily restored images for my system, but I can't use it if I don't know what drive is the real one.
Anybody ever seen this before?
Thanks
Gordon