I'm trying to upgrade my single 250 ssd cache to dual 500GB. The problem is I can only add one of the 2 drives to the array "sdn".

The other one "sdo" I can see in the terminal using fdisk -l "see attachment". But its not showing up in the webui.

 

Any idea what could be causing that?

Already tried swapping cables around no difference. It looks like it just doesn't want to mount. no idea why.

What do you mean by not showing up on the ui?

You should post your system diagnostics zip file (obtained via Tools >> Diagnostics).   It might also be worth posting a screenshot of the Main tab at the point you are trying to add the SSD.

1 hour ago, testdasi said:

What do you mean by not showing up on the ui?

When the array is stopped You can add cache devices I can add 1 ssd but the second one is not showing up I would post a screenshot but I can't stop the array right now cause of parity check. I started a new config but that also didn't fix it.

47 minutes ago, itimpi said:

You should post your system diagnostics zip file (obtained via Tools >> Diagnostics).   It might also be worth posting a screenshot of the Main tab at the point you are trying to add the SSD.

Hope it helps

nas-diagnostics-20190629-1824.zip

Just to be absolutely clear of the problem. Here I should be able to select my second ssd "sdo" but I can't.

The syslog shows that the system is getting errors reported trying to query /dev/sdo which probably explains why it is not showing up.   However I have no idea what is causing the errors.

3 hours ago, itimpi said:

The syslog shows that the system is getting errors reported trying to query /dev/sdo which probably explains why it is not showing up.   However I have no idea what is causing the errors.

Its a new drive so it should work but ok I will try it in another system and report back.

Tried the drive in my windows pc made a partition it works fine. See picture. 

Posted the diagnostics file again too.

nas-diagnostics-20190702-1709.zip

The problem is that both SSDs are identified the same:

Jul  2 19:03:21 NAS kernel: ata5.00: ATA-9: Intenso SSD, 3813450-531609030, O1217A, max UDMA/133
...
Jul  2 19:03:21 NAS kernel: ata6.00: ATA-9: Intenso SSD, 3813450-531609030, O1217A, max UDMA/133

This is very unusual, usually the serial number is part of the identification, e.g.

Jul  2 19:03:21 NAS kernel: ata1.00: ATA-8: WDC WD20EURS-63S48Y0,      WD-WCAZAA480715, 51.0AB51, max UDMA/133

 

Because of this you can only use one of these as an Unraid server assigned device.

1 minute ago, johnnie.black said:

The problem is that both SSDs are identified the same:

Jul  2 19:03:21 NAS kernel: ata5.00: ATA-9: Intenso SSD, 3813450-531609030, O1217A, max UDMA/133
...
Jul  2 19:03:21 NAS kernel: ata6.00: ATA-9: Intenso SSD, 3813450-531609030, O1217A, max UDMA/133

This is very unusual, usually the serial number is part of the identification, e.g.

Jul  2 19:03:21 NAS kernel: ata1.00: ATA-8: WDC WD20EURS-63S48Y0,      WD-WCAZAA480715, 51.0AB51, max UDMA/133

 

Because of this you can only use one of these as an Unraid server assigned device.

There is no way around it? 

1 minute ago, FlyGuy94 said:

There is no way around it? 

Only if there is a firmware update that adds the serial to the id.

Just now, johnnie.black said:

Only if there is a firmware update that adds the serial to the id.

Well, forget that, according to the SMART report that is the serial:

 

Device Model:     Intenso SSD
Serial Number:    3813450-531609030

 

So both have the same serial, tha't not a real serial.

9 minutes ago, johnnie.black said:

So both have the same serial, tha't not a real serial.

I did pull out the ssd's they do both have thesame number but its not defined as a serial number on the sticker. So that means I'm SOL?

Just now, FlyGuy94 said:

So that means I'm SOL?

Yep, Unraid requires valid serials to identify and track the assigned devices, those SSDs have a fake serial, so you can only use one.

Well I guess these are going in my gaming rig then just my luck. Thanks anyway.