Jamie Gruener
Dabbler
- Joined
- Jan 20, 2014
- Messages
- 18
Okay, that's not exactly true because each drive has a unique SCSI ID. But they all share the same LUN. We have 3 Areca cards, two 1882XI cards, and an 1882LP. All exhibit the same behavior. We've set them to JBOD, but we still have to export a single disk as a "pass-through" disk to make it available to the OS (FreeNAS, Windows, Linux, ESXi, whatever).
When we do, the Logical Unit id value reported by SMART (or in Linux) is always the same for all disks from a given vendor. Below is the results of smartctl from a Seagate. Other Seagate drives will all have the same Logical Unit id. This value is the same across all three Areca cards. (Western Digital drives come up with a different id; haven't tested if the WD value is common among our 3 Areca cards, but I assume it is.)
This causes a couple of problems for us. First, FreeNAS will sometimes report these drives as Multi-path, which isn't true. We can delete the multi-path info easily enough. Also, when a drive is pulled and then re-inserted, it's name changes. Maybe that's to be expected for drives that haven't been made part of a vdev or zpool, but it seems weird to me.
But, once the drive is made part of a vdev or zpool, it seems to behave normally. If I pull a drive and then re-insert I do have to "remove" it from the volume and the re-add it to restore fault tolerance/resilver, I can't just say "it's back!", but maybe that's to be expected, too.
Is there any other possible downside to this weirdness? I'm considering using this card for a production environment.
Here are smartctl results. Note the Logical Unit id value.
Thanks,
--Jamie
When we do, the Logical Unit id value reported by SMART (or in Linux) is always the same for all disks from a given vendor. Below is the results of smartctl from a Seagate. Other Seagate drives will all have the same Logical Unit id. This value is the same across all three Areca cards. (Western Digital drives come up with a different id; haven't tested if the WD value is common among our 3 Areca cards, but I assume it is.)
This causes a couple of problems for us. First, FreeNAS will sometimes report these drives as Multi-path, which isn't true. We can delete the multi-path info easily enough. Also, when a drive is pulled and then re-inserted, it's name changes. Maybe that's to be expected for drives that haven't been made part of a vdev or zpool, but it seems weird to me.
But, once the drive is made part of a vdev or zpool, it seems to behave normally. If I pull a drive and then re-insert I do have to "remove" it from the volume and the re-add it to restore fault tolerance/resilver, I can't just say "it's back!", but maybe that's to be expected, too.
Is there any other possible downside to this weirdness? I'm considering using this card for a production environment.
Here are smartctl results. Note the Logical Unit id value.
[root@folio ~]# smartctl -i /dev/da0
smartctl 6.2 2013-07-26 r3841 [FreeBSD 9.2-RELEASE-p3 amd64] (local build)
Copyright (C) 2002-13, Bruce Allen, Christrian Franke, www.smarmontools.org
=== START OF INFORMATION SECTION ===
Vendor: Seagate
Product: ST4000NM0033-9ZM
Revision: R001
User Capacity: 4,000,787,030,016 bytes [4.00 TB]
Logical block size: 512 bytes
Rotation Rate: 10000 rpm
Logical Unit id: 0x001b4d2000000000
Serial number: Z1Z0AHE1
Device type: disk
Transport protocol: Fiber channel (FCP-2)
Local Time is: Mon Mar 17 11:36:15 2014 PDT
SMART support is: Available - device has SMART capability.
SMART support is: Enabled
Temperature Warning: Disabled or Not Supported
Thanks,
--Jamie