Problema com Boot Repair [RESOLVIDO]

1. Problema com Boot Repair [RESOLVIDO]

Laura
lauraglima

(usa Ubuntu)

Enviado em 12/11/2020 - 00:00h

Minha gente, oi. Seguinte.. Uns meses atrás eu instalei o o linux mint 19.3 cinnamon, com 5.4.0-42-generic.. aí que começou a dar erro quando eu tentava salvar arquivos no libbreoffice e problema na inicialização do sistema. Um dia fui tentar entrar e aparecia o seguinte:
1.301019] ACPI BIOS Error (bug): Could not resolve symbol [\_SB.PCI0.LPCB.HEC.ECRD], AE_NOT_FOUND (20190816/psargs-330)
[ 1.304023] ACPI Error: Aborting method \_TZ.TZ00._TMP due to previous error
[ 1.304178] ACPI BIOS Error (bug): Could not resolve symbol [\_SB.PCI0.LPCB.H
[ 1.304185] ACPI Error: Aborting method \_TZ.TZ00._TMP due to previous error
[ 1.304257]
ACPI BIOS Error (bug): Could not resolve symbol [\_SB.PCI0.LPCB.H
[ 1.304263] ACPI Error: Aborting method \_TZ.TZ00._TMP due to previous error
[ 1.304321]ACPI BIOS Error (bug): Could not resolve symbol [\_SB.PCI0.LPCB.H
[ 1.304326] ACPI Error: Aborting method \_TZ.TZ00._TMP due to previous error
BusyBox v1.27.2 (Ubuntu 1:1.27.2-2ubuntu3.2) built-in shell (ash)
Enter 'help' for a list of built-in commands
(initramfs)

Um usuário me sugeriu dar um fsck manual no sda2. Eu fiz, deu certo. Só que comecei a ter que fazer toda vez que eu ligava. Eu sabia que mais dia, menos dia, ia zicar tudo - só que eu tô escrevendo minha tese de doutorado, então tava só ignorando a parada. Ontem, quando liguei, deu uma tela bem matrix, com números malucos rodando a tela. Desliguei no botão, consegui acessar o modo gráfico pela inicialização de segurança, formatei o pc e instalei o Linux Mint 20 Cinnamon. Acontece que quando eu fui dar o boot para instalar, já apareceram várias mensagens, mas muito rápido, não consegui ver o que era. Instalei normal. Agora, toda vez que eu ligo, aparece essa tela com mensagens muito rápidas, demora para inicializar, mas rola. Então instalei o boot repair (relatório abaixo), deu esse erro, e agora ele não desliga mais, só quando eu aperto o botão. Será que alguém consegue me ajudar?

boot-repair-4ppa125 [20201111_1401]
============================= Boot Repair Summary ==============================
Default settings: ______________________________________________________________
The default repair of the Boot-Repair utility would reinstall the grub-efi-amd64-signed of
sda2,
using the following options: sda1/boot/efi,
Additional repair would be performed: unhide-bootmenu-10s use-standard-efi-file restore-efi-backups
Final advice in case of suggested repair: ______________________________________
Please do not forget to make your UEFI firmware boot on the o SO atualmente em uso - Linux Mint 20 CurrentSession entry (sda1/efi/****/shim****.efi (**** will be updated in the final message) file) !
User settings: _________________________________________________________________
/usr/share/boot-sav/bs-cmd_terminal.sh: linha 177: aviso: substituição de comando: byte nulo ignorado na entrada
The settings chosen by the user will reinstall the grub-efi-amd64-signed of
sda2,
using the following options: sda1/boot/efi, add-kernel-option (acpi=off),
Additional repair will be performed: unhide-bootmenu-10s use-standard-efi-file restore-efi-backups
/boot/efi added in sda2/fstab
rm /boot/efi/efi/Boot/bootx64.efi
mv /boot/efi/efi/Boot/bkpbootx64.efi /boot/efi/efi/Boot/bootx64.efi
sda2/boot/efi not empty
add_kernel_option CHOSEN_KERNEL_OPTION is : acpi=off
Added kernel options in sda2/etc/default/grub
================= Reinstall the grub-efi-amd64-signed of sda2 ==================
grub-install --version
grub-install (GRUB) 2.04-1ubuntu26.6
efibootmgr -v from chroot before grub install
BootCurrent: 0000
Timeout: 0 seconds
BootOrder: 0000,0003,0001
Boot0000* ubuntu HD(1,GPT,7ad526ad-8d5b-4c12-b89c-5e6ed9b71692,0x800,0x100000)/File(EFIubuntushimx64.efi)
Boot0001* EFI USB Device (KingstonDataTraveler 2.0) PciRoot(0x0)/Pci(0x1d,0x0)/USB(0,0)/USB(1,0)/HD(1,MBR,0x4089a39b,0x288,0x1f00)RC
Boot0003* Windows Boot Manager HD(1,GPT,ec212246-7662-4033-a1b8-dd9d1c1cd341,0x800,0xfa000)/File(EFIMicrosoftBootbootmgfw.efi)WINDOWS.........x...B.C.D.O.B.J.E.C.T.=.{.9.d.e.a.8.6.2.c.-.5.c.d.d.-.4.e.7.0.-.a.c.c.1.-.f.3.2.b.3.4.4.d.4.7.9.5.}....................
uname -r
5.4.0-53-generic
grub-install --efi-directory=/boot/efi --target=x86_64-efi --uefi-secure-boot
Installing for x86_64-efi platform.
Installation finished. No error reported.
df /dev/sda1
mv /boot/efi/EFI/Boot/bootx64.efi /boot/efi/EFI/Boot/bkpbootx64.efi
cp /boot/efi/EFI/ubuntu/shimx64.efi /boot/efi/EFI/Boot/bootx64.efi
grub-install --efi-directory=/boot/efi --target=x86_64-efi --uefi-secure-boot
Installing for x86_64-efi platform.
Installation finished. No error reported.
efibootmgr -v from chroot after grub install
BootCurrent: 0000
Timeout: 0 seconds
BootOrder: 0000,0003,0001
Boot0000* ubuntu HD(1,GPT,7ad526ad-8d5b-4c12-b89c-5e6ed9b71692,0x800,0x100000)/File(EFIubuntushimx64.efi)
Boot0001* EFI USB Device (KingstonDataTraveler 2.0) PciRoot(0x0)/Pci(0x1d,0x0)/USB(0,0)/USB(1,0)/HD(1,MBR,0x4089a39b,0x288,0x1f00)RC
Boot0003* Windows Boot Manager HD(1,GPT,ec212246-7662-4033-a1b8-dd9d1c1cd341,0x800,0xfa000)/File(EFIMicrosoftBootbootmgfw.efi)WINDOWS.........x...B.C.D.O.B.J.E.C.T.=.{.9.d.e.a.8.6.2.c.-.5.c.d.d.-.4.e.7.0.-.a.c.c.1.-.f.3.2.b.3.4.4.d.4.7.9.5.}....................
Error: NVram is locked (Linuxmint not found in efibootmgr).
update-grub
Sourcing file `/etc/default/grub'
Sourcing file `/etc/default/grub.d/50_linuxmint.cfg'
Sourcing file `/etc/default/grub.d/init-select.cfg'
Generating grub configuration file ...
Found linux image: /boot/vmlinuz-5.4.0-53-generic
Found initrd image: /boot/initrd.img-5.4.0-53-generic
Found linux image: /boot/vmlinuz-5.4.0-26-generic
Found initrd image: /boot/initrd.img-5.4.0-26-generic
File descriptor 63 (pipe:[42812]) leaked on lvs invocation. Parent PID 14230: /bin/sh
Adding boot menu entry for UEFI Firmware Settings
Unhide GRUB boot menu in sda2/boot/grub/grub.cfg
Ocorreu um erro durante a reparação.
Locked-NVram detectado.
============================ Boot Info After Repair ============================
=> No boot loader is installed in the MBR of /dev/sda.
sda1: __________________________________________________________________________
File system: vfat
Boot sector type: FAT32
Boot sector info: No errors found in the Boot Parameter Block.
Operating System:
Boot files: /efi/BOOT/bkpbootx64.efi /efi/BOOT/bootx64.efi
/efi/BOOT/fbx64.efi /efi/BOOT/grubx64.efi
/efi/BOOT/mmx64.efi /efi/ubuntu/grubx64.efi
/efi/ubuntu/mmx64.efi /efi/ubuntu/shimx64.efi
/efi/ubuntu/grub.cfg
sda2: __________________________________________________________________________
File system: ext4
Boot sector type: -
Boot sector info:
Operating System: Linux Mint 20
Boot files: /boot/grub/grub.cfg /etc/fstab /etc/default/grub
================================ 1 OS detected =================================
OS#1: o SO atualmente em uso - Linux Mint 20 CurrentSession on sda2
============================ Architecture/Host Info ============================
CPU architecture: 64-bit
BOOT_IMAGE of the installed session in use:
/boot/vmlinuz-5.4.0-53-generic root=UUID=8b1bfded-b682-4421-8b50-e2246fcb5893 ro quiet splash
===================================== UEFI =====================================
BIOS is EFI-compatible, and is setup in EFI-mode for this installed-session.
SecureBoot disabled.
efibootmgr -v
BootCurrent: 0000
Timeout: 0 seconds
BootOrder: 0000,0003,0001
Boot0000* ubuntu HD(1,GPT,7ad526ad-8d5b-4c12-b89c-5e6ed9b71692,0x800,0x100000)/File(\EFI\ubuntu\shimx64.efi)
Boot0001* EFI USB Device (KingstonDataTraveler 2.0) PciRoot(0x0)/Pci(0x1d,0x0)/USB(0,0)/USB(1,0)/HD(1,MBR,0x4089a39b,0x288,0x1f00)RC
Boot0003* Windows Boot Manager HD(1,GPT,ec212246-7662-4033-a1b8-dd9d1c1cd341,0x800,0xfa000)/File(\EFI\Microsoft\Boot\bootmgfw.efi)WINDOWS.........x...B.C.D.O.B.J.E.C.T.=.{.9.d.e.a.8.6.2.c.-.5.c.d.d.-.4.e.7.0.-.a.c.c.1.-.f.3.2.b.3.4.4.d.4.7.9.5.}....................
78415fb8fb9b909f8029858113f1335f sda1/BOOT/bkpbootx64.efi
78415fb8fb9b909f8029858113f1335f sda1/BOOT/bootx64.efi
2895d47544fd587b26c7e29be1295c27 sda1/BOOT/fbx64.efi
d8b4b9ae3018b1f4612611be7f42507a sda1/BOOT/grubx64.efi
dc3c47be2f78a78e5e57d097ae6c5c84 sda1/BOOT/mmx64.efi
d8b4b9ae3018b1f4612611be7f42507a sda1/ubuntu/grubx64.efi
dc3c47be2f78a78e5e57d097ae6c5c84 sda1/ubuntu/mmx64.efi
78415fb8fb9b909f8029858113f1335f sda1/ubuntu/shimx64.efi
============================= Drive/Partition Info =============================
Disks info: ____________________________________________________________________
sda : is-GPT, no-BIOSboot, has---ESP, not-usb, not-mmc, has-os, 2048 sectors * 512 bytes
Partitions info (1/3): _________________________________________________________
sda2 : is-os, 64, apt-get, signed grub-pc grub-efi , grub2, grub-install, grubenv-ok, update-grub, farbios
sda1 : no-os, 32, nopakmgr, no-docgrub, nogrub, nogrubinstall, no-grubenv, noupdategrub, not-far
Partitions info (2/3): _________________________________________________________
sda2 : isnotESP, fstab-has-goodEFI, no-nt, no-winload, no-recov-nor-hid, no-bmgr, notwinboot
sda1 : is---ESP, part-has-no-fstab, no-nt, no-winload, no-recov-nor-hid, no-bmgr, notwinboot
Partitions info (3/3): _________________________________________________________
sda2 : not-sepboot, with-boot, fstab-without-boot, not-sep-usr, with--usr, fstab-without-usr, std-grub.d, sda
sda1 : not-sepboot, no-boot, part-has-no-fstab, not-sep-usr, no---usr, part-has-no-fstab, std-grub.d, sda
fdisk -l (filtered): ___________________________________________________________
Disk sda: 465.78 GiB, 500107862016 bytes, 976773168 sectors
Disk identifier: B3B16B9A-158D-4BAB-8116-A82AD05024B2
Start End Sectors Size Type
sda1 2048 1050623 1048576 512M EFI System
sda2 1050624 976771071 975720448 465.3G Linux filesystem
parted -lm (filtered): _________________________________________________________
sda:500GB:scsi:512:4096:gpt:ATA TOSHIBA MQ02ABF0:;
1:1049kB:538MB:537MB:fat32:EFI System Partition:boot, esp;
2:538MB:500GB:500GB:ext4::;
blkid (filtered): ______________________________________________________________
NAME FSTYPE UUID PARTUUID LABEL PARTLABEL
sda
├─sda1 vfat 9C11-2CC8 7ad526ad-8d5b-4c12-b89c-5e6ed9b71692 EFI System Partition
└─sda2 ext4 8b1bfded-b682-4421-8b50-e2246fcb5893 602609c6-68bd-46af-aafa-c77d3b9f717e
df (filtered): _________________________________________________________________
Avail Use% Mounted on
sda2 411G 5% /
Mount options: __________________________________________________________________
sda2 rw,relatime,errors=remount-ro
===================== sda1/efi/ubuntu/grub.cfg (filtered) ======================
search.fs_uuid 8b1bfded-b682-4421-8b50-e2246fcb5893 root hd0,gpt2
set prefix=($root)'/boot/grub'
configfile $prefix/grub.cfg
====================== sda2/boot/grub/grub.cfg (filtered) ======================
Ubuntu 8b1bfded-b682-4421-8b50-e2246fcb5893
Ubuntu, with Linux 5.4.0-53-generic 8b1bfded-b682-4421-8b50-e2246fcb5893
Ubuntu, with Linux 5.4.0-26-generic 8b1bfded-b682-4421-8b50-e2246fcb5893
### END /etc/grub.d/30_os-prober ###
UEFI Firmware Settings uefi-firmware
### END /etc/grub.d/30_uefi-firmware ###
========================== sda2/etc/fstab (filtered) ===========================
# <file system> <mount point> <type> <options> <dump> <pass>
# / was on /dev/sda2 during installation
UUID=8b1bfded-b682-4421-8b50-e2246fcb5893 / ext4 errors=remount-ro 0 1
# /boot/efi was on /dev/sda1 during installation
/swapfile none swap sw 0 0
UUID=9C11-2CC8 /boot/efi vfat defaults 0 1
======================= sda2/etc/default/grub (filtered) =======================
GRUB_DEFAULT=0
GRUB_TIMEOUT_STYLE=hidden
GRUB_TIMEOUT=10
GRUB_DISTRIBUTOR=`lsb_release -i -s 2> /dev/null || echo Debian`
GRUB_CMDLINE_LINUX_DEFAULT="quiet splash acpi=off"
GRUB_CMDLINE_LINUX=""
==================== sda2: Location of files loaded by Grub ====================
GiB - GB File Fragment(s)
80.657123566 = 86.604926976 boot/grub/grub.cfg 1
8.277477264 = 8.887873536 boot/vmlinuz 1
4.800895691 = 5.154922496 boot/vmlinuz-5.4.0-26-generic 1
8.277477264 = 8.887873536 boot/vmlinuz-5.4.0-53-generic 1
4.800895691 = 5.154922496 boot/vmlinuz.old 1
2.997028351 = 3.218034688 boot/initrd.img 1
8.719722748 = 9.362731008 boot/initrd.img-5.4.0-26-generic 3
2.997028351 = 3.218034688 boot/initrd.img-5.4.0-53-generic 1
8.719722748 = 9.362731008 boot/initrd.img.old 3
===================== sda2: ls -l /etc/grub.d/ (filtered) ======================
-rwxr-xr-x 1 root root 17622 out 1 12:19 10_linux
-rwxr-xr-x 1 root root 42359 out 1 12:19 10_linux_zfs
-rwxr-xr-x 1 root root 12894 abr 15 2020 20_linux_xen
-rwxr-xr-x 1 root root 12059 abr 15 2020 30_os-prober
-rwxr-xr-x 1 root root 1424 abr 15 2020 30_uefi-firmware
-rwxr-xr-x 1 root root 214 abr 15 2020 40_custom
-rwxr-xr-x 1 root root 216 abr 15 2020 41_custom
=============================== StdErr Messages ================================
File descriptor 63 (pipe:[42812]) leaked on lvs invocation. Parent PID 2037: /bin/bash


  


2. Re: Problema com Boot Repair [RESOLVIDO]

leandro peçanha scardua
leandropscardua

(usa Ubuntu)

Enviado em 12/11/2020 - 10:18h

Vamos olhar os logs do shutdown
journalctl -rb -1
Se a saídafor mto grande rode
journalctl -rb -1 | head -n 20
Qto ao bootrepair vamos ver se os problemas estão relacionados.


3. Re: Problema com Boot Repair [RESOLVIDO]

Laura
lauraglima

(usa Ubuntu)

Enviado em 12/11/2020 - 10:43h

-- Logs begin at Wed 2020-11-11 11:52:50 -03, end at Thu 2020-11-12 10:38:30 -0>
nov 12 10:09:43 hima-Inspiron-7348 systemd-journald[369]: Journal stopped
nov 12 10:09:43 hima-Inspiron-7348 systemd-shutdown[1]: Sending SIGTERM to rema>
nov 12 10:09:43 hima-Inspiron-7348 systemd-shutdown[1]: Syncing filesystems and>
nov 12 10:09:43 hima-Inspiron-7348 systemd[1]: Shutting down.
nov 12 10:09:43 hima-Inspiron-7348 systemd[1]: Reached target Reboot.
nov 12 10:09:43 hima-Inspiron-7348 systemd[1]: Finished Reboot.
nov 12 10:09:43 hima-Inspiron-7348 systemd[1]: systemd-reboot.service: Succeede>
nov 12 10:09:43 hima-Inspiron-7348 systemd[1]: Reached target Final Step.
nov 12 10:09:43 hima-Inspiron-7348 systemd[1]: Finished Shuts down the "live" p>
nov 12 10:09:43 hima-Inspiron-7348 systemd[1]: casper.service: Succeeded.
nov 12 10:09:43 hima-Inspiron-7348 systemd[1]: Starting Shuts down the "live" p>
nov 12 10:09:43 hima-Inspiron-7348 systemd[1]: Reached target Shutdown.
nov 12 10:09:43 hima-Inspiron-7348 systemd[1]: Stopped Monitoring of LVM2 mirro>
nov 12 10:09:43 hima-Inspiron-7348 systemd[1]: lvm2-monitor.service: Succeeded.
nov 12 10:09:43 hima-Inspiron-7348 systemd[1]: Stopped Remount Root and Kernel >
nov 12 10:09:43 hima-Inspiron-7348 systemd[1]: systemd-remount-fs.service: Succ>
nov 12 10:09:43 hima-Inspiron-7348 systemd[1]: Stopped Create System Users.
nov 12 10:09:43 hima-Inspiron-7348 systemd[1]: systemd-sysusers.service: Succee>
nov 12 10:09:43 hima-Inspiron-7348 systemd[1]: Stopped Create Static Device Nod>
nov 12 10:09:43 hima-Inspiron-7348 systemd[1]: systemd-tmpfiles-setup-dev.servi>
nov 12 10:09:43 hima-Inspiron-7348 systemd[1]: Stopping Monitoring of LVM2 mirr>
nov 12 10:09:43 hima-Inspiron-7348 systemd[1]: Stopped target Local File System>
lines 1-23...skipping...
-- Logs begin at Wed 2020-11-11 11:52:50 -03, end at Thu 2020-11-12 10:38:30 -03. --
nov 12 10:09:43 hima-Inspiron-7348 systemd-journald[369]: Journal stopped
nov 12 10:09:43 hima-Inspiron-7348 systemd-shutdown[1]: Sending SIGTERM to remaining processes...
nov 12 10:09:43 hima-Inspiron-7348 systemd-shutdown[1]: Syncing filesystems and block devices.
nov 12 10:09:43 hima-Inspiron-7348 systemd[1]: Shutting down.
nov 12 10:09:43 hima-Inspiron-7348 systemd[1]: Reached target Reboot.
nov 12 10:09:43 hima-Inspiron-7348 systemd[1]: Finished Reboot.
nov 12 10:09:43 hima-Inspiron-7348 systemd[1]: systemd-reboot.service: Succeeded.
nov 12 10:09:43 hima-Inspiron-7348 systemd[1]: Reached target Final Step.
nov 12 10:09:43 hima-Inspiron-7348 systemd[1]: Finished Shuts down the "live" preinstalled system cleanly.
nov 12 10:09:43 hima-Inspiron-7348 systemd[1]: casper.service: Succeeded.
nov 12 10:09:43 hima-Inspiron-7348 systemd[1]: Starting Shuts down the "live" preinstalled system cleanly...
nov 12 10:09:43 hima-Inspiron-7348 systemd[1]: Reached target Shutdown.
nov 12 10:09:43 hima-Inspiron-7348 systemd[1]: Stopped Monitoring of LVM2 mirrors, snapshots etc. using dmeventd or progress polling.
nov 12 10:09:43 hima-Inspiron-7348 systemd[1]: lvm2-monitor.service: Succeeded.
nov 12 10:09:43 hima-Inspiron-7348 systemd[1]: Stopped Remount Root and Kernel File Systems.
nov 12 10:09:43 hima-Inspiron-7348 systemd[1]: systemd-remount-fs.service: Succeeded.
nov 12 10:09:43 hima-Inspiron-7348 systemd[1]: Stopped Create System Users.
nov 12 10:09:43 hima-Inspiron-7348 systemd[1]: systemd-sysusers.service: Succeeded.
nov 12 10:09:43 hima-Inspiron-7348 systemd[1]: Stopped Create Static Device Nodes in /dev.
nov 12 10:09:43 hima-Inspiron-7348 systemd[1]: systemd-tmpfiles-setup-dev.service: Succeeded.
nov 12 10:09:43 hima-Inspiron-7348 systemd[1]: Stopping Monitoring of LVM2 mirrors, snapshots etc. using dmeventd or progress polling...
nov 12 10:09:43 hima-Inspiron-7348 systemd[1]: Stopped target Local File Systems (Pre).
nov 12 10:09:43 hima-Inspiron-7348 systemd[1]: Removed slice system-systemd\x2dfsck.slice.
nov 12 10:09:43 hima-Inspiron-7348 systemd[1]: Stopped File System Check on /dev/disk/by-uuid/9C11-2CC8.
nov 12 10:09:43 hima-Inspiron-7348 systemd[1]: [email protected]\x2duuid-9C11\x2d2CC8.service: Succeeded.
nov 12 10:09:43 hima-Inspiron-7348 systemd[1]: Reached target Unmount All Filesystems.
nov 12 10:09:43 hima-Inspiron-7348 systemd[1]: Unmounted /boot/efi.
nov 12 10:09:43 hima-Inspiron-7348 systemd[1]: boot-efi.mount: Succeeded.
nov 12 10:09:43 hima-Inspiron-7348 systemd[1]: Unmounting /boot/efi...
nov 12 10:09:43 hima-Inspiron-7348 systemd[1]: Stopped target Local File Systems.
nov 12 10:09:43 hima-Inspiron-7348 systemd[1]: Stopped Create Volatile Files and Directories.
nov 12 10:09:43 hima-Inspiron-7348 systemd[1]: systemd-tmpfiles-setup.service: Succeeded.
nov 12 10:09:43 hima-Inspiron-7348 systemd[1]: Stopped Update UTMP about System Boot/Shutdown.
nov 12 10:09:43 hima-Inspiron-7348 systemd[1]: systemd-update-utmp.service: Succeeded.
nov 12 10:09:43 hima-Inspiron-7348 systemd[1]: Removed slice system-systemd\x2dbacklight.slice.
nov 12 10:09:43 hima-Inspiron-7348 systemd[1]: Stopped Load/Save Screen Backlight Brightness of backlight:intel_backlight.
nov 12 10:09:43 hima-Inspiron-7348 systemd[1]: [email protected]:intel_backlight.service: Succeeded.
nov 12 10:09:43 hima-Inspiron-7348 systemd[1]: Deactivated swap /swapfile.
nov 12 10:09:43 hima-Inspiron-7348 systemd[1]: swapfile.swap: Succeeded.
nov 12 10:09:43 hima-Inspiron-7348 systemd[1]: Stopped Network Time Synchronization.
nov 12 10:09:43 hima-Inspiron-7348 systemd[1]: systemd-timesyncd.service: Succeeded.
nov 12 10:09:43 hima-Inspiron-7348 systemd[1]: Stopping Update UTMP about System Boot/Shutdown...
nov 12 10:09:43 hima-Inspiron-7348 systemd[1]: Stopping Network Time Synchronization...
nov 12 10:09:43 hima-Inspiron-7348 systemd[1]: Stopped Load Kernel Modules.
nov 12 10:09:43 hima-Inspiron-7348 systemd[1]: systemd-modules-load.service: Succeeded.
nov 12 10:09:43 hima-Inspiron-7348 systemd[1]: Stopped Apply Kernel Variables.
nov 12 10:09:43 hima-Inspiron-7348 systemd[1]: systemd-sysctl.service: Succeeded.
nov 12 10:09:43 hima-Inspiron-7348 systemd[1]: Stopping Load/Save Screen Backlight Brightness of backlight:intel_backlight...
nov 12 10:09:43 hima-Inspiron-7348 systemd[1]: Deactivating swap /swapfile...

Por sugestão eu fui dar uma olhada na BIOS, e percebi que tava com o boot em legacy, troquei para UEFI, desativei a opção secure boot, rodei o boot repair, ainda assim nada (Como desde ontem tá isso de não desligar e eu tive que entrar na Bios algumas vezes, liguei e desliguei rapidamente pelo botão).



4. Re: Problema com Boot Repair [RESOLVIDO]

Laura
lauraglima

(usa Ubuntu)

Enviado em 12/11/2020 - 10:53h

Nao sei se essa tela aqui ajuda algo... quando eu tento desligar, fica com a logo do mint, se eu aperto alguma tecla f, aparece ela


5. Re: Problema com Boot Repair [RESOLVIDO]

Laura
lauraglima

(usa Ubuntu)

Enviado em 12/11/2020 - 11:05h

COnsegui resolver a questão do desligar e dar reboot da seguinte forma. Me foi sugerido que poderia ser uma questão de ACPI - o meu tava off. Só que no BIOS não existia a opção de gerenciamento de energia, então eu mexi editando as configurações do grub.
na linha GRUB_CMDLINE_LINUX_DEFAULT="quiet splash acpi=off" tentei colocar acpi=force (sugestão num tutorial) não deu certo, coloquei acpi=on daí ele tá rebootando e desligando normal. Para ligar ainda tá demorando mais do que o esperado e aparecem mensagens rápidas na tela (que eu não consigo ler).. não sei se é algo que eu posso só ignorar ou que vai zuar tudo daqui em pouco tempo.


6. Re: Problema com Boot Repair [RESOLVIDO]

leandro peçanha scardua
leandropscardua

(usa Ubuntu)

Enviado em 12/11/2020 - 17:20h

lauraglima escreveu:

COnsegui resolver a questão do desligar e dar reboot da seguinte forma. Me foi sugerido que poderia ser uma questão de ACPI - o meu tava off. Só que no BIOS não existia a opção de gerenciamento de energia, então eu mexi editando as configurações do grub.
na linha GRUB_CMDLINE_LINUX_DEFAULT="quiet splash acpi=off" tentei colocar acpi=force (sugestão num tutorial) não deu certo, coloquei acpi=on daí ele tá rebootando e desligando normal. Para ligar ainda tá demorando mais do que o esperado e aparecem mensagens rápidas na tela (que eu não consigo ler).. não sei se é algo que eu posso só ignorar ou que vai zuar tudo daqui em pouco tempo.

As mensagens q vc colocou no 1o post ainda permanecem?
Para analisar o tempo de boot digite
systemd-analyze blame
P analisar msgs de erro digite
dmesg --level=err, warn



7. Re: Problema com Boot Repair [RESOLVIDO]

Laura
lauraglima

(usa Ubuntu)

Enviado em 13/11/2020 - 09:50h

Sim, continuam. e são de ACPI ó. Você tem ideia do que pode ser?
(ah, obrigada pela ajuda!)

[ 0.000000] DMAR: [Firmware Bug]: No firmware reserved region can cover this RMRR [0x000000009d800000-0x000000009fffffff], contact BIOS vendor for fixes
[ 0.510904] ACPI BIOS Error (bug): Could not resolve symbol [\_SB.PCI0.LPCB.HEC.ECRD], AE_NOT_FOUND (20200528/psargs-330)
[ 0.510957] ACPI Error: Aborting method \_TZ.TZ00._TMP due to previous error (AE_NOT_FOUND) (20200528/psparse-529)
[ 0.511130] ACPI BIOS Error (bug): Could not resolve symbol [\_SB.PCI0.LPCB.HEC.ECRD], AE_NOT_FOUND (20200528/psargs-330)
[ 0.511179] ACPI Error: Aborting method \_TZ.TZ00._TMP due to previous error (AE_NOT_FOUND) (20200528/psparse-529)
[ 0.511286] ACPI BIOS Error (bug): Could not resolve symbol [\_SB.PCI0.LPCB.HEC.ECRD], AE_NOT_FOUND (20200528/psargs-330)
[ 0.511333] ACPI Error: Aborting method \_TZ.TZ01._TMP due to previous error (AE_NOT_FOUND) (20200528/psparse-529)
[ 0.511432] ACPI BIOS Error (bug): Could not resolve symbol [\_SB.PCI0.LPCB.HEC.ECRD], AE_NOT_FOUND (20200528/psargs-330)
[ 0.511480] ACPI Error: Aborting method \_TZ.TZ01._TMP due to previous error (AE_NOT_FOUND) (20200528/psparse-529)
[ 5.498347] Bluetooth: hci0: unexpected event for opcode 0xfc2f



8. Re: Problema com Boot Repair [RESOLVIDO]

Laura
lauraglima

(usa Ubuntu)

Enviado em 13/11/2020 - 11:52h

Atualizei a BIOS da Dell, mas as mensagens de erro continuam.
o comando err, deu essa saída:
[ 0.000000] DMAR: [Firmware Bug]: No firmware reserved region can cover this RMRR [0x000000009d800000-0x000000009fffffff], contact BIOS vendor for fixes
[ 0.517875] ACPI BIOS Error (bug): Could not resolve symbol [\_SB.PCI0.LPCB.HEC.ECRD], AE_NOT_FOUND (20200528/psargs-330)
[ 0.517927] ACPI Error: Aborting method \_TZ.TZ00._TMP due to previous error (AE_NOT_FOUND) (20200528/psparse-529)
[ 0.518100] ACPI BIOS Error (bug): Could not resolve symbol [\_SB.PCI0.LPCB.HEC.ECRD], AE_NOT_FOUND (20200528/psargs-330)
[ 0.518147] ACPI Error: Aborting method \_TZ.TZ00._TMP due to previous error (AE_NOT_FOUND) (20200528/psparse-529)
[ 0.518253] ACPI BIOS Error (bug): Could not resolve symbol [\_SB.PCI0.LPCB.HEC.ECRD], AE_NOT_FOUND (20200528/psargs-330)
[ 0.518300] ACPI Error: Aborting method \_TZ.TZ01._TMP due to previous error (AE_NOT_FOUND) (20200528/psparse-529)
[ 0.518398] ACPI BIOS Error (bug): Could not resolve symbol [\_SB.PCI0.LPCB.HEC.ECRD], AE_NOT_FOUND (20200528/psargs-330)
[ 0.518445] ACPI Error: Aborting method \_TZ.TZ01._TMP due to previous error (AE_NOT_FOUND) (20200528/psparse-529)


o comando warn deu essa saída aqui:


[ 0.000000] Malformed early option 'acpi'
[ 0.000000] DMAR: [Firmware Bug]: Your BIOS is broken; bad RMRR [0x000000009d800000-0x000000009fffffff]
BIOS vendor: Dell Inc.; Ver: A15; Product Version: A15
[ 0.016028] MDS CPU bug present and SMT on, data leak possible. See https://www.kernel.org/doc/html/latest/admin-guide/hw-vuln/mds.html for more details.
[ 0.016161] #3
[ 0.020768] ENERGY_PERF_BIAS: Set to 'normal', was 'performance'
[ 0.211505] pci 0000:00:14.0: can't derive routing for PCI INT A
[ 0.211506] pci 0000:00:14.0: PCI INT A: no GSI - using ISA IRQ 7
[ 0.517925] No Local Variables are initialized for Method [_TMP]
[ 0.517926] No Arguments are initialized for method [_TMP]
[ 0.518145] No Local Variables are initialized for Method [_TMP]
[ 0.518146] No Arguments are initialized for method [_TMP]
[ 0.518298] No Local Variables are initialized for Method [_TMP]
[ 0.518299] No Arguments are initialized for method [_TMP]
[ 0.518443] No Local Variables are initialized for Method [_TMP]
[ 0.518444] No Arguments are initialized for method [_TMP]
[ 0.546531] platform eisa.0: EISA: Cannot allocate resource for mainboard
[ 0.546532] platform eisa.0: Cannot allocate resource for EISA slot 1
[ 0.546533] platform eisa.0: Cannot allocate resource for EISA slot 2
[ 0.546534] platform eisa.0: Cannot allocate resource for EISA slot 3
[ 0.546535] platform eisa.0: Cannot allocate resource for EISA slot 4
[ 0.546536] platform eisa.0: Cannot allocate resource for EISA slot 5
[ 0.546536] platform eisa.0: Cannot allocate resource for EISA slot 6
[ 0.546537] platform eisa.0: Cannot allocate resource for EISA slot 7
[ 0.546538] platform eisa.0: Cannot allocate resource for EISA slot 8
[ 1.064299] i2c_hid i2c-DLL0675:00: supply vdd not found, using dummy regulator
[ 1.064318] i2c_hid i2c-DLL0675:00: supply vddl not found, using dummy regulator
[ 1.092527] wmi_bus wmi_bus-PNP0C14:00: WQBC data block query control method not found
[ 1.094085] xhci_hcd 0000:00:14.0: can't derive routing for PCI INT A
[ 1.094088] xhci_hcd 0000:00:14.0: PCI INT A: no GSI - using ISA IRQ 7
[ 1.104660] usb: port power management may be unreliable
[ 4.348477] Started bpfilter
[ 5.030587] at24 1-0050: supply vcc not found, using dummy regulator
[ 5.184417] iwlwifi 0000:01:00.0: Direct firmware load for iwl-debug-yoyo.bin failed with error -2
[ 5.252624] uvcvideo 2-5:1.0: Entity type for entity Extension 4 was not initialized!
[ 5.252627] uvcvideo 2-5:1.0: Entity type for entity Extension 3 was not initialized!
[ 5.252628] uvcvideo 2-5:1.0: Entity type for entity Processing 2 was not initialized!
[ 5.252630] uvcvideo 2-5:1.0: Entity type for entity Camera 1 was not initialized!
[ 5.327186] thermal thermal_zone7: failed to read out thermal zone (-61)
[ 7.006633] iwlwifi 0000:01:00.0: FW already configured (0) - re-configuring
[ 61.338990] [UFW BLOCK] IN=wlp1s0 OUT= MAC=01:00:5e:00:00:01:a8:6a:bb:c8:ce:be:08:00 SRC=192.168.0.1 DST=224.0.0.1 LEN=36 TOS=0x00 PREC=0x00 TTL=1 ID=25310 DF PROTO=2



9. Re: Problema com Boot Repair [RESOLVIDO]

rafael
rgmprd

(usa elementary OS)

Enviado em 25/02/2021 - 02:11h

Olá, houve alguma solução definitiva para este problema?

Pergunto para evitar abrir novo tópico, estou com um problema semelhante.


10. Re: Problema com Boot Repair [RESOLVIDO]

Laura
lauraglima

(usa Ubuntu)

Enviado em 25/02/2021 - 13:14h

Então, eu voltei para o Mint 19 e pro kernel 4.15; provavelmente foi um problema na isntalação do 20 ou uma incompatibilidade de kernel com a máquina (que é de 2015). também existe a possibilidade deu estar tendo erros no HD, então to planejando trocar por um SDD em breve.






Patrocínio

Site hospedado pelo provedor RedeHost.
Linux banner
Linux banner
Linux banner

Destaques

Artigos

Dicas

Tópicos

Top 10 do mês

Scripts