You are not logged in.
I cloned my sdd (40Gb) to a larger one (240Gb) by using
dd
as described here : https://wiki.archlinux.org/index.php/di … _hard_disk
After that, I keep seeing a bunch of errors like
systemd-journald[179]: Failed to write entry (12 items, 337 bytes), ignoring: Cannot assign requested address
on every boot.
After some research, I found a forum post describing my issue and providing a fix for it : https://www.linuxquestions.org/question … 175527467/
I am unable to follow it through, so I'll do the most I can and describing what I get in this post.
I first run
dmesg
The whole output is uploaded to http://pastebin.com/myb7EuHR
It contains a lot of error messages like :
[ 3.568890] systemd-journald[179]: Failed to write entry (9 items, 257 bytes), ignoring: Cannot assign requested address
[ 3.568945] systemd-journald[179]: Failed to write entry (9 items, 268 bytes), ignoring: Cannot assign requested address
[ 3.568967] systemd-journald[179]: Failed to write entry (9 items, 262 bytes), ignoring: Cannot assign requested address
[ 3.568992] systemd-journald[179]: Failed to write entry (9 items, 265 bytes), ignoring: Cannot assign requested address
[ 3.569010] systemd-journald[179]: Failed to write entry (9 items, 234 bytes), ignoring: Cannot assign requested address
journalctl -xn
outputs http://pastebin.com/FVTKRYZj
journalctl --verify
writes on the console
PASS: /run/log/journal/8320c89772da42a28ab9a22f91db393b/system.journal
PASS: /var/log/journal/8320c89772da42a28ab9a22f91db393b/system@40811675655c4215b7005e21720e1ec7-0000000000000001-0005320193123821.journal
ee6ee8: Invalid object
File corruption detected at /var/log/journal/8320c89772da42a28ab9a22f91db393b/system.journal:ee6ee8 (of 16777216 bytes, 93%).
FAIL: /var/log/journal/8320c89772da42a28ab9a22f91db393b/system.journal (Bad message)
PASS: /var/log/journal/8320c89772da42a28ab9a22f91db393b/system@000533cba54426b1-4fff5b5ad5181e82.journal~
PASS: /var/log/journal/8320c89772da42a28ab9a22f91db393b/system@0005295f3f7b9dbf-9dd7b110dadce128.journal~
7fd628: Unused data (entry_offset==0)
PASS: /var/log/journal/8320c89772da42a28ab9a22f91db393b/system@0005311195f04a61-6a91ec1a922995b9.journal~
7fff18: Unused data (entry_offset==0)
PASS: /var/log/journal/8320c89772da42a28ab9a22f91db393b/system@000530f5c421f6d5-be27b65a3e7c97a8.journal~
PASS: /var/log/journal/8320c89772da42a28ab9a22f91db393b/system@00052cdf687307f7-897345744b431ee9.journal~
7fff60: Unused data (entry_offset==0)
PASS: /var/log/journal/8320c89772da42a28ab9a22f91db393b/system@0005320193126931-610038068c19d851.journal~
PASS: /var/log/journal/8320c89772da42a28ab9a22f91db393b/user-1000@000533cba5addf1d-ecf1a4cb0c7c6105.journal~
7ffe00: Unused data (entry_offset==0)
PASS: /var/log/journal/8320c89772da42a28ab9a22f91db393b/system@00053186b77c0dae-345dc26b515ea8b5.journal~
29b2e78: Invalid entry item (21/23 offset: 000000
29b2e78: Invalid object contents: Bad message
File corruption detected at /var/log/journal/8320c89772da42a28ab9a22f91db393b/system@00052a1706314172-64cb48bf3d675eb9.journal~:29b2e78 (of 50331648 bytes, 86%).
FAIL: /var/log/journal/8320c89772da42a28ab9a22f91db393b/system@00052a1706314172-64cb48bf3d675eb9.journal~ (Bad message)
000000: Invalid tail monotonic timestamp
File corruption detected at /var/log/journal/8320c89772da42a28ab9a22f91db393b/user-1000@3a5227a6123e40efb4a7f757149a0213-0000000000000866-00052934a2b98c94.journal:913a78 (of 16777216 bytes, 56%).
FAIL: /var/log/journal/8320c89772da42a28ab9a22f91db393b/user-1000@3a5227a6123e40efb4a7f757149a0213-0000000000000866-00052934a2b98c94.journal (Bad message)
PASS: /var/log/journal/8320c89772da42a28ab9a22f91db393b/system@40811675655c4215b7005e21720e1ec7-0000000000016ee2-000533338a4547af.journal
PASS: /var/log/journal/8320c89772da42a28ab9a22f91db393b/system@00052f46dced137e-ab391be72bf0ec4e.journal~
PASS: /var/log/journal/8320c89772da42a28ab9a22f91db393b/user-1000.journal
7fff38: Unused data (entry_offset==0)
PASS: /var/log/journal/8320c89772da42a28ab9a22f91db393b/system@0005315054154b5c-878f9d53eb4fdde3.journal~
PASS: /var/log/journal/8320c89772da42a28ab9a22f91db393b/system@000530be15373d98-6100ec19b412af84.journal~
PASS: /var/log/journal/8320c89772da42a28ab9a22f91db393b/user-1000@3a5227a6123e40efb4a7f757149a0213-0000000000016ed8-000533338a453e3a.journal
35d9ab0: Unused data (entry_offset==0)
PASS: /var/log/journal/8320c89772da42a28ab9a22f91db393b/system@0005308dbd5fcb26-afcd4460a52ab40a.journal~
and gives me back the prompt
journalctl --disk-usage
outputs
Archived and active journals take up 456.0M on disk.
I don't understand what is happening. The other forum post describes large logs whereas mine are not that big, and I still have plenty of space available.
I have no idea what steps I should do to solve this issue.
--
edit : I use a thinkpad x201 if it helps.
Last edited by mehz (2016-06-04 15:25:18)
Offline
You might try to clean your journal using one of the options:
--vacuum-size=, --vacuum-time=, --vacuum-files=
See 'man journalctl'.
It should be better than manually removing corrupted journal files.
Offline
I just ran
sudo journalctl --vacuum-size=10M
it printed on the console
Vacuuming done, freed 0B of archived journals on disk.
Deleted archived journal /var/log/journal/8320c89772da42a28ab9a22f91db393b/system@0005295f3f7b9dbf-9dd7b110dadce128.journal~ (32.0M).
Deleted archived journal /var/log/journal/8320c89772da42a28ab9a22f91db393b/user-1000@3a5227a6123e40efb4a7f757149a0213-0000000000000866-00052934a2b98c94.journal (16.0M).
Deleted archived journal /var/log/journal/8320c89772da42a28ab9a22f91db393b/system@00052a1706314172-64cb48bf3d675eb9.journal~ (48.0M).
Deleted archived journal /var/log/journal/8320c89772da42a28ab9a22f91db393b/system@00052cdf687307f7-897345744b431ee9.journal~ (64.0M).
Deleted archived journal /var/log/journal/8320c89772da42a28ab9a22f91db393b/system@00052f46dced137e-ab391be72bf0ec4e.journal~ (64.0M).
Deleted archived journal /var/log/journal/8320c89772da42a28ab9a22f91db393b/system@0005308dbd5fcb26-afcd4460a52ab40a.journal~ (56.0M).
Deleted archived journal /var/log/journal/8320c89772da42a28ab9a22f91db393b/system@000530be15373d98-6100ec19b412af84.journal~ (8.0M).
Deleted archived journal /var/log/journal/8320c89772da42a28ab9a22f91db393b/system@000530f5c421f6d5-be27b65a3e7c97a8.journal~ (8.0M).
Deleted archived journal /var/log/journal/8320c89772da42a28ab9a22f91db393b/system@0005311195f04a61-6a91ec1a922995b9.journal~ (8.0M).
Deleted archived journal /var/log/journal/8320c89772da42a28ab9a22f91db393b/system@0005315054154b5c-878f9d53eb4fdde3.journal~ (8.0M).
Deleted archived journal /var/log/journal/8320c89772da42a28ab9a22f91db393b/system@00053186b77c0dae-345dc26b515ea8b5.journal~ (8.0M).
Deleted archived journal /var/log/journal/8320c89772da42a28ab9a22f91db393b/system@0005320193126931-610038068c19d851.journal~ (8.0M).
Deleted archived journal /var/log/journal/8320c89772da42a28ab9a22f91db393b/system@40811675655c4215b7005e21720e1ec7-0000000000000001-0005320193123821.journal (48.0M).
Deleted archived journal /var/log/journal/8320c89772da42a28ab9a22f91db393b/system@40811675655c4215b7005e21720e1ec7-0000000000016ee2-000533338a4547af.journal (8.0M).
Deleted archived journal /var/log/journal/8320c89772da42a28ab9a22f91db393b/user-1000@3a5227a6123e40efb4a7f757149a0213-0000000000016ed8-000533338a453e3a.journal (8.0M).
Deleted archived journal /var/log/journal/8320c89772da42a28ab9a22f91db393b/system@000533cba54426b1-4fff5b5ad5181e82.journal~ (24.0M).
Vacuuming done, freed 416.0M of archived journals on disk.
I then reboot the computer, but the issue was not solved.
I tried
sudo journalctl --vacuum-size=100M
Vacuuming done, freed 0B of archived journals on disk.
Vacuuming done, freed 0B of archived journals on disk.
Offline
So there is something else than missing space on disk.
But I don't use a SSD disk, so I cannot help you more on this matter. Sorry.
Offline