Não consigo inicializar no Ubuntu 16.04 depois de instalar o Ubuntu 18.04 (em uma partição separada)

0

Eu tenho um sistema de inicialização múltipla com dois discos rígidos:

  • Windows e algumas versões antigas do Ubuntu em / dev / sda
  • Ubuntu 16.04 em / dev / sdb1

Então eu instalei o Ubuntu 18.04 na partição vazia / dev / sdb2. Eu não lembro onde o carregador de boot antigo estava localizado, então escolhi o / dev / sdb para o novo bootloader.

Agora eu posso inicializar o Ubuntu 18.04 sem problemas, mas quando eu inicio o Ubuntu 16.04, eu entendo isso: 

[   1.820371] [drm:intel_set_pch_fifo_underrun_reporting [i915]] *ERROR* uncleared pch fifo underrun on pch transcoder A
[   1.820395] [drm:intel_pch_fifo_underrun_irq_handler [i915]]  *ERROR* PCH transcoder A FIFO underrun
[   2.023723] usb 2-1.6: string descriptor 0 read error: -22
ssd1: clean, ... files, ... blocks
[   5.074685] usb 2-1.6: string descriptor 0 read error: -22
Welcome to emergency mode! After logging in, ...

Eu já tentei entrar no modo de recuperação e correr sudo fsck -f / dev / sdb1 , mas sem sucesso.

Como posso reparar isso?

EDITAR:

Meu boot.log: 

$ cat boot.log
[  OK  ] Started Show Plymouth Boot Screen.
[  OK  ] Mounted /media/ssd3.
[  OK  ] Started Forward Password Requests to Plymouth Directory Watch.
[  OK  ] Started Braille Device Support.
[  OK  ] Found device ST9500325AS 6.
[  OK  ] Found device ST9500325AS 7.
[  OK  ] Found device ST9500325AS 5.
[  OK  ] Found device ST9500325AS Acer.
         Mounting /media/C...
         Activating swap /dev/disk/by-uuid/d7c7e54d-0eb9-49e9-bdba-de11b5637723...
         Starting File System Check on /dev/disk/by-uuid/425e03d0-535c-4c23-9570-b7a03afc2b39...
         Starting File System Check on /dev/disk/by-uuid/99158754-acff-4379-9640-1adc6edb157e...
[  OK  ] Activated swap /dev/disk/by-uuid/d7c7e54d-0eb9-49e9-bdba-de11b5637723.
[  OK  ] Reached target Swap.
[  OK  ] Found device ST9500325AS Daten.
         Mounting /media/E...
[  OK  ] Started File System Check on /dev/disk/by-uuid/425e03d0-535c-4c23-9570-b7a03afc2b39.
         Mounting /media/ubuntu1210...
[  OK  ] Found device ST9500325AS shared.
         Starting File System Check on /dev/disk/by-uuid/661027b0-7fb9-4e5b-bc30-4bdf232eda36...
[  OK  ] Mounted /media/ubuntu1210.
[  OK  ] Started File System Check on /dev/disk/by-uuid/99158754-acff-4379-9640-1adc6edb157e.
         Mounting /media/ubuntu1404...
[  OK  ] Mounted /media/ubuntu1404.
[  OK  ] Mounted /media/C.
[  OK  ] Mounted /media/E.
[  OK  ] Started File System Check on /dev/disk/by-uuid/661027b0-7fb9-4e5b-bc30-4bdf232eda36.
         Mounting /media/shared...
[  OK  ] Mounted /media/shared.
[ TIME ] Timed out waiting for device dev-disk-by\x2duuid-57f163ae\x2d54d6\x2d4c56\x2db5c7\x2d84e1d5e4b438.device.
[DEPEND] Dependency failed for File System Check on /dev/disk/by-uuid/57f163ae-54d6-4c56-b5c7-84e1d5e4b438.
[DEPEND] Dependency failed for /media/ssd2.
[DEPEND] Dependency failed for Local File Systems.
[DEPEND] Dependency failed for Clean up any mess left by 0dns-up.
         Starting Set console font and keymap...
         Starting Enable support for additional executable binary formats...
[  OK  ] Stopped Clean PHP session files every 30 mins.
[  OK  ] Stopped target Graphical Interface.
[  OK  ] Stopped Accounts Service.
[  OK  ] Started Stop ureadahead data collection 45s after completed startup.
[  OK  ] Closed UUID daemon activation socket.
[  OK  ] Stopped Getty on tty1.
[  OK  ] Stopped getty on tty2-tty6 if dbus and logind are not available.
[  OK  ] Stopped Daily apt upgrade and clean activities.
[  OK  ] Stopped Daily apt download activities.
[  OK  ] Stopped Bluetooth service.
[  OK  ] Reached target Bluetooth.
[  OK  ] Stopped Save/Restore Sound Card State.
[  OK  ] Stopped Manage Sound Card State (restore and store).
[  OK  ] Stopped ACPI Events Check.
[  OK  ] Stopped Light Display Manager.
[  OK  ] Stopped Detect the available GPUs and deal with any system changes.
[  OK  ] Stopped Daily Cleanup of Temporary Directories.
[  OK  ] Stopped Timer to automatically fetch and run repair assertions.
[  OK  ] Reached target Timers.
[  OK  ] Stopped IIO Sensor Proxy service.
[  OK  ] Closed Unix socket for apport crash forwarding.
[  OK  ] Closed ACPID Listen Socket.
[  OK  ] Stopped target Multi-User System.
[  OK  ] Stopped LSB: Speech Dispatcher.
[  OK  ] Stopped Make remote CUPS printers available locally.
[  OK  ] Stopped CUPS Scheduler.
[  OK  ] Closed CUPS Scheduler.
[  OK  ] Stopped LSB: Set the CPU Frequency Scaling governor to "ondemand".
[  OK  ] Stopped Modem Manager.
[  OK  ] Stopped Cgroup management proxy.
[  OK  ] Stopped Restore /etc/resolv.conf if the system crashed before the ppp link was shut down.
[  OK  ] Stopped Initialize hardware monitoring sensors.
[  OK  ] Stopped LSB: Start xrdp and sesman daemons.
[  OK  ] Stopped Login Service.
[  OK  ] Stopped TeamViewer remote control daemon.
[  OK  ] Stopped Network Manager Wait Online.
[  OK  ] Stopped crash report submission daemon.
[  OK  ] Stopped LSB: automatic crash report generation.
[  OK  ] Stopped The PHP 7.0 FastCGI Process Manager.
[  OK  ] Stopped Auto import assertions from block devices.
[  OK  ] Stopped Avahi mDNS/DNS-SD Stack.
[  OK  ] Stopped LSB: Apache2 web server.
[  OK  ] Stopped Regular background program processing daemon.
[  OK  ] Stopped Network Manager.
[  OK  ] Stopped LSB: Record successful boot for GRUB.
[  OK  ] Stopped Hold until boot process finishes up.
[  OK  ] Stopped /etc/rc.local Compatibility.
[  OK  ] Stopped Permit User Sessions.
         Starting Set console scheme...
[  OK  ] Stopped Snappy daemon.
[  OK  ] Closed Socket activation for snappy daemon.
[  OK  ] Stopped CUPS Scheduler.
[  OK  ] Stopped Automatically repair incorrect owner/permissions on core devices.
[  OK  ] Stopped Unattended Upgrades Shutdown.
[  OK  ] Stopped LSB: daemon to balance interrupts for SMP systems.
[  OK  ] Stopped MySQL Community Server.
[  OK  ] Stopped System Logging Service.
[  OK  ] Closed Syslog Socket.
[  OK  ] Stopped Run anacron jobs.
[  OK  ] Stopped D-Bus System Message Bus.
[  OK  ] Reached target Login Prompts.
[  OK  ] Stopped Cgroup management daemon.
[  OK  ] Closed Avahi mDNS/DNS-SD Stack Activation Socket.
[  OK  ] Stopped Thermal Daemon Service.
[  OK  ] Stopped target Basic System.
[  OK  ] Reached target Paths.
[  OK  ] Closed D-Bus System Message Bus Socket.
[  OK  ] Reached target Sockets.
[  OK  ] Stopped target System Initialization.
[  OK  ] Started Emergency Shell.
[  OK  ] Reached target Emergency Mode.
         Starting Create Volatile Files and Directories...
         Starting LSB: AppArmor initialization...
         Starting Tell Plymouth To Write Out Runtime Data...
         Starting Nameserver information manager...
[  OK  ] Started Set console scheme.
[  OK  ] Started Nameserver information manager.
[  OK  ] Started Create Volatile Files and Directories.
[  OK  ] Started Tell Plymouth To Write Out Runtime Data.
         Starting Network Time Synchronization...
         Starting Update UTMP about System Boot/Shutdown...
[  OK  ] Reached target Network (Pre).
         Mounting Arbitrary Executable File Formats File System...
[  OK  ] Started Set console font and keymap.
[  OK  ] Mounted Arbitrary Executable File Formats File System.
[  OK  ] Started Network Time Synchronization.
[  OK  ] Started Update UTMP about System Boot/Shutdown.
[  OK  ] Started Enable support for additional executable binary formats.
         Starting Update UTMP about System Runlevel Changes...
[  OK  ] Reached target System Time Synchronized.
[  OK  ] Created slice system-getty.slice.
[  OK  ] Started Update UTMP about System Runlevel Changes.
[  OK  ] Started LSB: AppArmor initialization.
         Starting Raise network interfaces...
[  OK  ] Started Raise network interfaces.
[  OK  ] Reached target Network.
[  OK  ] Reached target Network is Online.

Como estou tentando carregar o mesmo SO no mesmo hardware de antes, acho que meu problema é sobre a nova versão ou configuração do GRUB.

Entrada de menu para o Ubuntu 16.04 na instalação do Ubuntu 16.04 (/boot/grub/grub.cfg): 

menuentry 'Ubuntu' --class ubuntu --class gnu-linux --class gnu --class os $menuentry_id_option 'gnulinux-simple-8276f4fe-1bcd-4d25-8d6d-874f8e69a9b7' {
    recordfail
    load_video
    gfxmode $linux_gfx_mode
    insmod gzio
    if [ x$grub_platform = xxen ]; then insmod xzio; insmod lzopio; fi
    insmod part_msdos
    insmod ext2
    set root='hd1,msdos1'
    if [ x$feature_platform_search_hint = xy ]; then
      search --no-floppy --fs-uuid --set=root --hint-bios=hd1,msdos1 --hint-efi=hd1,msdos1 --hint-baremetal=ahci1,msdos1  8276f4fe-1bcd-4d25-8d6d-874f8e69a9b7
    else
      search --no-floppy --fs-uuid --set=root 8276f4fe-1bcd-4d25-8d6d-874f8e69a9b7
    fi
        linux   /boot/vmlinuz-4.4.0-121-generic root=UUID=8276f4fe-1bcd-4d25-8d6d-874f8e69a9b7 ro  quiet splash $vt_handoff
    initrd  /boot/initrd.img-4.4.0-121-generic
}

Entrada de menu para o Ubuntu 16.04 na instalação do Ubuntu 18.04 (/boot/grub/grub.cfg): 

menuentry 'Ubuntu 16.04.4 LTS (16.04) (auf /dev/sdb1)' --class ubuntu --class gnu-linux --class gnu --class os $menuentry_id_option 'osprober-gnulinux-simple-8276f4fe-1bcd-4d25-8d6d-874f8e69a9b7' {
    insmod part_msdos
    insmod ext2
    set root='hd1,msdos1'
    if [ x$feature_platform_search_hint = xy ]; then
      search --no-floppy --fs-uuid --set=root --hint-bios=hd1,msdos1 --hint-efi=hd1,msdos1 --hint-baremetal=ahci1,msdos1  8276f4fe-1bcd-4d25-8d6d-874f8e69a9b7
    else
      search --no-floppy --fs-uuid --set=root 8276f4fe-1bcd-4d25-8d6d-874f8e69a9b7
    fi
    linux /boot/vmlinuz-4.4.0-121-generic root=UUID=8276f4fe-1bcd-4d25-8d6d-874f8e69a9b7 ro quiet splash $vt_handoff
    initrd /boot/initrd.img-4.4.0-121-generic
}
linux ubuntu boot grub2 MaxGyver
fonte
Se você puder, não use o DisplayPort. IIRC este é um bug de longa data que não foi resolvido. Isso só acontece quando se usa o DisplayPort.
Daniel B
Eu não tenho DisplayPort. Eu só tenho HDMI conectado. Desconectar minha segunda tela não ajuda.
MaxGyver
Hm, é provavelmente uma questão diferente, desculpe. É causada pelo driver gráfico da Intel. No meu caso, isso fez com que o fluxo de dados de exibição parasse de uma forma que fazia até o monitor travar. Você planeja usar aplicativos com uso intensivo de GPU no Linux?
Daniel B
Não. Posso descarregar o driver gráfico da Intel?
MaxGyver
Eu acho que o título é enganoso: eu não vejo uma relação entre o aviso da placa gráfica e a inicialização abortada
A.B

Respostas:

0

Adivinhe: O Ubuntu 18.04 possui drivers de kernel que configuram o hardware de certas maneiras que os drivers do kernel no Ubunutu 16.04 não entendem, ou não levam em conta durante a inicialização. Então, se você inicializar o Ubuntu 16.04 após inicializar o Ubuntu 18.04, o mesmo hardware básico não funcionará como esperado, levando a esses erros.

Diagnose: Inicialização a frio do Ubuntu 16.04 (desligue o computador, corte a energia por alguns segundos) e veja se o problema ainda acontece.

Solução: Sempre faça o boot a frio do Ubuntu 16.04.

dirkt
fonte
Boa dica! Quando eu bota o Ubuntu 16.04, ele fica mais longe do que antes. Mas ainda termina com "Bem-vindo ao modo de emergência". Posso remover manualmente alguns drivers do kernel no GRUB?
MaxGyver
0

O problema era que / dev / sdb2 foi formatado durante a instalação do Ubuntu 18.04. Então, seu UUID mudou e / etc / fstab não estava mais correto.

Eu tive que inicializar o Ubuntu 18.04, para montar / dev / sdb2 e atualizar seu UUID em / etc / fstab (da partição montada).

O UUID pode ser recuperado via sudo blkid .

MaxGyver
fonte