From nobody Sun Dec 19 23:59:42 2021 X-Original-To: freebsd-questions@mlmmj.nyi.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mlmmj.nyi.freebsd.org (Postfix) with ESMTP id 2CDB618E5C72 for ; Sun, 19 Dec 2021 23:52:10 +0000 (UTC) (envelope-from emailrob@risebroadband.net) Received: from mail42c28.carrierzone.com (mail42c28.carrierzone.com [66.175.52.148]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id 4JHKJT1pHRz3kHD for ; Sun, 19 Dec 2021 23:52:09 +0000 (UTC) (envelope-from emailrob@risebroadband.net) X-Authenticated-User: emailrob@risebroadband.net DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=carrierzone.com; s=mailmia; t=1639957927; bh=Qwc8vZ91/91h8Sqx8723fQ75dD8svHvPCe/hNY8eWp4=; h=Subject:Reply-To:References:To:From:Date:In-Reply-To:From; b=2JrqtRWUAT4EfCEGiDmmjTHmU6yWDWqRd4EXBKAZSVGebIKn/FktXFrELroIVGkfM 01MzxhzZ3N6n5fdbx5SaEmic17kq+ul7Pv/7qHOx6JO4PknHnXql7DtVW31Mgfg3qd KqkiyMgCjtp939g24+NE4cEydDONqSt1paMEtCu4= Feedback-ID:emailrob@risebr Received: from catherine.ntrprnr.com (cust-66-114-191-36.wireless.t6b.com [66.114.191.36] (may be forged)) (authenticated bits=0) by mail42c28.carrierzone.com (8.14.9/8.13.1) with ESMTP id 1BJNq5PX016460; Sun, 19 Dec 2021 23:52:07 +0000 Subject: ada[0-5] versus ahcich[0-5] on 11.4_amd64 Reply-To: emailrob@emailrob.com References: <7e5dc966-0660-849d-f534-acbd90d3966f@risebroadband.net> To: freebsd-questions@freebsd.org From: spellberg_robert X-Forwarded-Message-Id: <7e5dc966-0660-849d-f534-acbd90d3966f@risebroadband.net> Message-ID: <1ae74128-36a6-816b-e2c3-1c38c85903dd@risebroadband.net> Date: Sun, 19 Dec 2021 23:59:42 +0000 User-Agent: Mozilla/5.0 (X11; FreeBSD amd64; rv:78.0) Gecko/20100101 Thunderbird/78.10.2 List-Id: User questions List-Archive: https://lists.freebsd.org/archives/freebsd-questions List-Help: List-Post: List-Subscribe: List-Unsubscribe: Sender: owner-freebsd-questions@freebsd.org X-BeenThere: freebsd-questions@freebsd.org MIME-Version: 1.0 In-Reply-To: <7e5dc966-0660-849d-f534-acbd90d3966f@risebroadband.net> Content-Type: text/plain; charset=utf-8; format=flowed Content-Language: en-US Content-Transfer-Encoding: 7bit X-CTCH-RefID: str=0001.0A742F1F.61BFC5A7.0021,ss=1,re=0.000,recu=0.000,reip=0.000,cl=1,cld=1,fgs=0 X-CTCH-VOD: Unknown X-CTCH-Spam: Unknown X-CTCH-Score: 0.000 X-CTCH-Rules: X-CTCH-Flags: 0 X-CTCH-ScoreCust: 0.000 X-Origin-Country: US X-Rspamd-Queue-Id: 4JHKJT1pHRz3kHD X-Spamd-Bar: - Authentication-Results: mx1.freebsd.org; dkim=pass header.d=carrierzone.com header.s=mailmia header.b=2JrqtRWU; dmarc=none; spf=pass (mx1.freebsd.org: domain of emailrob@risebroadband.net designates 66.175.52.148 as permitted sender) smtp.mailfrom=emailrob@risebroadband.net X-Spamd-Result: default: False [-1.94 / 15.00]; ARC_NA(0.00)[]; HAS_REPLYTO(0.00)[emailrob@emailrob.com]; R_DKIM_ALLOW(-0.20)[carrierzone.com:s=mailmia]; RCVD_IN_DNSWL_LOW(-0.10)[66.175.52.148:from]; FROM_HAS_DN(0.00)[]; R_SPF_ALLOW(-0.20)[+ip4:66.175.52.128/26:c]; TO_MATCH_ENVRCPT_ALL(0.00)[]; MIME_GOOD(-0.10)[text/plain]; REPLYTO_DOM_NEQ_FROM_DOM(0.00)[]; TO_DN_NONE(0.00)[]; NEURAL_SPAM_MEDIUM(0.51)[0.513]; RCPT_COUNT_ONE(0.00)[1]; NEURAL_HAM_LONG(-0.85)[-0.854]; DMARC_NA(0.00)[risebroadband.net]; DKIM_TRACE(0.00)[carrierzone.com:+]; NEURAL_HAM_SHORT(-1.00)[-1.000]; FROM_EQ_ENVFROM(0.00)[]; MIME_TRACE(0.00)[0:+]; RCVD_TLS_LAST(0.00)[]; ASN(0.00)[asn:30447, ipnet:66.175.0.0/18, country:US]; RCVD_COUNT_TWO(0.00)[2]; MID_RHS_MATCH_FROM(0.00)[]; DWL_DNSWL_NONE(0.00)[carrierzone.com:dkim] X-ThisMailContainsUnwantedMimeParts: N 2021_dec_19_sun howdy , folks --- it has been a_while , so , i hope that all of you_and_yours are well ; we are doing just fine . in this post , all platforms are fbsd_amd64 , on intel "skylake" "i3/5/7" cpus [ coming_soon , "rocket_lake" , thanks to "avx_512" ] , with "z170" chip_sets , on "atx"_format moboes , in "mid_tower"_sized cases , except as noted . context ------- one specific thing which i liked about fbsd , when i discovered it about 20 years ago [ 3.5.1 , 4.2 ; after using 4bsd on vaxen in grad_school ] , compared to the ms_platform , which it replaced , was that hard_disk_drives were identified by the mobo_socket , to which they were attached , rather than by some probe_order [ anyone remember "drive_letter shifting" ? ] . as i recall , this characteristic remained through my 9.3 boxen . on my 10.3 boxen , "/dev/ada[0-5]" entries appeared , along with "/dev/ad[0-5]" sym_links to these entries . of these two styles , both were valid in "/etc/fstab" ; so , i continued to use the "/dev/ad[0-5]" style . very recently , i have been converting to 11.4 , for regular use , and , soon , i will build a 12.2 box , for testing . i choose to rely upon the last minor_number , for each major_number , until the next major acquires its last minor [ 12.4 ? ] . exceptions to this policy are rare [ simply , i never "got_around_to" 10.4 ] . on my initial 11.4 box , i observed that the "/dev/ad[0-5]" style no_longer appeared . this did_not concern me , until i installed , later , an additional hdd . -- sha_ZAM !!! -- [ thank you , "captain marvel" ] . fbsd has , now , that ms_platform "feature" , which is known , affectionately , as "drive_letter shifting" . i was perplexed ; for a_while , i ruminated . then , i examined "/var/run/dmesg.boot" , in which i found these selected entries [ there are 6 sockets ] : cd0 at ahcich0 ... [ on mobo_sata_socket_1 ] , ada0 at ahcich1 ... [ on mobo_sata_socket_2 ] , ada1 at ahcich2 ... [ on mobo_sata_socket_3 ] , ada2 at ahcich4 ... [ on mobo_sata_socket_5 ] , ada3 at ahcich5 ... [ on mobo_sata_socket_6 ] . the partition "/dev/ada0p3" is mounted at "/" . for cable_management reasons , i prefer to use the nearest socket . research -------- it is remarkable how_much one can learn from the fbsd_handbook , the "man"_pages and "that inter_web thing" [ this is why i have not posted a question , in quite some time ] . so , i began to read . alas , i have found nothing , so_far , which addresses , directly , this concept . i --have-- found some_thing about "hdd_labelling" ; how_ever , none of my --numerous-- drives are "labelled" , including those from foreign platforms ; thus , this does not help . i have enough trouble inventing unique identifiers in my code ; they change over time , almost in_variably . also , i found some_thing about combining the "ata"_driver with the "scsi"_driver [ aha ! ; a potential explanation ] . i have never used scsi drives , for three reasons : a] i do not run a "server_farm" , requiring higher reliability ; b] they are more expensive [ i maintain many back_ups ] and c] their identification depends upon their location along a cable [ like "pata" ] . question -------- from the boot_messages [ above ] , i know that the mobo_socket is known , at some point , during boot . is there a way to identify a sata_hdd , by its mobo_socket , in a manner which will satisfy "/etc/fstab" ? in advance , regarding this matter , i thank every_one for their suggestions , complaints and great_thoughts and i remain very sincerely yours , rob