hi, can you tell me where are stored the boot log?
I searched in messages and boot.log but it not seems the same thing.
thanks
Which boot log are you talking about?
What exactly are you looking for?
I searched in messages and boot.log but it not seems the same thing.
Of course not.
messages is written by rsyslog (or any other syslog daemon you may have running) and contains every log message sent to it that isn’t filtered out to another file by its configuaration.
boot.log on the other hand is written by plymouth and contains all messages that would have been printed on the text mode console while booting.
I.e. that what you would see on VT-0 when you disable plymouth or press ESC during boot.
And then there’s also systemd’s journal, which is similar to messages, i.e. a system-wide message log for everything.
Uhm precisely when I start opensuse and press ESC button I view some logs messages, this log where are stored?? In boot.log there aren’t 
They should be. Unless you disabled plymouth.
Here’s what mine looks like:
Trying manual resume from /dev/sdb2
Invoking userspace resume from /dev/sdb2
resume: libgcrypt version: 1.5.4
Trying manual resume from /dev/sdb2
Invoking in-kernel resume from /dev/sdb2
Waiting for device /dev/root to appear: ok
fsck from util-linux 2.23.2
[/sbin/fsck.reiserfs (1) -- /] fsck.reiserfs -a /dev/sda1
Reiserfs super block in block 16 on 0x801 of format 3.6 with standard journal
Blocks (total/free): 19537040/697726 by 4096 bytes
Filesystem is clean
fsck succeeded. Mounting root device read-write.
Mounting root /dev/root
mount -o rw,acl,user_xattr -t reiserfs /dev/root /root
Welcome to openSUSE 13.1 (Bottle) (x86_64)!
Starting Replay Read-Ahead Data...
Starting Collect Read-Ahead Data...
OK ] Listening on Syslog Socket.
OK ] Reached target System Time Synchronized.
OK ] Reached target Remote File Systems (Pre).
OK ] Reached target Remote File Systems.
OK ] Listening on Delayed Shutdown Socket.
OK ] Listening on /dev/initctl Compatibility Named Pipe.
OK ] Listening on LVM2 metadata daemon socket.
OK ] Reached target Encrypted Volumes.
OK ] Listening on udev Kernel Socket.
OK ] Listening on udev Control Socket.
OK ] Set up automount Arbitrary Executable File Formats File System Automount Point.
OK ] Listening on Journal Socket.
Starting LSB: Set default boot entry if called...
Mounting POSIX Message Queue File System...
Starting Create list of required static device nodes for the current kernel...
Mounting Debug File System...
...
Or they should be in systemd’s journal as well, use “journalctl” to display that (as root preferably).
If you are looking for the message about a particular service, you might better use “systemctl status service”, this will show you more detailed information. And if you run it as root (with sudo e.g.) it will even print the corresponding lines from the journal. 
If this doesn’t help you, then please specify what exactly you want to achieve/find. There might be other ways to get that information.
I obtain a swap mounting error during the boot and I’d like to read well the error because the loading and the log is very fast for read all the error. Maybe this error can be in journalctl ??
Thanks again
Should be, yes.
I see you have a different thread running about this as well.
Apparently your swap is actually mounted successfully?
Check with “swapon”.
If yes, you can just ignore that error, or remove the swap entry from /etc/fstab.
At least on some systems systemd seems to mount all available swap partitions automatically and then in addition those listed in fstab which leads to an error of course because they are already mounted.
I don’t see that here btw, but I have seen other people reporting it.
I tried to ask because in systems.swap page I read that if in the system there are both swap mount line, the system automatically should mount only from one and not report any errors, correct me if I wrong please 
if yes should be a small bug?
Well, according to the documentation, yes.
But IIRC (from other users’ reports) the swap is mounted once via the device name (/dev/sdb2 e.g.), once via ID (/dev/disk/by-id/ata-SAMSUNG_SP1203N_S00QJ10Y321445-part2 e.g. which is actually a symlink to /dev/sdb2), and maybe even via UUID (/dev/disk/by-uuid/…) as well.
If I were to guess, I’d say that the swap unit generator (or maybe systemd itself) is not smart enough to recognize that all those (and the entry in fstab) are actually the same partition.
Under certain circumstances at least. As mentioned I do not see that here.
What does “systemctl|grep swap” say, btw?
if yes should be a small bug?
Probably.
Unfortunately the (open)SUSE systemd maintainers are quite reluctant nowadays to release updates because of possible problems.
On Thu 23 Oct 2014 08:36:02 AM CDT, susecom wrote:
hi, can you tell me where are stored the boot log?
I searched in messages and boot.log but it not seems the same thing.
thanks
Hi
Have you used the journactl command (examples in the man page)?
eg;
journalctl -x |grep swap
Oct 20 12:18:54 big-bird systemd[1]: Activating swap /dev/disk/by-id/ata-OCZ-VERTEX4_OCZ-7B81SXCWP5VKVR6X-part4...
-- Subject: Unit dev-disk-by\x2did-ata\x2dOCZ\x2dVERTEX4_OCZ\x2d7B81SXCWP5VKVR6X\x2dpart4.swap has begun with start-up
-- Unit dev-disk-by\x2did-ata\x2dOCZ\x2dVERTEX4_OCZ\x2d7B81SXCWP5VKVR6X\x2dpart4.swap has begun starting up.
Oct 20 12:18:54 big-bird kernel: Adding 8388604k swap on /dev/sda4. Priority:-1 extents:1 across:8388604k SSFS
Oct 20 12:18:54 big-bird systemd[1]: Activated swap /dev/disk/by-id/ata-OCZ-VERTEX4_OCZ-7B81SXCWP5VKVR6X-part4.
-- Subject: Unit dev-disk-by\x2did-ata\x2dOCZ\x2dVERTEX4_OCZ\x2d7B81SXCWP5VKVR6X\x2dpart4.swap has finished start-up
-- Unit dev-disk-by\x2did-ata\x2dOCZ\x2dVERTEX4_OCZ\x2d7B81SXCWP5VKVR6X\x2dpart4.swap has finished starting up.
-- Subject: Unit swap.target has begun with start-up
-- Unit swap.target has begun starting up.
-- Subject: Unit swap.target has finished start-up
-- Unit swap.target has finished starting up.
–
Cheers Malcolm °¿° LFCS, SUSE Knowledge Partner (Linux Counter #276890)
openSUSE 13.1 (Bottle) (x86_64) GNOME 3.10.1 Kernel 3.11.10-21-desktop
If you find this post helpful and are logged into the web interface,
please show your appreciation and click on the star below… Thanks!
this is my log when I have a swap mount line in fstab too:
kernel: ALSA patch_realtek.c:426 SKU: swap=0x0
systemd[1]: Activating swap /dev/sda2…
– Subject: Unit dev-sda2.swap has begun with start-up
– Unit dev-sda2.swap has begun starting up.
systemd[1]: Activating swap /dev/disk/by-id/ata-HGST_HTS766050A7E630_TF766AWHH5E4NM-part2…
– Subject: Unit dev-disk-by\x2did-ata\x2dHGST_HTS766050A7E630_TF766AWHH5E4NM\x2dpart2.swap has begun with start-up
– Unit dev-disk-by\x2did-ata\x2dHGST_HTS766050A7E630_TF766AWHH5E4NM\x2dpart2.swap has begun starting up.
swapon[876]: swapon: /dev/disk/by-id/ata-HGST_HTS766050A7E630_TF766AWHH5E4NM-part2: swapon failed: Device or resource busy
systemd[1]: dev-disk-by\x2did-ata\x2dHGST_HTS766050A7E630_TF766AWHH5E4NM\x2dpart2.swap swap process exited, code=exited status=255
systemd[1]: Failed to activate swap /dev/disk/by-id/ata-HGST_HTS766050A7E630_TF766AWHH5E4NM-part2.
– Subject: Unit dev-disk-by\x2did-ata\x2dHGST_HTS766050A7E630_TF766AWHH5E4NM\x2dpart2.swap has failed
– Unit dev-disk-by\x2did-ata\x2dHGST_HTS766050A7E630_TF766AWHH5E4NM\x2dpart2.swap has failed.
– Subject: Unit swap.target has failed
– Unit swap.target has failed.