[SOLVED] Disk check failed at boot.

Hello,
I've got a problem with arch booting. It looks like my cpu doesn't like being left alone fat night. I powered it on today and what I get iss disk check failed error and reboot message. I've tried fsck-ing all partitions and everything seems to be allright. What's more I can mount everything when press ctrl+z when arch tries to reboot and system loading goes on. Any tips? What should I post?
Last edited by muchzill4 (2010-02-05 10:02:48)

You have some messed up file systems. As if you didn't know.=O)
Have you changed fstab? Switched disks around? Try using uuid in fstab instead of '/dev/sdxx'.
Check this thread http://bbs.archlinux.org/viewtopic.php?id=89857
and use
ls -l /dev/disk/by-uuid

Similar Messages

[SOLVED] "Filesystem check failed" during boot process

I was using XFCE on my netbook recently and clicked "shutdown". It logged out to the command prompt and nothing happened. Assuming that I'd clicked "logout" by mistake, I typed "pacman -Syu" to run an update... And moments later it suddenly started the shutdown process.
Now, whenever I boot up, I see the message below. I tried booting from a GParted CD to check the filesystems for errors, but none were detected.
Can anyone suggest what I might need to do to fix the problem?
rootfs: clean, 11026/246512 files, 477083/984576 blocks
home: clean, 4386/527280 files, 237183/2105344 blocks
/dev/sdb2 is mounted. e2fsck: Cannot continue, aborting.
************* FILESYSTEM CHECK FAILED ************
* Please repair manually and reboot. Note that the root
* file system is currently mounted read-only. To remount
* it read-write type: mount -n -o remount,rw /
* when you exit the maintenance shell the system will
* reboot automatically.
Give root password for maintenance
(or type Control-D to continue):
Last edited by esuhl (2012-03-27 01:20:07)

Thank you all for your replies :-)
hadrons123 wrote:What happens when you do try the suggestion given by it?
I don't exactly know how I should "repair manually"... I thought a filesystem check in GParted would have been enough...
lijpbasin wrote:You can boot the system using a archlinux live cd, and run fsck manually on every linux partition in the old system with options.
DON'T mount any of the filesystems before running fsck, or your data will probably be lost. If you want to check the partition information first, run fdisk -l with root privileges.
Thanks. I tried booting from an ArchBang live CD last night and ran "e2fsck -pcv" on each partition. The check completed, but the problem persists... I just tried again using "fsck" as you suggested and got the following output (but the machine still fails to boot with the same error as before):
fsck from util-linux 2.20.1
e2fsck 1.41.14 (22-Dec-2010)
usr was not cleanly unmounted, check forced.
Pass 1: Checking inodes, blocks, and sizes
Pass 2: Checking directory structure
Pass 3: Checking directory connectivity
Pass 4: Checking reference counts
Pass 5: Checking group summary information
usr: 115811/458752 files (1.7% non-contiguous), 783161/1834496 blocks
Gcool wrote:
/dev/sdb2 is mounted. e2fsck: Cannot continue, aborting.
As mentioned already, the reason it's failing is because the /dev/sdb2 partition is mounted before it can be fsck'd. What is this partition exactly (which filesystem, what's on it, mountpoint,...)?
I'm not overly familiar with the Linux boot process, but why would it suddenly be mounting this partition before fsck-ing it? Even if it was mounted when the netbook shutdown, surely the boot process starts with all partitions unmounted...? Anyway, the partition details from /etc/fstab are below.
<file system> <dir> <type> <options> <dump> <pass>
tmpfs /tmp tmpfs nodev,nosuid 0 0
/dev/sda1 / ext2 defaults,noatime 0 1
/dev/sdb1 /home ext2 defaults,noatime,user_xattr 0 1
/dev/sdb2 /usr ext2 defaults,noatime 0 1
I'm (now) aware that mounting /usr as a separate partition is a bad idea and (having read the "Error when booting with the new initscripts" thread), I have told pacman to ignore updates to the initscripts package (until I figure out how best to work round or fix that issue).
Shark wrote:Write umount /dev/sdb2 in konsole or unmount partition in gparted by right click on problematic partition and click unmount. Than proced.
If I type "umount /dev/sdb2" at the prompt, I get the following error:
umount: /usr: device is busy.
(In some cases useful info about processes that use
the device is found by lsof(8) or fuser(1))
I tried "umount -l /dev/sdb2" to unmount when the device becomes free... but it never does.
I also booted into GParted, but there is no option to "unmount" /dev/sdb2. There is a "mount" option in the menu, but it is greyed out. If I open a terminal window from the GParted Live environment and type "sudo umount /dev/sdb2" I get the following message:
umount: /dev/sdb2: not mounted
DSpider wrote:Are you mounting the root drive with "ro" (read only) in fstab?
No (as shown above). I don't *think* I've messed anything up with fstab or any other config files -- everything was working perfectly till the netbook shutdown whilst pacman was running.

[SOLVED] Filesystem check failed - All seems normal

Yesterday i turned of my computer after it had been on for a week or so and this morning i can't get it to boot.
While booting, on the filesystem check stage, it reports all filesystems as clean, but then says [FAIL], and gives me access to the maintenance shell.
- I booted the system with a Gparted live cd and did a check on all partitions on all disks. It reported no errors.
- in fstab I commented out the external disk and the internal one which doesn't contain any system partitions, still the same.
- I remounted root rw in the maintainance shell, and did a full system upgrade (last kernel upgrade was applied) ... still no cookies...
- I also tried to mount all the partitions in the maintenance shell. All were mounted without an error, and as far as i can tell all data was there and browsable at least.
- I tried to boot with a /forcefsck file and the checks were all done without any messages, after which it failed as usual.
Also i tried fallback (before the upgrade), which as you can guess by now, also gave the same error. The message about the filesystem check failing is not giving me any useful information. All it does is list the partitions saying every partition is clean, and then says the filesystem check has failed.
As you can probably tell, I did all the steps I could find on the forums that looked it could solve my problems, and I've hit a dead end. If I knew which partition had the problem I could move the data and format it. Could this be a hardware error?
Thanks in advance for any help offered
Last edited by vexxor (2009-07-28 11:04:02)

KimTjik wrote:Maybe a stupid question, but it's not that some partition is totally full?
Nope. I just checked.
Funny thing. In the maintenance console, when i do a "mount -a", I can navigate to the now mounted directories, but I can't see the mounted partitions as an output of either "mount" or "df".
I figured this out when I was checking if the disks were full. Root gets shown, and its on 53%. Just in case i deleted about 20GB of stuff from the media partition, but the problem remains.

[solved] Filesystem check fail - Cannot access LVM Logical Volumes

I am getting a "File System Check Failed"on startup, I recently did a full system upgrade but I'm not entirely sure that the cause of the issue as I don't reboot very often.
I get the error right before this line is echo'ed out:
/dev/mapper/Arch_LVM-Root:
The super block could not be read or does not describe a correct ext2 filesystem...
this is odd because the only ext2 filesystem I have is on an non-LVM boot partition...
I can log-in and mount / as read/write and I can activate LVM with
modprobe dm-mod
and
vgchange -ay Arch_LVM
and they show up in lvdisplay but their status is "NOT available"
I just need to mount these logical volumes so I can retrieve some personal data in my home directory, I am also hesitant to use LVM again if I can't retrieve my data.
any suggestions?
Last edited by action_owl (2010-08-15 02:15:58)

I just popped in the install disk and was able to mount and access the LVM groups as expected, something must have been wonky with my filesystem

Filesystem check failed + accidental /boot deletion

Yesterday I rebooted my PC and suddenly Arch started complaining about "Filesystem check failed", just like stated by the OP in this thread https://bbs.archlinux.org/viewtopic.php … 00#p941200
The problem was with two partitions: /boot and /home. I tried to no avail to manually fsck them using the maintenance console and e2fsck as well as the forcefsck command but it didn't work.
I didn't try any LiveCD back then but since I saw that in that thread the OP solved his problem by deleting some folders located at /media:
Fixed the problem.
The /dev/sda2 and /dev/sda5 were being mounted in the wrong place.
Instead of being mounted in /home and /boot as per /etc/fstab, they were being mounted in new directories in /media called /media/usbhd-sda2 and /media/usbhd-sda5. Upon deleting those folders, everything has gone back to normal.
I have no idea how those new folders got created...but problem solved now.
Thanks for the help, guys
Samsom
Problem is I didn't think at all when I read this post and went right away to delete the problematic folders (the post itself didn't exactly explain how the OP managed to unmount the partitions and then proceed to delete the folders, my umount commands didn't work so it wasn't crystal clear to me how he managed it, my bad tho for not checking what I was deleting).
Luckily, I think I only managed to delete partially my /boot folder (thus GRUB now complains and doesn't boot any system). So now my question is, is there a way to restore my /boot folder without a full system re-install?
Thanks in advance.

But what is the command? mkinitcpio -p kernel26 ? Also how do I fix this grub issue? I'm assuming grub created a default menu.lst after I copied the config files and setup the hd0 but I actually don't recall checking that.
Just re-did all steps including rebuilding the kernel, I still can't get the boot menu when I reboot. It goes directly to grub console.
I checked the generated menu.lst, it lists my root as the device where /boot partition is and the kernel line root enrty is defined for the arch system I want to boot :\
Last edited by Grimn (2011-05-31 17:50:02)

[Solved] Filesystem check failed after removing harddrive

I have a harddrive in a arch computer which is not listed in fstab and not used as root, boot or home. I want to remove it from the computer, but when I try this I get the error filesystem check failed. I get the option to repair, and then get logged in as root. Here I can see my ordinary boot, root and home with fdisk -l. How can I tell the computer that there is nothing wrong, that I dont want use that disk? I searched the forum for this error and found a recommendation to use e2fsck, but since the error is because of the removed disk I cant do that.
Last edited by heptapod (2011-04-28 07:51:23)

Always use persistent block device naming to prevent this.
https://wiki.archlinux.org/index.php/Pe … ice_naming

[Solved] Filesystem check failed - manual repair too

Good Evening.
Recently my Arch box hang up and I had to reboot forcefully. I expected to get a filesysem scan. The messages on bootup say, that the filesystem check failed and I have to repair it manually. The exact error message is similar to http://bbs.archlinux.org/viewtopic.php?id=89394.
Then I log into the maintenance shell and try to run fsck -pck /dev/sdXX. But that doesn't work because it complains that the filesystem is no ext2-fs or the superblock is corrupt. I should try one of the backup superblocks. To figure out the backup superblocks, I tried mke2fs -n /dev/sdXX but that does not work either. Now it complains that /dev/sdXX does not exist! I looked in /dev and the partitions really don't show up. Where are they? I mean, the maintenance shell works on the / partition, or does it?
To cut a long story short, I can't check my partitions and I don't know any other way how to fix the problem. The next ArchLive CD is 500 km away.
I appreciate any help.
Greetz,
haunted
EDIT:
Ok, I solved the problem as I got my ArchLive CD. If it's to anybody's use, that's the procedure I went through:
I inserted the CD and booted from it. I ran the e2fsck several times. First I did an overall check (e2fsck -v /dev/sdaX) on my Arch partition which I had to do manually i.e. type "y" to every inconsisteny found, then updated the badblock list (e2fsck -vc /dev/sdaX) and checked the partition again.
I rebooted the system without the CD to look if I succeded repairing the hdd. Eventually I deleted the /sys mountpoint in the procedure and had to create it again via ArchLive CD. After the next reboot it complained that the superblock's timestap was written in the future. Rebooting with the CD again, checking again and rebooting without CD again.
It wasn´t of any use and Arch complained again. Then I simply rebooted the system (without CD) again and on start up it stopped complaining and did a normal check on the Arch partition, completed the check and went on loading as normal. System repaired.
Last edited by hauntergeist (2010-02-08 11:11:59)

It went ahead and fixed the filesystem, however some of the files (music files mostly) are corrupted and won't play. I have backups of those so it's no big lose, as long as the file system works now.

Filesystem check failed on boot

Hi,
Recently I reinstalled Arch Linux on my laptop (Dell Studio 1737) due to bloating and pacman generally being pretty borked.
For the first few boots it was fine - I installed xorg and xfce, then ran a Pacman -Syu. However, when I reboot, I get the following:
root: clean, XXXX/XXXXXX files, XXXX/XXXXXX blocks
home: clean, XXXX/XXXXXX files, XXXX/XXXXXX blocks
var: clean, XXXX/XXXXXX files, XXXX/XXXXXX blocks
/dev/sda6 is mounted. e2fsck: cannot continue, aborting.
FILESYSTEM CHECK FAILED
Please repair manually and reboot. Note that the root file system is currently mounted read-only. To remount it read-write type: mount -o remount,rw /
When you exit the maintenance shell the system will reboot automatically.
I have tried removing mtab, fsck (despite it saying the filesystem is mounted, even when umount says it is not), among other "fixes"
My current setup is
/dev/sda2: /
/dev/sda3: swap
/dev/sda4: /home
/dev/sda5: /var
/dev/sda6: /usr (this is where the problem occurs)
Can anybody help?
Thanks,
Sam

https://bbs.archlinux.org/viewtopic.php?id=134024

[SOLVED] Filesystem check failed on LVM partition...

My server experienced a power outage last night, and I noticed today that it wasn't booting correctly. Apparently, the storage partition, /dev/mapper/VolGroup00-lvolstorage fails the filesystem check. The first time I booted into it, I ran a manual check and answered (y) to the questions. Now when booting, it quickly displays a bunch of numbers and that scrolls for a little while (goes too fast to understand what they are...). Then it says:
####Filesystem Check Failed####
Please repair manually, blah blah blah
I'm not really sure what to do. Running fsck does the whole numbers scrolling across the screen thing again, finally asking if I want to clone multiply-claimed blocks... =/ I don't want to answer yes anymore until I get someone's input. <_<
EDIT: It said before that there are 81 inodes containing multiply-claimed blocks... Then it said a certain large file (inode #20) has 27818 multiply-claimed blocks shared with 24 other files, and it then lists other files.
Last edited by XtrmGmr99 (2010-05-21 14:14:25)

It went ahead and fixed the filesystem, however some of the files (music files mostly) are corrupted and won't play. I have backups of those so it's no big lose, as long as the file system works now.

[SOLVED] QEMU-KVM fails to boot if passed q35 machine type

As I understand it, qemu still uses the PII3X as the default machine type. I had been using -machine type=q35,accel=kvm for a few weeks to learn more about qemu and KVM. With this code I could boot a win7 VM and I confirmed the ICH9 chipset appeared in the device manager.
After a system update I am no longer able to pass that command. I am using the linux-0.2 image located here.
If I enter this code, the system boots normally:
qemu-system-x86_64 -enable-kvm -boot order=c linux-0.2.img
This however does not work and the bios complains that there is no bootable media found (after waiting for pxe):
qemu-system-x86_64 -enable-kvm -boot order=c -M q35 linux-0.2.img
qemu is 1.7.0-2 (built 02/19/14 but this is the only package in pacman's cache)
seabios is 1.7.3.1-2 (built 09/21/13)
I actually tried this on two different machines with the same result. What can I do next to troubleshoot? Thanks.
Last edited by gizzard (2014-04-13 15:55:25)

R00KIE wrote:
The iso should boot, yes. I did try using -M q35 with a WinXP image I have here and it started to boot (I get blue screens and automatic reboots since lots of things change with -M q35).
One different thing I have however is the specification of the interface type for disks. Try using "-drive file=/path/to/image,if=scsi" or "-drive file=/path/to/image,if=virtio", that seems to make it work for me, it still might make Win7 complain though.
I think I'm getting closer thanks to your help. Adding the if variable allows the debian image to boot using the q35 machine type. Here are results of some trials (command and result):
1. qemu-system-x86_64 -enable-kvm -cpu host -m 1024 debian-live-7.4-amd64-standard.iso
- boots fine
user@debian:~$ lspci | grep ACPI
00:01.3 Bridge: Intel Corporation 82371AB/EB/MB PIIX4 ACPI (rev 03)
2. qemu-system-x86_64 -enable-kvm -cpu host -m 1024 -machine type=q35,accel=kvm debian-live-7.4-amd64-standard.iso
- fails to boot
3. qemu-system-x86_64 -enable-kvm -cpu host -m 1024 -machine type=q35,accel=kvm -drive file=debian-live-7.4-amd64-standard.iso,if=ide
- fails to boot
4. qemu-system-x86_64 -enable-kvm -cpu host -m 1024 -machine type=q35,accel=kvm -drive file=debian-live-7.4-amd64-standard.iso,if=scsi
- boots fine
user@debian:~$ lspci | grep AHCI
00:1f.2 SATA controller: Intel Corporation 82901IR/IO/IH (ICH9R/DO/DH) 6 port SATA Controller [AHCI mode] (rev 02)
user@debian:~$ lspci | grep SCSI
00:03.0 SCSI storage controller: LSI Logic / Symbios Logic 53c895a
4. qemu-system-x86_64 -enable-kvm -cpu host -m 1024 -machine type=q35,accel=kvm -drive file=debian-live-7.4-amd64-standard.iso,if=virtio
- boots fine
user@debian:~$ lspci | grep AHCI
00:1f.2 SATA controller: Intel Corporation 82901IR/IO/IH (ICH9R/DO/DH) 6 port SATA Controller [AHCI mode] (rev 02)
user@debian:~$ lspci | grep SCSI
00:03.0 SCSI storage controller: Red Hat, Inc Virtio block device
I will try these options with the win7 VM and report back. I may need to recreate it from scratch, so it might take a little while.

Filesystem check failed while booting [SOLVED]

I tried to get some help from my previous post but got no answers, so I'll summarize in hope of getting an answer:
I've installed linux before windows because I had this operating system before. But, when I've partitioned I've made a NTFS type 83 for windows, cause I know I'd install it later on.
Now, I've restored my bootloader (grub) but when I try to boot my arch linux copy, a message tells me that my partition sda2 which is my Windows one, isn't clean or corrupt.
all my linux partition are clean, but my NTFS windows partition make me unable to boot on my linux OS with this error msg:
fsck.ext4: Bad magic number in super-block while trying to open /dev/sda2
/dev/sda2:
The superblock could not be read or does not describe a correct ext filesystem. If the devine is valid and it really contains an ext2 filesystem (and not swao or ufs or simething else), then the superblock is corrupt, and you might try running e2fsck with an alternate superbloc:
e2fsck -b 8193 <device>
Next I can do is entering the root psw and use the command line, I really need help to restore my linux partition without formating anything, please.
My guess is that linux doesn't reorganize the partition as it is NTFS and doesn't boot for this reason, but didn't find how to fix it over internet yet, some help would be really appreciated.
Last edited by Mazh (2011-06-10 20:30:39)

My partition layout is:
fdisk -l output:
/dev/sda1 ID (5) extended (don't know what's that didn't think I've made that myself, maybe coming from windows when I installed the NTFS partition)
/dev/sda2 * HPFS/NTFS/exFAT ID (7) (strange cause I had set 87 but well, windows is working correctly it seems)
/dev/sda3 ID (83) linux
/dev/sda5 ID (83) linux
/dev/sda6 ID (83) linux
/dev/sda7 ID (83) linux
/dev/sda8 * ID (83) linux
yep, it's actually strange that my fsck.ext4 check my sda2 partition NTFS...
cat /etc/fstab:
/dev/sda2 /home ext4 defaults 0 1
/dev/sda5 swap defaults 0 0
/dev/sda6 /var ext4 defaults 0 1
/dev/sda7 /usr ext4 defaults 0 1
/dev/sda8 / ext4 defaults 0 1
menu.lst
linux grub
/dev/sd0 (fd0)
/dev/sda (hd0)
/dev/sdb2 (hd1,1)
/dev/sda3 (hd0,2)
title arch linux
root (hd0,7)
kernel /bootvmlinuz26 root=/dev/sda8 ro
initrd /boot/kernel26.img
the arch fallback (same)
title Windows xp lite sp3
rootnoverify (hd0,1)
makeactive
chainloader +1
I really have to write by hands, so if you wants more info tell me and I'll write more.
it's strange, could you explain me what does mean hd1 or hd0? isn't the 1st and second hard drive? and the second array the partition? cause if so, i've only 1 drive. But I'm probably not correct. Hope you get enough info to get me out of this problem!
And no, I'm not using UUIDs, thx for your suggestion!

"Filesystem check failed" on boot [Solved]

It seems to not like /home or /. Tried reinstalling Arch using ext3 instead of ext4 but I still get the same error. I tried searching for a fix on the forums already but couldn't find one that worked for me.
Misc Info:
- Using VirtualBox 3.1.2
- Using 2009.08 netinstall iso
Last edited by NightKev (2010-02-17 05:15:11)

I don't know how you would do so in VB, but on my desktop I used an Arch LiveCD to reinstall GRUB in order to get /root and the kernel image working from the /boot directory. I entered the command "grub" as root in a terminal to open the grub prompt "grub>" then I entered "find /boot/grub/stage1" and received back" (hd1,1)" which is where my root partition was located. I then entered "root (hd1,1)" and then "setup (hd0)" and then "quit". It installed GRUB to the MBR. I don't know if that's helpful in your case though, but if GRUB is installed it could be.

HDD disk checking failed

Hello everyone
I have a HP MINI 110105TU ,today while booting up it suddenly showed disk error and further process was terminated just after the HP logon screen so tired with CTRL+ALT+DEL and restarted but still the same so while I tried to format my HDD it won't showed up while selecting the drive to install the OS and after a self diagnostic check at BIOS it failed with a number 7 written before failed.Even sometimes AMI screen pops up and check the HDD and say " capable status bad backup and replace"
My warranty has expired is there anyway I can restore or reset my HDD with any OS windows 7/xp ? Any how I can manage to fix this up ?
Thanks in advance.

I haven't seen a warning or error message with that exact wording on an HP system. Did you get that message before booting into Windows or after booting into Windows? It sounds like the imminent failure warning. If you are getting the imminent failure warning, it doesn't necessarily mean it is going to fail right away or is currently failed but it does mean that keeping a regular backup should be considered. I have a notebook that received the imminent failure warning error message about four years ago and it is still working today.
In any case, I am glad it is currently working for you. Thanks for updating the community.
↙-----------How do I give Kudos?| How do I mark a post as Solved? ----------------↓

[SOLVED] Live USB fail to boot

Booting Arch netinstall and core from a USB fails on waht appears to be "booting the kernel"
After that the screen is flood with what looks like a dump.
The last 5 lines are something like (i quickly copied them down) and each line is preceded by a bunch of numbers:
do_one_initcall +0x35/0x170
? quick_tc86c001_idet +0x22/0x22
kernel_init +0xae/0x13a
? start_kernel +0x35d/0x35d
kernel_thread_helper +0x6/0x10
_ *blinking*
It hangs there and doesn't go away until I reset the machine
iso was torrented but I did a md5 check anyway and then created it using Universal USB installer. It works fine on my laptop.
Hardware
Mother board: Gigabyte GA-Z77-D3H
BIOS: BIOS Date: 02/21/12 15:12:36 Ver: 04.06.05
Processor: Intel(R) Core(TM) i5-2500K CPU @ 3.30GHz (4 CPUs), ~5.9GHz
Card name: NVIDIA GeForce GTX 560 Ti
NIC:Atheros AR8151 PCI-E Gigabit Ethernet Controller (NDIS 6.20)
Last edited by glethro (2012-06-17 03:23:54)

glethro wrote:I will leave this as solved as the kernel panic is no longer happening.. But archbot doesn't seem to work either. When in the configure step it shows a fstab file with an entry only for tmp. I booted this and it created the entire file system as read only. I reinstalled and used my own fstab file and was still left with a read-only system.
I successfully installed archlinux using archboot... concerning your fstab issue, I just haven't look this file in the configure step and everything worked fine... did you try editing this file manually without using the archboot installer ?

[SOLVED] gdm randomly fails on boot

Hello everybody,
I'm new to arch and it took me some time to get everything going, but now it works almost without issues. One not really critical, but very annoying thing is the following:
Sometimes when booting the system (pure systemd setup), gdm will not start (i. e. no graphical login appears). Instead, I'm directed to tty1, have to log in and do systemctl stop/start gdm.service. I have absolutely no idea why it is working sometimes and sometimes not - it seems like a random phenomenon... Here are the Xorg.log files of the situation when everything's working and when it's not:
working: http://pastie.org/private/szwlmvl8pcbcaoe0xurba
failing: http://pastie.org/private/webtcyiyktdwkeke8rb9kq
The output is not very conclusive, in my opinion. What other logfiles could be helpful?
Thanks for your help in advance!
Last edited by michaels (2012-10-24 20:47:19)

1) to push this one a little...
2) to give some more information: Checking the output of journalctl thoroughly, I found out that in the not-working case the gdm error messages (GDM display: display lasted xxx seconds / maximum number of X display failures reached) appear between messages from the kernel. Those indicate that the system is still busy loading kernel modules (device drivers for sound and chipset, in particular). Maybe some modules which are needed for the X server to run properly aren't loaded when systemd attempts to start gdm? Then, how to apply a timeout or, even better, a proper dependency to gdm.service unit?
journal failing: http://pastie.org/private/0k6fjkoievd7k90ytnqdq
journal working (truncated after gdm started successfully): http://pastie.org/private/orbvisc9hbjgmosxplmtra
I also tried to upgrade gdm from [testing] with all its dependencies, but this does not work at all.

[SOLVED] Disk check failed at boot.

Similar Messages

Maybe you are looking for