NASD XML format - droboports/droboports.github.io GitHub Wiki
The DroboFS has a daemon process listening on ports TCP 5000, TCP 5001 and UDP 5002. When a connection is established on port 5000 using a telnet client, this is the resulting output:
DRINASD9<?xml version="1.0" encoding="utf-8"?>
<ESATMUpdate>
<mESAUpdateSignature>ESAINFO</mESAUpdateSignature>
<mESAUpdateVersion>1</mESAUpdateVersion>
<mESAUpdateSize>16131</mESAUpdateSize>
<mESAID>0db1XXXXXXXX</mESAID>
<mSerial>0db1XXXXXXXX</mSerial>
<mName>DroboFS</mName>
<mVersion>1.2.4 [4.37.51655]</mVersion>
<mReleaseDate>Jun 21 2012,08:20:51</mReleaseDate>
<mArch>ArmMarvell</mArch>
<mFirmwareFeatures>34602495</mFirmwareFeatures>
<mFirmwareTestFeatures>3</mFirmwareTestFeatures>
<mFirmwareTestState>0</mFirmwareTestState>
<mFirmwareTestValue>1</mFirmwareTestValue>
<mStatus>98304</mStatus>
<mRelayoutCount>0</mRelayoutCount>
<mTotalCapacityProtected>5928828272640</mTotalCapacityProtected>
<mUsedCapacityProtected>1751838081024</mUsedCapacityProtected>
<mFreeCapacityProtected>4176990191616</mFreeCapacityProtected>
<mTotalCapacityUnprotected>0</mTotalCapacityUnprotected>
<mUsedCapacityOS>1749728460800</mUsedCapacityOS>
<mYellowThreshold>8500</mYellowThreshold>
<mRedThreshold>9500</mRedThreshold>
<mUseUnprotectedCapacity>0</mUseUnprotectedCapacity>
<mRealTimeIntegrityChecking>0</mRealTimeIntegrityChecking>
<mStoredFirmwareTestState>0</mStoredFirmwareTestState>
<mStoredFirmwareTestValue>1</mStoredFirmwareTestValue>
<mDiskPackID>0</mDiskPackID>
<mDroboName>DroboFS</mDroboName>
<mConnectionType>0</mConnectionType>
<mSlotCountExp>8</mSlotCountExp>
<mSlotsExp>
<n0>
<mSlotNumber>0</mSlotNumber>
<mStatus>3</mStatus>
<mESAID/>
<mMake/>
<mModel/>
<mPhysicalCapacity>500107862016</mPhysicalCapacity>
</n0>
<n1>
<mSlotNumber>1</mSlotNumber>
<mStatus>3</mStatus>
<mESAID/>
<mMake/>
<mModel/>
<mPhysicalCapacity>1500301910016</mPhysicalCapacity>
</n1>
<n2>
<mSlotNumber>2</mSlotNumber>
<mStatus>3</mStatus>
<mESAID/>
<mMake/>
<mModel/>
<mPhysicalCapacity>2000398934016</mPhysicalCapacity>
</n2>
<n3>
<mSlotNumber>3</mSlotNumber>
<mStatus>3</mStatus>
<mESAID/>
<mMake/>
<mModel/>
<mPhysicalCapacity>2000398934016</mPhysicalCapacity>
</n3>
<n4>
<mSlotNumber>4</mSlotNumber>
<mStatus>3</mStatus>
<mESAID/>
<mMake/>
<mModel/>
<mPhysicalCapacity>2000398934016</mPhysicalCapacity>
</n4>
<n5>
<mSlotNumber>5</mSlotNumber>
<mStatus>128</mStatus>
<mESAID/>
<mMake/>
<mModel/>
<mPhysicalCapacity>0</mPhysicalCapacity>
</n5>
<n6>
<mSlotNumber>6</mSlotNumber>
<mStatus>128</mStatus>
<mESAID/>
<mMake/>
<mModel/>
<mPhysicalCapacity>0</mPhysicalCapacity>
</n6>
<n7>
<mSlotNumber>7</mSlotNumber>
<mStatus>128</mStatus>
<mESAID/>
<mMake/>
<mModel/>
<mPhysicalCapacity>0</mPhysicalCapacity>
</n7>
</mSlotsExp>
<mLUNUpdates>
<n0>
<mLUN>0</mLUN>
<mUniqueLUNID>1000</mUniqueLUNID>
<mTargetName/>
<mLUNName/>
<mMaximumLUNSize>17592186044416</mMaximumLUNSize>
<mUsedCapacityOS>1749728460800</mUsedCapacityOS>
<mFlags>2</mFlags>
<mPartitionCount>2</mPartitionCount>
<mPartitionType>3</mPartitionType>
<mPartitionFormat>16</mPartitionFormat>
<mShareState>0</mShareState>
<mNextAvailableID>1001</mNextAvailableID>
<mUsedCapacityOS>1749728460800</mUsedCapacityOS>
<mInitiatorCount>0</mInitiatorCount>
<mLoggedIn>1</mLoggedIn>
</n0>
</mLUNUpdates>
<mFirmwareFeatureStates>6</mFirmwareFeatureStates>
<mLUNCount>1</mLUNCount>
<mMaxLUNs>16</mMaxLUNs>
<mSledName>DroboFS</mSledName>
<mSledVersion/>
<mShareCount>0</mShareCount>
<mShareInfo/>
<mSledStatus>0</mSledStatus>
<mSledSerial/>
<mDiskPackStatus>0</mDiskPackStatus>
<DNASStatus>6</DNASStatus>
<DNASConfigVersion>15</DNASConfigVersion>
<DNASDroboAppsShared>1</DNASDroboAppsShared>
<DNASDiskPackId>D0273FB5F0076B12</DNASDiskPackId>
<DNASFeatureTable>7</DNASFeatureTable>
<DNASEmailConfigEnabled>1</DNASEmailConfigEnabled>
</ESATMUpdate>
If the connection is kept open, the DroboFS will resend this document with updated information every 10~20 seconds.
This is the XML output for the Drobo5N:
DRINASDa<?xml version="1.0" encoding="utf-8"?>
<ESATMUpdate>
<mESAUpdateSignature>ESAINFO</mESAUpdateSignature>
<mESAUpdateVersion>1</mESAUpdateVersion>
<mESAUpdateSize>29153</mESAUpdateSize>
<mESAID>drb1XXXXXXXXXXX</mESAID>
<mSerial>drb1XXXXXXXXXXX</mSerial>
<mName>Drobo5N</mName>
<mVersion>3.1.0 [8.30.62261]</mVersion>
<mReleaseDate>Mar 26 2013,00:13:44</mReleaseDate>
<mArch>ArmMarvell</mArch>
<mFirmwareFeatures>2456813055</mFirmwareFeatures>
<extFtr>47</extFtr>
<mFirmwareTestFeatures>3</mFirmwareTestFeatures>
<mFirmwareTestState>0</mFirmwareTestState>
<mFirmwareTestValue>1</mFirmwareTestValue>
<mStatus>32768</mStatus>
<mRelayoutCount>0</mRelayoutCount>
<mDoubleDegradedCnt>0</mDoubleDegradedCnt>
<mTotalCapacityProtected>5438248058880</mTotalCapacityProtected>
<mUsedCapacityProtected>4329232494592</mUsedCapacityProtected>
<mFreeCapacityProtected>1109015564288</mFreeCapacityProtected>
<mTotalCapacityUnprotected>0</mTotalCapacityUnprotected>
<mUsedCapacityOS>4311686946816</mUsedCapacityOS>
<mTotalCapacityPT>0</mTotalCapacityPT>
<mUsedCapacityPT>0</mUsedCapacityPT>
<mYellowThreshold>8500</mYellowThreshold>
<mRedThreshold>9500</mRedThreshold>
<mUseUnprotectedCapacity>0</mUseUnprotectedCapacity>
<mRealTimeIntegrityChecking>0</mRealTimeIntegrityChecking>
<mStoredFirmwareTestState>0</mStoredFirmwareTestState>
<mStoredFirmwareTestValue>1</mStoredFirmwareTestValue>
<mDiskPackID>1116661887715456451</mDiskPackID>
<mDroboName>Drobo5N</mDroboName>
<mConnectionType>7</mConnectionType>
<mSlotCountExp>6</mSlotCountExp>
<mSlotsExp>
<n0>
<mESAID>drb1XXXXXXXXXXX</mESAID>
<mSlotNumber>0</mSlotNumber>
<mStatus>3</mStatus>
<mErrorCount>0</mErrorCount>
<mDiskState>16</mDiskState>
<mDiskType>0</mDiskType>
<mTemperature>0</mTemperature>
<mMake>WDC WD30EFRX-68A</mMake>
<mDiskFwRev>80.00A8</mDiskFwRev>
<mSerial>WD-WMC1TXXXXXX</mSerial>
<mManagedCapacity>0</mManagedCapacity>
<mPhysicalCapacity>3000592982016</mPhysicalCapacity>
<SSDLifeRemaining>100</SSDLifeRemaining>
</n0>
<n1>
<mESAID>drb1XXXXXXXXXXX</mESAID>
<mSlotNumber>1</mSlotNumber>
<mStatus>3</mStatus>
<mErrorCount>0</mErrorCount>
<mDiskState>16</mDiskState>
<mDiskType>0</mDiskType>
<mTemperature>0</mTemperature>
<mMake>WDC WD30EFRX-68A</mMake>
<mDiskFwRev>80.00A8</mDiskFwRev>
<mSerial>XXXX</mSerial>
<mManagedCapacity>0</mManagedCapacity>
<mPhysicalCapacity>3000592982016</mPhysicalCapacity>
<SSDLifeRemaining>100</SSDLifeRemaining>
</n1>
<n2>
<mESAID>drb1XXXXXXXXXXX</mESAID>
<mSlotNumber>2</mSlotNumber>
<mStatus>3</mStatus>
<mErrorCount>0</mErrorCount>
<mDiskState>16</mDiskState>
<mDiskType>0</mDiskType>
<mTemperature>0</mTemperature>
<mMake>WDC WD5000AAKS-2</mMake>
<mDiskFwRev>01.03B0</mDiskFwRev>
<mSerial>XXXX</mSerial>
<mManagedCapacity>0</mManagedCapacity>
<mPhysicalCapacity>500107862016</mPhysicalCapacity>
<SSDLifeRemaining>100</SSDLifeRemaining>
</n2>
<n3>
<mESAID>drb1XXXXXXXXXXX</mESAID>
<mSlotNumber>3</mSlotNumber>
<mStatus>3</mStatus>
<mErrorCount>0</mErrorCount>
<mDiskState>16</mDiskState>
<mDiskType>0</mDiskType>
<mTemperature>0</mTemperature>
<mMake>WDC WD5000AAKS-2</mMake>
<mDiskFwRev>01.03B0</mDiskFwRev>
<mSerial>XXXX</mSerial>
<mManagedCapacity>0</mManagedCapacity>
<mPhysicalCapacity>500107862016</mPhysicalCapacity>
<SSDLifeRemaining>100</SSDLifeRemaining>
</n3>
<n4>
<mESAID>drb1XXXXXXXXXXX</mESAID>
<mSlotNumber>4</mSlotNumber>
<mStatus>3</mStatus>
<mErrorCount>0</mErrorCount>
<mDiskState>16</mDiskState>
<mDiskType>0</mDiskType>
<mTemperature>0</mTemperature>
<mMake>SAMSUNG HD154UI</mMake>
<mDiskFwRev>1AG0111</mDiskFwRev>
<mSerial>XXXX</mSerial>
<mManagedCapacity>0</mManagedCapacity>
<mPhysicalCapacity>1500301910016</mPhysicalCapacity>
<SSDLifeRemaining>100</SSDLifeRemaining>
</n4>
<n5>
<mESAID>drb1XXXXXXXXXXX</mESAID>
<mSlotNumber>5</mSlotNumber>
<mStatus>134</mStatus>
<mErrorCount>0</mErrorCount>
<mDiskState>35</mDiskState>
<mDiskType>4</mDiskType>
<mTemperature>0</mTemperature>
<mMake>KINGSTON SMS200SSATA</mMake>
<mDiskFwRev>507KC4</mDiskFwRev>
<mSerial>XXXX</mSerial>
<mManagedCapacity>0</mManagedCapacity>
<mPhysicalCapacity>30016659456</mPhysicalCapacity>
<SSDLifeRemaining>100</SSDLifeRemaining>
</n5>
<n5>
<mESAID>drb1XXXXXXXXXXX</mESAID>
<mSlotNumber>5</mSlotNumber>
<mStatus>128</mStatus>
<mErrorCount>0</mErrorCount>
<mDiskState>0</mDiskState>
<mDiskType>0</mDiskType>
<mTemperature>0</mTemperature>
<mMake/>
<mDiskFwRev/>
<mSerial/>
<mManagedCapacity>0</mManagedCapacity>
<mPhysicalCapacity>0</mPhysicalCapacity>
<SSDLifeRemaining>0</SSDLifeRemaining>
</n5>
</mSlotsExp>
<mLUNUpdates>
<n0>
<mLUN>0</mLUN>
<mUniqueLUNID>1000</mUniqueLUNID>
<mTargetName/>
<mLUNName/>
<mMaximumLUNSize>17592186044416</mMaximumLUNSize>
<mInitiatorNames/>
<ExtraInitatorInfo>0</ExtraInitatorInfo>
<mUsedCapacityOS>0</mUsedCapacityOS>
<mFlags>0</mFlags>
<mPartitionCount>2</mPartitionCount>
<mPartitionType>3</mPartitionType>
<mPartitionFormat>16</mPartitionFormat>
<mShareState>0</mShareState>
<mNextAvailableID>1001</mNextAvailableID>
<mInitiatorCount>0</mInitiatorCount>
<mLoggedInState>2</mLoggedInState>
</n0>
</mLUNUpdates>
<mFirmwareFeatureStates>6</mFirmwareFeatureStates>
<mLUNCount>1</mLUNCount>
<mMaxLUNs>16</mMaxLUNs>
<mSledName>Drobo5N</mSledName>
<mSledVersion/>
<mShareCount>0</mShareCount>
<mShareInfo/>
<mSledStatus>0</mSledStatus>
<mSledSerial/>
<mDiskPackStatus>0</mDiskPackStatus>
<LoggedinUsername/>
<mDeviceType>10</mDeviceType>
<DNASStatus>6</DNASStatus>
<DNASConfigVersion>14</DNASConfigVersion>
<DNASDroboAppsShared>0</DNASDroboAppsShared>
<DNASDiskPackId>0F7F2E120F7F35C3</DNASDiskPackId>
<DNASFeatureTable>7</DNASFeatureTable>
<DNASEmailConfigEnabled>1</DNASEmailConfigEnabled>
<DroboAppErrors>0</DroboAppErrors>
</ESATMUpdate>
This is the Drobo5N, firmware 3.2.0:
DRINASD<?xml version="1.0" encoding="utf-8"?>
<ESATMUpdate>
<mESAUpdateSignature>ESAINFO</mESAUpdateSignature>
<mESAUpdateVersion>1</mESAUpdateVersion>
<mESAUpdateSize>29157</mESAUpdateSize>
<mESAID>drbXXXXXXXXXXXX</mESAID>
<mSerial>drbXXXXXXXXXXXX</mSerial>
<mName>Drobo5N</mName>
<mVersion>3.2.0 [8.45.72385]</mVersion>
<mReleaseDate>Jan 20 2015,22:11:47</mReleaseDate>
<mArch>ArmMarvell</mArch>
<mFirmwareFeatures>2456813055</mFirmwareFeatures>
<extFtr>303</extFtr>
<mFirmwareTestFeatures>3</mFirmwareTestFeatures>
<mFirmwareTestState>0</mFirmwareTestState>
<mFirmwareTestValue>1</mFirmwareTestValue>
<mStatus>98304</mStatus>
<mRelayoutCount>0</mRelayoutCount>
<mDoubleDegradedCnt>0</mDoubleDegradedCnt>
<mLatestUELGenNumber>956301312</mLatestUELGenNumber>
<mTotalCapacityProtected>11929579683840</mTotalCapacityProtected>
<mUsedCapacityProtected>6662803726336</mUsedCapacityProtected>
<mFreeCapacityProtected>5266775957504</mFreeCapacityProtected>
<mTotalCapacityUnprotected>0</mTotalCapacityUnprotected>
<mUsedCapacityOS>6645038243840</mUsedCapacityOS>
<mTotalCapacityPT>0</mTotalCapacityPT>
<mUsedCapacityPT>0</mUsedCapacityPT>
<mYellowThreshold>8500</mYellowThreshold>
<mRedThreshold>9500</mRedThreshold>
<mUseUnprotectedCapacity>0</mUseUnprotectedCapacity>
<mRealTimeIntegrityChecking>0</mRealTimeIntegrityChecking>
<mStoredFirmwareTestState>0</mStoredFirmwareTestState>
<mStoredFirmwareTestValue>1</mStoredFirmwareTestValue>
<mDiskPackID>1116661887715456451</mDiskPackID>
<mDroboName>Drobo5N</mDroboName>
<mConnectionType>7</mConnectionType>
<mSlotCountExp>6</mSlotCountExp>
<mSlotsExp>
<n0>
<mESAID>drbXXXXXXXXXXXX</mESAID>
<mSlotNumber>0</mSlotNumber>
<mStatus>3</mStatus>
<mErrorCount>0</mErrorCount>
<mDiskState>16</mDiskState>
<mDiskType>0</mDiskType>
<mTemperature>0</mTemperature>
<mMake>WDC WD30EFRX-68A</mMake>
<mDiskFwRev>80.00A80</mDiskFwRev>
<mSerial>XXXX</mSerial>
<mManagedCapacity>0</mManagedCapacity>
<mPhysicalCapacity>3000592982016</mPhysicalCapacity>
<SSDLifeRemaining>100</SSDLifeRemaining>
</n0>
<n1>
<mESAID>drbXXXXXXXXXXXX</mESAID>
<mSlotNumber>1</mSlotNumber>
<mStatus>3</mStatus>
<mErrorCount>0</mErrorCount>
<mDiskState>16</mDiskState>
<mDiskType>0</mDiskType>
<mTemperature>0</mTemperature>
<mMake>WDC WD30EFRX-68A</mMake>
<mDiskFwRev>80.00A80</mDiskFwRev>
<mSerial>XXXX</mSerial>
<mManagedCapacity>0</mManagedCapacity>
<mPhysicalCapacity>3000592982016</mPhysicalCapacity>
<SSDLifeRemaining>100</SSDLifeRemaining>
</n1>
<n2>
<mESAID>drbXXXXXXXXXXXX</mESAID>
<mSlotNumber>2</mSlotNumber>
<mStatus>3</mStatus>
<mErrorCount>0</mErrorCount>
<mDiskState>16</mDiskState>
<mDiskType>0</mDiskType>
<mTemperature>0</mTemperature>
<mMake>WDC WD30EFRX-68A</mMake>
<mDiskFwRev>80.00A80</mDiskFwRev>
<mSerial>XXXX</mSerial>
<mManagedCapacity>0</mManagedCapacity>
<mPhysicalCapacity>3000592982016</mPhysicalCapacity>
<SSDLifeRemaining>100</SSDLifeRemaining>
</n2>
<n3>
<mESAID>drbXXXXXXXXXXXX</mESAID>
<mSlotNumber>3</mSlotNumber>
<mStatus>3</mStatus>
<mErrorCount>0</mErrorCount>
<mDiskState>16</mDiskState>
<mDiskType>0</mDiskType>
<mTemperature>0</mTemperature>
<mMake>WDC WD30EFRX-68E</mMake>
<mDiskFwRev>80.00A80</mDiskFwRev>
<mSerial>XXXX</mSerial>
<mManagedCapacity>0</mManagedCapacity>
<mPhysicalCapacity>3000592982016</mPhysicalCapacity>
<SSDLifeRemaining>100</SSDLifeRemaining>
</n3>
<n4>
<mESAID>drbXXXXXXXXXXXX</mESAID>
<mSlotNumber>4</mSlotNumber>
<mStatus>3</mStatus>
<mErrorCount>0</mErrorCount>
<mDiskState>16</mDiskState>
<mDiskType>0</mDiskType>
<mTemperature>0</mTemperature>
<mMake>WDC WD30EFRX-68E</mMake>
<mDiskFwRev>80.00A80</mDiskFwRev>
<mSerial>XXXX</mSerial>
<mManagedCapacity>0</mManagedCapacity>
<mPhysicalCapacity>3000592982016</mPhysicalCapacity>
<SSDLifeRemaining>100</SSDLifeRemaining>
</n4>
<n5>
<mESAID>drbXXXXXXXXXXXX</mESAID>
<mSlotNumber>5</mSlotNumber>
<mStatus>3</mStatus>
<mErrorCount>0</mErrorCount>
<mDiskState>32</mDiskState>
<mDiskType>4</mDiskType>
<mTemperature>0</mTemperature>
<mMake>INTEL SSDMCEAC03SATA</mMake>
<mDiskFwRev>LLLi</mDiskFwRev>
<mSerial>XXXX</mSerial>
<mManagedCapacity>0</mManagedCapacity>
<mPhysicalCapacity>30016659456</mPhysicalCapacity>
<SSDLifeRemaining>100</SSDLifeRemaining>
</n5>
</mSlotsExp>
<mLUNUpdates>
<n0>
<mLUN>0</mLUN>
<mUniqueLUNID>1000</mUniqueLUNID>
<mTargetName/>
<mLUNName/>
<mMaximumLUNSize>17592186044416</mMaximumLUNSize>
<mInitiatorNames/>
<ExtraInitatorInfo>0</ExtraInitatorInfo>
<mUsedCapacityOS>0</mUsedCapacityOS>
<mFlags>0</mFlags>
<mPartitionCount>2</mPartitionCount>
<mPartitionType>3</mPartitionType>
<mPartitionFormat>16</mPartitionFormat>
<mShareState>0</mShareState>
<mNextAvailableID>1001</mNextAvailableID>
<mInitiatorCount>0</mInitiatorCount>
<mLoggedInState>2</mLoggedInState>
</n0>
</mLUNUpdates>
<mFirmwareFeatureStates>6</mFirmwareFeatureStates>
<mLUNCount>1</mLUNCount>
<mMaxLUNs>16</mMaxLUNs>
<mSledName>Drobo5N</mSledName>
<mSledVersion/>
<mSledStatus>0</mSledStatus>
<mSledSerial/>
<mDiskPackStatus>0</mDiskPackStatus>
<LoggedinUsername/>
<mStatusEx>0</mStatusEx>
<mDeviceType>11</mDeviceType>
<mModel>Drobo 5N</mModel>
<DNASStatus>6</DNASStatus>
<DNASConfigVersion>16</DNASConfigVersion>
<DNASDroboAppsShared>0</DNASDroboAppsShared>
<DNASDiskPackId>0F7F2E120F7F35C3</DNASDiskPackId>
<DNASFeatureTable>7</DNASFeatureTable>
<DNASEmailConfigEnabled>1</DNASEmailConfigEnabled>
<DroboApps>
<DNASDroboAppsEnabled>1</DNASDroboAppsEnabled>
</DroboApps>
</ESATMUpdate>
The string DRINASD9
, DRINASDa
, DRINASD
is always sent before the document.
It seems to indicate the version of the document. The latest firmware for both DroboFS and Drobo5N (1.2.6 and 3.2.0 respectively) report DRINASD
.
Both mESAID
and mSerial
return the same data.
The field contains the device's serial number, as indicated by the file /sys/bus/dri_dnas_fake_bus/drivers/dri_dnas_scsi/serial
. In the case of the FS, the first character is replaced with a 0 (zero).
The user-friendly name of the device, as defined in the Dashboard.
The version of the firmware.
The release date of the firmware.
A string representing the CPU type (Arm) and board manufacturer (Marvell). Observed value: ArmMarvell for both DroboFS and Drobo5N.
Unknown. It is 34602495
for the DroboFS, and 2456813055
for the Drobo5N.
Could possibly be used to identify the device, but it changes with firmware versions. For example, it was 1048063
for DroboFS firmware version 1.1.1.
Unknown. Only available on Drobo5N. Value observed: 303.
Unknown.
Unknown.
Unknown.
The current status of the Drobo. The current values have been observed from a DroboFS:
Code | Hex | Status |
---|---|---|
32768 | 0x8000 | Drobo is OK. |
32772 | 0x8004 | Drobo over yellow threshold (with empty slots?). See mSlotsExp/nX/mStatus for more information. |
32774 | 0x8006 | Drobo over red threshold (with empty slots?). See mSlotsExp/nX/mStatus for more information. |
32784 | 0x8010 | Drobo has a bad drive. See mSlotsExp/nX/mStatus for more information. |
32838 | 0x8046 | A drive has been removed. See mSlotsExp/nX/mStatus for more information. |
33344 | 0x8240 | Data protection in progress. See mRelayoutCount for more information. |
98304 | 0x18000 | Unknown. Dashboard indicates Drobo is OK. |
98310 | 0x18006 | Drobo over red threshold (no empty slots?). See mSlotsExp/nX/mStatus for more information. |
98880 | 0x18240 | Data protection in progress. You may continue accessing your data, but please do not remove any drives with blinking yellow/green lights. (yellow triangle icon); Drive redundancy in critical state with no extra drives due to a failed or removed drive. Do not remove any drive. (red stop sign) |
Number of blocks (?) that still need to be processed after a disk pack change (insertion, replacement or removal of a drive).
Outside of a data relayout (a.k.a. "data protection"), this field is always zero. Once a data relayout starts, it counts down to zero. By monitoring the rate at which this number decreases it is possible to estimate the remaining time.
Unknown. Only available on Drobo5N. Value observed: 0.
Unknown. Only available on Drobo5N (with firmware 3.2.0+ ?). Value observed: 956301312.
The total usable space in bytes. This is the number that gets reported in the Dashboard as the "Total" capacity.
The total used space in bytes. This is the number that gets reported in the Dashboard as "Used Space."
This is the free space in bytes. This is the number that gets reported in the Dashboard as "Free Space."
Unknown. Assumed to be the "Reserved for expansion" space.
Unknown.
Unknown. Only available on Drobo5N. Observed value: 0.
Unknown. Only available on Drobo5N. Observed value: 0.
The percentage of used space to reach the yellow threshold. Format is XXYY
which translates to XX.YY%
. Observed value: 8500.
The percentage of used space to reach the red threshold. Format is XXYY
which translates to XX.YY%
. Observed value: 9500.
Unknown. Zero for both DroboFS and Drobo5N. Observed value: 0.
Unknown. Observed value: 0.
Unknown. Observed value: 0.
Unknown. Observed value: 1.
Zero for the DroboFS, unknown value for the Drobo5N. Probably an identificator for the current disk pack.
Seems to be the same value as mName
.
Unknown. Observed 0 on DroboFS, 7 on Drobo5N.
The number of disk slots on the device. The value is 8 for the DroboFS, and 6 for the Drobo5N.
This tag contains the detailed information about each disk slot.
Each one indicates a disk slot on the device. The numbering starts at zero for the topmost slot on the device, and increases downwards.
Older versions of the DroboFS firmware reported eight slots, although only the nodes n0 to n4 contained actual information. The latest version (1.2.6) reports 5 slots.
For both the DroboFS and Drobo5N, n0 is the topmost slot, and n4 is the bottom slot. For the Drobo5N, n5 is the mSATA slot.
Empty on DroboFS, same as first mESAID
on Drobo5N.
This is the numeric id of the slot.
Status code for the slot. These are the codes observed from a DroboFS:
Code | Hex | Status |
---|---|---|
1 | 0x01 | Used space over 95%. Replace/insert drive in this slot. Slot led is red. |
2 | 0x02 | Used space over 85%. Replace/insert drive in this slot. Slot led is yellow. |
3 | 0x03 | Everything is ok with this slot. Slot led is green. |
4 | 0x04 | Data relayout in progress. Do not remove this disk. Slot led is blinking green/yellow. |
128 | 0x80 | Slot empty. Slot led is off. |
129 | 0x81 | Disk was removed from slot. Slot led is blinking red. |
134 | 0x86 | Disk failure. Slot led is blinking red. |
Unknown. Only available on Drobo5N.
Unknown. Only available on Drobo5N. Observed values: 16 for HDDs and 32 for mSATA SSDs.
Zero for HDDs, 4 for SDDs. Only available on Drobo5N.
Unknown. Always zero. Only available on Drobo5N.
Empty on DroboFS. Manufacturer and model as reported by the disk on Drobo5N, or empty if slot is empty. For the Drobo5N this string is split and reported as "Vendor ID" and "Product ID" on the Dashboard.
Disk firmware revision, or empty if slot is empty. Only available on Drobo5N.
Disk serial number, or empty if slot is empty. Only available on Drobo5N.
Unknown. Only available on Drobo5N. Observed value: 0.
Disk capacity in bytes, or zero if slot is empty.
Unknown. Set to 100 for both HDDs and SSDs, 0 if slot is empty. Only available on Drobo5N.
Empty. Only available on DroboFS.
This tag and all its children are unknown. Probably related to thin provisioning.
It seems to indicate whether or not dual-redundancy is enabled.
Value | State |
---|---|
4 | Unknown |
6 | Single redundancy |
7 | Dual redundancy |
Indicates the number of children nodes to mLUNUpdates
.
Probably the maximum number of mLUNUpdates
children.
Seems to be the same as mName
and mDroboName
.
Unknown. Empty on both DroboFS and Drobo5N.
Unknown. Zero on both DroboFS and Drobo5N. No longer available on latest Drobo5N firmware (3.2.0).
Unknown. Empty on both DroboFS and Drobo5N. No longer available on latest Drobo5N firmware (3.2.0).
Unknown. Observed 0 on both DroboFS and Drobo5N.
Unknown. Empty on both DroboFS and Drobo5N.
Unknown. Zero on both DroboFS and Drobo5N.
Unknown. Only available on Drobo5N. Observed: empty.
Unknown. Only available on Drobo5N. Observed: 10 in older firmwares, 11 in latest (3.2.0).
Unknown. Value is always 6.
Unknown. It could be a version number for the configuration revision, i.e., some kind of timestamp.
Unknown. Observed: 1 on DroboFS, 0 on Drobo5N.
Unknown. It looks like some kind of GUID.
Unknown. Observed: 7 for both DroboFS and Drobo5N.
Unknown. Observed: 0 if no email alerts configured, 1 if email alerts configured on the device.
Unknown. Only available on older versions of the Drobo5N firmware. No longer available on the latest version (3.2.0).
Unknown.
Whether DroboApps are enabled or not.