{"id":568,"date":"2011-12-17T16:48:05","date_gmt":"2011-12-17T16:48:05","guid":{"rendered":"http:\/\/poojanwagh.opalstacked.com\/techblog\/?p=568"},"modified":"2011-12-17T16:54:11","modified_gmt":"2011-12-17T16:54:11","slug":"creating-static-adax-mappings-for","status":"publish","type":"post","link":"https:\/\/tech.poojanblog.com\/blog\/unix-linux\/creating-static-adax-mappings-for\/","title":{"rendered":"Creating static adaX mappings for FreeBSD drives"},"content":{"rendered":"

I recently had a problem with ZFS. I went back to not using glabel, mainly because I wanted to force 4KB sector alignment on my drives and therefore used a gnop trick. About a month after doing so, I shuffled my drives around. I had ada4 and ada5 set up in a mirror configuration. At some point, I moved a drive around and ada4 became ada3 and ada3 became ada2. I could have (and should have) used the methods below to re-assign ada3\/ada4 to their right positions. Anyway, I’m doing it now.<\/p>\n

<\/p>\n

Here’s the controller\/bus enumeration before any changes:<\/p>\n


\nDec 3 17:05:35 server kernel: ahci0: mem 0xfdefe000-0xfdefffff irq 17 at device 0.0 on pci2
\nDec 3 17:05:35 server kernel: ahci0: [ITHREAD]
\nDec 3 17:05:35 server kernel: ahci0: AHCI v1.00 with 2 3Gbps ports, Port Multiplier supported
\nDec 3 17:05:35 server kernel: ahcich0: at channel 0 on ahci0
\nDec 3 17:05:35 server kernel: ahcich0: [ITHREAD]
\nDec 3 17:05:35 server kernel: ahcich1: at channel 1 on ahci0
\nDec 3 17:05:35 server kernel: ahcich1: [ITHREAD]
\nDec 3 17:05:35 server kernel: atapci0: port 0xdf00-0xdf07,0xde00-0xde03,0xdd00-0xdd07,0xdc00-0xdc03,0xdb00-0xdb0f irq 18 at device
\nDec 3 17:05:35 server kernel: atapci0: [ITHREAD]
\nDec 3 17:05:35 server kernel: ata2: on atapci0
\nDec 3 17:05:35 server kernel: ata2: [ITHREAD]
\n...
\nDec 3 17:05:35 server kernel: siis0: port 0xcf00-0xcf0f mem 0xfdcff000-0xfdcff07f,0xfdcf0000-0xfdcf7fff irq 20 at device 0.0 on pci3
\nDec 3 17:05:35 server kernel: siis0: [ITHREAD]
\nDec 3 17:05:35 server kernel: siisch0: at channel 0 on siis0
\nDec 3 17:05:35 server kernel: siisch0: [ITHREAD]
\nDec 3 17:05:35 server kernel: siisch1: at channel 1 on siis0
\nDec 3 17:05:35 server kernel: siisch1: [ITHREAD]
\nDec 3 17:05:35 server kernel: siisch2: at channel 2 on siis0
\nDec 3 17:05:35 server kernel: siisch2: [ITHREAD]
\nDec 3 17:05:35 server kernel: siisch3: at channel 3 on siis0
\nDec 3 17:05:35 server kernel: siisch3: [ITHREAD]
\n...Dec 3 17:11:28 server kernel: ahci1: port 0xfa00-0xfa07,0xf900-0xf903,0xf800-0xf807,0xf700-0xf703,0xf600-0xf60f mem 0xfdffe000-0xfdff
\nDec 3 17:11:28 server kernel: ahci1: [ITHREAD]
\nDec 3 17:11:28 server kernel: ahci1: AHCI v1.10 with 4 3Gbps ports, Port Multiplier not supported
\nDec 3 17:11:28 server kernel: ahcich2: at channel 0 on ahci1
\nDec 3 17:11:28 server kernel: ahcich2: [ITHREAD]
\nDec 3 17:11:28 server kernel: ahcich3: at channel 1 on ahci1
\nDec 3 17:11:28 server kernel: ahcich3: [ITHREAD]
\nDec 3 17:11:28 server kernel: ahcich4: at channel 2 on ahci1
\nDec 3 17:11:28 server kernel: ahcich4: [ITHREAD]
\nDec 3 17:11:28 server kernel: ahcich5: at channel 3 on ahci1
\nDec 3 17:11:28 server kernel: ahcich5: [ITHREAD]
\n<\/code><\/p>\n

Curiously, I don’t think ahci1 (the Intel South Bridge) physically exposes all 4 channels on the motherboard. Only 2 SATA ports are available. Which doesn’t make sense, since Gigabyte explicitly put another 2-port SATA controller on the board<\/p>\n


\n# Intel SATA controller (South Bridge)
\nhint.scbus.0.at=\"ahcich2\"
\nhint.scbus.0.bus=\"0\"
\nhint.scbus.1.at=\"ahcich3\"
\nhint.scbus.1.bus=\"0\"
\n# JMicron SATA controller (Gigabyte Motherboard)
\nhint.scbus.2.at=\"ahcich0\"
\nhint.scbus.2.bus=\"0\"
\nhint.scbus.3.at=\"ahcich1\"
\nhint.scbus.3.bus=\"0\"
\n# SiiS controller (PCI slot)
\nhint.scbus.4.at=\"siisch0\"
\nhint.scbus.4.bus=\"0\"
\nhint.scbus.5.at=\"siisch1\"
\nhint.scbus.5.bus=\"0\"
\nhint.scbus.6.at=\"siisch2\"
\nhint.scbus.6.bus=\"0\"
\nhint.scbus.7.at=\"siisch3\"
\nhint.scbus.7.bus=\"0\"
\n<\/code><\/p>\n

Originally, I had something like:<\/p>\n


\nhint.scbus.0.at=\"ahci0\"
\nhint.scbus.0.bus=\"0\"
\n<\/code><\/p>\n

However, it seems like a “bus” as defined by hit.scbus isn’t the same as a SATA port. The system seems to enumerate all the SATA ports (from many controllers) on the same driver as ahcich0, ahcich1, etc.<\/p>\n

Anyway, I rebooted and found that the above works<\/p>\n


\nada0 at ahcich2 bus 0 scbus0 target 0 lun 0
\nada0: ATA-8 SATA 2.x device
\nada0: 300.000MB\/s transfers (SATA 2.x, UDMA6, PIO 8192bytes)
\nada0: Command Queueing enabled
\nada0: 1430799MB (2930277168 512 byte sectors: 16H 63S\/T 16383C)
\nada1 at ahcich3 bus 0 scbus1 target 0 lun 0
\nada1: ATA-8 SATA 2.x device
\nada1: 300.000MB\/s transfers (SATA 2.x, UDMA6, PIO 8192bytes)
\nada1: Command Queueing enabled
\nada1: 1907729MB (3907029168 512 byte sectors: 16H 63S\/T 16383C)
\nada2 at ahcich1 bus 0 scbus3 target 0 lun 0
\nada2: ATA-8 SATA 2.x device
\nada2: 300.000MB\/s transfers (SATA 2.x, UDMA5, PIO 8192bytes)
\nada2: Command Queueing enabled
\nada2: 61057MB (125045424 512 byte sectors: 16H 63S\/T 16383C)
\nada3 at siisch0 bus 0 scbus4 target 0 lun 0
\nada3: ATA-7 SATA 1.x device
\nada3: 150.000MB\/s transfers (SATA 1.x, UDMA6, PIO 512bytes)
\nada3: 7641MB (15649200 512 byte sectors: 16H 63S\/T 15525C)
\nada4 at siisch1 bus 0 scbus5 target 0 lun 0
\nada4: ATA-7 SATA 1.x device
\nada4: 150.000MB\/s transfers (SATA 1.x, UDMA6, PIO 512bytes)
\nada4: 7641MB (15649200 512 byte sectors: 16H 63S\/T 15525C)
\n<\/code><\/p>\n

You’ll notice that scbus2 is unconnected. ada1 is on scbus1 and ada2 is on scbus3. That’s where the problem arises. If I were to connect another hard drive to scbus2, it would become the new ada2 and the previous ada2 would be shifted to ada3. Here’s how to assign them non-contiguous numbers:<\/p>\n


\nhint.ada.0.at=\"scbus0\"
\nhint.ada.0.target=\"0\"
\nhint.ada.0.unit=\"0\"
\nhint.ada.1.at=\"scbus1\"
\nhint.ada.1.target=\"0\"
\nhint.ada.1.unit=\"0\"
\nhint.ada.2.at=\"scbus2\"
\nhint.ada.2.target=\"0\"
\nhint.ada.2.unit=\"0\"
\nhint.ada.3.at=\"scbus3\"
\nhint.ada.3.target=\"0\"
\nhint.ada.3.unit=\"0\"
\nhint.ada.4.at=\"scbus4\"
\nhint.ada.4.target=\"0\"
\nhint.ada.4.unit=\"0\"
\nhint.ada.5.at=\"scbus5\"
\nhint.ada.5.target=\"0\"
\nhint.ada.5.unit=\"0\"
\nhint.ada.6.at=\"scbus6\"
\nhint.ada.6.target=\"0\"
\nhint.ada.6.unit=\"0\"
\nhint.ada.7.at=\"scbus7\"
\nhint.ada.7.target=\"0\"
\nhint.ada.7.unit=\"0\"
\n<\/code><\/p>\n

Looks good. I get ada0, ada1, and skip ada2<\/p>\n


\nDec 17 10:24:10 server kernel: ada0 at ahcich2 bus 0 scbus0 target 0 lun 0
\nDec 17 10:24:10 server kernel: ada0: ATA-8 SATA 2.x device
\nDec 17 10:24:10 server kernel: ada0: 300.000MB\/s transfers (SATA 2.x, UDMA6, PIO 8192bytes)
\nDec 17 10:24:10 server kernel: ada0: Command Queueing enabled
\nDec 17 10:24:10 server kernel: ada0: 1430799MB (2930277168 512 byte sectors: 16H 63S\/T 16383C)
\nDec 17 10:24:10 server kernel: ada1 at ahcich3 bus 0 scbus1 target 0 lun 0
\nDec 17 10:24:10 server kernel: ada1: ATA-8 SATA 2.x device
\nDec 17 10:24:10 server kernel: ada1: 300.000MB\/s transfers (SATA 2.x, UDMA6, PIO 8192bytes)
\nDec 17 10:24:10 server kernel: ada1: Command Queueing enabled
\nDec 17 10:24:10 server kernel: ada1: 1907729MB (3907029168 512 byte sectors: 16H 63S\/T 16383C)
\nDec 17 10:24:10 server kernel: ada3 at ahcich1 bus 0 scbus3 target 0 lun 0
\nDec 17 10:24:10 server kernel: ada3: ATA-8 SATA 2.x device
\nDec 17 10:24:10 server kernel: ada3: 300.000MB\/s transfers (SATA 2.x, UDMA5, PIO 8192bytes)
\nDec 17 10:24:10 server kernel: ada3: Command Queueing enabled
\nDec 17 10:24:10 server kernel: ada3: 61057MB (125045424 512 byte sectors: 16H 63S\/T 16383C)
\nDec 17 10:24:10 server kernel: ada4 at siisch0 bus 0 scbus4 target 0 lun 0
\nDec 17 10:24:10 server kernel: ada4: ATA-7 SATA 1.x device
\nDec 17 10:24:10 server kernel: ada4: 150.000MB\/s transfers (SATA 1.x, UDMA6, PIO 512bytes)
\nDec 17 10:24:10 server kernel: ada4: 7641MB (15649200 512 byte sectors: 16H 63S\/T 15525C)
\nDec 17 10:24:10 server kernel: ada5 at siisch1 bus 0 scbus5 target 0 lun 0
\nDec 17 10:24:10 server kernel: ada5: ATA-7 SATA 1.x device
\nDec 17 10:24:10 server kernel: ada5: 150.000MB\/s transfers (SATA 1.x, UDMA6, PIO 512bytes)
\nDec 17 10:24:10 server kernel: ada5: 7641MB (15649200 512 byte sectors: 16H 63S\/T 15525C)
\n<\/code><\/p>\n

Another thing I ran up against was that my 2 drives are not the same size. One is a 1.5TB and one is a 2TB. When this mess happened, the system put the 2TB in the place of the 1.5 TB (I think). This would have been fine, except, I couldn’t then re-add the 1.5TB drive as a replacement for the 2TB drive as it will only accept something the same size or bigger. This has been documented before here<\/a>. For now, I’m throwing caution to the wind and not doing a gpart\/glabel. Maybe I’ll regret it later, but I want to try this out (ZFS native only) for now. I’ve seen quite a bit on the forums that ZFS should handle everything natively.<\/p>\n<\/p>\n