Sas enclosure not detected dsm 6.2.3

[kaneelschep]

Hi all.

 

I have a long working 6.2.3 system.

It has an lsi 9211sas card in it with 7 disks.

 

Now i got another 9211 with an hp sas enclosure. Basicly a half cut of an hp dl180.

 

I tested the sas controller and enclosure with a fresh install of latest  tinycoreredpill dsm 7.2. On some i3 i had laying around.

It all worked fine. No issues.

Also played a bit with a 22sas disk setup on an hp ml350. 

All no problems.

So dsm7 doesnt seem to have any issues with all the drives and expanders.

 

But now i added the enclosure and lsi 9211 to the working 6.2.3 system which was the plan all along.

And this does not see the drives.

I already took out a few so it does not exceed the max of 12. 

Still nothing. 

 

I have a feeling its because of the enclosure's expander.

Maybe 6.2.3 just doesnt like that?

 

I tried ssh'ing and doing the typical fdisk etc. but i am not a huge linux expert. 

I think it does show the drives there.

 

Anyone experience tips with this?

How to test if the linux does see the disks?

That sort of things i think of.

 

Thanks!

[kaneelschep]

df -h sais this.

So I see my 6 existing volumes.

And then under it I also see 5 empty 4tb drives.

Those are the drives in the enclosure. 

After playing with them in dsm 7, I booted some hiren bootcd and formatted all the drives in the enclosure to ntfs and copied something onto them.

Just to make sure I would not get a migration warning when adding them to the 6.2.3.

 

Could this be an issue? Or why would df show it, but DSM does not.

 

Thanks!

 

[kaneelschep]

I hooked up one of the drives from the enclosure to a sata port on the motherboard. It showed up immediately.. no problems. Made pool, volume, share. Works fine.

 

But first i hung that drive on port 2 of the original sas controller.

And like in the enclosure it also didnt show up in dsm.

But it did show up the same way in df -h as the drives on the second controller/enclosure.

Like in the above screenshot.

 

The originals sas controller uses 2x 1sff8087 to 4sata cables.

And I noticed i always left sata cable/port 2 and 3 empty.

Now i remember why.

The drives on those 2 ports never ever showed in dsm.

Which is very weird. 6 from the 8 ports work and the other 2 dont.. 

And not logically the first 2 of either sas port. Or the last. Or the middle. No the 2 last ports on 1 sas port.

 

And it seems the drives on the second sas controller/enclosure now have the same issue.

 

I dont know what that means.

Especially as df just sees the drives. 

The sas controllers both show all drives in the sas bios. And in the posting.

 

Maybe someone has an idea?

 

Thanks!

 

[kaneelschep]

When i pulled out a disk from the enclosure, i got an error email. That an external sata drive was nog unplugged correctly.

Why does it see it as an external sata drive?

And is this maybe a clue why they dont work?   

 

[kaneelschep]

so yeah the drives are popping up under external drives.

They should be changed to internal drives somehow.

 

[kaneelschep]

so I found a lot of topics where this is discussed in some form. Not directly to my issue though.

But it comes down to the fact that it thinks these drives are on esata ports and they should be internal drives.

This is the best topic I found on the subject of more than 12 disks.

 

So I checked the synoinfo.conf and found the data it is now.

 

maxdisks="12"
esataportcfg="0xff000"      0000 0000 0000 1111 1111 0000 0000 0000
usbportcfg="0x300000"    0000 0000 0011 0000 0000 0000 0000 0000
internalportcfg="0xfff"        0000 0000 0000 0000 0000 1111 1111 1111

 

What I am still trying to figure out though is how the 1's relate to the actual drive position it will get in the DSM.

How does DSM decide from this what number the drive will get.

 

In DSM I see my mobo sata ports are first. As there are 2 drives on that now, and they report as drive 2 and 3 in DSM. So I just assume these 6 mobo sata ports are 1-6 in DSM.

Then we have the First sas controllers with 6 drives, reporting as 7-12.

So it would be really nice to know how do these numbers relate to the position of the 1's in the binary string.. My guess it might be first come first served.

and this also explains why the first sas controller only gets 6 slots. And the 2 ports 'dont work'.  CQ are recognized as Esata ports.

 

Even though I have max only 20 drives on the 2 sas controllers. I also have 6 sata ports that it will count if I like it or not.. So 26 sata slots on the hardware.

And i really dont want to go over 24 drive slots. As that causes problems we read in the added topic .

So i am going to loose the Esata and usb ports all together. And put the internal drives on 24. Then we should be at 24. and I will be probably be good.

Which should look like this.

 

maxdisks="24"
esataportcfg="0x0"             0000 0000 0000 0000 0000 0000
usbportcfg="0x0"               0000 0000 0000 0000 0000 0000
internalportcfg="0xFFFFFF"     1111 1111 1111 1111 1111 1111

 

 

[kaneelschep]

This solved the issue. All drives were detected. Also the other hds I wanted to add are working. Hot swappable and all.

 

After this I added SHR functionality back, so I can make SHR2 pool out of the 6x4tb.

This is a good tutorial for that. just have to mind the location of the added command.

https://www.doyler.net/security-not-included/enable-shr-on-synology-ds3615xs

 

After it is done making the pool. I will try to get the 2 drives on the motherboards sata to work on the sas controller. And then try to deactivate sata on the motherboard.

But its not a very high prio..

 

All in all good outcome!

Thanks all for letting me talk to myself.