BonBonSlick
@BonBonSlick
Vanilla Web Architect

Debian stuck on «[OK] started User Manager UID 116»?

Dual Boot, Win 10 + Deb 9


Запустил утром ПК, дебиан висит при запуске.
Никаких апдейтов и апгрейдов не делал долгое время.
Проверил свободное местоdf -h4.5 гб свободно.
Как пишут все и советуют надо нажать
ALT + F3
войти в профиль, если есть пароль и ввести след команды
apt-get update
apt-get upgrade
apt-get dist-upgrade


Чтобы ввести эти команды, пришлось перезагрузить ПК раз 12-15, потому что через 5-7 сек после входа в консоль через F3 возможность ввода пропадает, консоль виснет и мигает раз в 20-30 секунд на пол секунды.

Первые 2 команды прошли безрезультатно, выдало кучу ошибок что could not resolve ...
А вот апгрейд прошел, да и еще какой Failed to mount EFI!
Теперь возможность запустить только в recovery mode.

Логи и ошибки

Первого фото где висит после старта нет.

После того как попробовал apt-get clean / autoclean / autoremove слетел GRUB, единственный вариант войти конкретную OS это выбрать ее в BIOS.

SSD Health Status

UPD.
user@debian:~$ df -h
Filesystem      Size  Used Avail Use% Mounted on
udev            7.8G     0  7.8G   0% /dev
tmpfs           1.6G  9.7M  1.6G   1% /run
/dev/sdb1        15G  2.4G   13G  17% /run/live/medium
/dev/loop0      2.2G  2.2G     0 100% /run/live/rootfs/filesystem.squashfs
tmpfs           7.8G  396M  7.4G   5% /run/live/overlay
overlay         7.8G  396M  7.4G   5% /
tmpfs           7.8G  329M  7.5G   5% /dev/shm
tmpfs           5.0M  4.0K  5.0M   1% /run/lock
tmpfs           7.8G     0  7.8G   0% /sys/fs/cgroup
tmpfs           7.8G   68K  7.8G   1% /tmp
tmpfs           1.6G  5.8M  1.6G   1% /run/user/1000
/dev/sda5        49G   38G  8.5G  82% /mnt/linux


this
got
root@debian:~# grub-install /dev/sda
grub-install: error: /usr/lib/grub/i386-pc/modinfo.sh doesn't exist. Please specify --target or --directory.

on this step
grub-install /dev/sda
root@debian:~# ls -la /usr/lib/grub/
total 56
drwxr-xr-x   3 root root  4096 Jul  6 19:03 .
drwxr-xr-x 140 root root 12288 Jul  6 13:32 ..
lrwxrwxrwx   1 root root    34 Jun 12  2019 grub-mkconfig_lib -> ../../share/grub/grub-mkconfig_lib
drwxr-xr-x   2 root root 36864 Dec 11  2019 x86_64-efi
root@debian:~#

same as
stack answer


Tried to
root@debian:/tmp# ping 208.67.222.222
PING 208.67.222.222 (208.67.222.222) 56(84) bytes of data.
64 bytes from 208.67.222.222: icmp_seq=1 ttl=49 time=38.3 ms
...
--- 208.67.222.222 ping statistics ---
5 packets transmitted, 5 received, 0% packet loss, time 4005ms
rtt min/avg/max/mdev = 38.287/38.329/38.394/0.250 ms

ping works for everything

Tried
root@debian:/#  apt install grub-customizer
Reading package lists... Done
Building dependency tree       
Reading state information... Done
E: Unable to locate package grub-customizer

==========================

root@debian:/# apt-get install grub-pc
Reading package lists... Done
Building dependency tree       
Reading state information... Done
The following packages were automatically installed and are no longer required:
  efibootmgr grub-efi-amd64-bin libefiboot1 libefivar1
Use 'sudo apt autoremove' to remove them.
The following additional packages will be installed:
  grub-pc-bin
The following packages will be REMOVED:
  grub-efi-amd64
The following NEW packages will be installed:
  grub-pc grub-pc-bin
0 upgraded, 2 newly installed, 1 to remove and 1 not upgraded.
Need to get 1,101 kB of archives.
After this operation, 3,342 kB of additional disk space will be used.
Do you want to continue? [Y/n] y
Err:1 http://debian.volia.net/debian stretch/main amd64 grub-pc-bin amd64 2.02~beta3-5+deb9u2
  Could not resolve 'debian.volia.net'
...
E: Unable to fetch some archives, maybe run apt-get update or try with --fix-missing?

==========================

root@debian:/# apt-get install grub-pc-bin
Reading package lists... Done
Building dependency tree       
Reading state information... Done
The following NEW packages will be installed:
  grub-pc-bin
0 upgraded, 1 newly installed, 0 to remove and 1 not upgraded.
Need to get 897 kB of archives.
After this operation, 2,979 kB of additional disk space will be used.
Err:1 http://debian.volia.net/debian stretch/main amd64 grub-pc-bin amd64 2.02~beta3-5+deb9u2
  Could not resolve 'debian.volia.net'
...
E: Unable to fetch some archives, maybe run apt-get update or try with --fix-missing?


=================
...


result
root@debian:~# uname -a
Linux debian 4.19.0-9-amd64 #1 SMP Debian 4.19.118-2 (2020-04-29) x86_64 GNU/Linux
root@debian:~# fdisk -l
Disk /dev/sda: 232.9 GiB, 250059350016 bytes, 488397168 sectors
Units: sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 512 bytes
I/O size (minimum/optimal): 512 bytes / 512 bytes
Disklabel type: gpt
Disk identifier: 0408DB1E-B708-4237-AE10-D7F7C20DFE25

Device         Start       End   Sectors   Size Type
/dev/sda1       2048   1023999   1021952   499M Windows recovery environment
/dev/sda2    1024000   1228799    204800   100M EFI System
/dev/sda3    1228800   1261567     32768    16M Microsoft reserved
/dev/sda4    1261568 385245183 383983616 183.1G Microsoft basic data
/dev/sda5  385245184 488396799 103151616  49.2G Linux filesystem


Disk /dev/sdb: 14.5 GiB, 15571353600 bytes, 30412800 sectors
Units: sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 512 bytes
I/O size (minimum/optimal): 512 bytes / 512 bytes
Disklabel type: dos
Disk identifier: 0x00586063

Device     Boot Start      End  Sectors  Size Id Type
/dev/sdb1  *     2048 30412799 30410752 14.5G  c W95 FAT32 (LBA)


Disk /dev/loop0: 2.1 GiB, 2288304128 bytes, 4469344 sectors
Units: sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 512 bytes
I/O size (minimum/optimal): 512 bytes / 512 bytes
root@debian:~# grub-install /dev/sda5
grub-install: error: /usr/lib/grub/i386-pc/modinfo.sh doesn't exist. Please specify --target or --directory.
root@debian:~#


sudo apt-get update; sudo apt-get install --reinstall grub
root@debian:/# sudo apt-get update; sudo apt-get install --reinstall grub
Err:1 http://debian.volia.net/debian stretch InRelease
  Could not resolve 'debian.volia.net'
...
Err:11 https://deb.nodesource.com/node_10.x stretch InRelease
  Could not resolve host: deb.nodesource.com
Reading package lists... Done
W: Failed to fetch http://debian.volia.net/debian/dists/stretch/InRelease  Could not resolve 'debian.volia.net'
...
W: Failed to fetch http://linux.teamviewer.com/deb/dists/stable/InRelease  Could not resolve 'linux.teamviewer.com'
W: Some index files failed to download. They have been ignored, or old ones used instead.
Reading package lists... Done
Building dependency tree       
Reading state information... Done
Note, selecting 'grub-legacy' instead of 'grub'
The following packages were automatically installed and are no longer required:
  efibootmgr grub-efi-amd64-bin libefiboot1 libefivar1
Use 'sudo apt autoremove' to remove them.
Suggested packages:
  grub-legacy-doc multiboot mdadm
The following packages will be REMOVED:
  grub-efi-amd64 grub2-common
The following NEW packages will be installed:
  grub-legacy
0 upgraded, 1 newly installed, 2 to remove and 1 not upgraded.
Need to get 293 kB of archives.
After this operation, 663 kB disk space will be freed.
Do you want to continue? [Y/n] y
Err:1 http://debian.volia.net/debian stretch/main amd64 grub-legacy amd64 0.97-72
  Could not resolve 'debian.volia.net'
...
E: Unable to fetch some archives, maybe run apt-get update or try with --fix-missing?

root@debian:/# grub-install --boot-directory=boot --bootloader-id=grub  --target=x86_64-efi --efi-directory=/usr/lib/grub/x86_64-efi
Installing for x86_64-efi platform.
grub-install: error: /usr/lib/grub/x86_64-efi doesn't look like an EFI partition.

root@debian:/# grub-install   --target=x86_64-efi
Installing for x86_64-efi platform.
grub-install: error: cannot find EFI directory.


Processor health
Win 10 tools showed that Memory is 100% OK.
  • Вопрос задан
  • 107 просмотров
Решения вопроса 1
BonBonSlick
@BonBonSlick Автор вопроса
Vanilla Web Architect
1 - reinstall GRUB as mentioned above, follow question description and comments! (restore boot/efi)
2 - rollback Kernel, it is possible to launch with it in Advanced mode during booting in GRUB menu.
3 - remove new Kernel

IMPORTANT! Do no run this shitty command sudo apt-get dist-upgrade, it will do more damage then fixing!

Make sure you have enough space to mount.
You also may need edit GRUB setting like default kernel to launch

Only thing I dont have time to fix right now, is that GRUB does not see Windows anymore.
Any suggestions how to fix it, appriciated.

Reason could be:
1 - mechanical demage
2 - windows damaged linux files
Ответ написан
Пригласить эксперта
Ваш ответ на вопрос

Войдите, чтобы написать ответ

Войти через центр авторизации
Похожие вопросы