Sign in to follow this  
forum-merlin

Disk to Slot Mapping

Recommended Posts

Hi @ All

 

as I reported in another thread, I had built my new hardware based NAS a few weeks ago.

My setup is:

AsRock Q2900M

DELL H200 SAS Controller crossflashed with LSI Firmwapre (P19) in IT Mode

5x3TB HDDs >> Volume 3

3x2TB HDDs >> Volume 2

1x2TB HDDs >> Volume 4

1x1.5TB HDD >> Volume 1

10 Disks in total and all SATA Ports used.

 

When I was inserting my Disks to the new NAS, I labeled them with a P-touch to know, which HDD is which Drive in DSM and to know in which slot they are in my case.

 

I noticed, that when attaching a Drive on Port 1 from the SAS Card, It was Disk 3. If it was Port 4 it was Disk 5 then.

So far so good!

If I added the Port 2 of the Mainboard it was Disk 2.

Also okay for me.

 

A few weeks later one of my very old Test Disks 1x2TB Volume 4 failed.

As I had expected this, I had no data on it. So no problem.

I expected, that as next one of my three 2TB in volume 2 will fail.

And it happened as expected.

 

And here is my Problem...

 

As I said, at the beginning, everything was OK and understandable for me about the Port to Disk to Slot mapping

This was the mapping when I started.

Disk 1 = SATA Port 1 on Mainboard = SLOT 1 = 1.5TB WD Disk = Volume 1

Disk 2 = SATA Port 2 on Mainboard = SLOT 2 = 2TB WD Disk = Volume 2

 

Disk 3 = SATA Port A1 on SAS Controller = SLOT 3 = 3TB Seagate = Volume 3

Disk 4 = SATA Port A2 on SAS Controller = SLOT 4 = 3TB Seagate = Volume 3

Disk 5 = SATA Port A3 on SAS Controller = SLOT 5 = 3TB Seagate = Volume 3

Disk 6 = SATA Port A4 on SAS Controller = SLOT 5 = 3TB Seagate = Volume 3

Disk 7 = SATA Port B1 on SAS Controller = SLOT 7 = 3TB Seagate = Volume 3

 

Disk 8 = SATA Port B2 on SAS Controller = SLOT 8 = 2TB WD Disk = Volume 4

Disk 9 = SATA Port B3 on SAS Controller = SLOT 9 = 2TB WD Disk = Volume 4

Disk 10 = SATA Port B4 on SAS Controller = SLOT 10 = 2TB WD Disk = Volume 4

 

 

Today it looks like this:

Disk 1 = SATA Port 1 on Mainboard = SLOT 1 = 1.5TB WD Disk = Volume 1

 

>>FAILED<< No Disk 2 = SATA Port 2 on Mainboard = SLOT 2 = 2TB WD Disk = Volume 2

 

 

Disk 3 = SATA Port B2 on SAS Controller = SLOT 8 = 2TB WD Disk = Volume 4

Disk 4 = SATA Port B3 on SAS Controller = SLOT 9 = 2TB WD Disk = Volume 4

>>FAILED<< No Disk 5 = SATA Port B4 on SAS Controller = SLOT 10 = 2TB WD Disk = Volume 4

 

Disk 6 = SATA Port A1 on SAS Controller = SLOT 3 = 3TB Seagate = Volume 3

Disk 7 = SATA Port A2 on SAS Controller = SLOT 4 = 3TB Seagate = Volume 3

Disk 8 = SATA Port A3 on SAS Controller = SLOT 5 = 3TB Seagate = Volume 3

Disk 9 = SATA Port A4 on SAS Controller = SLOT 5 = 3TB Seagate = Volume 3

Disk10 = SATA Port B1 on SAS Controller = SLOT 7 = 3TB Seagate = Volume 3

 

 

At this point, the Slots are no longer mapped to the disks as when I stared.

 

 

QUESTION:

Is it somehow possible to map the disks to the Slots?

Why has this changed?

I thought the SATA Port is the mapping, because my adding procedure at the beginning showed the disk number in relation to the SATA Port

 

 

Please let me know, what I can do now to get it sorted again.

 

otherwise, I have to label the disks with the serial numbers. and this is not what I wanted to do.

 

Thanks

merlin

Share this post


Link to post
Share on other sites

t's a known problem sadly.

 

Drives jump around all over the place.... but dont actually cause any issues.......as mdadm uses the uuid of the drives to assemle the arrays....but yes makes identifiying drives a little messy

 

.

Share this post


Link to post
Share on other sites
Sign in to follow this