【小ネタ】 Amazon Linux 2 / 2023 で、EC2 インスタンス停止時に追加 EBS ボリュームがアンマウントされるか確認してみた
2026.04.01
はじめに
テクニカルサポートの 片方 です。
今回は EC2 インスタンスに追加した EBS ボリュームについて、インスタンス停止時に自動的にアンマウントされるのか気になったため、Amazon Linux 2 および Amazon Linux 2023 で確認してみました。
・インスタンスから Amazon EBS ボリュームをデタッチするには、明示的にデタッチするか、インスタンスを終了します。ただし、インスタンスが実行中の場合、最初にインスタンスからボリュームをアンマウントする必要があります。
・EBS ボリュームがインスタンスのルートデバイスである場合、ボリュームをデタッチする前に、インスタンスを停止する必要があります。
・(アンマウントせずに) 切り離したボリュームを再接続することはできますが、同じマウントポイントが得られない可能性があります。進行中のボリュームがデタッチされたときにそのボリュームへの書き込みがあった場合、ボリューム上のデータは同期していない可能性があります。
先に結論から
今回確認した Amazon Linux 2 / Amazon Linux 2023 では、EC2 インスタンス停止時に追加 EBS ボリューム上のマウント済みファイルシステムが正常にアンマウントされることを確認できました。
確認してみた
Amazon Linux 2
Amazon Linux 2 に追加 EBS ボリュームをアタッチし、/data にマウントした状態で EC2 インスタンスの停止・起動を実施しました。
起動後に /var/log/messages を確認したところ、Unmounting /data...、Unmounted /data.、XFS (nvme1n1): Unmounting Filesystem といったログを確認できました。
このことから、Amazon Linux 2 では EC2 インスタンス停止時に、追加 EBS ボリューム上のマウント済みファイルシステムが正常にアンマウントされることを確認できました。
検証結果
sh-4.2$ df -hT
Filesystem Type Size Used Avail Use% Mounted on
devtmpfs devtmpfs 3.8G 0 3.8G 0% /dev
tmpfs tmpfs 3.8G 0 3.8G 0% /dev/shm
tmpfs tmpfs 3.8G 352K 3.8G 1% /run
tmpfs tmpfs 3.8G 0 3.8G 0% /sys/fs/cgroup
/dev/nvme0n1p1 xfs 8.0G 3.0G 5.1G 37% /
/dev/nvme1n1 xfs 10G 104M 9.9G 2% /data
sh-4.2$ lsblk -o NAME,FSTYPE,SIZE,MOUNTPOINT
NAME FSTYPE SIZE MOUNTPOINT
nvme1n1 xfs 10G /data
nvme0n1 8G
├─nvme0n1p1 xfs 8G /
└─nvme0n1p128 1M
sh-4.2$ date
Tue Mar 31 02:57:52 UTC 2026
sh-4.2$
（停止・起動）
sh-4.2$ date
Tue Mar 31 03:02:32 UTC 2026
sh-4.2$ df -hT
Filesystem Type Size Used Avail Use% Mounted on
devtmpfs devtmpfs 3.8G 0 3.8G 0% /dev
tmpfs tmpfs 3.8G 0 3.8G 0% /dev/shm
tmpfs tmpfs 3.8G 408K 3.8G 1% /run
tmpfs tmpfs 3.8G 0 3.8G 0% /sys/fs/cgroup
/dev/nvme0n1p1 xfs 8.0G 3.0G 5.1G 37% /
tmpfs tmpfs 767M 0 767M 0% /run/user/0
sh-4.2$ lsblk -o NAME,FSTYPE,SIZE,MOUNTPOINT
NAME FSTYPE SIZE MOUNTPOINT
nvme1n1 xfs 10G
nvme0n1 8G
├─nvme0n1p1 xfs 8G /
└─nvme0n1p128 1M
sh-4.2$ sudo grep -Ei 'shutdown|poweroff|unmount|umount|nvme1n1|/data' /var/log/messages
Aug 28 20:56:23 ip-172-31-85-148 kernel: Command line: BOOT_IMAGE=/boot/vmlinuz-4.14.355-280.672.amzn2.x86_64 root=UUID=39a62717-8b51-48e0-ba3a-b52c6b5792f9 ro console=tty0 console=ttyS0,115200n8 net.ifnames=0 biosdevname=0 nvme_core.io_timeout=4294967295 rd.emergency=poweroff rd.shell=0
Aug 28 20:56:23 ip-172-31-85-148 kernel: Kernel command line: BOOT_IMAGE=/boot/vmlinuz-4.14.355-280.672.amzn2.x86_64 root=UUID=39a62717-8b51-48e0-ba3a-b52c6b5792f9 ro console=tty0 console=ttyS0,115200n8 net.ifnames=0 biosdevname=0 nvme_core.io_timeout=4294967295 rd.emergency=poweroff rd.shell=0
Aug 28 20:56:26 ip-172-31-85-148 systemd: Starting Update UTMP about System Boot/Shutdown...
Aug 28 20:56:26 ip-172-31-85-148 systemd: Started Update UTMP about System Boot/Shutdown.
Aug 28 21:00:43 ip-172-31-85-148 systemd: Reached target Unmount All Filesystems.
Aug 28 21:00:43 ip-172-31-85-148 systemd: Unmounting RPC Pipe File System...
Aug 28 21:00:43 ip-172-31-85-148 systemd: Unmounted RPC Pipe File System.
Aug 28 21:00:50 ip-172-31-85-148 systemd: Stopping Update UTMP about System Boot/Shutdown...
Aug 28 21:00:50 ip-172-31-85-148 systemd: Stopped Update UTMP about System Boot/Shutdown.
Aug 28 21:00:50 ip-172-31-85-148 systemd: Reached target Shutdown.
Aug 28 21:00:50 ip-172-31-85-148 systemd-shutdown[1]: Syncing filesystems and block devices.
Aug 28 21:01:20 ip-172-31-85-148 kernel: Command line: BOOT_IMAGE=/boot/vmlinuz-4.14.355-280.672.amzn2.x86_64 root=UUID=39a62717-8b51-48e0-ba3a-b52c6b5792f9 ro console=tty0 console=ttyS0,115200n8 net.ifnames=0 biosdevname=0 nvme_core.io_timeout=4294967295 rd.emergency=poweroff rd.shell=0
Aug 28 21:01:20 ip-172-31-85-148 kernel: Kernel command line: BOOT_IMAGE=/boot/vmlinuz-4.14.355-280.672.amzn2.x86_64 root=UUID=39a62717-8b51-48e0-ba3a-b52c6b5792f9 ro console=tty0 console=ttyS0,115200n8 net.ifnames=0 biosdevname=0 nvme_core.io_timeout=4294967295 rd.emergency=poweroff rd.shell=0
Aug 28 21:01:22 ip-172-31-85-148 systemd: Starting Update UTMP about System Boot/Shutdown...
Aug 28 21:01:22 ip-172-31-85-148 systemd: Started Update UTMP about System Boot/Shutdown.
Aug 28 21:02:35 ip-172-31-85-148 sqlservr: 2025-08-28 21:02:35.69 Server Setup step is FORCE copying system data file 'C:\templatedata\model_replicatedmaster.mdf' to '/var/opt/mssql/data/model_replicatedmaster.mdf'.
Aug 28 21:02:35 ip-172-31-85-148 sqlservr: 2025-08-28 21:02:35.72 Server Setup step is FORCE copying system data file 'C:\templatedata\model_replicatedmaster.ldf' to '/var/opt/mssql/data/model_replicatedmaster.ldf'.
Aug 28 21:02:35 ip-172-31-85-148 sqlservr: 2025-08-28 21:02:35.73 Server Setup step is FORCE copying system data file 'C:\templatedata\model_msdbdata.mdf' to '/var/opt/mssql/data/model_msdbdata.mdf'.
Aug 28 21:02:35 ip-172-31-85-148 sqlservr: 2025-08-28 21:02:35.74 Server Setup step is FORCE copying system data file 'C:\templatedata\model_msdblog.ldf' to '/var/opt/mssql/data/model_msdblog.ldf'.
Aug 28 21:02:35 ip-172-31-85-148 sqlservr: -d /var/opt/mssql/data/master.mdf
Aug 28 21:02:35 ip-172-31-85-148 sqlservr: -l /var/opt/mssql/data/mastlog.ldf
Aug 28 21:02:47 ip-172-31-85-148 sqlservr: 2025-08-28 21:02:47.24 spid9s SQL Trace was stopped due to server shutdown. Trace ID = '1'. This is an informational message only; no user action is required.
Aug 28 21:02:52 ip-172-31-85-148 sqlservr: 2025-08-28 21:02:52.90 Server Setup step is FORCE copying system data file 'C:\templatedata\model_replicatedmaster.mdf' to '/var/opt/mssql/data/model_replicatedmaster.mdf'.
Aug 28 21:02:52 ip-172-31-85-148 sqlservr: 2025-08-28 21:02:52.93 Server Setup step is FORCE copying system data file 'C:\templatedata\model_replicatedmaster.ldf' to '/var/opt/mssql/data/model_replicatedmaster.ldf'.
Aug 28 21:02:52 ip-172-31-85-148 sqlservr: 2025-08-28 21:02:52.94 Server Setup step is FORCE copying system data file 'C:\templatedata\model_msdbdata.mdf' to '/var/opt/mssql/data/model_msdbdata.mdf'.
Aug 28 21:02:52 ip-172-31-85-148 sqlservr: 2025-08-28 21:02:52.95 Server Setup step is FORCE copying system data file 'C:\templatedata\model_msdblog.ldf' to '/var/opt/mssql/data/model_msdblog.ldf'.
Aug 28 21:02:53 ip-172-31-85-148 sqlservr: -d /var/opt/mssql/data/master.mdf
Aug 28 21:02:53 ip-172-31-85-148 sqlservr: -l /var/opt/mssql/data/mastlog.ldf
Aug 28 21:03:04 ip-172-31-85-148 sqlservr: 2025-08-28 21:03:04.51 spid9s SQL Trace was stopped due to server shutdown. Trace ID = '1'. This is an informational message only; no user action is required.
Aug 28 21:05:01 ip-10-0-30-207 systemd: Reached target Unmount All Filesystems.
Aug 28 21:05:01 ip-10-0-30-207 systemd: Unmounting RPC Pipe File System...
Aug 28 21:05:01 ip-10-0-30-207 umount: umount: /var/lib/nfs/rpc_pipefs: not mounted.
Aug 28 21:05:01 ip-10-0-30-207 systemd: Unmounted RPC Pipe File System.
Aug 28 21:05:08 ip-10-0-30-207 systemd: Stopping Update UTMP about System Boot/Shutdown...
Aug 28 21:05:08 ip-10-0-30-207 systemd: Stopped Update UTMP about System Boot/Shutdown.
Aug 28 21:05:08 ip-10-0-30-207 systemd: Reached target Shutdown.
Aug 28 21:05:08 ip-10-0-30-207 systemd-shutdown[1]: Syncing filesystems and block devices.
Mar 31 02:48:18 ip-10-0-30-207 kernel: Command line: BOOT_IMAGE=/boot/vmlinuz-4.14.355-280.672.amzn2.x86_64 root=UUID=39a62717-8b51-48e0-ba3a-b52c6b5792f9 ro console=tty0 console=ttyS0,115200n8 net.ifnames=0 biosdevname=0 nvme_core.io_timeout=4294967295 rd.emergency=poweroff rd.shell=0
Mar 31 02:48:18 ip-10-0-30-207 kernel: Kernel command line: BOOT_IMAGE=/boot/vmlinuz-4.14.355-280.672.amzn2.x86_64 root=UUID=39a62717-8b51-48e0-ba3a-b52c6b5792f9 ro console=tty0 console=ttyS0,115200n8 net.ifnames=0 biosdevname=0 nvme_core.io_timeout=4294967295 rd.emergency=poweroff rd.shell=0
Mar 31 02:48:23 ip-10-0-30-207 systemd: Starting Update UTMP about System Boot/Shutdown...
Mar 31 02:48:23 ip-10-0-30-207 systemd: Started Update UTMP about System Boot/Shutdown.
Mar 31 02:49:10 ip-10-0-30-207 dracut: *** Including module: shutdown ***
Mar 31 02:49:37 ip-10-0-30-207 sqlservr: 2026-03-31 02:49:37.59 Server Setup step is FORCE copying system data file 'C:\templatedata\model_replicatedmaster.mdf' to '/var/opt/mssql/data/model_replicatedmaster.mdf'.
Mar 31 02:49:37 ip-10-0-30-207 sqlservr: 2026-03-31 02:49:37.63 Server Setup step is FORCE copying system data file 'C:\templatedata\model_replicatedmaster.ldf' to '/var/opt/mssql/data/model_replicatedmaster.ldf'.
Mar 31 02:49:37 ip-10-0-30-207 sqlservr: 2026-03-31 02:49:37.63 Server Setup step is FORCE copying system data file 'C:\templatedata\model_msdbdata.mdf' to '/var/opt/mssql/data/model_msdbdata.mdf'.
Mar 31 02:49:37 ip-10-0-30-207 sqlservr: 2026-03-31 02:49:37.64 Server Setup step is FORCE copying system data file 'C:\templatedata\model_msdblog.ldf' to '/var/opt/mssql/data/model_msdblog.ldf'.
Mar 31 02:49:37 ip-10-0-30-207 sqlservr: -d /var/opt/mssql/data/master.mdf
Mar 31 02:49:37 ip-10-0-30-207 sqlservr: -l /var/opt/mssql/data/mastlog.ldf
Mar 31 02:53:47 ip-10-0-30-207 kernel: XFS (nvme1n1): EXPERIMENTAL reflink feature enabled. Use at your own risk!
Mar 31 02:53:47 ip-10-0-30-207 kernel: XFS (nvme1n1): Mounting V5 Filesystem
Mar 31 02:53:47 ip-10-0-30-207 kernel: XFS (nvme1n1): Ending clean mount
Mar 31 02:58:25 ip-10-0-30-207 systemd: Unmounting RPC Pipe File System...
Mar 31 02:58:25 ip-10-0-30-207 sqlservr: 2026-03-31 02:58:25.76 spid8s SQL Trace was stopped due to server shutdown. Trace ID = '1'. This is an informational message only; no user action is required.
Mar 31 02:58:25 ip-10-0-30-207 systemd: Unmounted RPC Pipe File System.
Mar 31 02:58:33 ip-10-0-30-207 systemd: Unmounting /data...
Mar 31 02:58:33 ip-10-0-30-207 systemd: Unmounted /data.
Mar 31 02:58:33 ip-10-0-30-207 systemd: Reached target Unmount All Filesystems.
Mar 31 02:58:33 ip-10-0-30-207 kernel: XFS (nvme1n1): Unmounting Filesystem
Mar 31 02:58:33 ip-10-0-30-207 systemd: Reached target Shutdown.
Mar 31 02:58:33 ip-10-0-30-207 systemd-shutdown[1]: Syncing filesystems and block devices.
Mar 31 02:59:54 ip-10-0-30-207 kernel: Command line: BOOT_IMAGE=/boot/vmlinuz-4.14.355-280.672.amzn2.x86_64 root=UUID=39a62717-8b51-48e0-ba3a-b52c6b5792f9 ro console=tty0 console=ttyS0,115200n8 net.ifnames=0 biosdevname=0 nvme_core.io_timeout=4294967295 rd.emergency=poweroff rd.shell=0
Mar 31 02:59:54 ip-10-0-30-207 kernel: Kernel command line: BOOT_IMAGE=/boot/vmlinuz-4.14.355-280.672.amzn2.x86_64 root=UUID=39a62717-8b51-48e0-ba3a-b52c6b5792f9 ro console=tty0 console=ttyS0,115200n8 net.ifnames=0 biosdevname=0 nvme_core.io_timeout=4294967295 rd.emergency=poweroff rd.shell=0
Mar 31 02:59:57 ip-10-0-30-207 systemd: Starting Update UTMP about System Boot/Shutdown...
Mar 31 02:59:57 ip-10-0-30-207 systemd: Started Update UTMP about System Boot/Shutdown.
Mar 31 03:00:11 ip-10-0-30-207 sqlservr: 2026-03-31 03:00:11.34 Server Setup step is FORCE copying system data file 'C:\templatedata\model_replicatedmaster.mdf' to '/var/opt/mssql/data/model_replicatedmaster.mdf'.
Mar 31 03:00:11 ip-10-0-30-207 sqlservr: 2026-03-31 03:00:11.40 Server Setup step is FORCE copying system data file 'C:\templatedata\model_replicatedmaster.ldf' to '/var/opt/mssql/data/model_replicatedmaster.ldf'.
Mar 31 03:00:11 ip-10-0-30-207 sqlservr: 2026-03-31 03:00:11.40 Server Setup step is FORCE copying system data file 'C:\templatedata\model_msdbdata.mdf' to '/var/opt/mssql/data/model_msdbdata.mdf'.
Mar 31 03:00:11 ip-10-0-30-207 sqlservr: 2026-03-31 03:00:11.42 Server Setup step is FORCE copying system data file 'C:\templatedata\model_msdblog.ldf' to '/var/opt/mssql/data/model_msdblog.ldf'.
Mar 31 03:00:11 ip-10-0-30-207 sqlservr: -d /var/opt/mssql/data/master.mdf
Mar 31 03:00:11 ip-10-0-30-207 sqlservr: -l /var/opt/mssql/data/mastlog.ldf
sh-4.2$
Amazon Linux 2023
Amazon Linux 2023 でも同様に、追加 EBS ボリュームを /data にマウントした状態で EC2 インスタンスの停止・起動を実施しました。
起動後に journalctl で前回 boot のログを確認したところ、Unmounting data.mount - /data...、Unmounted data.mount - /data.、XFS (nvme1n1): Unmounting Filesystem というログを確認できました。
このことから、Amazon Linux 2023 でも EC2 インスタンス停止時に、追加 EBS ボリューム上のマウント済みファイルシステムが正常にアンマウントされることを確認できました。
検証結果
sh-5.2$ df -hT
Filesystem Type Size Used Avail Use% Mounted on
devtmpfs devtmpfs 4.0M 0 4.0M 0% /dev
tmpfs tmpfs 3.9G 0 3.9G 0% /dev/shm
tmpfs tmpfs 1.6G 432K 1.6G 1% /run
/dev/nvme0n1p1 xfs 8.0G 1.6G 6.4G 20% /
tmpfs tmpfs 3.9G 0 3.9G 0% /tmp
/dev/nvme0n1p128 vfat 10M 1.3M 8.7M 13% /boot/efi
/dev/nvme1n1 xfs 10G 104M 9.9G 2% /data
sh-5.2$ lsblk -o NAME,FSTYPE,SIZE,MOUNTPOINT
NAME FSTYPE SIZE MOUNTPOINT
nvme1n1 xfs 10G /data
nvme0n1 8G
├─nvme0n1p1 xfs 8G /
├─nvme0n1p127 1M
└─nvme0n1p128 vfat 10M /boot/efi
sh-5.2$ date
Tue Mar 31 06:05:38 UTC 2026
sh-5.2$
(停止・起動)
sh-5.2$ date
Tue Mar 31 06:10:46 UTC 2026
sh-5.2$ sudo journalctl -b -1 --no-pager | grep -Ei 'unmount|umount|shutdown|poweroff|/data|nvme1n1'
Mar 31 05:58:18 localhost kernel: Command line: BOOT_IMAGE=(hd0,gpt1)/boot/vmlinuz-6.1.164-196.303.amzn2023.x86_64 root=UUID=a7e0b2a5-da35-4366-bb65-556fc198bb3f ro console=tty0 console=ttyS0,115200n8 nvme_core.io_timeout=4294967295 rd.emergency=poweroff rd.shell=0 selinux=1 security=selinux quiet
Mar 31 05:58:18 localhost kernel: Kernel command line: BOOT_IMAGE=(hd0,gpt1)/boot/vmlinuz-6.1.164-196.303.amzn2023.x86_64 root=UUID=a7e0b2a5-da35-4366-bb65-556fc198bb3f ro console=tty0 console=ttyS0,115200n8 nvme_core.io_timeout=4294967295 rd.emergency=poweroff rd.shell=0 selinux=1 security=selinux quiet
Mar 31 05:58:18 localhost kernel: Freeing unused kernel image (rodata/data gap) memory: 1284K
Mar 31 05:58:18 localhost dracut-cmdline[358]: Using kernel command line parameters: BOOT_IMAGE=(hd0,gpt1)/boot/vmlinuz-6.1.164-196.303.amzn2023.x86_64 root=UUID=a7e0b2a5-da35-4366-bb65-556fc198bb3f ro console=tty0 console=ttyS0,115200n8 nvme_core.io_timeout=4294967295 rd.emergency=poweroff rd.shell=0 selinux=1 security=selinux quiet
Mar 31 05:58:22 localhost systemd[1]: Starting systemd-update-utmp.service - Record System Boot/Shutdown in UTMP...
Mar 31 05:58:22 localhost systemd[1]: Finished systemd-update-utmp.service - Record System Boot/Shutdown in UTMP.
Mar 31 05:58:23 localhost systemd[1]: Starting dracut-shutdown.service - Restore /run/initramfs on shutdown...
Mar 31 05:58:23 localhost audit[1]: SERVICE_START pid=1 uid=0 auid=4294967295 ses=4294967295 subj=system_u:system_r:init_t:s0 msg='unit=dracut-shutdown comm="systemd" exe="/usr/lib/systemd/systemd" hostname=? addr=? terminal=? res=success'
Mar 31 05:58:23 localhost systemd[1]: Finished dracut-shutdown.service - Restore /run/initramfs on shutdown.
Mar 31 06:03:36 ip-10-0-30-35.ap-northeast-1.compute.internal sudo[1975]: ssm-user : TTY=pts/0 ; PWD=/usr/bin ; USER=root ; COMMAND=/usr/bin/file -s /dev/nvme1n1
Mar 31 06:03:36 ip-10-0-30-35.ap-northeast-1.compute.internal sudo[2043]: ssm-user : TTY=pts/0 ; PWD=/usr/bin ; USER=root ; COMMAND=/usr/bin/mkdir -p /data
Mar 31 06:03:37 ip-10-0-30-35.ap-northeast-1.compute.internal sudo[2047]: ssm-user : TTY=pts/0 ; PWD=/usr/bin ; USER=root ; COMMAND=/usr/sbin/mkfs -t xfs /dev/nvme1n1
Mar 31 06:03:37 ip-10-0-30-35.ap-northeast-1.compute.internal sudo[2052]: ssm-user : TTY=pts/0 ; PWD=/usr/bin ; USER=root ; COMMAND=/usr/bin/mount /dev/nvme1n1 /data
Mar 31 06:03:37 ip-10-0-30-35.ap-northeast-1.compute.internal kernel: XFS (nvme1n1): Mounting V5 Filesystem
Mar 31 06:03:37 ip-10-0-30-35.ap-northeast-1.compute.internal kernel: XFS (nvme1n1): Ending clean mount
Mar 31 06:03:47 ip-10-0-30-35.ap-northeast-1.compute.internal systemd[2031]: Reached target shutdown.target - Shutdown.
Mar 31 06:06:38 ip-10-0-30-35.ap-northeast-1.compute.internal systemd[1]: Unmounting var-lib-nfs-rpc_pipefs.mount - RPC Pipe File System...
Mar 31 06:06:39 ip-10-0-30-35.ap-northeast-1.compute.internal systemd[1]: Stopping dracut-shutdown.service - Restore /run/initramfs on shutdown...
Mar 31 06:06:39 ip-10-0-30-35.ap-northeast-1.compute.internal systemd[1]: Unmounted var-lib-nfs-rpc_pipefs.mount - RPC Pipe File System.
Mar 31 06:06:39 ip-10-0-30-35.ap-northeast-1.compute.internal systemd[1]: dracut-shutdown.service: Deactivated successfully.
Mar 31 06:06:39 ip-10-0-30-35.ap-northeast-1.compute.internal systemd[1]: Stopped dracut-shutdown.service - Restore /run/initramfs on shutdown.
Mar 31 06:06:39 ip-10-0-30-35.ap-northeast-1.compute.internal audit[1]: SERVICE_STOP pid=1 uid=0 auid=4294967295 ses=4294967295 subj=system_u:system_r:init_t:s0 msg='unit=dracut-shutdown comm="systemd" exe="/usr/lib/systemd/systemd" hostname=? addr=? terminal=? res=success'
Mar 31 06:06:46 ip-10-0-30-35.ap-northeast-1.compute.internal systemd[1]: Stopping systemd-update-utmp.service - Record System Boot/Shutdown in UTMP...
Mar 31 06:06:46 ip-10-0-30-35.ap-northeast-1.compute.internal audit[2223]: SYSTEM_SHUTDOWN pid=2223 uid=0 auid=4294967295 ses=4294967295 subj=system_u:system_r:init_t:s0 msg=' comm="systemd-update-utmp"exe="/usr/lib/systemd/systemd-update-utmp" hostname=? addr=? terminal=? res=success'
Mar 31 06:06:46 ip-10-0-30-35.ap-northeast-1.compute.internal systemd[1]: Unmounted run-credentials-systemd\x2dsysctl.service.mount - /run/credentials/systemd-sysctl.service.
Mar 31 06:06:46 ip-10-0-30-35.ap-northeast-1.compute.internal systemd[1]: Stopped systemd-update-utmp.service - Record System Boot/Shutdown in UTMP.
Mar 31 06:06:46 ip-10-0-30-35.ap-northeast-1.compute.internal systemd[1]: Unmounting boot-efi.mount - /boot/efi...
Mar 31 06:06:46 ip-10-0-30-35.ap-northeast-1.compute.internal systemd[1]: Unmounting data.mount - /data...
Mar 31 06:06:46 ip-10-0-30-35.ap-northeast-1.compute.internal systemd[1]: Unmounting run-credentials-systemd\x2dtmpfiles\x2dsetup.service.mount - /run/credentials/systemd-tmpfiles-setup.service...
Mar 31 06:06:46 ip-10-0-30-35.ap-northeast-1.compute.internal umount[2229]: umount: /run/credentials/systemd-tmpfiles-setup.service: no mount point specified.
Mar 31 06:06:46 ip-10-0-30-35.ap-northeast-1.compute.internal kernel: XFS (nvme1n1): Unmounting Filesystem
Mar 31 06:06:46 ip-10-0-30-35.ap-northeast-1.compute.internal systemd[1]: Unmounting run-credentials-systemd\x2dtmpfiles\x2dsetup\x2ddev.service.mount - /run/credentials/systemd-tmpfiles-setup-dev.service...
Mar 31 06:06:46 ip-10-0-30-35.ap-northeast-1.compute.internal systemd[1]: Unmounting tmp.mount - Temporary Directory /tmp...
Mar 31 06:06:46 ip-10-0-30-35.ap-northeast-1.compute.internal systemd[1]: Unmounted boot-efi.mount - /boot/efi.
Mar 31 06:06:46 ip-10-0-30-35.ap-northeast-1.compute.internal systemd[1]: Unmounted data.mount - /data.
Mar 31 06:06:46 ip-10-0-30-35.ap-northeast-1.compute.internal systemd[1]: Unmounted run-credentials-systemd\x2dtmpfiles\x2dsetup.service.mount - /run/credentials/systemd-tmpfiles-setup.service.
Mar 31 06:06:46 ip-10-0-30-35.ap-northeast-1.compute.internal systemd[1]: Unmounted run-credentials-systemd\x2dtmpfiles\x2dsetup\x2ddev.service.mount - /run/credentials/systemd-tmpfiles-setup-dev.service.
Mar 31 06:06:46 ip-10-0-30-35.ap-northeast-1.compute.internal systemd[1]: Unmounted tmp.mount - Temporary Directory /tmp.
Mar 31 06:06:46 ip-10-0-30-35.ap-northeast-1.compute.internal systemd[1]: Reached target umount.target - Unmount All Filesystems.
Mar 31 06:06:46 ip-10-0-30-35.ap-northeast-1.compute.internal kernel: audit: type=1130 audit(1774937206.819:342): pid=1 uid=0 auid=4294967295 ses=4294967295 subj=system_u:system_r:init_t:s0 msg='unit=systemd-poweroff comm="systemd" exe="/usr/lib/systemd/systemd" hostname=? addr=? terminal=? res=success'
Mar 31 06:06:46 ip-10-0-30-35.ap-northeast-1.compute.internal kernel: audit: type=1131 audit(1774937206.819:343): pid=1 uid=0 auid=4294967295 ses=4294967295 subj=system_u:system_r:init_t:s0 msg='unit=systemd-poweroff comm="systemd" exe="/usr/lib/systemd/systemd" hostname=? addr=? terminal=? res=success'
Mar 31 06:06:46 ip-10-0-30-35.ap-northeast-1.compute.internal audit[1]: SERVICE_START pid=1 uid=0 auid=4294967295 ses=4294967295 subj=system_u:system_r:init_t:s0 msg='unit=systemd-poweroff comm="systemd" exe="/usr/lib/systemd/systemd" hostname=? addr=? terminal=? res=success'
Mar 31 06:06:46 ip-10-0-30-35.ap-northeast-1.compute.internal audit[1]: SERVICE_STOP pid=1 uid=0 auid=4294967295 ses=4294967295 subj=system_u:system_r:init_t:s0 msg='unit=systemd-poweroff comm="systemd"exe="/usr/lib/systemd/systemd" hostname=? addr=? terminal=? res=success'
Mar 31 06:06:46 ip-10-0-30-35.ap-northeast-1.compute.internal systemd[1]: Reached target shutdown.target - System Shutdown.
Mar 31 06:06:46 ip-10-0-30-35.ap-northeast-1.compute.internal systemd[1]: Reached target final.target - Late Shutdown Services.
Mar 31 06:06:46 ip-10-0-30-35.ap-northeast-1.compute.internal systemd[1]: systemd-poweroff.service: Deactivated successfully.
Mar 31 06:06:46 ip-10-0-30-35.ap-northeast-1.compute.internal systemd[1]: Finished systemd-poweroff.service - System Power Off.
Mar 31 06:06:46 ip-10-0-30-35.ap-northeast-1.compute.internal systemd[1]: Reached target poweroff.target - System Power Off.
Mar 31 06:06:47 ip-10-0-30-35.ap-northeast-1.compute.internal systemd-shutdown[1]: Syncing filesystems and block devices.
Mar 31 06:06:47 ip-10-0-30-35.ap-northeast-1.compute.internal systemd-shutdown[1]: Sending SIGTERM to remaining processes...
sh-5.2$
まとめ
今回の検証では、Amazon Linux 2 / Amazon Linux 2023 のいずれも、EC2 インスタンス停止時に追加 EBS ボリューム上のマウント済みファイルシステムが正常にアンマウントされることを確認できました。
Amazon Linux 2 では /var/log/messages、Amazon Linux 2023 では journalctl を確認することで、停止時の挙動を確認できました。
本ブログが誰かの参考になれば幸いです。
参考資料
Amazon EC2 インスタンスから Amazon EBS ボリュームをデタッチ - Amazon EBS
クラスメソッドオペレーションズ株式会社について
クラスメソッドグループのオペレーション企業です。
運用・保守開発・サポート・情シス・バックオフィスの専門チームが、IT・AIをフル活用した「しくみ」を通じて、お客様の業務代行から課題解決や高付加価値サービスまでを提供するエキスパート集団です。
当社は様々な職種でメンバーを募集しています。
「オペレーション・エクセレンス」と「らしく働く、らしく生きる」を共に実現するカルチャー・しくみ・働き方にご興味がある方は、クラスメソッドオペレーションズ株式会社 コーポレートサイト をぜひご覧ください。※2026年1月 アノテーション㈱から社名変更しました
