Unsolved
This post is more than 5 years old
8 Posts
0
27721
October 10th, 2007 19:00
No Boot, 'Device set to narrow' using Adaptec u320 SCSI
Dell Precision 360 won't boot and error message states that 'Device set to narrow'.
It's a Raid 1 array with 2 Seagate drives using SCSI ultra320 card.
I have downloaded the drive manual and there is no way to set the drives to narrow SCSI, furthermore, the card is automatically conifgured to use Wide SCSI so I can understand why this problem is occuring.
Can't access BIOS for card or for motherboard, have tried known good keyboard.
Can't access safe mode or last known good configuration.
Anyone got any advice?
Is it possible that the cable could be the problem? One of hte pins on one of the surplus connecters is bent but the machine has not been booting since before that occured.
Bit stuck here and would appreciate any advice......
It's a Raid 1 array with 2 Seagate drives using SCSI ultra320 card.
I have downloaded the drive manual and there is no way to set the drives to narrow SCSI, furthermore, the card is automatically conifgured to use Wide SCSI so I can understand why this problem is occuring.
Can't access BIOS for card or for motherboard, have tried known good keyboard.
Can't access safe mode or last known good configuration.
Anyone got any advice?
Is it possible that the cable could be the problem? One of hte pins on one of the surplus connecters is bent but the machine has not been booting since before that occured.
Bit stuck here and would appreciate any advice......
No Events found!
Dev Mgr
6 Operator
•
9.3K Posts
0
October 11th, 2007 11:00
Disconnect the scsi cable from the scsi controller and see if you can then get into bios for the card and motherboard. If so, the card is most likely just fine and you're down to the cable and/or harddrive. Make sure you have a terminator on the cable (some drives have a jumper to do termination, but you generally just want to use an active terminator on the cable).
If you have a spare cable around with a terminator, try swapping this. If you don't, try 1 drive at a time.
Obviously; make sure the drives don't have conflicting scsi IDs.