SSD not available

[Ragetti]

Hi all,

I have a Samsung SSD installed on my TrueNAS system (12.0-U3.1) which appears under Storage/Disks but when i try to add it to a pool to does not appear in the list of available disks.

Can anyone help?

 

[sretalla]

First thing to try is a Wipe on that disk in Storage | Disks.

If that succeeds, you should see it as an option for pool operations.

 

[Ragetti]

I don't get an option to Wipe the disk as i do with my others unfortunately.

 

[sretalla]

I can't see from that screenshot, but I think it's ada2, so (assuming that's correct) you can use:
gpart destroy -F /dev/ada2

 

[Ragetti]

Yeah, you assume correct :)

Code:

root@nas[~]# gpart destroy -F /dev/ada2
gpart: Device busy
root@nas[~]#

I have tried with sudo but that makes no difference.

 

[Patrick M. Hausen]

Have you "imported" the disk in the UI? What is the output of mount?

 

[Ragetti]

The disk doesn't show in the dropdown.

I've run gpart list and it has returned this:

Code:

Geom name: ada2
modified: false
state: OK
fwheads: 16
fwsectors: 63
last: 500118151
first: 40
entries: 128
scheme: GPT
Providers:
1. Name: ada2p1
   Mediasize: 272629760 (260M)
   Sectorsize: 512
   Stripesize: 4096
   Stripeoffset: 0
   Mode: r0w0e0
   efimedia: HD(1,GPT,d8fbf35c-2a71-11eb-9b63-d45d642063d2,0x28,0x82000)
   rawuuid: d8fbf35c-2a71-11eb-9b63-d45d642063d2
   rawtype: c12a7328-f81f-11d2-ba4b-00a0c93ec93b
   label: (null)
   length: 272629760
   offset: 20480
   type: efi
   index: 1
   end: 532519
   start: 40
2. Name: ada2p2
   Mediasize: 255785435136 (238G)
   Sectorsize: 512
   Stripesize: 4096
   Stripeoffset: 0
   Mode: r1w1e1
   efimedia: HD(2,GPT,d900a31f-2a71-11eb-9b63-d45d642063d2,0x82028,0x1dc70000)
   rawuuid: d900a31f-2a71-11eb-9b63-d45d642063d2
   rawtype: 516e7cba-6ecf-11d6-8ff8-00022d09712b
   label: (null)
   length: 255785435136
   offset: 272650240
   type: freebsd-zfs
   index: 2
   end: 500113447
   start: 532520
Consumers:
1. Name: ada2
   Mediasize: 256060514304 (238G)
   Sectorsize: 512
   Stripesize: 4096
   Stripeoffset: 0
   Mode: r1w1e2

 

[Patrick M. Hausen]

I asked if you did that. I did not recommend to do it. So the answer is "no"? Good.
What is the output of mount? And while we are at it, what is the output of swapinfo and gmirror status?

Something is actively holding your disk "open", so you cannot add it to your pool. I am trying to find out what that may be.

Edit: please add the output of zpool status, too. The partition table of your ada2 looks suspiciously like a TrueNAS boot disk. So possibly we are looking at the wrong device.

 

[Ragetti]

I asked if you did that. I did not recommend to do it. So the answer is "no"? Good.
What is the output of mount? And while we are at it, what is the output of swapinfo and gmirror status?

Something is actively holding your disk "open", so you cannot add it to your pool. I am trying to find out what that may be.

I have run the following:

Code:

root@nas[~]# mount ada2
mount: ada2: unknown special file or file system

Code:

root@nas[~]# swapinfo ada2
Device          1K-blocks     Used    Avail Capacity
/dev/mirror/swap0.eli   2097152 

Code:

root@nas[~]# gmirror status
        Name    Status  Components
mirror/swap0  COMPLETE  ada3p1 (ACTIVE)
                        ada0p1 (ACTIVE)

 

[Patrick M. Hausen]

Did I write mount ada2? Just mount and the ENTER key, please.

 

[Ragetti]

Did I write mount ada2? Just mount and the ENTER key, please.

Apologies Patrick - just habbit!

Here you go:

Code:

Last login: Fri May 14 11:19:14 on pts/7
FreeBSD 12.2-RELEASE-p6 facd5d71c97(HEAD) TRUENAS

        TrueNAS (c) 2009-2021, iXsystems, Inc.
        All rights reserved.
        TrueNAS code is released under the modified BSD license with some
        files copyrighted by (c) iXsystems, Inc.

        For more information, documentation, help or support, go here:
        http://truenas.com
Welcome to FreeNAS

Warning: settings changed through the CLI are not written to
the configuration database and will be reset on reboot.

root@nas[~]# mount
freenas-boot/ROOT/12.0-U3.1 on / (zfs, local, noatime, nfsv4acls)
devfs on /dev (devfs, local, multilabel)
tmpfs on /etc (tmpfs, local)
tmpfs on /mnt (tmpfs, local)
tmpfs on /var (tmpfs, local)
fdescfs on /dev/fd (fdescfs)
SSD on /mnt/SSD (zfs, local, nfsv4acls)
SSD/iocage on /mnt/SSD/iocage (zfs, local, nfsv4acls)
SSD/iocage/templates on /mnt/SSD/iocage/templates (zfs, local, nfsv4acls)
SSD/iocage/log on /mnt/SSD/iocage/log (zfs, local, nfsv4acls)
SSD/iocage/download on /mnt/SSD/iocage/download (zfs, local, nfsv4acls)
SSD/iocage/jails on /mnt/SSD/iocage/jails (zfs, local, nfsv4acls)
SSD/iocage/images on /mnt/SSD/iocage/images (zfs, local, nfsv4acls)
SSD/iocage/releases on /mnt/SSD/iocage/releases (zfs, local, nfsv4acls)
SSD/iocage/download/11.2-RELEASE on /mnt/SSD/iocage/download/11.2-RELEASE (zfs,local, nfsv4acls)
SSD/iocage/download/11.3-RELEASE on /mnt/SSD/iocage/download/11.3-RELEASE (zfs,local, nfsv4acls)
SSD/iocage/download/12.1-RELEASE on /mnt/SSD/iocage/download/12.1-RELEASE (zfs,local, nfsv4acls)
SSD/iocage/releases/11.2-RELEASE on /mnt/SSD/iocage/releases/11.2-RELEASE (zfs,local, nfsv4acls)
SSD/iocage/releases/11.3-RELEASE on /mnt/SSD/iocage/releases/11.3-RELEASE (zfs,local, nfsv4acls)
SSD/iocage/jails/Plex-Media-Server on /mnt/SSD/iocage/jails/Plex-Media-Server (zfs, local, nfsv4acls)
SSD/iocage/releases/12.1-RELEASE on /mnt/SSD/iocage/releases/12.1-RELEASE (zfs,local, nfsv4acls)
SSD/iocage/jails/Plex-Media-Server/root on /mnt/SSD/iocage/jails/Plex-Media-Server/root (zfs, local, nfsv4acls)
SSD/iocage/releases/11.3-RELEASE/root on /mnt/SSD/iocage/releases/11.3-RELEASE/root (zfs, local, nfsv4acls)
SSD/iocage/releases/11.2-RELEASE/root on /mnt/SSD/iocage/releases/11.2-RELEASE/root (zfs, local, nfsv4acls)
SSD/iocage/releases/12.1-RELEASE/root on /mnt/SSD/iocage/releases/12.1-RELEASE/root (zfs, local, nfsv4acls)
NAS on /mnt/NAS (zfs, local, nfsv4acls)
NAS/Time Machine on /mnt/NAS/Time Machine (zfs, local, nfsv4acls)
NAS/Backup on /mnt/NAS/Backup (zfs, local, nfsv4acls)
NAS/Media on /mnt/NAS/Media (zfs, local, nfsv4acls)
SSD/.system on /var/db/system (zfs, local, nfsv4acls)
SSD/.system/cores on /var/db/system/cores (zfs, local, nfsv4acls)
SSD/.system/samba4 on /var/db/system/samba4 (zfs, local, nfsv4acls)
SSD/.system/syslog-ae1f6b9a44d94d15a639a40c1e91b328 on /var/db/system/syslog-ae1f6b9a44d94d15a639a40c1e91b328 (zfs, local, nfsv4acls)
SSD/.system/rrd-ae1f6b9a44d94d15a639a40c1e91b328 on /var/db/system/rrd-ae1f6b9a44d94d15a639a40c1e91b328 (zfs, local, nfsv4acls)
SSD/.system/configs-ae1f6b9a44d94d15a639a40c1e91b328 on /var/db/system/configs-ae1f6b9a44d94d15a639a40c1e91b328 (zfs, local, nfsv4acls)
SSD/.system/webui on /var/db/system/webui (zfs, local, nfsv4acls)
SSD/.system/services on /var/db/system/services (zfs, local, nfsv4acls)
/mnt/SSD/iocage/releases/12.1-RELEASE/root/bin on /mnt/SSD/iocage/jails/Plex-Media-Server/root/bin (nullfs, local, read-only)
/mnt/SSD/iocage/releases/12.1-RELEASE/root/boot on /mnt/SSD/iocage/jails/Plex-Media-Server/root/boot (nullfs, local, read-only)
/mnt/SSD/iocage/releases/12.1-RELEASE/root/lib on /mnt/SSD/iocage/jails/Plex-Media-Server/root/lib (nullfs, local, read-only)
/mnt/SSD/iocage/releases/12.1-RELEASE/root/libexec on /mnt/SSD/iocage/jails/Plex-Media-Server/root/libexec (nullfs, local, read-only)
/mnt/SSD/iocage/releases/12.1-RELEASE/root/rescue on /mnt/SSD/iocage/jails/Plex-Media-Server/root/rescue (nullfs, local, read-only)
/mnt/SSD/iocage/releases/12.1-RELEASE/root/sbin on /mnt/SSD/iocage/jails/Plex-Media-Server/root/sbin (nullfs, local, read-only)
/mnt/SSD/iocage/releases/12.1-RELEASE/root/usr/bin on /mnt/SSD/iocage/jails/Plex-Media-Server/root/usr/bin (nullfs, local, read-only)
/mnt/SSD/iocage/releases/12.1-RELEASE/root/usr/include on /mnt/SSD/iocage/jails/Plex-Media-Server/root/usr/include (nullfs, local, read-only)
/mnt/SSD/iocage/releases/12.1-RELEASE/root/usr/lib on /mnt/SSD/iocage/jails/Plex-Media-Server/root/usr/lib (nullfs, local, read-only)
/mnt/SSD/iocage/releases/12.1-RELEASE/root/usr/libexec on /mnt/SSD/iocage/jails/Plex-Media-Server/root/usr/libexec (nullfs, local, read-only)
/mnt/SSD/iocage/releases/12.1-RELEASE/root/usr/sbin on /mnt/SSD/iocage/jails/Plex-Media-Server/root/usr/sbin (nullfs, local, read-only)
/mnt/SSD/iocage/releases/12.1-RELEASE/root/usr/share on /mnt/SSD/iocage/jails/Plex-Media-Server/root/usr/share (nullfs, local, read-only)
/mnt/SSD/iocage/releases/12.1-RELEASE/root/usr/libdata on /mnt/SSD/iocage/jails/Plex-Media-Server/root/usr/libdata (nullfs, local, read-only)
/mnt/SSD/iocage/releases/12.1-RELEASE/root/usr/lib32 on /mnt/SSD/iocage/jails/Plex-Media-Server/root/usr/lib32 (nullfs, local, read-only)
/mnt/NAS/Media on /mnt/SSD/iocage/jails/Plex-Media-Server/root/mnt/PlexMediaFiles (nullfs, local)
devfs on /mnt/SSD/iocage/jails/Plex-Media-Server/root/dev (devfs, local, multilabel)
fdescfs on /mnt/SSD/iocage/jails/Plex-Media-Server/root/dev/fd (fdescfs)
root@nas[~]#

 

[Patrick M. Hausen]

Please add the output of zpool status, then I can possibly spot something.

 

[Ragetti]

Please add the output of zpool status, then I can possibly spot something.

Code:

Last login: Fri May 14 12:02:46 on pts/15
FreeBSD 12.2-RELEASE-p6 facd5d71c97(HEAD) TRUENAS

        TrueNAS (c) 2009-2021, iXsystems, Inc.
        All rights reserved.
        TrueNAS code is released under the modified BSD license with some
        files copyrighted by (c) iXsystems, Inc.

        For more information, documentation, help or support, go here:
        http://truenas.com
Welcome to FreeNAS

Warning: settings changed through the CLI are not written to
the configuration database and will be reset on reboot.

root@nas[~]# zpool status
  pool: NAS
 state: ONLINE
config:

        NAME                                          STATE     READ WRITE CKSUM
        NAS                                           ONLINE       0     0     0
          gptid/59a4a93f-b3cc-11eb-9932-d45d642063d2  ONLINE       0     0     0

errors: No known data errors

  pool: SSD
 state: ONLINE
status: Some supported 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(5) for details.
  scan: scrub repaired 0B in 00:01:37 with 0 errors on Sun Apr 11 00:01:37 2021
config:

        NAME                                          STATE     READ WRITE CKSUM
        SSD                                           ONLINE       0     0     0
          gptid/d5055923-2a77-11eb-9606-d45d642063d2  ONLINE       0     0     0

errors: No known data errors

  pool: freenas-boot
 state: ONLINE
status: Some supported 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(5) for details.
  scan: scrub repaired 0B in 00:00:27 with 0 errors on Thu May 13 03:45:27 2021
config:

        NAME          STATE     READ WRITE CKSUM
        freenas-boot  ONLINE       0     0     0
          ada2p2      ONLINE       0     0     0

errors: No known data errors

By the look of this, does this mean that this drive is being used for the boot disk, even if the system dataset is on the other drive? If that is the case, can i save the wasted space on this SSD by moving across to the drive used as the system dataset?

 

[Patrick M. Hausen]

Yes, this drive is used as the boot disk. From your initial post we got the impression that you added the Samsung drive to an existing installation.
TrueNAS must have a dedicated boot device. No way around that. And a small SSD is a good choice for a boot device.

The system dataset is a completely different matter. It is where TrueNAS writes log files, configuration backups, volatile data, ...
It is moved from the boot device to the first pool you create because the latter is in most cases redundant and frequently built from rotating disks. So not to ruin your boot SSD with continuous writes every couple of seconds.

There is no way around that architecture though you can cheat and just use e.g. 32G of your SSD for the boot pool and create another pool on the remaining space. There's an intermediate installation on a USB drive and quite some command line wizardry involved and of course it is completely unsupported.

HOWTO: setup a pair of larger SSDs for boot pool and data

Moderator Warning: This HOWTO will damage the ability of your TrueNAS appliance to properly maintain itself, will break the ability to replace failed drives, and may cause problems with upgrades and updates. TrueNAS is not designed to do this sort of partitioning, and the developers are not...

www.truenas.com

 

[Ragetti]

Yes, this drive is used as the boot disk. From your initial post we got the impression that you added the Samsung drive to an existing installation.
TrueNAS must have a dedicated boot device. No way around that. And a small SSD is a good choice for a boot device.

The system dataset is a completely different matter. It is where TrueNAS writes log files, configuration backups, volatile data, ...
It is moved from the boot device to the first pool you create because the latter is in most cases redundant and frequently built from rotating disks. So not to ruin your boot SSD with continuous writes every couple of seconds.

There is no way around that architecture though you can cheat and just use e.g. 32G of your SSD for the boot pool and create another pool on the remaining space. There's an intermediate installation on a USB drive and quite some command line wizardry involved and of course it is completely unsupported.

HOWTO: setup a pair of larger SSDs for boot pool and data

Moderator Warning: This HOWTO will damage the ability of your TrueNAS appliance to properly maintain itself, will break the ability to replace failed drives, and may cause problems with upgrades and updates. TrueNAS is not designed to do this sort of partitioning, and the developers are not...

www.truenas.com

Thanks Patrick, that is really helpful. I installed a new Ironwolf 10TB drive this week and i think i may have formatted an old drive which i used to mirror the system SSD which maybe where my confusion came from.

On my Freenas system before the Truenas release i did use a 32gb flash drive as the boot drive but on this new setup i thought it wish to move onto an SSD. However, I thought that it would be wise to move onto an SSD for stability. I have a second 240gb SSD that is not being used - do you think it wise to mirror the System Data drive or the boot drive?

 

[Patrick M. Hausen]

I run mirrored SSDs, but bought a pair of cheap 32G sized ones for the boot pool. If you mirror the 240G SSDs you can still follow my HOWTO linked above. You need a 16G or 32G flash drive temporarily to do that.