I have the following configuration

2 IBM x335

1 FASTT200 HA

1 Disk Array RAID 10 - 1 Partition (Drive S:)
1 Disk Array Raid 1 - 2 Partitions (Drives Q: & L:)

The q: Drive and l: drive being 1 physical cluster
resource, the sql server will NOT let me place the SQL
Logs on the L: Drives because the system does not see it
as a dependency.

Nothing you can do. Cluster resources are arbitrated at the physical layer.
All logical partitions on a host-managed raid array must move together. Yet
another reason I do not recommend SCSI clusters.

--
Geoff N. Hiten
Microsoft SQL Server MVP
Senior Database Administrator
Careerbuilder.com


[quoted text, click to view]

That is behavior as expected. How you carve up your LUNs
at the disk level affects a cluster. A server cluster
only sees what the OS sees, and SQL, what the server
cluster sees.

Although you defined two logical drives, you created them
on one LUN. To the OS, if you look in Computer
Management, you will see that you have two drives on one
LUN.

Now, in a cluster, it recognizes it at the whole LUN
level, so that if you have two drives, it still shows up
as one drive. You have that drive with Q: in your main
cluster group. Drives cannot be shared across groups, as
SQL Server installs in its own group.

You need to create another LUN & drive for the SQL logs
and put it in the SQL group and make it as a dependency of
the SQL Server resource.

[quoted text, click to view]