D-Link Forums
The Graveyard - Products No Longer Supported => D-Link Storage => DSN-3200 => Topic started by: tenmast on March 09, 2009, 05:36:12 AM
-
I am getting this return code when I try to grow one of my volumes, any idea what this means and how do I correct what ever is causing the problem.
ARussell
-
What firmware version are you running? Where exactly are you receiving that code.. from the logs?
-
i am running firmware version 2.5.2.81, and yes it is in the logs.
When i actually try to grow the volume the message that I get at that time is "Failed to grow volume" and the log shows the Unknown CMP message.
ARussell
This is the actual message from the log
Category:
Management
Severity:
Warning
EventID:
Warning Text
Source:
SMIS
Summary:
Unknown CMP return code (37) returned
Sequence ID
1595
Text
Unknown CMP return code (37) returned.
File
CMPMessageHeader
Func
getReturnCode
Line
137
-
37 eh?
What type of volume are you growing? how much are you growing it.how much space does each drive have?
-
IT is a parity volume, it 2TB now with three drives i am trying to grow it to 3TB across 4 drives. All are 1TB drives.
-
What kind of drives are you using? (Who is the manufacturer)
-
Western Digital
-
Can you grow the volume to something less than a TB. Try 500GB and see if that makes a difference. Also are you trying to grow the volume from the management port? Are all the drives in the SAN the same size or are they different?
-
IT is currently 2TB, so I cannot grow it to anything less I can try growing a different volume.
All of the drives in the unit are not the same size but all of the drives that I am trying to use with the initial volume are of the same size all are 1TB.
-
I don't mean to reduce from 2TB.. Try adding to the 2TB but not entering the full 3TB (e.g. 2.5TB). Or see if you can do it in GB's
-
Ok,
I tried growing the volume from 2000GB to 2500GB same error, then i went down the list per se untill I got to 2100 and it worked.
This is a bit strange especially since I ahve almost 2TB of space available across the entire unit. After it finishes this task I will try to grow it by another 200GB and see what happens
-
Thanks.. please do keep us posted. I'd like to try and replicate your setup here in house. What raid settings do you have again? Any additional info you think that will be helpful will be appreciated. I want to try and replicate your setup exactly how you have it.
-
Our Xstack is populated with 13 drives.
4 - WDC 2500ys 250GB - in a Stripe/Mirror which is 464.4GB in size
The other eight drives have multiple extents that support 4 other volumes.
1 - The 2TB volume that is now 2.2TB after issueing two grow commands of 1000MB
2 - A 800GB volume that supports a Xen Virtual Server
3 - A 250GB Volume that supports a backup for some workstations
4 - Last but not least a 100GB volume taht supports the web server farm.
As I mentioned before it is on firmeware version 2.5.1.81
All of the disks are WD ranging from 250Gb to 1TB
And I have a total of 5 connected Initiators 1 per volume
I have 7.05TB availalbe and it is reporting 5.44 in use (although I cannot account for that)
and I have one drive that seems to be stuck in a "Down Drive" state that I cannot cancel or resume
Hopefully this is enough information.
-
I forgot to mention that the last 4 volumes are all parity ( Should be raid 5) the unit handled the parity settings
-
Can you post a screenshot of your physical storage tab?
-
Tried to post tells me that the attachement dir is not writable.
-
Try to print screen and go to a website like photobucket and post the link here.
-
Ok, try this out.
http://i691.photobucket.com/albums/vv278/Tekin2/Drives.jpg
-
What kind of drives are connected to drives 5 and 8? I remember you said Western Digital earlier in the thread but wanted to confirm again? Are all the drives the same brand?
-
After strange unit reset, it restarted itself for no appaent reason, the error code is gone and drive 8 started to resume the "Down" that it was stuck at.
At this moment the unit is performing without an issue. Very strange behavior.
Thanks for the help.
-
interesting.. it appears it just needed a clean boot.
-
Ok, try this out.
http://i691.photobucket.com/albums/vv278/Tekin2/Drives.jpg
Drive 05 is not Initialized
usually from Pulling the Physical Drive out of the system then replacing it back into the system.
Drive 08 is [DriveDown] a state that happens when the admin sets the drive to Down Or the S.M.A.R.T caught an Error and brought the volume down.
On system boot all drives that are not initlized by the system will be, clearing the state on 05
Rebooting the system will Reset the S.M.A.R.T Threshold counters for volumes and bringing it out of the DriveDown state clearing 08.
Check the S.M.A.R.T response time for Drive08, if its anything higher than 500MS there is a problem with that volume.
-
Ok, try this out.
http://i691.photobucket.com/albums/vv278/Tekin2/Drives.jpg
Thanks for sharing the link!