Booten in Ubuntu 16.04 nach der Installation von Ubuntu 18.04 (auf separater Partition) nicht möglich

2611
MaxGyver

Ich habe ein Multiboot-System mit zwei Festplatten:

  • Windows und einige alte Ubuntu-Versionen unter / dev / sda
  • Ubuntu 16.04 auf / dev / sdb1

Dann habe ich Ubuntu 18.04 auf der leeren Partition / dev / sdb2 installiert. Ich konnte mich nicht erinnern, wo sich der alte Bootloader befand, also wählte ich / dev / sdb für den neuen Bootloader.

Jetzt kann ich Ubuntu 18.04 ohne Probleme booten, aber wenn ich Ubuntu 16.04 boote, bekomme ich Folgendes:

[ 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, ... 

Ich habe bereits versucht, mich im Rettungsmodus anzumelden und Sudo fsck -f / dev / sdb1 auszuführen, jedoch ohne Erfolg.

Wie kann ich das reparieren?

BEARBEITEN:

Mein 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. 

Da ich versuche, dasselbe Betriebssystem auf derselben Hardware wie zuvor zu laden, liegt das Problem bei der neuen GRUB-Version oder -Konfiguration.

Menüeintrag für Ubuntu 16.04 in der Installation von 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 } 

Menüeintrag für Ubuntu 16.04 in der Installation von 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 } 
0
Wenn möglich, verwenden Sie DisplayPort nicht. IIRC Dies ist ein seit langem bestehender Fehler, der nicht behoben wurde. Dies geschieht nur bei der Verwendung von DisplayPort. Daniel B vor 5 Jahren 0
Ich habe keinen DisplayPort. Ich habe nur HDMI angeschlossen. Das Entfernen des zweiten Bildschirms hilft nicht. MaxGyver vor 5 Jahren 0
Hm, dann ist es wahrscheinlich ein anderes Thema, sorry. Ursache ist der Intel-Grafiktreiber. In meinem Fall wurde der Anzeigedatenstrom so eingestellt, dass sogar die Anzeige abstürzte. Planen Sie, GPU-intensive Anwendungen unter Linux zu verwenden? Daniel B vor 5 Jahren 0
Nein. Kann ich den Intel-Grafiktreiber entfernen? MaxGyver vor 5 Jahren 0
Ich denke, der Titel ist irreführend: Ich sehe keinen Zusammenhang zwischen der Grafikkartenwarnung und dem abgebrochenen Startvorgang A.B vor 5 Jahren 0
Glaubst du, es geht um den USB-Fehler? MaxGyver vor 5 Jahren 0
Okay, ich habe den Titel geändert. MaxGyver vor 5 Jahren 0

2 Antworten auf die Frage

0
dirkt

Vermutung: Ubuntu 18.04 hat Kerneltreiber, die die Hardware auf bestimmte Arten einrichten, die die Kerneltreiber in Ubunutu 16.04 nicht verstehen oder bei der Initialisierung nicht berücksichtigen. Wenn Sie Ubuntu 16.04 nach dem Booten von Ubuntu 18.04 neu starten, verhält sich dieselbe Hardware nicht wie erwartet, was zu Fehlern führt.

Diagnose: Kaltstart Ubuntu 16.04 (Computer ausschalten, Strom für einige Sekunden ausschalten) und prüfen, ob das Problem weiterhin auftritt.

Umgehung: Ubuntu 16.04 immer kalt starten.

Guter Hinweis! Wenn ich Ubuntu 16.04 kalte boote, wird es weiter als zuvor. Es endet aber immer noch mit "Willkommen im Notfallmodus". Kann ich einige Kerneltreiber in GRUB manuell entfernen? MaxGyver vor 5 Jahren 0
0
MaxGyver

Das Problem war, dass / dev / sdb2 während der Installation von Ubuntu 18.04 formatiert wurde. Die UUID hat sich also geändert und / etc / fstab war nicht mehr korrekt.

Ich musste Ubuntu 18.04 booten, um / dev / sdb2 zu mounten und seine UUID in / etc / fstab (der gemounteten Partition) zu aktualisieren .

Die UUID kann über sudo blkid abgerufen werden .