After switching to the SSD from the HDD on my laptop (and following upgrade to 13.1) I’m experiencing a pretty long delay on startup. It happens somewhere before Login request.
If I use arrow keys, then I can see output telling me something about time out on trying to connect to a partition on my old HDD as well as a couple of other messages. Last of them says about apparmor.
The strange thing is, the graphical startup screen seems to blink multiple times and console seems to generate messages, but they seems to be the same messages again and again.
The whole system start till the login screen takes about one minute.
In the boot logs I’ve found following entries:
/usr/sbin/cron: pam_unix(crond:session): session opened for user root by (uid=0)
systemd: Starting user-0.slice.
systemd: Created slice user-0.slice.
systemd: Expecting device dev-disk-by\x2did-ata\x2dHitachi_HTS545050B9A300_120517PBN4751710V8WE\x2dpart5.device...
systemd: Starting User Manager for 0...
systemd: Starting Session 2 of user root.
systemd: Started Session 2 of user root.
systemd: pam_unix(systemd-user:session): session opened for user root by (uid=0)
systemd: Failed to open private bus connection: Failed to connect to socket /run/user/0/dbus/user_bus_socket: No such file or directory
systemd: Job dev-disk-by\x2did-ata\x2dHitachi_HTS545050B9A300_120517PBN4751710V8WE\x2dpart5.device/start timed out.systemd: Timed out waiting for device dev-disk-by\x2did-ata\x2dHitachi_HTS545050B9A300_120517PBN4751710V8WE\x2dpart5.device.
systemd: Dependency failed for /dev/disk/by-id/ata-Hitachi_HTS545050B9A300_120517PBN4751710V8WE-part5.
And the systemd-analyze tells, that I should take a look on the user space:
I was a little bit confused by the yast partitioner.
It has shown the swap on the /sda5 and I only have noticed, that it wasn’t mounted as I’ve chosen the editing of the swap partition. After having selected to mount this swap partition and having applied the changes I’ve noticed, that the fstab got the new row for swap on /sda5 but the old erroneous one remained.
Sorry, I haven’t seen that effect on preview: it seems to be an issue of the copy command from the terminal output. It seems not to copy the first line break. Actually the UUID in the first line of my post is located in the second line.
I’ve commended the first line out and moved the last one with the correct swap mount to the top of the file and it has done the job - my laptop is starting in under a 40 seconds.
On 2013-12-21 22:36, kostgr wrote:
> robin_listas;2610450 Wrote:
>> On 2013-12-21 19:36, kostgr wrote:
>>> By the way, is it correct to mount the swap at the end?
>> Traditionally, fstab entries were activated in the order they appear.
>> Swap entry at the end might be
>> important if you need swap space early.
> Is it really important to have the swap mounting point at the end of the
I think it should be at the start.
What I meant is that if you put it at the end, you would mount swap at the very end, and if it is
needed because you have little memory, boot would crash. A people nowdays have lots of memory, this
would not happen and possition of the swap entry would be irrelevant.
You understood me the other way round.
> Does openSuse handle mounts differently?
As I said, traditionally entries were mounted in read order. Nowdays, with systemd, I think I heard
it was different, but I don’t clearly remember this. It is possible that the system decides
automatically what to do.
Cheers / Saludos,
Carlos E. R.
(from 13.1 x86_64 “Bottle” (Elessar))