[Touch-packages] [Bug 1832834] Re: Irregular system freezes after updating to 1.1.1b-1ubuntu2.2
With 1.1.1b-1ubuntu2.3 it's a bit different. The system doesn't seem to freeze anymore, but network traffic stops working. Happend about 1-2 hours after a fresh reboot (after applying updates). It still answered to PINGs, but no other network traffic. Neither SSH, nor HTTP/HTTPS or XMPP. After downgrading to 1.1.1b-1ubuntu2.1 it's now running for 3 hours without problems. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to openssl in Ubuntu. https://bugs.launchpad.net/bugs/1832834 Title: Irregular system freezes after updating to 1.1.1b-1ubuntu2.2 Status in openssl package in Ubuntu: New Bug description: Yesterday, I've updated openssl on my Raspberry Pi 3B+ running disco arm64 from 1.1.1b-1ubuntu2.1 to 1.1.1b-1ubuntu2.2 . That was at 10:41 CEST. About 12:36 the system froze. I was able to reset the system at around 17:17. It froze again at around 17:55. Reset it again 19:09, froze again 00:15. Freeze = solid green "busy" light and doesn't answer to anything. Since it's a headless system, I only have the logfiles but they don't show anything obvious. At 01:06, I've downgraded back to 1.1.1b-1ubuntu2.1 and didn't have ANY freeze at all since then (13:13 now here). The system is running ejabberd, SyncThing and a few more programs, that make heavy use of OpenSSL. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/openssl/+bug/1832834/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1832834] [NEW] Irregular system freezes after updating to 1.1.1b-1ubuntu2.2
Public bug reported: Yesterday, I've updated openssl on my Raspberry Pi 3B+ running disco arm64 from 1.1.1b-1ubuntu2.1 to 1.1.1b-1ubuntu2.2 . That was at 10:41 CEST. About 12:36 the system froze. I was able to reset the system at around 17:17. It froze again at around 17:55. Reset it again 19:09, froze again 00:15. Freeze = solid green "busy" light and doesn't answer to anything. Since it's a headless system, I only have the logfiles but they don't show anything obvious. At 01:06, I've downgraded back to 1.1.1b-1ubuntu2.1 and didn't have ANY freeze at all since then (13:13 now here). The system is running ejabberd, SyncThing and a few more programs, that make heavy use of OpenSSL. ** Affects: openssl (Ubuntu) Importance: Undecided Status: New ** Description changed: Yesterday, I've updated openssl on my Raspberry Pi 3B+ running disco arm64 from 1.1.1b-1ubuntu2.1 to 1.1.1b-1ubuntu2.2 . That was at 10:41 CEST. About 12:36 the system froze. I was able to reset the system at around 17:17. It froze again at around 17:55. Reset it again 19:09, froze again 00:15. Freeze = solid green "busy" light and doesn't answer to anything. Since it's a headless system, I only have the logfiles but they don't show anything obvious. At 01:06, I've downgraded back to 1.1.1b-1ubuntu2.1 and didn't have ANY - freeze at all since then. + freeze at all since then (13:13 now here). The system is running ejabberd, SyncThing and a few more programs, that make heavy use of OpenSSL. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to openssl in Ubuntu. https://bugs.launchpad.net/bugs/1832834 Title: Irregular system freezes after updating to 1.1.1b-1ubuntu2.2 Status in openssl package in Ubuntu: New Bug description: Yesterday, I've updated openssl on my Raspberry Pi 3B+ running disco arm64 from 1.1.1b-1ubuntu2.1 to 1.1.1b-1ubuntu2.2 . That was at 10:41 CEST. About 12:36 the system froze. I was able to reset the system at around 17:17. It froze again at around 17:55. Reset it again 19:09, froze again 00:15. Freeze = solid green "busy" light and doesn't answer to anything. Since it's a headless system, I only have the logfiles but they don't show anything obvious. At 01:06, I've downgraded back to 1.1.1b-1ubuntu2.1 and didn't have ANY freeze at all since then (13:13 now here). The system is running ejabberd, SyncThing and a few more programs, that make heavy use of OpenSSL. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/openssl/+bug/1832834/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1826403] Re: Ethernet won't connect when cable is plugged in at boot
I have this, too, on a Raspberry Pi 3 with arm64 Ubuntu. However, I've also upgraded my Raspberry Pi 2 with armhf and there, NetworkManager still autoconnects just fine after boot. The configuration looks identical on both machines. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to network-manager in Ubuntu. https://bugs.launchpad.net/bugs/1826403 Title: Ethernet won't connect when cable is plugged in at boot Status in network-manager package in Ubuntu: Confirmed Bug description: When booting Ubuntu 19.04 with the Ethernet cable plugged in, after boot, network manager won't connect. Unplugging and plugging back in the cable with the system running doesn't work to establish a connection. The workaround is to boot with the cable unplugged, then to plug it in after boot. This problem emerged immediately following an upgrade from 18.10 to 19.04. On the first boot networking was fine, but from the first reboot a networking connection through the Ethernet cable couldn't be established if the cable was plugged in at boot. This issue is also described here: https://askubuntu.com/questions/1135412/updated-to-19-04-and-no- ethernet-now/1135726#1135726 and here: https://ubuntu- mate.community/t/19-04-ethernet-wired-connection-refuses-to-connect- when-plugged-in-before-boot/19333/6 ProblemType: Bug DistroRelease: Ubuntu 19.04 Package: network-manager 1.16.0-0ubuntu2 ProcVersionSignature: Ubuntu 5.0.0-13.14-generic 5.0.6 Uname: Linux 5.0.0-13-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.10-0ubuntu27 Architecture: amd64 CurrentDesktop: GNOME Date: Thu Apr 25 21:50:27 2019 IfupdownConfig: # interfaces(5) file used by ifup(8) and ifdown(8) auto enp4s0f1 auto lo iface lo inet loopback InstallationDate: Installed on 2018-11-23 (153 days ago) InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 (20180725) IpRoute: default via 192.168.11.1 dev enp4s0f1 proto dhcp metric 100 169.254.0.0/16 dev enp4s0f1 scope link metric 1000 192.168.11.0/24 dev enp4s0f1 proto kernel scope link src 192.168.11.13 metric 100 NetworkManager.state: [main] NetworkingEnabled=true WirelessEnabled=false WWANEnabled=true SourcePackage: network-manager UpgradeStatus: Upgraded to disco on 2019-04-25 (0 days ago) mtime.conffile..etc.NetworkManager.NetworkManager.conf: 2019-04-25T20:03:28.380204 nmcli-dev: DEVICETYPE STATEIP4-CONNECTIVITY IP6-CONNECTIVITY DBUS-PATH CONNECTIONCON-UUID CON-PATH enp4s0f1 ethernet connectedfull limited /org/freedesktop/NetworkManager/Devices/2 Automatic connection e906293b-df71-435b-8909-7d88ca006540 /org/freedesktop/NetworkManager/ActiveConnection/1 wlp3s0wifi unavailable limited limited /org/freedesktop/NetworkManager/Devices/3 ---- -- loloopback unmanagedunknown unknown /org/freedesktop/NetworkManager/Devices/1 ---- -- nmcli-nm: RUNNING VERSION STATE STARTUP CONNECTIVITY NETWORKING WIFI-HW WIFI WWAN-HW WWAN running 1.16.0 connected started full enabled enabled disabled enabled enabled To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1826403/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1725458] Re: System unbootable with root fs mounted ro after update to systemd 234-2ubuntu12 (from 234-2ubuntu10) on artful
*** This bug is a duplicate of bug 1726930 *** https://bugs.launchpad.net/bugs/1726930 ** This bug has been marked a duplicate of bug 1726930 System fails to start (boot) on battery due to read-only root file-system -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to systemd in Ubuntu. https://bugs.launchpad.net/bugs/1725458 Title: System unbootable with root fs mounted ro after update to systemd 234-2ubuntu12 (from 234-2ubuntu10) on artful Status in systemd package in Ubuntu: New Bug description: After not touching my notebook since 30th September (where I did the dist-upgrade to artful and installed all available updates), I did all available updates today (20th October) and the system didn't boot after that. The last message I see is "Reached target Bluetooth". Before that, there are several failed services. GDM doesn't come up. After logging in on tty2, I saw that the root partition was mounted read-only. Inspecting the messages of e.g. systemd-resolved shows that it didn't start because of the read-only filesystem. After remounting it fw, I was able to restart the daemons and could also start GDM and login fine. My fstab shows: UUID=a936dbe9-5ab5-4272-aaae-d22030824373 / ext4 errors=remount-ro 0 1 The UUID is correct as "mount / -o remount,rw" works fine. Booting with the previous kernel doesn't change anything. ProblemType: Bug DistroRelease: Ubuntu 17.10 Package: systemd 234-2ubuntu12 ProcVersionSignature: Ubuntu 4.13.0-16.19-generic 4.13.4 Uname: Linux 4.13.0-16-generic x86_64 ApportVersion: 2.20.7-0ubuntu3 Architecture: amd64 Date: Fri Oct 20 21:46:36 2017 EcryptfsInUse: Yes InstallationDate: Installed on 2016-07-26 (451 days ago) InstallationMedia: Ubuntu 16.04.1 LTS "Xenial Xerus" - Release amd64 (20160719) Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 004: ID 04f3:2073 Elan Microelectronics Corp. Bus 001 Device 003: ID 8087:0a2a Intel Corp. Bus 001 Device 002: ID 1bcf:2c7d Sunplus Innovation Technology Inc. Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: HP HP Spectre x360 Convertible ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.13.0-16-generic.efi.signed root=UUID=a936dbe9-5ab5-4272-aaae-d22030824373 ro text SourcePackage: systemd UpgradeStatus: Upgraded to artful on 2017-09-30 (20 days ago) dmi.bios.date: 09/28/2016 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: F.43 dmi.board.asset.tag: Base Board Asset Tag dmi.board.name: 81A1 dmi.board.vendor: HP dmi.board.version: 33.76 dmi.chassis.type: 10 dmi.chassis.vendor: HP dmi.chassis.version: Chassis Version dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrF.43:bd09/28/2016:svnHP:pnHPSpectrex360Convertible:pvr:rvnHP:rn81A1:rvr33.76:cvnHP:ct10:cvrChassisVersion: dmi.product.family: 103C_5335KV G=N L=CON B=HP S=SPT dmi.product.name: HP Spectre x360 Convertible dmi.sys.vendor: HP To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1725458/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1577575] Re: NFS share does not mount on boot using fstab
This bug reappeared (with cifs/smb mounts in fstab) after upgrade to 17.10 "artful" for me. The fix in #5 worked just fine. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to systemd in Ubuntu. https://bugs.launchpad.net/bugs/1577575 Title: NFS share does not mount on boot using fstab Status in systemd package in Ubuntu: Confirmed Bug description: What I expected to happen? I want an NFS share to be mounted on startup using 192.168.178.66:/media/captainplanet/7EF8B26FF8B22575/ /media/captainplanet/banane/ nfs rw 0 0 What happened instead? It does not mount on startup. Systemd waits 91sec instead and finally starts after failing. I can successfully mount the NFS share with sudo mount 192.168.178.66:/media/captainplanet/7EF8B26FF8B22575 /media/captainplanet/banane/ When I try to shutdown Xubuntu it hangs forever. Unmounting the NFS share manually before shutdown fixes the second problem. Do you need more information? ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: systemd 229-4ubuntu4 ProcVersionSignature: Ubuntu 4.4.0-21.37-generic 4.4.6 Uname: Linux 4.4.0-21-generic x86_64 NonfreeKernelModules: nvidia_uvm nvidia_modeset nvidia ApportVersion: 2.20.1-0ubuntu2 Architecture: amd64 CurrentDesktop: XFCE Date: Mon May 2 23:10:50 2016 EcryptfsInUse: Yes InstallationDate: Installed on 2016-04-22 (10 days ago) InstallationMedia: Xubuntu 16.04 LTS "Xenial Xerus" - Release amd64 (20160420.1) MachineType: LENOVO 20DM003XUK ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-21-generic root=UUID=eece9973-0430-4a60-9291-9a994782bf86 ro quiet splash SourcePackage: systemd SystemdDelta: [EXTENDED] /lib/systemd/system/systemd-timesyncd.service → /lib/systemd/system/systemd-timesyncd.service.d/disable-with-time-daemon.conf [EXTENDED] /lib/systemd/system/rc-local.service → /lib/systemd/system/rc-local.service.d/debian.conf 2 overridden configuration files found. UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 08/26/2015 dmi.bios.vendor: LENOVO dmi.bios.version: JFET44WW(1.21) dmi.board.asset.tag: Not Available dmi.board.name: 20DM003XUK dmi.board.vendor: LENOVO dmi.board.version: SDK0E50512 STD dmi.chassis.asset.tag: No Asset Information dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: None dmi.modalias: dmi:bvnLENOVO:bvrJFET44WW(1.21):bd08/26/2015:svnLENOVO:pn20DM003XUK:pvrThinkPadS3Yoga14:rvnLENOVO:rn20DM003XUK:rvrSDK0E50512STD:cvnLENOVO:ct10:cvrNone: dmi.product.name: 20DM003XUK dmi.product.version: ThinkPad S3 Yoga 14 dmi.sys.vendor: LENOVO To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1577575/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1726930] Re: System fails to start (boot) on battery due to read-only root file-system
Confirmed on a hp Spectre x360 13-4104ng. On battery power, the system DOESN'T boot up. With the charger connected, the system boots up just fine. See https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1725458 for my apport logs. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to systemd in Ubuntu. https://bugs.launchpad.net/bugs/1726930 Title: System fails to start (boot) on battery due to read-only root file- system Status in laptop-mode-tools package in Ubuntu: Confirmed Status in systemd package in Ubuntu: Confirmed Status in systemd package in Debian: Unknown Bug description: This report is to capture the extended diagnostic efforts done on IRC #ubuntu for user maszlo, who has a Lenovo T450 with SSD that was upgraded from 17.04 to 17.10 and since fails to complete start-up of services when powered on battery. We'd previously applied the "acpi=os=! 'acpi_osi=Windows 2015'" workaround in case this was an ACPI DSDT issue. This appears to be due to a read-only root file-system. What is not clear is how the rootfs goes read-only. The file-system (sda6, ext4) is fsck-ed successfully in the initrd according to the /run/initramfs/fsck.log. From the start-up logs (with "systemd.log_level=debug") we see the ext4 driver report a remount operation not once but five times. $ grep 'EXT4-fs.*sda6' systemd-debug.log Oct 23 18:10:44 T450s kernel: EXT4-fs (sda6): mounted filesystem with ordered data mode. Opts: (null) Oct 23 18:10:44 T450s kernel: EXT4-fs (sda6): re-mounted. Opts: errors=remount-ro Oct 23 18:10:46 T450s kernel: EXT4-fs (sda6): re-mounted. Opts: errors=remount-ro,data=ordered,commit=600 Oct 23 18:10:47 T450s kernel: EXT4-fs (sda6): re-mounted. Opts: errors=remount-ro,data=ordered,commit=600 Oct 23 18:10:48 T450s kernel: EXT4-fs (sda6): re-mounted. Opts: errors=remount-ro,data=ordered,commit=600 Oct 23 18:10:48 T450s kernel: EXT4-fs (sda6): re-mounted. Opts: errors=remount-ro,data=ordered,commit=600 Oct 23 18:10:49 T450s kernel: EXT4-fs (sda6): re-mounted. Opts: errors=remount-ro,data=ordered,commit=600 Those last five appear to be carrying options generated by laptop- mode-tools. User has disabled laptop-mode.service and laptop-mode.timer, and lmt- poll.service, but the issue remains. We see several reports of "read-only file-system": $ grep 'Read-only' systemd-debug.log Oct 23 18:10:46 T450s grub-common[1792]: grub-editenv: error: cannot open `/boot/grub/grubenv': Read-only file system. Oct 23 18:10:46 T450s systemd[1]: colord.service: Failed to run 'start' task: Read-only file system Oct 23 18:10:46 T450s gpu-manager[1797]: Warning: writing to /var/log/gpu-manager.log failed (Read-only file system) Oct 23 18:10:46 T450s systemd[1]: systemd-resolved.service: Failed to run 'start' task: Read-only file system Oct 23 18:10:46 T450s systemd[1]: systemd-resolved.service: Failed to run 'start' task: Read-only file system Oct 23 18:10:46 T450s gdm3[1932]: Failed to create LogDir /var/log/gdm3: Read-only file system ... Oct 23 18:11:26 T450s cupsd[1461]: Unable to change ownership of "/var/log/cups" - Read-only file system Oct 23 18:11:26 T450s cupsd[1461]: Unable to open log file "/var/log/cups/access_log" - Read-only file system Oct 23 18:12:52 T450s login[9248]: pam_lastlog(login:session): unable to open /var/log/lastlog: Read-only file system We also see several problems with systemd's connection to Dbus: $ grep 'Transport endpoint' systemd-debug.log Oct 23 18:10:46 T450s systemd[1]: Failed to send job change signal for 773: Transport endpoint is not connected Oct 23 18:10:46 T450s systemd[1]: systemd-logind.service: Failed to send unit change signal for systemd-logind.service: Transport endpoint is not connected Oct 23 18:10:46 T450s systemd[1]: Failed to send job remove signal for 156: Transport endpoint is not connected Oct 23 18:10:46 T450s systemd[1]: lmt-poll.service: Failed to send unit change signal for lmt-poll.service: Transport endpoint is not connected Oct 23 18:10:46 T450s systemd[1]: Failed to send job remove signal for 182: Transport endpoint is not connected Oct 23 18:10:46 T450s systemd[1]: Failed to send job remove signal for 95: Transport endpoint is not connected Oct 23 18:10:46 T450s systemd[1]: polkit.service: Failed to send unit change signal for polkit.service: Transport endpoint is not connected Oct 23 18:10:46 T450s systemd[1]: cups-browsed.service: Failed to send unit change signal for cups-browsed.service: Transport endpoint is not connected Oct 23 18:10:46 T450s systemd[1]: Failed to send job change signal for 773: Transport endpoint is not connected Oct 23 18:10:46 T450s systemd[1]: Failed to send job remove signal for 161: Transport endpoint is not connected Oct 23 18:10:46 T450s systemd[1]: gdomap.service: Failed to send unit change signal for gdomap.
[Touch-packages] [Bug 1725458] Re: System unbootable with root fs mounted ro after update to systemd 234-2ubuntu12 (from 234-2ubuntu10) on artful
Yes, this seems to be a duplicate of your bug. On battery power, the system DOESN'T boot up. With the charger connected, the system boots up just fine. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to systemd in Ubuntu. https://bugs.launchpad.net/bugs/1725458 Title: System unbootable with root fs mounted ro after update to systemd 234-2ubuntu12 (from 234-2ubuntu10) on artful Status in systemd package in Ubuntu: New Bug description: After not touching my notebook since 30th September (where I did the dist-upgrade to artful and installed all available updates), I did all available updates today (20th October) and the system didn't boot after that. The last message I see is "Reached target Bluetooth". Before that, there are several failed services. GDM doesn't come up. After logging in on tty2, I saw that the root partition was mounted read-only. Inspecting the messages of e.g. systemd-resolved shows that it didn't start because of the read-only filesystem. After remounting it fw, I was able to restart the daemons and could also start GDM and login fine. My fstab shows: UUID=a936dbe9-5ab5-4272-aaae-d22030824373 / ext4 errors=remount-ro 0 1 The UUID is correct as "mount / -o remount,rw" works fine. Booting with the previous kernel doesn't change anything. ProblemType: Bug DistroRelease: Ubuntu 17.10 Package: systemd 234-2ubuntu12 ProcVersionSignature: Ubuntu 4.13.0-16.19-generic 4.13.4 Uname: Linux 4.13.0-16-generic x86_64 ApportVersion: 2.20.7-0ubuntu3 Architecture: amd64 Date: Fri Oct 20 21:46:36 2017 EcryptfsInUse: Yes InstallationDate: Installed on 2016-07-26 (451 days ago) InstallationMedia: Ubuntu 16.04.1 LTS "Xenial Xerus" - Release amd64 (20160719) Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 004: ID 04f3:2073 Elan Microelectronics Corp. Bus 001 Device 003: ID 8087:0a2a Intel Corp. Bus 001 Device 002: ID 1bcf:2c7d Sunplus Innovation Technology Inc. Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: HP HP Spectre x360 Convertible ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.13.0-16-generic.efi.signed root=UUID=a936dbe9-5ab5-4272-aaae-d22030824373 ro text SourcePackage: systemd UpgradeStatus: Upgraded to artful on 2017-09-30 (20 days ago) dmi.bios.date: 09/28/2016 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: F.43 dmi.board.asset.tag: Base Board Asset Tag dmi.board.name: 81A1 dmi.board.vendor: HP dmi.board.version: 33.76 dmi.chassis.type: 10 dmi.chassis.vendor: HP dmi.chassis.version: Chassis Version dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrF.43:bd09/28/2016:svnHP:pnHPSpectrex360Convertible:pvr:rvnHP:rn81A1:rvr33.76:cvnHP:ct10:cvrChassisVersion: dmi.product.family: 103C_5335KV G=N L=CON B=HP S=SPT dmi.product.name: HP Spectre x360 Convertible dmi.sys.vendor: HP To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1725458/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1725458] Re: System unbootable with root fs mounted ro after update to systemd 234-2ubuntu12 (from 234-2ubuntu10) on artful
The change in the fstab seems to have worked only once. Today, it doesn't boot again (with the changed fstab). I've tried switching from UEFI to Legacy mode without luck, too. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to systemd in Ubuntu. https://bugs.launchpad.net/bugs/1725458 Title: System unbootable with root fs mounted ro after update to systemd 234-2ubuntu12 (from 234-2ubuntu10) on artful Status in systemd package in Ubuntu: New Bug description: After not touching my notebook since 30th September (where I did the dist-upgrade to artful and installed all available updates), I did all available updates today (20th October) and the system didn't boot after that. The last message I see is "Reached target Bluetooth". Before that, there are several failed services. GDM doesn't come up. After logging in on tty2, I saw that the root partition was mounted read-only. Inspecting the messages of e.g. systemd-resolved shows that it didn't start because of the read-only filesystem. After remounting it fw, I was able to restart the daemons and could also start GDM and login fine. My fstab shows: UUID=a936dbe9-5ab5-4272-aaae-d22030824373 / ext4 errors=remount-ro 0 1 The UUID is correct as "mount / -o remount,rw" works fine. Booting with the previous kernel doesn't change anything. ProblemType: Bug DistroRelease: Ubuntu 17.10 Package: systemd 234-2ubuntu12 ProcVersionSignature: Ubuntu 4.13.0-16.19-generic 4.13.4 Uname: Linux 4.13.0-16-generic x86_64 ApportVersion: 2.20.7-0ubuntu3 Architecture: amd64 Date: Fri Oct 20 21:46:36 2017 EcryptfsInUse: Yes InstallationDate: Installed on 2016-07-26 (451 days ago) InstallationMedia: Ubuntu 16.04.1 LTS "Xenial Xerus" - Release amd64 (20160719) Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 004: ID 04f3:2073 Elan Microelectronics Corp. Bus 001 Device 003: ID 8087:0a2a Intel Corp. Bus 001 Device 002: ID 1bcf:2c7d Sunplus Innovation Technology Inc. Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: HP HP Spectre x360 Convertible ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.13.0-16-generic.efi.signed root=UUID=a936dbe9-5ab5-4272-aaae-d22030824373 ro text SourcePackage: systemd UpgradeStatus: Upgraded to artful on 2017-09-30 (20 days ago) dmi.bios.date: 09/28/2016 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: F.43 dmi.board.asset.tag: Base Board Asset Tag dmi.board.name: 81A1 dmi.board.vendor: HP dmi.board.version: 33.76 dmi.chassis.type: 10 dmi.chassis.vendor: HP dmi.chassis.version: Chassis Version dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrF.43:bd09/28/2016:svnHP:pnHPSpectrex360Convertible:pvr:rvnHP:rn81A1:rvr33.76:cvnHP:ct10:cvrChassisVersion: dmi.product.family: 103C_5335KV G=N L=CON B=HP S=SPT dmi.product.name: HP Spectre x360 Convertible dmi.sys.vendor: HP To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1725458/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1725458] Re: System unbootable with root fs mounted ro after update to systemd 234-2ubuntu12 (from 234-2ubuntu10) on artful
I changed my fstab from UUID=a936dbe9-5ab5-4272-aaae-d22030824373 / ext4 errors=remount-ro 0 1 to UUID=a936dbe9-5ab5-4272-aaae-d22030824373 / ext4 rw,errors=remount-ro 0 1 and it now boots fine again. I don't know why that is necessary now and why the update didn't notify me or made the change automatically. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to systemd in Ubuntu. https://bugs.launchpad.net/bugs/1725458 Title: System unbootable with root fs mounted ro after update to systemd 234-2ubuntu12 (from 234-2ubuntu10) on artful Status in systemd package in Ubuntu: New Bug description: After not touching my notebook since 30th September (where I did the dist-upgrade to artful and installed all available updates), I did all available updates today (20th October) and the system didn't boot after that. The last message I see is "Reached target Bluetooth". Before that, there are several failed services. GDM doesn't come up. After logging in on tty2, I saw that the root partition was mounted read-only. Inspecting the messages of e.g. systemd-resolved shows that it didn't start because of the read-only filesystem. After remounting it fw, I was able to restart the daemons and could also start GDM and login fine. My fstab shows: UUID=a936dbe9-5ab5-4272-aaae-d22030824373 / ext4 errors=remount-ro 0 1 The UUID is correct as "mount / -o remount,rw" works fine. Booting with the previous kernel doesn't change anything. ProblemType: Bug DistroRelease: Ubuntu 17.10 Package: systemd 234-2ubuntu12 ProcVersionSignature: Ubuntu 4.13.0-16.19-generic 4.13.4 Uname: Linux 4.13.0-16-generic x86_64 ApportVersion: 2.20.7-0ubuntu3 Architecture: amd64 Date: Fri Oct 20 21:46:36 2017 EcryptfsInUse: Yes InstallationDate: Installed on 2016-07-26 (451 days ago) InstallationMedia: Ubuntu 16.04.1 LTS "Xenial Xerus" - Release amd64 (20160719) Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 004: ID 04f3:2073 Elan Microelectronics Corp. Bus 001 Device 003: ID 8087:0a2a Intel Corp. Bus 001 Device 002: ID 1bcf:2c7d Sunplus Innovation Technology Inc. Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: HP HP Spectre x360 Convertible ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.13.0-16-generic.efi.signed root=UUID=a936dbe9-5ab5-4272-aaae-d22030824373 ro text SourcePackage: systemd UpgradeStatus: Upgraded to artful on 2017-09-30 (20 days ago) dmi.bios.date: 09/28/2016 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: F.43 dmi.board.asset.tag: Base Board Asset Tag dmi.board.name: 81A1 dmi.board.vendor: HP dmi.board.version: 33.76 dmi.chassis.type: 10 dmi.chassis.vendor: HP dmi.chassis.version: Chassis Version dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrF.43:bd09/28/2016:svnHP:pnHPSpectrex360Convertible:pvr:rvnHP:rn81A1:rvr33.76:cvnHP:ct10:cvrChassisVersion: dmi.product.family: 103C_5335KV G=N L=CON B=HP S=SPT dmi.product.name: HP Spectre x360 Convertible dmi.sys.vendor: HP To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1725458/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1725458] [NEW] System unbootable with root fs mounted ro after update to systemd 234-2ubuntu12 (from 234-2ubuntu10) on artful
Public bug reported: After not touching my notebook since 30th September (where I did the dist-upgrade to artful and installed all available updates), I did all available updates today (20th October) and the system didn't boot after that. The last message I see is "Reached target Bluetooth". Before that, there are several failed services. GDM doesn't come up. After logging in on tty2, I saw that the root partition was mounted read-only. Inspecting the messages of e.g. systemd-resolved shows that it didn't start because of the read-only filesystem. After remounting it fw, I was able to restart the daemons and could also start GDM and login fine. My fstab shows: UUID=a936dbe9-5ab5-4272-aaae-d22030824373 / ext4errors =remount-ro 0 1 The UUID is correct as "mount / -o remount,rw" works fine. Booting with the previous kernel doesn't change anything. ProblemType: Bug DistroRelease: Ubuntu 17.10 Package: systemd 234-2ubuntu12 ProcVersionSignature: Ubuntu 4.13.0-16.19-generic 4.13.4 Uname: Linux 4.13.0-16-generic x86_64 ApportVersion: 2.20.7-0ubuntu3 Architecture: amd64 Date: Fri Oct 20 21:46:36 2017 EcryptfsInUse: Yes InstallationDate: Installed on 2016-07-26 (451 days ago) InstallationMedia: Ubuntu 16.04.1 LTS "Xenial Xerus" - Release amd64 (20160719) Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 004: ID 04f3:2073 Elan Microelectronics Corp. Bus 001 Device 003: ID 8087:0a2a Intel Corp. Bus 001 Device 002: ID 1bcf:2c7d Sunplus Innovation Technology Inc. Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: HP HP Spectre x360 Convertible ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.13.0-16-generic.efi.signed root=UUID=a936dbe9-5ab5-4272-aaae-d22030824373 ro text SourcePackage: systemd UpgradeStatus: Upgraded to artful on 2017-09-30 (20 days ago) dmi.bios.date: 09/28/2016 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: F.43 dmi.board.asset.tag: Base Board Asset Tag dmi.board.name: 81A1 dmi.board.vendor: HP dmi.board.version: 33.76 dmi.chassis.type: 10 dmi.chassis.vendor: HP dmi.chassis.version: Chassis Version dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrF.43:bd09/28/2016:svnHP:pnHPSpectrex360Convertible:pvr:rvnHP:rn81A1:rvr33.76:cvnHP:ct10:cvrChassisVersion: dmi.product.family: 103C_5335KV G=N L=CON B=HP S=SPT dmi.product.name: HP Spectre x360 Convertible dmi.sys.vendor: HP ** Affects: systemd (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug artful -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to systemd in Ubuntu. https://bugs.launchpad.net/bugs/1725458 Title: System unbootable with root fs mounted ro after update to systemd 234-2ubuntu12 (from 234-2ubuntu10) on artful Status in systemd package in Ubuntu: New Bug description: After not touching my notebook since 30th September (where I did the dist-upgrade to artful and installed all available updates), I did all available updates today (20th October) and the system didn't boot after that. The last message I see is "Reached target Bluetooth". Before that, there are several failed services. GDM doesn't come up. After logging in on tty2, I saw that the root partition was mounted read-only. Inspecting the messages of e.g. systemd-resolved shows that it didn't start because of the read-only filesystem. After remounting it fw, I was able to restart the daemons and could also start GDM and login fine. My fstab shows: UUID=a936dbe9-5ab5-4272-aaae-d22030824373 / ext4 errors=remount-ro 0 1 The UUID is correct as "mount / -o remount,rw" works fine. Booting with the previous kernel doesn't change anything. ProblemType: Bug DistroRelease: Ubuntu 17.10 Package: systemd 234-2ubuntu12 ProcVersionSignature: Ubuntu 4.13.0-16.19-generic 4.13.4 Uname: Linux 4.13.0-16-generic x86_64 ApportVersion: 2.20.7-0ubuntu3 Architecture: amd64 Date: Fri Oct 20 21:46:36 2017 EcryptfsInUse: Yes InstallationDate: Installed on 2016-07-26 (451 days ago) InstallationMedia: Ubuntu 16.04.1 LTS "Xenial Xerus" - Release amd64 (20160719) Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 004: ID 04f3:2073 Elan Microelectronics Corp. Bus 001 Device 003: ID 8087:0a2a Intel Corp. Bus 001 Device 002: ID 1bcf:2c7d Sunplus Innovation Technology Inc. Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: HP HP Spectre x360 Convertible ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.13.0-16-generic.efi.signed root=UUID=a936dbe9-5ab5-4272-aaae-d22030824373 ro text SourcePackage: systemd UpgradeStatus: Upgraded to artful on 2017-09-30 (20 days ago) dmi.bios.date: 09/28/2016 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: F.43 dmi.board.asset.tag: Base Board Asset Tag dmi.board.name: 81A1 dmi.boar