Mapping QD6000 Disks to LUNs and Logs

 

There will be times when you may need to map individual disk drives from their hardware location through to the associated drawers and slots in a Major Event Log or to the RAID volumes and O/S LUNs they belong to.

 

Hardware Layout

 

The QD6000 consists of 5 drawers each with 12 drive slots. The drawers are numbered 1-5 from top to bottom. Within them the slots are numbered front to back, left to right, 1-12. (See lower diagram).

 

Disks are logically grouped in RAID sets vertically in side-by-side pairs in each drawer giving 10 drives per RAID set. As we use RAID 6 and no more than 2 drives are in any one drawer we can lose a whole drawer potentially without losing the filesystems relying on any of the disks in it.

 

Extracted from the StorNext Q-Series Storage Installation Reference Guide the following shows the layout :

 

 

IE slots 1 and 4 in each of the 5 drawers belong to the first RAID volume. (Red). Slots 7 and 8 belong to the second volume etc.

 

Logical Configuration

 

Within the logs, notably the storageArrayProfile.txt and majorEventLog.txt, the individual disks are addressed by tray, drawer and slot, eg “Tray 99, Drawer 2, Slot 5”. From there the disks are mapped to their RAID volume, volume group and LUN. The following example is from a unit with one expansion set :

 

Volume            Volume      LUN   Drive Drawer      Expansion

                        Group

TRAY_99_VOL_1A    0           0     1+4   1-5         Base

TRAY_99_VOL_1B    0           1     1+4   1-5         Base

TRAY_99_VOL_2A    1           2     7+10  1-5         Base

TRAY_99_VOL_2B    1           3     7+10  1-5         Base

TRAY_99_VOL_3A    2           4     2+5   1-5         E1

TRAY_99_VOL_3B    2           5     2+5   1-5         E1

 

The volumes are paired A and B for each of the controllers providing redundant access to the data in the event of a failure of a path.

 

 

Major Event Log Example

 

The following show examples from the majorEventLog.txt where you’ll see mention of drawers and slots which you can use the above information to identify the hardware components.

 

A disk drive spinning down in slot 5 of the second drawer :

 

Date/Time: 28/04/14 11:55:52

Sequence number: 899392

Event type: 2226

Event category: Internal

Priority: Informational

Event needs attention: false

Event send alert: false

Event visibility: true

Description: Drive spun down

Event specific codes: 0/0/0

Component type: Drive

Component location: Tray 99, Drawer 2, Slot 5

Logged by: Controller in slot B

 

A drive drawer being opened, possibly to replace a drive. (A similar message is posted when a drawer is closed) :

 

Date/Time: 28/04/14 12:01:19

Sequence number: 899398

Event type: 2857

Event category: Internal

Priority: Critical

Event needs attention: true

Event send alert: true

Event visibility: true

Description: Drawer open or removed

Event specific codes: 0/0/0

Component type: Drawer

Component location: Tray 99, Drawer 2

Logged by: Controller in slot A