2026/04/21

國際牌冷氣 無線控制模組 CZ-T007 設定

1.  CZ-T007 先安裝到冷氣機上,安裝時,冷氣機無需斷電。

2.  搖控器拔掉電池,然後按住"溫度上跟下鍵",裝上電池,看到搖控器顯示 "31 bu"的畫面時,放掉上下鍵。

3. 按下"下鍵",畫面會顯示 "31SA"

4. 開啟手機中安裝的Panasonic IOT app。

5. 選擇"新增裝置",選擇無線模組。

6. 照app上的操作,先開啟手機的wifi功能,連上這個無線模組的WIFI,然後再輸入家中的wifi帳號/密碼。

7. 這樣就新增成功了,但要記住,搖控器不能改回原本的樣子了,就保持在"31SA"這個模式下,這時搖控器畫面雖然不會顯示其他的東西,但開關機的功能還是可以用,其他的就在手機上操作。

如果搖控器改回原本的操作模組,無線模組就會無法使用。

2026/04/08

 環境:

commvault

掛載nas共用資料夾,當作媒體櫃,存放備份資料。

異常狀況:

nas密碼變更後,commvault無法掛載共用資料夾

解決過程:

在控制台,裡面有credentials manager,裡面有目前使用的帳號密碼設定,可以從這邊去修改。



ESXI 變更密碼 失敗 - 發生一般系統錯誤: Weak password: is based on the old one. *** passwd: Authentication token manipulation error

 環境:

esxi

異常狀況:

無法變更,會出現錯誤

解決過程:

在系統裡的進階設定,裡面有一個Security.PasswordQualityControl 參數。

在裡面加入 similar-permit ,存檔後馬上生效,就可以變更密碼了。







2026/03/27

使用LDAP與AD連線出現異常

 環境:

win2025 AD

異常狀況:

PHP程式要用LDAP協定,透過domain name抓ad使用者資料,時好時壞,改用IP連線也是。

連到不用的DC主機都會有狀況。

解決過程:

DC主機上的本機安全性原則中,在"電腦設定->windows設定->安全性設定->網域控制站:LDAP伺服器簽署要求強制執行",要設定成停用,每台DC都要設定成停用,就可以排除問題。


Environment:

Windows Server 2025 Active Directory

Issue:

A PHP application uses the LDAP protocol to query AD user information via the domain name, but the connection is unstable (intermittently works and fails).
Using the DC’s IP address shows the same issue.

The problem occurs when connecting to certain domain controllers.

Resolution:

On the domain controllers, modify the Local Security Policy:

  • Go to:
    Computer Configuration → Windows Settings → Security Settings → Domain Controller: LDAP server signing requirements
  • Set it to Disabled

This setting must be applied to all domain controllers.

After applying the change, the issue is resolved.


2026/03/26

Commvault 備份虛擬機 突然變的很慢

環境:

Commvault 備份虛擬機

異常狀況:

對新的虛擬機做第一次備份,可能容量比較大,過程中又有其他的備份,造成效能問題,最後就停住多個小時後,手動取消。

但後來要重新備份時,傳輸速度變超級慢,速度大概只剩之前的1/7~8,重開機也一樣。

解決過程:

後來發現之前備份失敗後,虛擬機上有一份snapshot沒被移除,先在esxi上,把那份snapshot刪除後,重新備份,就正常了。



Environment:

Commvault (VM Backup)

Issue:

When performing the first backup of a new virtual machine, the data size was relatively large. During the process, other backup jobs were also running, causing performance issues. Eventually, the job became unresponsive and was manually canceled after several hours.

After that, when attempting to run the backup again, the transfer speed became extremely slow, dropping to about 1/7–1/8 of the original speed. Restarting the system did not resolve the issue.

Resolution:

It was later discovered that after the failed backup, a snapshot remained on the virtual machine and was not removed.

By logging into ESXi and deleting the leftover snapshot, then running the backup again, the performance returned to normal.

2026/03/25

ESXI 無法開啟虛擬機器 xxx的電源。開啟模組 monitorloop 的電源失敗

  環境:

ESXI  

Synology active backup business

異常狀況:

用Synology active backup business備份的虛擬機,還原到其他esxi後,開機出現錯誤。



解決過程:

原機配置了較高的CPU與RAM,還原後,目的esxi上資源不足,無法開機,把虛擬機的CPU與RAM調低後,就可以正常開機


Environment:

ESXi
Synology Active Backup for Business

Issue:

After restoring a virtual machine using Synology Active Backup for Business to another ESXi host, the VM fails to power on and shows an error.

Resolution:

The original VM was configured with relatively high CPU and RAM.
After restoration, the target ESXi host did not have sufficient resources to support that configuration.

By reducing the VM’s CPU and RAM allocation, the virtual machine was able to power on normally.

2026/03/24

ESXI VMFS 增加容量失敗-無法變更主機組態。

 環境:

ESXI 6.7

異常狀況:

底層硬碟RAID擴充完一顆新硬碟後,要在ESXI上也對儲存區進行擴充。

在web console上操作,對著要擴充的datastore ,選擇"增加容量"。


再來選擇"擴充現有..........."。


第三步,要先在分割之前的圖,點選vmfs區塊,然後就會出現一個調整新增容量的設定,選擇要把新增的硬碟,擴充多少容量到vmfs中。


按下完成後,就會出現錯誤,試了很多次,擴充不同的容量,都一樣錯誤:

說明:延伸 VMFS 資料存放區範圍的容量

狀態:失敗 - 無法變更主機組態。

解決過程:

用指令的方式擴充,就成功了。



Environment:

ESXi 6.7

Issue:

After expanding the underlying RAID by adding a new disk, the datastore also needs to be extended in ESXi.

When performing the operation via the web console:

  1. Select the datastore and choose “Increase capacity”
  2. Then select “Expand existing…”
  3. In the partition layout screen, select the VMFS partition, and adjust how much of the newly added space should be allocated to VMFS

However, after clicking Finish, the following error occurs regardless of the size selected:

  • Description: Extend VMFS datastore capacity
  • Status: Failed – Unable to change the host configuration

Resolution:

Expanding the datastore using the command line (CLI) was successful.















2026/03/12

DHCP 設定匯出匯入

DHCP config export command

netsh dhcp server export d:\backup.txt all


DHCP config import command

 netsh dhcp server import d:\backup.txt all

2026/03/03

commvault 備份時會當機

  環境:

commvault

x3650m3

win2012

異常狀況:

已經運作多年的備份主機,突然開始在備份時會當機,備份比較大的資料才會當機,只是少量的就不會,不執行備份放一整個晚上也都沒問題。

當機後通常會進到藍底白字畫面,搜尋相關錯誤資訊,但未有任何進度就會直接重開機。

沒有memory dump檔,事件檢視器也沒有任何可參考的資訊,只會有意外當機的事項。

IMM 的log裡也沒有任何的異常。

raid程式裡,硬碟與raid卡都健康。

用內建的記憶體測試,正常。

解決過程:

關閉防毒->無效

調低備份的Maximum number of parallel data transfer operations->無效

關機拔電後重開->無效

拔掉六條記憶體擦一擦,只插回基本的兩條->無效

在找不到任何方法下,先把記憶體全部插回,再試試,居然就正常了....

但過了一週,又開始發生備份會當機的狀況,大概兩天後主機的raid跟pci就亮橘燈了。

更換raid卡後終於恢復正常。


Environment:

Commvault
IBM x3650 M3
Windows Server 2012

Issue:

A backup server that had been running normally for many years suddenly began crashing during backup operations.
The crash only occurred when backing up large amounts of data. Backups with small amounts of data completed normally, and the server could remain powered on overnight without issues if no backup jobs were running.

After the crash, the system usually entered a blue screen. When attempting to view the error details, the system rebooted before any useful information could be collected.

Additional observations:

  • No memory dump files were generated.

  • Event Viewer only recorded an unexpected shutdown with no useful details.

  • IMM logs showed no abnormalities.

  • RAID management reported that the disks and RAID controller were healthy.

  • The built-in memory diagnostic test passed without errors.

Troubleshooting Process:

  • Disabled antivirus → No effect

  • Reduced Maximum number of parallel data transfer operations in Commvault → No effect

  • Powered off the server and unplugged power before restarting → No effect

  • Removed six memory modules, cleaned them, and left only two installed → No effect

With no other solutions available, all memory modules were reinstalled again.
Unexpectedly, after reinstalling all the RAM, the system returned to normal operation and the backup jobs completed successfully.

However, about one week later, the backup server began to crash again during backup jobs.

After approximately two more days, the RAID and PCI indicator lights on the server turned orange.

The RAID controller was then replaced, and after replacing the RAID card, the system finally returned to stable operation and the backup crashes stopped.


2026/02/26

commvault備份虛擬機失敗 There are too many existing backup snapshots on virtual machine

 環境:

commvault

異常狀況:

備份失敗

錯誤碼: [91:148] 描述: There are too many existing backup snapshots on virtual machine [xx]. Backup snapshots are being cleaned up, but manual intervention may be required to ensure that all snapshots are removed. This may indicate that the storage is unable to keep up with the I/O activity of the virtual machine during a backup. Source: backupserver, Process: vsbkp 

解決過程:

主要是因為備份虛擬機時,會先建立快照,但因為備份程式當掉,當成快照沒被清除。

之後要再備份就會出現此錯誤。

這時就連上esxi,到該虛擬機的快照管理中,把快照"全部刪除",然後就可以正常備份了。


Environment:

Commvault

Issue:

Backup failed with the following error:

Error Code: [91:148]
Description:
There are too many existing backup snapshots on virtual machine [xx]. Backup snapshots are being cleaned up, but manual intervention may be required to ensure that all snapshots are removed. This may indicate that the storage is unable to keep up with the I/O activity of the virtual machine during a backup.
Source: backupserver
Process: vsbkp

Resolution:

This issue occurs because when backing up a virtual machine, the system first creates snapshots. However, if the backup process crashes or fails, the snapshots may not be removed properly.

When attempting the next backup, this error will appear.

To resolve the issue:

  1. Log in to the ESXi host.

  2. Open the Snapshot Manager for the affected virtual machine.

  3. Select Delete All snapshots.

After removing all snapshots, the backup should run normally again.