[SOLVED] jessie -- systemd fsck looks like computer is hanging

radiodee1 · 08-06-2014, 01:52 PM

I have been following testing for some time. I believe I'm running systemd now. My problem is that when fsck runs it looks like my boot up is hanging. Is there any way to get the old progress bar to display when the computer decides to do a fsck check?

EDDY1 · 08-06-2014, 08:22 PM

On my system it seems to do fsck every boot. But it doesn't display all of the messages lime wheezy, even if I put verbose in /etc/default/grub. You can either check syslog, messages or dmesg for info. Keep in mind that systemd is new to debian & it will take some time to get used to. & yes I have error messages that I haven't figured out yet. Also I switched from gnome to Xfce.

gradinaruvasile · 08-06-2014, 11:21 PM

Quote:

Originally Posted by EDDY1

On my system it seems to do fsck every boot. But it doesn't display all of the messages lime wheezy, even if I put verbose in /etc/default/grub. You can either check syslog, messages or dmesg for info.

Try "debug ignore_loglevel" added to CMDLINE_LINUX. I have tons of boot up messages with these.

EDDY1 · 08-07-2014, 02:48 AM

Quote:

Originally Posted by gradinaruvasile

Try "debug ignore_loglevel" added to CMDLINE_LINUX. I have tons of boot up messages with these.

Thanks I will after I finish my LFS101x corse at Linux EDX.

radiodee1 · 08-07-2014, 08:25 AM

'debug ignore_loglevel' did not work for me. I edited /etc/default/grub and executed 'update-grub'. My messages stayed the same. Any other suggestions?

EDDY1 · 08-07-2014, 04:17 PM

Have you tried to work on the errors starting from the top of messages?

radiodee1 · 08-07-2014, 04:39 PM

I think the issue is probably that I dual boot and I have to make changes to grub in the other operating system. I'll try again and get back to this post later.

radiodee1 · 08-08-2014, 01:25 PM

so I dual boot with fedora, and the fedora grub took over my machine. I added ' ; verbose ' to the /etc/default/grub CMDLINE_LINUX line on fedora. (note the semicolon! ) This causes fedora to report 'verbose' as an error, and then asks me to press any key during boot up... BUT this is interpreted by debian correctly and the boot up is verbose when I start the deb OS. I suppose I can live with the repercussions in fedora since I want the correct outcome in debian.

EDDY1 · 08-08-2014, 04:24 PM

Quote:

Originally Posted by radiodee1

so I dual boot with fedora, and the fedora grub took over my machine. I added ' ; verbose ' to the /etc/default/grub CMDLINE_LINUX line on fedora. (note the semicolon! ) This causes fedora to report 'verbose' as an error, and then asks me to press any key during boot up... BUT this is interpreted by debian correctly and the boot up is verbose when I start the deb OS. I suppose I can live with the repercussions in fedora since I want the correct outcome in debian.

Fedora runs on systemd have you checked the differences in the config files? What desktop environment?

radiodee1 · 08-09-2014, 07:34 AM

for desktop environment I use gnome on fedora and xfce on debian. I really have not looked at the difference in the config files.

EDDY1 · 08-09-2014, 12:29 PM

Quote:

Originally Posted by radiodee1

for desktop environment I use gnome on fedora and xfce on debian. I really have not looked at the difference in the config files.

Well that would be a great place to start. You can do it quite easily using "diff"