On 9/13/18 11:41 AM, Bruno Friedmann wrote:
On jeudi, 13 septembre 2018 14.43:02 h CEST mike wrote:
On 9/13/18 6:36 AM, Maximilian Trummer wrote:
Am Mittwoch, 12. September 2018, 20:03:26 CEST schrieb mike:
On 9/12/18 1:37 PM, Maximilian Trummer wrote:
Am Mittwoch, 12. September 2018, 18:57:24 CEST schrieb mike:
Hi,
Running Tumbleweed...is this a known problem...unable to reboot
or shut down with an nvme ssd?? Running with a Ryzen 2700 and
Gigabyte 470 aorus ultra gaming motherboard...Thanks for any help...
mike Does it really not shut down and reboot at all, or does it after a much longer time than what you would expect from an NVMe-SSD?
well it goes all the way to the reboot or shutdown message than
wait...wait
then some kind of message about workers giving up...than hangs and
never
completes.....
If it's the latter, I might have the same problem, already reported to the bugzilla but so far no response:
https://bugzilla.opensuse.org/show_bug.cgi?id=1106629
https://forums.opensuse.org/showthread.php/532311-Extremely-slow-boot-wi th -encrypted-root
regards It does appear to be the same....I waited this time and it doe shutdown & reboot...It takes
like 3 1/2 minutes to complete....kind of makes having an ssd a handicap....
mike
Is your root disk with Tumbleweed on it encrypted? No........ Fully encrypted M2 here and booting, shutdown working like a breath. You should also check your nvme mfg to be sure your use the last firmware.
just did that from windows using samsung magician, runs noticeably quicker......
nvme-cli can help (also smartctl) to identifying troubles.
just got it
Now to debug check the wiki page about booting systemd in debug mode, this will help you to get more messages about the root cause about the slowliness
I will do that.....the ssd runs super fast when booting, with the system running....it's just the shutdown stalls after the reboot or shutdown message appears, good news is with firmware update instead of taking 3 1/2 minutes, it's down to 3 minutes.....thanks for the help, mike
another tricks, go to logout of your normal user xorg session. then after 10s check if any process is still running with that users.
ntp is often the case of failure (ntp looking for a ntpd server to synchronize clock, but the network is already gone...) move to systemd-timesyncd.service
-- To unsubscribe, e-mail: opensuse-support+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-support+owner@opensuse.org