![]() | |
![]() |
| | Thread Tools | Display Modes |
#1
| |||
| |||
|
#2
| |||
| |||
|
|
I am attempting to install my 3rd cluster into an ip5000 iscsi SAN and I am encountering some very odd behaviour. I have finally concluded after about 25 hours of testing that there is an issue with the SQL2k install handling disk volumes of, in this instance, 160GB. I initially thought this to be a Intransa or Alacritech TOE card problem. However SQL will happily install with all these components active. I am able to install SQL to a 40GB iscsi disk, but the install fails on a 160 GB disk. BTW the server is a DL585 Thoughts appreciated, DY |
#3
| |||
| |||
|
|
I don't know anything about the particular iSCSI SAN. But I don't remember having any problem with SQL2000 handling 160GB or bigger volume. We have many 200GB volumes. If the problem indeed has something to do with the volume size, it could be someting else other than SQL2000 that's having that problem. Linchi "The Lorax" <lorax (AT) nospam (DOT) nospam> wrote in message news:5h2v219tg1an4jsaqqu1t631mf7vm3atr9 (AT) 4ax (DOT) com... I am attempting to install my 3rd cluster into an ip5000 iscsi SAN and I am encountering some very odd behaviour. I have finally concluded after about 25 hours of testing that there is an issue with the SQL2k install handling disk volumes of, in this instance, 160GB. I initially thought this to be a Intransa or Alacritech TOE card problem. However SQL will happily install with all these components active. I am able to install SQL to a 40GB iscsi disk, but the install fails on a 160 GB disk. BTW the server is a DL585 Thoughts appreciated, DY |
#4
| |||
| |||
|
|
Thanks. I have another server installed without any issues of 160 GB on another SAN. I think there may be a problem with the iscsi driver and the ip san. However it would be good to know what sql does when it is preparing to install. I am hoping someone at MS might take a look at this. DY On Thu, 10 Mar 2005 01:33:59 -0500, "Linchi Shea" linchi_shea (AT) NOSPAM (DOT) ml.com> wrote: I don't know anything about the particular iSCSI SAN. But I don't remember having any problem with SQL2000 handling 160GB or bigger volume. We have many 200GB volumes. If the problem indeed has something to do with the volume size, it could be someting else other than SQL2000 that's having that problem. Linchi "The Lorax" <lorax (AT) nospam (DOT) nospam> wrote in message news:5h2v219tg1an4jsaqqu1t631mf7vm3atr9 (AT) 4ax (DOT) com... I am attempting to install my 3rd cluster into an ip5000 iscsi SAN and I am encountering some very odd behaviour. I have finally concluded after about 25 hours of testing that there is an issue with the SQL2k install handling disk volumes of, in this instance, 160GB. I initially thought this to be a Intransa or Alacritech TOE card problem. However SQL will happily install with all these components active. I am able to install SQL to a 40GB iscsi disk, but the install fails on a 160 GB disk. BTW the server is a DL585 Thoughts appreciated, DY |
#5
| |||
| |||
|
|
Hi I installed on a 2.4TB volume yesterday. Make sure that your volume is a basic disk and not a dynamic disk. Regards -------------------------------- Mike Epprecht, Microsoft SQL Server MVP Zurich, Switzerland IM: mike (AT) epprecht (DOT) net MVP Program: http://www.microsoft.com/mvp Blog: http://www.msmvps.com/epprecht/ "The Lorax" <lorax (AT) nospam (DOT) nospam> wrote in message news:mp2031drbj2ammrqb8qq0e8a6q35q0r38g (AT) 4ax (DOT) com... Thanks. I have another server installed without any issues of 160 GB on another SAN. I think there may be a problem with the iscsi driver and the ip san. However it would be good to know what sql does when it is preparing to install. I am hoping someone at MS might take a look at this. DY |
#6
| |||
| |||
|
#7
| |||
| |||
|
|
Hi I installed on a 2.4TB volume yesterday. Make sure that your volume is a basic disk and not a dynamic disk. Regards -------------------------------- Mike Epprecht, Microsoft SQL Server MVP Zurich, Switzerland IM: mike (AT) epprecht (DOT) net MVP Program: http://www.microsoft.com/mvp Blog: http://www.msmvps.com/epprecht/ "The Lorax" <lorax (AT) nospam (DOT) nospam> wrote in message news:mp2031drbj2ammrqb8qq0e8a6q35q0r38g (AT) 4ax (DOT) com... Thanks. I have another server installed without any issues of 160 GB on another SAN. I think there may be a problem with the iscsi driver and the ip san. However it would be good to know what sql does when it is preparing to install. I am hoping someone at MS might take a look at this. DY On Thu, 10 Mar 2005 01:33:59 -0500, "Linchi Shea" linchi_shea (AT) NOSPAM (DOT) ml.com> wrote: I don't know anything about the particular iSCSI SAN. But I don't remember having any problem with SQL2000 handling 160GB or bigger volume. We have many 200GB volumes. If the problem indeed has something to do with the volume size, it could be someting else other than SQL2000 that's having that problem. Linchi "The Lorax" <lorax (AT) nospam (DOT) nospam> wrote in message news:5h2v219tg1an4jsaqqu1t631mf7vm3atr9 (AT) 4ax (DOT) com... I am attempting to install my 3rd cluster into an ip5000 iscsi SAN and I am encountering some very odd behaviour. I have finally concluded after about 25 hours of testing that there is an issue with the SQL2k install handling disk volumes of, in this instance, 160GB. I initially thought this to be a Intransa or Alacritech TOE card problem. However SQL will happily install with all these components active. I am able to install SQL to a 40GB iscsi disk, but the install fails on a 160 GB disk. BTW the server is a DL585 Thoughts appreciated, DY |
#8
| |||
| |||
|
|
Mike, you talking about a single 2.4TB volume??? That's brave! Linchi "Mike Epprecht (SQL MVP)" <mike (AT) epprecht (DOT) net> wrote in message news:uo$TMsbJFHA.3356 (AT) TK2MSFTNGP12 (DOT) phx.gbl... Hi I installed on a 2.4TB volume yesterday. Make sure that your volume is a basic disk and not a dynamic disk. Regards -------------------------------- Mike Epprecht, Microsoft SQL Server MVP Zurich, Switzerland IM: mike (AT) epprecht (DOT) net MVP Program: http://www.microsoft.com/mvp Blog: http://www.msmvps.com/epprecht/ "The Lorax" <lorax (AT) nospam (DOT) nospam> wrote in message news:mp2031drbj2ammrqb8qq0e8a6q35q0r38g (AT) 4ax (DOT) com... Thanks. I have another server installed without any issues of 160 GB on another SAN. I think there may be a problem with the iscsi driver and the ip san. However it would be good to know what sql does when it is preparing to install. I am hoping someone at MS might take a look at this. DY On Thu, 10 Mar 2005 01:33:59 -0500, "Linchi Shea" linchi_shea (AT) NOSPAM (DOT) ml.com> wrote: I don't know anything about the particular iSCSI SAN. But I don't remember having any problem with SQL2000 handling 160GB or bigger volume. We have many 200GB volumes. If the problem indeed has something to do with the volume size, it could be someting else other than SQL2000 that's having that problem. Linchi "The Lorax" <lorax (AT) nospam (DOT) nospam> wrote in message news:5h2v219tg1an4jsaqqu1t631mf7vm3atr9 (AT) 4ax (DOT) com... I am attempting to install my 3rd cluster into an ip5000 iscsi SAN and I am encountering some very odd behaviour. I have finally concluded after about 25 hours of testing that there is an issue with the SQL2k install handling disk volumes of, in this instance, 160GB. I initially thought this to be a Intransa or Alacritech TOE card problem. However SQL will happily install with all these components active. I am able to install SQL to a 40GB iscsi disk, but the install fails on a 160 GB disk. BTW the server is a DL585 Thoughts appreciated, DY |
![]() |
| Thread Tools | |
| Display Modes | |
| |