WxMan1

I just recently obtained AHS-39160, a pair of 'Twist'n'Flat' cables (one having in-dwelt U320 terminator), several LVD SCA cards, and a HDD (all of which combined are spoda do the whole mojo).

What's up with SCSI ID priority?

Does it matter where the boot device is ON the buss?

I thought SCSI-buss ID briority goes 7-0 and then from 15-8.

NOT ONLY can I NOT make out how Adaptec fingers out, but Windows appears to do just whatever the hell it wants (as if IT can want anything).

Tyrsonswood

Motherboard bios needs to be set to boot from SCSI device, then the SCSI routine rom needs to be set to point to the drive you want to be bootable. There's no actual "priority" any SCSI device in the chain can be the boot drive. During install of Windows punch F6 repetedly when prompted so you can load the SCSI driver for the card. It should load the driver and then continue with install. Let Windows do a full format on the SCSI drive at this time.

Should work....... although SCSI can be a pain like that. I've always used IDE as boot device and Windows partition and SCSI as a second drive so never had to deal with this Cr@p. If you want to boot from SCSI it may be a good idea to not have any IDE hard drives in the system as Windows will want to use it even if the hardware is set up otherwise...... You can add them back later. If you have multiple SCSI drives you can also leave out the non-boot drives until after Windows install and then add them back later.

__________________

WxMan1

What seems to be the deal is that the first physical HDD detected is the ID of the HDD defined as the boot device in the AHS-39160. Then it detects SCSI ID 4 and then the other device, e.g., ID 6, 4, 5. It makes no difference where SCSI ID 4 device is on the buss. Its even come up with the following sequence: ID 5, 4, 6.

Now, then, in diskmgmt.msc, the disks are ordered 0, 1 & 2, i.e., SCSI ID 4, 5, 6, respectively.

That can be dangerous when imaging, formatting or restoring the wrong disk number.

This is maddening.

What I'm trying figure out is how to edit the boot.ini file for dual boot. Currently the entry is:

default=multi(0)disk(0)rdisk(0)partition(1)\WINDOW S
[operating systems]
multi(0)disk(0)rdisk(0)partition(1)\WINDOWS="Windo ws Server 2003, Standard" /fastdetect /NoExecute=OptOut

But that doesn't make any sense given that Windows sees the boot device as Disk 2, i.e., third in line (0, 1 & 2). The dual-boot WinXP was installed on what windows sees as disk 0. None of that jibes with the order in which the HDD's are detected by the SCSI adapter.

WxMan1

Found a copy of boot.ini in one of my system drive image files dated 16 Aug 11. The entry corresponding to the dual-boot installation appears to be the following:

multi(0)disk(0)rdisk(2)partition(1)\WINDOWS="Micro soft Windows XP Professional" /noexecute=optin /fastdetect

So Disk 2 is actually Disk 0 in diskmgmt.msc, and Disk 0 is actually Disk 2 in diskmgmt.msc. And since SCSI ID 4 is the second physical device - of three total - detected during SCSI BIOS scan (SCSI ID 6 being detected as the first HDD), its all beginning to make sense now. No wonder SCSI ID 6 HDD is Disk 2 in diskmgmt.msc.



Not.

Tyrsonswood

__________________

WxMan1

Yes, at my expense, MERRY CHRISTMAS.

It didn't matter anyways: I got the message 'bout NTOSKRNL being corrupt or wacked or sumpn.

Dunno what's different: except that ALL of my HDD's are now U160; I guess the orginal WinXP SP3 installation is now wacked eh? WHATEVER.

The whole thing just pisses me off; I believe this is nothing more than Microfroth's doing.

WxMan1

O.k., here it is:

[boot loader]
timeout=5
default=multi(0)disk(0)rdisk(0)partition(1)\WINDOW S
[operating systems]
multi(0)disk(0)rdisk(0)partition(1)\WINDOWS="Windo ws Server 2003, Standard" /fastdetect /NoExecute=OptOut
multi(0)disk(0)rdisk(1)partition(1)\WINDOWS="Micro soft Windows XP Professional" /noexecute=optin /fastdetect
C:\cmdcons\BOOTSECT.DAT="Microsoft Windows Recovery Console" /cmdcons

...after doing the repair dance.

That boot.ini works for ME. If you can 'splain it then I'm all eyes / ears. 'Till then all I knows is what works for me.

WxMan1

'Kay; finally fingered it out.

For SCSI chain, the MS ordering of HDD is in accordance to decreasing priority.

In my case: I flipped the SCSI ID of my boot HDD & archive HDD from 6,4 to 4,6 (and changed the boot device from 6 to 4 in SCSI BIOS)

Now the SCSI host adapter detects 4,5,6; diskmgmt.msc shows Disk 0 as being my Fujitsu MAU (Disk 1 is my 'other' HDD (73 GB), and Disk 2 is the original system drive now relegated to archival duty.

Yea! Happy, happy, joy, joy!

So Win2003 R2 apparently orders HDD device numbers in accordance to device priority on the buss, i.e., lowest to highest: Disk 2 having higher priority on the buss than Disk 0.

I'd bet all of your lives that translates to WinXP; dunno if that bet would pan out with Vista or Win7.

I dunno which is worse: that I'm not sufficiently comfortable to bet my own life, or that I'm willing to gamble with other people's lives; that's for you guys to finger out (I'm happy: things are working for me now).

Tyrsonswood

Glad you got it sorted....... my stuff is still sitting on a shelf. lol

__________________