Errors 5105-5170 when creating large datafile

Greetings.
We recently added a second RAID array to our four-way server to add another
filegroup to our 400GB database. Using SQL EM, I tried adding a new 400GB
data file to a new filegroup on this new array. It ran for about 12 hours
and then came back with the following two errors:
Error 5105: Device activation error. The physical file name
'f:\MSSQL\data\Clarity_Data2_Data.NDF' may be incorrect. Extending database
by 393000.00 MB on disk 'Clarity_Data2'.
Error 5170: Cannot create file 'f:\MSSQL\data\Clarity_Data2_Data.NDF'
because it already exists. ALTER DATABASE failed. Some disk names listed i
n
the statement were not found. Check that the names exist and are spelled
correctly before rerunning the statement. Extending database by 393000.00 M
B
on disk 'Clarity_Data2'.
First of all, the drive, folder, and now the file do exist. What happened
here to make this fail? Is there a way for me to successfully get this file
added to my database without going through the 12+ hour ALTER again?
Secondly, I would have thought that creating the new datafile would not have
taken that long to run, even though it was 400GB in size. It's a RAID 5
array on its own controller on a four-way box running Windows Server 2003.
Any thoughts?
Thanks.
Dale.
P.S. The only info I found on this in the KB mentioned the DEFAULTLOG and
DEFAULTDATA registry keys. There was no default set up for this server, so
I
don't think that is related.Was RAID array already build when you have started to add a new data file ?
I'm sorry for silly question, but when you will create an RAID array, it wil
l
accessible immediately, but RAID controller will build it up in a background
.
It always good to wait when building processs will finished before work with
new array.This actually can cause performance issue as well as accessibility
issues.
Regards.
"Dale M." wrote:

> Greetings.
> We recently added a second RAID array to our four-way server to add anothe
r
> filegroup to our 400GB database. Using SQL EM, I tried adding a new 400GB
> data file to a new filegroup on this new array. It ran for about 12 hours
> and then came back with the following two errors:
> Error 5105: Device activation error. The physical file name
> 'f:\MSSQL\data\Clarity_Data2_Data.NDF' may be incorrect. Extending databa
se
> by 393000.00 MB on disk 'Clarity_Data2'.
> Error 5170: Cannot create file 'f:\MSSQL\data\Clarity_Data2_Data.NDF'
> because it already exists. ALTER DATABASE failed. Some disk names listed
in
> the statement were not found. Check that the names exist and are spelled
> correctly before rerunning the statement. Extending database by 393000.00
MB
> on disk 'Clarity_Data2'.
> First of all, the drive, folder, and now the file do exist. What happened
> here to make this fail? Is there a way for me to successfully get this fi
le
> added to my database without going through the 12+ hour ALTER again?
> Secondly, I would have thought that creating the new datafile would not ha
ve
> taken that long to run, even though it was 400GB in size. It's a RAID 5
> array on its own controller on a four-way box running Windows Server 2003.
> Any thoughts?
> Thanks.
> Dale.
> P.S. The only info I found on this in the KB mentioned the DEFAULTLOG and
> DEFAULTDATA registry keys. There was no default set up for this server, s
o I
> don't think that is related.|||Yes, it was already built. It had been online for most of a day already.
"SkyWalker" wrote:
[vbcol=seagreen]
> Was RAID array already build when you have started to add a new data file
?
> I'm sorry for silly question, but when you will create an RAID array, it w
ill
> accessible immediately, but RAID controller will build it up in a backgrou
nd.
> It always good to wait when building processs will finished before work wi
th
> new array.This actually can cause performance issue as well as accessibili
ty
> issues.
> Regards.
> "Dale M." wrote:
>