DX4000 4x4TB - reset to factory ("Recreate my storage") - only using 3x4TB

Hello,
we tried to reset a DX4000 which originally had 4 drives with 4TB.

Because we do not need so much space on the NAS we removed one of
the drives just using 3 of them. (One in reserve in case of trouble in the future :wink: )

We followed exactly the description in the manual and
everything seemed to work fine …

But now we have the message “Initialzing OK Searching …” on the display
of the DX4000 for several days!! and nothing seems to happen.

Could it be that the removed drive makes trouble (initializing with 3x4TB instead of 4x4TB)?
Or in other words is it possible at all to intialize a 4x4TB DX4000 as 3x4TB?

Does anybody succeed in doing this?

I know that a DX4000 works with 3 drives, we have another one which was
originally delivered with 2x2TB which we expanded with a 3rd drive, by
just adding a 2TB drive ‘on the run’ and it worked perfect …

But maybe a DX4000 4x4TB is somehow different to a DX4000 2x2TB
and requires that all 4 drives are present on initializing?

best regards and thanks for your answers
Michael

Well this says it may take up to 6 days.
http://support.wdc.com/KnowledgeBase/answer.aspx?ID=9792

But I think what may happen is if it does boot it is going to complain about the missing drive. If you still have the thumb drive used in the middle step look in the wd folder for a log file. At the end look and see if you can tell if it is trying to do raid 5 with the 4 original drives.

If it is all you need to do is clean all 4 drives with diskpart, then stick 3 in the box and start over with the middle step. The drives do not forget how they were configured. It took me over 3 months to figure this out. I had 2 drives like your other box and stuck a 3rd in just to see it work, Then I tried over and over to go back to 2 drives. It would go about 5 days and then say fail

Thanks for your fast answer! :slight_smile:

We have found 2 log-files (‘recovery.log’ and ‘ServerRecovery.log’).
http://varlab.eu/downloads/WD-Forum/recovery.log
http://varlab.eu/downloads/WD-Forum/ServerRecovery.log

Inside the ‘recovery.log’ (line 768) we found this lines:

RAID Volumes

Volume 01 / 01
SerialNo:Volume0 Summary:Degraded
RaidLevel: 5 MemberDisks:04 Domains/Mirrors:01 TargetId:0x01
SizeInMB:11446336 BytesPerBlock:0x00000200 StripSize: 64KB
Action:00 Array:00 MapState:02 MigrState:00 MigrType:01 CfgStatus:0x00000000

Total Volumes = 1

RAID Arrays

Array 01 / 01
NumDisks:04 RAIDDevs:01 TotalMB:15261790 FreeMB:7
State:00 CheckBox:0x00000000

Total Arrays = 1

I think ‘MemberDisks:04’ and ‘NumDisks:04’ could be the prove of what you are saying!

That is kinda what I was expecting.
So if you have the time and are just curious you can wait and see what happens. But if it boots it is going to complain of the missing disc all the time and I am not real sure if it would run on 2 disc’s if one failed. Maybe, maybe not.

So I think you are going to have to do it again, cleaning the raid profiles from the disc(s) for it to be right. Either go ahead and abort or wait and see what happens.

This post was flagged by the community and is temporarily hidden.

OK - thanks - I will clean the 4 drives …

Just as a note, I found 5 partitions on (one of) the drive(s):

_ “Basic data partition”: 3.58 TB
_ “EFI system partition”: 100 MB
_ “Microsoft reserved partition”: 128 MB
_ “I:” 60 GB
_ “G:” 10.86 TB

“I:” is obviously the partition for the Windows system,
“Basic data partition” is the ‘real’ data partition as I guess :wink:
and “G:” is the problem, as I think, because it ‘simulates’ the complete raid
which can only have 10.86 TB if 4 drives are present - 3 drives should have much less …

Just another note:
*I had tried to add some screenshots but my (last) post was hidden (flagged by the community) *
*because of that … *
*So no pictures of my investigations - sorry!! :wink: *

They don’t like serial numbers in posts. You need to black them out.

So did the process complete or did you just go ahead and abort it?

I canceled the process and I am just cleaning the disks …

Another thing I found on one of the drives:

Sector 7814037166

3A3817D5C00: 49 6E 74 65 6C 20 52 61 - 69 64 20 49 53 4D 20 43 Intel Raid ISM C
3A3817D5C10: 66 67 20 53 69 67 2E 20 - 31 2E 33 2E 30 30 00 00 fg Sig. 1.3.00…
3A3817D5C20: DC D1 D9 76 48 02 00 00 - 6C 4A A8 2E 03 48 00 00 ÜÑÙvH…lJ¨…H…
3A3817D5C30: F8 11 00 00 10 00 00 A4 - 04 01 02 00 00 00 00 00 ø…¤…
3A3817D5C40: 47 F6 A7 2E 01 00 00 00 - 00 00 00 00 01 00 00 00 Gö§…
3A3817D5C50: 00 00 00 00 00 00 00 00 - 00 00 00 00 00 00 00 00 …
3A3817D5C60: 00 00 00 00 00 00 00 00 - 00 00 00 00 00 00 00 00 …
3A3817D5C70: 00 00 00 00 00 00 00 00 - 00 00 00 00 00 00 00 00 …
3A3817D5C80: 00 00 00 00 00 00 00 00 - 00 00 00 00 00 00 00 00 …
3A3817D5C90: 00 00 00 00 00 00 00 00 - 00 00 00 00 00 00 00 00 …
3A3817D5CA0: 00 00 00 00 00 00 00 00 - 00 00 00 00 00 00 00 00 …
3A3817D5CB0: 00 00 00 00 00 00 00 00 - 00 00 00 00 00 00 00 00 …
3A3817D5CC0: 00 00 00 00 00 00 00 00 - 00 00 00 00 00 00 00 00 …
3A3817D5CD0: 00 00 00 00 00 00 00 00 - 57 44 2D 57 43 43 35 44 …WD-WCC5D
3A3817D5CE0: 33 43 43 31 4C 56 52 00 - B0 BE C0 D1 00 00 02 00 3CC1LVR.°¾ÀÑ…
3A3817D5CF0: 3A 05 00 00 00 00 00 00 - 01 00 00 00 00 00 00 00 :…
3A3817D5D00: 00 00 00 00 00 00 00 00 - 57 44 2D 57 43 43 35 44 …WD-WCC5D
3A3817D5D10: 31 41 4C 48 59 37 4B 00 - B0 BE C0 D1 00 00 03 00 1ALHY7K.°¾ÀÑ…
3A3817D5D20: 3A 05 00 00 00 00 00 00 - 01 00 00 00 00 00 00 00 :…
3A3817D5D30: 00 00 00 00 00 00 00 00 - 57 44 2D 57 43 43 35 44 …WD-WCC5D
3A3817D5D40: 31 41 4C 48 35 5A 35 00 - B0 BE C0 D1 00 00 04 00 1ALH5Z5.°¾ÀÑ…
3A3817D5D50: 3A 05 00 00 00 00 00 00 - 01 00 00 00 00 00 00 00 :…
3A3817D5D60: 00 00 00 00 00 00 00 00 - 44 2D 57 43 43 35 44 30 …D-WCC5D0
3A3817D5D70: 43 58 59 37 50 36 3A 30 - 00 BE C0 D1 FF FF FF FF CXY7P6:0.¾ÀÑÿÿÿÿ
3A3817D5D80: 02 00 00 00 00 00 00 00 - 01 00 00 00 00 00 00 00 …
3A3817D5D90: 00 00 00 00 00 00 00 00 - 56 6F 6C 75 6D 65 30 00 …Volume0.
3A3817D5DA0: 00 00 00 00 00 00 00 00 - 00 00 42 75 05 00 00 00 …Bu…
3A3817D5DB0: 0C 00 00 00 00 00 00 00 - 00 00 01 00 01 01 00 00 …
3A3817D5DC0: 01 00 00 00 00 00 00 00 - 00 00 00 00 00 00 00 00 …
3A3817D5DD0: 00 00 00 00 00 00 00 00 - 00 00 00 00 00 00 00 00 …
3A3817D5DE0: 00 00 00 00 00 00 00 00 - 56 81 A3 03 00 00 00 00 …V.£…
3A3817D5DF0: 00 01 00 FF 00 00 00 00 - 00 00 00 00 00 00 00 00 …ÿ…

Do you think it’s enough to clean the drives or must I use “clean all” ?

We have used just clean with no problems

OK - good :slight_smile: - we will also use just clean … thanks!!

Just an update what’s going on:

After cleaning the disks we had (the usual) “Bad Storage” on the LCD
After “recreate my storage” this was fixed
(see: It show me “Bad Storage” in LCD )

Now we are in Recovery mode (since nearly 2 days :wink: ) - LCD shoes “Recovery Started” …

Did you look at the log file the second time around? It say Raid 5, three disc?

No, we didn’t, we are a little bit unsure when/if we may remove the USB-Stick,
So we started the recovery and did not touch the box (and the stick of course) … :wink:

I am talking about the thumb drive from the middle step. It uses a different thumb drive for the bottom step? I thought you were on step 3/recover now

I was not personally doing this but as far as I know the same stick was used … :frowning:

Good news, it was not the same stick, I will inspect the info from the
logfile and add the info here as soon as possible …

first it starts with

RAID Volumes

Volume 01 / 01
SerialNo:Volume0 Summary:Failed
RaidLevel: 5 MemberDisks:04 Domains/Mirrors:01 TargetId:0x01
SizeInMB:11446336 BytesPerBlock:0x00000200 StripSize: 64KB
Action:00 Array:00 MapState:03 MigrState:00 MigrType:01 CfgStatus:0x00000000

Total Volumes = 1

RAID Arrays

Array 01 / 01
NumDisks:04 RAIDDevs:01 TotalMB:15261790 FreeMB:7
State:00 CheckBox:0x00000000

Total Arrays = 1

which is really bad - still 4 disks :frowning:

a little bit later there is:

2015.11.24 18:28:02 - INFO - RaidCfg64 detected 3 drives
2015.11.24 18:28:02 - INFO - RaidCfg64 drive WD-WCC5D1ALH5Z5: port=4
2015.11.24 18:28:02 - INFO - RaidCfg64 drive WD-WCC5D1ALHY7K: port=3
2015.11.24 18:28:02 - INFO - RaidCfg64 drive WD-WCC5D3CC1LVR: port=2
2015.11.24 18:28:02 - INFO - RAID volume status is ‘FAILED’!
2015.11.24 18:28:02 - INFO - Matched drive 2 serial WD-WCC5D1ALH5Z5 model WDC WD4000F9MZ-76NVPL0 with white list entry Enterprise Storage 4 TB
2015.11.24 18:28:02 - INFO - Matched drive 1 serial WD-WCC5D1ALHY7K model WDC WD4000F9MZ-76NVPL0 with white list entry Enterprise Storage 4 TB
2015.11.24 18:28:02 - INFO - Matched drive 0 serial WD-WCC5D3CC1LVR model WDC WD4000F9MZ-76NVPL0 with white list entry Enterprise Storage 4 TB
2015.11.24 18:28:02 - WARN - Drive ‘WD-WCC5D3CC1LVR’ is not part of the RAID!
2015.11.24 18:28:02 - INFO - Checking RAID status (1): Volume Does Not Contain All Valid Drives

and then:

Delete RAID Volume…
Deleting Volume “Volume0”…Deleted

2015.11.24 18:28:05 - INFO - Deleted RAID volume ‘Volume0’
2015.11.24 18:28:10 - INFO - Re-creating RAID volume
2015.11.24 18:28:10 - INFO - C:\wdrecovery\raidcfg64.exe /Y /c:Volume0 /l:5 /ss:64 /ds:4 3 2
2015.11.24 18:28:11 - INFO - raidcfg64.exe output

and finally we have:

RAID Volumes

Volume 01 / 01
SerialNo:Volume0 Summary:Normal
RaidLevel: 5 MemberDisks:03 Domains/Mirrors:01 TargetId:0x01
SizeInMB:7630891 BytesPerBlock:0x00000200 StripSize: 64KB
Action:00 Array:00 MapState:00 MigrState:00 MigrType:00 CfgStatus:0x00000000

Total Volumes = 1

RAID Arrays

Array 01 / 01
NumDisks:03 RAIDDevs:01 TotalMB:11446342 FreeMB:5
State:00 CheckBox:0x00000000

Total Arrays = 1

which looks very good! ( RaidLevel: 5 MemberDisks:03 / NumDisks:03)

I would say it looks fine with member discs 3 at the end. The other said 4 member discs and the MB’s is lower.
I was worried you might have to do 2 drives then add the 3 since I don’t think they ever ship a box with just 3 drives they may not have planned that option.
I would say let it roll and see what happens.

Just a short update on this:

It’s now running for 8 days and still searching … :frowning: