컴퓨터의 전원이 꺼지는 이유 알아보기

컴퓨터의 전원이 꺼지는 이유 알아보기

오늘 컴퓨터를 켰는데 시작 작업 흐름 중에 전원이 몇 번 꺼졌습니다.

로그를 확인했지만 이유를 찾을 수 없었습니다. 14:00쯤에 전원을 켰습니다(성공적으로 부팅하는 데 여러 번 걸렸습니다).

예상치 못한 정전은 시스템 로드 후, GRUB 메뉴가 화면에 나타난 후, 비밀번호 입력 후, X-Window Manager 로드 후, 이전 브라우저 세션이 다시 시작된 후 또는 새 인터넷 페이지가 시작될 때 등 다양한 시점에 발생합니다. 열리기 시작합니다.

그러다가 지금까지 일을 하게 됐어요.

아래 목록에는 14:13 부팅 후 몇 줄, 14:19 새 부팅 전 몇 줄이 표시되어 있으며 외부 정전이 발생하기 약 6분 전에 작동했기 때문에 아마도 원인을 요약할 수 있을 것입니다. 다음과 같은 오류 메시지를 찾을 수 없습니다.

: 컴퓨터의 전원이... 이유 또는 기타 이유로 꺼져 있습니다.

manjournalctl을 읽었는데, 모르겠어요. 어떤 주제를 찾아야 합니까?

예상치 못한 정전의 정확한 원인을 찾는 방법은 무엇입니까?

아래에는 오늘 첫 번째 전원 켜기의 로그가 나열되어 있습니다. 여기에는 시작부터 정상적인 작업 흐름까지의 모든 짧은 시간이 포함되어 있습니다.

sudo Journalctl -S "오늘" -U "17:00"

 ov 04 04:40:26 debian systemd[1]: Reached target shutdown.target - System Shutdown.
Nov 04 04:40:26 debian systemd[1]: Reached target final.target - Late Shutdown Services.
Nov 04 04:40:26 debian systemd[1]: systemd-poweroff.service: Deactivated successfully.
Nov 04 04:40:26 debian systemd[1]: Finished systemd-poweroff.service - System Power Off.
Nov 04 04:40:26 debian systemd[1]: Reached target poweroff.target - System Power Off.
Nov 04 04:40:26 debian systemd[1]: Shutting down.
Nov 04 04:40:26 debian systemd-shutdown[1]: Syncing filesystems and block devices.
Nov 04 04:40:26 debian systemd-shutdown[1]: Sending SIGTERM to remaining processes...
Nov 04 04:40:26 debian systemd-journald[258]: Received SIGTERM from PID 1 (systemd-shutdow).
Nov 04 04:40:26 debian systemd-journald[258]: Journal stopped
-- Boot 5e8abe8207f54af483786970a32bfdb1 --
Nov 04 14:13:53 debian kernel: microcode: microcode updated early to revision 0x22, date = 2022-0>
Nov 04 14:13:53 debian kernel: Linux version 6.1.0-13-amd64 ([email protected]) (gcc>
Nov 04 14:13:53 debian kernel: Command line: BOOT_IMAGE=/boot/vmlinuz-6.1.0-13-amd64 root=UUID=a4>
Nov 04 14:13:53 debian kernel: BIOS-provided physical RAM map:
Nov 04 14:13:53 debian kernel: BIOS-e820: [mem 0x0000000000000000-0x000000000009b3ff] usable
Nov 04 14:13:53 debian kernel: BIOS-e820: [mem 0x000000000009b400-0x000000000009ffff] reserved
Nov 04 14:13:53 debian kernel: BIOS-e820: [mem 0x00000000000e0000-0x00000000000fffff] reserved
Nov 04 14:13:53 debian kernel: BIOS-e820: [mem 0x0000000000100000-0x000000000fffffff] usable
Nov 04 14:13:53 debian kernel: BIOS-e820: [mem 0x0000000010000000-0x0000000012150fff] reserved
Nov 04 14:13:53 debian kernel: BIOS-e820: [mem 0x0000000012151000-0x00000000771abfff] usable
Nov 04 14:13:53 debian kernel: BIOS-e820: [mem 0x00000000771ac000-0x0000000079a73fff] reserved
Nov 04 14:13:53 debian kernel: BIOS-e820: [mem 0x0000000079a74000-0x0000000079aadfff] ACPI data
Nov 04 14:13:53 debian kernel: BIOS-e820: [mem 0x0000000079aae000-0x0000000079e7cfff] ACPI NVS
Nov 04 14:13:53 debian kernel: BIOS-e820: [mem 0x0000000079e7d000-0x000000007a23dfff] reserved
Nov 04 14:13:53 debian kernel: BIOS-e820: [mem 0x000000007a23e000-0x000000007aa2cfff] usable
Nov 04 14:13:53 debian kernel: BIOS-e820: [mem 0x000000007aa2d000-0x000000007aa2dfff] ACPI NVS
Nov 04 14:13:53 debian kernel: BIOS-e820: [mem 0x000000007aa2e000-0x000000007aa2ffff] reserved
Nov 04 14:13:53 debian kernel: BIOS-e820: [mem 0x000000007aa30000-0x000000007aae4fff] usable
Nov 04 14:13:53 debian kernel: BIOS-e820: [mem 0x000000007aae5000-0x000000007ab94fff] reserved
Nov 04 14:13:53 debian kernel: BIOS-e820: [mem 0x000000007ab95000-0x000000007affffff] usable
Nov 04 14:13:53 debian kernel: BIOS-e820: [mem 0x000000007b000000-0x000000007fffffff] reserved
Nov 04 14:13:53 d

다음 부팅 전 몇 줄이므로 정전 원인을 유추할 수도 있겠지만 어느 쪽인지 이해가 되지 않습니다. 오류 메시지 없이

   ov 04 14:17:54 debian systemd[1]: Finished systemd-remount-fs.service - Remount Root and Kernel >
Nov 04 14:17:54 debian systemd[1]: systemd-firstboot.service - First Boot Wizard was skipped beca>
Nov 04 14:17:54 debian systemd[1]: systemd-pstore.service - Platform Persistent Storage Archival >
Nov 04 14:17:54 debian systemd[1]: Starting systemd-random-seed.service - Load/Save Random Seed...
Nov 04 14:17:54 debian systemd[1]: Starting systemd-sysusers.service - Create System Users...
Nov 04 14:17:54 debian kernel: lp: driver loaded but no devices found
Nov 04 14:17:54 debian kernel: ppdev: user-space parallel port driver
Nov 04 14:17:54 debian systemd[1]: Finished systemd-random-seed.service - Load/Save Random Seed.
Nov 04 14:17:54 debian systemd[1]: first-boot-complete.target - First Boot Complete was skipped b>
Nov 04 14:17:54 debian systemd[1]: Finished systemd-modules-load.service - Load Kernel Modules.
Nov 04 14:17:54 debian systemd[1]: Starting systemd-sysctl.service - Apply Kernel Variables...
Nov 04 14:17:54 debian systemd[1]: Finished systemd-sysusers.service - Create System Users.
Nov 04 14:17:54 debian systemd[1]: Starting systemd-tmpfiles-setup-dev.service - Create Static De>
Nov 04 14:17:54 debian systemd[1]: Finished systemd-sysctl.service - Apply Kernel Variables.
Nov 04 14:17:54 debian systemd-journald[259]: Journal started
Nov 04 14:17:54 debian systemd-journald[259]: Runtime Journal (/run/log/journal/337f99dad83d4d2fb>
Nov 04 14:17:53 debian systemd-modules-load[261]: Inserted module 'lp'
Nov 04 14:17:53 debian systemd-modules-load[261]: Inserted module 'ppdev'
Nov 04 14:17:53 debian systemd-modules-load[261]: Inserted module 'parport_pc'
Nov 04 14:17:54 debian systemd[1]: Started systemd-journald.service - Journal Service.
Nov 04 14:17:54 debian systemd[1]: Starting systemd-journal-flush.service - Flush Journal to Pers>
Nov 04 14:17:54 debian systemd[1]: Finished systemd-tmpfiles-setup-dev.service - Create Static De>
Nov 04 14:17:54 debian systemd[1]: Starting systemd-udevd.service - Rule-based Manager for Device>
Nov 04 14:17:54 debian systemd-journald[259]: Time spent on flushing to /var/log/journal/337f99da>
-- Boot 59ee50dd793649a3b9022074301768ee --
ov 04 14:19:07 debian kernel: microcode: microcode updated early to revision 0x22, date = 2022-0>
Nov 04 14:19:07 debian kernel: Linux version 6.1.0-13-amd64 ([email protected]) (gcc>
Nov 04 14:19:07 debian kernel: Command line: BOOT_IMAGE=/boot/vmlinuz-6.1.0-13-amd64 root=UUID=a4>
Nov 04 14:19:07 debian kernel: BIOS-provided physical RAM map:
Nov 04 14:19:07 debian kernel: BIOS-e820: [mem 0x0000000000000000-0x000000000009b3ff] usable
Nov 04 14:19:07 debian kernel: BIOS-e820: [mem 0x000000000009b400-0x000000000009ffff] reserved
Nov 04 14:19:07 debian kernel: BIOS-e820: [mem 0x00000000000e0000-0x00000000000fffff] reserved
Nov 04 14:19:07 debian kernel: BIOS-e820: [mem 0x0000000000100000-0x000000000fffffff] usable
Nov 04 14:19:07 debian kernel: BIOS-e820: [mem 0x0000000010000000-0x0000000012150fff] reserved
Nov 04 14:19:07 debian kernel: BIOS-e820: [mem 0x0000000012151000-0x00000000771abfff] usable
Nov 04 14:19:07 debian kernel: BIOS-e820: [mem 0x00000000771ac000-0x0000000079a73fff] reserved
Nov 04 14:19:07 debian kernel: BIOS-e820: [mem 0x0000000079a74000-0x0000000079aadfff] ACPI data


BIOS Information
Vendor: American Megatrends Inc.
Version: 5.13
Release Date: 10/19/2020
Address: 0xF0000
Runtime Size: 64 kB
ROM Size: 5 MB
Characteristics:
    PCI is supported
    BIOS is upgradeable
    BIOS shadowing is allowed
    Boot from CD is supported
    Selectable boot is supported
    BIOS ROM is socketed
    EDD is supported
    5.25"/1.2 MB floppy services are supported (int 13h)
    3.5"/720 kB floppy services are supported (int 13h)
    3.5"/2.88 MB floppy services are supported (int 13h)
    Print screen service is supported (int 5h)
    8042 keyboard services are supported (int 9h)
    Serial services are supported (int 14h)
    Printer services are supported (int 17h)
    ACPI is supported
    USB legacy is supported
    BIOS boot specification is supported
    Targeted content distribution is supported
    UEFI is supported
BIOS Revision: 5.13

관련 정보