Mix of SATA2 & SATA3 DOMs for mirrored boot device

[saurav]

As part of my attempt to upgrade to 9.3 on a mirrored boot device, I have installed a 16GB SATA DOM in my FreeNAS mini, which is detected like below:

Code:

Aug 16 13:05:41 freenas-primary kernel: ada2 at ahcich2 bus 0 scbus2 target 0 lun 0
Aug 16 13:05:41 freenas-primary kernel: ada2: <BIWIN SSD N1224A> ATA-8 SATA 2.x device
Aug 16 13:05:41 freenas-primary kernel: ada2: Serial Number 152104001023
Aug 16 13:05:41 freenas-primary kernel: ada2: 300.000MB/s transfers (SATA 2.x, UDMA6, PIO 512bytes)
Aug 16 13:05:41 freenas-primary kernel: ada2: 15104MB (30932992 512 byte sectors: 16H 63S/T 16383C)
Aug 16 13:05:41 freenas-primary kernel: ada2: Previously was known as ad8
Aug 16 13:05:41 freenas-primary kernel: ada3 at ahcich3 bus 0 scbus3 target 0 lun 0
Aug 16 13:05:41 freenas-primary kernel: ada3: <16GB SATA Flash Drive SFDE001A> ATA-9 SATA 3.x device
Aug 16 13:05:41 freenas-primary kernel: ada3: Serial Number B0214251300000000012
Aug 16 13:05:41 freenas-primary kernel: ada3: 600.000MB/s transfers (SATA 3.x, UDMA5, PIO 512bytes)
Aug 16 13:05:41 freenas-primary kernel: ada3: Command Queueing enabled
Aug 16 13:05:41 freenas-primary kernel: ada3: 15272MB (31277232 512 byte sectors: 16H 63S/T 16383C)
Aug 16 13:05:41 freenas-primary kernel: ada3: Previously was known as ad10

It looks like this SATA DOM supports SATA2, but the Apacer SATA DOM the mini came with (and I'm running 9.2 from) is SATA 3. Is it a bad idea to pair the two as a mirrored boot device for 9.3?

The sizes are also slightly different.

Also, the Apacer SATA DOM was earlier detected as ada2, and is now ada3. The system booted up fine, and I see no alerts, but could that be a problem later?

Thanks,
Saurav.

 

[Ericloewe]

Not a problem.