[Kernel-packages] [Bug 1807682] Re: system does not start

2020-09-22 Thread sunbeam
Thanks g.bruno ..it has solved my headache

-- 
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1807682

Title:
  system does not start

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  The System does not start. When starting in recovery mode the error

  "failed to start Create Static Device Nodes in /dev.
  See 'systemctl status systemd-tmpfiles-setupd-dev.service' for details"
  is shown.

  When typing

  systemctl status systemd-tmpfiles-setupd-dev.service

  into the console, the answer is:

  Unit systemd-tmpfiles-setupd-dev.service could not be found.

  The System does only start in recovery mode and I would expect an
  normal start.

  Thanks for help in advance.

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: linux-image-4.15.0-42-generic 4.15.0-42.45
  ProcVersionSignature: Ubuntu 4.15.0-42.45-generic 4.15.18
  Uname: Linux 4.15.0-42-generic x86_64
  ApportVersion: 2.20.9-0ubuntu7.5
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  administrator   2025 F pulseaudio
   /dev/snd/controlC1:  administrator   2025 F pulseaudio
  CurrentDesktop: ubuntu:GNOME
  Date: Mon Dec 10 10:42:07 2018
  HibernationDevice: RESUME=UUID=6ffe8604-b66f-421e-afbd-50bcdeb4ff9e
  InstallationDate: Installed on 2012-05-11 (2404 days ago)
  InstallationMedia: Ubuntu 12.04 LTS "Precise Pangolin" - Release amd64 
(20120425)
  IwConfig:
   eth0  no wireless extensions.
   
   lono wireless extensions.
  ProcFB:
   
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-42-generic 
root=UUID=0c7307f0-bcbe-4a1e-8d04-3004f27151bc ro recovery nomodeset
  RelatedPackageVersions:
   linux-restricted-modules-4.15.0-42-generic N/A
   linux-backports-modules-4.15.0-42-generic  N/A
   linux-firmware 1.173.2
  RfKill:
   
  SourcePackage: linux
  UpgradeStatus: Upgraded to bionic on 2018-12-10 (0 days ago)
  dmi.bios.date: 12/27/2011
  dmi.bios.vendor: Intel Corp.
  dmi.bios.version: BLH6710H.86A.0146.2011.1227.1631
  dmi.board.asset.tag: To be filled by O.E.M.
  dmi.board.name: DH67BL
  dmi.board.vendor: Intel Corporation
  dmi.board.version: AAG10189-209
  dmi.chassis.type: 3
  dmi.modalias: 
dmi:bvnIntelCorp.:bvrBLH6710H.86A.0146.2011.1227.1631:bd12/27/2011:svnbluechipComputerAG:pn:pvr:rvnIntelCorporation:rnDH67BL:rvrAAG10189-209:cvn:ct3:cvr:
  dmi.sys.vendor: bluechip Computer AG

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1807682/+subscriptions

-- 
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help   : https://help.launchpad.net/ListHelp


[Kernel-packages] [Bug 1807682] Re: system does not start

2020-02-14 Thread Fabricio
Thats it! Thank you!!!

-- 
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1807682

Title:
  system does not start

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  The System does not start. When starting in recovery mode the error

  "failed to start Create Static Device Nodes in /dev.
  See 'systemctl status systemd-tmpfiles-setupd-dev.service' for details"
  is shown.

  When typing

  systemctl status systemd-tmpfiles-setupd-dev.service

  into the console, the answer is:

  Unit systemd-tmpfiles-setupd-dev.service could not be found.

  The System does only start in recovery mode and I would expect an
  normal start.

  Thanks for help in advance.

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: linux-image-4.15.0-42-generic 4.15.0-42.45
  ProcVersionSignature: Ubuntu 4.15.0-42.45-generic 4.15.18
  Uname: Linux 4.15.0-42-generic x86_64
  ApportVersion: 2.20.9-0ubuntu7.5
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  administrator   2025 F pulseaudio
   /dev/snd/controlC1:  administrator   2025 F pulseaudio
  CurrentDesktop: ubuntu:GNOME
  Date: Mon Dec 10 10:42:07 2018
  HibernationDevice: RESUME=UUID=6ffe8604-b66f-421e-afbd-50bcdeb4ff9e
  InstallationDate: Installed on 2012-05-11 (2404 days ago)
  InstallationMedia: Ubuntu 12.04 LTS "Precise Pangolin" - Release amd64 
(20120425)
  IwConfig:
   eth0  no wireless extensions.
   
   lono wireless extensions.
  ProcFB:
   
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-42-generic 
root=UUID=0c7307f0-bcbe-4a1e-8d04-3004f27151bc ro recovery nomodeset
  RelatedPackageVersions:
   linux-restricted-modules-4.15.0-42-generic N/A
   linux-backports-modules-4.15.0-42-generic  N/A
   linux-firmware 1.173.2
  RfKill:
   
  SourcePackage: linux
  UpgradeStatus: Upgraded to bionic on 2018-12-10 (0 days ago)
  dmi.bios.date: 12/27/2011
  dmi.bios.vendor: Intel Corp.
  dmi.bios.version: BLH6710H.86A.0146.2011.1227.1631
  dmi.board.asset.tag: To be filled by O.E.M.
  dmi.board.name: DH67BL
  dmi.board.vendor: Intel Corporation
  dmi.board.version: AAG10189-209
  dmi.chassis.type: 3
  dmi.modalias: 
dmi:bvnIntelCorp.:bvrBLH6710H.86A.0146.2011.1227.1631:bd12/27/2011:svnbluechipComputerAG:pn:pvr:rvnIntelCorporation:rnDH67BL:rvrAAG10189-209:cvn:ct3:cvr:
  dmi.sys.vendor: bluechip Computer AG

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1807682/+subscriptions

-- 
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help   : https://help.launchpad.net/ListHelp


[Kernel-packages] [Bug 1807682] Re: system does not start

2019-01-11 Thread g.bruno
Found a possible solution on 
https://ubuntuforums.org/showthread.php?t=2406453
---
Well. Problem is the root folder has user as an owner.
Code:

root@myserver:~# stat -c "%U %G" /
user user

Solution is:
Code:

root@myserver:~# chown root:root /
root@myserver:~# stat -c "%U %G" /
root root

root@myserver:~# systemctl start systemd-tmpfiles-setup
root@myserver:~#
-
For me the result of 'stat -c "%U %G" /' is
nobody nogroup
I changed it to root:root and hope that it will work.
Greetings gbruno

-- 
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1807682

Title:
  system does not start

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  The System does not start. When starting in recovery mode the error

  "failed to start Create Static Device Nodes in /dev.
  See 'systemctl status systemd-tmpfiles-setupd-dev.service' for details"
  is shown.

  When typing

  systemctl status systemd-tmpfiles-setupd-dev.service

  into the console, the answer is:

  Unit systemd-tmpfiles-setupd-dev.service could not be found.

  The System does only start in recovery mode and I would expect an
  normal start.

  Thanks for help in advance.

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: linux-image-4.15.0-42-generic 4.15.0-42.45
  ProcVersionSignature: Ubuntu 4.15.0-42.45-generic 4.15.18
  Uname: Linux 4.15.0-42-generic x86_64
  ApportVersion: 2.20.9-0ubuntu7.5
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  administrator   2025 F pulseaudio
   /dev/snd/controlC1:  administrator   2025 F pulseaudio
  CurrentDesktop: ubuntu:GNOME
  Date: Mon Dec 10 10:42:07 2018
  HibernationDevice: RESUME=UUID=6ffe8604-b66f-421e-afbd-50bcdeb4ff9e
  InstallationDate: Installed on 2012-05-11 (2404 days ago)
  InstallationMedia: Ubuntu 12.04 LTS "Precise Pangolin" - Release amd64 
(20120425)
  IwConfig:
   eth0  no wireless extensions.
   
   lono wireless extensions.
  ProcFB:
   
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-42-generic 
root=UUID=0c7307f0-bcbe-4a1e-8d04-3004f27151bc ro recovery nomodeset
  RelatedPackageVersions:
   linux-restricted-modules-4.15.0-42-generic N/A
   linux-backports-modules-4.15.0-42-generic  N/A
   linux-firmware 1.173.2
  RfKill:
   
  SourcePackage: linux
  UpgradeStatus: Upgraded to bionic on 2018-12-10 (0 days ago)
  dmi.bios.date: 12/27/2011
  dmi.bios.vendor: Intel Corp.
  dmi.bios.version: BLH6710H.86A.0146.2011.1227.1631
  dmi.board.asset.tag: To be filled by O.E.M.
  dmi.board.name: DH67BL
  dmi.board.vendor: Intel Corporation
  dmi.board.version: AAG10189-209
  dmi.chassis.type: 3
  dmi.modalias: 
dmi:bvnIntelCorp.:bvrBLH6710H.86A.0146.2011.1227.1631:bd12/27/2011:svnbluechipComputerAG:pn:pvr:rvnIntelCorporation:rnDH67BL:rvrAAG10189-209:cvn:ct3:cvr:
  dmi.sys.vendor: bluechip Computer AG

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1807682/+subscriptions

-- 
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help   : https://help.launchpad.net/ListHelp


[Kernel-packages] [Bug 1807682] Re: system does not start

2019-01-11 Thread g.bruno
I got the same issue. "systemctl status systemd-tmpfiles-setupd-dev.service" 
yields the same response. But my system (Ubunutu 18.04.1) is starting properly 
and there are no problems when using it. 
In /var/log/syslog these lines precede the error:
Jan 11 14:37:48 Intel-i5-Tower systemd[1]: Started Apply Kernel Variables.
Jan 11 14:37:48 Intel-i5-Tower systemd-tmpfiles[311]: Unsafe symlinks 
encountered in /dev/cuse, refusing.
Jan 11 14:37:48 Intel-i5-Tower systemd-tmpfiles[311]: Unsafe symlinks 
encountered in /dev/autofs, refusing.
Jan 11 14:37:48 Intel-i5-Tower systemd-tmpfiles[311]: Unsafe symlinks 
encountered in /dev/btrfs-control, refusing.
Jan 11 14:37:48 Intel-i5-Tower systemd-tmpfiles[311]: Unsafe symlinks 
encountered in /dev/userio, refusing.
Jan 11 14:37:48 Intel-i5-Tower systemd-tmpfiles[311]: Unsafe symlinks 
encountered in /dev/vfio, refusing.
Jan 11 14:37:48 Intel-i5-Tower systemd-tmpfiles[311]: Unsafe symlinks 
encountered in /dev/vfio/vfio, refusing.
Jan 11 14:37:48 Intel-i5-Tower systemd-tmpfiles[311]: Unsafe symlinks 
encountered in /dev/vhci, refusing.
Jan 11 14:37:48 Intel-i5-Tower systemd-tmpfiles[311]: Unsafe symlinks 
encountered in /dev/uhid, refusing.
Jan 11 14:37:48 Intel-i5-Tower systemd-tmpfiles[311]: Unsafe symlinks 
encountered in /dev/vhost-net, refusing.
Jan 11 14:37:48 Intel-i5-Tower systemd-tmpfiles[311]: Unsafe symlinks 
encountered in /dev/vhost-vsock, refusing.
Jan 11 14:37:48 Intel-i5-Tower systemd-tmpfiles[311]: Unsafe symlinks 
encountered in /dev/snd, refusing.
Jan 11 14:37:48 Intel-i5-Tower systemd-tmpfiles[311]: Unsafe symlinks 
encountered in /dev/snd, refusing.
Jan 11 14:37:48 Intel-i5-Tower systemd-tmpfiles[311]: Unsafe symlinks 
encountered in /dev/snd/timer, refusing.
Jan 11 14:37:48 Intel-i5-Tower systemd-tmpfiles[311]: Unsafe symlinks 
encountered in /dev/snd/seq, refusing.
Jan 11 14:37:48 Intel-i5-Tower systemd[1]: systemd-tmpfiles-setup-dev.service: 
Main process exited, code=exited, status=1/FAILURE
Jan 11 14:37:48 Intel-i5-Tower systemd[1]: systemd-tmpfiles-setup-dev.service: 
Failed with result 'exit-code'.
Jan 11 14:37:48 Intel-i5-Tower systemd-fsck[584]: Ubuntu/home: sauber, 
316299/66273280 Dateien, 223989723/265086556 Blöcke
Jan 11 14:37:48 Intel-i5-Tower systemd[1]: Failed to start Create Static Device 
Nodes in /dev.
Jan 11 14:37:48 Intel-i5-Tower systemd[1]: Reached target Local File Systems 
(Pre).

Perhaps the error is due to the unsave symlinks?

-- 
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1807682

Title:
  system does not start

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  The System does not start. When starting in recovery mode the error

  "failed to start Create Static Device Nodes in /dev.
  See 'systemctl status systemd-tmpfiles-setupd-dev.service' for details"
  is shown.

  When typing

  systemctl status systemd-tmpfiles-setupd-dev.service

  into the console, the answer is:

  Unit systemd-tmpfiles-setupd-dev.service could not be found.

  The System does only start in recovery mode and I would expect an
  normal start.

  Thanks for help in advance.

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: linux-image-4.15.0-42-generic 4.15.0-42.45
  ProcVersionSignature: Ubuntu 4.15.0-42.45-generic 4.15.18
  Uname: Linux 4.15.0-42-generic x86_64
  ApportVersion: 2.20.9-0ubuntu7.5
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  administrator   2025 F pulseaudio
   /dev/snd/controlC1:  administrator   2025 F pulseaudio
  CurrentDesktop: ubuntu:GNOME
  Date: Mon Dec 10 10:42:07 2018
  HibernationDevice: RESUME=UUID=6ffe8604-b66f-421e-afbd-50bcdeb4ff9e
  InstallationDate: Installed on 2012-05-11 (2404 days ago)
  InstallationMedia: Ubuntu 12.04 LTS "Precise Pangolin" - Release amd64 
(20120425)
  IwConfig:
   eth0  no wireless extensions.
   
   lono wireless extensions.
  ProcFB:
   
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-42-generic 
root=UUID=0c7307f0-bcbe-4a1e-8d04-3004f27151bc ro recovery nomodeset
  RelatedPackageVersions:
   linux-restricted-modules-4.15.0-42-generic N/A
   linux-backports-modules-4.15.0-42-generic  N/A
   linux-firmware 1.173.2
  RfKill:
   
  SourcePackage: linux
  UpgradeStatus: Upgraded to bionic on 2018-12-10 (0 days ago)
  dmi.bios.date: 12/27/2011
  dmi.bios.vendor: Intel Corp.
  dmi.bios.version: BLH6710H.86A.0146.2011.1227.1631
  dmi.board.asset.tag: To be filled by O.E.M.
  dmi.board.name: DH67BL
  dmi.board.vendor: Intel Corporation
  dmi.board.version: AAG10189-209
  dmi.chassis.type: 3
  dmi.modalias: 
dmi:bvnIntelCorp.:bvrBLH6710H.86A.0146.2011.1227.1631:bd12/27/2011:svnbluechipComputerAG:pn:pvr:rvnIntelCorporation:rnDH67BL:rvrAAG10189-209:cvn:ct3:cvr:
  dmi.sys.vendor: bluechip Computer AG

To manage notifications about this bug go to: