FreeNAS-11.3-U2 not seeing my added drive

[delovelady]

I have an NTFS 2T drive that I transferred a bunch of media files onto from a Windows system. Now I have shutdown, added the drive into the system, and powered back up twice. I don't see the unit. I did the same thing with a different drive bay slot - same thing. I can see the disk power up with the others and so on, but FreeNAS doesn't see it.

When I list disks, it doesn't show up. When I try Import Disk, the dropdown is empty (see image)

What steps should I take to diagnose?

 

[Samuel Tai]

Does the drive appear when you run dmesg from shell? If the hardware detects it, dmesg should have entries with that drive's serial number. From there, you should be able to get the drive's device node.

 

[delovelady]

Apparently not. It should have been one of the ada in this list. It is a 2TB drive, and I don't seen any like that. Plus what I see is already accounted for.

Code:

> dmesg|egrep '^ada|^da'
ada0 at ahcich0 bus 0 scbus0 target 0 lun 0
ada0: <ST6000VN0001-1SF17Z AN05> ACS-3 ATA SATA 3.x device
ada0: Serial Number Z4D2YZT8
ada0: 600.000MB/s transfers (SATA 3.x, UDMA6, PIO 8192bytes)
ada0: Command Queueing enabled
ada0: 5723166MB (11721045168 512 byte sectors)
ada1 at ahcich1 bus 0 scbus1 target 0 lun 0
ada1: <Samsung SSD 850 EVO 1TB EMT01B6Q> ACS-2 ATA SATA 3.x device
ada1: Serial Number S21CNXAG644286W
ada1: 600.000MB/s transfers (SATA 3.x, UDMA6, PIO 512bytes)
ada1: Command Queueing enabled
ada1: 953869MB (1953525168 512 byte sectors)
ada1: quirks=0x3<4K,NCQ_TRIM_BROKEN>
ada2 at ahcich2 bus 0 scbus2 target 0 lun 0
ada2: <ST6000VN0001-1SF17Z AN02> ACS-3 ATA SATA 3.x device
ada2: Serial Number Z4D39CWM
ada2: 600.000MB/s transfers (SATA 3.x, UDMA6, PIO 8192bytes)
ada2: Command Queueing enabled
ada2: 5723166MB (11721045168 512 byte sectors)
ada3 at ahcich3 bus 0 scbus3 target 0 lun 0
ada3: <Samsung SSD 850 EVO 1TB EMT01B6Q> ACS-2 ATA SATA 3.x device
ada3: Serial Number S21CNXAG557607X
ada3: 600.000MB/s transfers (SATA 3.x, UDMA6, PIO 512bytes)
ada3: Command Queueing enabled
ada3: 953869MB (1953525168 512 byte sectors)
ada3: quirks=0x3<4K,NCQ_TRIM_BROKEN>
ada4 at ahcich5 bus 0 scbus5 target 0 lun 0
ada4: <Samsung SSD 850 EVO 1TB EMT01B6Q> ACS-2 ATA SATA 3.x device
ada4: Serial Number S21CNXAG644304W
ada4: 600.000MB/s transfers (SATA 3.x, UDMA6, PIO 512bytes)
ada4: Command Queueing enabled
ada4: 953869MB (1953525168 512 byte sectors)
ada4: quirks=0x3<4K,NCQ_TRIM_BROKEN>
ada5 at ahcich6 bus 0 scbus6 target 0 lun 0
ada5: <ST6000VN0001-1SF17Z AN02> ACS-3 ATA SATA 3.x device
ada5: Serial Number Z4D3MHQL
ada5: 600.000MB/s transfers (SATA 3.x, UDMA6, PIO 8192bytes)
ada5: Command Queueing enabled
ada5: 5723166MB (11721045168 512 byte sectors)
ada6 at ahcich7 bus 0 scbus7 target 0 lun 0
ada6: <ST6000VN0001-1SF17Z AN02> ACS-3 ATA SATA 3.x device
ada6: Serial Number Z4D3H678
ada6: 600.000MB/s transfers (SATA 3.x, UDMA6, PIO 8192bytes)
ada6: Command Queueing enabled
ada6: 5723166MB (11721045168 512 byte sectors)
ada7 at ahcich8 bus 0 scbus8 target 0 lun 0
ada7: <ST6000VN0001-1SF17Z AN02> ACS-3 ATA SATA 3.x device
ada7: Serial Number Z4D39Z2N
ada7: 600.000MB/s transfers (SATA 3.x, UDMA6, PIO 8192bytes)
ada7: Command Queueing enabled
ada7: 5723166MB (11721045168 512 byte sectors)
ada8 at ahcich9 bus 0 scbus9 target 0 lun 0
ada8: <ST6000VN0001-1SF17Z AN02> ACS-3 ATA SATA 3.x device
ada8: Serial Number Z4D3MH3E
ada8: 600.000MB/s transfers (SATA 3.x, UDMA6, PIO 8192bytes)
ada8: Command Queueing enabled
ada8: 5723166MB (11721045168 512 byte sectors)
da0 at umass-sim0 bus 0 scbus12 target 0 lun 0
da0: <SanDisk Ultra 1.00> Removable Direct Access SPC-4 SCSI device
da0: Serial Number 4C531001550128108361
da0: 400.000MB/s transfers
da0: 14663MB (30031250 512 byte sectors)
da0: quirks=0x2<NO_6_BYTE>
dennis@nas1:/mnt/SSDs/home/dennis   05/10 09:06:29
>

 

[Samuel Tai]

OK, then your backplane may be faulty, or at least the last couple of slots.

 

[delovelady]

I'll swap positions with another, working... we'll see what happens. Funny, I tried this as a USB connection (using Black Widow); server didn't see it. Plug it into Windows, works fine. Plug it into a Ubuntu box, works fine. Plug it into FreeNAS, not seen. Not seen on backplane either. Move back to Black widow, it's working fine. Just droning. I'll report back.

 

[delovelady]

By the way: Tnanks for your attention @Samuel Tai.

I swapped it with ada8. Now both work. Go figure.

But I'm wondering if Import is what I really wanted. I expected a quick mount (all I want to do is copy files from the drive). It's been several minutes and is 8% into the Import process. Did I misstep?

 

[Samuel Tai]

You're welcome. No, I don't think you misstepped. Import is the by-the-book answer, and is the official way to do it via the UI.