You are not logged in.
Pages: 1
I upraded my system and rebooted it totay. Now I cant get it works because services and targets are loaded extremely slow (~ 10min each) and kernel periodicaly writes messages like:
INFO: task kworker... blocked for more than 120 seconds
INFO: task systemd-journal... blocked for more than 120 seconds
I use uefi system installed on ssd with f2fs filesystem with hybrid ati + intel graphic
I tried to rollback to previous kernel version, fsck partitions, update my system and disable a lot of services but it didn't help
journal doesn't write log as well
Offline
I upraded my system and rebooted it totay. Now I cant get it works because services and targets are loaded extremely slow (~ 10min each) and kernel periodicaly writes messages like:
Can you please rephrase your post? I found it very difficult to read.
Before jumping to rolling back do you know what got upgraded? Did you look at the pacman.log?
journal doesn't write log as well
What do you mean the journal doesn't write log? That tells me nothing I mean you could at least paste the output of the error when you try to call the Journal?
What system / architecture are you using?
How did you update your system?
list goes on..
Offline
Before jumping to rolling back do you know what got upgraded? Did you look at the pacman.log?
Yes I did,.
mesa, mesa-libgl, intel-dri, xf86-video-intel, ati-dri, linux, linux-headers and other not so important packages were upgraded without errors
What system / architecture are you using?
x86_64
What do you mean the journal doesn't write log? That tells me nothing I mean you could at least paste the output of the error when you try to call the Journal?
There are no errors, it hasn't written anything since last successfull bootup
It seems kernel can't write anything to disk , but I tried to create/edit/delete some files mannualy and it worked
Last edited by amenzhisnky (2014-01-14 13:48:47)
Offline
So where exactly in the boot process are you failing?
Offline
So where exactly in the boot process are you failing?
I can't wait for hours until system is loaded
Offline
captaincurrie wrote:So where exactly in the boot process are you failing?
I can't wait for hours until system is loaded
What do you mean?
Offline
amenzhisnky wrote:captaincurrie wrote:So where exactly in the boot process are you failing?
I can't wait for hours until system is loaded
What do you mean?
I mean the problem is that system can't write anything to disk, systemd normally starts services but some of them which depends on I/O can't start successfully.
There're no error messages except info that systemd-journal is blocked for more than 120 seconds
Offline
So you can't even chroot into the system using a live CD? You will be able to get the relevant logs / information required then
Last edited by Kartious (2014-01-14 14:45:21)
Offline
So you can't even chroot into the system using a live CD? You will be able to get the relevant logs / information required then
Yes I can, I bumped into kernel bug at fs/f2fs/fsfs.h:800 when I used vim, it could be a problem with my disk or root partition's inconsistency, I'll try to reformat it when I get home ![]()
Offline
I would really recommend using f2fs for now. Sure it is a great idea, and I applaud Samsung for taking the initiative to make a fancy new filesystem. But there is still quite a bit of work to be done before it can really be relied upon. Until just a few months ago, there wasn't even a fsck tool.
Offline
I would really recommend using f2fs for now. Sure it is a great idea, and I applaud Samsung for taking the initiative to make a fancy new filesystem. But there is still quite a bit of work to be done before it can really be relied upon. Until just a few months ago, there wasn't even a fsck tool.
I think you meant "i would really not recommend...."
Offline
Indeed I did.
Thanks captain!
For the record, I am an experimental filesystem user myself (btrfs). But I use it with the full expectation that I need working tested backups, which in this case are on the same machine, and the desire to loosely follow the happenings of the upstream development.
Offline
Problem was caused by f2fs, thus I refomated root filesystem and it's gone.
I'm looking forward to '-a' flag for fsck.f2fs tool
Last edited by amenzhisnky (2014-01-14 17:01:48)
Offline
That is one of the reasons I recommend against fsf2 for now. They have created a fsck.f2fs which has none of the standard flags, no --help/-h, and no man page. IMO it wasn't ready to be given the standard fsck.* name yet, as it doesn't comply with the expectations that the init system might have.
Offline
Pages: 1