I have bought a SSD with M.2 socket (B & M) key, but my computer just have a B key socket. My question is if I can connect the SSD in this B socket, and would it work correctly?
M.2 SSD – How to Connect a B & M Key SSD into a B Socket
m.2socketsssd
Related Solutions
With current Intel chipsets that have included RAID, I normally expect drives to be in AHCI mode even with RAID enabled until the drive is manually added to a RAID volume. I'm not certain how your motherboard/controller manages it.
In the event that it actually won't let you use a drive on a 'RAID' port as a normal AHCI drive, you should try installing the SATA drivers provided by ASUS here. It could be a 'FakeRaid' port, which would require the OS to have the appropriate drivers before RAID works.
And yes, single drive RAID is possible. Not normally done, since it provides absolutely no advantages over AHCI, but if your motherboard demands drives on that port to be in a RAID array, it is possible.
Possibly relevant is this:
He wanted to install an OS on the RAID drive.
Advice given:
So I do see a Marvell module. It is possible you would need to configure a single disk as a "stripe of one disk" or something similar, then do an F6 install of a RAID driver, to get it to work.
Now, when I look in the e2736 M2V user manual, it says:
"Do not install the operating system with the device connected to the Marvell® 88SE6121 Serial ATA connector."
So that is not an encouraging sign. It implies Asus doesn't think it will work.
As Bill said, give it a try, but there are no guarantees it will work. It all depends on things like the RAID setup in the BIOS, the Marvell driver and what it is capable of, and so on.
Final result:
I have installed Windows via the SATA ports connected to the VIA southbridge, with no problems. (also had to swap the HD, the 160 Gbyte had some problems, now have an 250gbyte SATA)
After that I installed the marvell drivers (drive still connected to the southbridge SATA).
After all this I connected the SATA driver to the Marvell connector (the internal one) and it tried to reboot: Windows logo showed up but somehow the SBOD (the well known bleu screen) showed up.
My conclusion is: Booting from the Marvell connected harddrive is possible, as long you have the proper SATA drivers for it.
I had a similar issue with permissions and it was a result of SELinux not having the policy for nginx to write to sockets
You can check SELinux AVC messages via audit2why -al
to see more details of the error, something along the lines of
type=AVC msg=audit(1414460265.454:2612): avc: denied { connectto } for pid=22107 comm="nginx" path="/tmp/uwsgi.sock" scontext=system_u:system_r:httpd_t:s0 tcontext=unconfined_u:unconfined_r:unconfined_t:s0-s0:c0.c1023 tclass=unix_stream_socket
Was caused by:
Missing type enforcement (TE) allow rule.
You can use audit2allow to generate a loadable module to allow this access.
To add the enforcement policy for nginx, first confirm the enforcement policy by running
> grep nginx /var/log/audit/audit.log | audit2allow -m nginx
You should see an output similar to
module nginx 1.0;
require {
type unconfined_t;
type httpd_t;
type home_root_t;
type soundd_port_t;
class sock_file write;
class unix_stream_socket connectto;
class tcp_socket name_connect;
}
#============= httpd_t ==============
#!!!! This avc is allowed in the current policy
allow httpd_t home_root_t:sock_file write;
#!!!! This avc is allowed in the current policy
allow httpd_t soundd_port_t:tcp_socket name_connect;
allow httpd_t unconfined_t:unix_stream_socket connectto;
Finally you load the custom policy by running
> grep nginx /var/log/audit/audit.log | audit2allow -M nginx
> semodule -i nginx.pp
Best Answer
It should... a B&M module should work with either a B or M socket, this is by design.
If your module is B&M SATA (most likely), connecting it to a B or M socket should work fine since both types support SATA.
Of course, being a bootable device is another story, this depends on your hardware and UEFI.