I added a SSD to function as a cache and I cannot seem to get the drive to show in any of the areas I would normally see it to either add it to my array or mount it using unassigned devices/pool cache. 

 

I had this same drive setup as a cache a few updates ago and finally got around to trying to fix it why it just disappeared. 

 

When I look at the logs it doesn't even show up. 

 

I am a but perplexed and looking for some guidance. I did remove it and test it in a ubuntu box and it shows up there without issue. 

 

 

tower-diagnostics-20220209-2146.zip

If it's connected to the RAID controller you might need to initialize it or create a RAID0/JBOD volume with it.

are you thinking in BIOS of the HP itself? 

 

Exploring bios was going to be my next step.

RAID controller BIOS, also keep in mind that RAID controllers are not recommended, this is just one of the reasons.

Yea for sure, I think I just have the disks mounted as individuals on the HP.

 

As I recall it was a while ago when I set the box up there was no way to avoid the controller.

 

Thanks for the help.

Just did some work on this over the weekend and I recall what I did. 

 

So when I install the second SSD that I was using for a cache (primary for VM's) Unraid shows both Devices as Dev 1 and seems to lump them together. Which is a bit confusing, in the HP bios I have each drive setup as a individual raid 0 in the same manner I have my whole array setup but the two SSD's for some reason show the same UUID. 

 

Unraid shows them as sdf and sdh but the Id's are the same, is this whats causing the problem?

 

Any thoughts?

Edited February 14, 20224 yr by ejg3855

36 minutes ago, ejg3855 said:

is this whats causing the problem?

Yep, Unraid requires all devices to have a unique s/n.

Is there a way to change the id, they are two physically different drives.

Edited February 14, 20224 yr by ejg3855

when i look at the dev settings they have clearly different ids, is this a truncation problem with UD? 

 

LOGICAL_VOLUME_0014380337D7200_3600508b1001c9d70bb2587130140cdbf (sdh)
LOGICAL_VOLUME_0014380337D7200_3600508b1001cf95ff760c0e4274362fa (sdf)

 

so they have different serials right? Unraid is just seeing them as the same UUID? Is t hat the correct terminology? 

Edited February 14, 20224 yr by ejg3855

11 minutes ago, ejg3855 said:

is this a truncation problem with UD? 

You can try posting in the UD support thread to see if there's anything that can be done, simple solution is to not use RAID controllers.

Will do.

 

The more I look at it though its Unraid/UM issue not using the whole volume ID. 

 

I agree on the raidcontroller issue but this is the only Drive in my whole setup that has this issue, both Samsung SSD's. The other 6 drives are fine.

38 minutes ago, ejg3855 said:

LOGICAL_VOLUME_0014380337D7200_3600508b1001c9d70bb2587130140cdbf (sdh)
LOGICAL_VOLUME_0014380337D7200_3600508b1001cf95ff760c0e4274362fa (sdf)

 

so they have different serials right?

These are not actual serial numbers, just identifiers the RAID controller gives them.

On 2/10/2022 at 9:29 AM, JorgeB said:

RAID controllers are not recommended, this is just one of the reasons.

 

Makes sense. What doesn't make sense is why is it only the SSD's and all the other drives in the array work as anticipated.

 

Thanks

Edited February 14, 20224 yr by ejg3855