Hdd id's change when adding more drives

[Matt.b483]

I setup a truenas system on a i7 first gen 16g ram gigabyte motherboard. The motherboard has 2 sata controllers allowing for 10 sata devices connected 6 on SC1 and 4 on SC2 sata controller1(sc1) is raid capable and seems to have faster transfer rates than sc2 I have 7 drives /dev/ada0-/dev/ada6 the issue I have is I want to install a new drive this new drive should be located at /dev/ada7 but for some reason truenas sets it as /dev/ada1 causing /dev/ada1-ada5 to change to /dev/ada2-ada6 making all pools to stop working with errors about drives changing or missing. I would like to know if there is a way to force my second controller to be labeled differently than my first? or force trunas to start counting at sc1. I theorize that truenas starts counting drives on the second control first because the system drive is located on sc2 sata slot 0
I am new to truenas first one I have ever setup. currently the pools are empty so its not a big deal to set them up again. but at a later date i will want to add 2 more hdd to the system, this will cause all my /dev/ada's to move down the list making the pools unusable again.
any input or suggestions is welcome and please remember i am new to all of this but willing to learn.

 

[Chris Moore]

Your system should not care what the ada number is. FreeNAS doesn't define pools that way. How did you create your pool?
What software are you using? You mention Debian... Is this TrueNAS SCALE? It may work differently because of the Debian subsystem...
It is also in Alpah, so if you run into problems you should definetely be filing bug reports.

 

[Matt.b483]

Your FreeNAS system should not care what the ada number is. FreeNAS doesn't define pools that way. How did you create your pool?

i created the pool with truenas core 11.3 gui it also gave me an error saying that one of the drives in my pool has changed. and then basically said that because I'm using raid z it had enough data to recover from the error
error sent to email"pool netshare state is degraded: one or more devices could not be opened. sufficient replicas exist for pool to continue functioning in a degraded state" the error at dashboard was different it actually stated the drive changed

 

[Chris Moore]

Please read the Forum Guidelines
https://www.ixsystems.com/community/threads/forum-guidelines.45124/

There is some information that we need so we can help you.

 

[Chris Moore]

are you able to SSH to your NAS to access the command prompt?

 

[Matt.b483]

unfortunately i am no able to get any of the information until tomorrow evening as I don't have remote access setup

 

[Chris Moore]

Will you share the output of the command zpool status -v

it should look something like this:

Code:

  pool: Emily
state: ONLINE
  scan: scrub repaired 0B in 06:21:38 with 0 errors on Tue Dec 15 06:21:40 2020
config:

        NAME                                            STATE     READ WRITE CKSUM
        Emily                                           ONLINE       0     0     0
          raidz2-0                                      ONLINE       0     0     0
            gptid/af7c42c6-bf05-11e8-b5f3-0cc47a9cd5a4  ONLINE       0     0     0
            gptid/b07bc723-bf05-11e8-b5f3-0cc47a9cd5a4  ONLINE       0     0     0
            gptid/b1893397-bf05-11e8-b5f3-0cc47a9cd5a4  ONLINE       0     0     0
            gptid/b2bfc678-bf05-11e8-b5f3-0cc47a9cd5a4  ONLINE       0     0     0
            gptid/b3c1849e-bf05-11e8-b5f3-0cc47a9cd5a4  ONLINE       0     0     0
            gptid/b4d16ad2-bf05-11e8-b5f3-0cc47a9cd5a4  ONLINE       0     0     0
          raidz2-1                                      ONLINE       0     0     0
            gptid/acb0b918-ba5d-11e9-b6dd-00074306773b  ONLINE       0     0     0
            gptid/85d8ab3b-e442-11ea-99b6-00074306773b  ONLINE       0     0     0
            gptid/d1ea0d87-ba96-11e9-b6dd-00074306773b  ONLINE       0     0     0
            gptid/b9de3232-bf05-11e8-b5f3-0cc47a9cd5a4  ONLINE       0     0     0
            gptid/baf4aba8-bf05-11e8-b5f3-0cc47a9cd5a4  ONLINE       0     0     0
            gptid/bbf26621-bf05-11e8-b5f3-0cc47a9cd5a4  ONLINE       0     0     0
        logs
          gptid/ae487c50-bec3-11e8-b1c8-0cc47a9cd5a4    ONLINE       0     0     0
        cache
          gptid/ae52d59d-bec3-11e8-b1c8-0cc47a9cd5a4    ONLINE       0     0     0

errors: No known data errors

 

[danb35]

this new drive should be located at /dev/adb1

No, it shouldn't--FreeBSD isn't Linux. Under FreeBSD, disks would generally be identified as adan or dan, with n representing the disk number--you'd never see adbn. Under Linux, you'd have sda, sdb, sdc, etc., with the letters representing the disk "number"; numbers are used to denote partitions.

for some reason truenas sets it as /dev/ada1 causing /dev/ada1-5 to change to /dev/ada2-6 making all pools to stop working with errors about drives changing or missing.

Disks are numbered in the order in which the OS sees them, but that order doesn't (shouldn't) mean anything to FreeNAS. In addition to the output of zpool status that Chris is asking for, the output of camcontrol devlist would likely be helpful.

 

[Matt.b483]

I'm sorry but could you please bump this.
when i was removing hdd's to get the model numbers I found a sata cable with a small nick in it, i replaced the cable and no longer get the error. i think the cut was always there but when I added the drive I think I moved the cable enough that it was no longer completing the connection, causing the drive to no longer be recognized by the bios or Truenas. sorry for any time this post may have wasted