Mike R.
asked on
Supermicro SMC2208 not recognizing replacement OS drive
We have a Supermicro SMC2208RAid
Basics :
======
Controller = 0
Model = Supermicro SMC2208
Serial Number = FW-ACC***********
Current Controller Date/Time = 02/19/2019, 16:36:25
Current System Date/time = 02/19/2019, 16:36:40
SAS Address = 500304800e9c8500
PCI Address = 00:82:00:00
Mfg Date = 00/00/00
Rework Date = 00/00/00
Revision No =
The second Operating System drive failed:<br>
- Enclosure ID:252<br>
- Slot:1<br>
- Model: `INTEL SSDSC2CW240A3`
This drive is on its own backplane, and is handled by the RAID controller as a RAID1 (mirror) of only two drives.
--------------------------
EID:Slt DID State DG Size Intf Med SED PI SeSz Model Sp
--------------------------
0:0 3 Onln 1 1.817 TB SATA HDD N N 512B Hitachi HUA723020ALA640 U
(...snip...)
252:0 28 Onln 0 222.585 GB SATA SSD N N 512B INTEL SSDSC2CW240A3 U
252:1 27 UBad - 222.585 GB SATA SSD N N 512B U
--------------------------
Because that Intel model is no longer available, we replaced it with a:
`Intel SSDSC2KB240G801`. It is the same size and form factor, with very similar specs. All the critical specs are - I believe - the same EXCEPT this new drive is AES256 hardware encrypted. The old drive was AES128 encrypted. My understanding is; this encryption is only at the hardware level - so the controller/driveconnector should not care. But I can't confirm this.
However, the drive is not seen. In fact, `storcli` does not even show a drive slot there anymore.
(After inserting new drive)
--------------------------
EID:Slt DID State DG Size Intf Med SED PI SeSz Model Sp
--------------------------
0:0 3 Onln 1 1.817 TB SATA HDD N N 512B Hitachi HUA723020ALA640 U
(...snip...)
252:0 28 Onln 0 222.585 GB SATA SSD N N 512B INTEL SSDSC2CW240A3 U
--------------------------
I inherited this controller and it is long out of support.
**Any idea what's wrong? Is the new drive simply incompatible?**
Basics :
======
Controller = 0
Model = Supermicro SMC2208
Serial Number = FW-ACC***********
Current Controller Date/Time = 02/19/2019, 16:36:25
Current System Date/time = 02/19/2019, 16:36:40
SAS Address = 500304800e9c8500
PCI Address = 00:82:00:00
Mfg Date = 00/00/00
Rework Date = 00/00/00
Revision No =
The second Operating System drive failed:<br>
- Enclosure ID:252<br>
- Slot:1<br>
- Model: `INTEL SSDSC2CW240A3`
This drive is on its own backplane, and is handled by the RAID controller as a RAID1 (mirror) of only two drives.
--------------------------
EID:Slt DID State DG Size Intf Med SED PI SeSz Model Sp
--------------------------
0:0 3 Onln 1 1.817 TB SATA HDD N N 512B Hitachi HUA723020ALA640 U
(...snip...)
252:0 28 Onln 0 222.585 GB SATA SSD N N 512B INTEL SSDSC2CW240A3 U
252:1 27 UBad - 222.585 GB SATA SSD N N 512B U
--------------------------
Because that Intel model is no longer available, we replaced it with a:
`Intel SSDSC2KB240G801`. It is the same size and form factor, with very similar specs. All the critical specs are - I believe - the same EXCEPT this new drive is AES256 hardware encrypted. The old drive was AES128 encrypted. My understanding is; this encryption is only at the hardware level - so the controller/driveconnector should not care. But I can't confirm this.
However, the drive is not seen. In fact, `storcli` does not even show a drive slot there anymore.
(After inserting new drive)
--------------------------
EID:Slt DID State DG Size Intf Med SED PI SeSz Model Sp
--------------------------
0:0 3 Onln 1 1.817 TB SATA HDD N N 512B Hitachi HUA723020ALA640 U
(...snip...)
252:0 28 Onln 0 222.585 GB SATA SSD N N 512B INTEL SSDSC2CW240A3 U
--------------------------
I inherited this controller and it is long out of support.
**Any idea what's wrong? Is the new drive simply incompatible?**
ASKER CERTIFIED SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
Sorry, was going from " 252:1 27 UBad - 222.585 GB SATA SSD N N 512B U" and didn't scroll down enough to see that it was not seen at all when replaced. SED encryption is indeed internal to the drive and isn't normally used anyway. Bear in mind you can always put any SFF HDD in the slot and look for it with storcli, won't rebuild onto it of course.
ASKER
@AndyAlder
Thanks again for the reply. I did try the link anyway, but it didnt work (see below).
When I plug the drive in, I also don't get a connection light.
Perhaps the drive is bad?
I ordered two, but I hesitate to try the second one becaquse the seller has rigid return policies. If the issue is the drive model, I hate to break the second drive's seal.
Error:
root@fileserver:~# storcli /c0 /e252 /s1 set good
Controller = 0
Status = Failure
Description = No drive found!
Detailed Status :
===============
--------------------------
Drive Status ErrCd ErrMsg
--------------------------
/c0/e252/s1 Failure 255 Drive not found
--------------------------
Thanks again for the reply. I did try the link anyway, but it didnt work (see below).
When I plug the drive in, I also don't get a connection light.
Perhaps the drive is bad?
I ordered two, but I hesitate to try the second one becaquse the seller has rigid return policies. If the issue is the drive model, I hate to break the second drive's seal.
Error:
root@fileserver:~# storcli /c0 /e252 /s1 set good
Controller = 0
Status = Failure
Description = No drive found!
Detailed Status :
===============
--------------------------
Drive Status ErrCd ErrMsg
--------------------------
/c0/e252/s1 Failure 255 Drive not found
--------------------------
Surely you have a SFF disk lying about somewhere? SAS or SATA doesn't matter since it is just to see if the controller sees it in the slot.
ASKER
@andyalder
We did. That's what originally prompted the question.
When the drive reported as bad, we tried replacing it with a new unpartitioned sata disk. The light didn't even come on, and the RAID reported the "255 Drive not found" error when I tried to manually mark it good (using your link).
Then I tested the original drive (mounted it on an Ubuntu 18 box) and the ext4 partition reported fine (I couldn't test the LSI partition though). So, I put it BACK in the RAID's slot, the drive light came on, but when I tried to mark it good I again got the "255 Drive not found" error.
So, at this point, I'm assuming the slot is bad. It's one of the two SFF drive slots in the back of the controller, used for the OS:
We did. That's what originally prompted the question.
When the drive reported as bad, we tried replacing it with a new unpartitioned sata disk. The light didn't even come on, and the RAID reported the "255 Drive not found" error when I tried to manually mark it good (using your link).
Then I tested the original drive (mounted it on an Ubuntu 18 box) and the ext4 partition reported fine (I couldn't test the LSI partition though). So, I put it BACK in the RAID's slot, the drive light came on, but when I tried to mark it good I again got the "255 Drive not found" error.
So, at this point, I'm assuming the slot is bad. It's one of the two SFF drive slots in the back of the controller, used for the OS: