<?xml version="1.0" encoding="UTF-8"?><rss version="2.0"
	xmlns:content="http://purl.org/rss/1.0/modules/content/"
	xmlns:wfw="http://wellformedweb.org/CommentAPI/"
	xmlns:dc="http://purl.org/dc/elements/1.1/"
	xmlns:atom="http://www.w3.org/2005/Atom"
	xmlns:sy="http://purl.org/rss/1.0/modules/syndication/"
	xmlns:slash="http://purl.org/rss/1.0/modules/slash/"
	>

<channel>
	<title>OSAKANA TAROのメモ帳</title>
	<atom:link href="https://blog.osakana.net/feed" rel="self" type="application/rss+xml" />
	<link>https://blog.osakana.net</link>
	<description>技術的なことをメインにいろいろ書いてくサイトです</description>
	<lastBuildDate>Wed, 04 Nov 2026 09:45:15 +0000</lastBuildDate>
	<language>ja</language>
	<sy:updatePeriod>
	hourly	</sy:updatePeriod>
	<sy:updateFrequency>
	1	</sy:updateFrequency>
	<generator>https://wordpress.org/?v=7.1.4</generator>
	<item>
		<title>Active DirectoryサーバをLDAPサーバとして使っている場合、2026年10月のWindows Updateで接続できなくなる可能性</title>
		<link>https://blog.osakana.net/archives/17669</link>
					<comments>https://blog.osakana.net/archives/17669#respond</comments>
		
		<dc:creator><![CDATA[osakanataro]]></dc:creator>
		<pubDate>Mon, 02 Nov 2026 09:38:40 +0000</pubDate>
				<category><![CDATA[LDAP/ActiveDirectory]]></category>
		<category><![CDATA[NetApp]]></category>
		<category><![CDATA[OS]]></category>
		<category><![CDATA[Windows]]></category>
		<category><![CDATA[サービスや仕組み]]></category>
		<category><![CDATA[ストレージ]]></category>
		<category><![CDATA[メール]]></category>
		<category><![CDATA[認証]]></category>
		<guid isPermaLink="false">https://blog.osakana.net/?p=17669</guid>

					<description><![CDATA[php2shellのパッチをダウンロードするためにONTAPのダウンロードページにアクセスしたら、phpに関する警告の他に、下記の警告も出ていた AD-LDAP Authentication Errors After M &#8230; <p class="link-more"><a href="https://blog.osakana.net/archives/17669" class="more-link"><span class="screen-reader-text">"Active DirectoryサーバをLDAPサーバとして使っている場合、2026年10月のWindows Updateで接続できなくなる可能性" の</span>続きを読む</a></p>]]></description>
										<content:encoded><![CDATA[
<p class="wp-block-paragraph">php2shellのパッチをダウンロードするためにONTAPのダウンロードページにアクセスしたら、phpに関する警告の他に、下記の警告も出ていた</p>



<p class="wp-block-paragraph">AD-LDAP Authentication Errors After Microsoft October 2026 DC Patch Updates<br>Microsoft October 2026 domain controller (DCs) patches may affect AD-LDAP authentication requests from ONTAP to DCs resulting in protocol outrages or login disruptions. See <a href="https://kb.netapp.com/Support_Bulletins/Customer_Bulletins/SU628" target="_blank" rel="noopener">SU628</a> for more details.</p>



<p class="wp-block-paragraph">Active DirectoryサーバをLDAPサーバとして利用している場合、2026年10月のWindows Updateにより、平文のLDAPアクセスが禁止され、署名ありのLDAPアクセスもしくはLDAPSアクセスが必須となる、という話だった</p>



<p class="wp-block-paragraph">具体的なWindows Server側のパッチ<br>　Windows Server 2025 <a href="https://support.microsoft.com/ja-jp/servicing/os/windows-server/2026/10/kb5126646-windows-server-2025-security-update">KB5126646</a><br>　Windows Server 2022 <a href="https://support.microsoft.com/ja-jp/servicing/os/windows-server/2026/10/kb5126655-windows-server-2022-security-update">KB5126655</a><br>　Windows Server 2019 <a href="https://support.microsoft.com/ja-jp/servicing/os/windows-10/2026/10/kb5126651-windows-10-1809-security-update">KB5126651</a><br>　Windows Server 2016 <a href="https://support.microsoft.com/ja-jp/servicing/os/windows-10/2026/10/kb5126868-windows-10-1607-security-update">KB5126868</a></p>



<p class="wp-block-paragraph">基本的に、Windows Server側に適用されたセキュリティ強化設定を解除することはできない</p>



<p class="wp-block-paragraph">Windows Server側のLDAP接続に関するドキュメント「<a href="https://learn.microsoft.com/ja-jp/windows-server/identity/ad-ds/ldap-channel-binding">Active Directory Domain ServicesのLDAPチャネルバインディング概要</a>」と「<a href="https://learn.microsoft.com/ja-jp/windows-server/identity/ad-ds/ldap-signing">Active Directory Domain Services における LDAP 署名の概要</a>」</p>



<p class="wp-block-paragraph">NetApp側のドキュメント「<a href="https://kb-ja.netapp.com/on-prem/ontap/da/NAS/NAS-KBs/October_2026_LDAP_Invalid_Credentials_after_DC_updates_FAQ">2026年10月 ドメイン コントローラ更新後のLDAP無効な認証情報 FAQ</a>」(<a href="https://kb.netapp.com/on-prem/ontap/da/NAS/NAS-KBs/October_2026_LDAP_Invalid_Credentials_after_DC_updates_FAQ">英語版</a>)</p>



<p class="wp-block-paragraph">まずはLDAPSでアクセスするための「<a href="https://learn.microsoft.com/ja-jp/windows-server/identity/ad-ds/configure-ldap-signing-certificates?tabs=microsoft-enterprise-ca">Active Directory Domain Services で SSL 経由で LDAP の証明書を構成する</a>」で、署名などで使用する証明書を用意する</p>



<p class="wp-block-paragraph">この設定については過去に「<a href="https://blog.osakana.net/archives/15622">Windows Server 2025で作ったActive Directory環境でldapsを使えるようにする</a>」でRHEL からopensslコマンドとldapsearchコマンドを使って確認する方法と共に記載している</p>



<p class="wp-block-paragraph">次に「<a href="https://learn.microsoft.com/ja-jp/windows-server/identity/manage-ldap-signing-group-policy?tabs=windows-server-2025">Active Directory Domain Services のグループポリシーを使ってLDAP署名を設定する</a>」でクライアントからのアクセス時にLDAP署名を強制する設定を行う、と</p>



<hr class="wp-block-separator has-alpha-channel-opacity"/>



<h2 class="wp-block-heading">クライアントからアクセスする時に確認するべき点のメモ</h2>



<figure class="wp-block-table"><table class="has-fixed-layout"><tbody><tr><td>アクセステスト内容</td><td>署名不要のDC</td><td>署名必須のDC</td></tr><tr><td>LDAP(389) + Simple bind</td><td>成功</td><td>失敗（Strong Auth Required / LDAPエラー8）</td></tr><tr><td>LDAP(389) + SASL（署名）</td><td>成功</td><td>成功</td></tr><tr><td>LDAPS(636）+ Simple bind</td><td>証明書があれば成功</td><td>証明書があれば成功</td></tr></tbody></table></figure>



<h2 class="wp-block-heading">ldapsearch コマンドで挙動を確認する手法のメモ</h2>



<h3 class="wp-block-heading">① 署名必須かどうか（LDAP+Simple bind）</h3>



<p class="wp-block-paragraph">確認コマンド</p>


<div class="wp-block-syntaxhighlighter-code "><pre class="brush: plain; title: ; notranslate">
ldapsearch -x -H ldap://dc01.example.local \
  -D &quot;user@example.local&quot; -W \
  -b &quot;dc=example,dc=local&quot; -s base &quot;(objectClass=*)&quot; dn
</pre></div>


<p class="wp-block-paragraph">署名必須の場合、下記の様なエラー</p>


<div class="wp-block-syntaxhighlighter-code "><pre class="brush: plain; title: ; notranslate">
ldap_bind: Strong(er) authentication required (8)
  additional info: 00002028: LdapErr: DSID-0C09xxxx, The server requires binds to turn on integrity checking if SSL\TLS are not already active on the connection
</pre></div>


<h3 class="wp-block-heading">② LDAP+SASL（Kerberos）＋署名での接続</h3>



<p class="wp-block-paragraph">確認コマンド</p>


<div class="wp-block-syntaxhighlighter-code "><pre class="brush: plain; title: ; notranslate">
kinit user@EXAMPLE.LOCAL
ldapsearch -Y GSSAPI -H ldap://dc01.example.local -b &quot;dc=example,dc=local&quot; -s base dn

# 署名なしを強制して失敗するか確認（失敗すれば署名必須）
ldapsearch -Y GSSAPI -O &quot;minssf=0,maxssf=0&quot; -H ldap://dc01.example.local -b &quot;dc=example,dc=local&quot; -s base dn
</pre></div>


<h3 class="wp-block-heading">③ LDAPSでのテスト</h3>



<p class="wp-block-paragraph">確認コマンド</p>


<div class="wp-block-syntaxhighlighter-code "><pre class="brush: plain; title: ; notranslate">
# 証明書・TLSバージョンの確認
openssl s_client -connect dc01.example.local:636 -showcerts &amp;lt;/dev/null

# LDAPSでbind
LDAPTLS_CACERT=/path/to/ca.pem \
ldapsearch -x -H ldaps://dc01.example.local \
  -D &quot;user@example.local&quot; -W -b &quot;dc=example,dc=local&quot; -s base dn

# StartTLS（389）
ldapsearch -x -ZZ -H ldap://dc01.example.local -D &quot;user@example.local&quot; -W -b &quot;dc=example,dc=local&quot; -s base dn
</pre></div>


<p class="wp-block-paragraph">自己署名環境の場合、「LDAPTLS_REQCERT=never」を設定することで証明書検証を省略できる</p>



<p class="wp-block-paragraph">LDAPS上でGSSAPIを使う場合、ADはTLS上のsign/sealを拒否するため「-O maxssf=0」オプションの追加、もしくは ldap.conf に「SASL_SECPROPS maxssf=0」を設定する</p>



<h2 class="wp-block-heading">Windows環境で確認するためのメモ</h2>



<h3 class="wp-block-heading">PowerShellの場合</h3>


<div class="wp-block-syntaxhighlighter-code "><pre class="brush: plain; title: ; notranslate">
Add-Type -AssemblyName System.DirectoryServices.Protocols
$cred = Get-Credential   # user@example.local

# 389 + Simple bind（署名必須なら例外）
$c = New-Object System.DirectoryServices.Protocols.LdapConnection(&quot;dc01.example.local:389&quot;)
$c.SessionOptions.ProtocolVersion = 3
$c.AuthType = &#x5B;System.DirectoryServices.Protocols.AuthType]::Basic
try { $c.Bind($cred.GetNetworkCredential()); &quot;389 Simple bind: 成功（署名不要）&quot; }
catch { &quot;389 Simple bind: 失敗 -&gt; $($_.Exception.InnerException.Message)&quot; }

# 636 LDAPS
$s = New-Object System.DirectoryServices.Protocols.LdapConnection(&quot;dc01.example.local:636&quot;)
$s.SessionOptions.ProtocolVersion = 3
$s.SessionOptions.SecureSocketLayer = $true
$s.AuthType = &#x5B;System.DirectoryServices.Protocols.AuthType]::Basic
try { $s.Bind($cred.GetNetworkCredential()); &quot;LDAPS: 成功&quot; }
catch { &quot;LDAPS: 失敗 -&gt; $($_.Exception.InnerException.Message)&quot; }
</pre></div>


<p class="wp-block-paragraph"><code>Test-NetConnection dc01 -Port 636</code> はTCP疎通しか見ないため、TLSが成立するかの確認には上記のbindテストを使う</p>



<p class="wp-block-paragraph">また、クライアント側でレジストリが設定されているか確認</p>


<div class="wp-block-syntaxhighlighter-code "><pre class="brush: plain; title: ; notranslate">
Get-ItemProperty HKLM:\SYSTEM\CurrentControlSet\Services\LDAP -Name LDAPClientIntegrity
# 0=なし, 1=ネゴシエート(既定), 2=必須
</pre></div>


<h2 class="wp-block-heading">Active Directoryサーバ側で確認する手法</h2>



<h4 class="wp-block-heading">レジストリ「HKLM\SYSTEM\CurrentControlSet\Services\NTDS\Parameters」を確認</h4>



<p class="wp-block-paragraph">LDAPServerIntegrity が「1」は署名無し、「2」は署名必須</p>



<p class="wp-block-paragraph">LdapEnforceChannelBinding が「0」無効、「1」サポートしてるなら使う、「2」必須</p>



<p class="wp-block-paragraph">GPOでの設定項目「ドメイン コントローラー: LDAP サーバー署名必須」</p>



<h4 class="wp-block-heading">イベントログでの確認</h4>



<p class="wp-block-paragraph">Directory Serviceのイベントログに出てくるイベントID</p>



<p class="wp-block-paragraph">2886/2887：署名なしbindの存在・件数の警告</p>



<p class="wp-block-paragraph">2889：署名なしbindを行ったクライアントIPとアカウント（「16 LDAP Interface Events」の診断ログを2に設定して出力）</p>



<p class="wp-block-paragraph">3039～3041：チャネルバインディング関連</p>



<p class="wp-block-paragraph"></p>
]]></content:encoded>
					
					<wfw:commentRss>https://blog.osakana.net/archives/17669/feed</wfw:commentRss>
			<slash:comments>0</slash:comments>
		
		
			</item>
		<item>
		<title>4インチ前後で480&#215;800の小型E-INK電子書籍端末群を比較する(Xteink X4 Pro,M5Stack PaperMono, reTerminal Sticky, Metalio E-INK4, Murphy M4)</title>
		<link>https://blog.osakana.net/archives/17631</link>
					<comments>https://blog.osakana.net/archives/17631#respond</comments>
		
		<dc:creator><![CDATA[osakanataro]]></dc:creator>
		<pubDate>Thu, 17 Sep 2026 05:02:08 +0000</pubDate>
				<category><![CDATA[CPU]]></category>
		<category><![CDATA[ESP8266 / ESP32]]></category>
		<category><![CDATA[XTEINK]]></category>
		<category><![CDATA[プログラム]]></category>
		<category><![CDATA[マイナーハード]]></category>
		<category><![CDATA[電子書籍]]></category>
		<guid isPermaLink="false">https://blog.osakana.net/?p=17631</guid>

					<description><![CDATA[4インチ前後で480&#215;800解像度の小型E-INK端末がいろいろ出ている aliexpressで見かけるやつでも探してみるとgithubで利用できるソースコードが公開されているものもあったりする それらをまとめ &#8230; <p class="link-more"><a href="https://blog.osakana.net/archives/17631" class="more-link"><span class="screen-reader-text">"4インチ前後で480&#215;800の小型E-INK電子書籍端末群を比較する(Xteink X4 Pro,M5Stack PaperMono, reTerminal Sticky, Metalio E-INK4, Murphy M4)" の</span>続きを読む</a></p>]]></description>
										<content:encoded><![CDATA[
<p class="wp-block-paragraph">4インチ前後で480&#215;800解像度の小型E-INK端末がいろいろ出ている</p>



<p class="wp-block-paragraph">aliexpressで見かけるやつでも探してみるとgithubで利用できるソースコードが公開されているものもあったりする</p>



<p class="wp-block-paragraph">それらをまとめてみた</p>



<figure class="wp-block-image size-large"><a href="https://blog.osakana.net/wp-content/uploads/2026/09/image-3.png"><img fetchpriority="high" decoding="async" width="1024" height="551" src="https://blog.osakana.net/wp-content/uploads/2026/09/image-3-1024x551.png" alt="" class="wp-image-17642" srcset="https://blog.osakana.net/wp-content/uploads/2026/09/image-3-1024x551.png 1024w, https://blog.osakana.net/wp-content/uploads/2026/09/image-3-300x161.png 300w, https://blog.osakana.net/wp-content/uploads/2026/09/image-3-767x413.png 767w, https://blog.osakana.net/wp-content/uploads/2026/09/image-3.png 1161w" sizes="(max-width: 767px) 89vw, (max-width: 1000px) 54vw, (max-width: 1071px) 543px, 580px" /></a></figure>



<p class="wp-block-paragraph">claude opus5に比較表作らせた時のお勧めについては下記</p>



<figure class="wp-block-image size-full"><a href="https://blog.osakana.net/wp-content/uploads/2026/09/A78473E7-9651-4A2B-AAB6-9B94F5F220E7.png"><img decoding="async" width="809" height="605" src="https://blog.osakana.net/wp-content/uploads/2026/09/A78473E7-9651-4A2B-AAB6-9B94F5F220E7.png" alt="" class="wp-image-17641" srcset="https://blog.osakana.net/wp-content/uploads/2026/09/A78473E7-9651-4A2B-AAB6-9B94F5F220E7.png 809w, https://blog.osakana.net/wp-content/uploads/2026/09/A78473E7-9651-4A2B-AAB6-9B94F5F220E7-300x224.png 300w, https://blog.osakana.net/wp-content/uploads/2026/09/A78473E7-9651-4A2B-AAB6-9B94F5F220E7-768x574.png 768w" sizes="(max-width: 767px) 89vw, (max-width: 1000px) 54vw, (max-width: 1071px) 543px, 580px" /></a></figure>



<p class="wp-block-paragraph"></p>



<p class="wp-block-paragraph">以下は検索用の文字表記版</p>



<figure class="wp-block-table"><table class="has-fixed-layout"><thead><tr><th>製品名</th><th><strong>X4 Pro</strong></th><th><strong>X4 Classic</strong></th><th><strong>Murphy M4</strong></th><th><strong>PaperMono</strong></th><th><strong>reTerminal Sticky</strong></th><th><strong>Metalio E-INK4</strong></th></tr></thead><tbody><tr><td>SoC</td><td>ESP32-S3</td><td>ESP32-S3</td><td>ESP32-S3</td><td>ESP32-S3R8</td><td>ESP32-S3R8</td><td>ESP32-S3</td></tr><tr><td>PSRAM / Flash</td><td>8 MB Octal / ? MB</td><td><strong>なし</strong> / 4 MB</td><td>8 MB Quad / 16 MB</td><td>8 MB Octal / 16 MB</td><td>8 MB Octal / <strong>32 MB</strong>?</td><td>?MB Octal / 16 MB</td></tr><tr><td>画面仕様</td><td>4.3&#8243; 480×800 219 ppi</td><td>4.3&#8243; 480×800 219 ppi</td><td>4.26&#8243; 480×800 219 ppi</td><td>3.97&#8243; 480×800 <strong>235 ppi</strong></td><td>3.97&#8243; 800×480 <strong>235 ppi</strong></td><td>3.97&#8243; 800×480 <strong>235 ppi</strong></td></tr><tr><td>E-INK表示機構</td><td>SSD1677</td><td>SSD1677</td><td>SSD1677</td><td>SSD1677</td><td>SSD1677</td><td>SSD1677</td></tr><tr><td>タッチ</td><td>○<br>GT911 (0x5D)</td><td>×</td><td>○<br>FT6336U(0x2E)</td><td>○<br>FT6336G(0x38)</td><td>○<br>GT911(0x5D)</td><td>○<br>CST816S</td></tr><tr><td>物理ボタン</td><td>計3個<br>電源<br>側面2</td><td>計7個<br>電源<br>側面2<br>前面2<br>上面1</td><td>計3個<br>決定&amp;電源<br>UP<br>Down</td><td>計3個<br>電源<br>Up<br>Down</td><td>計3個<br>決定&amp;電源<br>UP<br>Down</td><td>見た目的には計7個<br>内部的には3個+仮想ボタンらしい</td></tr><tr><td><strong>フロントライト</strong></td><td><strong>○ 2ch 暖/寒</strong></td><td>×</td><td><strong>○ 2ch 暖/寒</strong></td><td><strong>○ 1ch 輝度のみ</strong></td><td>×</td><td>×</td></tr><tr><td>バッテリ</td><td>1,100 mAh<br>CW2017</td><td>920 mAh<br>CW2017</td><td>容量非公開<br>ADC</td><td>1,150 mAh<br>ADC</td><td>750 mAh<br>BQ27220</td><td>容量非公開<br>BQ27220</td></tr><tr><td>RTC</td><td>BM8563(0x51)</td><td>なし</td><td>なし</td><td>RX8130(0x32)</td><td>なし</td><td>PCF8563</td></tr><tr><td>充電</td><td><strong>ポゴピン</strong>（USB-C コネクタなし）</td><td><strong>ポゴピン</strong>（USB-C コネクタなし）</td><td>USB-C</td><td>USB-C</td><td>USB-C</td><td>USB-C</td></tr><tr><td>microSD</td><td>○</td><td>○</td><td>○</td><td>○</td><td>○</td><td>○</td></tr><tr><td>IMU</td><td>なし</td><td>QMI8658</td><td>なし</td><td>BMI270</td><td>6軸IMU</td><td>SC7A20H</td></tr><tr><td>音声</td><td>なし</td><td>なし</td><td>スピーカーあり?</td><td>PDM マイク+ブザー</td><td>マイク+ブザー</td><td><strong>スピーカー+マイク+BT</strong></td></tr><tr><td>無線</td><td>Wi-Fi/BT</td><td>Wi-Fi/BT</td><td>Wi-Fi/BT</td><td>Wi-Fi/BT, LoRa</td><td>Wi-Fi/BT</td><td>Wi-Fi + 外付BT</td></tr><tr><td>重量</td><td>72g</td><td>68g</td><td></td><td>74.7g</td><td>70g</td><td></td></tr><tr><td>その他</td><td>吸着磁石</td><td>吸着磁石</td><td>側面3ボタン</td><td>IMU, RTC, RGB LED</td><td>温湿度, IMU, 磁石</td><td>加速度, RTC, 振動, カメラ端子</td></tr><tr><td><strong>CrossPoint</strong></td><td><strong>公式</strong></td><td><strong>公式</strong></td><td>PR <a href="https://github.com/crosspoint-reader/crosspoint-reader/pull/2930" target="_blank" rel="noopener">crosspoint-reader/crosspoint-reader#2930</a> </td><td><strong>公式</strong></td><td><strong>公式</strong></td><td><strong>未対応</strong></td></tr><tr><td>関連資料</td><td>&#8211;</td><td>&#8211;</td><td><a href="https://github.com/crosspoint-reader/Murphy">機器資料</a><br><a href="https://github.com/czdaniel/crosspoint-murphy-m4">crosspointの移植github</a></td><td><a href="https://docs.m5stack.com/ja/core/PaperMono">公式資料</a></td><td><a href="https://www.seeedstudio.com/sticky/docs/">公式資料</a><br><a href="https://github.com/Seeed-Projects/reterminal-sticky-playground-registry">公式github</a></td><td><a href="https://github.com/CloudZao/Metalio-E-INK4">機器資料</a></td></tr></tbody></table></figure>



<figure class="wp-block-table"><table class="has-fixed-layout"><tbody><tr><td>読書最優先 Xteink X4 Pro</td><td>2ch 寒暖照明<br>GT911 によるタッチ操作<br>バッテリー残量検出が正確<br>完成品としての仕上げが最も高い<br>microSDへのアクセスはSDMMC 1bitとそれなり<br>欠点はポゴピン充電で、汎用のUSB-C ケーブルが使えないこと</td></tr><tr><td>ボタン派・軽量 Xteink X4 Classic</td><td>68 g / 4.9 mm<br>個別ボタン7個で全操作が完結<br>バッテリー残量検出が正確<br>QMI8658 使った物理的に振ってページ送り<br>初代X4より高速化<br>microSDへのアクセスはSDMMC 1bitとX4より早い<br>欠点は 照明とタッチがないこと</td></tr><tr><td>読書＋工作 M5Stack PaperMono</td><td>1ch 照明<br>タッチ対応<br>LoRa と NFC に対応したHW<br>microSDへのアクセスはSDMMC 4bitと高速<br>欠点は、開発キット寄りの筐体と次回生産時期が2027年予定</td></tr><tr><td>最安で弄る reTerminal Sticky</td><td>センサー類が搭載されていて、読書専用機というより貼れるサイネージ兼リーダーという作り<br>欠点は、ライトなし、とmicroSDアクセスがSPIと共有の為、遅いこと</td></tr><tr><td>2ch 照明＋自前ビルド Murphy M4</td><td>2ch寒暖照明<br>microSDへのアクセスはSDMMC 4bitと高速<br>欠点は、crosspoint reader公式非対応と、バッテリー残量検出がADCによる電圧からの推測のみということ</td></tr><tr><td>AI 端末自作 Metalio E-INK4</td><td>スピーカー・マイク・BT 音声・振動・RTC・カメラ端子を積んだ音声アシスタント基板。<br>microSDへのアクセスはSDMMC 1bitとそれなり<br>欠点は、現状crosspoint reader未対応、ライトなし、ということ</td></tr></tbody></table></figure>



<p class="wp-block-paragraph">下記は製品写真</p>



<figure class="wp-block-image size-full"><a href="https://blog.osakana.net/wp-content/uploads/2026/09/3F2C63A6-5431-4BEF-A2C0-B3B746A81EA5.png"><img decoding="async" width="412" height="488" src="https://blog.osakana.net/wp-content/uploads/2026/09/3F2C63A6-5431-4BEF-A2C0-B3B746A81EA5.png" alt="" class="wp-image-17639" srcset="https://blog.osakana.net/wp-content/uploads/2026/09/3F2C63A6-5431-4BEF-A2C0-B3B746A81EA5.png 412w, https://blog.osakana.net/wp-content/uploads/2026/09/3F2C63A6-5431-4BEF-A2C0-B3B746A81EA5-253x300.png 253w" sizes="(max-width: 412px) 100vw, 412px" /></a></figure>



<figure class="wp-block-image size-large"><a href="https://blog.osakana.net/wp-content/uploads/2026/09/image-1.png"><img loading="lazy" decoding="async" width="1024" height="1024" src="https://blog.osakana.net/wp-content/uploads/2026/09/image-1-1024x1024.png" alt="" class="wp-image-17637" srcset="https://blog.osakana.net/wp-content/uploads/2026/09/image-1-1024x1024.png 1024w, https://blog.osakana.net/wp-content/uploads/2026/09/image-1-150x150.png 150w, https://blog.osakana.net/wp-content/uploads/2026/09/image-1-300x300.png 300w, https://blog.osakana.net/wp-content/uploads/2026/09/image-1-768x768.png 768w, https://blog.osakana.net/wp-content/uploads/2026/09/image-1-1536x1536.png 1536w, https://blog.osakana.net/wp-content/uploads/2026/09/image-1-100x100.png 100w, https://blog.osakana.net/wp-content/uploads/2026/09/image-1.png 1600w" sizes="auto, (max-width: 767px) 89vw, (max-width: 1000px) 54vw, (max-width: 1071px) 543px, 580px" /></a></figure>



<figure class="wp-block-image size-large"><a href="https://blog.osakana.net/wp-content/uploads/2026/09/image-2.png"><img loading="lazy" decoding="async" width="673" height="1024" src="https://blog.osakana.net/wp-content/uploads/2026/09/image-2-673x1024.png" alt="" class="wp-image-17638" srcset="https://blog.osakana.net/wp-content/uploads/2026/09/image-2-673x1024.png 673w, https://blog.osakana.net/wp-content/uploads/2026/09/image-2-197x300.png 197w, https://blog.osakana.net/wp-content/uploads/2026/09/image-2.png 755w" sizes="auto, (max-width: 673px) 100vw, 673px" /></a></figure>



<figure class="wp-block-image size-large"><a href="https://blog.osakana.net/wp-content/uploads/2026/09/image.png"><img loading="lazy" decoding="async" width="1024" height="1024" src="https://blog.osakana.net/wp-content/uploads/2026/09/image-1024x1024.png" alt="" class="wp-image-17635" srcset="https://blog.osakana.net/wp-content/uploads/2026/09/image-1024x1024.png 1024w, https://blog.osakana.net/wp-content/uploads/2026/09/image-150x150.png 150w, https://blog.osakana.net/wp-content/uploads/2026/09/image-300x300.png 300w, https://blog.osakana.net/wp-content/uploads/2026/09/image-768x768.png 768w, https://blog.osakana.net/wp-content/uploads/2026/09/image-100x100.png 100w, https://blog.osakana.net/wp-content/uploads/2026/09/image.png 1200w" sizes="auto, (max-width: 767px) 89vw, (max-width: 1000px) 54vw, (max-width: 1071px) 543px, 580px" /></a></figure>



<p class="wp-block-paragraph"></p>



<p class="wp-block-paragraph"></p>



<p class="wp-block-paragraph"></p>
]]></content:encoded>
					
					<wfw:commentRss>https://blog.osakana.net/archives/17631/feed</wfw:commentRss>
			<slash:comments>0</slash:comments>
		
		
			</item>
		<item>
		<title>Androidにつないだ日本語配列Bluetoothキーボードで記号がちゃんと入力できない</title>
		<link>https://blog.osakana.net/archives/17606</link>
					<comments>https://blog.osakana.net/archives/17606#respond</comments>
		
		<dc:creator><![CDATA[osakanataro]]></dc:creator>
		<pubDate>Wed, 19 Aug 2026 02:03:45 +0000</pubDate>
				<category><![CDATA[未分類]]></category>
		<guid isPermaLink="false">https://blog.osakana.net/?p=17606</guid>

					<description><![CDATA[だいぶ前に購入したBluetooth キーボード SK-9071 をAndroidタブレットで使ってみようとしたところ、キーボードが英語配列として認識されたようで、記号の入力がうまくいかない状態でした。 ぐぐると2022 &#8230; <p class="link-more"><a href="https://blog.osakana.net/archives/17606" class="more-link"><span class="screen-reader-text">"Androidにつないだ日本語配列Bluetoothキーボードで記号がちゃんと入力できない" の</span>続きを読む</a></p>]]></description>
										<content:encoded><![CDATA[
<p class="wp-block-paragraph">だいぶ前に購入したBluetooth キーボード SK-9071 をAndroidタブレットで使ってみようとしたところ、キーボードが英語配列として認識されたようで、記号の入力がうまくいかない状態でした。</p>



<p class="wp-block-paragraph">ぐぐると2022年の「<a href="https://osato512.hatenablog.jp/entry/2022/01/31/144414">Androidタブレットへの日本語配列キーボードの繋ぎ方</a>」という記事があり、そこではGboardだとうまく動かないので、サポート終了してるGoogle日本語入力を使った、と書かれている。</p>



<p class="wp-block-paragraph">いろいろ確認したところ、2026年時点ではGboardでもなんとかなることが確認出来た。</p>



<p class="wp-block-paragraph">ただ、元凶はGboardがしっかりしてないから、ということには代わりは無かった</p>



<p class="wp-block-paragraph">その現況のGboardから見えるBluetoothキーボードの配列に関する設定が下記の様に「日本語 109A 配列」となっていても、@ キーを押しても @が入力できないという状況の時に何をすればいいのか</p>



<figure class="wp-block-image size-large"><a href="https://blog.osakana.net/wp-content/uploads/2026/08/1000000524.png"><img loading="lazy" decoding="async" width="640" height="1024" src="https://blog.osakana.net/wp-content/uploads/2026/08/1000000524-640x1024.png" alt="" class="wp-image-17608" srcset="https://blog.osakana.net/wp-content/uploads/2026/08/1000000524-640x1024.png 640w, https://blog.osakana.net/wp-content/uploads/2026/08/1000000524-188x300.png 188w, https://blog.osakana.net/wp-content/uploads/2026/08/1000000524-768x1229.png 768w, https://blog.osakana.net/wp-content/uploads/2026/08/1000000524-960x1536.png 960w, https://blog.osakana.net/wp-content/uploads/2026/08/1000000524.png 1200w" sizes="auto, (max-width: 640px) 100vw, 640px" /></a></figure>



<p class="wp-block-paragraph">それはBluetoothキーボードでCtrlキーとスペースキーを同時押しすること。</p>



<p class="wp-block-paragraph">これにより、Androidシステムの言語切り替えの仕組みが動いて、日本語配列が認識されました。</p>



<p class="wp-block-paragraph">ただ、よくわからないのは、これで英語配列→日本語配列になったということは、もう1回、Ctrl+Spaceを押すと日本語配列→英語配列になるのか？と思ったら、2回目以降はただの変換モードのオン/オフに変わりました。</p>



<p class="wp-block-paragraph">察するに、「Gboard 英語配列」で動作していたものを設定上は「Gboard 日本語109A配列」に変更しても内部的にはまだ切り替わっていなくて、Ctrl+Spaceを押すことで「Gboard 日本語109A配列」設定に変わっていることが認識されたんじゃないか、ということですね</p>
]]></content:encoded>
					
					<wfw:commentRss>https://blog.osakana.net/archives/17606/feed</wfw:commentRss>
			<slash:comments>0</slash:comments>
		
		
			</item>
		<item>
		<title>Windows版Claude DesktopのcodeでUbuntuへのsshが失敗する</title>
		<link>https://blog.osakana.net/archives/17577</link>
					<comments>https://blog.osakana.net/archives/17577#respond</comments>
		
		<dc:creator><![CDATA[osakanataro]]></dc:creator>
		<pubDate>Tue, 11 Aug 2026 14:24:28 +0000</pubDate>
				<category><![CDATA[AI]]></category>
		<category><![CDATA[Claude]]></category>
		<category><![CDATA[Linux]]></category>
		<category><![CDATA[OS]]></category>
		<category><![CDATA[Ubuntu / Debian]]></category>
		<category><![CDATA[Windows]]></category>
		<category><![CDATA[プログラム]]></category>
		<guid isPermaLink="false">https://blog.osakana.net/?p=17577</guid>

					<description><![CDATA[Windows環境にClaude Desktopをインストールして、codeにてubuntuサーバへのsshを設定してみたところ接続できなかった 先にうちの事例での答えを書いておくと、原因は2つ ・WindowsのOpe &#8230; <p class="link-more"><a href="https://blog.osakana.net/archives/17577" class="more-link"><span class="screen-reader-text">"Windows版Claude DesktopのcodeでUbuntuへのsshが失敗する" の</span>続きを読む</a></p>]]></description>
										<content:encoded><![CDATA[
<p class="wp-block-paragraph">Windows環境にClaude Desktopをインストールして、codeにてubuntuサーバへのsshを設定してみたところ接続できなかった</p>



<figure class="wp-block-image size-full"><a href="https://blog.osakana.net/wp-content/uploads/2026/08/image-20.png"><img loading="lazy" decoding="async" width="493" height="115" src="https://blog.osakana.net/wp-content/uploads/2026/08/image-20.png" alt="" class="wp-image-17579" srcset="https://blog.osakana.net/wp-content/uploads/2026/08/image-20.png 493w, https://blog.osakana.net/wp-content/uploads/2026/08/image-20-300x70.png 300w" sizes="auto, (max-width: 493px) 100vw, 493px" /></a></figure>


<div class="wp-block-syntaxhighlighter-code "><pre class="brush: plain; title: ; notranslate">
pcuser@192.168.1.21に接続できませんでした
SSH 接続を確立できませんでした。ホストに到達可能であること、および SSH の設定が正しいことを確認してから、再試行してください。詳細なエラーは以下に表示されています。
Host denied (verification failed)
</pre></div>


<p class="wp-block-paragraph">先にうちの事例での答えを書いておくと、原因は2つ</p>



<p class="wp-block-paragraph">・WindowsのOpenSSHをインストールしていなかった<br>　→ インストールした</p>



<p class="wp-block-paragraph">・環境変数HOMEが未設定だったこと<br>　→ 設定した</p>



<p class="wp-block-paragraph">これで解決しました。</p>



<p class="wp-block-paragraph">解決に至るまでの経緯として。以下にメモを残しておく</p>



<p class="wp-block-paragraph">まずClaude Codeでのsshトラブルの際に、Claude code側のssh設定は以下で確認できる</p>


<div class="wp-block-syntaxhighlighter-code "><pre class="brush: powershell; title: ; notranslate">
Get-Content &quot;$env:LOCALAPPDATA\Packages\Claude_pzs8sxrjxfjjc\LocalCache\Roaming\Claude\ssh_configs.json&quot;
</pre></div>


<p class="wp-block-paragraph">設定ファイルをみてもまあわかることはないかな</p>



<p class="wp-block-paragraph">実際のログを確認するには以下をPowerShellで実行して確認</p>


<div class="wp-block-syntaxhighlighter-code "><pre class="brush: powershell; title: ; notranslate">
Get-Content &quot;$env:LOCALAPPDATA\Packages\Claude_pzs8sxrjxfjjc\LocalCache\Roaming\Claude\logs\ssh.log&quot; -Tail 60
</pre></div>


<p class="wp-block-paragraph">今回は下記の様になっていた。</p>


<div class="wp-block-syntaxhighlighter-code "><pre class="brush: bash; title: ; notranslate">
2026-08-11 22:28:06 &#x5B;info] &#x5B;ClaudeSSHManager] Initialized with version 5db5e4a12f88487e47c2c48259b69a2d630bb3f7
2026-08-11 22:28:08 &#x5B;info] &#x5B;RemoteServerController] Ensuring server is ready on pcuser@192.168.1.21 (trigger: warm_up)
2026-08-11 22:28:08 &#x5B;info] &#x5B;BinaryDeployment] Setting up remote server on pcuser@192.168.1.21
2026-08-11 22:28:08 &#x5B;info] &#x5B;SSH2Connection] Resolved pcuser@192.168.1.21 -&gt; pcuser@192.168.1.21:22 (identityFiles: 0)
2026-08-11 22:28:08 &#x5B;warn] &#x5B;SSH2Connection] Host 192.168.1.21:22 is not in known_hosts
2026-08-11 22:28:08 &#x5B;info] &#x5B;SSH2Connection] Connecting to pcuser@192.168.1.21:22 (agent: none, keys: 1&#x5B;ssh-ed25519], proxy: false, keyboard: true)
2026-08-11 22:28:08 &#x5B;warn] &#x5B;SSH2Connection] Rejecting host key for 192.168.1.21:22 — host is not in known_hosts
2026-08-11 22:28:08 &#x5B;error] &#x5B;SSH2Connection] Connection error: Host denied (verification failed)
2026-08-11 22:28:08 &#x5B;error] &#x5B;RemoteServerController] Connection failed (79ms, trigger: warm_up): Host denied (verification failed)
2026-08-11 22:28:11 &#x5B;info] &#x5B;RemoteServerController] Ensuring server is ready on pcuser@192.168.1.21 (trigger: send_message)
2026-08-11 22:28:11 &#x5B;info] &#x5B;BinaryDeployment] Setting up remote server on pcuser@192.168.1.21
2026-08-11 22:28:11 &#x5B;info] &#x5B;SSH2Connection] Resolved pcuser@192.168.1.21 -&gt; pcuser@192.168.1.21:22 (identityFiles: 0)
2026-08-11 22:28:11 &#x5B;warn] &#x5B;SSH2Connection] Host 192.168.1.21:22 is not in known_hosts
2026-08-11 22:28:11 &#x5B;info] &#x5B;SSH2Connection] Connecting to pcuser@192.168.1.21:22 (agent: none, keys: 1&#x5B;ssh-ed25519], proxy: false, keyboard: true)
2026-08-11 22:28:11 &#x5B;warn] &#x5B;SSH2Connection] Rejecting host key for 192.168.1.21:22 — host is not in known_hosts
2026-08-11 22:28:11 &#x5B;error] &#x5B;SSH2Connection] Connection error: Host denied (verification failed)
2026-08-11 22:28:11 &#x5B;error] &#x5B;RemoteServerController] Connection failed (46ms, trigger: send_message): Host denied (verification failed)
2026-08-11 22:28:19 &#x5B;info] &#x5B;RemoteServerController] Detaching (leaving daemon running)
2026-08-11 22:34:38 &#x5B;info] &#x5B;ClaudeSSHManager] Initialized with version 5db5e4a12f88487e47c2c48259b69a2d630bb3f7
2026-08-11 22:34:40 &#x5B;info] &#x5B;RemoteServerController] Ensuring server is ready on pcuser@192.168.1.21 (trigger: warm_up)
2026-08-11 22:34:40 &#x5B;info] &#x5B;BinaryDeployment] Setting up remote server on pcuser@192.168.1.21
2026-08-11 22:34:40 &#x5B;info] &#x5B;SSH2Connection] Resolved pcuser@192.168.1.21 -&gt; pcuser@192.168.1.21:22 (identityFiles: 0)
2026-08-11 22:34:40 &#x5B;warn] &#x5B;SSH2Connection] Host 192.168.1.21:22 is not in known_hosts
2026-08-11 22:34:40 &#x5B;info] &#x5B;SSH2Connection] Connecting to pcuser@192.168.1.21:22 (agent: none, keys: 1&#x5B;ssh-ed25519], proxy: false, keyboard: true)
2026-08-11 22:34:40 &#x5B;warn] &#x5B;SSH2Connection] Rejecting host key for 192.168.1.21:22 — host is not in known_hosts
2026-08-11 22:34:40 &#x5B;error] &#x5B;SSH2Connection] Connection error: Host denied (verification failed)
2026-08-11 22:34:40 &#x5B;error] &#x5B;RemoteServerController] Connection failed (109ms, trigger: warm_up): Host denied (verification failed)
</pre></div>


<p class="wp-block-paragraph">注目すべき点は「identityFiles: 0」</p>



<p class="wp-block-paragraph">ホームディレクトリにある.ssh\known_hosts には複数の定義があるのに、「0」と報告されている</p>



<p class="wp-block-paragraph">何が問題かを確認するため、HOME関連の環境変数定義の状態を確認</p>


<div class="wp-block-syntaxhighlighter-code "><pre class="brush: powershell; title: ; notranslate">
&quot;HOME       = $env:HOME&quot;
&quot;USERPROFILE= $env:USERPROFILE&quot;
&quot;HOMEDRIVE  = $env:HOMEDRIVE&quot;
&quot;HOMEPATH   = $env:HOMEPATH&quot;
</pre></div>


<p class="wp-block-paragraph">そうしたら、HOMEが設定されていないことが判明</p>


<div class="wp-block-syntaxhighlighter-code "><pre class="brush: powershell; title: ; notranslate">
PS C:\Users\OSAKANATARO&gt; &quot;HOME       = $env:HOME&quot;
HOME       =
PS C:\Users\OSAKANATARO&gt; &quot;USERPROFILE= $env:USERPROFILE&quot;
USERPROFILE= C:\Users\OSAKANATARO
PS C:\Users\OSAKANATARO&gt; &quot;HOMEDRIVE  = $env:HOMEDRIVE&quot;
HOMEDRIVE  = C:
PS C:\Users\OSAKANATARO&gt; &quot;HOMEPATH   = $env:HOMEPATH&quot;
HOMEPATH   = \Users\OSAKANATARO
PS C:\Users\OSAKANATARO&gt; 
</pre></div>


<p class="wp-block-paragraph"></p>


<div class="wp-block-syntaxhighlighter-code "><pre class="brush: powershell; title: ; notranslate">
PS C:\Users\OSAKANATARO&gt; &#x5B;Environment]::SetEnvironmentVariable(&quot;HOME&quot;, $env:USERPROFILE, &quot;User&quot;)
</pre></div>


<p class="wp-block-paragraph">設定後、Windows再起動</p>


<div class="wp-block-syntaxhighlighter-code "><pre class="brush: powershell; title: ; notranslate">
PS C:\Users\OSAKANATARO&gt; &quot;HOME       = $env:HOME&quot;
HOME       = C:\Users\OSAKANATARO
PS C:\Users\OSAKANATARO&gt; &quot;USERPROFILE= $env:USERPROFILE&quot;
USERPROFILE= C:\Users\OSAKANATARO
PS C:\Users\OSAKANATARO&gt; &quot;HOMEDRIVE  = $env:HOMEDRIVE&quot;
HOMEDRIVE  = C:
PS C:\Users\OSAKANATARO&gt; &quot;HOMEPATH   = $env:HOMEPATH&quot;
HOMEPATH   = \Users\OSAKANATARO
PS C:\Users\OSAKANATARO&gt;
</pre></div>


<p class="wp-block-paragraph">しかし、結果は変わらず</p>



<p class="wp-block-paragraph">Claude自身に思考させるとSysteminternalの<a href="https://learn.microsoft.com/ja-jp/sysinternals/downloads/procmon">プロセス モニター</a>で確認しろとのこと</p>



<p class="wp-block-paragraph"><code>Procmon64.exe</code> を管理者実行。</p>



<ol class="wp-block-list">
<li><code>Ctrl+L</code> でフィルタを開く</li>



<li><code>Path</code> <code>contains</code> <code>ssh</code> → Add → OK</li>



<li><code>Ctrl+X</code> で既存イベントをクリア</li>



<li>Claude Desktop で接続を試行</li>



<li><code>Ctrl+E</code> でキャプチャ停止</li>
</ol>



<figure class="wp-block-image size-full"><a href="https://blog.osakana.net/wp-content/uploads/2026/08/image-21.png"><img loading="lazy" decoding="async" width="588" height="346" src="https://blog.osakana.net/wp-content/uploads/2026/08/image-21.png" alt="" class="wp-image-17583" srcset="https://blog.osakana.net/wp-content/uploads/2026/08/image-21.png 588w, https://blog.osakana.net/wp-content/uploads/2026/08/image-21-300x177.png 300w" sizes="auto, (max-width: 588px) 100vw, 588px" /></a></figure>



<p class="wp-block-paragraph">なんかssh.exe を捜索してるログがたくさん・・・</p>



<p class="wp-block-paragraph">Windows提供のOpenSSHを入れろとのこと</p>



<p class="wp-block-paragraph">「Get-WindowsCapability -Online -Name OpenSSH.Client*」を実行して確認。</p>


<div class="wp-block-syntaxhighlighter-code "><pre class="brush: powershell; title: ; notranslate">
PS C:\Users\OSAKANATARO&gt; Get-WindowsCapability -Online -Name OpenSSH.Client*


Name         : OpenSSH.Client~~~~0.0.1.0
State        : NotPresent
DisplayName  : OpenSSH クライアント
Description  : OpenSSH ベースのセキュア シェル (SSH) クライアントで、セキュアなキー管理とリモート マシンへのアクセスを
               可能にします。
DownloadSize : 0
InstallSize  : 0



PS C:\Users\OSAKANATARO&gt;
</pre></div>


<p class="wp-block-paragraph">「NotPresent」とインストールされていないので「Add-WindowsCapability -Online -Name OpenSSH.Client」でインストールする</p>


<div class="wp-block-syntaxhighlighter-code "><pre class="brush: powershell; title: ; notranslate">
PS C:\Users\OSAKANATARO&gt; Add-WindowsCapability -Online -Name OpenSSH.Client


Path          :
Online        : True
RestartNeeded : False



PS C:\Users\OSAKANATARO&gt; Get-WindowsCapability -Online -Name OpenSSH.Client*


Name         : OpenSSH.Client~~~~0.0.1.0
State        : Installed
DisplayName  : OpenSSH クライアント
Description  : OpenSSH ベースのセキュア シェル (SSH) クライアントで、セキュアなキー管理とリモート マシンへのアクセスを
               可能にします。
DownloadSize : 0
InstallSize  : 7995927



PS C:\Users\OSAKANATARO&gt;
</pre></div>


<p class="wp-block-paragraph">で・・・再起動しないでClaude Codeの再チャレンジをしてみたところ、今度は成功しました</p>



<p class="wp-block-paragraph">成功した時のsshログは以下</p>


<div class="wp-block-syntaxhighlighter-code "><pre class="brush: powershell; title: ; notranslate">
PS C:\Users\OSAKANATARO&gt; Get-Content &quot;$env:LOCALAPPDATA\Packages\Claude_pzs8sxrjxfjjc\LocalCache\Roaming\Claude\logs\ssh.log&quot; -Tail 30 -Encoding utf8
＜略＞
2026-08-11 23:20:24 &#x5B;info] &#x5B;RemoteServerController] Ensuring server is ready on pcuser@192.168.1.21 (trigger: send_message)
2026-08-11 23:20:24 &#x5B;info] &#x5B;BinaryDeployment] Setting up remote server on pcuser@192.168.1.21
2026-08-11 23:20:24 &#x5B;info] &#x5B;SSH2Connection] Resolved pcuser@192.168.1.21 -&gt; pcuser@192.168.1.21:22 (identityFiles: 7)
2026-08-11 23:20:24 &#x5B;info] &#x5B;SSH2Connection] Connecting to pcuser@192.168.1.21:22 (agent: none, keys: 1&#x5B;ssh-ed25519], proxy: false, keyboard: true)
2026-08-11 23:20:24 &#x5B;info] &#x5B;SSH2Connection] ssh2: Outbound: Sending SERVICE_REQUEST (ssh-userauth)
2026-08-11 23:20:24 &#x5B;info] &#x5B;SSH2Connection] ssh2: Inbound: Received SERVICE_ACCEPT (ssh-userauth)
2026-08-11 23:20:24 &#x5B;info] &#x5B;SSH2Connection] ssh2: Outbound: Sending USERAUTH_REQUEST (none)
2026-08-11 23:20:24 &#x5B;info] &#x5B;SSH2Connection] ssh2: Inbound: Received USERAUTH_FAILURE (publickey,password)
2026-08-11 23:20:24 &#x5B;info] &#x5B;SSH2Connection] ssh2: Client: none auth failed
2026-08-11 23:20:24 &#x5B;info] &#x5B;SSH2Connection] ssh2: Outbound: Sending USERAUTH_REQUEST (publickey -- check)
2026-08-11 23:20:24 &#x5B;info] &#x5B;SSH2Connection] ssh2: Inbound: Received USERAUTH_PK_OK
2026-08-11 23:20:24 &#x5B;info] &#x5B;SSH2Connection] ssh2: Outbound: Sending USERAUTH_REQUEST (publickey)
2026-08-11 23:20:25 &#x5B;info] &#x5B;SSH2Connection] ssh2: Inbound: Received USERAUTH_SUCCESS
2026-08-11 23:20:25 &#x5B;info] &#x5B;SSH2Connection] Connected to pcuser@192.168.1.21:22
2026-08-11 23:20:25 &#x5B;info] &#x5B;BinaryDeployment] Remote: home=/home/pcuser, platform=linux-amd64, shell=posix, localVer=5db5e4a12f88487e47c2c48259b69a2d630bb3f7
2026-08-11 23:20:25 &#x5B;info] &#x5B;BinaryDeployment] Server binary up to date (5db5e4a12f88487e47c2c48259b69a2d630bb3f7), skipping upload
2026-08-11 23:20:25 &#x5B;info] &#x5B;BinaryDeployment] CLI v2.1.222 cached
2026-08-11 23:20:26 &#x5B;info] &#x5B;BinaryDeployment] Remote server started
2026-08-11 23:20:26 &#x5B;info] &#x5B;BinaryDeployment] Bridge channel opened
2026-08-11 23:20:26 &#x5B;info] &#x5B;RemoteServerController] server capabilities: version=5db5e4a12f88487e47c2c48259b69a2d630bb3f7, methods=19, features=&#x5B;process.stdin.offset]
2026-08-11 23:20:26 &#x5B;info] &#x5B;RemoteServerController] Connected to remote server (1557ms, trigger: send_message, reused: false)
PS C:\Users\OSAKANATARO&gt;
</pre></div>


<p class="wp-block-paragraph">ちゃんと「identityFiles: 7」と.ssh\known_hosts に登録されているホストの数が認識されていました</p>



<p class="wp-block-paragraph"></p>
]]></content:encoded>
					
					<wfw:commentRss>https://blog.osakana.net/archives/17577/feed</wfw:commentRss>
			<slash:comments>0</slash:comments>
		
		
			</item>
		<item>
		<title>XTEINK X3をaliexpressで買った</title>
		<link>https://blog.osakana.net/archives/17542</link>
					<comments>https://blog.osakana.net/archives/17542#respond</comments>
		
		<dc:creator><![CDATA[osakanataro]]></dc:creator>
		<pubDate>Wed, 05 Aug 2026 14:40:31 +0000</pubDate>
				<category><![CDATA[CPU]]></category>
		<category><![CDATA[ESP8266 / ESP32]]></category>
		<category><![CDATA[XTEINK]]></category>
		<category><![CDATA[マイナーハード]]></category>
		<guid isPermaLink="false">https://blog.osakana.net/?p=17542</guid>

					<description><![CDATA[小型E-INKデバイスXTEINK X4とX3をaliexpressでよく見かけていたんだけど、crosspoint readerというオープンソースのfirmwareに入れ替えられることを知ったので入手してみた cro &#8230; <p class="link-more"><a href="https://blog.osakana.net/archives/17542" class="more-link"><span class="screen-reader-text">"XTEINK X3をaliexpressで買った" の</span>続きを読む</a></p>]]></description>
										<content:encoded><![CDATA[
<p class="wp-block-paragraph">小型E-INKデバイス<a href="https://www.xteink.com/ja/products/xteink-x4">XTEINK X4</a>と<a href="https://www.xteink.com/ja/products/xteink-x3">X3</a>をaliexpressでよく見かけていたんだけど、<a href="https://crosspointreader.com/">crosspoint reader</a>というオープンソースのfirmwareに入れ替えられることを知ったので入手してみた</p>



<p class="wp-block-paragraph">crosspoint公式github <a href="https://github.com/crosspoint-reader/crosspoint-reader">https://github.com/crosspoint-reader/crosspoint-reader</a></p>



<p class="wp-block-paragraph">XTEINKで買うと1万円以上しているけど、aliexpressでコイン割引で7660円となるものがあったので買ってみた</p>



<a href="https://s.click.aliexpress.com/e/_c3ngFg4J" target="_blank"><img decoding="async" src="//ae01.alicdn.com/kf/S24188061320f41ee842eed99c2229e3b4.jpg_350x350.jpg" /></a>



<p class="wp-block-paragraph">2026/07/21発注で2026/08/06到着と、珍しく時間がかかって届いた。おそらく台湾発送の「AliExpress Standard for Special Goods」での取り扱いだったことが原因なんだろうなぁ、と思われる。</p>



<p class="wp-block-paragraph">届いた中身は箱2つだった。</p>



<figure class="wp-block-image size-full"><a href="https://blog.osakana.net/wp-content/uploads/2026/08/image-9.png"><img loading="lazy" decoding="async" width="589" height="414" src="https://blog.osakana.net/wp-content/uploads/2026/08/image-9.png" alt="" class="wp-image-17558" srcset="https://blog.osakana.net/wp-content/uploads/2026/08/image-9.png 589w, https://blog.osakana.net/wp-content/uploads/2026/08/image-9-300x211.png 300w" sizes="auto, (max-width: 589px) 100vw, 589px" /></a></figure>



<p class="wp-block-paragraph">小さな箱は、画面保護シート、microSDリーダ/ライターと、magsafeっぽく使えるようにするための磁石リング2個</p>



<figure class="wp-block-image size-full"><a href="https://blog.osakana.net/wp-content/uploads/2026/08/image-10.png"><img loading="lazy" decoding="async" width="843" height="577" src="https://blog.osakana.net/wp-content/uploads/2026/08/image-10.png" alt="" class="wp-image-17559" srcset="https://blog.osakana.net/wp-content/uploads/2026/08/image-10.png 843w, https://blog.osakana.net/wp-content/uploads/2026/08/image-10-300x205.png 300w, https://blog.osakana.net/wp-content/uploads/2026/08/image-10-768x526.png 768w" sizes="auto, (max-width: 767px) 89vw, (max-width: 1000px) 54vw, (max-width: 1071px) 543px, 580px" /></a></figure>



<p class="wp-block-paragraph">本体箱の中身はこんな感じ</p>



<figure class="wp-block-image size-full"><a href="https://blog.osakana.net/wp-content/uploads/2026/08/image-11.png"><img loading="lazy" decoding="async" width="897" height="333" src="https://blog.osakana.net/wp-content/uploads/2026/08/image-11.png" alt="" class="wp-image-17560" srcset="https://blog.osakana.net/wp-content/uploads/2026/08/image-11.png 897w, https://blog.osakana.net/wp-content/uploads/2026/08/image-11-300x111.png 300w, https://blog.osakana.net/wp-content/uploads/2026/08/image-11-768x285.png 768w" sizes="auto, (max-width: 767px) 89vw, (max-width: 1000px) 54vw, (max-width: 1071px) 543px, 580px" /></a></figure>



<p class="wp-block-paragraph">本体、充電用USBケーブル、マニュアルが入っていました</p>



<figure class="wp-block-image size-full"><a href="https://blog.osakana.net/wp-content/uploads/2026/08/image-12.png"><img loading="lazy" decoding="async" width="856" height="484" src="https://blog.osakana.net/wp-content/uploads/2026/08/image-12.png" alt="" class="wp-image-17561" srcset="https://blog.osakana.net/wp-content/uploads/2026/08/image-12.png 856w, https://blog.osakana.net/wp-content/uploads/2026/08/image-12-300x170.png 300w, https://blog.osakana.net/wp-content/uploads/2026/08/image-12-768x434.png 768w" sizes="auto, (max-width: 767px) 89vw, (max-width: 1000px) 54vw, (max-width: 1071px) 543px, 580px" /></a></figure>



<h2 class="wp-block-heading">初期firmware</h2>



<p class="wp-block-paragraph">初期画面はこんな感じで、上面右側のボタンを長押しして電源を入れます。</p>



<figure class="wp-block-image size-full"><a href="https://blog.osakana.net/wp-content/uploads/2026/08/image-13.png"><img loading="lazy" decoding="async" width="901" height="675" src="https://blog.osakana.net/wp-content/uploads/2026/08/image-13.png" alt="" class="wp-image-17562" srcset="https://blog.osakana.net/wp-content/uploads/2026/08/image-13.png 901w, https://blog.osakana.net/wp-content/uploads/2026/08/image-13-300x225.png 300w, https://blog.osakana.net/wp-content/uploads/2026/08/image-13-768x575.png 768w" sizes="auto, (max-width: 767px) 89vw, (max-width: 1000px) 54vw, (max-width: 1071px) 543px, 580px" /></a></figure>



<p class="wp-block-paragraph">初回起動時はこんな画面でした。</p>



<figure class="wp-block-image size-full"><a href="https://blog.osakana.net/wp-content/uploads/2026/08/image-14.png"><img loading="lazy" decoding="async" width="507" height="675" src="https://blog.osakana.net/wp-content/uploads/2026/08/image-14.png" alt="" class="wp-image-17563" srcset="https://blog.osakana.net/wp-content/uploads/2026/08/image-14.png 507w, https://blog.osakana.net/wp-content/uploads/2026/08/image-14-225x300.png 225w" sizes="auto, (max-width: 507px) 100vw, 507px" /></a></figure>



<p class="wp-block-paragraph">設定(没置)を選択すると、「语言」で言語が選択できる</p>



<figure class="wp-block-image size-full"><a href="https://blog.osakana.net/wp-content/uploads/2026/08/image-15.png"><img loading="lazy" decoding="async" width="507" height="675" src="https://blog.osakana.net/wp-content/uploads/2026/08/image-15.png" alt="" class="wp-image-17566" srcset="https://blog.osakana.net/wp-content/uploads/2026/08/image-15.png 507w, https://blog.osakana.net/wp-content/uploads/2026/08/image-15-225x300.png 225w" sizes="auto, (max-width: 507px) 100vw, 507px" /></a></figure>



<p class="wp-block-paragraph">意外なことに「日本語」があった。選択すると下記の様に日本語になる。</p>



<figure class="wp-block-image size-full"><a href="https://blog.osakana.net/wp-content/uploads/2026/08/image-16.png"><img loading="lazy" decoding="async" width="507" height="675" src="https://blog.osakana.net/wp-content/uploads/2026/08/image-16.png" alt="" class="wp-image-17567" srcset="https://blog.osakana.net/wp-content/uploads/2026/08/image-16.png 507w, https://blog.osakana.net/wp-content/uploads/2026/08/image-16-225x300.png 225w" sizes="auto, (max-width: 507px) 100vw, 507px" /></a></figure>



<p class="wp-block-paragraph">到着時のfirmwareはXTOS V5.2.13</p>



<figure class="wp-block-image size-full"><a href="https://blog.osakana.net/wp-content/uploads/2026/08/image-17.png"><img loading="lazy" decoding="async" width="507" height="675" src="https://blog.osakana.net/wp-content/uploads/2026/08/image-17.png" alt="" class="wp-image-17568" srcset="https://blog.osakana.net/wp-content/uploads/2026/08/image-17.png 507w, https://blog.osakana.net/wp-content/uploads/2026/08/image-17-225x300.png 225w" sizes="auto, (max-width: 507px) 100vw, 507px" /></a></figure>



<p class="wp-block-paragraph">WiFiに接続して、最新のfirmware XTOS 6..4にバージョンアップ</p>



<figure class="wp-block-image size-full"><a href="https://blog.osakana.net/wp-content/uploads/2026/08/image-18.png"><img loading="lazy" decoding="async" width="507" height="675" src="https://blog.osakana.net/wp-content/uploads/2026/08/image-18.png" alt="" class="wp-image-17569" srcset="https://blog.osakana.net/wp-content/uploads/2026/08/image-18.png 507w, https://blog.osakana.net/wp-content/uploads/2026/08/image-18-225x300.png 225w" sizes="auto, (max-width: 507px) 100vw, 507px" /></a></figure>



<figure class="wp-block-image size-full"><a href="https://blog.osakana.net/wp-content/uploads/2026/08/image-19.png"><img loading="lazy" decoding="async" width="507" height="675" src="https://blog.osakana.net/wp-content/uploads/2026/08/image-19.png" alt="" class="wp-image-17570" srcset="https://blog.osakana.net/wp-content/uploads/2026/08/image-19.png 507w, https://blog.osakana.net/wp-content/uploads/2026/08/image-19-225x300.png 225w" sizes="auto, (max-width: 507px) 100vw, 507px" /></a></figure>



<p class="wp-block-paragraph">microSDにテスト用epubファイルをコピーして開いてみる</p>



<figure class="wp-block-image size-full"><a href="https://blog.osakana.net/wp-content/uploads/2026/08/image.png"><img loading="lazy" decoding="async" width="645" height="860" src="https://blog.osakana.net/wp-content/uploads/2026/08/image.png" alt="" class="wp-image-17544" srcset="https://blog.osakana.net/wp-content/uploads/2026/08/image.png 645w, https://blog.osakana.net/wp-content/uploads/2026/08/image-225x300.png 225w" sizes="auto, (max-width: 645px) 100vw, 645px" /></a></figure>



<p class="wp-block-paragraph">中華フォントですね</p>



<h2 class="wp-block-heading">Firmware入れ替え</h2>



<p class="wp-block-paragraph">付属のUSBケーブルを使ってWindows機につなげても認識してくれない状態でした</p>



<p class="wp-block-paragraph">crosspoint readerの日本語対応版を開発している <a href="https://github.com/zrn-ns/crosspoint-jp">https://github.com/zrn-ns/crosspoint-jp</a> を見ると理由が書いてあった</p>



<p class="wp-block-paragraph">aliexpress版はUSB機能が殺されているlock版で、USB機能は使えないが、microSD経由でfirmwareを変更することはできる、と</p>



<p class="wp-block-paragraph">crosspoint reader公式に<a href="https://crosspointreader.com/unlock">unlock firmware</a>が提供されているので「update.bin」をmicroSDカードに保存してXTEINK X3に戻す</p>



<p class="wp-block-paragraph">XTEINK X3にUSBケーブルをつなげて充電状態にする</p>



<p class="wp-block-paragraph">XTEINK X3が起動してても/起動していなくても、電源ボタン(上面の右側ボタン)と上ボタン（左面のボタン）を押し続ける</p>



<figure class="wp-block-image size-full"><a href="https://blog.osakana.net/wp-content/uploads/2026/08/image-1.png"><img loading="lazy" decoding="async" width="556" height="824" src="https://blog.osakana.net/wp-content/uploads/2026/08/image-1.png" alt="" class="wp-image-17545" srcset="https://blog.osakana.net/wp-content/uploads/2026/08/image-1.png 556w, https://blog.osakana.net/wp-content/uploads/2026/08/image-1-202x300.png 202w" sizes="auto, (max-width: 556px) 100vw, 556px" /></a></figure>



<p class="wp-block-paragraph">画面が「更新中」となったら手を離して終了まで待つ</p>



<figure class="wp-block-image size-full"><a href="https://blog.osakana.net/wp-content/uploads/2026/08/image-2.png"><img loading="lazy" decoding="async" width="555" height="654" src="https://blog.osakana.net/wp-content/uploads/2026/08/image-2.png" alt="" class="wp-image-17546" srcset="https://blog.osakana.net/wp-content/uploads/2026/08/image-2.png 555w, https://blog.osakana.net/wp-content/uploads/2026/08/image-2-255x300.png 255w" sizes="auto, (max-width: 555px) 100vw, 555px" /></a></figure>



<p class="wp-block-paragraph">下記の様に英語表示になったら書き換え終了です</p>



<figure class="wp-block-image size-full"><a href="https://blog.osakana.net/wp-content/uploads/2026/08/image-3.png"><img loading="lazy" decoding="async" width="569" height="629" src="https://blog.osakana.net/wp-content/uploads/2026/08/image-3.png" alt="" class="wp-image-17547" srcset="https://blog.osakana.net/wp-content/uploads/2026/08/image-3.png 569w, https://blog.osakana.net/wp-content/uploads/2026/08/image-3-271x300.png 271w" sizes="auto, (max-width: 569px) 100vw, 569px" /></a></figure>



<p class="wp-block-paragraph">XTOSで使用したテスト用epubファイルを読み込んでみる・・・System Crash</p>



<figure class="wp-block-image size-full"><a href="https://blog.osakana.net/wp-content/uploads/2026/08/image-4.png"><img loading="lazy" decoding="async" width="525" height="670" src="https://blog.osakana.net/wp-content/uploads/2026/08/image-4.png" alt="" class="wp-image-17548" srcset="https://blog.osakana.net/wp-content/uploads/2026/08/image-4.png 525w, https://blog.osakana.net/wp-content/uploads/2026/08/image-4-235x300.png 235w" sizes="auto, (max-width: 525px) 100vw, 525px" /></a></figure>



<p class="wp-block-paragraph">XTOSでいけたのに、ダメなのか、と意外な結果に驚きが・・・</p>



<p class="wp-block-paragraph">続いて日本語対応版 <a href="https://github.com/zrn-ns/crosspoint-jp">https://github.com/zrn-ns/crosspoint-jp</a> をインストールしてみます</p>



<p class="wp-block-paragraph">microsdにfirmware.binをコピーして</p>



<p class="wp-block-paragraph">XTEINK X3の「Settings」→「System」→「SD Card Firmware Update」で「firmware.bin」を選択して更新</p>



<p class="wp-block-paragraph">アップデート中&#8230;</p>



<figure class="wp-block-image size-full"><a href="https://blog.osakana.net/wp-content/uploads/2026/08/image-5.png"><img loading="lazy" decoding="async" width="588" height="669" src="https://blog.osakana.net/wp-content/uploads/2026/08/image-5.png" alt="" class="wp-image-17549" srcset="https://blog.osakana.net/wp-content/uploads/2026/08/image-5.png 588w, https://blog.osakana.net/wp-content/uploads/2026/08/image-5-264x300.png 264w" sizes="auto, (max-width: 588px) 100vw, 588px" /></a></figure>



<p class="wp-block-paragraph">おや？ばけばけ</p>



<figure class="wp-block-image size-full"><a href="https://blog.osakana.net/wp-content/uploads/2026/08/image-6.png"><img loading="lazy" decoding="async" width="607" height="730" src="https://blog.osakana.net/wp-content/uploads/2026/08/image-6.png" alt="" class="wp-image-17550" srcset="https://blog.osakana.net/wp-content/uploads/2026/08/image-6.png 607w, https://blog.osakana.net/wp-content/uploads/2026/08/image-6-249x300.png 249w" sizes="auto, (max-width: 607px) 100vw, 607px" /></a></figure>



<p class="wp-block-paragraph">フォントをインストールしてから表示するとエラーで落ちる・・・</p>



<figure class="wp-block-image size-full"><a href="https://blog.osakana.net/wp-content/uploads/2026/08/image-7.png"><img loading="lazy" decoding="async" width="645" height="860" src="https://blog.osakana.net/wp-content/uploads/2026/08/image-7.png" alt="" class="wp-image-17551" srcset="https://blog.osakana.net/wp-content/uploads/2026/08/image-7.png 645w, https://blog.osakana.net/wp-content/uploads/2026/08/image-7-225x300.png 225w" sizes="auto, (max-width: 645px) 100vw, 645px" /></a></figure>



<figure class="wp-block-image size-full"><a href="https://blog.osakana.net/wp-content/uploads/2026/08/image-8.png"><img loading="lazy" decoding="async" width="645" height="860" src="https://blog.osakana.net/wp-content/uploads/2026/08/image-8.png" alt="" class="wp-image-17552" srcset="https://blog.osakana.net/wp-content/uploads/2026/08/image-8.png 645w, https://blog.osakana.net/wp-content/uploads/2026/08/image-8-225x300.png 225w" sizes="auto, (max-width: 645px) 100vw, 645px" /></a></figure>



<p class="wp-block-paragraph">うーん・・・</p>



<p class="wp-block-paragraph"><a href="https://github.com/zrn-ns/crosspoint-jp/issues">crosspoint jpのissue</a> に<a href="https://github.com/zrn-ns/crosspoint-jp/issues/105">事象を登録</a>してから、詳細を見ていくと、<a href="https://github.com/zrn-ns/crosspoint-jp/issues/103">#103</a> の角川系EPUBファイルで発生している事象の問題がまさしくそのものっぽい。</p>



<p class="wp-block-paragraph">「書籍の埋め込みスタイル」を「OFF」にすることで表示できる、ということも発見した。</p>



<p class="wp-block-paragraph">2026/09/08 追記: メモリエラーの件は、その後のバージョンで解決している</p>



<p class="wp-block-paragraph"></p>
]]></content:encoded>
					
					<wfw:commentRss>https://blog.osakana.net/archives/17542/feed</wfw:commentRss>
			<slash:comments>0</slash:comments>
		
		
			</item>
		<item>
		<title>Linux上でのSecure boot関連操作のメモ</title>
		<link>https://blog.osakana.net/archives/17538</link>
					<comments>https://blog.osakana.net/archives/17538#respond</comments>
		
		<dc:creator><![CDATA[osakanataro]]></dc:creator>
		<pubDate>Wed, 05 Aug 2026 09:15:51 +0000</pubDate>
				<category><![CDATA[Linux]]></category>
		<category><![CDATA[Oracle Linux / CentOS / RHEL]]></category>
		<category><![CDATA[OS]]></category>
		<category><![CDATA[Ubuntu / Debian]]></category>
		<guid isPermaLink="false">https://blog.osakana.net/?p=17538</guid>

					<description><![CDATA[Secure Bootに使われるUEFI内に保存されている証明書に関して、Secure Boot開始初期にMicrosoftが作成した証明書の有効期限が切れてしまう、という時期になった。 LinuxでもSecure Bo &#8230; <p class="link-more"><a href="https://blog.osakana.net/archives/17538" class="more-link"><span class="screen-reader-text">"Linux上でのSecure boot関連操作のメモ" の</span>続きを読む</a></p>]]></description>
										<content:encoded><![CDATA[
<p class="wp-block-paragraph">Secure Bootに使われるUEFI内に保存されている証明書に関して、Secure Boot開始初期にMicrosoftが作成した証明書の有効期限が切れてしまう、という時期になった。</p>



<p class="wp-block-paragraph">LinuxでもSecure Bootを有効にしていると関係する話である。</p>



<p class="wp-block-paragraph">AlmaLinux「<a href="https://almalinux.org/blog/2026-07-14-secure-boot-2023-certificates/">Microsoft 2011 Secure Boot certificates have expired — AlmaLinux users are covered!</a>」<br>Debian「<a href="https://wiki.debian.org/SecureBoot/CAChanges">SecureBootCAChanges</a>」<br>DELL 「<a href="https://www.dell.com/support/kbdoc/ja-jp/000385747/">セキュア ブート証明書を確認する方法</a>」<br>VMware「<a href="https://blogs.vmware.com/vmware-japan/2026/04/secureboot.html">[TAM Blog] セキュアブート証明書の有効期限切れに関する注意点と対応について</a>」<br>Dynabook「<a href="https://dynabook.com/assistpc/info/2026/20260217_secureboot.htm">Windows セキュアブート証明書の有効期限切れについて</a>」</p>



<h2 class="wp-block-heading">Secure Bootの状態確認</h2>



<p class="wp-block-paragraph">Secure Bootが有効な状態となっているかを「mokutil &#8211;sb-state」を実行して「enabled」となっているか、で確認します。</p>


<div class="wp-block-syntaxhighlighter-code "><pre class="brush: bash; title: ; notranslate">
pcuser@ubuntu:~$ sudo mokutil --sb-state
SecureBoot enabled
pcuser@ubuntu:~$
</pre></div>


<p class="wp-block-paragraph">Secure Bootを使えない環境の例</p>


<div class="wp-block-syntaxhighlighter-code "><pre class="brush: bash; title: ; notranslate">
&#x5B;pcuser@almalinux9 ~]$ sudo mokutil --sb-state
SecureBoot disabled
Platform is in Setup Mode
&#x5B;pcuser@almalinux9 ~]$
</pre></div>


<h2 class="wp-block-heading">Secure Boot証明書 データベースの登録確認</h2>



<p class="wp-block-paragraph">Secure Bootの証明書データベースに登録されているものは「mokutil &#8211;db」で確認します。</p>


<div class="wp-block-syntaxhighlighter-code "><pre class="brush: bash; title: ; notranslate">
pcuser@ubuntu:~$ sudo mokutil --db
&#x5B;key 1]
SHA1 Fingerprint: 13:7e:57:1f:0b:81:8a:0f:5c:32:3d:a2:7f:4a:ec:cf:95:98:0c:96
Certificate:
    Data:
        Version: 3 (0x2)
        Serial Number:
            e9:d9:ff:69:e6:f3:e7:e4
        Signature Algorithm: sha256WithRSAEncryption
        Issuer: C=US, ST=California, L=Palo Alto, O=VMware, Inc.
        Validity
            Not Before: Oct 16 17:16:05 2008 GMT
            Not After : Dec 31 17:16:05 2019 GMT
        Subject: C=US, ST=California, L=Palo Alto, O=VMware, Inc.
        Subject Public Key Info:
            Public Key Algorithm: rsaEncryption
                Public-Key: (2048 bit)
                Modulus:
                    00:c5:65:a7:45:cf:67:7f:f3:15:2e:79:0e:7f:53:
                    bb:cc:76:27:96:b7:6a:fa:08:93:b2:ac:84:74:59:
                    dc:3f:17:57:6d:e5:05:4d:fe:e5:b9:bc:1d:0f:ab:
                    80:81:0b:a4:bf:fc:64:c8:fe:54:46:4b:5d:93:ff:
                    ef:30:88:bf:3c:6c:25:0a:ef:12:6f:46:b6:dc:2e:
                    e6:a3:da:71:f0:80:e5:a3:21:22:fa:48:35:8b:5f:
                    66:29:cf:b9:1b:73:a2:8a:fe:29:52:cd:a5:e1:d4:
                    d7:f6:f0:b6:17:84:19:43:8f:8c:96:3a:f4:4d:67:
                    4b:48:b4:31:13:9c:c6:4c:8f:e4:83:44:a2:50:0a:
                    a4:75:b3:9f:c9:b0:b9:0c:9f:eb:bc:c7:c7:8b:34:
                    2d:9a:25:e9:81:98:a2:3c:da:2a:a5:8f:d1:7f:f6:
                    e5:11:14:3f:06:89:14:1f:04:8a:1c:ed:05:7f:3d:
                    b9:e7:dd:11:84:05:b0:3b:90:b8:9f:d4:18:05:0c:
                    5e:54:51:b4:de:4e:a5:ad:04:f4:3b:8b:0b:85:46:
                    88:5d:a1:94:12:86:d4:f1:53:1c:ab:c9:e4:df:a2:
                    6d:af:e0:9c:95:3c:75:c6:21:18:79:f6:2c:b0:f6:
                    ba:dc:a8:b3:5d:b8:b4:7a:40:7f:e6:c4:02:b0:5a:
                    13:7f
                Exponent: 3 (0x3)
        X509v3 extensions:
            X509v3 Subject Key Identifier:
                4A:D8:BA:04:72:07:3D:28:12:77:06:DD:C6:CC:B9:05:04:41:BB:C7
            X509v3 Authority Key Identifier:
                keyid:4A:D8:BA:04:72:07:3D:28:12:77:06:DD:C6:CC:B9:05:04:41:BB:C7
                DirName:/C=US/ST=California/L=Palo Alto/O=VMware, Inc.
                serial:E9:D9:FF:69:E6:F3:E7:E4
            X509v3 Basic Constraints:
                CA:TRUE
    Signature Algorithm: sha256WithRSAEncryption
    Signature Value:
        70:ef:b4:2e:c4:c4:ae:66:d8:18:20:27:1c:0c:8d:0d:4f:9e:
        93:b3:e7:f4:e5:95:6f:6c:09:45:79:16:27:20:c3:9d:94:3f:
        b0:db:c0:e7:b7:45:92:a7:4b:49:a7:43:8b:94:0b:59:c7:de:
        18:65:31:84:75:53:c0:35:bc:16:0b:2b:93:9b:d5:fb:52:52:
        a0:59:08:3c:37:a4:f5:01:51:f8:3f:bd:62:7b:35:25:ec:c6:
        bb:b5:21:9d:a2:17:5d:80:8a:0d:fc:1b:4c:87:53:83:63:b4:
        0b:d5:49:93:0d:69:f6:72:33:ec:da:ee:c8:39:8d:ac:8f:6a:
        be:80:33:b8:e1:68:e3:44:0a:66:03:75:45:ca:ca:2a:e0:10:
        ee:52:06:45:32:ca:1b:67:b7:d0:24:bc:9b:be:a2:91:59:0c:
        0a:7e:34:2a:26:4f:a5:80:15:b9:d3:47:23:cd:0b:c3:4b:c9:
        94:f8:43:d1:6f:87:48:39:ba:de:ef:16:82:13:cb:4d:0a:3f:
        05:c1:a1:be:64:7f:b2:54:d4:73:96:7d:85:a6:7a:c5:ee:d3:
        51:4c:4e:3c:77:bc:df:40:1b:49:62:60:70:f8:08:0b:dd:32:
        28:eb:d1:5b:57:08:2e:00:a8:c0:5b:21:35:71:28:36:43:3a:
        97:e9:6c:a3

&#x5B;key 2]
SHA1 Fingerprint: 73:8a:96:2b:d9:c8:1b:72:77:17:af:17:ee:09:3f:e9:b4:ba:ee:c0
Certificate:
    Data:
        Version: 3 (0x2)
        Serial Number:
            e3:4c:a7:5a:0a:61:58:53
        Signature Algorithm: sha256WithRSAEncryption
        Issuer: C=US, ST=California, L=Palo Alto, O=VMware, Inc., CN=VMware Secure Boot Signing
        Validity
            Not Before: Oct 24 06:47:59 2017 GMT
            Not After : Oct 19 06:47:59 2037 GMT
        Subject: C=US, ST=California, L=Palo Alto, O=VMware, Inc., CN=VMware Secure Boot Signing
        Subject Public Key Info:
            Public Key Algorithm: rsaEncryption
＜略＞
</pre></div>


<p class="wp-block-paragraph">ちょっと量が多くてわかりにくいです。</p>



<p class="wp-block-paragraph">重要なのは名称と有効期限です。</p>



<p class="wp-block-paragraph">「mokutil &#8211;db|grep -e &#8216;Subject:&#8217; -e &#8216;Not After&#8217;」で確認出来ます。</p>


<div class="wp-block-syntaxhighlighter-code "><pre class="brush: bash; title: ; notranslate">
pcuser@ubuntu:~$ sudo mokutil --db|grep -e &#039;Subject:&#039; -e &#039;Not After&#039;
            Not After : Dec 31 17:16:05 2019 GMT
        Subject: C=US, ST=California, L=Palo Alto, O=VMware, Inc.
            Not After : Oct 19 06:47:59 2037 GMT
        Subject: C=US, ST=California, L=Palo Alto, O=VMware, Inc., CN=VMware Secure Boot Signing
            Not After : Jun 27 21:32:45 2026 GMT
        Subject: C=US, ST=Washington, L=Redmond, O=Microsoft Corporation, CN=Microsoft Corporation UEFI CA 2011
            Not After : Oct 19 18:51:42 2026 GMT
        Subject: C=US, ST=Washington, L=Redmond, O=Microsoft Corporation, CN=Microsoft Windows Production PCA 2011
            Not After : Jun 13 19:08:29 2035 GMT
        Subject: C=US, O=Microsoft Corporation, CN=Windows UEFI CA 2023
            Not After : Jun 13 19:31:47 2038 GMT
        Subject: C=US, O=Microsoft Corporation, CN=Microsoft UEFI CA 2023
pcuser@ubuntu:~$
</pre></div>


<p class="wp-block-paragraph">ESXi 8上の仮想マシンなので、VMwareの証明書が2個入っていて、1つは有効期限が切れていました。</p>



<p class="wp-block-paragraph">Microsoftの証明書が2011年発行のが2つ、2023年発行のが2つあり、2011年の1つは有効期限切れでもう1つももうすぐですね。</p>



<h2 class="wp-block-heading">Secure Boot キー登録鍵の状態確認</h2>



<p class="wp-block-paragraph">KEY(Key Exchange Key)というUEFIに新しくSecure Boot用の証明書を登録する時に必要なものです。</p>



<p class="wp-block-paragraph">「mokutil &#8211;kek」で確認します</p>


<div class="wp-block-syntaxhighlighter-code "><pre class="brush: bash; title: ; notranslate">

pcuser@ubuntu:~$ sudo mokutil --kek
&#x5B;key 1]
SHA1 Fingerprint: 45:9a:b6:fb:5e:28:4d:27:2d:5e:3e:6a:bc:8e:d6:63:82:9d:63:2b
Certificate:
    Data:
        Version: 3 (0x2)
        Serial Number:
            33:00:00:00:13:14:16:b8:61:6d:82:82:4b:00:00:00:00:00:13
        Signature Algorithm: sha256WithRSAEncryption
        Issuer: C=US, O=Microsoft Corporation, CN=Microsoft RSA Devices Root CA 2021
        Validity
            Not Before: Mar  2 20:21:35 2023 GMT
            Not After : Mar  2 20:31:35 2038 GMT
        Subject: C=US, O=Microsoft Corporation, CN=Microsoft Corporation KEK 2K CA 2023
        Subject Public Key Info:
            Public Key Algorithm: rsaEncryption
                Public-Key: (2048 bit)
                Modulus:
                    00:e3:5e:88:8b:73:2c:c3:0a:c4:e9:f5:ce:81:2d:
                    f1:0f:f1:26:35:37:d1:49:53:71:b1:5b:93:52:af:
                    e1:15:df:de:8b:39:bd:af:4c:65:75:53:e5:da:0a:
                    32:98:2f:33:26:b6:2b:be:94:99:9f:ec:da:c2:8e:
                    05:34:92:13:0f:63:bf:74:a2:72:a8:29:7e:9f:32:
                    21:29:08:59:c4:77:c4:2a:92:4c:87:b6:03:37:eb:
                    9a:e2:c3:c9:b4:48:21:c3:61:94:ea:17:51:b1:e7:
                    14:e2:24:63:2e:d5:f2:c6:a5:f2:a2:5e:1f:69:c6:
                    51:0d:a7:29:fb:52:0a:9b:e3:88:e8:68:ff:bb:fa:
                    92:69:af:c4:16:ff:5d:e5:5f:e0:df:ec:66:55:0b:
                    61:c2:ac:3b:20:6e:df:b4:0d:eb:2b:c8:d0:c2:34:
                    4e:82:96:39:ee:f1:31:85:04:3d:ef:d6:76:fb:c3:
                    ca:c1:d5:8c:2f:0b:10:28:9b:48:9a:b0:10:14:a4:
                    d9:94:e5:68:5b:cd:6e:e7:7a:ec:bc:a0:49:b8:a9:
                    53:d8:4d:2f:b2:7b:c8:da:bc:b2:e7:fc:ab:70:10:
                    77:95:45:49:fd:ad:d2:3f:17:cb:66:9a:f2:7d:36:
                    dd:0a:2c:e2:c0:87:21:2d:93:db:08:96:d2:e8:5c:
                    54:e1
                Exponent: 65537 (0x10001)
        X509v3 extensions:
            X509v3 Key Usage: critical
                Digital Signature, Certificate Sign, CRL Sign
            1.3.6.1.4.1.311.21.1:
                ...
            X509v3 Subject Key Identifier:
                E0:AB:72:BC:96:3E:FF:B8:66:9B:7D:10:5A:43:3E:5C:42:54:87:5F
            1.3.6.1.4.1.311.20.2:
                .
.S.u.b.C.A
            X509v3 Basic Constraints: critical
                CA:TRUE
            X509v3 Authority Key Identifier:
                84:44:86:06:00:98:3F:2C:AA:B3:C5:89:F3:AC:2E:C9:E6:9D:09:03
            X509v3 CRL Distribution Points:
                Full Name:
                  URI:http://www.microsoft.com/pkiops/crl/Microsoft%20RSA%20Devices%20Root%20CA%202021.crl
            Authority Information Access:
                CA Issuers - URI:http://www.microsoft.com/pkiops/certs/Microsoft%20RSA%20Devices%20Root%20CA%202021.crt
    Signature Algorithm: sha256WithRSAEncryption
    Signature Value:
        85:02:06:12:fa:67:ae:4f:39:a9:b8:34:dc:5d:2a:78:19:7b:
        38:ee:9c:82:8f:1b:e2:3c:3d:32:0a:5e:bf:58:06:e7:6f:f8:
        8d:18:a8:1b:84:f5:9b:ca:ad:8b:08:44:0e:26:8d:2c:d8:5f:
        6e:23:25:07:fa:5b:4c:26:2e:76:31:43:2e:6e:e8:c8:31:c1:
        4a:d2:f2:02:b7:a6:f1:75:e4:96:ed:06:e2:ca:95:78:44:a8:
        33:76:d4:2b:4d:d7:bc:dc:87:3b:ab:4d:29:ad:96:89:b7:d5:
        c2:8f:ab:46:c3:5d:b3:fd:ed:a5:9e:f5:76:b7:2b:85:ff:98:
        a1:9f:6b:1c:9b:3e:f7:ee:0e:17:a3:fd:36:2f:e1:cd:28:98:
        1c:40:99:26:ca:03:8d:a6:35:ea:d2:0a:a7:8b:16:ae:21:01:
        00:1e:27:0f:b7:0e:b2:42:31:56:2e:e6:f8:8e:ea:0c:34:f0:
        4e:df:70:30:69:04:d1:cf:d3:9c:64:46:6f:cc:21:cd:cb:ef:
        05:32:bb:08:a6:d8:9f:45:38:5d:4e:d2:9c:92:89:e9:73:e4:
        7a:08:35:1e:4f:a6:c2:ba:6b:3e:b7:1f:54:34:49:fa:b4:7a:
        cb:da:a0:1f:59:81:2b:2a:f6:88:26:b0:fa:6c:f2:eb:c1:d8:
        ae:41:e1:6f:fc:bf:13:e8:6e:14:e7:e7:c7:03:8b:40:99:10:
        38:06:6d:70:bd:01:c8:de:8d:56:1d:38:0f:4f:23:a8:25:40:
        de:bb:28:2d:43:af:a4:bc:20:83:b5:06:f9:05:21:9f:3b:b9:
        79:0d:70:6b:53:c0:75:c2:1b:10:13:b3:e4:6f:09:a8:cf:d1:
        b7:0e:71:5c:b7:c9:8f:e5:1c:f0:13:55:d9:93:b9:ae:5d:3f:
        ca:0b:b0:59:6a:45:4a:c3:e1:e3:27:78:0d:16:81:fc:58:2d:
        b1:41:ba:18:0d:cf:f0:ef:ab:08:1e:4f:f8:fc:c6:fd:4b:dd:
        1d:ef:30:25:50:39:a3:df:fe:3f:b9:fa:eb:96:97:d0:cd:f9:
        04:26:fb:0d:48:19:08:d8:e1:93:c1:50:c7:6e:6d:d8:d0:6b:
        8e:95:72:64:50:c9:ed:55:89:6e:c1:4b:a2:06:d4:32:b5:a9:
        6d:65:01:7a:f1:52:57:18:05:30:5c:b8:28:66:11:b7:7a:f0:
        71:4e:86:61:60:7a:6d:56:c7:5b:09:3e:a2:ef:d4:0e:9e:92:
        d3:1f:99:f6:9d:b1:1d:78:78:6b:ff:e8:2a:04:af:78:67:3e:
        f0:2a:0b:a7:e0:5d:01:e9:87:99:35:30:90:ed:d7:45:6b:9c:
        cc:e6:a2:e4:e6:17:a7:dd

&#x5B;key 2]
SHA1 Fingerprint: 31:59:0b:fd:89:c9:d7:4e:d0:87:df:ac:66:33:4b:39:31:25:4b:30
Certificate:
    Data:
        Version: 3 (0x2)
        Serial Number:
            61:0a:d1:88:00:00:00:00:00:03
        Signature Algorithm: sha256WithRSAEncryption
        Issuer: C=US, ST=Washington, L=Redmond, O=Microsoft Corporation, CN=Microsoft Corporation Third Party Marketplace Root
        Validity
            Not Before: Jun 24 20:41:29 2011 GMT
            Not After : Jun 24 20:51:29 2026 GMT
        Subject: C=US, ST=Washington, L=Redmond, O=Microsoft Corporation, CN=Microsoft Corporation KEK CA 2011
        Subject Public Key Info:
＜略＞
</pre></div>


<p class="wp-block-paragraph">これもまた量が多いですが、こちらも重要なのは「Subject:」と「Not After」です</p>


<div class="wp-block-syntaxhighlighter-code "><pre class="brush: bash; title: ; notranslate">
pcuser@ubuntu:~$ sudo mokutil --kek|grep -e &#039;Subject:&#039; -e &#039;Not After&#039;
            Not After : Mar  2 20:31:35 2038 GMT
        Subject: C=US, O=Microsoft Corporation, CN=Microsoft Corporation KEK 2K CA 2023
            Not After : Jun 24 20:51:29 2026 GMT
        Subject: C=US, ST=Washington, L=Redmond, O=Microsoft Corporation, CN=Microsoft Corporation KEK CA 2011
pcuser@ubuntu:~$
</pre></div>


<h2 class="wp-block-heading">Secure Boot証明書 失効データベースの登録確認</h2>



<p class="wp-block-paragraph">今回の事例ではあまり重要ではないですが、明示的にダメな証明書群を登録する失効データベースがあります。</p>



<p class="wp-block-paragraph">こちらは「mokutil &#8211;dbx」で確認します</p>


<div class="wp-block-syntaxhighlighter-code "><pre class="brush: bash; title: ; notranslate">
pcuser@ubuntu:~$ sudo mokutil --dbx
&#x5B;key 1]
  &#x5B;sha256]
  80b4d96931bf0d02fd91a61e19d14f1da452e66db2408ca8604d411f92659f0a
  f52f83a3fa9cfbd6920f722824dbe4034534d25b8507246b3b957dac6e1bce7a
＜略＞
  13a1f37bedfb5417b6b737e2a3816c8fd587d74d836914b2b2edc9fd6ca30e58

&#x5B;key 2]
SHA1 Fingerprint: 8d:a5:a1:98:f2:e8:b2:7d:0d:51:d0:b4:d7:34:21:52:5b:a8:df:5d
Certificate:
    Data:
        Version: 3 (0x2)
        Serial Number: 2806418927 (0xa7468def)
        Signature Algorithm: sha256WithRSAEncryption
        Issuer: CN=Debian Secure Boot CA
        Validity
            Not Before: Aug 16 18:22:50 2016 GMT
            Not After : Aug 16 18:22:50 2026 GMT
        Subject: CN=Debian Secure Boot Signer
        Subject Public Key Info:
            Public Key Algorithm: rsaEncryption
                Public-Key: (2048 bit)
                Modulus:
                    00:d3:d1:83:90:0f:da:65:a2:2f:07:5a:60:95:eb:
                    f7:c7:86:7c:20:86:da:65:a3:a6:12:eb:5b:3b:ce:
                    c8:fb:3f:a1:72:4b:9e:df:50:c5:03:33:a4:0c:2b:
                    5f:d6:41:04:0d:b6:cf:95:48:ed:8a:b2:ad:d6:e5:
                    01:37:4e:60:cd:b2:4a:38:04:b3:44:80:94:af:9f:
                    6e:54:db:a8:1f:3c:b7:4b:30:de:21:81:6f:09:a3:
                    66:ba:6a:2b:96:d6:9a:61:77:0c:d4:ed:3c:d0:71:
                    bb:ad:8c:f0:22:5c:3e:25:cc:6d:22:2e:61:97:95:
                    af:9b:2e:4d:58:b6:7e:78:02:c3:0e:b9:fa:b2:5b:
                    27:de:7d:a2:be:0c:14:ac:73:ec:97:b0:15:5e:ed:
                    ed:e5:a5:75:3f:78:e0:71:ce:2f:ce:83:ed:53:31:
                    30:98:4e:e6:f9:01:a2:88:88:a6:23:08:7c:0d:b7:
                    54:3a:16:95:ed:5e:79:5e:90:4e:fe:cd:aa:de:82:
                    fc:f6:96:71:4e:49:49:b9:d3:e9:b0:ab:7f:d7:2a:
                    47:b7:53:30:27:7c:dc:66:98:09:6f:d1:7e:f5:7f:
                    3d:3e:d4:a2:6a:88:59:02:2f:2f:3d:c8:c6:28:de:
                    42:fe:d9:52:3d:24:c2:fc:40:98:11:f6:76:bf:8c:
                    bb:65
                Exponent: 65537 (0x10001)
        X509v3 extensions:
            Netscape Cert Type:
                Object Signing
            X509v3 Extended Key Usage:
                Microsoft Trust List Signing
            X509v3 Key Usage:
                Digital Signature
    Signature Algorithm: sha256WithRSAEncryption
＜略＞
</pre></div>


<p class="wp-block-paragraph">なんですかね、Debianの証明書が失効で登録されていました</p>



<h2 class="wp-block-heading">Linux OS上でのアップデート？</h2>



<p class="wp-block-paragraph">fwupdtoolコマンドでアップデートができるらしい？</p>



<p class="wp-block-paragraph">「fwupdtool get-updates」でアップデートがあるか確認できるらしい</p>


<div class="wp-block-syntaxhighlighter-code "><pre class="brush: bash; title: ; notranslate">
pcuser@ubuntu:~$ sudo fwupdtool get-updates
ロード中…                &#x5B;************************************** ]
WARNING: UEFI capsule updates not available or enabled in firmware setup
See https://github.com/fwupd/fwupd/wiki/PluginFlag:capsules-unsupported for more information.
Devices with no available firmware updates:
 ~ UEFI dbx
No updates available for remaining devices
pcuser@ubuntu:~$
</pre></div>


<p class="wp-block-paragraph">「fwupdtool refresh」で情報更新</p>


<div class="wp-block-syntaxhighlighter-code "><pre class="brush: bash; title: ; notranslate">
pcuser@ubuntu:~$ sudo fwupdtool refresh
ロード中…                &#x5B;************************************** ]
WARNING: UEFI capsule updates not available or enabled in firmware setup
See https://github.com/fwupd/fwupd/wiki/PluginFlag:capsules-unsupported for more information.
Metadata is up to date; use --force to refresh again.
pcuser@ubuntu:~$
</pre></div>


<p class="wp-block-paragraph">VMware上の仮想マシンだとアップデートがないので、実行できないけど</p>



<p class="wp-block-paragraph">「fwupdtool update」でアップデートできるらしい</p>
]]></content:encoded>
					
					<wfw:commentRss>https://blog.osakana.net/archives/17538/feed</wfw:commentRss>
			<slash:comments>0</slash:comments>
		
		
			</item>
		<item>
		<title>openKylyn 3.0 Alpha 1をインストールしてみた</title>
		<link>https://blog.osakana.net/archives/17459</link>
					<comments>https://blog.osakana.net/archives/17459#respond</comments>
		
		<dc:creator><![CDATA[osakanataro]]></dc:creator>
		<pubDate>Fri, 10 Jul 2026 07:26:33 +0000</pubDate>
				<category><![CDATA[Linux]]></category>
		<category><![CDATA[OS]]></category>
		<category><![CDATA[Ubuntu / Debian]]></category>
		<guid isPermaLink="false">https://blog.osakana.net/?p=17459</guid>

					<description><![CDATA[「中国OS「銀河麒麟」、Linuxデスクトップ上でAndroidアプリのネイティブ動作を実現させる」という記事で、銀河麒麟(Kylin OS)のことが紹介されていた 2023年5月に openKylin 0.9.5 をイ &#8230; <p class="link-more"><a href="https://blog.osakana.net/archives/17459" class="more-link"><span class="screen-reader-text">"openKylyn 3.0 Alpha 1をインストールしてみた" の</span>続きを読む</a></p>]]></description>
										<content:encoded><![CDATA[
<p class="wp-block-paragraph">「<a href="https://japan.zdnet.com/article/35250319/">中国OS「銀河麒麟」、Linuxデスクトップ上でAndroidアプリのネイティブ動作を実現させる</a>」という記事で、銀河麒麟(Kylin OS)のことが紹介されていた</p>



<p class="wp-block-paragraph">2023年5月に openKylin 0.9.5 をインストールしてみたことあったけど、どう変わったのかな？と確認してみることにした</p>



<figure class="wp-block-embed is-type-rich is-provider-x wp-block-embed-x"><div class="wp-block-embed__wrapper">
<blockquote class="twitter-tweet" data-width="525" data-dnt="true"><p lang="ja" dir="ltr">Englishして再起動 <a href="https://t.co/gM0cVVWzWT">pic.twitter.com/gM0cVVWzWT</a></p>&mdash; OSAKANA TARO (@osakanataro2) <a href="https://x.com/osakanataro2/status/1658763258151698434?ref_src=twsrc%5Etfw">May 17, 2023</a></blockquote><script async src="https://platform.x.com/widgets.js" charset="utf-8"></script>
</div></figure>



<p class="wp-block-paragraph">まず、<a href="https://www.openkylin.top/downloads/index-cn.html">openKylinの公式</a>ページから openKylin 3.0 Alpha1 のISOを入手</p>



<figure class="wp-block-image size-large"><a href="https://blog.osakana.net/wp-content/uploads/2026/07/25E1C749-9E02-4182-9A55-250109A2F699.png"><img loading="lazy" decoding="async" width="1024" height="494" src="https://blog.osakana.net/wp-content/uploads/2026/07/25E1C749-9E02-4182-9A55-250109A2F699-1024x494.png" alt="" class="wp-image-17461" srcset="https://blog.osakana.net/wp-content/uploads/2026/07/25E1C749-9E02-4182-9A55-250109A2F699-1024x494.png 1024w, https://blog.osakana.net/wp-content/uploads/2026/07/25E1C749-9E02-4182-9A55-250109A2F699-300x145.png 300w, https://blog.osakana.net/wp-content/uploads/2026/07/25E1C749-9E02-4182-9A55-250109A2F699-768x371.png 768w, https://blog.osakana.net/wp-content/uploads/2026/07/25E1C749-9E02-4182-9A55-250109A2F699.png 1235w" sizes="auto, (max-width: 767px) 89vw, (max-width: 1000px) 54vw, (max-width: 1071px) 543px, 580px" /></a></figure>



<p class="wp-block-paragraph">仮想環境上で起動</p>



<p class="wp-block-paragraph"></p>



<figure class="wp-block-image size-full"><a href="https://blog.osakana.net/wp-content/uploads/2026/07/DB1A2D85-2AD8-4628-9651-43416423419F.png"><img loading="lazy" decoding="async" width="920" height="717" src="https://blog.osakana.net/wp-content/uploads/2026/07/DB1A2D85-2AD8-4628-9651-43416423419F.png" alt="" class="wp-image-17462" srcset="https://blog.osakana.net/wp-content/uploads/2026/07/DB1A2D85-2AD8-4628-9651-43416423419F.png 920w, https://blog.osakana.net/wp-content/uploads/2026/07/DB1A2D85-2AD8-4628-9651-43416423419F-300x234.png 300w, https://blog.osakana.net/wp-content/uploads/2026/07/DB1A2D85-2AD8-4628-9651-43416423419F-768x599.png 768w" sizes="auto, (max-width: 767px) 89vw, (max-width: 1000px) 54vw, (max-width: 1071px) 543px, 580px" /></a></figure>



<figure class="wp-block-image size-large"><a href="https://blog.osakana.net/wp-content/uploads/2026/07/B8BBA391-7353-43B6-9E6A-6101ED3651E3.png"><img loading="lazy" decoding="async" width="1024" height="600" src="https://blog.osakana.net/wp-content/uploads/2026/07/B8BBA391-7353-43B6-9E6A-6101ED3651E3-1024x600.png" alt="" class="wp-image-17463" srcset="https://blog.osakana.net/wp-content/uploads/2026/07/B8BBA391-7353-43B6-9E6A-6101ED3651E3-1024x600.png 1024w, https://blog.osakana.net/wp-content/uploads/2026/07/B8BBA391-7353-43B6-9E6A-6101ED3651E3-300x176.png 300w, https://blog.osakana.net/wp-content/uploads/2026/07/B8BBA391-7353-43B6-9E6A-6101ED3651E3-768x450.png 768w, https://blog.osakana.net/wp-content/uploads/2026/07/B8BBA391-7353-43B6-9E6A-6101ED3651E3-1536x900.png 1536w, https://blog.osakana.net/wp-content/uploads/2026/07/B8BBA391-7353-43B6-9E6A-6101ED3651E3.png 1577w" sizes="auto, (max-width: 767px) 89vw, (max-width: 1000px) 54vw, (max-width: 1071px) 543px, 580px" /></a></figure>



<p class="wp-block-paragraph">openKylin 3.0 (huanghe)  huanghe は 黄河の意味<br>Linux kernelは 7.0.0-1-generic</p>



<figure class="wp-block-image size-large"><a href="https://blog.osakana.net/wp-content/uploads/2026/07/74F51743-BAC7-43E4-A39E-2FA671615AFE.png"><img loading="lazy" decoding="async" width="1024" height="611" src="https://blog.osakana.net/wp-content/uploads/2026/07/74F51743-BAC7-43E4-A39E-2FA671615AFE-1024x611.png" alt="" class="wp-image-17464" srcset="https://blog.osakana.net/wp-content/uploads/2026/07/74F51743-BAC7-43E4-A39E-2FA671615AFE-1024x611.png 1024w, https://blog.osakana.net/wp-content/uploads/2026/07/74F51743-BAC7-43E4-A39E-2FA671615AFE-300x179.png 300w, https://blog.osakana.net/wp-content/uploads/2026/07/74F51743-BAC7-43E4-A39E-2FA671615AFE-768x458.png 768w, https://blog.osakana.net/wp-content/uploads/2026/07/74F51743-BAC7-43E4-A39E-2FA671615AFE.png 1091w" sizes="auto, (max-width: 767px) 89vw, (max-width: 1000px) 54vw, (max-width: 1071px) 543px, 580px" /></a></figure>



<p class="wp-block-paragraph">aptのレポジトリはこんな感じ</p>



<figure class="wp-block-image size-large"><a href="https://blog.osakana.net/wp-content/uploads/2026/07/CF066A20-A343-4FEA-B54F-C767AC1EF9C3.png"><img loading="lazy" decoding="async" width="1024" height="252" src="https://blog.osakana.net/wp-content/uploads/2026/07/CF066A20-A343-4FEA-B54F-C767AC1EF9C3-1024x252.png" alt="" class="wp-image-17465" srcset="https://blog.osakana.net/wp-content/uploads/2026/07/CF066A20-A343-4FEA-B54F-C767AC1EF9C3-1024x252.png 1024w, https://blog.osakana.net/wp-content/uploads/2026/07/CF066A20-A343-4FEA-B54F-C767AC1EF9C3-300x74.png 300w, https://blog.osakana.net/wp-content/uploads/2026/07/CF066A20-A343-4FEA-B54F-C767AC1EF9C3-768x189.png 768w, https://blog.osakana.net/wp-content/uploads/2026/07/CF066A20-A343-4FEA-B54F-C767AC1EF9C3.png 1105w" sizes="auto, (max-width: 767px) 89vw, (max-width: 1000px) 54vw, (max-width: 1071px) 543px, 580px" /></a></figure>



<p class="wp-block-paragraph">独自のものしかない感じですね</p>



<p class="wp-block-paragraph">デスクトップ上の「安装 openKylin」をクリックしてインストールを行う</p>



<p class="wp-block-paragraph">言語選択</p>



<figure class="wp-block-image size-large"><a href="https://blog.osakana.net/wp-content/uploads/2026/07/7C61BD9C-7BAA-47E5-A77B-F03F067CBCFC.png"><img loading="lazy" decoding="async" width="1024" height="601" src="https://blog.osakana.net/wp-content/uploads/2026/07/7C61BD9C-7BAA-47E5-A77B-F03F067CBCFC-1024x601.png" alt="" class="wp-image-17466" srcset="https://blog.osakana.net/wp-content/uploads/2026/07/7C61BD9C-7BAA-47E5-A77B-F03F067CBCFC-1024x601.png 1024w, https://blog.osakana.net/wp-content/uploads/2026/07/7C61BD9C-7BAA-47E5-A77B-F03F067CBCFC-300x176.png 300w, https://blog.osakana.net/wp-content/uploads/2026/07/7C61BD9C-7BAA-47E5-A77B-F03F067CBCFC-768x450.png 768w, https://blog.osakana.net/wp-content/uploads/2026/07/7C61BD9C-7BAA-47E5-A77B-F03F067CBCFC-1536x901.png 1536w, https://blog.osakana.net/wp-content/uploads/2026/07/7C61BD9C-7BAA-47E5-A77B-F03F067CBCFC.png 1601w" sizes="auto, (max-width: 767px) 89vw, (max-width: 1000px) 54vw, (max-width: 1071px) 543px, 580px" /></a></figure>



<figure class="wp-block-image size-large"><a href="https://blog.osakana.net/wp-content/uploads/2026/07/37AAE2D5-92F9-468D-AC63-45412B036D2D.png"><img loading="lazy" decoding="async" width="1024" height="601" src="https://blog.osakana.net/wp-content/uploads/2026/07/37AAE2D5-92F9-468D-AC63-45412B036D2D-1024x601.png" alt="" class="wp-image-17467" srcset="https://blog.osakana.net/wp-content/uploads/2026/07/37AAE2D5-92F9-468D-AC63-45412B036D2D-1024x601.png 1024w, https://blog.osakana.net/wp-content/uploads/2026/07/37AAE2D5-92F9-468D-AC63-45412B036D2D-300x176.png 300w, https://blog.osakana.net/wp-content/uploads/2026/07/37AAE2D5-92F9-468D-AC63-45412B036D2D-768x451.png 768w, https://blog.osakana.net/wp-content/uploads/2026/07/37AAE2D5-92F9-468D-AC63-45412B036D2D-1536x902.png 1536w, https://blog.osakana.net/wp-content/uploads/2026/07/37AAE2D5-92F9-468D-AC63-45412B036D2D.png 1560w" sizes="auto, (max-width: 767px) 89vw, (max-width: 1000px) 54vw, (max-width: 1071px) 543px, 580px" /></a></figure>



<p class="wp-block-paragraph">「日本語」はないので「English」を選択</p>



<figure class="wp-block-image size-large"><a href="https://blog.osakana.net/wp-content/uploads/2026/07/14EF61AC-9534-4CBB-B790-4D65EDC88DE6.png"><img loading="lazy" decoding="async" width="1024" height="605" src="https://blog.osakana.net/wp-content/uploads/2026/07/14EF61AC-9534-4CBB-B790-4D65EDC88DE6-1024x605.png" alt="" class="wp-image-17468" srcset="https://blog.osakana.net/wp-content/uploads/2026/07/14EF61AC-9534-4CBB-B790-4D65EDC88DE6-1024x605.png 1024w, https://blog.osakana.net/wp-content/uploads/2026/07/14EF61AC-9534-4CBB-B790-4D65EDC88DE6-300x177.png 300w, https://blog.osakana.net/wp-content/uploads/2026/07/14EF61AC-9534-4CBB-B790-4D65EDC88DE6-768x454.png 768w, https://blog.osakana.net/wp-content/uploads/2026/07/14EF61AC-9534-4CBB-B790-4D65EDC88DE6-1536x907.png 1536w, https://blog.osakana.net/wp-content/uploads/2026/07/14EF61AC-9534-4CBB-B790-4D65EDC88DE6.png 1600w" sizes="auto, (max-width: 767px) 89vw, (max-width: 1000px) 54vw, (max-width: 1071px) 543px, 580px" /></a></figure>



<figure class="wp-block-image size-large"><a href="https://blog.osakana.net/wp-content/uploads/2026/07/80722950-55D0-40A6-8BBB-2A6FC7BEF156.png"><img loading="lazy" decoding="async" width="1024" height="592" src="https://blog.osakana.net/wp-content/uploads/2026/07/80722950-55D0-40A6-8BBB-2A6FC7BEF156-1024x592.png" alt="" class="wp-image-17469" srcset="https://blog.osakana.net/wp-content/uploads/2026/07/80722950-55D0-40A6-8BBB-2A6FC7BEF156-1024x592.png 1024w, https://blog.osakana.net/wp-content/uploads/2026/07/80722950-55D0-40A6-8BBB-2A6FC7BEF156-300x174.png 300w, https://blog.osakana.net/wp-content/uploads/2026/07/80722950-55D0-40A6-8BBB-2A6FC7BEF156-768x444.png 768w, https://blog.osakana.net/wp-content/uploads/2026/07/80722950-55D0-40A6-8BBB-2A6FC7BEF156-1536x888.png 1536w, https://blog.osakana.net/wp-content/uploads/2026/07/80722950-55D0-40A6-8BBB-2A6FC7BEF156.png 1594w" sizes="auto, (max-width: 767px) 89vw, (max-width: 1000px) 54vw, (max-width: 1071px) 543px, 580px" /></a></figure>



<figure class="wp-block-image size-large"><a href="https://blog.osakana.net/wp-content/uploads/2026/07/CD71C9DE-B03F-4C5D-BE9D-3EFC71BAA6A5.png"><img loading="lazy" decoding="async" width="1024" height="610" src="https://blog.osakana.net/wp-content/uploads/2026/07/CD71C9DE-B03F-4C5D-BE9D-3EFC71BAA6A5-1024x610.png" alt="" class="wp-image-17470" srcset="https://blog.osakana.net/wp-content/uploads/2026/07/CD71C9DE-B03F-4C5D-BE9D-3EFC71BAA6A5-1024x610.png 1024w, https://blog.osakana.net/wp-content/uploads/2026/07/CD71C9DE-B03F-4C5D-BE9D-3EFC71BAA6A5-300x179.png 300w, https://blog.osakana.net/wp-content/uploads/2026/07/CD71C9DE-B03F-4C5D-BE9D-3EFC71BAA6A5-768x457.png 768w, https://blog.osakana.net/wp-content/uploads/2026/07/CD71C9DE-B03F-4C5D-BE9D-3EFC71BAA6A5-1536x914.png 1536w, https://blog.osakana.net/wp-content/uploads/2026/07/CD71C9DE-B03F-4C5D-BE9D-3EFC71BAA6A5.png 1584w" sizes="auto, (max-width: 767px) 89vw, (max-width: 1000px) 54vw, (max-width: 1071px) 543px, 580px" /></a></figure>



<p class="wp-block-paragraph">どうやら同じネットワーク内にあるサーバからコピーしてインストールする、という「Install from ghost」という機能がある模様</p>



<figure class="wp-block-image size-large"><a href="https://blog.osakana.net/wp-content/uploads/2026/07/041C46D8-E81E-47A9-A102-9B423832B055.png"><img loading="lazy" decoding="async" width="1024" height="612" src="https://blog.osakana.net/wp-content/uploads/2026/07/041C46D8-E81E-47A9-A102-9B423832B055-1024x612.png" alt="" class="wp-image-17471" srcset="https://blog.osakana.net/wp-content/uploads/2026/07/041C46D8-E81E-47A9-A102-9B423832B055-1024x612.png 1024w, https://blog.osakana.net/wp-content/uploads/2026/07/041C46D8-E81E-47A9-A102-9B423832B055-300x179.png 300w, https://blog.osakana.net/wp-content/uploads/2026/07/041C46D8-E81E-47A9-A102-9B423832B055-768x459.png 768w, https://blog.osakana.net/wp-content/uploads/2026/07/041C46D8-E81E-47A9-A102-9B423832B055-1536x918.png 1536w, https://blog.osakana.net/wp-content/uploads/2026/07/041C46D8-E81E-47A9-A102-9B423832B055.png 1582w" sizes="auto, (max-width: 767px) 89vw, (max-width: 1000px) 54vw, (max-width: 1071px) 543px, 580px" /></a></figure>



<figure class="wp-block-image size-large"><a href="https://blog.osakana.net/wp-content/uploads/2026/07/2543C47F-5DCE-4F38-81AB-17E2B2468DEB.png"><img loading="lazy" decoding="async" width="1024" height="605" src="https://blog.osakana.net/wp-content/uploads/2026/07/2543C47F-5DCE-4F38-81AB-17E2B2468DEB-1024x605.png" alt="" class="wp-image-17472" srcset="https://blog.osakana.net/wp-content/uploads/2026/07/2543C47F-5DCE-4F38-81AB-17E2B2468DEB-1024x605.png 1024w, https://blog.osakana.net/wp-content/uploads/2026/07/2543C47F-5DCE-4F38-81AB-17E2B2468DEB-300x177.png 300w, https://blog.osakana.net/wp-content/uploads/2026/07/2543C47F-5DCE-4F38-81AB-17E2B2468DEB-768x454.png 768w, https://blog.osakana.net/wp-content/uploads/2026/07/2543C47F-5DCE-4F38-81AB-17E2B2468DEB-1536x908.png 1536w, https://blog.osakana.net/wp-content/uploads/2026/07/2543C47F-5DCE-4F38-81AB-17E2B2468DEB.png 1597w" sizes="auto, (max-width: 767px) 89vw, (max-width: 1000px) 54vw, (max-width: 1071px) 543px, 580px" /></a></figure>



<figure class="wp-block-image size-large"><a href="https://blog.osakana.net/wp-content/uploads/2026/07/63737E26-25D3-4141-AD81-C7E825663B8B.png"><img loading="lazy" decoding="async" width="1024" height="606" src="https://blog.osakana.net/wp-content/uploads/2026/07/63737E26-25D3-4141-AD81-C7E825663B8B-1024x606.png" alt="" class="wp-image-17474" srcset="https://blog.osakana.net/wp-content/uploads/2026/07/63737E26-25D3-4141-AD81-C7E825663B8B-1024x606.png 1024w, https://blog.osakana.net/wp-content/uploads/2026/07/63737E26-25D3-4141-AD81-C7E825663B8B-300x178.png 300w, https://blog.osakana.net/wp-content/uploads/2026/07/63737E26-25D3-4141-AD81-C7E825663B8B-768x455.png 768w, https://blog.osakana.net/wp-content/uploads/2026/07/63737E26-25D3-4141-AD81-C7E825663B8B-1536x909.png 1536w, https://blog.osakana.net/wp-content/uploads/2026/07/63737E26-25D3-4141-AD81-C7E825663B8B.png 1593w" sizes="auto, (max-width: 767px) 89vw, (max-width: 1000px) 54vw, (max-width: 1071px) 543px, 580px" /></a></figure>



<p class="wp-block-paragraph">おそらくopenKylinのアカウント登録が必要なようだけどあとで</p>



<figure class="wp-block-image size-large"><a href="https://blog.osakana.net/wp-content/uploads/2026/07/CFCEA6A3-8FA7-4875-9893-CDF4AB58D31C.png"><img loading="lazy" decoding="async" width="1024" height="611" src="https://blog.osakana.net/wp-content/uploads/2026/07/CFCEA6A3-8FA7-4875-9893-CDF4AB58D31C-1024x611.png" alt="" class="wp-image-17475" srcset="https://blog.osakana.net/wp-content/uploads/2026/07/CFCEA6A3-8FA7-4875-9893-CDF4AB58D31C-1024x611.png 1024w, https://blog.osakana.net/wp-content/uploads/2026/07/CFCEA6A3-8FA7-4875-9893-CDF4AB58D31C-300x179.png 300w, https://blog.osakana.net/wp-content/uploads/2026/07/CFCEA6A3-8FA7-4875-9893-CDF4AB58D31C-768x458.png 768w, https://blog.osakana.net/wp-content/uploads/2026/07/CFCEA6A3-8FA7-4875-9893-CDF4AB58D31C-1536x916.png 1536w, https://blog.osakana.net/wp-content/uploads/2026/07/CFCEA6A3-8FA7-4875-9893-CDF4AB58D31C.png 1588w" sizes="auto, (max-width: 767px) 89vw, (max-width: 1000px) 54vw, (max-width: 1071px) 543px, 580px" /></a></figure>



<p class="wp-block-paragraph">インストール開始</p>



<figure class="wp-block-image size-large"><a href="https://blog.osakana.net/wp-content/uploads/2026/07/68B032FB-F491-4EAB-93AA-B5FCE983C7ED.png"><img loading="lazy" decoding="async" width="1024" height="606" src="https://blog.osakana.net/wp-content/uploads/2026/07/68B032FB-F491-4EAB-93AA-B5FCE983C7ED-1024x606.png" alt="" class="wp-image-17476" srcset="https://blog.osakana.net/wp-content/uploads/2026/07/68B032FB-F491-4EAB-93AA-B5FCE983C7ED-1024x606.png 1024w, https://blog.osakana.net/wp-content/uploads/2026/07/68B032FB-F491-4EAB-93AA-B5FCE983C7ED-300x178.png 300w, https://blog.osakana.net/wp-content/uploads/2026/07/68B032FB-F491-4EAB-93AA-B5FCE983C7ED-768x455.png 768w, https://blog.osakana.net/wp-content/uploads/2026/07/68B032FB-F491-4EAB-93AA-B5FCE983C7ED-1536x909.png 1536w, https://blog.osakana.net/wp-content/uploads/2026/07/68B032FB-F491-4EAB-93AA-B5FCE983C7ED.png 1595w" sizes="auto, (max-width: 767px) 89vw, (max-width: 1000px) 54vw, (max-width: 1071px) 543px, 580px" /></a></figure>



<p class="wp-block-paragraph">インストール完了</p>



<figure class="wp-block-image size-large"><a href="https://blog.osakana.net/wp-content/uploads/2026/07/5776E1A5-2277-4056-8F36-0DF8B52F15E1.png"><img loading="lazy" decoding="async" width="1024" height="599" src="https://blog.osakana.net/wp-content/uploads/2026/07/5776E1A5-2277-4056-8F36-0DF8B52F15E1-1024x599.png" alt="" class="wp-image-17480" srcset="https://blog.osakana.net/wp-content/uploads/2026/07/5776E1A5-2277-4056-8F36-0DF8B52F15E1-1024x599.png 1024w, https://blog.osakana.net/wp-content/uploads/2026/07/5776E1A5-2277-4056-8F36-0DF8B52F15E1-300x175.png 300w, https://blog.osakana.net/wp-content/uploads/2026/07/5776E1A5-2277-4056-8F36-0DF8B52F15E1-768x449.png 768w, https://blog.osakana.net/wp-content/uploads/2026/07/5776E1A5-2277-4056-8F36-0DF8B52F15E1-1536x898.png 1536w, https://blog.osakana.net/wp-content/uploads/2026/07/5776E1A5-2277-4056-8F36-0DF8B52F15E1.png 1620w" sizes="auto, (max-width: 767px) 89vw, (max-width: 1000px) 54vw, (max-width: 1071px) 543px, 580px" /></a></figure>



<p class="wp-block-paragraph">再起動・・・</p>



<figure class="wp-block-image size-large"><a href="https://blog.osakana.net/wp-content/uploads/2026/07/47B975A6-3A94-4280-9A9C-EEF56F36189C.png"><img loading="lazy" decoding="async" width="1024" height="600" src="https://blog.osakana.net/wp-content/uploads/2026/07/47B975A6-3A94-4280-9A9C-EEF56F36189C-1024x600.png" alt="" class="wp-image-17482" srcset="https://blog.osakana.net/wp-content/uploads/2026/07/47B975A6-3A94-4280-9A9C-EEF56F36189C-1024x600.png 1024w, https://blog.osakana.net/wp-content/uploads/2026/07/47B975A6-3A94-4280-9A9C-EEF56F36189C-300x176.png 300w, https://blog.osakana.net/wp-content/uploads/2026/07/47B975A6-3A94-4280-9A9C-EEF56F36189C-768x450.png 768w, https://blog.osakana.net/wp-content/uploads/2026/07/47B975A6-3A94-4280-9A9C-EEF56F36189C-1536x900.png 1536w, https://blog.osakana.net/wp-content/uploads/2026/07/47B975A6-3A94-4280-9A9C-EEF56F36189C.png 1584w" sizes="auto, (max-width: 767px) 89vw, (max-width: 1000px) 54vw, (max-width: 1071px) 543px, 580px" /></a></figure>



<p class="wp-block-paragraph">「Computer」をクリックするとこんな感じ</p>



<figure class="wp-block-image size-large"><a href="https://blog.osakana.net/wp-content/uploads/2026/07/6757E2D0-70A8-4F17-B887-F996270898C3.png"><img loading="lazy" decoding="async" width="1024" height="595" src="https://blog.osakana.net/wp-content/uploads/2026/07/6757E2D0-70A8-4F17-B887-F996270898C3-1024x595.png" alt="" class="wp-image-17483" srcset="https://blog.osakana.net/wp-content/uploads/2026/07/6757E2D0-70A8-4F17-B887-F996270898C3-1024x595.png 1024w, https://blog.osakana.net/wp-content/uploads/2026/07/6757E2D0-70A8-4F17-B887-F996270898C3-300x174.png 300w, https://blog.osakana.net/wp-content/uploads/2026/07/6757E2D0-70A8-4F17-B887-F996270898C3-768x446.png 768w, https://blog.osakana.net/wp-content/uploads/2026/07/6757E2D0-70A8-4F17-B887-F996270898C3-1536x893.png 1536w, https://blog.osakana.net/wp-content/uploads/2026/07/6757E2D0-70A8-4F17-B887-F996270898C3.png 1583w" sizes="auto, (max-width: 767px) 89vw, (max-width: 1000px) 54vw, (max-width: 1071px) 543px, 580px" /></a></figure>



<p class="wp-block-paragraph">スタートメニュー的なものが出てこないのはEnglish非対応なのか？</p>



<p class="wp-block-paragraph">デスクトップの右クリックメニューから「Open Directory in Terminal」を実行</p>



<figure class="wp-block-image size-large"><a href="https://blog.osakana.net/wp-content/uploads/2026/07/F02BFF3B-578A-4C26-840B-F998A9B342F8.png"><img loading="lazy" decoding="async" width="1024" height="598" src="https://blog.osakana.net/wp-content/uploads/2026/07/F02BFF3B-578A-4C26-840B-F998A9B342F8-1024x598.png" alt="" class="wp-image-17484" srcset="https://blog.osakana.net/wp-content/uploads/2026/07/F02BFF3B-578A-4C26-840B-F998A9B342F8-1024x598.png 1024w, https://blog.osakana.net/wp-content/uploads/2026/07/F02BFF3B-578A-4C26-840B-F998A9B342F8-300x175.png 300w, https://blog.osakana.net/wp-content/uploads/2026/07/F02BFF3B-578A-4C26-840B-F998A9B342F8-768x449.png 768w, https://blog.osakana.net/wp-content/uploads/2026/07/F02BFF3B-578A-4C26-840B-F998A9B342F8-1536x897.png 1536w, https://blog.osakana.net/wp-content/uploads/2026/07/F02BFF3B-578A-4C26-840B-F998A9B342F8.png 1582w" sizes="auto, (max-width: 767px) 89vw, (max-width: 1000px) 54vw, (max-width: 1071px) 543px, 580px" /></a></figure>



<p class="wp-block-paragraph">インストールユーザは「oem」で、ホスト名は「oem-PC」だった</p>



<figure class="wp-block-image size-large"><a href="https://blog.osakana.net/wp-content/uploads/2026/07/A3E02FCE-15FA-4F41-BF62-64DDE4A34233.png"><img loading="lazy" decoding="async" width="1024" height="598" src="https://blog.osakana.net/wp-content/uploads/2026/07/A3E02FCE-15FA-4F41-BF62-64DDE4A34233-1024x598.png" alt="" class="wp-image-17485" srcset="https://blog.osakana.net/wp-content/uploads/2026/07/A3E02FCE-15FA-4F41-BF62-64DDE4A34233-1024x598.png 1024w, https://blog.osakana.net/wp-content/uploads/2026/07/A3E02FCE-15FA-4F41-BF62-64DDE4A34233-300x175.png 300w, https://blog.osakana.net/wp-content/uploads/2026/07/A3E02FCE-15FA-4F41-BF62-64DDE4A34233-768x448.png 768w, https://blog.osakana.net/wp-content/uploads/2026/07/A3E02FCE-15FA-4F41-BF62-64DDE4A34233-1536x896.png 1536w, https://blog.osakana.net/wp-content/uploads/2026/07/A3E02FCE-15FA-4F41-BF62-64DDE4A34233.png 1580w" sizes="auto, (max-width: 767px) 89vw, (max-width: 1000px) 54vw, (max-width: 1071px) 543px, 580px" /></a></figure>



<p class="wp-block-paragraph">とりあえず「sudo apt update」を実行してみたら、署名の問題が・・・</p>



<figure class="wp-block-image size-large"><a href="https://blog.osakana.net/wp-content/uploads/2026/07/12FABABC-568D-408A-ADB9-E4AC9AFB53F7.png"><img loading="lazy" decoding="async" width="1024" height="513" src="https://blog.osakana.net/wp-content/uploads/2026/07/12FABABC-568D-408A-ADB9-E4AC9AFB53F7-1024x513.png" alt="" class="wp-image-17486" srcset="https://blog.osakana.net/wp-content/uploads/2026/07/12FABABC-568D-408A-ADB9-E4AC9AFB53F7-1024x513.png 1024w, https://blog.osakana.net/wp-content/uploads/2026/07/12FABABC-568D-408A-ADB9-E4AC9AFB53F7-300x150.png 300w, https://blog.osakana.net/wp-content/uploads/2026/07/12FABABC-568D-408A-ADB9-E4AC9AFB53F7-768x385.png 768w, https://blog.osakana.net/wp-content/uploads/2026/07/12FABABC-568D-408A-ADB9-E4AC9AFB53F7.png 1239w" sizes="auto, (max-width: 767px) 89vw, (max-width: 1000px) 54vw, (max-width: 1071px) 543px, 580px" /></a></figure>



<p class="wp-block-paragraph">とりあえず<a href="https://blog.osakana.net/archives/8985">Ubuntu18.04で信頼できないレポジトリを使う</a> で行った「deb [ allow-insecure=yes trusted=yes ]」を追加する対処を行ってみる</p>



<figure class="wp-block-image size-large"><a href="https://blog.osakana.net/wp-content/uploads/2026/07/3EED10C2-7794-4434-9784-D58C47D887B1.png"><img loading="lazy" decoding="async" width="1024" height="631" src="https://blog.osakana.net/wp-content/uploads/2026/07/3EED10C2-7794-4434-9784-D58C47D887B1-1024x631.png" alt="" class="wp-image-17487" srcset="https://blog.osakana.net/wp-content/uploads/2026/07/3EED10C2-7794-4434-9784-D58C47D887B1-1024x631.png 1024w, https://blog.osakana.net/wp-content/uploads/2026/07/3EED10C2-7794-4434-9784-D58C47D887B1-300x185.png 300w, https://blog.osakana.net/wp-content/uploads/2026/07/3EED10C2-7794-4434-9784-D58C47D887B1-768x473.png 768w, https://blog.osakana.net/wp-content/uploads/2026/07/3EED10C2-7794-4434-9784-D58C47D887B1.png 1237w" sizes="auto, (max-width: 767px) 89vw, (max-width: 1000px) 54vw, (max-width: 1071px) 543px, 580px" /></a></figure>



<p class="wp-block-paragraph">/etc/apt/sources.list への編集をしていなかったので、再修正</p>



<figure class="wp-block-image size-large"><a href="https://blog.osakana.net/wp-content/uploads/2026/07/B52D5B96-5983-48D4-8705-223828C5935F.png"><img loading="lazy" decoding="async" width="1024" height="539" src="https://blog.osakana.net/wp-content/uploads/2026/07/B52D5B96-5983-48D4-8705-223828C5935F-1024x539.png" alt="" class="wp-image-17488" srcset="https://blog.osakana.net/wp-content/uploads/2026/07/B52D5B96-5983-48D4-8705-223828C5935F-1024x539.png 1024w, https://blog.osakana.net/wp-content/uploads/2026/07/B52D5B96-5983-48D4-8705-223828C5935F-300x158.png 300w, https://blog.osakana.net/wp-content/uploads/2026/07/B52D5B96-5983-48D4-8705-223828C5935F-768x404.png 768w, https://blog.osakana.net/wp-content/uploads/2026/07/B52D5B96-5983-48D4-8705-223828C5935F.png 1239w" sizes="auto, (max-width: 767px) 89vw, (max-width: 1000px) 54vw, (max-width: 1071px) 543px, 580px" /></a></figure>



<p class="wp-block-paragraph">変わらない？</p>



<p class="wp-block-paragraph">メッセージにある「apt modernize-sources」を実行</p>



<figure class="wp-block-image size-full"><a href="https://blog.osakana.net/wp-content/uploads/2026/07/2058C9FC-0C2E-49CB-903C-359D132EFEA9.png"><img loading="lazy" decoding="async" width="1004" height="480" src="https://blog.osakana.net/wp-content/uploads/2026/07/2058C9FC-0C2E-49CB-903C-359D132EFEA9.png" alt="" class="wp-image-17489" srcset="https://blog.osakana.net/wp-content/uploads/2026/07/2058C9FC-0C2E-49CB-903C-359D132EFEA9.png 1004w, https://blog.osakana.net/wp-content/uploads/2026/07/2058C9FC-0C2E-49CB-903C-359D132EFEA9-300x143.png 300w, https://blog.osakana.net/wp-content/uploads/2026/07/2058C9FC-0C2E-49CB-903C-359D132EFEA9-768x367.png 768w" sizes="auto, (max-width: 767px) 89vw, (max-width: 1000px) 54vw, (max-width: 1071px) 543px, 580px" /></a></figure>



<figure class="wp-block-image size-large"><a href="https://blog.osakana.net/wp-content/uploads/2026/07/8DE3693F-B86C-4B55-9375-9C61C409E966.png"><img loading="lazy" decoding="async" width="1024" height="562" src="https://blog.osakana.net/wp-content/uploads/2026/07/8DE3693F-B86C-4B55-9375-9C61C409E966-1024x562.png" alt="" class="wp-image-17490" srcset="https://blog.osakana.net/wp-content/uploads/2026/07/8DE3693F-B86C-4B55-9375-9C61C409E966-1024x562.png 1024w, https://blog.osakana.net/wp-content/uploads/2026/07/8DE3693F-B86C-4B55-9375-9C61C409E966-300x165.png 300w, https://blog.osakana.net/wp-content/uploads/2026/07/8DE3693F-B86C-4B55-9375-9C61C409E966-768x422.png 768w, https://blog.osakana.net/wp-content/uploads/2026/07/8DE3693F-B86C-4B55-9375-9C61C409E966.png 1135w" sizes="auto, (max-width: 767px) 89vw, (max-width: 1000px) 54vw, (max-width: 1071px) 543px, 580px" /></a></figure>



<p class="wp-block-paragraph">aptレポジトリの書式が変わるコマンドでしたか</p>



<p class="wp-block-paragraph">/etc/apt/sources.list.d/ にある ~.sources 内にある「Trusted: yes」を「Trusted: no」に書き換えて見るもエラー</p>



<figure class="wp-block-image size-large"><a href="https://blog.osakana.net/wp-content/uploads/2026/07/49F8D3A0-CF0C-4AFD-9F30-4217EF85088D.png"><img loading="lazy" decoding="async" width="1024" height="560" src="https://blog.osakana.net/wp-content/uploads/2026/07/49F8D3A0-CF0C-4AFD-9F30-4217EF85088D-1024x560.png" alt="" class="wp-image-17491" srcset="https://blog.osakana.net/wp-content/uploads/2026/07/49F8D3A0-CF0C-4AFD-9F30-4217EF85088D-1024x560.png 1024w, https://blog.osakana.net/wp-content/uploads/2026/07/49F8D3A0-CF0C-4AFD-9F30-4217EF85088D-300x164.png 300w, https://blog.osakana.net/wp-content/uploads/2026/07/49F8D3A0-CF0C-4AFD-9F30-4217EF85088D-768x420.png 768w, https://blog.osakana.net/wp-content/uploads/2026/07/49F8D3A0-CF0C-4AFD-9F30-4217EF85088D.png 1234w" sizes="auto, (max-width: 767px) 89vw, (max-width: 1000px) 54vw, (max-width: 1071px) 543px, 580px" /></a></figure>



<p class="wp-block-paragraph">このあと、いくつか実験をしてみたが、解決にはいたらず</p>



<p class="wp-block-paragraph">また、中国語以外だとうまく動かないだけ？というのがあったので、再インストール</p>



<figure class="wp-block-image size-large"><a href="https://blog.osakana.net/wp-content/uploads/2026/07/4FE496EC-4B68-400A-8525-F0E6E37A9ED8.png"><img loading="lazy" decoding="async" width="1024" height="594" src="https://blog.osakana.net/wp-content/uploads/2026/07/4FE496EC-4B68-400A-8525-F0E6E37A9ED8-1024x594.png" alt="" class="wp-image-17492" srcset="https://blog.osakana.net/wp-content/uploads/2026/07/4FE496EC-4B68-400A-8525-F0E6E37A9ED8-1024x594.png 1024w, https://blog.osakana.net/wp-content/uploads/2026/07/4FE496EC-4B68-400A-8525-F0E6E37A9ED8-300x174.png 300w, https://blog.osakana.net/wp-content/uploads/2026/07/4FE496EC-4B68-400A-8525-F0E6E37A9ED8-768x445.png 768w, https://blog.osakana.net/wp-content/uploads/2026/07/4FE496EC-4B68-400A-8525-F0E6E37A9ED8-1536x890.png 1536w, https://blog.osakana.net/wp-content/uploads/2026/07/4FE496EC-4B68-400A-8525-F0E6E37A9ED8.png 1594w" sizes="auto, (max-width: 767px) 89vw, (max-width: 1000px) 54vw, (max-width: 1071px) 543px, 580px" /></a></figure>



<figure class="wp-block-image size-large"><a href="https://blog.osakana.net/wp-content/uploads/2026/07/4F4D335A-F46A-42A8-B0B1-C2C1FA95B341.png"><img loading="lazy" decoding="async" width="1024" height="598" src="https://blog.osakana.net/wp-content/uploads/2026/07/4F4D335A-F46A-42A8-B0B1-C2C1FA95B341-1024x598.png" alt="" class="wp-image-17495" srcset="https://blog.osakana.net/wp-content/uploads/2026/07/4F4D335A-F46A-42A8-B0B1-C2C1FA95B341-1024x598.png 1024w, https://blog.osakana.net/wp-content/uploads/2026/07/4F4D335A-F46A-42A8-B0B1-C2C1FA95B341-300x175.png 300w, https://blog.osakana.net/wp-content/uploads/2026/07/4F4D335A-F46A-42A8-B0B1-C2C1FA95B341-768x449.png 768w, https://blog.osakana.net/wp-content/uploads/2026/07/4F4D335A-F46A-42A8-B0B1-C2C1FA95B341-1536x898.png 1536w, https://blog.osakana.net/wp-content/uploads/2026/07/4F4D335A-F46A-42A8-B0B1-C2C1FA95B341.png 1576w" sizes="auto, (max-width: 767px) 89vw, (max-width: 1000px) 54vw, (max-width: 1071px) 543px, 580px" /></a></figure>



<p class="wp-block-paragraph">変化はありませんでした</p>



<p class="wp-block-paragraph">terminalで調査していたところ、突然表示されました</p>



<figure class="wp-block-image size-large"><a href="https://blog.osakana.net/wp-content/uploads/2026/07/78CB2131-63DD-4E5B-9DD5-784CACDAD265.png"><img loading="lazy" decoding="async" width="1024" height="601" src="https://blog.osakana.net/wp-content/uploads/2026/07/78CB2131-63DD-4E5B-9DD5-784CACDAD265-1024x601.png" alt="" class="wp-image-17499" srcset="https://blog.osakana.net/wp-content/uploads/2026/07/78CB2131-63DD-4E5B-9DD5-784CACDAD265-1024x601.png 1024w, https://blog.osakana.net/wp-content/uploads/2026/07/78CB2131-63DD-4E5B-9DD5-784CACDAD265-300x176.png 300w, https://blog.osakana.net/wp-content/uploads/2026/07/78CB2131-63DD-4E5B-9DD5-784CACDAD265-768x451.png 768w, https://blog.osakana.net/wp-content/uploads/2026/07/78CB2131-63DD-4E5B-9DD5-784CACDAD265-1536x902.png 1536w, https://blog.osakana.net/wp-content/uploads/2026/07/78CB2131-63DD-4E5B-9DD5-784CACDAD265.png 1577w" sizes="auto, (max-width: 767px) 89vw, (max-width: 1000px) 54vw, (max-width: 1071px) 543px, 580px" /></a></figure>



<p class="wp-block-paragraph">アプリの登録がない？</p>



<figure class="wp-block-image size-large"><a href="https://blog.osakana.net/wp-content/uploads/2026/07/8CFBB21B-7AEE-4A9A-853F-EC1586640C99.png"><img loading="lazy" decoding="async" width="1024" height="596" src="https://blog.osakana.net/wp-content/uploads/2026/07/8CFBB21B-7AEE-4A9A-853F-EC1586640C99-1024x596.png" alt="" class="wp-image-17501" srcset="https://blog.osakana.net/wp-content/uploads/2026/07/8CFBB21B-7AEE-4A9A-853F-EC1586640C99-1024x596.png 1024w, https://blog.osakana.net/wp-content/uploads/2026/07/8CFBB21B-7AEE-4A9A-853F-EC1586640C99-300x175.png 300w, https://blog.osakana.net/wp-content/uploads/2026/07/8CFBB21B-7AEE-4A9A-853F-EC1586640C99-768x447.png 768w, https://blog.osakana.net/wp-content/uploads/2026/07/8CFBB21B-7AEE-4A9A-853F-EC1586640C99-1536x894.png 1536w, https://blog.osakana.net/wp-content/uploads/2026/07/8CFBB21B-7AEE-4A9A-853F-EC1586640C99.png 1577w" sizes="auto, (max-width: 767px) 89vw, (max-width: 1000px) 54vw, (max-width: 1071px) 543px, 580px" /></a></figure>



<p class="wp-block-paragraph">設定から言語変更を行う</p>



<figure class="wp-block-image size-large"><a href="https://blog.osakana.net/wp-content/uploads/2026/07/72BC725C-05AF-4472-A25B-95D76687A40D.png"><img loading="lazy" decoding="async" width="1024" height="641" src="https://blog.osakana.net/wp-content/uploads/2026/07/72BC725C-05AF-4472-A25B-95D76687A40D-1024x641.png" alt="" class="wp-image-17502" srcset="https://blog.osakana.net/wp-content/uploads/2026/07/72BC725C-05AF-4472-A25B-95D76687A40D-1024x641.png 1024w, https://blog.osakana.net/wp-content/uploads/2026/07/72BC725C-05AF-4472-A25B-95D76687A40D-300x188.png 300w, https://blog.osakana.net/wp-content/uploads/2026/07/72BC725C-05AF-4472-A25B-95D76687A40D-768x481.png 768w, https://blog.osakana.net/wp-content/uploads/2026/07/72BC725C-05AF-4472-A25B-95D76687A40D.png 1171w" sizes="auto, (max-width: 767px) 89vw, (max-width: 1000px) 54vw, (max-width: 1071px) 543px, 580px" /></a></figure>



<figure class="wp-block-image size-full"><a href="https://blog.osakana.net/wp-content/uploads/2026/07/4E7E01CA-B90D-43A2-B1B1-9E62271D10D9.png"><img loading="lazy" decoding="async" width="931" height="498" src="https://blog.osakana.net/wp-content/uploads/2026/07/4E7E01CA-B90D-43A2-B1B1-9E62271D10D9.png" alt="" class="wp-image-17503" srcset="https://blog.osakana.net/wp-content/uploads/2026/07/4E7E01CA-B90D-43A2-B1B1-9E62271D10D9.png 931w, https://blog.osakana.net/wp-content/uploads/2026/07/4E7E01CA-B90D-43A2-B1B1-9E62271D10D9-300x160.png 300w, https://blog.osakana.net/wp-content/uploads/2026/07/4E7E01CA-B90D-43A2-B1B1-9E62271D10D9-768x411.png 768w" sizes="auto, (max-width: 767px) 89vw, (max-width: 1000px) 54vw, (max-width: 1071px) 543px, 580px" /></a></figure>



<p class="wp-block-paragraph">下段の「検討言語」には「日本語」があった</p>



<figure class="wp-block-image size-large"><a href="https://blog.osakana.net/wp-content/uploads/2026/07/3A921D68-1806-4CFE-BF82-369FA1410568.png"><img loading="lazy" decoding="async" width="1024" height="645" src="https://blog.osakana.net/wp-content/uploads/2026/07/3A921D68-1806-4CFE-BF82-369FA1410568-1024x645.png" alt="" class="wp-image-17504" srcset="https://blog.osakana.net/wp-content/uploads/2026/07/3A921D68-1806-4CFE-BF82-369FA1410568-1024x645.png 1024w, https://blog.osakana.net/wp-content/uploads/2026/07/3A921D68-1806-4CFE-BF82-369FA1410568-300x189.png 300w, https://blog.osakana.net/wp-content/uploads/2026/07/3A921D68-1806-4CFE-BF82-369FA1410568-768x484.png 768w, https://blog.osakana.net/wp-content/uploads/2026/07/3A921D68-1806-4CFE-BF82-369FA1410568.png 1167w" sizes="auto, (max-width: 767px) 89vw, (max-width: 1000px) 54vw, (max-width: 1071px) 543px, 580px" /></a></figure>



<figure class="wp-block-image size-full"><a href="https://blog.osakana.net/wp-content/uploads/2026/07/DBAACAD6-3A78-426D-B70A-F27E242640C8.png"><img loading="lazy" decoding="async" width="486" height="574" src="https://blog.osakana.net/wp-content/uploads/2026/07/DBAACAD6-3A78-426D-B70A-F27E242640C8.png" alt="" class="wp-image-17505" srcset="https://blog.osakana.net/wp-content/uploads/2026/07/DBAACAD6-3A78-426D-B70A-F27E242640C8.png 486w, https://blog.osakana.net/wp-content/uploads/2026/07/DBAACAD6-3A78-426D-B70A-F27E242640C8-254x300.png 254w" sizes="auto, (max-width: 486px) 100vw, 486px" /></a></figure>



<figure class="wp-block-image size-full"><a href="https://blog.osakana.net/wp-content/uploads/2026/07/D683AD72-F288-4B10-A3F0-5A59876697F9.png"><img loading="lazy" decoding="async" width="938" height="479" src="https://blog.osakana.net/wp-content/uploads/2026/07/D683AD72-F288-4B10-A3F0-5A59876697F9.png" alt="" class="wp-image-17506" srcset="https://blog.osakana.net/wp-content/uploads/2026/07/D683AD72-F288-4B10-A3F0-5A59876697F9.png 938w, https://blog.osakana.net/wp-content/uploads/2026/07/D683AD72-F288-4B10-A3F0-5A59876697F9-300x153.png 300w, https://blog.osakana.net/wp-content/uploads/2026/07/D683AD72-F288-4B10-A3F0-5A59876697F9-768x392.png 768w" sizes="auto, (max-width: 767px) 89vw, (max-width: 1000px) 54vw, (max-width: 1071px) 543px, 580px" /></a></figure>



<p class="wp-block-paragraph">再起動するとデスクトップのアイテムが日本語に</p>



<figure class="wp-block-image size-large"><a href="https://blog.osakana.net/wp-content/uploads/2026/07/2F77FE31-6D9E-44AF-B1C2-E4948207919F.png"><img loading="lazy" decoding="async" width="1024" height="600" src="https://blog.osakana.net/wp-content/uploads/2026/07/2F77FE31-6D9E-44AF-B1C2-E4948207919F-1024x600.png" alt="" class="wp-image-17507" srcset="https://blog.osakana.net/wp-content/uploads/2026/07/2F77FE31-6D9E-44AF-B1C2-E4948207919F-1024x600.png 1024w, https://blog.osakana.net/wp-content/uploads/2026/07/2F77FE31-6D9E-44AF-B1C2-E4948207919F-300x176.png 300w, https://blog.osakana.net/wp-content/uploads/2026/07/2F77FE31-6D9E-44AF-B1C2-E4948207919F-768x450.png 768w, https://blog.osakana.net/wp-content/uploads/2026/07/2F77FE31-6D9E-44AF-B1C2-E4948207919F-1536x900.png 1536w, https://blog.osakana.net/wp-content/uploads/2026/07/2F77FE31-6D9E-44AF-B1C2-E4948207919F.png 1578w" sizes="auto, (max-width: 767px) 89vw, (max-width: 1000px) 54vw, (max-width: 1071px) 543px, 580px" /></a></figure>



<figure class="wp-block-image size-large"><a href="https://blog.osakana.net/wp-content/uploads/2026/07/E3F7C789-C75C-492A-82ED-870A0D7911C0.png"><img loading="lazy" decoding="async" width="1024" height="597" src="https://blog.osakana.net/wp-content/uploads/2026/07/E3F7C789-C75C-492A-82ED-870A0D7911C0-1024x597.png" alt="" class="wp-image-17508" srcset="https://blog.osakana.net/wp-content/uploads/2026/07/E3F7C789-C75C-492A-82ED-870A0D7911C0-1024x597.png 1024w, https://blog.osakana.net/wp-content/uploads/2026/07/E3F7C789-C75C-492A-82ED-870A0D7911C0-300x175.png 300w, https://blog.osakana.net/wp-content/uploads/2026/07/E3F7C789-C75C-492A-82ED-870A0D7911C0-768x448.png 768w, https://blog.osakana.net/wp-content/uploads/2026/07/E3F7C789-C75C-492A-82ED-870A0D7911C0-1536x896.png 1536w, https://blog.osakana.net/wp-content/uploads/2026/07/E3F7C789-C75C-492A-82ED-870A0D7911C0.png 1579w" sizes="auto, (max-width: 767px) 89vw, (max-width: 1000px) 54vw, (max-width: 1071px) 543px, 580px" /></a></figure>



<figure class="wp-block-image size-large"><a href="https://blog.osakana.net/wp-content/uploads/2026/07/636E96DE-A26A-421C-85E6-B40FA473EE5B.png"><img loading="lazy" decoding="async" width="1024" height="599" src="https://blog.osakana.net/wp-content/uploads/2026/07/636E96DE-A26A-421C-85E6-B40FA473EE5B-1024x599.png" alt="" class="wp-image-17509" srcset="https://blog.osakana.net/wp-content/uploads/2026/07/636E96DE-A26A-421C-85E6-B40FA473EE5B-1024x599.png 1024w, https://blog.osakana.net/wp-content/uploads/2026/07/636E96DE-A26A-421C-85E6-B40FA473EE5B-300x175.png 300w, https://blog.osakana.net/wp-content/uploads/2026/07/636E96DE-A26A-421C-85E6-B40FA473EE5B-768x449.png 768w, https://blog.osakana.net/wp-content/uploads/2026/07/636E96DE-A26A-421C-85E6-B40FA473EE5B-1536x898.png 1536w, https://blog.osakana.net/wp-content/uploads/2026/07/636E96DE-A26A-421C-85E6-B40FA473EE5B.png 1580w" sizes="auto, (max-width: 767px) 89vw, (max-width: 1000px) 54vw, (max-width: 1071px) 543px, 580px" /></a></figure>



<figure class="wp-block-image size-large"><a href="https://blog.osakana.net/wp-content/uploads/2026/07/27576B1E-DA97-4992-B990-5D59F049B0BA.png"><img loading="lazy" decoding="async" width="1024" height="602" src="https://blog.osakana.net/wp-content/uploads/2026/07/27576B1E-DA97-4992-B990-5D59F049B0BA-1024x602.png" alt="" class="wp-image-17510" srcset="https://blog.osakana.net/wp-content/uploads/2026/07/27576B1E-DA97-4992-B990-5D59F049B0BA-1024x602.png 1024w, https://blog.osakana.net/wp-content/uploads/2026/07/27576B1E-DA97-4992-B990-5D59F049B0BA-300x176.png 300w, https://blog.osakana.net/wp-content/uploads/2026/07/27576B1E-DA97-4992-B990-5D59F049B0BA-768x451.png 768w, https://blog.osakana.net/wp-content/uploads/2026/07/27576B1E-DA97-4992-B990-5D59F049B0BA-1536x903.png 1536w, https://blog.osakana.net/wp-content/uploads/2026/07/27576B1E-DA97-4992-B990-5D59F049B0BA.png 1565w" sizes="auto, (max-width: 767px) 89vw, (max-width: 1000px) 54vw, (max-width: 1071px) 543px, 580px" /></a></figure>



<figure class="wp-block-image size-large"><a href="https://blog.osakana.net/wp-content/uploads/2026/07/6485B2B2-C18A-4411-97AC-59A412FE4CF1.png"><img loading="lazy" decoding="async" width="1024" height="640" src="https://blog.osakana.net/wp-content/uploads/2026/07/6485B2B2-C18A-4411-97AC-59A412FE4CF1-1024x640.png" alt="" class="wp-image-17511" srcset="https://blog.osakana.net/wp-content/uploads/2026/07/6485B2B2-C18A-4411-97AC-59A412FE4CF1-1024x640.png 1024w, https://blog.osakana.net/wp-content/uploads/2026/07/6485B2B2-C18A-4411-97AC-59A412FE4CF1-300x187.png 300w, https://blog.osakana.net/wp-content/uploads/2026/07/6485B2B2-C18A-4411-97AC-59A412FE4CF1-768x480.png 768w, https://blog.osakana.net/wp-content/uploads/2026/07/6485B2B2-C18A-4411-97AC-59A412FE4CF1.png 1164w" sizes="auto, (max-width: 767px) 89vw, (max-width: 1000px) 54vw, (max-width: 1071px) 543px, 580px" /></a></figure>



<p class="wp-block-paragraph">GUIからもソフトウェア更新は失敗、と</p>



<figure class="wp-block-image size-large"><a href="https://blog.osakana.net/wp-content/uploads/2026/07/892A70A4-9340-49AA-898E-56108143EF18.png"><img loading="lazy" decoding="async" width="1024" height="645" src="https://blog.osakana.net/wp-content/uploads/2026/07/892A70A4-9340-49AA-898E-56108143EF18-1024x645.png" alt="" class="wp-image-17512" srcset="https://blog.osakana.net/wp-content/uploads/2026/07/892A70A4-9340-49AA-898E-56108143EF18-1024x645.png 1024w, https://blog.osakana.net/wp-content/uploads/2026/07/892A70A4-9340-49AA-898E-56108143EF18-300x189.png 300w, https://blog.osakana.net/wp-content/uploads/2026/07/892A70A4-9340-49AA-898E-56108143EF18-768x484.png 768w, https://blog.osakana.net/wp-content/uploads/2026/07/892A70A4-9340-49AA-898E-56108143EF18.png 1199w" sizes="auto, (max-width: 767px) 89vw, (max-width: 1000px) 54vw, (max-width: 1071px) 543px, 580px" /></a></figure>
]]></content:encoded>
					
					<wfw:commentRss>https://blog.osakana.net/archives/17459/feed</wfw:commentRss>
			<slash:comments>0</slash:comments>
		
		
			</item>
		<item>
		<title>Nutanix CE のAOSを6.8.1から7.3.1.9へアップデート、他</title>
		<link>https://blog.osakana.net/archives/17402</link>
					<comments>https://blog.osakana.net/archives/17402#respond</comments>
		
		<dc:creator><![CDATA[osakanataro]]></dc:creator>
		<pubDate>Thu, 09 Jul 2026 00:04:59 +0000</pubDate>
				<category><![CDATA[Nutanix]]></category>
		<category><![CDATA[VMware]]></category>
		<category><![CDATA[仮想化]]></category>
		<guid isPermaLink="false">https://blog.osakana.net/?p=17402</guid>

					<description><![CDATA[ESXi上にNutanix CE 2.1(AOS6.8.1)を新規インストールしてから、LCMでアップデートを実施したメモ書き 最終的には下記の状態となった AHV hypervisor: el8.nutanix.202 &#8230; <p class="link-more"><a href="https://blog.osakana.net/archives/17402" class="more-link"><span class="screen-reader-text">"Nutanix CE のAOSを6.8.1から7.3.1.9へアップデート、他" の</span>続きを読む</a></p>]]></description>
										<content:encoded><![CDATA[
<p class="wp-block-paragraph"><a href="https://blog.osakana.net/archives/17041">ESXi上にNutanix CE 2.1(AOS6.8.1)を新規インストール</a>してから、LCMでアップデートを実施したメモ書き</p>



<p class="wp-block-paragraph">最終的には下記の状態となった</p>



<p class="wp-block-paragraph">AHV hypervisor: el8.nutanix.20230302.101026 → 10.0.0.1 → 10.0.1.6 → 10.0.1.9 →× <s>10.3.1.5</s> <br>AOS: 6.8.1 → 6.10.1.14 / 7.0.1.15 → 7.3.1.9<br>FSM: 5.0.0.1 → 5.3.0.1<br>Foundation 5.6.1 → 5.10.4<br>NCC 5.0.1 → 5.3.1.1</p>



<p class="wp-block-paragraph">アップデートはLCMで[Inverntory]を実施した後、[Updates]から操作する</p>



<figure class="wp-block-image size-large"><a href="https://blog.osakana.net/wp-content/uploads/2026/07/5466C630-1ABC-421F-8C0E-54B626787007.png"><img loading="lazy" decoding="async" width="1024" height="376" src="https://blog.osakana.net/wp-content/uploads/2026/07/5466C630-1ABC-421F-8C0E-54B626787007-1024x376.png" alt="" class="wp-image-17403" srcset="https://blog.osakana.net/wp-content/uploads/2026/07/5466C630-1ABC-421F-8C0E-54B626787007-1024x376.png 1024w, https://blog.osakana.net/wp-content/uploads/2026/07/5466C630-1ABC-421F-8C0E-54B626787007-300x110.png 300w, https://blog.osakana.net/wp-content/uploads/2026/07/5466C630-1ABC-421F-8C0E-54B626787007-768x282.png 768w, https://blog.osakana.net/wp-content/uploads/2026/07/5466C630-1ABC-421F-8C0E-54B626787007-1536x564.png 1536w, https://blog.osakana.net/wp-content/uploads/2026/07/5466C630-1ABC-421F-8C0E-54B626787007.png 1911w" sizes="auto, (max-width: 767px) 89vw, (max-width: 1000px) 54vw, (max-width: 1071px) 543px, 580px" /></a></figure>



<p class="wp-block-paragraph">この段階でのバージョン変移予定<br>AHV hypervisor: el8.nutanix.20230302.101026 → 10.0.0.1<br>AOS: 6.8.1 → 6.10.1.14<br>FSM: 5.0.0.1 → 5.3.0.1<br>Foundation 5.6.1 → 5.10.4<br>NCC 5.0.1 → 5.3.1.1</p>



<p class="wp-block-paragraph">Nutanix CEではAHVを10.3以上にあげると死ぬ、という話があるけど</p>



<p class="wp-block-paragraph">　Nutanix Community「<a href="https://next.nutanix.com/discussion-forum-14/do-not-upgrade-ce-to-ahv-10-3-and-higher-45028">Do Not Upgrade CE to AHV 10.3 and Higher</a>」</p>



<p class="wp-block-paragraph">今回は「AHV hypervisor 10.0.0.1」となっているので、とりあえずは問題はないようだ</p>



<p class="wp-block-paragraph">ただ、10.0.0.1以降のバージョンもあるけど、なんで10.0.0.1が選択されているんだろう？</p>



<figure class="wp-block-image size-full"><a href="https://blog.osakana.net/wp-content/uploads/2026/07/image.png"><img loading="lazy" decoding="async" width="804" height="736" src="https://blog.osakana.net/wp-content/uploads/2026/07/image.png" alt="" class="wp-image-17405" srcset="https://blog.osakana.net/wp-content/uploads/2026/07/image.png 804w, https://blog.osakana.net/wp-content/uploads/2026/07/image-300x275.png 300w, https://blog.osakana.net/wp-content/uploads/2026/07/image-768x703.png 768w" sizes="auto, (max-width: 767px) 89vw, (max-width: 1000px) 54vw, (max-width: 1071px) 543px, 580px" /></a></figure>



<p class="wp-block-paragraph">とりあえず全部にチェックを入れて進めてみる</p>



<figure class="wp-block-image size-full"><a href="https://blog.osakana.net/wp-content/uploads/2026/07/313EC9C2-FC4A-4289-9DB4-D65D822009FA.png"><img loading="lazy" decoding="async" width="981" height="455" src="https://blog.osakana.net/wp-content/uploads/2026/07/313EC9C2-FC4A-4289-9DB4-D65D822009FA.png" alt="" class="wp-image-17406" srcset="https://blog.osakana.net/wp-content/uploads/2026/07/313EC9C2-FC4A-4289-9DB4-D65D822009FA.png 981w, https://blog.osakana.net/wp-content/uploads/2026/07/313EC9C2-FC4A-4289-9DB4-D65D822009FA-300x139.png 300w, https://blog.osakana.net/wp-content/uploads/2026/07/313EC9C2-FC4A-4289-9DB4-D65D822009FA-768x356.png 768w" sizes="auto, (max-width: 767px) 89vw, (max-width: 1000px) 54vw, (max-width: 1071px) 543px, 580px" /></a></figure>



<p class="wp-block-paragraph">あれ？AOSのバージョンが「6.0.1.14」から「7.0.1.15」に書き換わってる？？</p>



<p class="wp-block-paragraph">この段階でのバージョン変移予定<br>AHV hypervisor: el8.nutanix.20230302.101026 → 10.0.0.1<br>AOS: 6.8.1 → 6.10.1.14 / 7.0.1.15<br>FSM: 5.0.0.1 → 5.3.0.1<br>Foundation 5.6.1 → 5.10.4<br>NCC 5.0.1 → 5.3.1.1</p>



<figure class="wp-block-image size-large"><a href="https://blog.osakana.net/wp-content/uploads/2026/07/B8E142EF-BE74-42B6-A826-4076FFD53E01.png"><img loading="lazy" decoding="async" width="1024" height="455" src="https://blog.osakana.net/wp-content/uploads/2026/07/B8E142EF-BE74-42B6-A826-4076FFD53E01-1024x455.png" alt="" class="wp-image-17407" srcset="https://blog.osakana.net/wp-content/uploads/2026/07/B8E142EF-BE74-42B6-A826-4076FFD53E01-1024x455.png 1024w, https://blog.osakana.net/wp-content/uploads/2026/07/B8E142EF-BE74-42B6-A826-4076FFD53E01-300x133.png 300w, https://blog.osakana.net/wp-content/uploads/2026/07/B8E142EF-BE74-42B6-A826-4076FFD53E01-768x341.png 768w, https://blog.osakana.net/wp-content/uploads/2026/07/B8E142EF-BE74-42B6-A826-4076FFD53E01.png 1401w" sizes="auto, (max-width: 767px) 89vw, (max-width: 1000px) 54vw, (max-width: 1071px) 543px, 580px" /></a></figure>



<figure class="wp-block-image size-large"><a href="https://blog.osakana.net/wp-content/uploads/2026/07/22E65655-E47E-43E1-A73E-9FF9BFCA76BD.png"><img loading="lazy" decoding="async" width="1024" height="211" src="https://blog.osakana.net/wp-content/uploads/2026/07/22E65655-E47E-43E1-A73E-9FF9BFCA76BD-1024x211.png" alt="" class="wp-image-17408" srcset="https://blog.osakana.net/wp-content/uploads/2026/07/22E65655-E47E-43E1-A73E-9FF9BFCA76BD-1024x211.png 1024w, https://blog.osakana.net/wp-content/uploads/2026/07/22E65655-E47E-43E1-A73E-9FF9BFCA76BD-300x62.png 300w, https://blog.osakana.net/wp-content/uploads/2026/07/22E65655-E47E-43E1-A73E-9FF9BFCA76BD-768x158.png 768w, https://blog.osakana.net/wp-content/uploads/2026/07/22E65655-E47E-43E1-A73E-9FF9BFCA76BD.png 1396w" sizes="auto, (max-width: 767px) 89vw, (max-width: 1000px) 54vw, (max-width: 1071px) 543px, 580px" /></a></figure>



<p class="wp-block-paragraph">実行中・・・</p>



<figure class="wp-block-image size-large"><a href="https://blog.osakana.net/wp-content/uploads/2026/07/8AD039CD-AFD7-4E71-B0CA-5C4DD79EED83.png"><img loading="lazy" decoding="async" width="1024" height="247" src="https://blog.osakana.net/wp-content/uploads/2026/07/8AD039CD-AFD7-4E71-B0CA-5C4DD79EED83-1024x247.png" alt="" class="wp-image-17409" srcset="https://blog.osakana.net/wp-content/uploads/2026/07/8AD039CD-AFD7-4E71-B0CA-5C4DD79EED83-1024x247.png 1024w, https://blog.osakana.net/wp-content/uploads/2026/07/8AD039CD-AFD7-4E71-B0CA-5C4DD79EED83-300x72.png 300w, https://blog.osakana.net/wp-content/uploads/2026/07/8AD039CD-AFD7-4E71-B0CA-5C4DD79EED83-768x185.png 768w, https://blog.osakana.net/wp-content/uploads/2026/07/8AD039CD-AFD7-4E71-B0CA-5C4DD79EED83.png 1378w" sizes="auto, (max-width: 767px) 89vw, (max-width: 1000px) 54vw, (max-width: 1071px) 543px, 580px" /></a></figure>



<figure class="wp-block-image size-large"><a href="https://blog.osakana.net/wp-content/uploads/2026/07/D8A35CE7-1EE9-480F-B547-18E2BFEFEA44.png"><img loading="lazy" decoding="async" width="1024" height="321" src="https://blog.osakana.net/wp-content/uploads/2026/07/D8A35CE7-1EE9-480F-B547-18E2BFEFEA44-1024x321.png" alt="" class="wp-image-17410" srcset="https://blog.osakana.net/wp-content/uploads/2026/07/D8A35CE7-1EE9-480F-B547-18E2BFEFEA44-1024x321.png 1024w, https://blog.osakana.net/wp-content/uploads/2026/07/D8A35CE7-1EE9-480F-B547-18E2BFEFEA44-300x94.png 300w, https://blog.osakana.net/wp-content/uploads/2026/07/D8A35CE7-1EE9-480F-B547-18E2BFEFEA44-768x241.png 768w, https://blog.osakana.net/wp-content/uploads/2026/07/D8A35CE7-1EE9-480F-B547-18E2BFEFEA44-1536x482.png 1536w, https://blog.osakana.net/wp-content/uploads/2026/07/D8A35CE7-1EE9-480F-B547-18E2BFEFEA44.png 1908w" sizes="auto, (max-width: 767px) 89vw, (max-width: 1000px) 54vw, (max-width: 1071px) 543px, 580px" /></a></figure>



<figure class="wp-block-image size-large"><a href="https://blog.osakana.net/wp-content/uploads/2026/07/0C7B25C9-C4C9-4C65-B845-DE94D156C272.png"><img loading="lazy" decoding="async" width="1024" height="735" src="https://blog.osakana.net/wp-content/uploads/2026/07/0C7B25C9-C4C9-4C65-B845-DE94D156C272-1024x735.png" alt="" class="wp-image-17411" srcset="https://blog.osakana.net/wp-content/uploads/2026/07/0C7B25C9-C4C9-4C65-B845-DE94D156C272-1024x735.png 1024w, https://blog.osakana.net/wp-content/uploads/2026/07/0C7B25C9-C4C9-4C65-B845-DE94D156C272-300x215.png 300w, https://blog.osakana.net/wp-content/uploads/2026/07/0C7B25C9-C4C9-4C65-B845-DE94D156C272-768x552.png 768w, https://blog.osakana.net/wp-content/uploads/2026/07/0C7B25C9-C4C9-4C65-B845-DE94D156C272.png 1295w" sizes="auto, (max-width: 767px) 89vw, (max-width: 1000px) 54vw, (max-width: 1071px) 543px, 580px" /></a></figure>



<p class="wp-block-paragraph">おそらくCVM再起動で再ログイン後</p>



<figure class="wp-block-image size-large"><a href="https://blog.osakana.net/wp-content/uploads/2026/07/image-1.png"><img loading="lazy" decoding="async" width="1024" height="212" src="https://blog.osakana.net/wp-content/uploads/2026/07/image-1-1024x212.png" alt="" class="wp-image-17414" srcset="https://blog.osakana.net/wp-content/uploads/2026/07/image-1-1024x212.png 1024w, https://blog.osakana.net/wp-content/uploads/2026/07/image-1-300x62.png 300w, https://blog.osakana.net/wp-content/uploads/2026/07/image-1-768x159.png 768w, https://blog.osakana.net/wp-content/uploads/2026/07/image-1-1536x319.png 1536w, https://blog.osakana.net/wp-content/uploads/2026/07/image-1.png 1914w" sizes="auto, (max-width: 767px) 89vw, (max-width: 1000px) 54vw, (max-width: 1071px) 543px, 580px" /></a></figure>



<figure class="wp-block-image size-large"><a href="https://blog.osakana.net/wp-content/uploads/2026/07/48E2D664-2D93-4835-A410-72A69F469EBD.png"><img loading="lazy" decoding="async" width="1024" height="505" src="https://blog.osakana.net/wp-content/uploads/2026/07/48E2D664-2D93-4835-A410-72A69F469EBD-1024x505.png" alt="" class="wp-image-17415" srcset="https://blog.osakana.net/wp-content/uploads/2026/07/48E2D664-2D93-4835-A410-72A69F469EBD-1024x505.png 1024w, https://blog.osakana.net/wp-content/uploads/2026/07/48E2D664-2D93-4835-A410-72A69F469EBD-300x148.png 300w, https://blog.osakana.net/wp-content/uploads/2026/07/48E2D664-2D93-4835-A410-72A69F469EBD-768x379.png 768w, https://blog.osakana.net/wp-content/uploads/2026/07/48E2D664-2D93-4835-A410-72A69F469EBD-1536x757.png 1536w, https://blog.osakana.net/wp-content/uploads/2026/07/48E2D664-2D93-4835-A410-72A69F469EBD.png 1899w" sizes="auto, (max-width: 767px) 89vw, (max-width: 1000px) 54vw, (max-width: 1071px) 543px, 580px" /></a></figure>



<figure class="wp-block-image size-large"><a href="https://blog.osakana.net/wp-content/uploads/2026/07/3BAAA09F-5DB7-47C6-B7E3-5EA357F077AF.png"><img loading="lazy" decoding="async" width="1024" height="359" src="https://blog.osakana.net/wp-content/uploads/2026/07/3BAAA09F-5DB7-47C6-B7E3-5EA357F077AF-1024x359.png" alt="" class="wp-image-17416" srcset="https://blog.osakana.net/wp-content/uploads/2026/07/3BAAA09F-5DB7-47C6-B7E3-5EA357F077AF-1024x359.png 1024w, https://blog.osakana.net/wp-content/uploads/2026/07/3BAAA09F-5DB7-47C6-B7E3-5EA357F077AF-300x105.png 300w, https://blog.osakana.net/wp-content/uploads/2026/07/3BAAA09F-5DB7-47C6-B7E3-5EA357F077AF-768x269.png 768w, https://blog.osakana.net/wp-content/uploads/2026/07/3BAAA09F-5DB7-47C6-B7E3-5EA357F077AF.png 1102w" sizes="auto, (max-width: 767px) 89vw, (max-width: 1000px) 54vw, (max-width: 1071px) 543px, 580px" /></a></figure>



<figure class="wp-block-image size-large"><a href="https://blog.osakana.net/wp-content/uploads/2026/07/853E09BF-E0AF-4A99-9F07-A67DB4D9F4FD.png"><img loading="lazy" decoding="async" width="1024" height="500" src="https://blog.osakana.net/wp-content/uploads/2026/07/853E09BF-E0AF-4A99-9F07-A67DB4D9F4FD-1024x500.png" alt="" class="wp-image-17417" srcset="https://blog.osakana.net/wp-content/uploads/2026/07/853E09BF-E0AF-4A99-9F07-A67DB4D9F4FD-1024x500.png 1024w, https://blog.osakana.net/wp-content/uploads/2026/07/853E09BF-E0AF-4A99-9F07-A67DB4D9F4FD-300x146.png 300w, https://blog.osakana.net/wp-content/uploads/2026/07/853E09BF-E0AF-4A99-9F07-A67DB4D9F4FD-768x375.png 768w, https://blog.osakana.net/wp-content/uploads/2026/07/853E09BF-E0AF-4A99-9F07-A67DB4D9F4FD-1536x749.png 1536w, https://blog.osakana.net/wp-content/uploads/2026/07/853E09BF-E0AF-4A99-9F07-A67DB4D9F4FD.png 1890w" sizes="auto, (max-width: 767px) 89vw, (max-width: 1000px) 54vw, (max-width: 1071px) 543px, 580px" /></a></figure>



<p class="wp-block-paragraph">えーと、18:58開始で、終わったの21:30すぎのはずなんですが２時間ぐらいで終わったことになってるのなぜ？？</p>



<figure class="wp-block-image size-large"><a href="https://blog.osakana.net/wp-content/uploads/2026/07/DBAD88DE-C48E-456B-8ADC-C332D9B8C19C.png"><img loading="lazy" decoding="async" width="1024" height="144" src="https://blog.osakana.net/wp-content/uploads/2026/07/DBAD88DE-C48E-456B-8ADC-C332D9B8C19C-1024x144.png" alt="" class="wp-image-17418" srcset="https://blog.osakana.net/wp-content/uploads/2026/07/DBAD88DE-C48E-456B-8ADC-C332D9B8C19C-1024x144.png 1024w, https://blog.osakana.net/wp-content/uploads/2026/07/DBAD88DE-C48E-456B-8ADC-C332D9B8C19C-300x42.png 300w, https://blog.osakana.net/wp-content/uploads/2026/07/DBAD88DE-C48E-456B-8ADC-C332D9B8C19C-768x108.png 768w, https://blog.osakana.net/wp-content/uploads/2026/07/DBAD88DE-C48E-456B-8ADC-C332D9B8C19C-1536x216.png 1536w, https://blog.osakana.net/wp-content/uploads/2026/07/DBAD88DE-C48E-456B-8ADC-C332D9B8C19C.png 1901w" sizes="auto, (max-width: 767px) 89vw, (max-width: 1000px) 54vw, (max-width: 1071px) 543px, 580px" /></a></figure>



<p class="wp-block-paragraph">で、LCMに戻るとAHV Hypervisor 10.0.1.6へのアップデートが登場</p>



<figure class="wp-block-image size-large"><a href="https://blog.osakana.net/wp-content/uploads/2026/07/EE1DD563-D5D6-4E48-8A03-60412A6AE669.png"><img loading="lazy" decoding="async" width="1024" height="209" src="https://blog.osakana.net/wp-content/uploads/2026/07/EE1DD563-D5D6-4E48-8A03-60412A6AE669-1024x209.png" alt="" class="wp-image-17419" srcset="https://blog.osakana.net/wp-content/uploads/2026/07/EE1DD563-D5D6-4E48-8A03-60412A6AE669-1024x209.png 1024w, https://blog.osakana.net/wp-content/uploads/2026/07/EE1DD563-D5D6-4E48-8A03-60412A6AE669-300x61.png 300w, https://blog.osakana.net/wp-content/uploads/2026/07/EE1DD563-D5D6-4E48-8A03-60412A6AE669-768x157.png 768w, https://blog.osakana.net/wp-content/uploads/2026/07/EE1DD563-D5D6-4E48-8A03-60412A6AE669-1536x314.png 1536w, https://blog.osakana.net/wp-content/uploads/2026/07/EE1DD563-D5D6-4E48-8A03-60412A6AE669.png 1890w" sizes="auto, (max-width: 767px) 89vw, (max-width: 1000px) 54vw, (max-width: 1071px) 543px, 580px" /></a></figure>



<p class="wp-block-paragraph">この段階でのバージョン変移予定<br>AHV hypervisor: el8.nutanix.20230302.101026 → 10.0.0.1 → 10.0.1.6<br>AOS: 6.8.1 → 6.10.1.14 / 7.0.1.15<br>FSM: 5.0.0.1 → 5.3.0.1<br>Foundation 5.6.1 → 5.10.4<br>NCC 5.0.1 → 5.3.1.1</p>



<p class="wp-block-paragraph">よりあたらしい10.0.1.9があるのに、10.0.1.6か、と思いつつアップデート</p>



<figure class="wp-block-image size-full"><a href="https://blog.osakana.net/wp-content/uploads/2026/07/D35B25E8-2E25-45EF-9ABF-64EB29EEF0E6.png"><img loading="lazy" decoding="async" width="799" height="690" src="https://blog.osakana.net/wp-content/uploads/2026/07/D35B25E8-2E25-45EF-9ABF-64EB29EEF0E6.png" alt="" class="wp-image-17420" srcset="https://blog.osakana.net/wp-content/uploads/2026/07/D35B25E8-2E25-45EF-9ABF-64EB29EEF0E6.png 799w, https://blog.osakana.net/wp-content/uploads/2026/07/D35B25E8-2E25-45EF-9ABF-64EB29EEF0E6-300x259.png 300w, https://blog.osakana.net/wp-content/uploads/2026/07/D35B25E8-2E25-45EF-9ABF-64EB29EEF0E6-768x663.png 768w" sizes="auto, (max-width: 767px) 89vw, (max-width: 1000px) 54vw, (max-width: 1071px) 543px, 580px" /></a></figure>



<figure class="wp-block-image size-large"><a href="https://blog.osakana.net/wp-content/uploads/2026/07/FEB1763B-E4C1-4327-BF38-C4D725575DF3.png"><img loading="lazy" decoding="async" width="1024" height="318" src="https://blog.osakana.net/wp-content/uploads/2026/07/FEB1763B-E4C1-4327-BF38-C4D725575DF3-1024x318.png" alt="" class="wp-image-17421" srcset="https://blog.osakana.net/wp-content/uploads/2026/07/FEB1763B-E4C1-4327-BF38-C4D725575DF3-1024x318.png 1024w, https://blog.osakana.net/wp-content/uploads/2026/07/FEB1763B-E4C1-4327-BF38-C4D725575DF3-300x93.png 300w, https://blog.osakana.net/wp-content/uploads/2026/07/FEB1763B-E4C1-4327-BF38-C4D725575DF3-768x238.png 768w, https://blog.osakana.net/wp-content/uploads/2026/07/FEB1763B-E4C1-4327-BF38-C4D725575DF3-1536x477.png 1536w, https://blog.osakana.net/wp-content/uploads/2026/07/FEB1763B-E4C1-4327-BF38-C4D725575DF3.png 1894w" sizes="auto, (max-width: 767px) 89vw, (max-width: 1000px) 54vw, (max-width: 1071px) 543px, 580px" /></a></figure>



<p class="wp-block-paragraph">エラー発生 <a href="http://portal.nutanix.com/kb/6945">KB6945</a> を見ろとある</p>



<p class="wp-block-paragraph">とりあえず再起動して再挑戦すると、先に進める</p>



<figure class="wp-block-image size-large"><a href="https://blog.osakana.net/wp-content/uploads/2026/07/image-2.png"><img loading="lazy" decoding="async" width="1024" height="345" src="https://blog.osakana.net/wp-content/uploads/2026/07/image-2-1024x345.png" alt="" class="wp-image-17422" srcset="https://blog.osakana.net/wp-content/uploads/2026/07/image-2-1024x345.png 1024w, https://blog.osakana.net/wp-content/uploads/2026/07/image-2-300x101.png 300w, https://blog.osakana.net/wp-content/uploads/2026/07/image-2-768x259.png 768w, https://blog.osakana.net/wp-content/uploads/2026/07/image-2.png 1416w" sizes="auto, (max-width: 767px) 89vw, (max-width: 1000px) 54vw, (max-width: 1071px) 543px, 580px" /></a></figure>



<figure class="wp-block-image size-large"><a href="https://blog.osakana.net/wp-content/uploads/2026/07/429C83DB-DD58-43FB-845A-99BB4220DC3E.png"><img loading="lazy" decoding="async" width="1024" height="392" src="https://blog.osakana.net/wp-content/uploads/2026/07/429C83DB-DD58-43FB-845A-99BB4220DC3E-1024x392.png" alt="" class="wp-image-17423" srcset="https://blog.osakana.net/wp-content/uploads/2026/07/429C83DB-DD58-43FB-845A-99BB4220DC3E-1024x392.png 1024w, https://blog.osakana.net/wp-content/uploads/2026/07/429C83DB-DD58-43FB-845A-99BB4220DC3E-300x115.png 300w, https://blog.osakana.net/wp-content/uploads/2026/07/429C83DB-DD58-43FB-845A-99BB4220DC3E-768x294.png 768w, https://blog.osakana.net/wp-content/uploads/2026/07/429C83DB-DD58-43FB-845A-99BB4220DC3E.png 1307w" sizes="auto, (max-width: 767px) 89vw, (max-width: 1000px) 54vw, (max-width: 1071px) 543px, 580px" /></a></figure>



<figure class="wp-block-image size-large"><a href="https://blog.osakana.net/wp-content/uploads/2026/07/AB545D0E-3BFE-48A3-AB50-813A6A6FE7D4.png"><img loading="lazy" decoding="async" width="1024" height="606" src="https://blog.osakana.net/wp-content/uploads/2026/07/AB545D0E-3BFE-48A3-AB50-813A6A6FE7D4-1024x606.png" alt="" class="wp-image-17424" srcset="https://blog.osakana.net/wp-content/uploads/2026/07/AB545D0E-3BFE-48A3-AB50-813A6A6FE7D4-1024x606.png 1024w, https://blog.osakana.net/wp-content/uploads/2026/07/AB545D0E-3BFE-48A3-AB50-813A6A6FE7D4-300x178.png 300w, https://blog.osakana.net/wp-content/uploads/2026/07/AB545D0E-3BFE-48A3-AB50-813A6A6FE7D4-768x455.png 768w, https://blog.osakana.net/wp-content/uploads/2026/07/AB545D0E-3BFE-48A3-AB50-813A6A6FE7D4.png 1299w" sizes="auto, (max-width: 767px) 89vw, (max-width: 1000px) 54vw, (max-width: 1071px) 543px, 580px" /></a></figure>



<figure class="wp-block-image size-large"><a href="https://blog.osakana.net/wp-content/uploads/2026/07/image-3.png"><img loading="lazy" decoding="async" width="1024" height="535" src="https://blog.osakana.net/wp-content/uploads/2026/07/image-3-1024x535.png" alt="" class="wp-image-17425" srcset="https://blog.osakana.net/wp-content/uploads/2026/07/image-3-1024x535.png 1024w, https://blog.osakana.net/wp-content/uploads/2026/07/image-3-300x157.png 300w, https://blog.osakana.net/wp-content/uploads/2026/07/image-3-768x401.png 768w, https://blog.osakana.net/wp-content/uploads/2026/07/image-3.png 1297w" sizes="auto, (max-width: 767px) 89vw, (max-width: 1000px) 54vw, (max-width: 1071px) 543px, 580px" /></a></figure>



<p class="wp-block-paragraph">約３０分で終了</p>



<p class="wp-block-paragraph">次のアップデートは10.0.1.9</p>



<figure class="wp-block-image size-large"><a href="https://blog.osakana.net/wp-content/uploads/2026/07/D70B1162-470C-427C-8C1E-EA8865DF5CDF.png"><img loading="lazy" decoding="async" width="1024" height="109" src="https://blog.osakana.net/wp-content/uploads/2026/07/D70B1162-470C-427C-8C1E-EA8865DF5CDF-1024x109.png" alt="" class="wp-image-17426" srcset="https://blog.osakana.net/wp-content/uploads/2026/07/D70B1162-470C-427C-8C1E-EA8865DF5CDF-1024x109.png 1024w, https://blog.osakana.net/wp-content/uploads/2026/07/D70B1162-470C-427C-8C1E-EA8865DF5CDF-300x32.png 300w, https://blog.osakana.net/wp-content/uploads/2026/07/D70B1162-470C-427C-8C1E-EA8865DF5CDF-768x82.png 768w, https://blog.osakana.net/wp-content/uploads/2026/07/D70B1162-470C-427C-8C1E-EA8865DF5CDF-1536x164.png 1536w, https://blog.osakana.net/wp-content/uploads/2026/07/D70B1162-470C-427C-8C1E-EA8865DF5CDF.png 1887w" sizes="auto, (max-width: 767px) 89vw, (max-width: 1000px) 54vw, (max-width: 1071px) 543px, 580px" /></a></figure>



<figure class="wp-block-image size-full"><a href="https://blog.osakana.net/wp-content/uploads/2026/07/1951C254-1C33-43AC-9036-4C4AA07E6CF1.png"><img loading="lazy" decoding="async" width="785" height="387" src="https://blog.osakana.net/wp-content/uploads/2026/07/1951C254-1C33-43AC-9036-4C4AA07E6CF1.png" alt="" class="wp-image-17427" srcset="https://blog.osakana.net/wp-content/uploads/2026/07/1951C254-1C33-43AC-9036-4C4AA07E6CF1.png 785w, https://blog.osakana.net/wp-content/uploads/2026/07/1951C254-1C33-43AC-9036-4C4AA07E6CF1-300x148.png 300w, https://blog.osakana.net/wp-content/uploads/2026/07/1951C254-1C33-43AC-9036-4C4AA07E6CF1-768x379.png 768w" sizes="auto, (max-width: 767px) 89vw, (max-width: 1000px) 54vw, (max-width: 1071px) 543px, 580px" /></a></figure>



<p class="wp-block-paragraph">この段階でのバージョン変移予定<br>AHV hypervisor: el8.nutanix.20230302.101026 → 10.0.0.1 → 10.0.1.6 → 10.0.1.9<br>AOS: 6.8.1 → 6.10.1.14 / 7.0.1.15<br>FSM: 5.0.0.1 → 5.3.0.1<br>Foundation 5.6.1 → 5.10.4<br>NCC 5.0.1 → 5.3.1.1</p>



<figure class="wp-block-image size-large"><a href="https://blog.osakana.net/wp-content/uploads/2026/07/F9C22257-1F93-4073-A8BA-AFFD83C0E73A.png"><img loading="lazy" decoding="async" width="1024" height="342" src="https://blog.osakana.net/wp-content/uploads/2026/07/F9C22257-1F93-4073-A8BA-AFFD83C0E73A-1024x342.png" alt="" class="wp-image-17428" srcset="https://blog.osakana.net/wp-content/uploads/2026/07/F9C22257-1F93-4073-A8BA-AFFD83C0E73A-1024x342.png 1024w, https://blog.osakana.net/wp-content/uploads/2026/07/F9C22257-1F93-4073-A8BA-AFFD83C0E73A-300x100.png 300w, https://blog.osakana.net/wp-content/uploads/2026/07/F9C22257-1F93-4073-A8BA-AFFD83C0E73A-768x257.png 768w, https://blog.osakana.net/wp-content/uploads/2026/07/F9C22257-1F93-4073-A8BA-AFFD83C0E73A.png 1379w" sizes="auto, (max-width: 767px) 89vw, (max-width: 1000px) 54vw, (max-width: 1071px) 543px, 580px" /></a></figure>



<figure class="wp-block-image size-large"><a href="https://blog.osakana.net/wp-content/uploads/2026/07/0CBC8C0C-F140-44B6-8DF6-5BBFB5AFA5CA.png"><img loading="lazy" decoding="async" width="1024" height="396" src="https://blog.osakana.net/wp-content/uploads/2026/07/0CBC8C0C-F140-44B6-8DF6-5BBFB5AFA5CA-1024x396.png" alt="" class="wp-image-17429" srcset="https://blog.osakana.net/wp-content/uploads/2026/07/0CBC8C0C-F140-44B6-8DF6-5BBFB5AFA5CA-1024x396.png 1024w, https://blog.osakana.net/wp-content/uploads/2026/07/0CBC8C0C-F140-44B6-8DF6-5BBFB5AFA5CA-300x116.png 300w, https://blog.osakana.net/wp-content/uploads/2026/07/0CBC8C0C-F140-44B6-8DF6-5BBFB5AFA5CA-768x297.png 768w, https://blog.osakana.net/wp-content/uploads/2026/07/0CBC8C0C-F140-44B6-8DF6-5BBFB5AFA5CA.png 1285w" sizes="auto, (max-width: 767px) 89vw, (max-width: 1000px) 54vw, (max-width: 1071px) 543px, 580px" /></a></figure>



<figure class="wp-block-image size-large"><a href="https://blog.osakana.net/wp-content/uploads/2026/07/image-4.png"><img loading="lazy" decoding="async" width="1024" height="533" src="https://blog.osakana.net/wp-content/uploads/2026/07/image-4-1024x533.png" alt="" class="wp-image-17430" srcset="https://blog.osakana.net/wp-content/uploads/2026/07/image-4-1024x533.png 1024w, https://blog.osakana.net/wp-content/uploads/2026/07/image-4-300x156.png 300w, https://blog.osakana.net/wp-content/uploads/2026/07/image-4-768x400.png 768w, https://blog.osakana.net/wp-content/uploads/2026/07/image-4.png 1282w" sizes="auto, (max-width: 767px) 89vw, (max-width: 1000px) 54vw, (max-width: 1071px) 543px, 580px" /></a></figure>



<p class="wp-block-paragraph">とりあえずUpdateなしに？</p>



<figure class="wp-block-image size-large"><a href="https://blog.osakana.net/wp-content/uploads/2026/07/8A887A2E-F748-45E8-B684-94C5E103A55E.png"><img loading="lazy" decoding="async" width="1024" height="201" src="https://blog.osakana.net/wp-content/uploads/2026/07/8A887A2E-F748-45E8-B684-94C5E103A55E-1024x201.png" alt="" class="wp-image-17431" srcset="https://blog.osakana.net/wp-content/uploads/2026/07/8A887A2E-F748-45E8-B684-94C5E103A55E-1024x201.png 1024w, https://blog.osakana.net/wp-content/uploads/2026/07/8A887A2E-F748-45E8-B684-94C5E103A55E-300x59.png 300w, https://blog.osakana.net/wp-content/uploads/2026/07/8A887A2E-F748-45E8-B684-94C5E103A55E-768x151.png 768w, https://blog.osakana.net/wp-content/uploads/2026/07/8A887A2E-F748-45E8-B684-94C5E103A55E-1536x302.png 1536w, https://blog.osakana.net/wp-content/uploads/2026/07/8A887A2E-F748-45E8-B684-94C5E103A55E.png 1897w" sizes="auto, (max-width: 767px) 89vw, (max-width: 1000px) 54vw, (max-width: 1071px) 543px, 580px" /></a></figure>



<figure class="wp-block-image size-large"><a href="https://blog.osakana.net/wp-content/uploads/2026/07/FF4AF5E8-B235-4FCF-AAF1-E6C0A3324FE2.png"><img loading="lazy" decoding="async" width="1024" height="257" src="https://blog.osakana.net/wp-content/uploads/2026/07/FF4AF5E8-B235-4FCF-AAF1-E6C0A3324FE2-1024x257.png" alt="" class="wp-image-17432" srcset="https://blog.osakana.net/wp-content/uploads/2026/07/FF4AF5E8-B235-4FCF-AAF1-E6C0A3324FE2-1024x257.png 1024w, https://blog.osakana.net/wp-content/uploads/2026/07/FF4AF5E8-B235-4FCF-AAF1-E6C0A3324FE2-300x75.png 300w, https://blog.osakana.net/wp-content/uploads/2026/07/FF4AF5E8-B235-4FCF-AAF1-E6C0A3324FE2-768x193.png 768w, https://blog.osakana.net/wp-content/uploads/2026/07/FF4AF5E8-B235-4FCF-AAF1-E6C0A3324FE2-1536x386.png 1536w, https://blog.osakana.net/wp-content/uploads/2026/07/FF4AF5E8-B235-4FCF-AAF1-E6C0A3324FE2.png 1886w" sizes="auto, (max-width: 767px) 89vw, (max-width: 1000px) 54vw, (max-width: 1071px) 543px, 580px" /></a></figure>



<p class="wp-block-paragraph">もう１回Inventoryを実行してみたところアップデート登場</p>



<figure class="wp-block-image size-large"><a href="https://blog.osakana.net/wp-content/uploads/2026/07/6D987112-12C2-4643-AA11-F857144B74D6.png"><img loading="lazy" decoding="async" width="1024" height="251" src="https://blog.osakana.net/wp-content/uploads/2026/07/6D987112-12C2-4643-AA11-F857144B74D6-1024x251.png" alt="" class="wp-image-17433" srcset="https://blog.osakana.net/wp-content/uploads/2026/07/6D987112-12C2-4643-AA11-F857144B74D6-1024x251.png 1024w, https://blog.osakana.net/wp-content/uploads/2026/07/6D987112-12C2-4643-AA11-F857144B74D6-300x73.png 300w, https://blog.osakana.net/wp-content/uploads/2026/07/6D987112-12C2-4643-AA11-F857144B74D6-768x188.png 768w, https://blog.osakana.net/wp-content/uploads/2026/07/6D987112-12C2-4643-AA11-F857144B74D6-1536x376.png 1536w, https://blog.osakana.net/wp-content/uploads/2026/07/6D987112-12C2-4643-AA11-F857144B74D6.png 1890w" sizes="auto, (max-width: 767px) 89vw, (max-width: 1000px) 54vw, (max-width: 1071px) 543px, 580px" /></a></figure>



<p class="wp-block-paragraph">出たな！！問題児 10.3.x代の 10.3.1.5</p>



<figure class="wp-block-image size-full"><a href="https://blog.osakana.net/wp-content/uploads/2026/07/9E1AF81B-F9AF-42A6-822C-7FBFBDD8F6D2.png"><img loading="lazy" decoding="async" width="790" height="400" src="https://blog.osakana.net/wp-content/uploads/2026/07/9E1AF81B-F9AF-42A6-822C-7FBFBDD8F6D2.png" alt="" class="wp-image-17434" srcset="https://blog.osakana.net/wp-content/uploads/2026/07/9E1AF81B-F9AF-42A6-822C-7FBFBDD8F6D2.png 790w, https://blog.osakana.net/wp-content/uploads/2026/07/9E1AF81B-F9AF-42A6-822C-7FBFBDD8F6D2-300x152.png 300w, https://blog.osakana.net/wp-content/uploads/2026/07/9E1AF81B-F9AF-42A6-822C-7FBFBDD8F6D2-768x389.png 768w" sizes="auto, (max-width: 767px) 89vw, (max-width: 1000px) 54vw, (max-width: 1071px) 543px, 580px" /></a></figure>



<p class="wp-block-paragraph">10.0.1.9から 10.3.1.5の間のバージョンにすることはできない、と</p>



<p class="wp-block-paragraph">AOSの方はバージョンアップしても問題ないらしいので、7.0.1.15→7.3.1.9へのアップデートを試みる</p>



<p class="wp-block-paragraph">この段階でのバージョン変移予定<br>AHV hypervisor: el8.nutanix.20230302.101026 → 10.0.0.1 → 10.0.1.6 → 10.0.1.9 →× <s>10.3.1.5</s> <br>AOS: 6.8.1 → 6.10.1.14 / 7.0.1.15 → 7.3.1.9<br>FSM: 5.0.0.1 → 5.3.0.1<br>Foundation 5.6.1 → 5.10.4<br>NCC 5.0.1 → 5.3.1.1</p>



<figure class="wp-block-image size-large"><a href="https://blog.osakana.net/wp-content/uploads/2026/07/image-5.png"><img loading="lazy" decoding="async" width="1024" height="384" src="https://blog.osakana.net/wp-content/uploads/2026/07/image-5-1024x384.png" alt="" class="wp-image-17435" srcset="https://blog.osakana.net/wp-content/uploads/2026/07/image-5-1024x384.png 1024w, https://blog.osakana.net/wp-content/uploads/2026/07/image-5-300x112.png 300w, https://blog.osakana.net/wp-content/uploads/2026/07/image-5-768x288.png 768w, https://blog.osakana.net/wp-content/uploads/2026/07/image-5.png 1377w" sizes="auto, (max-width: 767px) 89vw, (max-width: 1000px) 54vw, (max-width: 1071px) 543px, 580px" /></a></figure>



<figure class="wp-block-image size-large"><a href="https://blog.osakana.net/wp-content/uploads/2026/07/29E9DF2A-0582-4667-8F72-AC855B40E4BE.png"><img loading="lazy" decoding="async" width="1024" height="224" src="https://blog.osakana.net/wp-content/uploads/2026/07/29E9DF2A-0582-4667-8F72-AC855B40E4BE-1024x224.png" alt="" class="wp-image-17436" srcset="https://blog.osakana.net/wp-content/uploads/2026/07/29E9DF2A-0582-4667-8F72-AC855B40E4BE-1024x224.png 1024w, https://blog.osakana.net/wp-content/uploads/2026/07/29E9DF2A-0582-4667-8F72-AC855B40E4BE-300x66.png 300w, https://blog.osakana.net/wp-content/uploads/2026/07/29E9DF2A-0582-4667-8F72-AC855B40E4BE-768x168.png 768w, https://blog.osakana.net/wp-content/uploads/2026/07/29E9DF2A-0582-4667-8F72-AC855B40E4BE.png 1379w" sizes="auto, (max-width: 767px) 89vw, (max-width: 1000px) 54vw, (max-width: 1071px) 543px, 580px" /></a></figure>



<figure class="wp-block-image size-large"><a href="https://blog.osakana.net/wp-content/uploads/2026/07/B7B614E9-A0EF-49BD-9E88-016D640B9153.png"><img loading="lazy" decoding="async" width="1024" height="389" src="https://blog.osakana.net/wp-content/uploads/2026/07/B7B614E9-A0EF-49BD-9E88-016D640B9153-1024x389.png" alt="" class="wp-image-17437" srcset="https://blog.osakana.net/wp-content/uploads/2026/07/B7B614E9-A0EF-49BD-9E88-016D640B9153-1024x389.png 1024w, https://blog.osakana.net/wp-content/uploads/2026/07/B7B614E9-A0EF-49BD-9E88-016D640B9153-300x114.png 300w, https://blog.osakana.net/wp-content/uploads/2026/07/B7B614E9-A0EF-49BD-9E88-016D640B9153-768x291.png 768w, https://blog.osakana.net/wp-content/uploads/2026/07/B7B614E9-A0EF-49BD-9E88-016D640B9153.png 1291w" sizes="auto, (max-width: 767px) 89vw, (max-width: 1000px) 54vw, (max-width: 1071px) 543px, 580px" /></a></figure>



<p class="wp-block-paragraph">アップデート完了</p>



<figure class="wp-block-image size-large"><a href="https://blog.osakana.net/wp-content/uploads/2026/07/6A8A3277-3A78-4731-806D-7AB6DD744849.png"><img loading="lazy" decoding="async" width="1024" height="126" src="https://blog.osakana.net/wp-content/uploads/2026/07/6A8A3277-3A78-4731-806D-7AB6DD744849-1024x126.png" alt="" class="wp-image-17438" srcset="https://blog.osakana.net/wp-content/uploads/2026/07/6A8A3277-3A78-4731-806D-7AB6DD744849-1024x126.png 1024w, https://blog.osakana.net/wp-content/uploads/2026/07/6A8A3277-3A78-4731-806D-7AB6DD744849-300x37.png 300w, https://blog.osakana.net/wp-content/uploads/2026/07/6A8A3277-3A78-4731-806D-7AB6DD744849-768x94.png 768w, https://blog.osakana.net/wp-content/uploads/2026/07/6A8A3277-3A78-4731-806D-7AB6DD744849-1536x189.png 1536w, https://blog.osakana.net/wp-content/uploads/2026/07/6A8A3277-3A78-4731-806D-7AB6DD744849.png 1898w" sizes="auto, (max-width: 767px) 89vw, (max-width: 1000px) 54vw, (max-width: 1071px) 543px, 580px" /></a></figure>



<figure class="wp-block-image size-large"><a href="https://blog.osakana.net/wp-content/uploads/2026/07/C57F8AE4-7E0D-44CB-AFD3-E8BE74A991E8.png"><img loading="lazy" decoding="async" width="1024" height="84" src="https://blog.osakana.net/wp-content/uploads/2026/07/C57F8AE4-7E0D-44CB-AFD3-E8BE74A991E8-1024x84.png" alt="" class="wp-image-17439" srcset="https://blog.osakana.net/wp-content/uploads/2026/07/C57F8AE4-7E0D-44CB-AFD3-E8BE74A991E8-1024x84.png 1024w, https://blog.osakana.net/wp-content/uploads/2026/07/C57F8AE4-7E0D-44CB-AFD3-E8BE74A991E8-300x24.png 300w, https://blog.osakana.net/wp-content/uploads/2026/07/C57F8AE4-7E0D-44CB-AFD3-E8BE74A991E8-768x63.png 768w, https://blog.osakana.net/wp-content/uploads/2026/07/C57F8AE4-7E0D-44CB-AFD3-E8BE74A991E8-1536x125.png 1536w, https://blog.osakana.net/wp-content/uploads/2026/07/C57F8AE4-7E0D-44CB-AFD3-E8BE74A991E8.png 1898w" sizes="auto, (max-width: 767px) 89vw, (max-width: 1000px) 54vw, (max-width: 1071px) 543px, 580px" /></a></figure>



<p class="wp-block-paragraph">現状<br>AHV hypervisor: el8.nutanix.20230302.101026 → 10.0.0.1 → 10.0.1.6 → 10.0.1.9 →× <s>10.3.1.5</s> <br>AOS: 6.8.1 → 6.10.1.14 / 7.0.1.15 → 7.3.1.9<br>FSM: 5.0.0.1 → 5.3.0.1<br>Foundation 5.6.1 → 5.10.4<br>NCC 5.0.1 → 5.3.1.1</p>



<hr class="wp-block-separator has-alpha-channel-opacity"/>



<p class="wp-block-paragraph">2026/07/10 追記</p>



<p class="wp-block-paragraph">実験してたら壊してしまったので再セットアップを行って、初回のバージョンアップが終わったところなんですがAHV hypervisorのバージョンに異変が・・・</p>



<figure class="wp-block-image size-large"><a href="https://blog.osakana.net/wp-content/uploads/2026/07/5165378E-0ECE-4DB9-8205-3A97A8D69496.png"><img loading="lazy" decoding="async" width="1024" height="89" src="https://blog.osakana.net/wp-content/uploads/2026/07/5165378E-0ECE-4DB9-8205-3A97A8D69496-1024x89.png" alt="" class="wp-image-17452" srcset="https://blog.osakana.net/wp-content/uploads/2026/07/5165378E-0ECE-4DB9-8205-3A97A8D69496-1024x89.png 1024w, https://blog.osakana.net/wp-content/uploads/2026/07/5165378E-0ECE-4DB9-8205-3A97A8D69496-300x26.png 300w, https://blog.osakana.net/wp-content/uploads/2026/07/5165378E-0ECE-4DB9-8205-3A97A8D69496-768x67.png 768w, https://blog.osakana.net/wp-content/uploads/2026/07/5165378E-0ECE-4DB9-8205-3A97A8D69496-1536x134.png 1536w, https://blog.osakana.net/wp-content/uploads/2026/07/5165378E-0ECE-4DB9-8205-3A97A8D69496.png 1890w" sizes="auto, (max-width: 767px) 89vw, (max-width: 1000px) 54vw, (max-width: 1071px) 543px, 580px" /></a></figure>



<figure class="wp-block-image size-large"><a href="https://blog.osakana.net/wp-content/uploads/2026/07/DED67F3D-6705-4A30-926D-70427AA108D3.png"><img loading="lazy" decoding="async" width="1024" height="163" src="https://blog.osakana.net/wp-content/uploads/2026/07/DED67F3D-6705-4A30-926D-70427AA108D3-1024x163.png" alt="" class="wp-image-17454" srcset="https://blog.osakana.net/wp-content/uploads/2026/07/DED67F3D-6705-4A30-926D-70427AA108D3-1024x163.png 1024w, https://blog.osakana.net/wp-content/uploads/2026/07/DED67F3D-6705-4A30-926D-70427AA108D3-300x48.png 300w, https://blog.osakana.net/wp-content/uploads/2026/07/DED67F3D-6705-4A30-926D-70427AA108D3-768x122.png 768w, https://blog.osakana.net/wp-content/uploads/2026/07/DED67F3D-6705-4A30-926D-70427AA108D3-1536x244.png 1536w, https://blog.osakana.net/wp-content/uploads/2026/07/DED67F3D-6705-4A30-926D-70427AA108D3.png 1901w" sizes="auto, (max-width: 767px) 89vw, (max-width: 1000px) 54vw, (max-width: 1071px) 543px, 580px" /></a></figure>



<p class="wp-block-paragraph">AHV Hypervisor el8.nutanix.20230302.101026 → <mark style="background-color:rgba(0, 0, 0, 0)" class="has-inline-color has-vivid-red-color">el8.nutanix.20230302.103053 </mark><br>AOS: 6.8.1 → <mark style="background-color:rgba(0, 0, 0, 0)" class="has-inline-color has-vivid-red-color">6.10.1.14</mark><br>FSM: 5.0.0.1 → <mark style="background-color:rgba(0, 0, 0, 0)" class="has-inline-color has-vivid-red-color">5.3.0.1</mark><br>Foundation 5.6.1 → <mark style="background-color:rgba(0, 0, 0, 0)" class="has-inline-color has-vivid-red-color">5.10.4</mark><br>NCC 5.0.1 →<mark style="background-color:rgba(0, 0, 0, 0)" class="has-inline-color has-vivid-red-color"> 5.3.1.1</mark></p>



<figure class="wp-block-image size-large"><a href="https://blog.osakana.net/wp-content/uploads/2026/07/C229B79F-832D-4089-860D-2E6D07EA93F3.png"><img loading="lazy" decoding="async" width="1024" height="87" src="https://blog.osakana.net/wp-content/uploads/2026/07/C229B79F-832D-4089-860D-2E6D07EA93F3-1024x87.png" alt="" class="wp-image-17477" srcset="https://blog.osakana.net/wp-content/uploads/2026/07/C229B79F-832D-4089-860D-2E6D07EA93F3-1024x87.png 1024w, https://blog.osakana.net/wp-content/uploads/2026/07/C229B79F-832D-4089-860D-2E6D07EA93F3-300x25.png 300w, https://blog.osakana.net/wp-content/uploads/2026/07/C229B79F-832D-4089-860D-2E6D07EA93F3-768x65.png 768w, https://blog.osakana.net/wp-content/uploads/2026/07/C229B79F-832D-4089-860D-2E6D07EA93F3-1536x131.png 1536w, https://blog.osakana.net/wp-content/uploads/2026/07/C229B79F-832D-4089-860D-2E6D07EA93F3.png 1883w" sizes="auto, (max-width: 767px) 89vw, (max-width: 1000px) 54vw, (max-width: 1071px) 543px, 580px" /></a></figure>



<figure class="wp-block-image size-large"><a href="https://blog.osakana.net/wp-content/uploads/2026/07/05C6B782-8999-40FD-A38A-CCD651A692CA.png"><img loading="lazy" decoding="async" width="1024" height="75" src="https://blog.osakana.net/wp-content/uploads/2026/07/05C6B782-8999-40FD-A38A-CCD651A692CA-1024x75.png" alt="" class="wp-image-17479" srcset="https://blog.osakana.net/wp-content/uploads/2026/07/05C6B782-8999-40FD-A38A-CCD651A692CA-1024x75.png 1024w, https://blog.osakana.net/wp-content/uploads/2026/07/05C6B782-8999-40FD-A38A-CCD651A692CA-300x22.png 300w, https://blog.osakana.net/wp-content/uploads/2026/07/05C6B782-8999-40FD-A38A-CCD651A692CA-768x56.png 768w, https://blog.osakana.net/wp-content/uploads/2026/07/05C6B782-8999-40FD-A38A-CCD651A692CA-1536x112.png 1536w, https://blog.osakana.net/wp-content/uploads/2026/07/05C6B782-8999-40FD-A38A-CCD651A692CA.png 1886w" sizes="auto, (max-width: 767px) 89vw, (max-width: 1000px) 54vw, (max-width: 1071px) 543px, 580px" /></a></figure>



<p class="wp-block-paragraph">AHV Hypervisor el8.nutanix.20230302.101026 → el8.nutanix.20230302.103053 → <mark style="background-color:rgba(0, 0, 0, 0)" class="has-inline-color has-vivid-red-color">el8.nutanix.20230302.103087 </mark><br>AOS: 6.8.1 → 6.10.1.14 → <mark style="background-color:rgba(0, 0, 0, 0)" class="has-inline-color has-vivid-red-color">7.0.1.15</mark><br>FSM: 5.0.0.1 → 5.3.0.1<br>Foundation 5.6.1 → 5.10.4<br>NCC 5.0.1 → 5.3.1.1</p>



<figure class="wp-block-image size-large"><a href="https://blog.osakana.net/wp-content/uploads/2026/07/CE046D12-8E88-4E7E-8360-8BA43FFB99A1.png"><img loading="lazy" decoding="async" width="1024" height="79" src="https://blog.osakana.net/wp-content/uploads/2026/07/CE046D12-8E88-4E7E-8360-8BA43FFB99A1-1024x79.png" alt="" class="wp-image-17493" srcset="https://blog.osakana.net/wp-content/uploads/2026/07/CE046D12-8E88-4E7E-8360-8BA43FFB99A1-1024x79.png 1024w, https://blog.osakana.net/wp-content/uploads/2026/07/CE046D12-8E88-4E7E-8360-8BA43FFB99A1-300x23.png 300w, https://blog.osakana.net/wp-content/uploads/2026/07/CE046D12-8E88-4E7E-8360-8BA43FFB99A1-768x60.png 768w, https://blog.osakana.net/wp-content/uploads/2026/07/CE046D12-8E88-4E7E-8360-8BA43FFB99A1-1536x119.png 1536w, https://blog.osakana.net/wp-content/uploads/2026/07/CE046D12-8E88-4E7E-8360-8BA43FFB99A1.png 1896w" sizes="auto, (max-width: 767px) 89vw, (max-width: 1000px) 54vw, (max-width: 1071px) 543px, 580px" /></a></figure>



<figure class="wp-block-image size-large"><a href="https://blog.osakana.net/wp-content/uploads/2026/07/64106597-C088-4F0B-9F81-4F46E1C43732.png"><img loading="lazy" decoding="async" width="1024" height="126" src="https://blog.osakana.net/wp-content/uploads/2026/07/64106597-C088-4F0B-9F81-4F46E1C43732-1024x126.png" alt="" class="wp-image-17494" srcset="https://blog.osakana.net/wp-content/uploads/2026/07/64106597-C088-4F0B-9F81-4F46E1C43732-1024x126.png 1024w, https://blog.osakana.net/wp-content/uploads/2026/07/64106597-C088-4F0B-9F81-4F46E1C43732-300x37.png 300w, https://blog.osakana.net/wp-content/uploads/2026/07/64106597-C088-4F0B-9F81-4F46E1C43732-768x95.png 768w, https://blog.osakana.net/wp-content/uploads/2026/07/64106597-C088-4F0B-9F81-4F46E1C43732-1536x189.png 1536w, https://blog.osakana.net/wp-content/uploads/2026/07/64106597-C088-4F0B-9F81-4F46E1C43732.png 1897w" sizes="auto, (max-width: 767px) 89vw, (max-width: 1000px) 54vw, (max-width: 1071px) 543px, 580px" /></a></figure>



<p class="wp-block-paragraph">AHV Hypervisor el8.nutanix.20230302.101026 → el8.nutanix.20230302.103053 → el8.nutanix.20230302.103087 → <mark style="background-color:rgba(0, 0, 0, 0)" class="has-inline-color has-vivid-red-color">10.0.1.9</mark> → × 10.3.1.7<br>AOS: 6.8.1 → 6.10.1.14 → 7.0.1.15 <br>FSM: 5.0.0.1 → 5.3.0.1<br>Foundation 5.6.1 → 5.10.4<br>NCC 5.0.1 → 5.3.1.1</p>



<figure class="wp-block-image size-large"><a href="https://blog.osakana.net/wp-content/uploads/2026/07/C0E17139-0DBC-45C8-88F2-9601190BDF91.png"><img loading="lazy" decoding="async" width="1024" height="80" src="https://blog.osakana.net/wp-content/uploads/2026/07/C0E17139-0DBC-45C8-88F2-9601190BDF91-1024x80.png" alt="" class="wp-image-17514" srcset="https://blog.osakana.net/wp-content/uploads/2026/07/C0E17139-0DBC-45C8-88F2-9601190BDF91-1024x80.png 1024w, https://blog.osakana.net/wp-content/uploads/2026/07/C0E17139-0DBC-45C8-88F2-9601190BDF91-300x24.png 300w, https://blog.osakana.net/wp-content/uploads/2026/07/C0E17139-0DBC-45C8-88F2-9601190BDF91-768x60.png 768w, https://blog.osakana.net/wp-content/uploads/2026/07/C0E17139-0DBC-45C8-88F2-9601190BDF91-1536x120.png 1536w, https://blog.osakana.net/wp-content/uploads/2026/07/C0E17139-0DBC-45C8-88F2-9601190BDF91.png 1887w" sizes="auto, (max-width: 767px) 89vw, (max-width: 1000px) 54vw, (max-width: 1071px) 543px, 580px" /></a></figure>



<figure class="wp-block-image size-large"><a href="https://blog.osakana.net/wp-content/uploads/2026/07/0E1571F2-6847-43EA-B616-FE9CC49E977D.png"><img loading="lazy" decoding="async" width="1024" height="81" src="https://blog.osakana.net/wp-content/uploads/2026/07/0E1571F2-6847-43EA-B616-FE9CC49E977D-1024x81.png" alt="" class="wp-image-17516" srcset="https://blog.osakana.net/wp-content/uploads/2026/07/0E1571F2-6847-43EA-B616-FE9CC49E977D-1024x81.png 1024w, https://blog.osakana.net/wp-content/uploads/2026/07/0E1571F2-6847-43EA-B616-FE9CC49E977D-300x24.png 300w, https://blog.osakana.net/wp-content/uploads/2026/07/0E1571F2-6847-43EA-B616-FE9CC49E977D-768x60.png 768w, https://blog.osakana.net/wp-content/uploads/2026/07/0E1571F2-6847-43EA-B616-FE9CC49E977D-1536x121.png 1536w, https://blog.osakana.net/wp-content/uploads/2026/07/0E1571F2-6847-43EA-B616-FE9CC49E977D.png 1892w" sizes="auto, (max-width: 767px) 89vw, (max-width: 1000px) 54vw, (max-width: 1071px) 543px, 580px" /></a></figure>



<p class="wp-block-paragraph">AHV Hypervisor el8.nutanix.20230302.101026 → el8.nutanix.20230302.103053 → el8.nutanix.20230302.103087 → 10.0.1.9 → × 10.3.1.7<br>AOS: 6.8.1 → 6.10.1.14 → 7.0.1.15 → <mark style="background-color:rgba(0, 0, 0, 0)" class="has-inline-color has-vivid-red-color">7.3.1.9</mark><br>FSM: 5.0.0.1 → 5.3.0.1<br>Foundation 5.6.1 → 5.10.4<br>NCC 5.0.1 → 5.3.1.1</p>



<p class="wp-block-paragraph"></p>
]]></content:encoded>
					
					<wfw:commentRss>https://blog.osakana.net/archives/17402/feed</wfw:commentRss>
			<slash:comments>0</slash:comments>
		
		
			</item>
		<item>
		<title>ESXi 8.0 FreeでNVMe SSDの温度を確認する</title>
		<link>https://blog.osakana.net/archives/17400</link>
					<comments>https://blog.osakana.net/archives/17400#respond</comments>
		
		<dc:creator><![CDATA[osakanataro]]></dc:creator>
		<pubDate>Wed, 08 Jul 2026 11:26:02 +0000</pubDate>
				<category><![CDATA[VMware]]></category>
		<category><![CDATA[仮想化]]></category>
		<guid isPermaLink="false">https://blog.osakana.net/?p=17400</guid>

					<description><![CDATA[ESXi 8.0 Free環境で、NVMe SSDの温度が取得できるのかを確認してみた まず情報源は「Commands to Display S.M.A.R.T. Data for NVMe Devices in ESX &#8230; <p class="link-more"><a href="https://blog.osakana.net/archives/17400" class="more-link"><span class="screen-reader-text">"ESXi 8.0 FreeでNVMe SSDの温度を確認する" の</span>続きを読む</a></p>]]></description>
										<content:encoded><![CDATA[
<p class="wp-block-paragraph">ESXi 8.0 Free環境で、NVMe SSDの温度が取得できるのかを確認してみた</p>



<p class="wp-block-paragraph">まず情報源は「<a href="https://knowledge.broadcom.com/external/article/314303/commands-to-display-smart-data-for-nvme.html">Commands to Display S.M.A.R.T. Data for NVMe Devices in ESXi</a>」</p>



<p class="wp-block-paragraph">S.M.A.R.T.データの読み出しを行うコマンドがある、と</p>



<h2 class="wp-block-heading">NVMe系コマンド操作で情報取得する場合</h2>



<p class="wp-block-paragraph">まず、NVMeストレージの一覧を確認</p>


<div class="wp-block-syntaxhighlighter-code "><pre class="brush: bash; title: ; notranslate">
&#x5B;root@esxi:~] esxcli nvme device list
HBA Name  Status  Signature
--------  ------  ---------
vmhba1    Online  nvmeMgmt-nvmhba0
vmhba0    Online  nvmeMgmt-nvmhba1
&#x5B;root@esxi:~]
</pre></div>


<p class="wp-block-paragraph">この環境には２つのNVMe SSDがあるので、２個表示される</p>



<p class="wp-block-paragraph">１個目を確認</p>


<div class="wp-block-syntaxhighlighter-code "><pre class="brush: bash; title: ; notranslate">
&#x5B;root@esxi:~] esxcli nvme device log smart get -A vmhba0
SMART And Health Info:
   Available Spare Space Below Threshold: false
   Temperature Warning: false
   NVM Subsystem Reliability Degradation: false
   Read Only Mode: false
   Volatile Memory Backup Device Failure: false
   Composite Temperature: 318 K
   Available Spare: 100 %
   Available Spare Threshold: 10 %
   Percentage Used: 0 %
   Data Units Read: 0x281ea0
   Data Units Written: 0x27e613
   Host Read Commands: 0x145c04f
   Host Write Commands: 0x161ca45
   Controller Busy Time: 0xa37
   Power Cycles: 0xb4
   Power On Hours: 0x608
   Unsafe Shutdowns: 0xf
   Media Errors: 0x0
   Number of Error Info Log Entries: 0x0
   Warning Composite Temperature Time: 12 Mins
   Critical Composite Temperature Time: 1001 Mins
   Temperature Sensor 1: 0 K
   Temperature Sensor 2: 0 K
   Temperature Sensor 3: 0 K
   Temperature Sensor 4: 0 K
   Temperature Sensor 5: 0 K
   Temperature Sensor 6: 0 K
   Temperature Sensor 7: 0 K
   Temperature Sensor 8: 0 K
&#x5B;root@esxi:~]
</pre></div>


<p class="wp-block-paragraph">Composite Temperatureの値はあるが、Temperature Sensorの値が全部なし</p>



<p class="wp-block-paragraph">これは、怪しいメーカ製のNVMe SSD(TWSC TSC1BN2562DF7T10A)であることに由来していると思われる</p>



<p class="wp-block-paragraph">じゃあ、２個目(SPD SP7002D2TNGH)は？</p>


<div class="wp-block-syntaxhighlighter-code "><pre class="brush: bash; title: ; notranslate">
&#x5B;root@esxi:~] esxcli nvme device log smart get -A vmhba1
SMART And Health Info:
   Available Spare Space Below Threshold: false
   Temperature Warning: false
   NVM Subsystem Reliability Degradation: false
   Read Only Mode: false
   Volatile Memory Backup Device Failure: false
   Composite Temperature: 316 K
   Available Spare: 100 %
   Available Spare Threshold: 1 %
   Percentage Used: 1 %
   Data Units Read: 0x1c706ba
   Data Units Written: 0x2fd6fe3
   Host Read Commands: 0x21811d5a
   Host Write Commands: 0x2509be1b
   Controller Busy Time: 0x891
   Power Cycles: 0xc7
   Power On Hours: 0x6db
   Unsafe Shutdowns: 0x14
   Media Errors: 0x0
   Number of Error Info Log Entries: 0x1
   Warning Composite Temperature Time: 3522 Mins
   Critical Composite Temperature Time: 1912 Mins
   Temperature Sensor 1: 316 K
   Temperature Sensor 2: 308 K
   Temperature Sensor 3: 0 K
   Temperature Sensor 4: 0 K
   Temperature Sensor 5: 0 K
   Temperature Sensor 6: 0 K
   Temperature Sensor 7: 0 K
   Temperature Sensor 8: 0 K
&#x5B;root@esxi:~]
</pre></div>


<p class="wp-block-paragraph">こちらは２個のセンサーが設定されていた</p>



<h2 class="wp-block-heading">ストレージ操作として情報を取得する場合</h2>



<p class="wp-block-paragraph">ストレージデバイス一覧を取得</p>


<div class="wp-block-syntaxhighlighter-code "><pre class="brush: bash; title: ; notranslate">
&#x5B;root@esxi:~] esxcli storage core device list
t10.NVMe____TWSC_TSC1BN2562DF7T10A___________________0000000000010000
   Display Name: Local NVMe Disk (t10.NVMe____TWSC_TSC1BN2562DF7T10A___________________0000000000010000)
   Has Settable Display Name: true
   Size: 244198
   Device Type: Direct-Access
   Multipath Plugin: HPP
   Devfs Path: /vmfs/devices/disks/t10.NVMe____TWSC_TSC1BN2562DF7T10A___________________0000000000010000
   Vendor: NVMe
   Model: TWSC TSC1BN256-F7T10A
   Revision: T1103N0L
   SCSI Level: 0
   Is Pseudo: false
   Status: on
   Is RDM Capable: false
   Is Local: true
   Is Removable: false
   Is SSD: true
   Is VVOL PE: false
   Is Offline: false
   Is Perennially Reserved: false
   Queue Full Sample Size: 0
   Queue Full Threshold: 0
   Thin Provisioning Status: no
   Attached Filters:
   VAAI Status: unsupported
   Other UIDs: vml.05382b44a545e29308c99c2e0ef990edeaa5ba7d16ef3c2ae03a9befc3814afd0d
   Is Shared Clusterwide: false
   Is SAS: false
   Is USB: false
   Is Boot Device: true
   Device Max Queue Depth: 255
   No of outstanding IOs with competing worlds: 32
   Drive Type: physical
   RAID Level: NA
   Number of Physical Drives: 1
   Protection Enabled: false
   PI Activated: false
   PI Type: 0
   PI Protection Mask: NO PROTECTION
   Supported Guard Types: NO GUARD SUPPORT
   DIX Enabled: false
   DIX Guard Type: NO GUARD SUPPORT
   Emulated DIX/DIF Enabled: false

t10.NVMe____SPD_SP7002D2TNGH_________________________0200000000000000
   Display Name: Local NVMe Disk (t10.NVMe____SPD_SP7002D2TNGH_________________________0200000000000000)
   Has Settable Display Name: true
   Size: 1953514
   Device Type: Direct-Access
   Multipath Plugin: HPP
   Devfs Path: /vmfs/devices/disks/t10.NVMe____SPD_SP7002D2TNGH_________________________0200000000000000
   Vendor: NVMe
   Model: SPD SP700-2TNGH
   Revision: SP02203A
   SCSI Level: 0
   Is Pseudo: false
   Status: on
   Is RDM Capable: false
   Is Local: true
   Is Removable: false
   Is SSD: true
   Is VVOL PE: false
   Is Offline: false
   Is Perennially Reserved: false
   Queue Full Sample Size: 0
   Queue Full Threshold: 0
   Thin Provisioning Status: no
   Attached Filters:
   VAAI Status: unsupported
   Other UIDs: vml.05c56298c6cae09f64ef49957d1d7af93c98b2a5792c87d191b47f87ea5b89f9e2
   Is Shared Clusterwide: false
   Is SAS: false
   Is USB: false
   Is Boot Device: false
   Device Max Queue Depth: 1023
   No of outstanding IOs with competing worlds: 32
   Drive Type: physical
   RAID Level: NA
   Number of Physical Drives: 1
   Protection Enabled: false
   PI Activated: false
   PI Type: 0
   PI Protection Mask: NO PROTECTION
   Supported Guard Types: NO GUARD SUPPORT
   DIX Enabled: false
   DIX Guard Type: NO GUARD SUPPORT
   Emulated DIX/DIF Enabled: false
&#x5B;root@esxi:~]
</pre></div>


<p class="wp-block-paragraph">各デバイスのS.M.A.R.T情報を取得</p>


<div class="wp-block-syntaxhighlighter-code "><pre class="brush: bash; title: ; notranslate">
&#x5B;root@esxi:~] esxcli storage core device smart get -d t10.NVMe____TWSC_TSC1BN256
2DF7T10A___________________0000000000010000
Parameter                 Value  Threshold  Worst  Raw
------------------------  -----  ---------  -----  ---
Health Status             OK     N/A        N/A    N/A
Power-on Hours            1544   N/A        N/A    N/A
Power Cycle Count         180    N/A        N/A    N/A
Reallocated Sector Count  0      90         N/A    N/A
Drive Temperature         43     83         N/A    N/A
&#x5B;root@esxi:~] esxcli storage core device smart get -d t10.NVMe____SPD_SP7002D2TN
GH_________________________0200000000000000
Parameter                 Value  Threshold  Worst  Raw
------------------------  -----  ---------  -----  ---
Health Status             OK     N/A        N/A    N/A
Power-on Hours            1755   N/A        N/A    N/A
Power Cycle Count         199    N/A        N/A    N/A
Reallocated Sector Count  0      99         N/A    N/A
Drive Temperature         43     90         N/A    N/A
&#x5B;root@esxi:~]
</pre></div>


<p class="wp-block-paragraph">「Drive Temperature」に温度は入っている</p>



<h2 class="wp-block-heading">検証</h2>



<p class="wp-block-paragraph">ここまではNVMe SSDのヒートシンクに向けて冷却ファンが稼働している状態で実行していた</p>



<p class="wp-block-paragraph">冷却ファンを止めて温度上昇が発生するのかを検証</p>


<div class="wp-block-syntaxhighlighter-code "><pre class="brush: bash; title: ; notranslate">
&#x5B;root@esxi:~] esxcli nvme device log smart get -A vmhba0
SMART And Health Info:
   Available Spare Space Below Threshold: false
   Temperature Warning: false
   NVM Subsystem Reliability Degradation: false
   Read Only Mode: false
   Volatile Memory Backup Device Failure: false
   Composite Temperature: 324 K
   Available Spare: 100 %
   Available Spare Threshold: 10 %
   Percentage Used: 0 %
   Data Units Read: 0x281fc3
   Data Units Written: 0x27e69c
   Host Read Commands: 0x145f45c
   Host Write Commands: 0x16201bc
   Controller Busy Time: 0xa38
   Power Cycles: 0xb4
   Power On Hours: 0x60a
   Unsafe Shutdowns: 0xf
   Media Errors: 0x0
   Number of Error Info Log Entries: 0x0
   Warning Composite Temperature Time: 12 Mins
   Critical Composite Temperature Time: 1001 Mins
   Temperature Sensor 1: 0 K
   Temperature Sensor 2: 0 K
   Temperature Sensor 3: 0 K
   Temperature Sensor 4: 0 K
   Temperature Sensor 5: 0 K
   Temperature Sensor 6: 0 K
   Temperature Sensor 7: 0 K
   Temperature Sensor 8: 0 K
&#x5B;root@esxi:~] esxcli storage core device smart get -d t10.NVMe____TWSC_TSC1BN256
2DF7T10A___________________0000000000010000
Parameter                 Value  Threshold  Worst  Raw
------------------------  -----  ---------  -----  ---
Health Status             OK     N/A        N/A    N/A
Power-on Hours            1546   N/A        N/A    N/A
Power Cycle Count         180    N/A        N/A    N/A
Reallocated Sector Count  0      90         N/A    N/A
Drive Temperature         52     83         N/A    N/A
&#x5B;root@esxi:~] esxcli nvme device log smart get -A vmhba1
SMART And Health Info:
   Available Spare Space Below Threshold: false
   Temperature Warning: false
   NVM Subsystem Reliability Degradation: false
   Read Only Mode: false
   Volatile Memory Backup Device Failure: false
   Composite Temperature: 317 K
   Available Spare: 100 %
   Available Spare Threshold: 1 %
   Percentage Used: 1 %
   Data Units Read: 0x1c71334
   Data Units Written: 0x2fd767a
   Host Read Commands: 0x2181e209
   Host Write Commands: 0x250ab10d
   Controller Busy Time: 0x891
   Power Cycles: 0xc7
   Power On Hours: 0x6dd
   Unsafe Shutdowns: 0x14
   Media Errors: 0x0
   Number of Error Info Log Entries: 0x1
   Warning Composite Temperature Time: 3522 Mins
   Critical Composite Temperature Time: 1912 Mins
   Temperature Sensor 1: 317 K
   Temperature Sensor 2: 319 K
   Temperature Sensor 3: 0 K
   Temperature Sensor 4: 0 K
   Temperature Sensor 5: 0 K
   Temperature Sensor 6: 0 K
   Temperature Sensor 7: 0 K
   Temperature Sensor 8: 0 K
&#x5B;root@esxi:~] esxcli storage core device smart get -d t10.NVMe____SPD_SP7002D2TN
GH_________________________0200000000000000
Parameter                 Value  Threshold  Worst  Raw
------------------------  -----  ---------  -----  ---
Health Status             OK     N/A        N/A    N/A
Power-on Hours            1757   N/A        N/A    N/A
Power Cycle Count         199    N/A        N/A    N/A
Reallocated Sector Count  0      99         N/A    N/A
Drive Temperature         44     90         N/A    N/A
&#x5B;root@esxi:~]
</pre></div>


<p class="wp-block-paragraph">2時間後</p>


<div class="wp-block-syntaxhighlighter-code "><pre class="brush: bash; title: ; notranslate">
&#x5B;root@esxi:~] esxcli storage core device smart get -d t10.NVMe____TWSC_TSC1BN256
2DF7T10A___________________0000000000010000
Parameter                 Value  Threshold  Worst  Raw
------------------------  -----  ---------  -----  ---
Health Status             OK     N/A        N/A    N/A
Power-on Hours            1547   N/A        N/A    N/A
Power Cycle Count         180    N/A        N/A    N/A
Reallocated Sector Count  0      90         N/A    N/A
Drive Temperature         54     83         N/A    N/A
&#x5B;root@esxi:~] esxcli nvme device log smart get -A vmhba0
SMART And Health Info:
   Available Spare Space Below Threshold: false
   Temperature Warning: false
   NVM Subsystem Reliability Degradation: false
   Read Only Mode: false
   Volatile Memory Backup Device Failure: false
   Composite Temperature: 327 K
   Available Spare: 100 %
   Available Spare Threshold: 10 %
   Percentage Used: 0 %
   Data Units Read: 0x2820c9
   Data Units Written: 0x27e737
   Host Read Commands: 0x1461a66
   Host Write Commands: 0x1622f01
   Controller Busy Time: 0xa39
   Power Cycles: 0xb4
   Power On Hours: 0x60b
   Unsafe Shutdowns: 0xf
   Media Errors: 0x0
   Number of Error Info Log Entries: 0x0
   Warning Composite Temperature Time: 12 Mins
   Critical Composite Temperature Time: 1001 Mins
   Temperature Sensor 1: 0 K
   Temperature Sensor 2: 0 K
   Temperature Sensor 3: 0 K
   Temperature Sensor 4: 0 K
   Temperature Sensor 5: 0 K
   Temperature Sensor 6: 0 K
   Temperature Sensor 7: 0 K
   Temperature Sensor 8: 0 K
&#x5B;root@esxi:~] esxcli storage core device smart get -d t10.NVMe____TWSC_TSC1BN256
2DF7T10A___________________0000000000010000
Parameter                 Value  Threshold  Worst  Raw
------------------------  -----  ---------  -----  ---
Health Status             OK     N/A        N/A    N/A
Power-on Hours            1547   N/A        N/A    N/A
Power Cycle Count         180    N/A        N/A    N/A
Reallocated Sector Count  0      90         N/A    N/A
Drive Temperature         54     83         N/A    N/A
&#x5B;root@esxi:~] esxcli nvme device log smart get -A vmhba1
SMART And Health Info:
   Available Spare Space Below Threshold: false
   Temperature Warning: false
   NVM Subsystem Reliability Degradation: false
   Read Only Mode: false
   Volatile Memory Backup Device Failure: false
   Composite Temperature: 320 K
   Available Spare: 100 %
   Available Spare Threshold: 1 %
   Percentage Used: 1 %
   Data Units Read: 0x1c78f10
   Data Units Written: 0x30203c4
   Host Read Commands: 0x218425aa
   Host Write Commands: 0x2519b431
   Controller Busy Time: 0x892
   Power Cycles: 0xc7
   Power On Hours: 0x6df
   Unsafe Shutdowns: 0x14
   Media Errors: 0x0
   Number of Error Info Log Entries: 0x1
   Warning Composite Temperature Time: 3522 Mins
   Critical Composite Temperature Time: 1912 Mins
   Temperature Sensor 1: 320 K
   Temperature Sensor 2: 334 K
   Temperature Sensor 3: 0 K
   Temperature Sensor 4: 0 K
   Temperature Sensor 5: 0 K
   Temperature Sensor 6: 0 K
   Temperature Sensor 7: 0 K
   Temperature Sensor 8: 0 K
&#x5B;root@esxi:~] esxcli nvme device log smart get -A vmhba1
SMART And Health Info:
   Available Spare Space Below Threshold: false
   Temperature Warning: false
   NVM Subsystem Reliability Degradation: false
   Read Only Mode: false
   Volatile Memory Backup Device Failure: false
   Composite Temperature: 320 K
   Available Spare: 100 %
   Available Spare Threshold: 1 %
   Percentage Used: 1 %
   Data Units Read: 0x1c78f11
   Data Units Written: 0x3020450
   Host Read Commands: 0x218425f1
   Host Write Commands: 0x2519b834
   Controller Busy Time: 0x892
   Power Cycles: 0xc7
   Power On Hours: 0x6df
   Unsafe Shutdowns: 0x14
   Media Errors: 0x0
   Number of Error Info Log Entries: 0x1
   Warning Composite Temperature Time: 3522 Mins
   Critical Composite Temperature Time: 1912 Mins
   Temperature Sensor 1: 320 K
   Temperature Sensor 2: 332 K
   Temperature Sensor 3: 0 K
   Temperature Sensor 4: 0 K
   Temperature Sensor 5: 0 K
   Temperature Sensor 6: 0 K
   Temperature Sensor 7: 0 K
   Temperature Sensor 8: 0 K
&#x5B;root@esxi:~] esxcli storage core device smart get -d t10.NVMe____SPD_SP7002D2TN
GH_________________________0200000000000000
Parameter                 Value  Threshold  Worst  Raw
------------------------  -----  ---------  -----  ---
Health Status             OK     N/A        N/A    N/A
Power-on Hours            1759   N/A        N/A    N/A
Power Cycle Count         199    N/A        N/A    N/A
Reallocated Sector Count  0      99         N/A    N/A
Drive Temperature         47     90         N/A    N/A
&#x5B;root@esxi:~]
</pre></div>

<div class="wp-block-syntaxhighlighter-code "><pre class="brush: bash; title: ; notranslate">
&#x5B;root@esxi:~] esxcli nvme device log smart get -A vmhba0
SMART And Health Info:
   Available Spare Space Below Threshold: false
   Temperature Warning: false
   NVM Subsystem Reliability Degradation: false
   Read Only Mode: false
   Volatile Memory Backup Device Failure: false
   Composite Temperature: 327 K
   Available Spare: 100 %
   Available Spare Threshold: 10 %
   Percentage Used: 0 %
   Data Units Read: 0x28249f
   Data Units Written: 0x27eada
   Host Read Commands: 0x146b7f3
   Host Write Commands: 0x16305bb
   Controller Busy Time: 0xa3d
   Power Cycles: 0xb4
   Power On Hours: 0x611
   Unsafe Shutdowns: 0xf
   Media Errors: 0x0
   Number of Error Info Log Entries: 0x0
   Warning Composite Temperature Time: 12 Mins
   Critical Composite Temperature Time: 1001 Mins
   Temperature Sensor 1: 0 K
   Temperature Sensor 2: 0 K
   Temperature Sensor 3: 0 K
   Temperature Sensor 4: 0 K
   Temperature Sensor 5: 0 K
   Temperature Sensor 6: 0 K
   Temperature Sensor 7: 0 K
   Temperature Sensor 8: 0 K
&#x5B;root@esxi:~] esxcli storage core device smart get -d t10.NVMe____TWSC_TSC1BN256
2DF7T10A___________________0000000000010000
Parameter                 Value  Threshold  Worst  Raw
------------------------  -----  ---------  -----  ---
Health Status             OK     N/A        N/A    N/A
Power-on Hours            1553   N/A        N/A    N/A
Power Cycle Count         180    N/A        N/A    N/A
Reallocated Sector Count  0      90         N/A    N/A
Drive Temperature         54     83         N/A    N/A
&#x5B;root@esxi:~] esxcli nvme device log smart get -A vmhba1
SMART And Health Info:
   Available Spare Space Below Threshold: false
   Temperature Warning: false
   NVM Subsystem Reliability Degradation: false
   Read Only Mode: false
   Volatile Memory Backup Device Failure: false
   Composite Temperature: 321 K
   Available Spare: 100 %
   Available Spare Threshold: 1 %
   Percentage Used: 1 %
   Data Units Read: 0x1cb74d7
   Data Units Written: 0x309f82b
   Host Read Commands: 0x21a21851
   Host Write Commands: 0x2596bdff
   Controller Busy Time: 0x899
   Power Cycles: 0xc7
   Power On Hours: 0x6e5
   Unsafe Shutdowns: 0x14
   Media Errors: 0x0
   Number of Error Info Log Entries: 0x1
   Warning Composite Temperature Time: 3788 Mins
   Critical Composite Temperature Time: 1936 Mins
   Temperature Sensor 1: 321 K
   Temperature Sensor 2: 342 K
   Temperature Sensor 3: 0 K
   Temperature Sensor 4: 0 K
   Temperature Sensor 5: 0 K
   Temperature Sensor 6: 0 K
   Temperature Sensor 7: 0 K
   Temperature Sensor 8: 0 K
&#x5B;root@esxi:~] esxcli storage core device smart get -d t10.NVMe____SPD_SP7002D2TN
GH_________________________0200000000000000
Parameter                 Value  Threshold  Worst  Raw
------------------------  -----  ---------  -----  ---
Health Status             OK     N/A        N/A    N/A
Power-on Hours            1765   N/A        N/A    N/A
Power Cycle Count         199    N/A        N/A    N/A
Reallocated Sector Count  0      99         N/A    N/A
Drive Temperature         48     90         N/A    N/A
&#x5B;root@esxi:~]
</pre></div>


<figure class="wp-block-table"><table class="has-fixed-layout"><tbody><tr><td></td><td>TWSCのNVMe SSD</td><td>SPDのNVMe SSD</td></tr><tr><td>最初</td><td>318K / 43度</td><td>316K / 43度</td></tr><tr><td>1時間後</td><td>324K / 52度</td><td>317K / 44度</td></tr><tr><td>2時間後</td><td>327K / 54度</td><td>320K / 47度</td></tr><tr><td>4時間後</td><td>327K / 54度</td><td>321K / 48度</td></tr></tbody></table></figure>



<p class="wp-block-paragraph"></p>
]]></content:encoded>
					
					<wfw:commentRss>https://blog.osakana.net/archives/17400/feed</wfw:commentRss>
			<slash:comments>0</slash:comments>
		
		
			</item>
		<item>
		<title>ESXi 8.0 FreeでCIMサーバが起動しない</title>
		<link>https://blog.osakana.net/archives/17393</link>
					<comments>https://blog.osakana.net/archives/17393#respond</comments>
		
		<dc:creator><![CDATA[osakanataro]]></dc:creator>
		<pubDate>Wed, 08 Jul 2026 01:55:45 +0000</pubDate>
				<category><![CDATA[VMware]]></category>
		<category><![CDATA[仮想化]]></category>
		<guid isPermaLink="false">https://blog.osakana.net/?p=17393</guid>

					<description><![CDATA[ESXi 8.0 Free環境でCIMサーバ(sfcbd-watchdog)が起動していない コマンドでステータスを確認 手動で起動を試みる 起動に失敗する 検索すると「How to enable CIM Server  &#8230; <p class="link-more"><a href="https://blog.osakana.net/archives/17393" class="more-link"><span class="screen-reader-text">"ESXi 8.0 FreeでCIMサーバが起動しない" の</span>続きを読む</a></p>]]></description>
										<content:encoded><![CDATA[
<p class="wp-block-paragraph">ESXi 8.0 Free環境でCIMサーバ(sfcbd-watchdog)が起動していない</p>



<figure class="wp-block-image size-large"><a href="https://blog.osakana.net/wp-content/uploads/2026/07/F9819458-D888-41AF-A4F3-C906ACE5A7EB.png"><img loading="lazy" decoding="async" width="1024" height="293" src="https://blog.osakana.net/wp-content/uploads/2026/07/F9819458-D888-41AF-A4F3-C906ACE5A7EB-1024x293.png" alt="" class="wp-image-17394" srcset="https://blog.osakana.net/wp-content/uploads/2026/07/F9819458-D888-41AF-A4F3-C906ACE5A7EB-1024x293.png 1024w, https://blog.osakana.net/wp-content/uploads/2026/07/F9819458-D888-41AF-A4F3-C906ACE5A7EB-300x86.png 300w, https://blog.osakana.net/wp-content/uploads/2026/07/F9819458-D888-41AF-A4F3-C906ACE5A7EB-768x220.png 768w, https://blog.osakana.net/wp-content/uploads/2026/07/F9819458-D888-41AF-A4F3-C906ACE5A7EB-1536x440.png 1536w, https://blog.osakana.net/wp-content/uploads/2026/07/F9819458-D888-41AF-A4F3-C906ACE5A7EB.png 1659w" sizes="auto, (max-width: 767px) 89vw, (max-width: 1000px) 54vw, (max-width: 1071px) 543px, 580px" /></a></figure>



<p class="wp-block-paragraph">コマンドでステータスを確認</p>


<div class="wp-block-syntaxhighlighter-code "><pre class="brush: bash; title: ; notranslate">
&#x5B;root@esxi:~] /etc/init.d/sfcbd-watchdog status
sfcbd-init&#x5B;1052108]: args (&#039;status&#039;)
sfcbd-init&#x5B;1052108]: Getting Exclusive access, please wait...
sfcbd-init&#x5B;1052108]: Exclusive access granted.
sfcbd is not running
&#x5B;root@esxi:~]
</pre></div>


<p class="wp-block-paragraph">手動で起動を試みる</p>


<div class="wp-block-syntaxhighlighter-code "><pre class="brush: bash; title: ; notranslate">
&#x5B;root@esxi:~] /etc/init.d/sfcbd-watchdog start
sfcbd-init&#x5B;1052119]: args (&#039;start&#039;)
sfcbd-init&#x5B;1052119]: Getting Exclusive access, please wait...
sfcbd-init&#x5B;1052119]: Exclusive access granted.
sfcbd-init&#x5B;1052119]: Request to start sfcbd-watchdog, pid 1052119
sfcbd-init&#x5B;1052119]: sfcbd not started, administratively disabled.
&#x5B;root@esxi:~]
</pre></div>


<p class="wp-block-paragraph">起動に失敗する</p>



<p class="wp-block-paragraph">検索すると「<a href="https://www.claudiokuenzler.com/blog/1280/how-to-enable-cim-server-wbem-service-esxi-8">How to enable CIM Server (WBEM service) in ESXi 8</a>」という記事を発見</p>



<p class="wp-block-paragraph">wbemを有効化すると使えるようになるらしい</p>



<p class="wp-block-paragraph">まず、現状wbemがどうなっているかを確認</p>


<div class="wp-block-syntaxhighlighter-code "><pre class="brush: bash; title: ; notranslate">
&#x5B;root@esxi:~] esxcli system wbem get
   Enabled: false
   WS-Management Service: true
   Enable HTTPS: true
   Authorization Model: password
   Port: 5989
   HTTP Procs: 2
   HTTPS Procs: 4
   Provider Procs: 16
   Keepalive Timeout: 1
   Keepalive Max Requests: 10
   Provider Sample Interval: 30
   Provider Timeout Interval: 120
   HTTP Max Content Length: 1048576
   Max Message Length: 40000000
   Thread Stack Size: 1048576
   Provider Resource Pool Override:
   SSL Cipher List: ECDHE+AESGCM:ECDHE+AES
   Threadpool Size: 5
   Readonly: false
   Log Level: warning
   Service Location Protocol PID: 0
   WS-Management PID: 0
   CIM Object Manager PID: 0
   Enabled SSL Protocols:
   Enabled System SSL Protocols: tlsv1.2
   Enabled Running SSL Protocols:
&#x5B;root@esxi:~]
</pre></div>


<p class="wp-block-paragraph">「Enabled: false」なので無効状態だった</p>



<p class="wp-block-paragraph">「esxcli system wbem set -e true」を実行して有効化する</p>


<div class="wp-block-syntaxhighlighter-code "><pre class="brush: bash; title: ; notranslate">
&#x5B;root@esxi:~] esxcli system wbem set -e true
&#x5B;root@esxi:~] esxcli system wbem get
   Enabled: true
   WS-Management Service: true
   Enable HTTPS: true
   Authorization Model: password
   Port: 5989
   HTTP Procs: 2
   HTTPS Procs: 4
   Provider Procs: 16
   Keepalive Timeout: 1
   Keepalive Max Requests: 10
   Provider Sample Interval: 30
   Provider Timeout Interval: 120
   HTTP Max Content Length: 1048576
   Max Message Length: 40000000
   Thread Stack Size: 1048576
   Provider Resource Pool Override:
   SSL Cipher List: ECDHE+AESGCM:ECDHE+AES
   Threadpool Size: 5
   Readonly: false
   Log Level: warning
   Service Location Protocol PID: 1052207
   WS-Management PID: 1053086
   CIM Object Manager PID: 1053049
   Enabled SSL Protocols:
   Enabled System SSL Protocols: tlsv1.2
   Enabled Running SSL Protocols: tlsv1.2
&#x5B;root@esxi:~]
</pre></div>


<p class="wp-block-paragraph">で、CIMサーバの状態を確認</p>


<div class="wp-block-syntaxhighlighter-code "><pre class="brush: bash; title: ; notranslate">
&#x5B;root@esxi:~] /etc/init.d/sfcbd-watchdog status
sfcbd-init&#x5B;1053334]: args (&#039;status&#039;)
sfcbd-init&#x5B;1053334]: Getting Exclusive access, please wait...
sfcbd-init&#x5B;1053334]: Exclusive access granted.
sfcbd is running
&#x5B;root@esxi:~]
</pre></div>


<p class="wp-block-paragraph">勝手に起動していた</p>



<p class="wp-block-paragraph">Web UI上でも起動を確認した</p>



<figure class="wp-block-image size-large"><a href="https://blog.osakana.net/wp-content/uploads/2026/07/6B5592E4-7499-4B56-A067-5D371D102D43.png"><img loading="lazy" decoding="async" width="1024" height="272" src="https://blog.osakana.net/wp-content/uploads/2026/07/6B5592E4-7499-4B56-A067-5D371D102D43-1024x272.png" alt="" class="wp-image-17396" srcset="https://blog.osakana.net/wp-content/uploads/2026/07/6B5592E4-7499-4B56-A067-5D371D102D43-1024x272.png 1024w, https://blog.osakana.net/wp-content/uploads/2026/07/6B5592E4-7499-4B56-A067-5D371D102D43-300x80.png 300w, https://blog.osakana.net/wp-content/uploads/2026/07/6B5592E4-7499-4B56-A067-5D371D102D43-768x204.png 768w, https://blog.osakana.net/wp-content/uploads/2026/07/6B5592E4-7499-4B56-A067-5D371D102D43-1536x408.png 1536w, https://blog.osakana.net/wp-content/uploads/2026/07/6B5592E4-7499-4B56-A067-5D371D102D43.png 1647w" sizes="auto, (max-width: 767px) 89vw, (max-width: 1000px) 54vw, (max-width: 1071px) 543px, 580px" /></a></figure>



<p class="wp-block-paragraph">CIMサーバ稼働したので[ハードウェア]-[ストレージ]に情報が表示されるようになったけど、ストレージじゃないなぁ・・・</p>



<figure class="wp-block-image size-large"><a href="https://blog.osakana.net/wp-content/uploads/2026/07/40A7C854-A068-4198-A5F0-9124516FBF20.png"><img loading="lazy" decoding="async" width="1024" height="390" src="https://blog.osakana.net/wp-content/uploads/2026/07/40A7C854-A068-4198-A5F0-9124516FBF20-1024x390.png" alt="" class="wp-image-17397" srcset="https://blog.osakana.net/wp-content/uploads/2026/07/40A7C854-A068-4198-A5F0-9124516FBF20-1024x390.png 1024w, https://blog.osakana.net/wp-content/uploads/2026/07/40A7C854-A068-4198-A5F0-9124516FBF20-300x114.png 300w, https://blog.osakana.net/wp-content/uploads/2026/07/40A7C854-A068-4198-A5F0-9124516FBF20-768x292.png 768w, https://blog.osakana.net/wp-content/uploads/2026/07/40A7C854-A068-4198-A5F0-9124516FBF20-1536x585.png 1536w, https://blog.osakana.net/wp-content/uploads/2026/07/40A7C854-A068-4198-A5F0-9124516FBF20.png 1652w" sizes="auto, (max-width: 767px) 89vw, (max-width: 1000px) 54vw, (max-width: 1071px) 543px, 580px" /></a></figure>
]]></content:encoded>
					
					<wfw:commentRss>https://blog.osakana.net/archives/17393/feed</wfw:commentRss>
			<slash:comments>0</slash:comments>
		
		
			</item>
		<item>
		<title>AMD Zen系CPU温度をとれるAMD Zen4/Zen5 IPMI Thermal DriverをRyzen 5 3500UのESXi 8.0 Freeにインストールしてみた</title>
		<link>https://blog.osakana.net/archives/17386</link>
					<comments>https://blog.osakana.net/archives/17386#respond</comments>
		
		<dc:creator><![CDATA[osakanataro]]></dc:creator>
		<pubDate>Wed, 08 Jul 2026 01:09:28 +0000</pubDate>
				<category><![CDATA[AMD]]></category>
		<category><![CDATA[CPU]]></category>
		<category><![CDATA[VMware]]></category>
		<category><![CDATA[仮想化]]></category>
		<guid isPermaLink="false">https://blog.osakana.net/?p=17386</guid>

					<description><![CDATA[VMware Flingsを見ていたらAMD Zen4/Zen5 IPMI Thermal Driver なるものがあった 検索してみると「AMD Zen4/Zen5 IPMI Thermal Driver for ES &#8230; <p class="link-more"><a href="https://blog.osakana.net/archives/17386" class="more-link"><span class="screen-reader-text">"AMD Zen系CPU温度をとれるAMD Zen4/Zen5 IPMI Thermal DriverをRyzen 5 3500UのESXi 8.0 Freeにインストールしてみた" の</span>続きを読む</a></p>]]></description>
										<content:encoded><![CDATA[
<p class="wp-block-paragraph">VMware Flingsを見ていたらAMD Zen4/Zen5 IPMI Thermal Driver なるものがあった</p>



<p class="wp-block-paragraph">検索してみると「<a href="https://williamlam.com/2026/05/amd-zen4-zen5-ipmi-thermal-driver-for-esx-fling.html">AMD Zen4/Zen5 IPMI Thermal Driver for ESX Fling</a>」という記事を見つけた</p>



<p class="wp-block-paragraph">それによれば、Zen4/Zen5とかいてあるがZen3も対応しているらしい</p>



<p class="wp-block-paragraph">もしかしてZen+のRyzen 5 3500Uでも使えるのかな？と実験してみた</p>



<p class="wp-block-paragraph">実験した環境はGMKtec NucBox G10 mini (Ryzen 5 3500U)環境で、32GBメモリ2枚増設して使っている。</p>



<figure class="wp-block-image size-large"><a href="https://blog.osakana.net/wp-content/uploads/2026/07/AEFA1586-AFA3-4B84-BF48-D326E0B7B560.png"><img loading="lazy" decoding="async" width="1024" height="238" src="https://blog.osakana.net/wp-content/uploads/2026/07/AEFA1586-AFA3-4B84-BF48-D326E0B7B560-1024x238.png" alt="" class="wp-image-17390" srcset="https://blog.osakana.net/wp-content/uploads/2026/07/AEFA1586-AFA3-4B84-BF48-D326E0B7B560-1024x238.png 1024w, https://blog.osakana.net/wp-content/uploads/2026/07/AEFA1586-AFA3-4B84-BF48-D326E0B7B560-300x70.png 300w, https://blog.osakana.net/wp-content/uploads/2026/07/AEFA1586-AFA3-4B84-BF48-D326E0B7B560-768x178.png 768w, https://blog.osakana.net/wp-content/uploads/2026/07/AEFA1586-AFA3-4B84-BF48-D326E0B7B560-1536x357.png 1536w, https://blog.osakana.net/wp-content/uploads/2026/07/AEFA1586-AFA3-4B84-BF48-D326E0B7B560-2048x476.png 2048w" sizes="auto, (max-width: 767px) 89vw, (max-width: 1000px) 54vw, (max-width: 1071px) 543px, 580px" /></a></figure>



<p class="wp-block-paragraph">まず、導入前の状態は下記の様になにもデータがない</p>



<figure class="wp-block-image size-large"><a href="https://blog.osakana.net/wp-content/uploads/2026/07/ADBE92B6-1816-4C03-8AC2-25126DEE9433.png"><img loading="lazy" decoding="async" width="1024" height="245" src="https://blog.osakana.net/wp-content/uploads/2026/07/ADBE92B6-1816-4C03-8AC2-25126DEE9433-1024x245.png" alt="" class="wp-image-17387" srcset="https://blog.osakana.net/wp-content/uploads/2026/07/ADBE92B6-1816-4C03-8AC2-25126DEE9433-1024x245.png 1024w, https://blog.osakana.net/wp-content/uploads/2026/07/ADBE92B6-1816-4C03-8AC2-25126DEE9433-300x72.png 300w, https://blog.osakana.net/wp-content/uploads/2026/07/ADBE92B6-1816-4C03-8AC2-25126DEE9433-768x183.png 768w, https://blog.osakana.net/wp-content/uploads/2026/07/ADBE92B6-1816-4C03-8AC2-25126DEE9433-1536x367.png 1536w, https://blog.osakana.net/wp-content/uploads/2026/07/ADBE92B6-1816-4C03-8AC2-25126DEE9433-2048x489.png 2048w" sizes="auto, (max-width: 767px) 89vw, (max-width: 1000px) 54vw, (max-width: 1071px) 543px, 580px" /></a></figure>



<p class="wp-block-paragraph"></p>



<p class="wp-block-paragraph">Flingsからダウンロードしたドライバzipファイルをローカルデータストア上に配置</p>


<div class="wp-block-syntaxhighlighter-code "><pre class="brush: bash; title: ; notranslate">
&#x5B;root@esxi:/vmfs/volumes/~/iso] ls -l /vmfs/volumes/~/iso/VMware-amd-zen-ipmi_thermal_910.1.0.0006-5vmw.803.0.0.24022510.zip
-rw-r--r--    1 root     root         23355 Jul  8 00:32 /vmfs/volumes/~/iso/VMware-amd-zen-ipmi_thermal_910.1.0.0006-5vmw.803.0.0.24022510.zip
&#x5B;root@esxi:/vmfs/volumes/~/iso]
</pre></div>


<p class="wp-block-paragraph">ドライバのインストール</p>


<div class="wp-block-syntaxhighlighter-code "><pre class="brush: bash; title: ; notranslate">
&#x5B;root@esxi:/vmfs/volumes/~/iso] esxcli softwar
e component apply -d /vmfs/volumes/~/iso/VMwar
e-amd-zen-ipmi_thermal_910.1.0.0006-5vmw.803.0.0.24022510.zip
Installation Result
   Message: The update completed successfully, but the system needs to be rebooted for the changes to be effective.
   Components Installed: VMware-smntemp_910.1.0.0006-5vmw.803.0.0.24022510
   Components Removed:
   Components Skipped:
   Reboot Required: true
   DPU Results:
&#x5B;root@esxi:/vmfs/volumes/~/iso]
</pre></div>


<p class="wp-block-paragraph">ドライバインストール後はESXi再起動必須</p>



<p class="wp-block-paragraph">再起動後、ステータスを確認すると、CPU温度を認識するようになった</p>



<figure class="wp-block-image size-large"><a href="https://blog.osakana.net/wp-content/uploads/2026/07/A8EB098F-7078-4623-9F9D-949671BE819E.png"><img loading="lazy" decoding="async" width="1024" height="188" src="https://blog.osakana.net/wp-content/uploads/2026/07/A8EB098F-7078-4623-9F9D-949671BE819E-1024x188.png" alt="" class="wp-image-17389" srcset="https://blog.osakana.net/wp-content/uploads/2026/07/A8EB098F-7078-4623-9F9D-949671BE819E-1024x188.png 1024w, https://blog.osakana.net/wp-content/uploads/2026/07/A8EB098F-7078-4623-9F9D-949671BE819E-300x55.png 300w, https://blog.osakana.net/wp-content/uploads/2026/07/A8EB098F-7078-4623-9F9D-949671BE819E-768x141.png 768w, https://blog.osakana.net/wp-content/uploads/2026/07/A8EB098F-7078-4623-9F9D-949671BE819E-1536x282.png 1536w, https://blog.osakana.net/wp-content/uploads/2026/07/A8EB098F-7078-4623-9F9D-949671BE819E-2048x375.png 2048w" sizes="auto, (max-width: 767px) 89vw, (max-width: 1000px) 54vw, (max-width: 1071px) 543px, 580px" /></a></figure>



<p class="wp-block-paragraph">CLIでも認識するようになった</p>


<div class="wp-block-syntaxhighlighter-code "><pre class="brush: bash; title: ; notranslate">
&#x5B;root@esxi:~] esxcli hardware ipmi sdr list
Node-Sensor  Description            Entity-Instance  Computed Reading  Base Unit  Raw Reading  Sensor Type  Timestamp/Comment    Raw  Formatted-Raw
-----------  ---------------------  ---------------  ----------------  ---------  -----------  -----------  -------------------  ---  -------------
0.1          Processor 1 CPU0_Tctl  3.1              59                degrees C  59           Temperature  2026-07-08T00:56:20
&#x5B;root@esxi:~]
</pre></div>


<p class="wp-block-paragraph">元記事ではドライバインストール後に標準では /etc/vmware/default.map.d/smntemp_extra.map ファイルを新規作成して、認識できるようにする必要がある、的な記載があるけどしなくても見れるなぁ・・・</p>



<p class="wp-block-paragraph">Ryzen 5 3500Uについては /etc/vmware/default.map.d/smntemp.map の方に情報あり、と</p>


<div class="wp-block-syntaxhighlighter-code "><pre class="brush: bash; title: ; notranslate">
&#x5B;root@esxi:~] lspci -v | grep -A2 &#039;0000:00:18.3&#039;
0000:00:18.3 Bridge Host bridge: Advanced Micro Devices, Inc. &#x5B;AMD] Raven/Raven2 Device 24: Function 3
         Class 0600: 1022:15eb

&#x5B;root@esxi:~] cat /etc/vmware/default.map.d/smntemp.map|grep 15eb
regtype=native,bus=pci,id=102215eb..............,driver=smntemp
&#x5B;root@esxi:~]
</pre></div>


<p class="wp-block-paragraph">どうやら、元記事は1.0.0005時代で、今回インストールしたのは AMD Zen4/Zen5 IPMI Thermal Driver for ESX 1.0.0006 なので、そこの違いである模様</p>
]]></content:encoded>
					
					<wfw:commentRss>https://blog.osakana.net/archives/17386/feed</wfw:commentRss>
			<slash:comments>0</slash:comments>
		
		
			</item>
		<item>
		<title>SPAM対応メモ 2026/06/24</title>
		<link>https://blog.osakana.net/archives/17340</link>
					<comments>https://blog.osakana.net/archives/17340#respond</comments>
		
		<dc:creator><![CDATA[osakanataro]]></dc:creator>
		<pubDate>Wed, 24 Jun 2026 04:30:30 +0000</pubDate>
				<category><![CDATA[iredmail]]></category>
		<category><![CDATA[サービスや仕組み]]></category>
		<category><![CDATA[トラブル話]]></category>
		<category><![CDATA[メール]]></category>
		<category><![CDATA[雑談]]></category>
		<guid isPermaLink="false">https://blog.osakana.net/?p=17340</guid>

					<description><![CDATA[メールサーバに新しいメールが入ってこない、というので調査したら、特定ユーザのメールパスワードがばれていてSPAM送信に使われていたという時のメモ (1) 落ちてるデーモンはいなかった を実行した際に止まっているものはいな &#8230; <p class="link-more"><a href="https://blog.osakana.net/archives/17340" class="more-link"><span class="screen-reader-text">"SPAM対応メモ 2026/06/24" の</span>続きを読む</a></p>]]></description>
										<content:encoded><![CDATA[
<p class="wp-block-paragraph">メールサーバに新しいメールが入ってこない、というので調査したら、特定ユーザのメールパスワードがばれていてSPAM送信に使われていたという時のメモ</p>



<h2 class="wp-block-heading">(1) 落ちてるデーモンはいなかった</h2>


<div class="wp-block-syntaxhighlighter-code "><pre class="brush: plain; title: ; notranslate">
systemctl --failed
</pre></div>


<p class="wp-block-paragraph">を実行した際に止まっているものはいなかった</p>



<h2 class="wp-block-heading">(2) メールのキューに異常</h2>



<p class="wp-block-paragraph">postfixのメールキューの状態を確認</p>


<div class="wp-block-syntaxhighlighter-code "><pre class="brush: plain; title: ; notranslate">
# postqueue -p
</pre></div>


<p class="wp-block-paragraph">数万通のメールが滞留していた</p>



<p class="wp-block-paragraph">差出人はほぼ1ユーザで、宛先は方々にわたる</p>



<h2 class="wp-block-heading">(3) メール配送停止</h2>



<p class="wp-block-paragraph">ひとまず、postfixのメール配送処理を止める</p>


<div class="wp-block-syntaxhighlighter-code "><pre class="brush: plain; title: ; notranslate">
# postfix abort
</pre></div>


<h2 class="wp-block-heading">(4) ログ確認</h2>



<p class="wp-block-paragraph">/var/log/messagesと/var/log/maillog に対して そのユーザ名でgrepをかけて確認</p>



<p class="wp-block-paragraph">roudcubeのログにて、roundcube内から多数のメールアドレスを指定してメール送信していることを確認</p>



<h2 class="wp-block-heading">(5) アクセス者IPアドレス確認</h2>



<p class="wp-block-paragraph">ログから該当する操作のIPアドレスを確認し、そのアドレスがどこなのかを確認</p>



<p class="wp-block-paragraph">今回は3IPアドレスからきており、どれも海外</p>



<h2 class="wp-block-heading">(6) あからさまにSPAMを削除</h2>



<p class="wp-block-paragraph">今回特定の時間帯の送信は全部SPAMっぽかったので以下のコマンドで該当ユーザのメールをpostsuper -d queueIDで削除</p>


<div class="wp-block-syntaxhighlighter-code "><pre class="brush: plain; title: ; notranslate">
# for queid in `postqueue -p|grep &quot;Jun 24 04&quot;  |grep ユーザ名|awk &#039;{ print $1 }&#039; | sed s/\*//ig`; do postsuper -d $queid; done
</pre></div>


<p class="wp-block-paragraph">あと、MAILER-DAEMON関連の返送処理も削除</p>


<div class="wp-block-syntaxhighlighter-code "><pre class="brush: plain; title: ; notranslate">
# for queid in `postqueue -p|grep MAILER|awk &#039;{ print $1 }&#039; | sed s/\*//ig`; do postsuper -d $queid; done
</pre></div>


<h2 class="wp-block-heading">(7) とりあえず再開</h2>



<hr class="wp-block-separator has-alpha-channel-opacity"/>



<p class="wp-block-paragraph">2026/07/21追記</p>



<h2 class="wp-block-heading">外部への影響報告</h2>



<h2 class="wp-block-heading">gmailサーバでのメール受信拒否</h2>



<p class="wp-block-paragraph">gmailサーバからメールの受け取り拒否を食らっていました<br>　<a href="https://support.google.com/a/answer/172179">https://support.google.com/a/answer/172179</a></p>



<p class="wp-block-paragraph">期間は2026/06/23 23:02～2026/07/19ぐらい？(2026/07/21 09:00には問題なかった)</p>



<p class="wp-block-paragraph">SPFやDMARCなどの設定は正確に実施されているにもかかわらず、gmail側は設定に不備があるから拒否、と言い張る状態でした。</p>



<p class="wp-block-paragraph">おそらくIPアドレスが同じ場合は、約30日経過しないと許可しないようです・・・</p>



<h2 class="wp-block-heading">各SPAMレポートサーバでの登録</h2>



<p class="wp-block-paragraph">いくつかのサービスで登録はされましたが、３日程度で削除されていました。</p>



<p class="wp-block-paragraph"><a href="https://www.spamcop.net/bl.shtml">spamcop</a><br><a href="http://www.gbudb.com/truncate/">GBUdb.com</a><br><a href="http://ipadmin.junkemailfilter.com/">junkmailfilter.com</a><br><a href="https://www.zedsd.net/blacklist.php">https://www.zedsd.net/blacklist.php</a></p>



<h2 class="wp-block-heading">2日程度のメール受信拒否を食らったところ</h2>



<p class="wp-block-paragraph">2日程度でSPAM扱いでメール受信拒否を食らったメッセージが帰ってきたところはこんな感じです</p>



<p class="wp-block-paragraph">意外だったのは、outlook.com 系から受信拒否を食らってなかったことです</p>



<p class="wp-block-paragraph">hostingシステム系からのエラー<br>・<a href="https://abuse.vadesecure.com/">https://abuse.vadesecure.com/</a><br>・<a href="https://www.strato-hosting.co.uk/faq/product/why-are-my-emails-not-being-delivered">https://www.strato-hosting.co.uk/faq/product/why-are-my-emails-not-being-delivered</a></p>



<p class="wp-block-paragraph">Apple icloud.comからのエラー<br>　<a href="https://support.apple.com/en-us/102322">https://support.apple.com/en-us/102322</a><br><br></p>
]]></content:encoded>
					
					<wfw:commentRss>https://blog.osakana.net/archives/17340/feed</wfw:commentRss>
			<slash:comments>0</slash:comments>
		
		
			</item>
		<item>
		<title>ONTAPシミュレータのaggregateが見えなくなった</title>
		<link>https://blog.osakana.net/archives/17280</link>
					<comments>https://blog.osakana.net/archives/17280#respond</comments>
		
		<dc:creator><![CDATA[osakanataro]]></dc:creator>
		<pubDate>Tue, 19 May 2026 05:58:07 +0000</pubDate>
				<category><![CDATA[NetApp]]></category>
		<category><![CDATA[ストレージ]]></category>
		<guid isPermaLink="false">https://blog.osakana.net/?p=17280</guid>

					<description><![CDATA[ESXi上に構築したONTAP シミュレータで データ用のaggregateにあるvolumeが見えなくなった 確認したところ、aggregateの状態が「restricted」となっていた とりあえずonlineできる &#8230; <p class="link-more"><a href="https://blog.osakana.net/archives/17280" class="more-link"><span class="screen-reader-text">"ONTAPシミュレータのaggregateが見えなくなった" の</span>続きを読む</a></p>]]></description>
										<content:encoded><![CDATA[
<p class="wp-block-paragraph">ESXi上に構築したONTAP シミュレータで データ用のaggregateにあるvolumeが見えなくなった</p>



<p class="wp-block-paragraph">確認したところ、aggregateの状態が「restricted」となっていた</p>


<div class="wp-block-syntaxhighlighter-code "><pre class="brush: bash; title: ; notranslate">
netapp::&gt; storage aggregate show


Aggregate     Size Available Used% State   #Vols  Nodes            RAID Status
--------- -------- --------- ----- ------- ------ ---------------- ------------
aggr0_netapp_01
           30.06GB    9.46GB   69% online       1 netapp-01        raid_dp,
                                                                   normal
netappSSD       0B        0B    0% restricted   0 netapp-01        raid_dp,
                                                                   normal
2 entries were displayed.

netapp::&gt;
</pre></div>


<p class="wp-block-paragraph">とりあえずonlineできるか確認してみる</p>


<div class="wp-block-syntaxhighlighter-code "><pre class="brush: bash; title: ; notranslate">
netapp::&gt; storage aggregate online -aggregate netappSSD

Error: command failed: Failed to bring aggregate &quot;netappSSD&quot; online. Reason: Neither fsinfo block of aggregate
       &#039;netappSSD&#039; is valid.

netapp::&gt;
</pre></div>


<p class="wp-block-paragraph">オンラインにできない状態であった</p>



<p class="wp-block-paragraph">エラーの事例を調べると、wafliron で処理をしてみて、ダメだったら、WAFLで問題おきてて、解決方法がないので、バックアップからリストアしろ、とのこと</p>



<p class="wp-block-paragraph">storage aggregate wafliron のコマンドを使えるように diagモードとして、状態を確認</p>


<div class="wp-block-syntaxhighlighter-code "><pre class="brush: bash; title: ; notranslate">
netapp::&gt; set diag

Warning: These diagnostic commands are for use by NetApp personnel only.
Do you want to continue? {y|n}: y

netapp::*&gt; storage aggregate wafliron show
This table is currently empty.

netapp::*&gt;
</pre></div>


<p class="wp-block-paragraph">wafliron startを実行</p>


<div class="wp-block-syntaxhighlighter-code "><pre class="brush: bash; title: ; notranslate">
netapp::*&gt; storage aggregate wafliron start -aggregate netappSSD

Warning: Aggregate netappSSD is in state &quot;restricted&quot;. This aggregate might contain one or more SnapMirror
         destination volumes. You have chosen to skip wafliron on the SnapMirror destination volumes. Do you still
         want to continue? {y|n}: y
Initiated wafliron-start on aggregate &quot;netappSSD&quot;.
Monitor the status with the &quot;storage aggregate wafliron show&quot; command.


netapp::*&gt;
</pre></div>


<p class="wp-block-paragraph">開始はされるが、すぐにエラー終了していた</p>


<div class="wp-block-syntaxhighlighter-code "><pre class="brush: bash; title: ; notranslate">
netapp::*&gt; storage aggregate wafliron show
                                                Percent
                                        Percent Summary  Last Last Start
                                         Blocks  Blocks Start Related
Aggregate      State   Current Status   Scanned Scanned Errno Information
-------------- ------- ---------------- ------- ------- ----- ----------------
netappSSD      restricted
                       not_running            -       -   138 Neither fsinfo
                                                              block of
                                                              aggregate
                                                              &#039;netappSSD&#039; is
                                                              valid.

netapp::*&gt;
</pre></div>


<p class="wp-block-paragraph">aggregate showで状態を確認</p>


<div class="wp-block-syntaxhighlighter-code "><pre class="brush: bash; title: ; notranslate">
netapp::*&gt; storage aggregate show


Aggregate     Size Available Used% State   #Vols  Nodes            RAID Status
--------- -------- --------- ----- ------- ------ ---------------- ------------
aggr0_netapp_01
           30.06GB    9.95GB   67% online       1 netapp-01        raid_dp,
                                                                   normal
netappSSD       0B        0B    0% restricted   0 netapp-01        raid_dp,
                                                                   normal
2 entries were displayed.

netapp::*&gt;
</pre></div>


<p class="wp-block-paragraph">onlineを実行したが、状況に変化はなし</p>


<div class="wp-block-syntaxhighlighter-code "><pre class="brush: bash; title: ; notranslate">
netapp::*&gt; storage aggregate online -aggregate netappSSD

Error: command failed: Failed to bring aggregate &quot;netappSSD&quot; online. Reason: Neither fsinfo block of aggregate
       &#039;netappSSD&#039; is valid.

netapp::*&gt;
</pre></div>


<p class="wp-block-paragraph">ということで、対処はできませんでした</p>
]]></content:encoded>
					
					<wfw:commentRss>https://blog.osakana.net/archives/17280/feed</wfw:commentRss>
			<slash:comments>0</slash:comments>
		
		
			</item>
		<item>
		<title>Windows OS上でユーザ権限でファイルシステムをマウントできるようにするDokany</title>
		<link>https://blog.osakana.net/archives/17216</link>
					<comments>https://blog.osakana.net/archives/17216#respond</comments>
		
		<dc:creator><![CDATA[osakanataro]]></dc:creator>
		<pubDate>Fri, 15 May 2026 00:59:47 +0000</pubDate>
				<category><![CDATA[OS]]></category>
		<category><![CDATA[Windows]]></category>
		<category><![CDATA[ストレージ]]></category>
		<category><![CDATA[ファイルシステム]]></category>
		<guid isPermaLink="false">https://blog.osakana.net/?p=17216</guid>

					<description><![CDATA[バックアップソフトのCommvaultの 取得したバックアップデータを実際にはリストアしないでユーザ側に直接ファイルシステムとしてアクセスできるようにする3DFSについてドキュメントを見ていたところ、下記の記述があった。 &#8230; <p class="link-more"><a href="https://blog.osakana.net/archives/17216" class="more-link"><span class="screen-reader-text">"Windows OS上でユーザ権限でファイルシステムをマウントできるようにするDokany" の</span>続きを読む</a></p>]]></description>
										<content:encoded><![CDATA[
<p class="wp-block-paragraph">バックアップソフトのCommvaultの 取得したバックアップデータを実際にはリストアしないでユーザ側に直接ファイルシステムとしてアクセスできるようにする<a href="https://documentation.commvault.com/v11/commcell-console/getting_started_with_3dfs.html">3DFS</a>についてドキュメントを見ていたところ、下記の記述があった。</p>



<figure class="wp-block-image size-full"><a href="https://blog.osakana.net/wp-content/uploads/2026/05/BC5DF14F-556C-433F-83D3-F07C0512A426.png"><img loading="lazy" decoding="async" width="861" height="316" src="https://blog.osakana.net/wp-content/uploads/2026/05/BC5DF14F-556C-433F-83D3-F07C0512A426.png" alt="" class="wp-image-17218" srcset="https://blog.osakana.net/wp-content/uploads/2026/05/BC5DF14F-556C-433F-83D3-F07C0512A426.png 861w, https://blog.osakana.net/wp-content/uploads/2026/05/BC5DF14F-556C-433F-83D3-F07C0512A426-300x110.png 300w, https://blog.osakana.net/wp-content/uploads/2026/05/BC5DF14F-556C-433F-83D3-F07C0512A426-768x282.png 768w" sizes="auto, (max-width: 767px) 89vw, (max-width: 1000px) 54vw, (max-width: 1071px) 543px, 580px" /></a></figure>



<p class="wp-block-paragraph">Windowsバックアップデータを、Windowsサーバ上でファイルシステムとして見れるようにする場合、Dokany というオープンソースのコールバックファイルシステムが必要だという。</p>



<p class="wp-block-paragraph">dokany を調べると github にあった</p>



<p class="wp-block-paragraph"> <a href="https://github.com/dokan-dev/dokany">https://github.com/dokan-dev/dokany</a></p>



<p class="wp-block-paragraph">&#8220;<em>Dokany is a fork of Dokan 0.6.0 with bug fixes, clean change history and updated to build with latest tools.</em>&#8220;</p>



<p class="wp-block-paragraph">dokan !? 「<a href="https://blog.osakana.net/archives/4293">Opendedupという重複排除機能搭載のLinux/Windows向けファイルシステム</a>」で使われていたやつだ</p>



<p class="wp-block-paragraph">2021年にdokan公式Webが消滅したので、forkしたってことですね</p>



<p class="wp-block-paragraph"> <a href="https://dokan-dev.github.io/">https://dokan-dev.github.io/</a> を見ると、Dokan FUSEを利用して、いろんなものをファイルシステムとしてマウントできるようにするものが作られているようです</p>



<p class="wp-block-paragraph"></p>



<p class="wp-block-paragraph"></p>
]]></content:encoded>
					
					<wfw:commentRss>https://blog.osakana.net/archives/17216/feed</wfw:commentRss>
			<slash:comments>0</slash:comments>
		
		
			</item>
		<item>
		<title>Proxmox VE 9.1でのパッチ適用は「apt dist-upgrade」で行う</title>
		<link>https://blog.osakana.net/archives/17180</link>
					<comments>https://blog.osakana.net/archives/17180#respond</comments>
		
		<dc:creator><![CDATA[osakanataro]]></dc:creator>
		<pubDate>Tue, 12 May 2026 05:23:08 +0000</pubDate>
				<category><![CDATA[Linux]]></category>
		<category><![CDATA[OS]]></category>
		<category><![CDATA[proxmox]]></category>
		<category><![CDATA[Ubuntu / Debian]]></category>
		<category><![CDATA[仮想化]]></category>
		<guid isPermaLink="false">https://blog.osakana.net/?p=17180</guid>

					<description><![CDATA[Proxmox VE 9.1環境で、sshログインして「apt upgrade -y」でアップデートしたんだけど、GUIでみると下記の様にパッケージが残っていた sshログインして「apt upgrade」を実行した場合 &#8230; <p class="link-more"><a href="https://blog.osakana.net/archives/17180" class="more-link"><span class="screen-reader-text">"Proxmox VE 9.1でのパッチ適用は「apt dist-upgrade」で行う" の</span>続きを読む</a></p>]]></description>
										<content:encoded><![CDATA[
<p class="wp-block-paragraph">Proxmox VE 9.1環境で、sshログインして「apt upgrade -y」でアップデートしたんだけど、GUIでみると下記の様にパッケージが残っていた</p>



<figure class="wp-block-image size-large"><a href="https://blog.osakana.net/wp-content/uploads/2026/05/EC2131E4-A8FF-4955-BA57-26C23A14E842.png"><img loading="lazy" decoding="async" width="1024" height="271" src="https://blog.osakana.net/wp-content/uploads/2026/05/EC2131E4-A8FF-4955-BA57-26C23A14E842-1024x271.png" alt="" class="wp-image-17182" srcset="https://blog.osakana.net/wp-content/uploads/2026/05/EC2131E4-A8FF-4955-BA57-26C23A14E842-1024x271.png 1024w, https://blog.osakana.net/wp-content/uploads/2026/05/EC2131E4-A8FF-4955-BA57-26C23A14E842-300x80.png 300w, https://blog.osakana.net/wp-content/uploads/2026/05/EC2131E4-A8FF-4955-BA57-26C23A14E842-768x204.png 768w, https://blog.osakana.net/wp-content/uploads/2026/05/EC2131E4-A8FF-4955-BA57-26C23A14E842.png 1256w" sizes="auto, (max-width: 767px) 89vw, (max-width: 1000px) 54vw, (max-width: 1071px) 543px, 580px" /></a></figure>



<p class="wp-block-paragraph">sshログインして「apt upgrade」を実行した場合は以下の結果</p>


<div class="wp-block-syntaxhighlighter-code "><pre class="brush: bash; title: ; notranslate">
root@proxmox1:~# apt upgrade
Not upgrading:
  zfs-initramfs  zfs-zed  zfsutils-linux

Summary:
  Upgrading: 0, Installing: 0, Removing: 0, Not Upgrading: 3
root@proxmox1:~#
</pre></div>


<p class="wp-block-paragraph">しかし、Web GUI上の「アップグレード」をクリックすると、</p>



<figure class="wp-block-image size-full"><a href="https://blog.osakana.net/wp-content/uploads/2026/05/image-2.png"><img loading="lazy" decoding="async" width="802" height="486" src="https://blog.osakana.net/wp-content/uploads/2026/05/image-2.png" alt="" class="wp-image-17183" srcset="https://blog.osakana.net/wp-content/uploads/2026/05/image-2.png 802w, https://blog.osakana.net/wp-content/uploads/2026/05/image-2-300x182.png 300w, https://blog.osakana.net/wp-content/uploads/2026/05/image-2-768x465.png 768w" sizes="auto, (max-width: 767px) 89vw, (max-width: 1000px) 54vw, (max-width: 1071px) 543px, 580px" /></a></figure>



<p class="wp-block-paragraph">上記の様な表示が出る・・・実行しているコマンドが「apt-get dist-upgrade」となっている</p>



<p class="wp-block-paragraph">おや？と思って、マニュアルを再確認してみる</p>



<p class="wp-block-paragraph">「<a href="https://pve.proxmox.com/pve-docs/pve-admin-guide.html#system_software_updates">3.2. System Software Updates</a>」によると・・・</p>



<figure class="wp-block-image size-full"><a href="https://blog.osakana.net/wp-content/uploads/2026/05/7E1DDBF8-FB26-4102-90E0-CF66C682A55E.png"><img loading="lazy" decoding="async" width="1010" height="432" src="https://blog.osakana.net/wp-content/uploads/2026/05/7E1DDBF8-FB26-4102-90E0-CF66C682A55E.png" alt="" class="wp-image-17184" srcset="https://blog.osakana.net/wp-content/uploads/2026/05/7E1DDBF8-FB26-4102-90E0-CF66C682A55E.png 1010w, https://blog.osakana.net/wp-content/uploads/2026/05/7E1DDBF8-FB26-4102-90E0-CF66C682A55E-300x128.png 300w, https://blog.osakana.net/wp-content/uploads/2026/05/7E1DDBF8-FB26-4102-90E0-CF66C682A55E-768x328.png 768w" sizes="auto, (max-width: 767px) 89vw, (max-width: 1000px) 54vw, (max-width: 1071px) 543px, 580px" /></a></figure>



<p class="wp-block-paragraph">「apt-get update」を実行したあと「apt-get dist-upgrade」を実行しろ、とあった</p>



<p class="wp-block-paragraph">というわけで「apt dist-upgrade」コマンドを実行</p>


<div class="wp-block-syntaxhighlighter-code "><pre class="brush: bash; title: ; notranslate">
root@proxmox1:~# apt dist-upgrade
Upgrading:
  zfs-initramfs  zfs-zed  zfsutils-linux

Installing dependencies:
  libzfs7linux  libzpool7linux

REMOVING:
  libzfs6linux

Summary:
  Upgrading: 3, Installing: 2, Removing: 1, Not Upgrading: 0
  Download size: 2,308 kB
  Space needed: 4,470 kB / 31.8 GB available

Continue? &#x5B;Y/n] y
Get:1 http://download.proxmox.com/debian/pve trixie/pve-no-subscription amd64 zfs-initramfs all 2.4.1-pve1 &#x5B;26.8 kB]
Get:2 http://download.proxmox.com/debian/pve trixie/pve-no-subscription amd64 zfsutils-linux amd64 2.4.1-pve1 &#x5B;596 kB]
Get:3 http://download.proxmox.com/debian/pve trixie/pve-no-subscription amd64 zfs-zed amd64 2.4.1-pve1 &#x5B;71.0 kB]
Get:4 http://download.proxmox.com/debian/pve trixie/pve-no-subscription amd64 libzfs7linux amd64 2.4.1-pve1 &#x5B;226 kB]
Get:5 http://download.proxmox.com/debian/pve trixie/pve-no-subscription amd64 libzpool7linux amd64 2.4.1-pve1 &#x5B;1,388 kB]
Fetched 2,308 kB in 2s (935 kB/s)
Reading changelogs... Done
(Reading database ... 76859 files and directories currently installed.)
Preparing to unpack .../zfs-initramfs_2.4.1-pve1_all.deb ...
Unpacking zfs-initramfs (2.4.1-pve1) over (2.3.4-pve1) ...
Preparing to unpack .../zfsutils-linux_2.4.1-pve1_amd64.deb ...
Unpacking zfsutils-linux (2.4.1-pve1) over (2.3.4-pve1) ...
Preparing to unpack .../zfs-zed_2.4.1-pve1_amd64.deb ...
Unpacking zfs-zed (2.4.1-pve1) over (2.3.4-pve1) ...
(Reading database ... 76862 files and directories currently installed.)
Removing libzfs6linux:amd64 (2.3.4-pve1) ...
Removing &#039;diversion of /lib/x86_64-linux-gnu/libzfs_core.so.3 to /lib/x86_64-linux-gnu/libzfs_core.so.3.usr-is-merged by libzfs6linux&#039;
Removing &#039;diversion of /lib/x86_64-linux-gnu/libzfs_core.so.3.0.0 to /lib/x86_64-linux-gnu/libzfs_core.so.3.0.0.usr-is-merged by libzfs6linux&#039;
Selecting previously unselected package libzfs7linux:amd64.
(Reading database ... 76850 files and directories currently installed.)
Preparing to unpack .../libzfs7linux_2.4.1-pve1_amd64.deb ...
Unpacking libzfs7linux:amd64 (2.4.1-pve1) ...
Selecting previously unselected package libzpool7linux:amd64.
Preparing to unpack .../libzpool7linux_2.4.1-pve1_amd64.deb ...
Unpacking libzpool7linux:amd64 (2.4.1-pve1) ...
Setting up libzpool7linux:amd64 (2.4.1-pve1) ...
Setting up libzfs7linux:amd64 (2.4.1-pve1) ...
No diversion &#039;diversion of /lib/x86_64-linux-gnu/libzfs_core.so.3 to /lib/x86_64-linux-gnu/libzfs_core.so.3.usr-is-merged by libzfs6linux&#039;, none removed.
No diversion &#039;diversion of /lib/x86_64-linux-gnu/libzfs_core.so.3.0.0 to /lib/x86_64-linux-gnu/libzfs_core.so.3.0.0.usr-is-merged by libzfs6linux&#039;, none removed.
Setting up zfsutils-linux (2.4.1-pve1) ...
Installing new version of config file /etc/default/zfs ...
Installing new version of config file /etc/zfs/zfs-functions ...
zfs-import-scan.service is a disabled or a static unit, not starting it.
Setting up zfs-initramfs (2.4.1-pve1) ...
Setting up zfs-zed (2.4.1-pve1) ...
Processing triggers for libc-bin (2.41-12+deb13u2) ...
Processing triggers for man-db (2.13.1-1) ...
Processing triggers for initramfs-tools (0.148.3) ...
update-initramfs: Generating /boot/initrd.img-7.0.2-2-pve
Running hook script &#039;zz-proxmox-boot&#039;..
Re-executing &#039;/etc/kernel/postinst.d/zz-proxmox-boot&#039; in new private mount namespace..
No /etc/kernel/proxmox-boot-uuids found, skipping ESP sync.
root@proxmox1:~#
</pre></div>


<p class="wp-block-paragraph">これで、アップデートしていないパッケージはなくなった</p>


<div class="wp-block-syntaxhighlighter-code "><pre class="brush: bash; title: ; notranslate">
root@proxmox1:~# apt update
Hit:1 http://security.debian.org/debian-security trixie-security InRelease
Hit:2 http://deb.debian.org/debian trixie InRelease
Hit:3 http://deb.debian.org/debian trixie-updates InRelease
Hit:4 http://download.proxmox.com/debian/ceph-squid trixie InRelease
Hit:5 http://download.proxmox.com/debian/pve trixie InRelease
All packages are up to date.
root@proxmox1:~#
</pre></div>


<figure class="wp-block-image size-full"><a href="https://blog.osakana.net/wp-content/uploads/2026/05/5CA70D29-1A47-4210-8F1C-213320D3D855.png"><img loading="lazy" decoding="async" width="791" height="266" src="https://blog.osakana.net/wp-content/uploads/2026/05/5CA70D29-1A47-4210-8F1C-213320D3D855.png" alt="" class="wp-image-17185" srcset="https://blog.osakana.net/wp-content/uploads/2026/05/5CA70D29-1A47-4210-8F1C-213320D3D855.png 791w, https://blog.osakana.net/wp-content/uploads/2026/05/5CA70D29-1A47-4210-8F1C-213320D3D855-300x101.png 300w, https://blog.osakana.net/wp-content/uploads/2026/05/5CA70D29-1A47-4210-8F1C-213320D3D855-768x258.png 768w" sizes="auto, (max-width: 767px) 89vw, (max-width: 1000px) 54vw, (max-width: 1071px) 543px, 580px" /></a></figure>
]]></content:encoded>
					
					<wfw:commentRss>https://blog.osakana.net/archives/17180/feed</wfw:commentRss>
			<slash:comments>0</slash:comments>
		
		
			</item>
		<item>
		<title>postfixのvirtual_transport=dovecot指定時にもvirtual_mailbox_mapsを指定したほうが良い件</title>
		<link>https://blog.osakana.net/archives/17066</link>
					<comments>https://blog.osakana.net/archives/17066#respond</comments>
		
		<dc:creator><![CDATA[osakanataro]]></dc:creator>
		<pubDate>Sat, 09 May 2026 08:17:41 +0000</pubDate>
				<category><![CDATA[LDAP/ActiveDirectory]]></category>
		<category><![CDATA[サービスや仕組み]]></category>
		<category><![CDATA[メール]]></category>
		<guid isPermaLink="false">https://blog.osakana.net/?p=17066</guid>

					<description><![CDATA[postfix/dovecotのメールサーバで、実ドメイン以外のドメインのメールも受け取るようpostfix側にvirtual mailbox domainsの設定を行うことがある その際、dovecotによるquota &#8230; <p class="link-more"><a href="https://blog.osakana.net/archives/17066" class="more-link"><span class="screen-reader-text">"postfixのvirtual_transport=dovecot指定時にもvirtual_mailbox_mapsを指定したほうが良い件" の</span>続きを読む</a></p>]]></description>
										<content:encoded><![CDATA[
<p class="wp-block-paragraph">postfix/dovecotのメールサーバで、実ドメイン以外のドメインのメールも受け取るようpostfix側にvirtual mailbox domainsの設定を行うことがある</p>



<p class="wp-block-paragraph">その際、dovecotによるquota制御を行いたい。</p>



<p class="wp-block-paragraph">その場合の手法は2種類ある。<br>　・dovecotドキュメント「<a href="https://doc.dovecot.org/2.3/configuration_manual/howto/dovecot_lda_postfix/">Dovecot LDA with Postfix</a>」の「virtual_transport = dovecot」を設定して&#8221;Virtual users&#8221;にある設定を行う手法<br>　・dovecotドキュメント「<a href="https://doc.dovecot.org/2.3/configuration_manual/howto/postfix_dovecot_lmtp/">Postfix and Dovecot LMTP</a>」の「virtual_transport = lmtp:unix:private/dovecot-lmtp」を設定してLMTPを使う手法</p>



<p class="wp-block-paragraph">LMTPの方は「Dovecot LDAのdeliverでは動作しません」と書いてあるため、dovecot のquotaを使うためにdovecot ldaを使用する場合には使えなさそう。</p>



<p class="wp-block-paragraph">このため、まずは「virtual_transport = dovecot」の手法を実装</p>



<p class="wp-block-paragraph">postfixの/etc/postfix/main.cf には以下の設定</p>


<div class="wp-block-syntaxhighlighter-code "><pre class="brush: bash; title: ; notranslate">
dovecot_destination_recipient_limit = 1
virtual_mailbox_domains = your.domain.here
virtual_transport = dovecot
</pre></div>


<p class="wp-block-paragraph">postfixの/etc/postfix/master.cf には以下の設定</p>


<div class="wp-block-syntaxhighlighter-code "><pre class="brush: bash; title: ; notranslate">
dovecot   unix  -       n       n       -       -       pipe
  flags=DRhu user=vmail:vmail argv=/usr/libexec/dovecot/dovecot-lda -f ${sender} -d ${recipient}
</pre></div>


<p class="wp-block-paragraph">しかし、この設定を行った場合、存在しないメールアドレス宛に来たメールを拒否する、という動作をしてくれない</p>



<p class="wp-block-paragraph">検証方法はこんな感じ</p>


<div class="wp-block-syntaxhighlighter-code "><pre class="brush: bash; title: ; notranslate">
$ telnet メールサーバホスト名 25
Trying 192.168.x.x...
Connected to 192.168.x.x.
Escape character is &#039;^]&#039;
220 メールサーバホスト名 ESMTP Postfix
ehlo testhost
250-メールサーバホスト名
250-＜以下省略＞
mail from: &lt;&gt;
250 2.1.0 Ok
rcpt to: nothing@your.domain.here
250 2.1.5 Ok
</pre></div>


<p class="wp-block-paragraph">存在しないアドレスを指定した「rcpt to: nothing@your.domain.here」に対する応答として「550 5.1.1 ～」が返ってくることを期待したものの、「250 2.1.5 Ok」という、メールアドレスが存在する場合と同じ応答となっている。</p>



<p class="wp-block-paragraph">これをなんとか出来ないかを調べてみると、プラグインを独自開発しろ、とかいう話が出てきたものの、意外な解決方法の糸口を発見・・・</p>



<p class="wp-block-paragraph">/etc/postfix/master.cf の smtpdの起動を「smtpd -v」と詳細ログ出力モードに変えて、上記操作をしてみたところ、rcpt to入力後の動作に気になるところが・・・</p>



<p class="wp-block-paragraph">「CHECKING Recipient address VALIDATION MAPS」の処理を見てみると以下の順番でメールアドレスの存在確認を行っている模様<br>　1) recipient_canonical_maps<br>　2) canonical_maps<br>　3) virtual_alias_maps</p>



<p class="wp-block-paragraph">検証環境ではvirtual_mailbox_domains とは別に virtual_alias_domains も設定され、virtual_alias_mapsはhashファイルが指定されている。これにより、virtual_alias_mapsの検索が行われていると判断される</p>



<p class="wp-block-paragraph">じゃあ、ここにvirtual_mailbox_mapsを設定したら、virtual_mailbox_mapsに対してメールアドレスの存在確認を行ってくれるんじゃないかな？と期待</p>



<p class="wp-block-paragraph">main.cfに「virtual_mailbox_maps = ldap:/etc/postfix/ldap-mailbox.cf」を追加して、LDAP検索のqueryは「query_filter = (&amp;(objectClass=user)(mail=%s))」で設定した</p>



<p class="wp-block-paragraph">設定後、「dnf install postfix-ldap」でpostfixのldapサポートを追加し、「systemctl restart postfix」でpostfixを再起動して見ると以下の結果となった</p>


<div class="wp-block-syntaxhighlighter-code "><pre class="brush: bash; title: ; notranslate">
$ telnet メールサーバホスト名 25
Trying 192.168.x.x...
Connected to 192.168.x.x.
Escape character is &#039;^]&#039;
220 メールサーバホスト名 ESMTP Postfix
ehlo testhost
250-メールサーバホスト名
250-＜以下省略＞
mail from: &lt;&gt;
250 2.1.0 Ok
rcpt to: nothing@your.domain.here
550 5.1.1 &lt;nothing@your.domain.here&gt;: Recipient address rejected: User unknown in virtual mailbox table
</pre></div>


<p class="wp-block-paragraph">期待通りに「550 5.1.1」による拒否を行ってくれるようになった</p>



<p class="wp-block-paragraph">postfixのdebugログを確認すると、virtual_alias_maps 処理の次に virtual_mailbox_maps処理が追加されていた。<br>　1) recipient_canonical_maps<br>　2) canonical_maps<br>　3) virtual_alias_maps<br>　4) virtual_mailbox_maps</p>



<p class="wp-block-paragraph">このことから、postfixで「virtual_transport=dovecot」を設定した場合であっても、virtual_mailbox_maps設定を行い、postfix側でメールアドレスの存在確認を行った方がよい、ということになる</p>



<p class="wp-block-paragraph"></p>
]]></content:encoded>
					
					<wfw:commentRss>https://blog.osakana.net/archives/17066/feed</wfw:commentRss>
			<slash:comments>0</slash:comments>
		
		
			</item>
		<item>
		<title>wordpressサーバの/var/lib/mysqlにbinlogファイルが大量にたまっていた</title>
		<link>https://blog.osakana.net/archives/17156</link>
					<comments>https://blog.osakana.net/archives/17156#respond</comments>
		
		<dc:creator><![CDATA[osakanataro]]></dc:creator>
		<pubDate>Thu, 07 May 2026 07:49:52 +0000</pubDate>
				<category><![CDATA[Linux]]></category>
		<category><![CDATA[Oracle Linux / CentOS / RHEL]]></category>
		<category><![CDATA[OS]]></category>
		<category><![CDATA[Web]]></category>
		<category><![CDATA[wordpress]]></category>
		<category><![CDATA[トラブル話]]></category>
		<category><![CDATA[雑談]]></category>
		<guid isPermaLink="false">https://blog.osakana.net/?p=17156</guid>

					<description><![CDATA[知り合いのとこのwordpressサーバが稼働していなかったので調査したところディスクフルが発生していた 状況を確認すると、 /var/lib/mysqlが15GBと大変な状態になっていた binlogがたまりまくってい &#8230; <p class="link-more"><a href="https://blog.osakana.net/archives/17156" class="more-link"><span class="screen-reader-text">"wordpressサーバの/var/lib/mysqlにbinlogファイルが大量にたまっていた" の</span>続きを読む</a></p>]]></description>
										<content:encoded><![CDATA[
<p class="wp-block-paragraph">知り合いのとこのwordpressサーバが稼働していなかったので調査したところディスクフルが発生していた</p>



<p class="wp-block-paragraph">状況を確認すると、 /var/lib/mysqlが15GBと大変な状態になっていた</p>



<figure class="wp-block-image size-full"><a href="https://blog.osakana.net/wp-content/uploads/2026/05/image-1.png"><img loading="lazy" decoding="async" width="472" height="696" src="https://blog.osakana.net/wp-content/uploads/2026/05/image-1.png" alt="" class="wp-image-17159" srcset="https://blog.osakana.net/wp-content/uploads/2026/05/image-1.png 472w, https://blog.osakana.net/wp-content/uploads/2026/05/image-1-203x300.png 203w" sizes="auto, (max-width: 472px) 100vw, 472px" /></a></figure>



<p class="wp-block-paragraph">binlogがたまりまくっていた</p>



<p class="wp-block-paragraph">というか、4/23以降、一日1GB以上出力されたりしてるのなんでだ？？</p>


<div class="wp-block-syntaxhighlighter-code "><pre class="brush: bash; title: ; notranslate">
&#x5B;root@xxxxxxxxxxx mysql]# ls -ltr /var/lib/mysql/binlog*
-rw-r-----. 1 mysql mysql 1076027128 Apr 11 12:15 /var/lib/mysql/binlog.000401
-rw-r-----. 1 mysql mysql  895282121 Apr 23 06:48 /var/lib/mysql/binlog.000402
-rw-r-----. 1 mysql mysql 1076428654 Apr 23 19:12 /var/lib/mysql/binlog.000403
-rw-r-----. 1 mysql mysql  596357576 Apr 24 03:25 /var/lib/mysql/binlog.000404
-rw-r-----. 1 mysql mysql 1074553571 Apr 24 22:57 /var/lib/mysql/binlog.000405
-rw-r-----. 1 mysql mysql 1075609896 Apr 26 11:28 /var/lib/mysql/binlog.000406
-rw-r-----. 1 mysql mysql 1075981972 Apr 27 18:37 /var/lib/mysql/binlog.000407
-rw-r-----. 1 mysql mysql 1075913505 Apr 28 00:47 /var/lib/mysql/binlog.000408
-rw-r-----. 1 mysql mysql 1075838660 Apr 28 05:05 /var/lib/mysql/binlog.000409
-rw-r-----. 1 mysql mysql 1075205513 Apr 28 08:48 /var/lib/mysql/binlog.000410
-rw-r-----. 1 mysql mysql    5651277 Apr 29 23:47 /var/lib/mysql/binlog.000411
-rw-r-----. 1 mysql mysql    2052256 Apr 29 23:56 /var/lib/mysql/binlog.000412
-rw-r-----. 1 mysql mysql     101787 Apr 30 00:01 /var/lib/mysql/binlog.000413
-rw-r-----. 1 mysql mysql    3171581 Apr 30 03:19 /var/lib/mysql/binlog.000414
-rw-r-----. 1 mysql mysql 1074621728 May  3 02:47 /var/lib/mysql/binlog.000415
-rw-r-----. 1 mysql mysql 1074747087 May  5 18:27 /var/lib/mysql/binlog.000416
-rw-r-----. 1 mysql mysql 1074122275 May  6 01:02 /var/lib/mysql/binlog.000417
-rw-r-----. 1 mysql mysql 1076183303 May  6 16:09 /var/lib/mysql/binlog.000418
-rw-r-----. 1 mysql mysql 1074003040 May  7 01:08 /var/lib/mysql/binlog.000419
-rw-r-----. 1 mysql mysql        320 May  7 01:08 /var/lib/mysql/binlog.index
-rw-r-----. 1 mysql mysql  286409863 May  7 16:07 /var/lib/mysql/binlog.000420
&#x5B;root@xxxxxxxxxxx mysql]# 
</pre></div>


<p class="wp-block-paragraph">とりあえず、binlog関連の設定を「show variables like &#8216;binlog%&#8217;;」を実行して確認してみる</p>


<div class="wp-block-syntaxhighlighter-code "><pre class="brush: bash; title: ; notranslate">
&#x5B;root@xxxxxxxxxxx mysql]# mysql -u root
Welcome to the MySQL monitor.  Commands end with ; or \g.
Your MySQL connection id is 50827
Server version: 8.0.45 Source distribution

Copyright (c) 2000, 2026, Oracle and/or its affiliates.

Oracle is a registered trademark of Oracle Corporation and/or its
affiliates. Other names may be trademarks of their respective
owners.

Type &#039;help;&#039; or &#039;\h&#039; for help. Type &#039;\c&#039; to clear the current input statement.

mysql&gt; show variables like &#039;binlog%&#039;;
+------------------------------------------------+--------------+
| Variable_name                                  | Value        |
+------------------------------------------------+--------------+
| binlog_cache_size                              | 32768        |
| binlog_checksum                                | CRC32        |
| binlog_direct_non_transactional_updates        | OFF          |
| binlog_encryption                              | OFF          |
| binlog_error_action                            | ABORT_SERVER |
| binlog_expire_logs_auto_purge                  | ON           |
| binlog_expire_logs_seconds                     | 2592000      |
| binlog_format                                  | ROW          |
| binlog_group_commit_sync_delay                 | 0            |
| binlog_group_commit_sync_no_delay_count        | 0            |
| binlog_gtid_simple_recovery                    | ON           |
| binlog_max_flush_queue_time                    | 0            |
| binlog_order_commits                           | ON           |
| binlog_rotate_encryption_master_key_at_startup | OFF          |
| binlog_row_event_max_size                      | 8192         |
| binlog_row_image                               | FULL         |
| binlog_row_metadata                            | MINIMAL      |
| binlog_row_value_options                       |              |
| binlog_rows_query_log_events                   | OFF          |
| binlog_stmt_cache_size                         | 32768        |
| binlog_transaction_compression                 | OFF          |
| binlog_transaction_compression_level_zstd      | 3            |
| binlog_transaction_dependency_history_size     | 25000        |
| binlog_transaction_dependency_tracking         | COMMIT_ORDER |
+------------------------------------------------+--------------+
24 rows in set (0.00 sec)

mysql&gt; 
</pre></div>


<p class="wp-block-paragraph"><a href="https://dev.mysql.com/doc/refman/8.0/ja/replication-options-binary-log.html#sysvar_binlog_expire_logs_seconds">17.1.6.4 バイナリロギングのオプションと変数</a>を参照するとbinlog_expire_logs_secondsが関連する設定で、これが&#8221;binlog_expire_logs_seconds=2592000&#8243; なので 720時間(30日)の保存となっている</p>



<p class="wp-block-paragraph">「show binary logs;」を実行して、mysql内部で認識されているbinlog一覧を確認。まあ、/var/lib/mysql以下にあるファイルと一致してますね</p>


<div class="wp-block-syntaxhighlighter-code "><pre class="brush: bash; title: ; notranslate">
mysql&gt; show binary logs;
+---------------+------------+-----------+
| Log_name      | File_size  | Encrypted |
+---------------+------------+-----------+
| binlog.000401 | 1076027128 | No        |
| binlog.000402 |  895282121 | No        |
| binlog.000403 | 1076428654 | No        |
| binlog.000404 |  596357576 | No        |
| binlog.000405 | 1074553571 | No        |
| binlog.000406 | 1075609896 | No        |
| binlog.000407 | 1075981972 | No        |
| binlog.000408 | 1075913505 | No        |
| binlog.000409 | 1075838660 | No        |
| binlog.000410 | 1075205513 | No        |
| binlog.000411 |    5651277 | No        |
| binlog.000412 |    2052256 | No        |
| binlog.000413 |     101787 | No        |
| binlog.000414 |    3171581 | No        |
| binlog.000415 | 1074621728 | No        |
| binlog.000416 | 1074747087 | No        |
| binlog.000417 | 1074122275 | No        |
| binlog.000418 | 1076183303 | No        |
| binlog.000419 | 1074003040 | No        |
| binlog.000420 |  319677238 | No        |
+---------------+------------+-----------+
20 rows in set (0.02 sec)

mysql&gt; 
</pre></div>


<p class="wp-block-paragraph">まず最初として、「set PERSIST binlog_expire_logs_seconds=604800;」を実行してbinlog_expire_logs_secondsを7日間に短縮する</p>


<div class="wp-block-syntaxhighlighter-code "><pre class="brush: bash; title: ; notranslate">
mysql&gt; set PERSIST binlog_expire_logs_seconds=604800;
Query OK, 0 rows affected (0.00 sec)

mysql&gt; show variables like &#039;binlog%&#039;;
+------------------------------------------------+--------------+
| Variable_name                                  | Value        |
+------------------------------------------------+--------------+
| binlog_cache_size                              | 32768        |
| binlog_checksum                                | CRC32        |
| binlog_direct_non_transactional_updates        | OFF          |
| binlog_encryption                              | OFF          |
| binlog_error_action                            | ABORT_SERVER |
| binlog_expire_logs_auto_purge                  | ON           |
| binlog_expire_logs_seconds                     | 604800       |
| binlog_format                                  | ROW          |
| binlog_group_commit_sync_delay                 | 0            |
| binlog_group_commit_sync_no_delay_count        | 0            |
| binlog_gtid_simple_recovery                    | ON           |
| binlog_max_flush_queue_time                    | 0            |
| binlog_order_commits                           | ON           |
| binlog_rotate_encryption_master_key_at_startup | OFF          |
| binlog_row_event_max_size                      | 8192         |
| binlog_row_image                               | FULL         |
| binlog_row_metadata                            | MINIMAL      |
| binlog_row_value_options                       |              |
| binlog_rows_query_log_events                   | OFF          |
| binlog_stmt_cache_size                         | 32768        |
| binlog_transaction_compression                 | OFF          |
| binlog_transaction_compression_level_zstd      | 3            |
| binlog_transaction_dependency_history_size     | 25000        |
| binlog_transaction_dependency_tracking         | COMMIT_ORDER |
+------------------------------------------------+--------------+
24 rows in set (0.00 sec)

mysql&gt; 
</pre></div>


<p class="wp-block-paragraph">ただ、設定を変更しただけでは反映されないようで、10分程度待機しただけでは show binary logs;の結果に変化はなかった</p>


<div class="wp-block-syntaxhighlighter-code "><pre class="brush: bash; title: ; notranslate">
mysql&gt; show binary logs;
+---------------+------------+-----------+
| Log_name      | File_size  | Encrypted |
+---------------+------------+-----------+
| binlog.000401 | 1076027128 | No        |
| binlog.000402 |  895282121 | No        |
| binlog.000403 | 1076428654 | No        |
| binlog.000404 |  596357576 | No        |
| binlog.000405 | 1074553571 | No        |
| binlog.000406 | 1075609896 | No        |
| binlog.000407 | 1075981972 | No        |
| binlog.000408 | 1075913505 | No        |
| binlog.000409 | 1075838660 | No        |
| binlog.000410 | 1075205513 | No        |
| binlog.000411 |    5651277 | No        |
| binlog.000412 |    2052256 | No        |
| binlog.000413 |     101787 | No        |
| binlog.000414 |    3171581 | No        |
| binlog.000415 | 1074621728 | No        |
| binlog.000416 | 1074747087 | No        |
| binlog.000417 | 1074122275 | No        |
| binlog.000418 | 1076183303 | No        |
| binlog.000419 | 1074003040 | No        |
| binlog.000420 |  358509579 | No        |
+---------------+------------+-----------+
20 rows in set (0.00 sec)

mysql&gt; 
</pre></div>


<p class="wp-block-paragraph"><a href="https://dev.mysql.com/doc/refman/8.0/ja/purge-binary-logs.html">13.4.1.1&nbsp;PURGE BINARY LOGS ステートメント</a> にあるように手動で「PURGE BINARY LOGS BEFORE &#8216;2026-05-01 00:00:00&#8217;;」と実行すれば2026/05/01以前のbinlogが削除されるのだと思うんだけど・・・ということで実行</p>


<div class="wp-block-syntaxhighlighter-code "><pre class="brush: bash; title: ; notranslate">
mysql&gt; PURGE BINARY LOGS BEFORE &#039;2026-05-01 00:00:00&#039;;
Query OK, 0 rows affected (0.02 sec)

mysql&gt; show binary logs;
+---------------+------------+-----------+
| Log_name      | File_size  | Encrypted |
+---------------+------------+-----------+
| binlog.000415 | 1074621728 | No        |
| binlog.000416 | 1074747087 | No        |
| binlog.000417 | 1074122275 | No        |
| binlog.000418 | 1076183303 | No        |
| binlog.000419 | 1074003040 | No        |
| binlog.000420 |  377894939 | No        |
+---------------+------------+-----------+
6 rows in set (0.00 sec)

mysql&gt; 
</pre></div>


<p class="wp-block-paragraph">ファイルは・・・削除されていますね</p>


<div class="wp-block-syntaxhighlighter-code "><pre class="brush: bash; title: ; notranslate">
&#x5B;root@xxxxxxxxxxx mysql]# ls -ltr /var/lib/mysql/binlog*
-rw-r-----. 1 mysql mysql 1074621728 May  3 02:47 /var/lib/mysql/binlog.000415
-rw-r-----. 1 mysql mysql 1074747087 May  5 18:27 /var/lib/mysql/binlog.000416
-rw-r-----. 1 mysql mysql 1074122275 May  6 01:02 /var/lib/mysql/binlog.000417
-rw-r-----. 1 mysql mysql 1076183303 May  6 16:09 /var/lib/mysql/binlog.000418
-rw-r-----. 1 mysql mysql 1074003040 May  7 01:08 /var/lib/mysql/binlog.000419
-rw-r-----. 1 mysql mysql         96 May  7 16:25 /var/lib/mysql/binlog.index
-rw-r-----. 1 mysql mysql  383435241 May  7 16:25 /var/lib/mysql/binlog.000420
&#x5B;root@xxxxxxxxxxx mysql]# 
</pre></div>


<p class="wp-block-paragraph">とりあえずしのいだので、次はなぜ4/23以降でbinlogが肥大化したのか調査ですね・・・</p>



<hr class="wp-block-separator has-alpha-channel-opacity"/>



<p class="wp-block-paragraph">2026/05/11追記</p>



<p class="wp-block-paragraph">原因がはっきりしないのだが、wordpressのプラグインで更新されていなかったものがあったので、アップデートを5/8に実施したところ、ファイルの増加量が減っていた</p>


<div class="wp-block-syntaxhighlighter-code "><pre class="brush: bash; title: ; notranslate">
&#x5B;root@xxxxxxxxxxx ~]# ls -ltr /var/lib/mysql/bin*
-rw-r-----. 1 mysql mysql 1074747087 May  5 18:27 /var/lib/mysql/binlog.000416
-rw-r-----. 1 mysql mysql 1074122275 May  6 01:02 /var/lib/mysql/binlog.000417
-rw-r-----. 1 mysql mysql 1076183303 May  6 16:09 /var/lib/mysql/binlog.000418
-rw-r-----. 1 mysql mysql 1074003040 May  7 01:08 /var/lib/mysql/binlog.000419
-rw-r-----. 1 mysql mysql 1074323672 May  8 03:18 /var/lib/mysql/binlog.000420
-rw-r-----. 1 mysql mysql 1073965591 May  8 16:47 /var/lib/mysql/binlog.000421
-rw-r-----. 1 mysql mysql 1074897443 May 10 12:39 /var/lib/mysql/binlog.000422
-rw-r-----. 1 mysql mysql        128 May 10 12:39 /var/lib/mysql/binlog.index
-rw-r-----. 1 mysql mysql  576882057 May 11 14:17 /var/lib/mysql/binlog.000423
&#x5B;root@xxxxxxxxxxx ~]#
</pre></div>


<p class="wp-block-paragraph">さらに翌日確認して、間違いなく増加率が激減していることを確認した</p>


<div class="wp-block-syntaxhighlighter-code "><pre class="brush: bash; title: ; notranslate">
&#x5B;root@xxxxxxxxxxx ~]# ls -ltr /var/lib/mysql/bin*
-rw-r-----. 1 mysql mysql 1074747087 May  5 18:27 /var/lib/mysql/binlog.000416
-rw-r-----. 1 mysql mysql 1074122275 May  6 01:02 /var/lib/mysql/binlog.000417
-rw-r-----. 1 mysql mysql 1076183303 May  6 16:09 /var/lib/mysql/binlog.000418
-rw-r-----. 1 mysql mysql 1074003040 May  7 01:08 /var/lib/mysql/binlog.000419
-rw-r-----. 1 mysql mysql 1074323672 May  8 03:18 /var/lib/mysql/binlog.000420
-rw-r-----. 1 mysql mysql 1073965591 May  8 16:47 /var/lib/mysql/binlog.000421
-rw-r-----. 1 mysql mysql 1074897443 May 10 12:39 /var/lib/mysql/binlog.000422
-rw-r-----. 1 mysql mysql        128 May 10 12:39 /var/lib/mysql/binlog.index
-rw-r-----. 1 mysql mysql  867993952 May 12 11:46 /var/lib/mysql/binlog.000423
&#x5B;root@xxxxxxxxxxx ~]# 
</pre></div>


<hr class="wp-block-separator has-alpha-channel-opacity"/>



<p class="wp-block-paragraph">2026/05/21追記</p>



<p class="wp-block-paragraph">落ち着いたかと思ったら、またかーーー</p>


<div class="wp-block-syntaxhighlighter-code "><pre class="brush: plain; title: ; notranslate">
-rw-r-----. 1 mysql mysql         56 Nov 16  2021  auto.cnf
-rw-r-----. 1 mysql mysql  880718553 May 14 03:39  binlog.000424
-rw-r-----. 1 mysql mysql 1074983980 May 15 22:05  binlog.000425
-rw-r-----. 1 mysql mysql 1074458947 May 16 01:00  binlog.000426
-rw-r-----. 1 mysql mysql 1076353655 May 16 04:11  binlog.000427
-rw-r-----. 1 mysql mysql 1075894927 May 16 11:45  binlog.000428
-rw-r-----. 1 mysql mysql 1076430757 May 16 20:30  binlog.000429
-rw-r-----. 1 mysql mysql 1074418130 May 17 01:11  binlog.000430
-rw-r-----. 1 mysql mysql 1075734983 May 17 17:52  binlog.000431
-rw-r-----. 1 mysql mysql 1074210923 May 18 13:17  binlog.000432
-rw-r-----. 1 mysql mysql 1074818836 May 18 19:42  binlog.000433
-rw-r-----. 1 mysql mysql 1075645558 May 19 00:18  binlog.000434
-rw-r-----. 1 mysql mysql 1074848030 May 19 10:46  binlog.000435
-rw-r-----. 1 mysql mysql 1075579091 May 19 15:20  binlog.000436
-rw-r-----. 1 mysql mysql 1076234338 May 19 20:25  binlog.000437
-rw-r-----. 1 mysql mysql  618166201 May 20 03:45  binlog.000438
-rw-r-----. 1 mysql mysql 1075233776 May 20 15:03  binlog.000439
-rw-r-----. 1 mysql mysql 1076237754 May 20 18:18  binlog.000440
-rw-r-----. 1 mysql mysql 1074276162 May 20 21:19  binlog.000441
-rw-r-----. 1 mysql mysql  227580182 May 21 11:19  binlog.000442
-rw-r-----. 1 mysql mysql        304 May 20 21:19  binlog.index
</pre></div>


<p class="wp-block-paragraph">もう set PERSIST binlog_expire_logs_seconds=1; を設定してしまおう・・・・(0が無限扱いだといやなので数値入れとくか的な)</p>


<div class="wp-block-syntaxhighlighter-code "><pre class="brush: bash; title: ; notranslate">
mysql&gt; set PERSIST binlog_expire_logs_seconds=1;
Query OK, 0 rows affected (0.00 sec)

mysql&gt; show variables like &#039;binlog%&#039;;
+------------------------------------------------+--------------+
| Variable_name                                  | Value        |
+------------------------------------------------+--------------+
| binlog_cache_size                              | 32768        |
| binlog_checksum                                | CRC32        |
| binlog_direct_non_transactional_updates        | OFF          |
| binlog_encryption                              | OFF          |
| binlog_error_action                            | ABORT_SERVER |
| binlog_expire_logs_auto_purge                  | ON           |
| binlog_expire_logs_seconds                     | 1            |
| binlog_format                                  | ROW          |
| binlog_group_commit_sync_delay                 | 0            |
| binlog_group_commit_sync_no_delay_count        | 0            |
| binlog_gtid_simple_recovery                    | ON           |
| binlog_max_flush_queue_time                    | 0            |
| binlog_order_commits                           | ON           |
| binlog_rotate_encryption_master_key_at_startup | OFF          |
| binlog_row_event_max_size                      | 8192         |
| binlog_row_image                               | FULL         |
| binlog_row_metadata                            | MINIMAL      |
| binlog_row_value_options                       |              |
| binlog_rows_query_log_events                   | OFF          |
| binlog_stmt_cache_size                         | 32768        |
| binlog_transaction_compression                 | OFF          |
| binlog_transaction_compression_level_zstd      | 3            |
| binlog_transaction_dependency_history_size     | 25000        |
| binlog_transaction_dependency_tracking         | COMMIT_ORDER |
+------------------------------------------------+--------------+
24 rows in set (0.00 sec)

mysql&gt; perge binary logs before &#039;2026-05-20 00:00:00&#039;;
ERROR 1064 (42000): You have an error in your SQL syntax; check the manual that corresponds to your MySQL server version for the right syntax to use near &#039;perge binary logs before &#039;2026-05-20 00:00:00&#039;&#039; at line 1
mysql&gt; purge binary logs before &#039;2026-05-20 00:00:00&#039;;
Query OK, 0 rows affected (0.12 sec)

mysql&gt; show binary logs;
+---------------+------------+-----------+
| Log_name      | File_size  | Encrypted |
+---------------+------------+-----------+
| binlog.000438 |  618166201 | No        |
| binlog.000439 | 1075233776 | No        |
| binlog.000440 | 1076237754 | No        |
| binlog.000441 | 1074276162 | No        |
| binlog.000442 |  234276939 | No        |
+---------------+------------+-----------+
5 rows in set (0.00 sec)

mysql&gt; purge binary logs before &#039;2026-05-21 00:00:00&#039;;
Query OK, 0 rows affected, 1 warning (0.05 sec)

mysql&gt; show binary logs;
+---------------+-----------+-----------+
| Log_name      | File_size | Encrypted |
+---------------+-----------+-----------+
| binlog.000442 | 234276939 | No        |
+---------------+-----------+-----------+
1 row in set (0.00 sec)

mysql&gt; 
</pre></div>]]></content:encoded>
					
					<wfw:commentRss>https://blog.osakana.net/archives/17156/feed</wfw:commentRss>
			<slash:comments>0</slash:comments>
		
		
			</item>
		<item>
		<title>CHUWEI UBOXにWindows 11を入れた</title>
		<link>https://blog.osakana.net/archives/16841</link>
					<comments>https://blog.osakana.net/archives/16841#respond</comments>
		
		<dc:creator><![CDATA[osakanataro]]></dc:creator>
		<pubDate>Thu, 09 Apr 2026 09:08:46 +0000</pubDate>
				<category><![CDATA[AMD]]></category>
		<category><![CDATA[CPU]]></category>
		<category><![CDATA[OS]]></category>
		<category><![CDATA[Windows]]></category>
		<category><![CDATA[パソコン]]></category>
		<category><![CDATA[ミニPC]]></category>
		<guid isPermaLink="false">https://blog.osakana.net/?p=16841</guid>

					<description><![CDATA[先日買ったGMKtec NucBox G10 mini は、32GB メモリ2枚とM.2 NVMe SSD 1TBを増設して、ESXi 8 Free版をインストールして検証に使用している 軽く使っている分には問題なかった &#8230; <p class="link-more"><a href="https://blog.osakana.net/archives/16841" class="more-link"><span class="screen-reader-text">"CHUWEI UBOXにWindows 11を入れた" の</span>続きを読む</a></p>]]></description>
										<content:encoded><![CDATA[
<p class="wp-block-paragraph">先日買った<a href="https://blog.osakana.net/archives/16437">GMKtec NucBox G10 mini</a> は、32GB メモリ2枚とM.2 NVMe SSD 1TBを増設して、ESXi 8 Free版をインストールして検証に使用している</p>



<p class="wp-block-paragraph">軽く使っている分には問題なかったのだが、64GBメモリを限界まで使うようになると、スワップなども行うためか M.2 SSDがめちゃくちゃ発熱する。</p>



<p class="wp-block-paragraph">上の蓋を取って冷却ファンを取り付けてみたものの不格好</p>



<p class="wp-block-paragraph">そんな中、aliexpressを見てたらメモリ16GB/SSD 512GBが入っているRyzen 5 7430U搭載のCHUWI UBOX が約39000円というお値段で売っているのを発見</p>



<a href="https://s.click.aliexpress.com/e/_c4tu5lyb" target="_blank"><img decoding="async" src="//ae01.alicdn.com/kf/S9acf6d5750064df09e05953a21fc38f3C.jpg_350x350.jpg" /></a>



<p class="wp-block-paragraph">SO-DIMMスロット2個、M.2 NVMe SSDスロット2個と置き換えには十分なスペックなので買ってみた。</p>



<h2 class="wp-block-heading">開梱</h2>



<p class="wp-block-paragraph">届いた・・・案外大きい、というのが第一印象</p>



<figure class="wp-block-image size-full"><a href="https://blog.osakana.net/wp-content/uploads/2026/02/image-18.png"><img loading="lazy" decoding="async" width="1009" height="757" src="https://blog.osakana.net/wp-content/uploads/2026/02/image-18.png" alt="" class="wp-image-16873" srcset="https://blog.osakana.net/wp-content/uploads/2026/02/image-18.png 1009w, https://blog.osakana.net/wp-content/uploads/2026/02/image-18-300x225.png 300w, https://blog.osakana.net/wp-content/uploads/2026/02/image-18-768x576.png 768w" sizes="auto, (max-width: 767px) 89vw, (max-width: 1000px) 54vw, (max-width: 1071px) 543px, 580px" /></a></figure>



<p class="wp-block-paragraph">3機種比較</p>



<p class="wp-block-paragraph">メモリ/SSD側を開けてみる</p>



<figure class="wp-block-image size-full"><a href="https://blog.osakana.net/wp-content/uploads/2026/02/6D423E63-889D-46C3-A377-758D0F77A0EA.png"><img loading="lazy" decoding="async" width="697" height="896" src="https://blog.osakana.net/wp-content/uploads/2026/02/6D423E63-889D-46C3-A377-758D0F77A0EA.png" alt="" class="wp-image-16874" srcset="https://blog.osakana.net/wp-content/uploads/2026/02/6D423E63-889D-46C3-A377-758D0F77A0EA.png 697w, https://blog.osakana.net/wp-content/uploads/2026/02/6D423E63-889D-46C3-A377-758D0F77A0EA-233x300.png 233w" sizes="auto, (max-width: 697px) 100vw, 697px" /></a></figure>



<p class="wp-block-paragraph">手で持っている蓋みたいなところがSSDのヒートシンクも兼ねていて放熱シリコンが貼り付けてある</p>



<p class="wp-block-paragraph">SSDをくるむ銀袋にAirDisk APF10 PCIe 3.0&#215;4 M.2 2280とかかれたSSDが入っている</p>



<figure class="wp-block-image size-full"><a href="https://blog.osakana.net/wp-content/uploads/2026/02/A64E7087-8C53-435C-B8F3-70E2C094D936.png"><img loading="lazy" decoding="async" width="543" height="436" src="https://blog.osakana.net/wp-content/uploads/2026/02/A64E7087-8C53-435C-B8F3-70E2C094D936.png" alt="" class="wp-image-16875" srcset="https://blog.osakana.net/wp-content/uploads/2026/02/A64E7087-8C53-435C-B8F3-70E2C094D936.png 543w, https://blog.osakana.net/wp-content/uploads/2026/02/A64E7087-8C53-435C-B8F3-70E2C094D936-300x241.png 300w" sizes="auto, (max-width: 543px) 100vw, 543px" /></a></figure>



<p class="wp-block-paragraph">メモリも銀でくるまれているが、こちらは貼り付けられていて外せなかった</p>



<figure class="wp-block-image size-full"><a href="https://blog.osakana.net/wp-content/uploads/2026/02/image-19.png"><img loading="lazy" decoding="async" width="562" height="256" src="https://blog.osakana.net/wp-content/uploads/2026/02/image-19.png" alt="" class="wp-image-16876" srcset="https://blog.osakana.net/wp-content/uploads/2026/02/image-19.png 562w, https://blog.osakana.net/wp-content/uploads/2026/02/image-19-300x137.png 300w" sizes="auto, (max-width: 562px) 100vw, 562px" /></a></figure>



<p class="wp-block-paragraph">WiFi はRTL8852BEと書かれていた</p>



<figure class="wp-block-image size-large"><a href="https://blog.osakana.net/wp-content/uploads/2026/02/F8BC50EA-1416-4D42-95FE-7831E5147875.png"><img loading="lazy" decoding="async" width="1024" height="822" src="https://blog.osakana.net/wp-content/uploads/2026/02/F8BC50EA-1416-4D42-95FE-7831E5147875-1024x822.png" alt="" class="wp-image-16877" srcset="https://blog.osakana.net/wp-content/uploads/2026/02/F8BC50EA-1416-4D42-95FE-7831E5147875-1024x822.png 1024w, https://blog.osakana.net/wp-content/uploads/2026/02/F8BC50EA-1416-4D42-95FE-7831E5147875-300x241.png 300w, https://blog.osakana.net/wp-content/uploads/2026/02/F8BC50EA-1416-4D42-95FE-7831E5147875-768x616.png 768w, https://blog.osakana.net/wp-content/uploads/2026/02/F8BC50EA-1416-4D42-95FE-7831E5147875.png 1053w" sizes="auto, (max-width: 767px) 89vw, (max-width: 1000px) 54vw, (max-width: 1071px) 543px, 580px" /></a></figure>



<p class="wp-block-paragraph">逆側はCPUが付いているので、ファンが付いている</p>



<figure class="wp-block-image size-full"><a href="https://blog.osakana.net/wp-content/uploads/2026/02/image-20.png"><img loading="lazy" decoding="async" width="737" height="687" src="https://blog.osakana.net/wp-content/uploads/2026/02/image-20.png" alt="" class="wp-image-16878" srcset="https://blog.osakana.net/wp-content/uploads/2026/02/image-20.png 737w, https://blog.osakana.net/wp-content/uploads/2026/02/image-20-300x280.png 300w" sizes="auto, (max-width: 737px) 100vw, 737px" /></a></figure>



<p class="wp-block-paragraph"></p>



<h2 class="wp-block-heading">初期状態</h2>



<p class="wp-block-paragraph">普通に初回ウィザードを経てログイン。コントロールパネルのショートカットが作成されていた</p>



<p class="wp-block-paragraph">あと、キーボード配列は英語だった。</p>



<figure class="wp-block-image size-large"><a href="https://blog.osakana.net/wp-content/uploads/2026/02/image-8.png"><img loading="lazy" decoding="async" width="1024" height="576" src="https://blog.osakana.net/wp-content/uploads/2026/02/image-8-1024x576.png" alt="" class="wp-image-16851" srcset="https://blog.osakana.net/wp-content/uploads/2026/02/image-8-1024x576.png 1024w, https://blog.osakana.net/wp-content/uploads/2026/02/image-8-300x169.png 300w, https://blog.osakana.net/wp-content/uploads/2026/02/image-8-768x432.png 768w, https://blog.osakana.net/wp-content/uploads/2026/02/image-8-1536x864.png 1536w, https://blog.osakana.net/wp-content/uploads/2026/02/image-8.png 1920w" sizes="auto, (max-width: 767px) 89vw, (max-width: 1000px) 54vw, (max-width: 1071px) 543px, 580px" /></a></figure>



<p class="wp-block-paragraph">タスクマネージャを起動して、スペック確認</p>



<p class="wp-block-paragraph">CPU <a href="https://www.amd.com/en/products/processors/laptop/ryzen/7000-series/amd-ryzen-5-7430u.html">Ryzen 5 7430U</a>を確認</p>



<figure class="wp-block-image size-full"><a href="https://blog.osakana.net/wp-content/uploads/2026/02/image-1.png"><img loading="lazy" decoding="async" width="766" height="583" src="https://blog.osakana.net/wp-content/uploads/2026/02/image-1.png" alt="" class="wp-image-16844" srcset="https://blog.osakana.net/wp-content/uploads/2026/02/image-1.png 766w, https://blog.osakana.net/wp-content/uploads/2026/02/image-1-300x228.png 300w" sizes="auto, (max-width: 706px) 89vw, (max-width: 767px) 82vw, 740px" /></a></figure>



<p class="wp-block-paragraph">メモリはPC4-25600(DDR4-3200) の16GB が1枚</p>



<figure class="wp-block-image size-full"><a href="https://blog.osakana.net/wp-content/uploads/2026/02/image-2.png"><img loading="lazy" decoding="async" width="766" height="583" src="https://blog.osakana.net/wp-content/uploads/2026/02/image-2.png" alt="" class="wp-image-16845" srcset="https://blog.osakana.net/wp-content/uploads/2026/02/image-2.png 766w, https://blog.osakana.net/wp-content/uploads/2026/02/image-2-300x228.png 300w" sizes="auto, (max-width: 706px) 89vw, (max-width: 767px) 82vw, 740px" /></a></figure>



<p class="wp-block-paragraph">ディスクは<a href="https://www.airdisk.cc/">AirDisk</a>というメーカの512GB</p>



<figure class="wp-block-image size-full"><a href="https://blog.osakana.net/wp-content/uploads/2026/02/image-3.png"><img loading="lazy" decoding="async" width="766" height="583" src="https://blog.osakana.net/wp-content/uploads/2026/02/image-3.png" alt="" class="wp-image-16846" srcset="https://blog.osakana.net/wp-content/uploads/2026/02/image-3.png 766w, https://blog.osakana.net/wp-content/uploads/2026/02/image-3-300x228.png 300w" sizes="auto, (max-width: 706px) 89vw, (max-width: 767px) 82vw, 740px" /></a></figure>



<p class="wp-block-paragraph">WiFiは、Realtek 8852BE</p>



<figure class="wp-block-image size-full"><a href="https://blog.osakana.net/wp-content/uploads/2026/02/image-4.png"><img loading="lazy" decoding="async" width="766" height="583" src="https://blog.osakana.net/wp-content/uploads/2026/02/image-4.png" alt="" class="wp-image-16847" srcset="https://blog.osakana.net/wp-content/uploads/2026/02/image-4.png 766w, https://blog.osakana.net/wp-content/uploads/2026/02/image-4-300x228.png 300w" sizes="auto, (max-width: 706px) 89vw, (max-width: 767px) 82vw, 740px" /></a></figure>



<p class="wp-block-paragraph">GPUは、メモリを512MB割り当てられていた</p>



<figure class="wp-block-image size-full"><a href="https://blog.osakana.net/wp-content/uploads/2026/02/image-5.png"><img loading="lazy" decoding="async" width="766" height="735" src="https://blog.osakana.net/wp-content/uploads/2026/02/image-5.png" alt="" class="wp-image-16848" srcset="https://blog.osakana.net/wp-content/uploads/2026/02/image-5.png 766w, https://blog.osakana.net/wp-content/uploads/2026/02/image-5-300x288.png 300w" sizes="auto, (max-width: 706px) 89vw, (max-width: 767px) 82vw, 740px" /></a></figure>



<p class="wp-block-paragraph">CPU-Z</p>



<figure class="wp-block-image size-full"><a href="https://blog.osakana.net/wp-content/uploads/2026/02/image-38.png"><img loading="lazy" decoding="async" width="605" height="603" src="https://blog.osakana.net/wp-content/uploads/2026/02/image-38.png" alt="" class="wp-image-16989" srcset="https://blog.osakana.net/wp-content/uploads/2026/02/image-38.png 605w, https://blog.osakana.net/wp-content/uploads/2026/02/image-38-300x300.png 300w, https://blog.osakana.net/wp-content/uploads/2026/02/image-38-150x150.png 150w, https://blog.osakana.net/wp-content/uploads/2026/02/image-38-100x100.png 100w" sizes="auto, (max-width: 605px) 100vw, 605px" /></a></figure>



<p class="wp-block-paragraph">Windows 11 Proのライセンスは「RETAIL」channelではあった</p>



<figure class="wp-block-image size-full"><a href="https://blog.osakana.net/wp-content/uploads/2026/02/image-6.png"><img loading="lazy" decoding="async" width="298" height="198" src="https://blog.osakana.net/wp-content/uploads/2026/02/image-6.png" alt="" class="wp-image-16849"/></a></figure>



<figure class="wp-block-image size-large"><a href="https://blog.osakana.net/wp-content/uploads/2026/02/image-16.png"><img loading="lazy" decoding="async" width="1024" height="796" src="https://blog.osakana.net/wp-content/uploads/2026/02/image-16-1024x796.png" alt="" class="wp-image-16861" srcset="https://blog.osakana.net/wp-content/uploads/2026/02/image-16-1024x796.png 1024w, https://blog.osakana.net/wp-content/uploads/2026/02/image-16-300x233.png 300w, https://blog.osakana.net/wp-content/uploads/2026/02/image-16-768x597.png 768w, https://blog.osakana.net/wp-content/uploads/2026/02/image-16.png 1202w" sizes="auto, (max-width: 767px) 89vw, (max-width: 1000px) 54vw, (max-width: 1071px) 543px, 580px" /></a></figure>



<figure class="wp-block-image size-large"><a href="https://blog.osakana.net/wp-content/uploads/2026/02/image-12.png"><img loading="lazy" decoding="async" width="1024" height="575" src="https://blog.osakana.net/wp-content/uploads/2026/02/image-12-1024x575.png" alt="" class="wp-image-16856" srcset="https://blog.osakana.net/wp-content/uploads/2026/02/image-12-1024x575.png 1024w, https://blog.osakana.net/wp-content/uploads/2026/02/image-12-300x168.png 300w, https://blog.osakana.net/wp-content/uploads/2026/02/image-12-768x431.png 768w, https://blog.osakana.net/wp-content/uploads/2026/02/image-12-1536x862.png 1536w, https://blog.osakana.net/wp-content/uploads/2026/02/image-12.png 1694w" sizes="auto, (max-width: 767px) 89vw, (max-width: 1000px) 54vw, (max-width: 1071px) 543px, 580px" /></a></figure>



<figure class="wp-block-image size-large"><a href="https://blog.osakana.net/wp-content/uploads/2026/02/image-13.png"><img loading="lazy" decoding="async" width="1024" height="575" src="https://blog.osakana.net/wp-content/uploads/2026/02/image-13-1024x575.png" alt="" class="wp-image-16857" srcset="https://blog.osakana.net/wp-content/uploads/2026/02/image-13-1024x575.png 1024w, https://blog.osakana.net/wp-content/uploads/2026/02/image-13-300x168.png 300w, https://blog.osakana.net/wp-content/uploads/2026/02/image-13-768x431.png 768w, https://blog.osakana.net/wp-content/uploads/2026/02/image-13-1536x862.png 1536w, https://blog.osakana.net/wp-content/uploads/2026/02/image-13.png 1694w" sizes="auto, (max-width: 767px) 89vw, (max-width: 1000px) 54vw, (max-width: 1071px) 543px, 580px" /></a></figure>



<p class="wp-block-paragraph">プレインストールのアプリは下記</p>



<figure class="wp-block-image size-large"><a href="https://blog.osakana.net/wp-content/uploads/2026/02/image-7.png"><img loading="lazy" decoding="async" width="1024" height="577" src="https://blog.osakana.net/wp-content/uploads/2026/02/image-7-1024x577.png" alt="" class="wp-image-16850" srcset="https://blog.osakana.net/wp-content/uploads/2026/02/image-7-1024x577.png 1024w, https://blog.osakana.net/wp-content/uploads/2026/02/image-7-300x169.png 300w, https://blog.osakana.net/wp-content/uploads/2026/02/image-7-768x433.png 768w, https://blog.osakana.net/wp-content/uploads/2026/02/image-7.png 1125w" sizes="auto, (max-width: 767px) 89vw, (max-width: 1000px) 54vw, (max-width: 1071px) 543px, 580px" /></a></figure>



<p class="wp-block-paragraph">AMD Settings は Radeon管理ソフトAdrenalin。ver 2024.0819.1807.1996 で新しくはない</p>



<p class="wp-block-paragraph">Realtek PCI-E Wireless LAN WiFi 6 Driver はWiFiのドライバで、ver 3.00.045</p>



<p class="wp-block-paragraph">Windows Updateを実施して、Windows 11 Pro 25H2 にアップデートした後</p>



<figure class="wp-block-image size-large"><a href="https://blog.osakana.net/wp-content/uploads/2026/02/image-15.png"><img loading="lazy" decoding="async" width="1024" height="796" src="https://blog.osakana.net/wp-content/uploads/2026/02/image-15-1024x796.png" alt="" class="wp-image-16860" srcset="https://blog.osakana.net/wp-content/uploads/2026/02/image-15-1024x796.png 1024w, https://blog.osakana.net/wp-content/uploads/2026/02/image-15-300x233.png 300w, https://blog.osakana.net/wp-content/uploads/2026/02/image-15-768x597.png 768w, https://blog.osakana.net/wp-content/uploads/2026/02/image-15.png 1202w" sizes="auto, (max-width: 767px) 89vw, (max-width: 1000px) 54vw, (max-width: 1071px) 543px, 580px" /></a></figure>



<hr class="wp-block-separator has-alpha-channel-opacity"/>



<blockquote class="wp-block-quote is-layout-flow wp-block-quote-is-layout-flow">
<p class="wp-block-paragraph">Windows 11 Pro再インストール実施</p>
</blockquote>



<p class="wp-block-paragraph">再インストール後のドライバ適用状態確認</p>



<figure class="wp-block-image size-full"><a href="https://blog.osakana.net/wp-content/uploads/2026/02/image-9.png"><img loading="lazy" decoding="async" width="450" height="782" src="https://blog.osakana.net/wp-content/uploads/2026/02/image-9.png" alt="" class="wp-image-16853" srcset="https://blog.osakana.net/wp-content/uploads/2026/02/image-9.png 450w, https://blog.osakana.net/wp-content/uploads/2026/02/image-9-173x300.png 173w" sizes="auto, (max-width: 450px) 100vw, 450px" /></a></figure>



<p class="wp-block-paragraph">ネットワークコントローラが未認識・・・</p>



<p class="wp-block-paragraph">有線LAN Realtek 2.5Gb NIC 2ポートは認識しているので、WiFiが未認識、ということになる。</p>



<p class="wp-block-paragraph">AMD Radeon Graphicsもあるので、GPUも認識はしていた。</p>



<figure class="wp-block-image size-full"><a href="https://blog.osakana.net/wp-content/uploads/2026/02/image-10.png"><img loading="lazy" decoding="async" width="531" height="392" src="https://blog.osakana.net/wp-content/uploads/2026/02/image-10.png" alt="" class="wp-image-16854" srcset="https://blog.osakana.net/wp-content/uploads/2026/02/image-10.png 531w, https://blog.osakana.net/wp-content/uploads/2026/02/image-10-300x221.png 300w" sizes="auto, (max-width: 531px) 100vw, 531px" /></a></figure>



<h3 class="wp-block-heading">ドライバ調査</h3>



<p class="wp-block-paragraph">とりあえずGPUは認識しているのだが、ドライババージョンが古め</p>



<figure class="wp-block-image size-full"><a href="https://blog.osakana.net/wp-content/uploads/2026/02/image-23.png"><img loading="lazy" decoding="async" width="699" height="823" src="https://blog.osakana.net/wp-content/uploads/2026/02/image-23.png" alt="" class="wp-image-16887" srcset="https://blog.osakana.net/wp-content/uploads/2026/02/image-23.png 699w, https://blog.osakana.net/wp-content/uploads/2026/02/image-23-255x300.png 255w" sizes="auto, (max-width: 699px) 100vw, 699px" /></a></figure>



<p class="wp-block-paragraph">Radeon管理ソフトAdrenalinも入れた方がいいのだろうと、<a href="https://www.amd.com/en/support/download/drivers.html">AMDのダウンロードページ</a>へ移動して、[Browse Products]の[Processors]を確認・・・</p>



<figure class="wp-block-image size-full"><a href="https://blog.osakana.net/wp-content/uploads/2026/02/image-17.png"><img loading="lazy" decoding="async" width="229" height="152" src="https://blog.osakana.net/wp-content/uploads/2026/02/image-17.png" alt="" class="wp-image-16870"/></a></figure>



<p class="wp-block-paragraph">Ryzen 5 7430Uがないのですが・・・</p>



<p class="wp-block-paragraph">検索すると下記のように <a href="https://www.amd.com/en/support/downloads/drivers.html/processors/ryzen/ryzen-7000-series/amd-ryzen-5-7530u.html">AMD Ryzen<img src="https://s.w.org/images/core/emoji/17.0.2/72x72/2122.png" alt="™" class="wp-smiley" style="height: 1em; max-height: 1em;" /> 5 7530U Drivers and Downloads &#8211; Latest Version</a> が出てくるのだが、ダウンロードはできなかった</p>



<figure class="wp-block-image size-full"><a href="https://blog.osakana.net/wp-content/uploads/2026/02/84B918A0-E5C1-4CC1-883A-F7B4BBB76087.png"><img loading="lazy" decoding="async" width="409" height="227" src="https://blog.osakana.net/wp-content/uploads/2026/02/84B918A0-E5C1-4CC1-883A-F7B4BBB76087.png" alt="" class="wp-image-16871" srcset="https://blog.osakana.net/wp-content/uploads/2026/02/84B918A0-E5C1-4CC1-883A-F7B4BBB76087.png 409w, https://blog.osakana.net/wp-content/uploads/2026/02/84B918A0-E5C1-4CC1-883A-F7B4BBB76087-300x167.png 300w" sizes="auto, (max-width: 409px) 100vw, 409px" /></a></figure>



<p class="wp-block-paragraph"><a href="https://www.amd.com/en/support/download/drivers.html">Drivers and Support for Processors and Graphics</a> から amd-software-adrenalin-edition-26.1.1-minimalsetup-260119_web.exe をダウンロードしてインストール</p>



<figure class="wp-block-image size-large"><a href="https://blog.osakana.net/wp-content/uploads/2026/02/image-24.png"><img loading="lazy" decoding="async" width="1024" height="717" src="https://blog.osakana.net/wp-content/uploads/2026/02/image-24-1024x717.png" alt="" class="wp-image-16888" srcset="https://blog.osakana.net/wp-content/uploads/2026/02/image-24-1024x717.png 1024w, https://blog.osakana.net/wp-content/uploads/2026/02/image-24-300x210.png 300w, https://blog.osakana.net/wp-content/uploads/2026/02/image-24-768x538.png 768w, https://blog.osakana.net/wp-content/uploads/2026/02/image-24.png 1200w" sizes="auto, (max-width: 767px) 89vw, (max-width: 1000px) 54vw, (max-width: 1071px) 543px, 580px" /></a></figure>



<p class="wp-block-paragraph">ドライバが更新されたことを確認</p>



<figure class="wp-block-image size-full"><a href="https://blog.osakana.net/wp-content/uploads/2026/02/image-25.png"><img loading="lazy" decoding="async" width="699" height="823" src="https://blog.osakana.net/wp-content/uploads/2026/02/image-25.png" alt="" class="wp-image-16889" srcset="https://blog.osakana.net/wp-content/uploads/2026/02/image-25.png 699w, https://blog.osakana.net/wp-content/uploads/2026/02/image-25-255x300.png 255w" sizes="auto, (max-width: 699px) 100vw, 699px" /></a></figure>



<p class="wp-block-paragraph">続いてRealtek 8852BEについて対処する。</p>



<p class="wp-block-paragraph">不明なデバイスとなっているWiFI部分については「PCI\VEN_10EC&amp;DEV_B852&amp;SUBSYS_B85210EC」をMicrosoft Update カタログで検索して入手する</p>



<figure class="wp-block-image size-full"><a href="https://blog.osakana.net/wp-content/uploads/2026/02/image-11.png"><img loading="lazy" decoding="async" width="699" height="823" src="https://blog.osakana.net/wp-content/uploads/2026/02/image-11.png" alt="" class="wp-image-16855" srcset="https://blog.osakana.net/wp-content/uploads/2026/02/image-11.png 699w, https://blog.osakana.net/wp-content/uploads/2026/02/image-11-255x300.png 255w" sizes="auto, (max-width: 699px) 100vw, 699px" /></a></figure>



<p class="wp-block-paragraph">検索すると <a href="https://catalog.update.microsoft.com/Search.aspx?q=VEN_10EC%26DEV_B852%26SUBSYS_B85210EC">Microsoft Update カタログ</a> が出てくるので、cabファイルを展開して適用すればOK</p>



<figure class="wp-block-image size-full"><a href="https://blog.osakana.net/wp-content/uploads/2026/02/image-14.png"><img loading="lazy" decoding="async" width="699" height="823" src="https://blog.osakana.net/wp-content/uploads/2026/02/image-14.png" alt="" class="wp-image-16858" srcset="https://blog.osakana.net/wp-content/uploads/2026/02/image-14.png 699w, https://blog.osakana.net/wp-content/uploads/2026/02/image-14-255x300.png 255w" sizes="auto, (max-width: 699px) 100vw, 699px" /></a></figure>



<p class="wp-block-paragraph">RealTek8852BEのBluetooth機能については、下記のように認識してるので大丈夫だろう、と思っていたのですが、実際にBluetooth接続のゲームパットをつなげようとしたら認識できないことを確認。</p>



<figure class="wp-block-image size-full"><a href="https://blog.osakana.net/wp-content/uploads/2026/02/image-21.png"><img loading="lazy" decoding="async" width="699" height="823" src="https://blog.osakana.net/wp-content/uploads/2026/02/image-21.png" alt="" class="wp-image-16884" srcset="https://blog.osakana.net/wp-content/uploads/2026/02/image-21.png 699w, https://blog.osakana.net/wp-content/uploads/2026/02/image-21-255x300.png 255w" sizes="auto, (max-width: 699px) 100vw, 699px" /></a></figure>



<p class="wp-block-paragraph">デバイス名「USB\VID_0BDA&amp;PID_B85B\00E04C000001」<a href="https://catalog.update.microsoft.com/Search.aspx?q=VID_0BDA%26PID_B85B">Microsoft Update カタログ</a> で検索して、cabファイルをダウンロードしてドライバを適用</p>



<p class="wp-block-paragraph">適用後は「Realtek Bluetooth Adapter」という認識に変わり、Bluetooth接続のゲームパットも正常に認識するようになった。</p>



<figure class="wp-block-image size-full"><a href="https://blog.osakana.net/wp-content/uploads/2026/02/image-22.png"><img loading="lazy" decoding="async" width="699" height="823" src="https://blog.osakana.net/wp-content/uploads/2026/02/image-22.png" alt="" class="wp-image-16885" srcset="https://blog.osakana.net/wp-content/uploads/2026/02/image-22.png 699w, https://blog.osakana.net/wp-content/uploads/2026/02/image-22-255x300.png 255w" sizes="auto, (max-width: 699px) 100vw, 699px" /></a></figure>



<p class="wp-block-paragraph">license HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows NT\CurrentVersion\SoftwareProtectionPlatform</p>



<figure class="wp-block-image size-large"><a href="https://blog.osakana.net/wp-content/uploads/2026/02/image-32.png"><img loading="lazy" decoding="async" width="1024" height="576" src="https://blog.osakana.net/wp-content/uploads/2026/02/image-32-1024x576.png" alt="" class="wp-image-16905" srcset="https://blog.osakana.net/wp-content/uploads/2026/02/image-32-1024x576.png 1024w, https://blog.osakana.net/wp-content/uploads/2026/02/image-32-300x169.png 300w, https://blog.osakana.net/wp-content/uploads/2026/02/image-32-768x432.png 768w, https://blog.osakana.net/wp-content/uploads/2026/02/image-32-1536x864.png 1536w, https://blog.osakana.net/wp-content/uploads/2026/02/image-32.png 1920w" sizes="auto, (max-width: 767px) 89vw, (max-width: 1000px) 54vw, (max-width: 1071px) 543px, 580px" /></a></figure>



<p class="wp-block-paragraph">VK7JG-NPHTM-C97JM-9MPGT-3V66T</p>



<figure class="wp-block-image size-full"><a href="https://blog.osakana.net/wp-content/uploads/2026/02/image-33.png"><img loading="lazy" decoding="async" width="799" height="521" src="https://blog.osakana.net/wp-content/uploads/2026/02/image-33.png" alt="" class="wp-image-16907" srcset="https://blog.osakana.net/wp-content/uploads/2026/02/image-33.png 799w, https://blog.osakana.net/wp-content/uploads/2026/02/image-33-300x196.png 300w, https://blog.osakana.net/wp-content/uploads/2026/02/image-33-768x501.png 768w" sizes="auto, (max-width: 767px) 89vw, (max-width: 1000px) 54vw, (max-width: 1071px) 543px, 580px" /></a></figure>



<hr class="wp-block-separator has-alpha-channel-opacity"/>



<p class="wp-block-paragraph">ドラクエベンチマーク</p>



<p class="wp-block-paragraph">GPUメモリ16GB割り当て時</p>



<figure class="wp-block-image size-full"><a href="https://blog.osakana.net/wp-content/uploads/2026/02/image-26.png"><img loading="lazy" decoding="async" width="750" height="600" src="https://blog.osakana.net/wp-content/uploads/2026/02/image-26.png" alt="" class="wp-image-16895" srcset="https://blog.osakana.net/wp-content/uploads/2026/02/image-26.png 750w, https://blog.osakana.net/wp-content/uploads/2026/02/image-26-300x240.png 300w" sizes="auto, (max-width: 706px) 89vw, (max-width: 767px) 82vw, 740px" /></a></figure>



<figure class="wp-block-image size-full"><a href="https://blog.osakana.net/wp-content/uploads/2026/02/image-27.png"><img loading="lazy" decoding="async" width="750" height="600" src="https://blog.osakana.net/wp-content/uploads/2026/02/image-27.png" alt="" class="wp-image-16896" srcset="https://blog.osakana.net/wp-content/uploads/2026/02/image-27.png 750w, https://blog.osakana.net/wp-content/uploads/2026/02/image-27-300x240.png 300w" sizes="auto, (max-width: 706px) 89vw, (max-width: 767px) 82vw, 740px" /></a></figure>



<figure class="wp-block-image size-full"><a href="https://blog.osakana.net/wp-content/uploads/2026/02/image-29.png"><img loading="lazy" decoding="async" width="750" height="600" src="https://blog.osakana.net/wp-content/uploads/2026/02/image-29.png" alt="" class="wp-image-16898" srcset="https://blog.osakana.net/wp-content/uploads/2026/02/image-29.png 750w, https://blog.osakana.net/wp-content/uploads/2026/02/image-29-300x240.png 300w" sizes="auto, (max-width: 706px) 89vw, (max-width: 767px) 82vw, 740px" /></a></figure>



<p class="wp-block-paragraph">GPUメモリ4GB割り当て時</p>



<figure class="wp-block-image size-full"><a href="https://blog.osakana.net/wp-content/uploads/2026/02/image-30.png"><img loading="lazy" decoding="async" width="750" height="600" src="https://blog.osakana.net/wp-content/uploads/2026/02/image-30.png" alt="" class="wp-image-16900" srcset="https://blog.osakana.net/wp-content/uploads/2026/02/image-30.png 750w, https://blog.osakana.net/wp-content/uploads/2026/02/image-30-300x240.png 300w" sizes="auto, (max-width: 706px) 89vw, (max-width: 767px) 82vw, 740px" /></a></figure>



<p class="wp-block-paragraph">GPU自動割り当て</p>



<figure class="wp-block-image size-full"><a href="https://blog.osakana.net/wp-content/uploads/2026/02/image-31.png"><img loading="lazy" decoding="async" width="750" height="600" src="https://blog.osakana.net/wp-content/uploads/2026/02/image-31.png" alt="" class="wp-image-16902" srcset="https://blog.osakana.net/wp-content/uploads/2026/02/image-31.png 750w, https://blog.osakana.net/wp-content/uploads/2026/02/image-31-300x240.png 300w" sizes="auto, (max-width: 706px) 89vw, (max-width: 767px) 82vw, 740px" /></a></figure>



<p class="wp-block-paragraph"></p>



<p class="wp-block-paragraph">CPU-Z</p>



<figure class="wp-block-image size-full"><a href="https://blog.osakana.net/wp-content/uploads/2026/02/image-39.png"><img loading="lazy" decoding="async" width="605" height="603" src="https://blog.osakana.net/wp-content/uploads/2026/02/image-39.png" alt="" class="wp-image-16990" srcset="https://blog.osakana.net/wp-content/uploads/2026/02/image-39.png 605w, https://blog.osakana.net/wp-content/uploads/2026/02/image-39-300x300.png 300w, https://blog.osakana.net/wp-content/uploads/2026/02/image-39-150x150.png 150w, https://blog.osakana.net/wp-content/uploads/2026/02/image-39-100x100.png 100w" sizes="auto, (max-width: 605px) 100vw, 605px" /></a></figure>



<figure class="wp-block-image size-full"><a href="https://blog.osakana.net/wp-content/uploads/2026/03/image.png"><img loading="lazy" decoding="async" width="605" height="603" src="https://blog.osakana.net/wp-content/uploads/2026/03/image.png" alt="" class="wp-image-16991" srcset="https://blog.osakana.net/wp-content/uploads/2026/03/image.png 605w, https://blog.osakana.net/wp-content/uploads/2026/03/image-300x300.png 300w, https://blog.osakana.net/wp-content/uploads/2026/03/image-150x150.png 150w, https://blog.osakana.net/wp-content/uploads/2026/03/image-100x100.png 100w" sizes="auto, (max-width: 605px) 100vw, 605px" /></a></figure>



<figure class="wp-block-image size-full is-resized"><a href="https://blog.osakana.net/wp-content/uploads/2026/03/image-1.png"><img loading="lazy" decoding="async" width="605" height="603" src="https://blog.osakana.net/wp-content/uploads/2026/03/image-1.png" alt="" class="wp-image-16992" style="width:607px;height:auto" srcset="https://blog.osakana.net/wp-content/uploads/2026/03/image-1.png 605w, https://blog.osakana.net/wp-content/uploads/2026/03/image-1-300x300.png 300w, https://blog.osakana.net/wp-content/uploads/2026/03/image-1-150x150.png 150w, https://blog.osakana.net/wp-content/uploads/2026/03/image-1-100x100.png 100w" sizes="auto, (max-width: 605px) 100vw, 605px" /></a></figure>



<figure class="wp-block-image size-full"><a href="https://blog.osakana.net/wp-content/uploads/2026/03/image-2.png"><img loading="lazy" decoding="async" width="605" height="603" src="https://blog.osakana.net/wp-content/uploads/2026/03/image-2.png" alt="" class="wp-image-16993" srcset="https://blog.osakana.net/wp-content/uploads/2026/03/image-2.png 605w, https://blog.osakana.net/wp-content/uploads/2026/03/image-2-300x300.png 300w, https://blog.osakana.net/wp-content/uploads/2026/03/image-2-150x150.png 150w, https://blog.osakana.net/wp-content/uploads/2026/03/image-2-100x100.png 100w" sizes="auto, (max-width: 605px) 100vw, 605px" /></a></figure>



<figure class="wp-block-image size-full"><a href="https://blog.osakana.net/wp-content/uploads/2026/03/image-3.png"><img loading="lazy" decoding="async" width="605" height="603" src="https://blog.osakana.net/wp-content/uploads/2026/03/image-3.png" alt="" class="wp-image-16994" srcset="https://blog.osakana.net/wp-content/uploads/2026/03/image-3.png 605w, https://blog.osakana.net/wp-content/uploads/2026/03/image-3-300x300.png 300w, https://blog.osakana.net/wp-content/uploads/2026/03/image-3-150x150.png 150w, https://blog.osakana.net/wp-content/uploads/2026/03/image-3-100x100.png 100w" sizes="auto, (max-width: 605px) 100vw, 605px" /></a></figure>
]]></content:encoded>
					
					<wfw:commentRss>https://blog.osakana.net/archives/16841/feed</wfw:commentRss>
			<slash:comments>0</slash:comments>
		
		
			</item>
		<item>
		<title>Nutanix CE 2.1(AOS 6.8.1)をRyzen 3700UのESXi 8上で構築したときのメモ 2026/04/03版</title>
		<link>https://blog.osakana.net/archives/17041</link>
					<comments>https://blog.osakana.net/archives/17041#respond</comments>
		
		<dc:creator><![CDATA[osakanataro]]></dc:creator>
		<pubDate>Thu, 09 Apr 2026 09:05:56 +0000</pubDate>
				<category><![CDATA[Nutanix]]></category>
		<category><![CDATA[仮想化]]></category>
		<guid isPermaLink="false">https://blog.osakana.net/?p=17041</guid>

					<description><![CDATA[各仮想環境で作成した仮想マシンハードウェアのlspci上での見た目の違いを確認しようと思って、Nutanix CE環境を新規で構築した そのときに迷ったことのメモ 入手について 公式には「Nutanix Communit &#8230; <p class="link-more"><a href="https://blog.osakana.net/archives/17041" class="more-link"><span class="screen-reader-text">"Nutanix CE 2.1(AOS 6.8.1)をRyzen 3700UのESXi 8上で構築したときのメモ 2026/04/03版" の</span>続きを読む</a></p>]]></description>
										<content:encoded><![CDATA[
<p class="wp-block-paragraph">各仮想環境で作成した仮想マシンハードウェアのlspci上での見た目の違いを確認しようと思って、Nutanix CE環境を新規で構築した</p>



<p class="wp-block-paragraph">そのときに迷ったことのメモ</p>



<h2 class="wp-block-heading">入手について</h2>



<p class="wp-block-paragraph">公式には「<a href="https://www.nutanix.com/ja/products/community-edition">Nutanix Communitiy Edition</a>」のページから遷移することになるがめんどくさい</p>



<p class="wp-block-paragraph">マニュアル「<a href="https://portal.nutanix.com/page/documents/details?targetId=Nutanix-Community-Edition-Getting-Started-v2_1:Nutanix-Community-Edition-Getting-Started-v2_1">Getting Started with Community Edition</a>」</p>



<p class="wp-block-paragraph">リリースノートなどは、サポート契約を要求されていて読むことは出来ない</p>



<p class="wp-block-paragraph">ソフトウェアのダウンロードは「<a href="https://next.nutanix.com/discussion-forum-14/download-community-edition-38417">Download Community Edition</a>」から行う</p>



<p class="wp-block-paragraph">2026/04/03時点でも、2024/08/19リリースの phoenix.x86_64-fnd_5.6.1_patch-aos_6.8.1_ga.iso が最新である模様</p>



<p class="wp-block-paragraph">CE 2.1はAOS 6.8.1ですが、通常版は<a href="https://next.nutanix.com/product-updates/aos-7-3-0-1-44672">現在 AOS 7.3.0.1</a> である模様</p>



<h2 class="wp-block-heading">インストールについて</h2>



<p class="wp-block-paragraph">ESXi 8の場合、「CPU ハードウェア仮想化:ハードウェア アシストによる仮想化をゲスト OS に公開」と「UEFI Secure boot 無効化」だけでいけるかと思いきや</p>



<p class="wp-block-paragraph">インストーラが途中で/dev/sdbが見つからないとして失敗</p>



<p class="wp-block-paragraph">NTNX日記の「<a href="https://blog.ntnx.jp/entry/2024/09/15/225354">ESXi で Nested Nutanix CE を構成してみる。（CE 2.1 / AOS 6.8.1 版）</a>」に書いてある「1つめのハード ディスクは、デフォルトで作成されるものを 32GB に変更するか、いったん削除して再作成します。」がポイントだとは思いませんでした。</p>



<p class="wp-block-paragraph">ゲストOSの種類はNTNX日記だと「Red Hat Enterprise Linux 8 (64 ビット)」だったのでそれで作ったのですが、open-vm-toolsを追加したところ「その他のLinux 6.x 以降(64ビット)」だ、と言われました。</p>



<p class="wp-block-paragraph">初回ログイン時のユーザ情報は「<a href="https://portal.nutanix.com/page/documents/details?targetId=Nutanix-Community-Edition-Getting-Started-v2_1:top-cluster-config-ce-t.html">Creating and Configuring a Cluster</a>」を参照</p>



<p class="wp-block-paragraph">AHVは「root」「nutanix/4u」<br>CVMは「nutanix」「nutanix/4u」<br>Web UIは「admin」「nutanix/4u」初回ログイン時にパスワード変更が求められるが制限がきつめ</p>



<p class="wp-block-paragraph">Web初回ログイン時にNEXTアカウントを要求されるが、Nutanix NEXTのMy profileで表示されるユーザ名ではなく「メールアドレス」を入力する</p>



<h2 class="wp-block-heading">その他メモ</h2>



<h3 class="wp-block-heading">LCMの動作にアクセスできるNTPサーバは必須</h3>



<p class="wp-block-paragraph">初期設定ではNTPサーバとして0.pool.ntp.org と 1.pool.ntp.org が登録されている</p>



<p class="wp-block-paragraph">これらにアクセスできないとLCMでのInventoryが失敗する</p>



<figure class="wp-block-image size-large"><a href="https://blog.osakana.net/wp-content/uploads/2026/04/6A536BC8-330C-4335-8F8D-D1ACFD36ACD5.png"><img loading="lazy" decoding="async" width="1024" height="461" src="https://blog.osakana.net/wp-content/uploads/2026/04/6A536BC8-330C-4335-8F8D-D1ACFD36ACD5-1024x461.png" alt="" class="wp-image-17043" srcset="https://blog.osakana.net/wp-content/uploads/2026/04/6A536BC8-330C-4335-8F8D-D1ACFD36ACD5-1024x461.png 1024w, https://blog.osakana.net/wp-content/uploads/2026/04/6A536BC8-330C-4335-8F8D-D1ACFD36ACD5-300x135.png 300w, https://blog.osakana.net/wp-content/uploads/2026/04/6A536BC8-330C-4335-8F8D-D1ACFD36ACD5-768x346.png 768w, https://blog.osakana.net/wp-content/uploads/2026/04/6A536BC8-330C-4335-8F8D-D1ACFD36ACD5.png 1500w" sizes="auto, (max-width: 767px) 89vw, (max-width: 1000px) 54vw, (max-width: 1071px) 543px, 580px" /></a></figure>


<div class="wp-block-syntaxhighlighter-code "><pre class="brush: bash; title: ; notranslate">
error alert
Lcm prechecks detected 1 issue that would cause upgrade failures.

Check &#039;test_ntp_server_reachability&#039; failed: Failure reason: Cannot upgrade if the configured NTP server(s): &#x5B;&#039;0.pool.ntp.org&#039;, &#039;1.pool.ntp.org&#039;] are not reachable. For details read article 6401
</pre></div>


<p class="wp-block-paragraph">設定してあるのに上記エラーが出ているというときに、Hypervisor側でNTP動作状況確認のコマンドを実行</p>


<div class="wp-block-syntaxhighlighter-code "><pre class="brush: bash; title: ; notranslate">
&#x5B;root@NTNX-4bc9a811-A ~]# chronyc -n sources -v

  .-- Source mode  &#039;^&#039; = server, &#039;=&#039; = peer, &#039;#&#039; = local clock.
 / .- Source state &#039;*&#039; = current best, &#039;+&#039; = combined, &#039;-&#039; = not combined,
| /             &#039;x&#039; = may be in error, &#039;~&#039; = too variable, &#039;?&#039; = unusable.
||                                                 .- xxxx &#x5B; yyyy ] +/- zzzz
||      Reachability register (octal) -.           |  xxxx = adjusted offset,
||      Log2(Polling interval) --.      |          |  yyyy = measured offset,
||                                \     |          |  zzzz = estimated error.
||                                 |    |           \
MS Name/IP address         Stratum Poll Reach LastRx Last sample
===============================================================================
^? 163.5.56.11                   0   9     0     -     +0ns&#x5B;   +0ns] +/-    0ns
^? 109.61.109.140                0   9     0     -     +0ns&#x5B;   +0ns] +/-    0ns
^? 192.168.1.1                   0   8     0     -     +0ns&#x5B;   +0ns] +/-    0ns
&#x5B;root@NTNX-4bc9a811-A ~]#
</pre></div>


<p class="wp-block-paragraph">hypervisor階層では問題無く動作している模様</p>



<p class="wp-block-paragraph">CVMの方を確認すると、設定されていないように見える</p>


<div class="wp-block-syntaxhighlighter-code "><pre class="brush: bash; title: ; notranslate">
nutanix@NTNX-4bc9a811-A-CVM:192.168.1.14:~$ sudo chronyc -n sources -v

  .-- Source mode  &#039;^&#039; = server, &#039;=&#039; = peer, &#039;#&#039; = local clock.
 / .- Source state &#039;*&#039; = current best, &#039;+&#039; = combined, &#039;-&#039; = not combined,
| /             &#039;x&#039; = may be in error, &#039;~&#039; = too variable, &#039;?&#039; = unusable.
||                                                 .- xxxx &#x5B; yyyy ] +/- zzzz
||      Reachability register (octal) -.           |  xxxx = adjusted offset,
||      Log2(Polling interval) --.      |          |  yyyy = measured offset,
||                                \     |          |  zzzz = estimated error.
||                                 |    |           \
MS Name/IP address         Stratum Poll Reach LastRx Last sample
===============================================================================
nutanix@NTNX-4bc9a811-A-CVM:192.168.1.14:~$
</pre></div>


<p class="wp-block-paragraph">実際設定ファイルにもない</p>


<div class="wp-block-syntaxhighlighter-code "><pre class="brush: bash; title: ; notranslate">
nutanix@NTNX-4bc9a811-A-CVM:192.168.1.14:~$ sudo cat /etc/chrony.conf
# Auto generated by ChronyConfig on Thu Jul  9 01:28:04 2026

local stratum 10
driftfile /var/lib/chrony/drift
maxdistance 16.0
makestep 1.0 3
rtcsync
allow 0.0.0.0/0
allow 127.0.0.1
allow ::/0
allow ::1
leapsectz right/UTC
cmdport 0
logdir /var/log/chrony
log measurements statistics tracking
nutanix@NTNX-4bc9a811-A-CVM:192.168.1.14:~
</pre></div>


<p class="wp-block-paragraph">hypervisorの方の /etc/chrony.confを確認すると、こちらにはNTPサーバ設定はある</p>


<div class="wp-block-syntaxhighlighter-code "><pre class="brush: bash; title: ; notranslate">
&#x5B;root@NTNX-4bc9a811-A ~]# cat /etc/chrony.conf
# Use public servers from the pool.ntp.org project.
# Please consider joining the pool (http://www.pool.ntp.org/join.html).

# Record the rate at which the system clock gains/losses time.
driftfile /var/lib/chrony/drift

# Allow the system clock to be stepped in the first three updates
# if its offset is larger than 1 second.

# Enable kernel synchronization of the real-time clock (RTC).
rtcsync

# Enable hardware timestamping on all interfaces that support it.
#hwtimestamp *

# Increase the minimum number of selectable sources required to adjust
# the system clock.
#minsources 2

# Allow NTP client access from local network.
#allow 192.168.0.0/16

# Serve time even if not synchronized to a time source.
#local stratum 10

# Specify file containing keys for NTP authentication.
keyfile /etc/chrony.keys

# Get TAI-UTC offset and leap seconds from the system tz database.
leapsectz right/UTC

# Specify directory for log files.
logdir /var/log/chrony

# Select which information is logged.
#log measurements statistics tracking
port 0
cmdport 0
server 1.pool.ntp.org maxpoll 10 iburst
server 0.pool.ntp.org maxpoll 10 iburst
server 192.168.1.1 maxpoll 10 iburst
&#x5B;root@NTNX-4bc9a811-A ~]#
</pre></div>


<p class="wp-block-paragraph">ncli clusterコマンドでNTPサーバ一覧を取得すると、サーバ群は登録されていることになっている</p>


<div class="wp-block-syntaxhighlighter-code "><pre class="brush: bash; title: ; notranslate">
nutanix@NTNX-4bc9a811-A-CVM:192.168.1.14:~$ ncli cluster get-ntp-servers

    NTP Servers               : 0.pool.ntp.org, 1.pool.ntp.org, 192.168.1.1
nutanix@NTNX-4bc9a811-A-CVM:192.168.1.14:~$
</pre></div>


<p class="wp-block-paragraph">CVM内部からNTPサーバ群へのNTPポート123へのアクセスは成功する</p>


<div class="wp-block-syntaxhighlighter-code "><pre class="brush: bash; title: ; notranslate">
nutanix@NTNX-4bc9a811-A-CVM:192.168.1.14:~$ nc -vz -u 192.168.1.1 123
Ncat: Version 7.92 ( https://nmap.org/ncat )
Ncat: Connected to 192.168.1.1:123.
Ncat: UDP packet sent successfully
Ncat: 1 bytes sent, 0 bytes received in 2.02 seconds.
nutanix@NTNX-4bc9a811-A-CVM:192.168.1.14:~$ nc -vz -u 163.5.56.11 123
Ncat: Version 7.92 ( https://nmap.org/ncat )
Ncat: Connected to 163.5.56.11:123.
Ncat: UDP packet sent successfully
Ncat: 1 bytes sent, 0 bytes received in 2.01 seconds.
nutanix@NTNX-4bc9a811-A-CVM:192.168.1.14:~$ nc -vz -u 109.61.109.140 123
Ncat: Version 7.92 ( https://nmap.org/ncat )
Ncat: Connected to 109.61.109.140:123.
Ncat: UDP packet sent successfully
Ncat: 1 bytes sent, 0 bytes received in 2.02 seconds.
nutanix@NTNX-4bc9a811-A-CVM:192.168.1.14:~$
</pre></div>


<p class="wp-block-paragraph">とりあえずCVMの/etc/chrony.confを直接編集してみた</p>


<div class="wp-block-syntaxhighlighter-code "><pre class="brush: bash; title: ; notranslate">
nutanix@NTNX-4bc9a811-A-CVM:192.168.1.14:~$ sudo vi /etc/chrony.conf
nutanix@NTNX-4bc9a811-A-CVM:192.168.1.14:~$ sudo cat /etc/chrony.conf
# Auto generated by ChronyConfig on Thu Jul  9 01:28:04 2026

local stratum 10
driftfile /var/lib/chrony/drift
maxdistance 16.0
makestep 1.0 3
rtcsync
allow 0.0.0.0/0
allow 127.0.0.1
allow ::/0
allow ::1
leapsectz right/UTC
cmdport 0
logdir /var/log/chrony
log measurements statistics tracking
server 192.168.1.1 maxpoll 10 iburst
nutanix@NTNX-4bc9a811-A-CVM:192.168.1.14:~$ sudo systemctl restart chronyd
nutanix@NTNX-4bc9a811-A-CVM:192.168.1.14:~$ sudo chronyc -n sources -v

  .-- Source mode  &#039;^&#039; = server, &#039;=&#039; = peer, &#039;#&#039; = local clock.
 / .- Source state &#039;*&#039; = current best, &#039;+&#039; = combined, &#039;-&#039; = not combined,
| /             &#039;x&#039; = may be in error, &#039;~&#039; = too variable, &#039;?&#039; = unusable.
||                                                 .- xxxx &#x5B; yyyy ] +/- zzzz
||      Reachability register (octal) -.           |  xxxx = adjusted offset,
||      Log2(Polling interval) --.      |          |  yyyy = measured offset,
||                                \     |          |  zzzz = estimated error.
||                                 |    |           \
MS Name/IP address         Stratum Poll Reach LastRx Last sample
===============================================================================
^? 192.168.1.1                   0   6     0     -     +0ns&#x5B;   +0ns] +/-    0ns
nutanix@NTNX-4bc9a811-A-CVM:192.168.1.14:~$
</pre></div>


<p class="wp-block-paragraph">とりあえずNTPを使えるようにした</p>



<p class="wp-block-paragraph">CLIでcheck_ntpを実行</p>


<div class="wp-block-syntaxhighlighter-code "><pre class="brush: bash; title: ; notranslate">
nutanix@NTNX-4bc9a811-A-CVM:192.168.1.14:~$ ncc health_checks network_checks check_ntp

####################################################
# TIMESTAMP : Thu Jul 09 01:52:10 2026 (UTC +0000) #
####################################################
Cluster Name: cvm
Cluster Id: 3772327690115644291
Cluster UUID: 00064e84-58d6-fd69-345a-000c29b67b83
Cluster Version: 6.8.1
NCC Version: 5.0.1-83db8d0f
    CVM ID(Svmid)            : 2
    CVM external IP          : 192.168.1.14
    Hypervisor IP            : 192.168.1.13
    Hypervisor version       : Nutanix 20230302.101026
    Node serial              : 61e640f9-e1fe-4ba3-a4cc-8c2384c95c9a
    Model                    : CommunityEdition
    Node Position            : A
    Block S/N                : 4bc9a811


Running : health_checks network_checks check_ntp
&#x5B;==================================================] 100%
/health_checks/network_checks/check_ntp                                              &#x5B; WARN ]
---------------------------------------------------------------------------------------------+

Detailed information for check_ntp:
Node 192.168.1.14:
WARN: NTP servers configured on CVM (&#x5B;&#039;192.168.1.1&#039;]) differ from those configured in the cluster (&#x5B;&#039;0.pool.ntp.org&#039;, &#039;1.pool.ntp.org&#039;, &#039;192.168.1.1&#039;]).
WARN: The host (192.168.1.13) is not synchronizing with any NTP server. This might occur if none of the configured NTP servers are available or you are currently experiencing network instability determined by the high offset/high jitter.
Refer to KB 4519 (http://portal.nutanix.com/kb/4519) for details on check_ntp or Recheck with: ncc health_checks network_checks check_ntp --cvm_list=192.168.1.14
+-----------------------+
| State         | Count |
+-----------------------+
| Warning       | 1     |
| Total Plugins | 1     |
+-----------------------+
Plugin output written to /home/nutanix/data/logs/ncc-output-latest.log
nutanix@NTNX-4bc9a811-A-CVM:192.168.1.14:~$
</pre></div>


<p class="wp-block-paragraph">NTPサーバ群の数が違うのでダメか</p>


<div class="wp-block-syntaxhighlighter-code "><pre class="brush: bash; title: ; notranslate">
nutanix@NTNX-4bc9a811-A-CVM:192.168.1.14:~$ sudo vi /etc/chrony.conf
nutanix@NTNX-4bc9a811-A-CVM:192.168.1.14:~$ sudo cat /etc/chrony.conf
# Auto generated by ChronyConfig on Thu Jul  9 01:28:04 2026

local stratum 10
driftfile /var/lib/chrony/drift
maxdistance 16.0
makestep 1.0 3
rtcsync
allow 0.0.0.0/0
allow 127.0.0.1
allow ::/0
allow ::1
leapsectz right/UTC
cmdport 0
logdir /var/log/chrony
log measurements statistics tracking
server 192.168.1.1 maxpoll 10 iburst
server 1.pool.ntp.org maxpoll 10 iburst
server 0.pool.ntp.org maxpoll 10 iburst
nutanix@NTNX-4bc9a811-A-CVM:192.168.1.14:~$ sudo systemctl restart chronyd
nutanix@NTNX-4bc9a811-A-CVM:192.168.1.14:~$ sudo chronyc -n sources -v

  .-- Source mode  &#039;^&#039; = server, &#039;=&#039; = peer, &#039;#&#039; = local clock.
 / .- Source state &#039;*&#039; = current best, &#039;+&#039; = combined, &#039;-&#039; = not combined,
| /             &#039;x&#039; = may be in error, &#039;~&#039; = too variable, &#039;?&#039; = unusable.
||                                                 .- xxxx &#x5B; yyyy ] +/- zzzz
||      Reachability register (octal) -.           |  xxxx = adjusted offset,
||      Log2(Polling interval) --.      |          |  yyyy = measured offset,
||                                \     |          |  zzzz = estimated error.
||                                 |    |           \
MS Name/IP address         Stratum Poll Reach LastRx Last sample
===============================================================================
^? 192.168.1.1                   0   6     0     -     +0ns&#x5B;   +0ns] +/-    0ns
^? 122.215.240.52                0   6     0     -     +0ns&#x5B;   +0ns] +/-    0ns
^? 46.250.253.227                0   6     0     -     +0ns&#x5B;   +0ns] +/-    0ns
nutanix@NTNX-4bc9a811-A-CVM:192.168.1.14:~$
</pre></div>


<p class="wp-block-paragraph">再チェック</p>


<div class="wp-block-syntaxhighlighter-code "><pre class="brush: bash; title: ; notranslate">
nutanix@NTNX-4bc9a811-A-CVM:192.168.1.14:~$ ncc health_checks network_checks check_ntp

####################################################
# TIMESTAMP : Thu Jul 09 01:57:28 2026 (UTC +0000) #
####################################################
Cluster Name: cvm
Cluster Id: 3772327690115644291
Cluster UUID: 00064e84-58d6-fd69-345a-000c29b67b83
Cluster Version: 6.8.1
NCC Version: 5.0.1-83db8d0f
    CVM ID(Svmid)            : 2
    CVM external IP          : 192.168.1.14
    Hypervisor IP            : 192.168.1.13
    Hypervisor version       : Nutanix 20230302.101026
    Node serial              : 61e640f9-e1fe-4ba3-a4cc-8c2384c95c9a
    Model                    : CommunityEdition
    Node Position            : A
    Block S/N                : 4bc9a811


Running : health_checks network_checks check_ntp
&#x5B;==================================================] 100%
/health_checks/network_checks/check_ntp                                              &#x5B; ERR  ]
---------------------------------------------------------------------------------------------+

Detailed information for check_ntp:
Node 192.168.1.14:
ERR : node (service_vm_id: 2) : NTP synchronized to server which is neither in the cluster nor in the list of allowed NTP servers
WARN: The host (192.168.1.13) is not synchronizing with any NTP server. This might occur if none of the configured NTP servers are available or you are currently experiencing network instability determined by the high offset/high jitter.
Refer to KB 4519 (http://portal.nutanix.com/kb/4519) for details on check_ntp or Recheck with: ncc health_checks network_checks check_ntp --cvm_list=192.168.1.14

One or more plugins generated ERROR as there were insufficient data to validate results. Please resolve other reported issues and re-run the health checks.
+-----------------------+
| State         | Count |
+-----------------------+
| Error         | 1     |
| Total Plugins | 1     |
+-----------------------+
Plugin output written to /home/nutanix/data/logs/ncc-output-latest.log
nutanix@NTNX-4bc9a811-A-CVM:192.168.1.14:~$
</pre></div>


<p class="wp-block-paragraph"><a href="https://portal.nutanix.com/kb/16363" target="_blank" rel="noreferrer noopener">KB-16363</a> を参照してみると、「sudo chronyc tracking」を実行して「Reference ID」のところにNTPサーバ名が出てるか確認、とある・・・ない</p>


<div class="wp-block-syntaxhighlighter-code "><pre class="brush: bash; title: ; notranslate">
nutanix@NTNX-4bc9a811-A-CVM:192.168.1.14:~$ sudo chronyc tracking
Reference ID    : 7F7F0101 ()
Stratum         : 10
Ref time (UTC)  : Thu Jul 09 02:06:19 2026
System time     : 0.000000004 seconds slow of NTP time
Last offset     : +0.000000000 seconds
RMS offset      : 0.000000000 seconds
Frequency       : 5.919 ppm slow
Residual freq   : +0.000 ppm
Skew            : 0.000 ppm
Root delay      : 0.000000000 seconds
Root dispersion : 0.000000000 seconds
Update interval : 0.0 seconds
Leap status     : Normal
nutanix@NTNX-4bc9a811-A-CVM:192.168.1.14:~$

&#x5B;root@NTNX-4bc9a811-A ~]# chronyc tracking
Reference ID    : 00000000 ()
Stratum         : 0
Ref time (UTC)  : Thu Jan 01 00:00:00 1970
System time     : 0.000000000 seconds slow of NTP time
Last offset     : +0.000000000 seconds
RMS offset      : 0.000000000 seconds
Frequency       : 5.788 ppm slow
Residual freq   : +0.000 ppm
Skew            : 0.000 ppm
Root delay      : 1.000000000 seconds
Root dispersion : 1.000000000 seconds
Update interval : 0.0 seconds
Leap status     : Not synchronised
&#x5B;root@NTNX-4bc9a811-A ~]#
</pre></div>


<p class="wp-block-paragraph">いろいろ試行していたところ、結局のところopenwrtで提供しようとしていたNTPに問題が出ていたようなので、別のLinuxでchronydによるNTPサーバを立てて見たところ、そちらではなんとかなった</p>


<div class="wp-block-syntaxhighlighter-code "><pre class="brush: bash; title: ; notranslate">
nutanix@NTNX-4bc9a811-A-CVM:192.168.1.14:~$ ncc health_checks network_checks check_ntp --cvm_list=192.168.1.14

####################################################
# TIMESTAMP : Thu Jul 09 06:07:56 2026 (UTC +0000) #
####################################################
Cluster Name: cvm
Cluster Id: 3772327690115644291
Cluster UUID: 00064e84-58d6-fd69-345a-000c29b67b83
Cluster Version: 6.8.1
NCC Version: 5.0.1-83db8d0f
    CVM ID(Svmid)            : 2
    CVM external IP          : 192.168.1.14
    Hypervisor IP            : 192.168.1.13
    Hypervisor version       : Nutanix 20230302.101026
    Node serial              : 61e640f9-e1fe-4ba3-a4cc-8c2384c95c9a
    Model                    : CommunityEdition
    Node Position            : A
    Block S/N                : 4bc9a811


Running : health_checks network_checks check_ntp
&#x5B;==================================================] 100%
/health_checks/network_checks/check_ntp                                              &#x5B; WARN ]
---------------------------------------------------------------------------------------------+

Detailed information for check_ntp:
Node 192.168.1.14:
WARN: NTP servers configured on CVM (&#x5B;&#039;0.pool.ntp.org&#039;, &#039;192.168.1.1&#039;, &#039;1.pool.ntp.org&#039;]) differ from those configured in the cluster (&#x5B;&#039;0.pool.ntp.org&#039;, &#039;1.pool.ntp.org&#039;, &#039;192.168.1.1&#039;, &#039;192.168.1.10&#039;]).
Refer to KB 4519 (http://portal.nutanix.com/kb/4519) for details on check_ntp or Recheck with: ncc health_checks network_checks check_ntp --cvm_list=192.168.1.14
+-----------------------+
| State         | Count |
+-----------------------+
| Warning       | 1     |
| Total Plugins | 1     |
+-----------------------+
Plugin output written to /home/nutanix/data/logs/ncc-output-latest.log
nutanix@NTNX-4bc9a811-A-CVM:192.168.1.14:~$
</pre></div>


<p class="wp-block-paragraph">CVM内の/etc/chrony.confも書き換わっていた</p>


<div class="wp-block-syntaxhighlighter-code "><pre class="brush: bash; title: ; notranslate">
nutanix@NTNX-4bc9a811-A-CVM:192.168.1.14:~$ sudo cat /etc/chrony.conf
# Auto generated by ChronyConfig on Thu Jul  9 06:11:50 2026

pool 0.pool.ntp.org iburst maxpoll 10
server 192.168.1.10 iburst maxpoll 10
pool 1.pool.ntp.org iburst maxpoll 10
server 192.168.1.1 iburst maxpoll 10
local stratum 10
driftfile /var/lib/chrony/drift
maxdistance 16.0
makestep 1.0 3
rtcsync
allow 0.0.0.0/0
allow 127.0.0.1
allow ::/0
allow ::1
leapsectz right/UTC
cmdport 0
logdir /var/log/chrony
log measurements statistics tracking
nutanix@NTNX-4bc9a811-A-CVM:192.168.1.14:~$
</pre></div>]]></content:encoded>
					
					<wfw:commentRss>https://blog.osakana.net/archives/17041/feed</wfw:commentRss>
			<slash:comments>0</slash:comments>
		
		
			</item>
		<item>
		<title>ESP32 C3 SuperMiniをUbuntu 24.04で使うときのメモ</title>
		<link>https://blog.osakana.net/archives/17053</link>
					<comments>https://blog.osakana.net/archives/17053#respond</comments>
		
		<dc:creator><![CDATA[osakanataro]]></dc:creator>
		<pubDate>Wed, 08 Apr 2026 03:03:48 +0000</pubDate>
				<category><![CDATA[Arduino]]></category>
		<category><![CDATA[Arduinoプログラム]]></category>
		<category><![CDATA[CPU]]></category>
		<category><![CDATA[ESP]]></category>
		<category><![CDATA[ESP8266 / ESP32]]></category>
		<category><![CDATA[ESP8266 / ESP32 搭載機]]></category>
		<category><![CDATA[プログラム]]></category>
		<category><![CDATA[工作]]></category>
		<guid isPermaLink="false">https://blog.osakana.net/?p=17053</guid>

					<description><![CDATA[ある一定温度になったら5Vファンを回す、程度の制御に使うマイコンとしてなんか買うか、とaliexpress見てたら、506円で ESP32 C3 SuperMiniというのがあったので買ってみた 購入したセラーのページに &#8230; <p class="link-more"><a href="https://blog.osakana.net/archives/17053" class="more-link"><span class="screen-reader-text">"ESP32 C3 SuperMiniをUbuntu 24.04で使うときのメモ" の</span>続きを読む</a></p>]]></description>
										<content:encoded><![CDATA[
<p class="wp-block-paragraph">ある一定温度になったら5Vファンを回す、程度の制御に使うマイコンとしてなんか買うか、とaliexpress見てたら、506円で ESP32 C3 SuperMiniというのがあったので買ってみた</p>



<a href="https://s.click.aliexpress.com/e/_c2uj2Y3B" target="_blank"><img decoding="async" src="//ae01.alicdn.com/kf/S9fcbdf33bbf049cf9ffa0f22978e3dd6z.jpg_350x350.jpg" /></a>



<figure class="wp-block-image size-full"><a href="https://blog.osakana.net/wp-content/uploads/2026/04/image.png"><img loading="lazy" decoding="async" width="561" height="339" src="https://blog.osakana.net/wp-content/uploads/2026/04/image.png" alt="" class="wp-image-17055" srcset="https://blog.osakana.net/wp-content/uploads/2026/04/image.png 561w, https://blog.osakana.net/wp-content/uploads/2026/04/image-300x181.png 300w" sizes="auto, (max-width: 561px) 100vw, 561px" /></a></figure>



<figure class="wp-block-image size-full"><a href="https://blog.osakana.net/wp-content/uploads/2026/04/image-1.png"><img loading="lazy" decoding="async" width="458" height="282" src="https://blog.osakana.net/wp-content/uploads/2026/04/image-1.png" alt="" class="wp-image-17056" srcset="https://blog.osakana.net/wp-content/uploads/2026/04/image-1.png 458w, https://blog.osakana.net/wp-content/uploads/2026/04/image-1-300x185.png 300w" sizes="auto, (max-width: 458px) 100vw, 458px" /></a></figure>



<p class="wp-block-paragraph">購入したセラーのページには詳細がなかったので、調べてみたら、「<a href="https://tamanegi-digick.com/it/smc3/">【Arduino】ESP32 C3 SuperMiniを使う</a>」を発見</p>



<p class="wp-block-paragraph">ESP32 C3 SuperMini という製品名に対して、細かなバージョン違いがあるらしい。</p>



<p class="wp-block-paragraph">掲載されている写真の部品配置と比較してみたところ、今回買ったものは「ESP32 C3 Super Mini(K2)」に相当しているみたいである</p>



<p class="wp-block-paragraph">で・・・Ubuntu 24.04Serverをインストールして、arduinoをインストールし、Windows上にインストールした<a href="https://github.com/marchaesen/vcxsrv/">VcXsrv</a>に画面を飛ばす。</p>



<p class="wp-block-paragraph">Arduiono上では、ボードマネージャにESP32追加し、ESP32 C3 Dev boardを選択して、サンプルを書き込み</p>



<figure class="wp-block-image size-large"><a href="https://blog.osakana.net/wp-content/uploads/2026/04/image-2.png"><img loading="lazy" decoding="async" width="1024" height="760" src="https://blog.osakana.net/wp-content/uploads/2026/04/image-2-1024x760.png" alt="" class="wp-image-17057" srcset="https://blog.osakana.net/wp-content/uploads/2026/04/image-2-1024x760.png 1024w, https://blog.osakana.net/wp-content/uploads/2026/04/image-2-300x223.png 300w, https://blog.osakana.net/wp-content/uploads/2026/04/image-2-768x570.png 768w, https://blog.osakana.net/wp-content/uploads/2026/04/image-2.png 1194w" sizes="auto, (max-width: 767px) 89vw, (max-width: 1000px) 54vw, (max-width: 1071px) 543px, 580px" /></a></figure>



<p class="wp-block-paragraph">エラー発生</p>


<div class="wp-block-syntaxhighlighter-code "><pre class="brush: bash; title: ; notranslate">
Arduino：1.8.19 (Linux), ボード：&quot;ESP32C3 Dev Module, Disabled, Disabled, Default 4MB with spiffs (1.2MB APP/1.5MB SPIFFS), 160MHz (WiFi), QIO, 80MHz, 4MB (32Mb), 921600, None, Disabled, Disabled&quot;

警告：ライブラリESP_SRのカテゴリ「Sound」は有効ではありません。「Uncategorized」に設定します。
警告：ライブラリHashのカテゴリ「Security」は有効ではありません。「Uncategorized」に設定します。
警告：ライブラリESP Insightsのカテゴリ「」は有効ではありません。「Uncategorized」に設定します。
警告：ライブラリESP RainMakerのカテゴリ「」は有効ではありません。「Uncategorized」に設定します。
警告：ライブラリTFLite Microのカテゴリ「」は有効ではありません。「Uncategorized」に設定します。
警告：ライブラリWiFiProvのカテゴリ「」は有効ではありません。「Uncategorized」に設定します。
最大1310720バイトのフラッシュメモリのうち、スケッチが282882バイト（21%）を使っています。
最大327680バイトのRAMのうち、グローバル変数が14240バイト（4%）を使っていて、ローカル変数で313440バイト使うことができます。
                                                                                
 Usage: esptool &#x5B;OPTIONS] COMMAND &#x5B;ARGS]...                                     
                                                                                
 Try &#039;esptool -h&#039; for help                                                      
╭─ Error ──────────────────────────────────────────────────────────────────────╮
│ Invalid value for &#039;--port&#039; / &#039;-p&#039;: Path &#039;/dev/ttyACM0&#039; is not readable.      │
╰──────────────────────────────────────────────────────────────────────────────╯
                                                                                
シリアルポート「                                                                                
」が選択されていますが、そのポートは存在しないか、ボードが接続されていません。


「ファイル」メニューの「環境設定」から
「より詳細な情報を表示する：コンパイル」を有効にすると
より詳しい情報が表示されます。

</pre></div>


<p class="wp-block-paragraph">確認してみる</p>



<p class="wp-block-paragraph">まず、USBデバイスが存在しているかを確認</p>


<div class="wp-block-syntaxhighlighter-code "><pre class="brush: bash; title: ; notranslate">
pcuser@ubuntu:~$ lsusb
Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
Bus 001 Device 002: ID 0e0f:0003 VMware, Inc. Virtual Mouse
Bus 001 Device 007: ID 0e0f:0002 VMware, Inc. Virtual USB Hub
Bus 001 Device 008: ID 0e0f:0002 VMware, Inc. Virtual USB Hub
Bus 001 Device 022: ID 303a:1001 Espressif USB JTAG/serial debug unit
Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
pcuser@ubuntu:~$
</pre></div>


<p class="wp-block-paragraph">ある</p>



<p class="wp-block-paragraph">rootユーザでesptoolを実行したらどうなる？</p>


<div class="wp-block-syntaxhighlighter-code "><pre class="brush: bash; title: ; notranslate">
root@ubuntu:~# /home/pcuser/.arduino15/packages/esp32/tools/esptool_py/5.1.0/esptool --port /dev/ttyACM0 chip-id
esptool v5.1.0
Connected to ESP32-C3 on /dev/ttyACM0:
Chip type:          ESP32-C3 (QFN32) (revision v0.4)
Features:           Wi-Fi, BT 5 (LE), Single Core, 160MHz, Embedded Flash 4MB (XMC)
Crystal frequency:  40MHz
USB mode:           USB-Serial/JTAG
MAC:                ac:eb:e6:6d:6b:b0

Stub flasher running.

Warning: ESP32-C3 has no chip ID. Reading MAC address instead.
MAC:                ac:eb:e6:6d:6b:b0

Hard resetting via RTS pin...
root@ubuntu:~#
</pre></div>


<p class="wp-block-paragraph">情報が取得できる</p>



<p class="wp-block-paragraph">一般ユーザだとどうなる？</p>


<div class="wp-block-syntaxhighlighter-code "><pre class="brush: bash; title: ; notranslate">
pcuser@ubuntu:~$ /home/pcuser/.arduino15/packages/esp32/tools/esptool_py/5.1.0/esptool --port /dev/ttyACM0 chip-id

 Usage: esptool &#x5B;OPTIONS] COMMAND &#x5B;ARGS]...

 Try &#039;esptool -h&#039; for help
lq Error qqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqk
x Invalid value for &#039;--port&#039; / &#039;-p&#039;: Path &#039;/dev/ttyACM0&#039; is not readable.     x
mqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqj

pcuser@ubuntu:~$
</pre></div>


<p class="wp-block-paragraph">エラーとなる</p>



<p class="wp-block-paragraph">つまり・・・/dev/ttyACM0 にアクセス権がない</p>


<div class="wp-block-syntaxhighlighter-code "><pre class="brush: bash; title: ; notranslate">
pcuser@ubuntu:~$ ls -l /dev/ttyACM0
crw-rw---- 1 root dialout 166, 0  4月  8 11:40 /dev/ttyACM0
pcuser@ubuntu:~$
</pre></div>


<p class="wp-block-paragraph">面倒くさいので /dev/ttyACM0自体に権限を与えてしまう</p>


<div class="wp-block-syntaxhighlighter-code "><pre class="brush: bash; title: ; notranslate">
pcuser@ubuntu:~$ sudo chmod a+rw /dev/ttyACM0
&#x5B;sudo] pcuser のパスワード:
pcuser@ubuntu:~$ ls -l /dev/ttyACM0
crw-rw-rw- 1 root dialout 166, 0  4月  8 11:40 /dev/ttyACM0
pcuser@ubuntu:~$
</pre></div>


<p class="wp-block-paragraph">変更後は一般ユーザでもesptoolの実行に成功した</p>


<div class="wp-block-syntaxhighlighter-code "><pre class="brush: bash; title: ; notranslate">
pcuser@ubuntu:~$ /home/pcuser/.arduino15/packages/esp32/tools/esptool_py/5.1.0/esptool --port /dev/ttyACM0 chip-id
esptool v5.1.0
Connected to ESP32-C3 on /dev/ttyACM0:
Chip type:          ESP32-C3 (QFN32) (revision v0.4)
Features:           Wi-Fi, BT 5 (LE), Single Core, 160MHz, Embedded Flash 4MB (XMC)
Crystal frequency:  40MHz
USB mode:           USB-Serial/JTAG
MAC:                ac:eb:e6:6d:6b:b0

Stub flasher running.

Warning: ESP32-C3 has no chip ID. Reading MAC address instead.
MAC:                ac:eb:e6:6d:6b:b0

Hard resetting via RTS pin...
pcuser@ubuntu:~$
</pre></div>


<p class="wp-block-paragraph">ただ、これだと、1回抜き差しすると/dev/ttyACM0は再作成されるので権限が元に戻ってしまう</p>


<div class="wp-block-syntaxhighlighter-code "><pre class="brush: bash; title: ; notranslate">
pcuser@ubuntu:~$ ls -l /dev/ttyACM0
crw-rw---- 1 root dialout 166, 0 4月 8 11:53 /dev/ttyACM0
pcuser@ubuntu:~$
</pre></div>


<p class="wp-block-paragraph">簡単に解決する方法は、上記/dev/ttyACM0のグループ権限にある「dialout」に、一般ユーザを追加すること</p>


<div class="wp-block-syntaxhighlighter-code "><pre class="brush: bash; title: ; notranslate">
pcuser@ubuntu:~$ sudo usermod -aG dialout pcuser
&#x5B;sudo] pcuser のパスワード:
pcuser@ubuntu:~$
</pre></div>


<p class="wp-block-paragraph">設定後、一回ログアウトする必要がある。ログアウトしないと古い権限が適用され使用できない</p>


<div class="wp-block-syntaxhighlighter-code "><pre class="brush: bash; title: ; notranslate">
pcuser@ubuntu:~$ ls -l /dev/ttyACM0
crw-rw---- 1 root dialout 166, 0  4月  8 11:53 /dev/ttyACM0
pcuser@ubuntu:~$ /home/pcuser/.arduino15/packages/esp32/tools/esptool_py/5.1.0/esptool --port /dev/ttyACM0 chip-id

 Usage: esptool &#x5B;OPTIONS] COMMAND &#x5B;ARGS]...

 Try &#039;esptool -h&#039; for help
lq Error qqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqk
x Invalid value for &#039;--port&#039; / &#039;-p&#039;: Path &#039;/dev/ttyACM0&#039; is not readable.     x
mqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqj

pcuser@ubuntu:~$
</pre></div>


<p class="wp-block-paragraph">ログインしなおすと、使えるようになる</p>


<div class="wp-block-syntaxhighlighter-code "><pre class="brush: bash; title: ; notranslate">
pcuser@ubuntu:~$ ls -l /dev/ttyACM0
crw-rw---- 1 root dialout 166, 0  4月  8 11:53 /dev/ttyACM0
pcuser@ubuntu:~$ /home/pcuser/.arduino15/packages/esp32/tools/esptool_py/5.1.0/esptool --port /dev/ttyACM0 chip-id
esptool v5.1.0
Connected to ESP32-C3 on /dev/ttyACM0:
Chip type:          ESP32-C3 (QFN32) (revision v0.4)
Features:           Wi-Fi, BT 5 (LE), Single Core, 160MHz, Embedded Flash 4MB (XMC)
Crystal frequency:  40MHz
USB mode:           USB-Serial/JTAG
MAC:                ac:eb:e6:6d:6b:b0

Stub flasher running.

Warning: ESP32-C3 has no chip ID. Reading MAC address instead.
MAC:                ac:eb:e6:6d:6b:b0

Hard resetting via RTS pin...
pcuser@ubuntu:~$ id
uid=1000(pcuser) gid=1000(pcuser) groups=1000(pcuser),4(adm),20(dialout),24(cdrom),27(sudo),30(dip),46(plugdev),101(lxd)
pcuser@ubuntu:~$
</pre></div>


<hr class="wp-block-separator has-alpha-channel-opacity"/>



<h2 class="wp-block-heading">シリアル出力をしない設定がある</h2>



<p class="wp-block-paragraph">debugのために下記の様な感じでシリアル出力を書いた</p>


<div class="wp-block-syntaxhighlighter-code "><pre class="brush: cpp; title: ; notranslate">
#define LED_PIN (8)

void setup() {
  Serial.begin(9600);
  Serial.print(&quot;start&quot;);
  pinMode(LED_PIN, OUTPUT);

  while(1)
  {
    digitalWrite(LED_PIN, LOW);
    delay(500);

    digitalWrite(LED_PIN, HIGH);
    delay(100);
  }

}

void loop() {

  Serial.println(&quot;loop test&quot;);
  delay(3000);
}
</pre></div>


<p class="wp-block-paragraph">しかし、シリアルモニタに何も出力されない</p>



<p class="wp-block-paragraph">調べると「<a href="https://qiita.com/rune187/items/7a8563ced7ac2811e7e6">esp32 c3系でシリアルモニタに出力されない</a>」に「USB CDC On Boot」が「Disabled」になってると出力されない、という話があった</p>



<p class="wp-block-paragraph">確認すると、Disabledであった</p>



<figure class="wp-block-image size-full"><a href="https://blog.osakana.net/wp-content/uploads/2026/04/image-3.png"><img loading="lazy" decoding="async" width="606" height="74" src="https://blog.osakana.net/wp-content/uploads/2026/04/image-3.png" alt="" class="wp-image-17076" srcset="https://blog.osakana.net/wp-content/uploads/2026/04/image-3.png 606w, https://blog.osakana.net/wp-content/uploads/2026/04/image-3-300x37.png 300w" sizes="auto, (max-width: 606px) 100vw, 606px" /></a></figure>



<p class="wp-block-paragraph">しかし「Enabled」に変えてから書き込みを行ってもシリアル出力はされない状態</p>



<p class="wp-block-paragraph">arduiono 1.8.19 on ubuntu 24.04</p>



<figure class="wp-block-image size-full"><a href="https://blog.osakana.net/wp-content/uploads/2026/04/image-4.png"><img loading="lazy" decoding="async" width="502" height="632" src="https://blog.osakana.net/wp-content/uploads/2026/04/image-4.png" alt="" class="wp-image-17079" srcset="https://blog.osakana.net/wp-content/uploads/2026/04/image-4.png 502w, https://blog.osakana.net/wp-content/uploads/2026/04/image-4-238x300.png 238w" sizes="auto, (max-width: 502px) 100vw, 502px" /></a></figure>



<p class="wp-block-paragraph">他の事例「<a href="https://forum.arduino.cc/t/esp32c3-super-mini-doent-communicate-with-serial-monitor-in-one-setup-but-it-does-in-another-setup-why/1220740">ESP32C3 Super Mini doen&#8217;t communicate with Serial Monitor in one setup, but it does in another setup &#8212; why?</a>」には「ESP32C3 Dev Module」ではなく「LOLIN C3 Mini」を選んで「USB CDC On Boot:Enabled」で書き込め、ということでやってみたが、ダメだった</p>



<p class="wp-block-paragraph">claudeに「esp32 c3 super mini にて シリアル出力が出てこない」と聞いてみたら「USB CDC の初期化待ち（重要！）」だそうな</p>



<p class="wp-block-paragraph">ということでSerial.begin(9600);の次にdelay(2000)を追加したところ、とりあえずsetup内のserial.printについては出力はされたが、loop無いのやつが出力されない&#8230;って、あ、setup内でループしてんじゃん</p>


<div class="wp-block-syntaxhighlighter-code "><pre class="brush: cpp; title: ; notranslate">
#define LED_PIN (8)

void setup() {
  Serial.begin(9600);
  delay(2000); 
  Serial.print(&quot;start&quot;);
  pinMode(LED_PIN, OUTPUT);

  //while(1)
  //{
  //  digitalWrite(LED_PIN, LOW);
  //  delay(500);

  //  digitalWrite(LED_PIN, HIGH);
  //  delay(100);
  //}

}

void loop() {

  Serial.println(&quot;loop test&quot;);
  delay(3000);
}
</pre></div>


<p class="wp-block-paragraph">ということで動作を確認</p>



<p class="wp-block-paragraph"></p>



<p class="wp-block-paragraph"></p>
]]></content:encoded>
					
					<wfw:commentRss>https://blog.osakana.net/archives/17053/feed</wfw:commentRss>
			<slash:comments>0</slash:comments>
		
		
			</item>
	</channel>
</rss>
