Add NVMe to Single Disc

TrueNAS General
1

Hi,
I have had a pool with 2 NVMe discs, where 1 disc got faulty and disappeared. Now the pool runs on 1 disc - I was able to get the same Samsung 980 NVMe again, but now - as the pool is only on 1 disc, I wonder how to attach the drive to the pool.

nvme list
only shows the current one, but the BIOS shows both discs.

lspci also shows both discs.

root@truenas[~]# lspci | grep Samsung
03:00.0 Non-Volatile memory controller: Samsung Electronics Co Ltd NVMe SSD Controller 980
08:00.0 Non-Volatile memory controller: Samsung Electronics Co Ltd NVMe SSD Controller 980

In the old TruesNAS around 4 or more years ago, there was a popup, mentioning, that a new drive has been detected and what I want to do with it. Now, there isn’t such.

Can someone assist, please?

2

From GUI, pool status, can you select the new after chose replace?
What version of truenas are you using?

1 Like
3

There is currently no replace button, as - as a silly click - I detached the defective one.

I am running TruesNAS Scale Dragonfish 24.04.2.1

4

Can you Share the zpool status?

5

Detached or offlined?

6

Storage > Pool > Status > (sole disk) > Extend from […] menu

3 Likes
7

2024-09-19 20_46_59-TrueNAS - 192.168.2.70
2024-09-19 20_46_59-TrueNAS - 192.168.2.701612Ă—397 43.6 KB

8 
root@truenas[~]# zpool status VirtualMachines
  pool: VirtualMachines
 state: ONLINE
status: Some supported and requested features are not enabled on the pool.
        The pool can still be used, but some features are unavailable.
action: Enable all features using 'zpool upgrade'. Once this is done,
        the pool may no longer be accessible by software that does not support
        the features. See zpool-features(7) for details.
  scan: scrub repaired 0B in 00:07:07 with 0 errors on Sun Aug 25 00:07:08 2024
config:

        NAME                                    STATE     READ WRITE CKSUM
        VirtualMachines                         ONLINE       0     0     0
          e96544bb-4007-4437-a54f-c09b57d2210c  ONLINE       0     0     0

errors: No known data errors
9

It was offlined by the system and i detached it by “silly clicking”

10

What you did was convert a mirror vdev to a single-drive stripe.

So now you need to do the “reverse” and convert it back to a mirror (which will require a resilver on the entire newly added drive.)

:point_down:

2 Likes
11

Ok, sure. But how to do this?

Under storage i have only the provided screenshot. Or shall i go to “Manage disks”?

12

Im not a Scale user but yes i think Is under “manage device” menu

13

2024-09-19 21_13_04-TrueNAS - 192.168.2.70
2024-09-19 21_13_04-TrueNAS - 192.168.2.701623Ă—326 16.5 KB

Even under disks i dont have the device

2024-09-19 21_14_20-Einstellungen
2024-09-19 21_14_20-Einstellungen1651Ă—530 30.9 KB

But:

root@truenas[~]# lspci | grep Samsung
03:00.0 Non-Volatile memory controller: Samsung Electronics Co Ltd NVMe SSD Controller 980
08:00.0 Non-Volatile memory controller: Samsung Electronics Co Ltd NVMe SSD Controller 980
14

FOR GREAT JUSTICE! VOTE FOR THIS FEATURE!

2 Likes
15

What about lsblk -o name,size,fstype

16 
root@truenas[~]# lsblk -o name,size,fstype
NAME          SIZE FSTYPE
sda         931.5G
├─sda1          2G
└─sda2      929.5G zfs_member
sdb         931.5G
├─sdb1          2G
└─sdb2      929.5G zfs_member
sdc         232.9G
├─sdc1          1M
├─sdc2        512M vfat
├─sdc3      216.4G zfs_member
└─sdc4         16G
  └─sdc4       16G swap
sdd         931.5G
├─sdd1          2G linux_raid_member
└─sdd2      929.5G zfs_member
zd0            10G
zd16          180G
zd32           50G
zd48            8G
zd64           30G
nvme0n1     931.5G
├─nvme0n1p1     2G
└─nvme0n1p2 929.5G zfs_member

root@truenas[~]# nvme list
Node                  Generic               SN                   Model                                    Namespace Usage                      Format           FW Rev
--------------------- --------------------- -------------------- ---------------------------------------- --------- -------------------------- ---------------- --------
/dev/nvme0n1          /dev/ng0n1            S649NU0WA52749J      Samsung SSD 980 1TB                      1         834.92  GB /   1.00  TB    512   B +  0 B   3B4QFXO7
17

Something’s not right…

If it’s the same exact model, and you installed it the same way in the same slot as the previous one…?

You say that the BIOS detects it. How does it present the information? The same as your “good” NVMe drive? The BIOS doesn’t have some poor man’s RAID configured for your NVMe slots, does it?

The Samsung NVMe you currently have in your pool has the latest firmware (ver 3B4QFXO7). I would assume that the same model purchased at a later date would also have the latest firmware.

18

I fully agree. Something is not right there. But what?

Can i check the Firmware through TrueNAS somehow?

The BIOS shows both NVMe’s inside the Storage Tab (or something different - i currently dont remember). And yes, its in the same slot as the previous one.

19

Does it reveal anything in here? Firmware? Status? Port? Some sort of “RAID” enabled?

Not if the underlying operating system (Debian Linux) does not detect it.

Your output of nvme list only displays a single NVMe device.

20

As far as i remember, the BIOS says, one M2 is in M2_1 and the other one in M2_2. It shows the name and the size. Nothing more.

Yes, nvme list shows 1 device, but why does lspci | grep Samsung show both?