Drives missing (unable to create pool)

[Jghake]

Hello,

I have a small Lenovo M92p and a 4 bay USB3 drive enclosure with 3 2TB drives. I have a 4th drive that is removed from the system and has my data on it.

I struggled quite a bit to get TrueNAS installed, but slaving the SSD to my laptop, using the CD drive to install it, then swapping the SSD back into the Lenovo and booting up. Only Legacy mode will work, but I am able to get into the web interface for TrueNAS.

When I try to create the pool, I am only presented with options for DA2. egrep 'da[0-9]|cd[0-9]' /var/run/dmesg.boot at the command line shows below:

Code:

truenas% egrep 'da[0-9]|cd[0-9]' /var/run/dmesg.boot
ada0 at ahcich0 bus 0 scbus0 target 0 lun 0
ada0: <PNY CS900 240GB SSD CS900P13> ACS-4 ATA SATA 3.x device
ada0: Serial Number PNY21022101050103F8E
ada0: 600.000MB/s transfers (SATA 3.x, UDMA6, PIO 8192bytes)
ada0: Command Queueing enabled
ada0: 228936MB (468862128 512 byte sectors)
ses0: ada0,pass0 in 'Slot 00', SATA Slot: scbus0 target 0
da0 at umass-sim0 bus 0 scbus3 target 0 lun 0
da0: <ST320006 44NS 0125> Fixed Direct Access SPC-4 SCSI device
da0: Serial Number 152D00539000
da0: 400.000MB/s transfers
da0: 1907729MB (3907029168 512 byte sectors)
da0: quirks=0x2<NO_6_BYTE>
da1 at umass-sim0 bus 0 scbus3 target 0 lun 1
da1: <ST320006 44NS 0125> Fixed Direct Access SPC-4 SCSI device
da1: Serial Number 152D00539000
da1: 400.000MB/s transfers
da1: 1907729MB (3907029168 512 byte sectors)
da1: quirks=0x2<NO_6_BYTE>
da2 at umass-sim0 bus 0 scbus3 target 0 lun 2
da2: <ST320006 44NS 0125> Fixed Direct Access SPC-4 SCSI device
da2: Serial Number 152D00539000
da2: 400.000MB/s transfers
da2: 1907729MB (3907029168 512 byte sectors)
da2: quirks=0x2<NO_6_BYTE>
GEOM_ELI: Device da1p1.eli created.

Does anyone have any insight?

 

[Spearfoot]

Hello,

I have a small Lenovo M92p and a 4 bay USB3 drive enclosure with 3 2TB drives. I have a 4th drive that is removed from the system and has my data on it.

I struggled quite a bit to get TrueNAS installed, but slaving the SSD to my laptop, using the CD drive to install it, then swapping the SSD back into the Lenovo and booting up. Only Legacy mode will work, but I am able to get into the web interface for TrueNAS.

When I try to create the pool, I am only presented with options for DA2. egrep 'da[0-9]|cd[0-9]' /var/run/dmesg.boot at the command line shows below:

Code:

truenas% egrep 'da[0-9]|cd[0-9]' /var/run/dmesg.boot
ada0 at ahcich0 bus 0 scbus0 target 0 lun 0
ada0: <PNY CS900 240GB SSD CS900P13> ACS-4 ATA SATA 3.x device
ada0: Serial Number PNY21022101050103F8E
ada0: 600.000MB/s transfers (SATA 3.x, UDMA6, PIO 8192bytes)
ada0: Command Queueing enabled
ada0: 228936MB (468862128 512 byte sectors)
ses0: ada0,pass0 in 'Slot 00', SATA Slot: scbus0 target 0
da0 at umass-sim0 bus 0 scbus3 target 0 lun 0
da0: <ST320006 44NS 0125> Fixed Direct Access SPC-4 SCSI device
da0: Serial Number 152D00539000
da0: 400.000MB/s transfers
da0: 1907729MB (3907029168 512 byte sectors)
da0: quirks=0x2<NO_6_BYTE>
da1 at umass-sim0 bus 0 scbus3 target 0 lun 1
da1: <ST320006 44NS 0125> Fixed Direct Access SPC-4 SCSI device
da1: Serial Number 152D00539000
da1: 400.000MB/s transfers
da1: 1907729MB (3907029168 512 byte sectors)
da1: quirks=0x2<NO_6_BYTE>
da2 at umass-sim0 bus 0 scbus3 target 0 lun 2
da2: <ST320006 44NS 0125> Fixed Direct Access SPC-4 SCSI device
da2: Serial Number 152D00539000
da2: 400.000MB/s transfers
da2: 1907729MB (3907029168 512 byte sectors)
da2: quirks=0x2<NO_6_BYTE>
GEOM_ELI: Device da1p1.eli created.

Does anyone have any insight?

Welcome to the forum!

Sorry that you're having problems setting up TrueNAS.

The gist of your troubles is that TrueNAS was not designed to work with USB enclosures, but with rather with direct connections to the disks, either via SATA ports or a Host Bus Adapter (HBA).

I know this probably isn't what you want to hear... but your best path forward is to acquire different hardware. For example, a system board with at least 6 SATA ports would work well with the disks you have.

 

[danb35]

Does anyone have any insight?

Yes, but unfortunately it's that you've chosen very poor hardware for a TrueNAS system. Really, nothing about it sounds good, but the big problem is the USB external disk enclosure. These are discouraged for many reasons, chief among them being that they just don't give a reliable connection, but another (which is what's happening here) is that they don't really give the OS direct access to the disk. You can tell that's happening here because each disk reports the same serial number (and $20 says it doesn't match the serial number on any of your actual disks). And since TrueNAS uses the disk's serial number internally as a disk ID, there's your problem.