Fresh install gets stuck in emergency.

[LRC1962]

I have been having major difficulties getting to desktop since upgrading to systemd. Some my fault, but the upgrade did not go well at all. So I have decided to do a fresh install. I used siduction-13.2.1-december-kde-i386-201401272132.iso. Livecd works fine. So I run installation I included where I wanted things like home, tmp, work and included a few other links that I have had setup in the past. Installation went fine. Check /media/ looked good. checked fstab. / was strange in that it had a uuid that blkid could not find at all.
So I tried to reboot into my fresh install fstab-generator errors came up with duplicate in fstab. 4 more partitions came up then things stopped for a long time. It then went into emergency mode.
fstab generated by fstab generator not install.

Code Select Expand

UUID=4c077c6d-cdd7-4471-ace2-1ac58c7c8666     /media/disk1part1    ext4         auto,users,rw,exec,relatime                   0    0   
UUID=40350e0e-978b-4f82-aa1e-cfff889e2ac7     /media/disk1part10   ext4         defaults,relatime,errors=remount-ro           0    2   
UUID=f244f469-1456-4fcb-ad3f-b8a3b3a985cd     none                 swap         sw                                            0    0   
UUID=83aeabe5-4a29-48a9-b492-e6ad82e5a5f2     /media/disk1part2    ext4         auto,users,rw,exec,relatime                   0    0   
UUID=5efcb006-7816-46f9-9af3-fd0c56d7fb00     /home                ext4         defaults,relatime,errors=remount-ro           0    2   
UUID=2fc15535-c998-46c1-a770-6e181c3ecab6     /media/disk1part4    ext4         defaults,relatime,errors=remount-ro           0    2   
UUID=8a7d09a2-485e-43cb-af34-49bd601e1497     /media/disk1part5    ext4         defaults,relatime,errors=remount-ro           0    2   
UUID=0cba73e4-8356-46b8-b955-b9f4c3a7fc4a     /media/disk1part6    ext4         defaults,relatime,errors=remount-ro           0    2   
UUID=5fa56e10-3e32-4f41-a4e0-46e88ff4cb78     /media/disk1part7    ext4         defaults,relatime,errors=remount-ro           0    2   
UUID=0133bc04-d9fc-4532-8e3d-2d383b22a06a     /media/disk1part8    ext4         defaults,relatime,errors=remount-ro           0    2   
UUID=8ff318fc-3b63-4d66-83a8-5838dc77387f     /media/disk1part9    ext4         defaults,relatime,errors=remount-ro           0    2   
UUID=2A6E-50BF                                /media/disk2part1    vfat         auto,users,rw,quiet,umask=000,shortname=lower 0    0   
UUID=92a7bfb7-432b-4ae0-881e-5b9da20ad166     /boot                ext4         defaults,relatime,errors=remount-ro           0    2   
UUID=fc783d4e-fdba-4779-8493-2c8c2713b0aa     /media/disk3part2    ext4         defaults,relatime,errors=remount-ro           0    2   
UUID=d1673abc-bb67-4cd9-be4a-dd2fc34dfab2     /media/disk3part3    ext4         auto,users,rw,exec,relatime                   0    0   
UUID=d1437690-5c28-4b44-a258-5182be8564a7     /Documents           ext4         defaults,relatime,errors=remount-ro           0    2   
UUID=c4383519-deda-4bc2-b434-ef376252d107     /media/disk3part5    ext4         auto,users,rw,exec,relatime                   0    0   
UUID=df2e8e60-1101-4ee2-a7bc-a3d3ab4909d5     /media/disk1part6    ext4         defaults,relatime,errors=remount-ro           0    2   
UUID=2631f629-9d5e-4132-bbe6-a07b39119771     none                 swap         sw                                            0    0   
UUID=fe5f506e-0748-43e6-97de-6eb07e5105c6     /media/disk2part1    ext4         defaults,relatime,errors=remount-ro           0    2   
UUID=53e591d5-faf2-4586-9586-904a227994b9     none                 swap         sw                                            0    0   
UUID=55c8a419-7b97-4f5f-84e8-464aa269543f     /                    ext4         defaults,relatime,errors=remount-ro           0    1   
UUID=EC88F8C188F88AFA                         /media/disk6part1    ntfs         auto,users,ro,dmask=0022,fmask=0133,nls=utf8  0    0   
UUID=98189168189145E2                         /media/disk6part2    ntfs         auto,users,ro,dmask=0022,fmask=0133,nls=utf8  0    0   
UUID=A482929482926A96                         /media/disk6part3    ntfs         auto,users,ro,dmask=0022,fmask=0133,nls=utf8  0    0

What really concerns me is that fstab got entirely changed by fstab-generator and media directory has an entirely different collection in it. How am I supposed to setup links like for home, if fstab-generator does things like that?
I do nt not know what in the world is going on with this new systmd, because I have done several fresh installs in the past and never had this kind of trouble.
I do know you like seeing logs. If you could tell me what you want and where to find them I will get them for you. If I need to generate them while in emergency mode please give instructions how as I have no clue.

[mylo]

Indeed systemd seems being in the grow-up phase in the moment. However I am sure that it is the better system (even not knowing what it does or influences all).

The experts on siduction decided for it and I assume we can trust their decision as it is for the future.

[dibl]

/ was strange in that it had a uuid that blkid could not find at all.

I would not call that "strange", I would call it "broken".


I put code tags around your /etc/fstab file -- makes it readable.


Next, if you could post the output of this one, in code tags please, probably we can learn something:

Code Select Expand

blkid -c /dev/null -o list




Other questions that occur to me are:

1. Why 3 different swap partitions?
2. Is that vfat partition really mounted continously on that system?  Because if it is not, the "auto" option will prevent your system from booting.

BTW, I have had zero problems from systemd on 6 siduction systems, since it was adopted.  So I am skeptical when I see suspicions that systemd is causing some kind of problem.  It could be, but probably not.

[devil]

Systemd gets the blame for everything that goes wrong these days. And I agree, this is most probably not a systemd issue.


greetz
devil

[musca]

Hello LCR1962,

you could edit your /etc/fstab and comment out everything, what is not needed (prepend with a #).
(You can re-add theese partitions later.)

At first you only need /, /boot and /home.
I hope the situation will be easier to handle with less details.

Then look for logs since last boot with priority error:  "journalctl -b -p err".

greetings
musca

[GoinEasy9]

The same extended fstab was created for me when I set up siduction (13.2) on my UEFI box.  But, for me, it was a plus.  Using kdiskfree, I have access to every partition of the 4  distros I have installed, automatically.  Which has come in handy on numerous occasions.

It didn't occur to me that systemd might be involved, I just thought that the fstab that was created, came from the fstab that was setup by the live installation disk (syslinux on usb). 

I also share one swap between the distros, being careful not to format swap when a new distro is installed.  I also don't use sleep or hibernate, which would cause problems with a shared swap.

This is what my fstab looks like:

Code Select Expand

UUID=4CE1-F5CB                                /boot/efi            vfat         auto,users,rw,quiet,umask=000,shortname=lower 0    0   
UUID=82ae5e83-97da-44c0-add4-48bba3f6526c     /media/disk1part10   ext4         auto,users,rw,exec,relatime                   0    0   
UUID=26324e9e-47ca-4517-b629-1f490c88149a     /media/disk1part11   ext4         auto,users,rw,exec,relatime                   0    0   
UUID=86cba58e-4d98-428a-99d3-defe902c9dc0     /media/disk1part2    ext3         auto,users,rw,exec,relatime                   0    0   
UUID=7d9dab4f-5471-4490-8c8f-dec86e9e25cf     /home                ext4         defaults,relatime,errors=remount-ro           0    2   
UUID=e806e017-5d02-49eb-a70c-7ccb2a347a36     /                    ext4         defaults,relatime,errors=remount-ro           0    1   
UUID=6d1a687c-70b3-46e4-9a74-032c73655a44     none                 swap         sw                                            0    0   
UUID=f254aef7-2428-4283-87f1-d523a6f63baf     /media/disk1part6    ext4         auto,users,rw,exec,relatime                   0    0   
UUID=84648980-da2d-4d75-b9db-d3d3d4b7a32f     /media/disk1part7    ext4         auto,users,rw,exec,relatime                   0    0   
UUID=2229e55f-44b1-42b9-b381-42d06005f285     /media/disk1part8    ext4         auto,users,rw,exec,relatime                   0    0   
UUID=d377b13f-bffb-481f-a5da-510264d67b6b     /media/disk1part9    ext4         auto,users,rw,exec,relatime                   0    0   
UUID=B7A9-52B1                                /media/disk2part1    vfat         auto,users,rw,quiet,umask=000,shortname=lower 0    0   
UUID=3a0b504a-3449-437f-ba37-e57305a6bfa5     /media/disk2part2    ext4         auto,users,rw,exec,relatime                   0    0   
UUID=dd893b03-7026-450b-b432-633c649aaf15     /media/disk2part3    ext4         auto,users,rw,exec,relatime                   0    0   
UUID=86c46edb-42cb-46fb-8409-f0a72aa91649     /media/disk2part5    ext4         auto,users,rw,exec,relatime                   0    0   
UUID=c4ab9df4-efad-4280-96fa-31670cc0f044     /media/disk2part6    ext4         auto,users,rw,exec,relatime                   0    0
My 2 vfat partitions are for use as ESP's.  The first one is in use, the second one, on the SSD, is for future use. 

[dibl]

This is particularly strange, and suggests some manual intervention or change of devices at a point:

.
.
. 
UUID=2A6E-50BF                                /media/disk2part1    vfat         auto,users,rw,quiet,umask=000,shortname=lower 0    0   
.
.
.
UUID=fe5f506e-0748-43e6-97de-6eb07e5105c6    /media/disk2part1    ext4         defaults,relatime,errors=remount-ro           0    2   

Which is why I use /mnt/xxx for permanently mounted partitions, just to avoid such trouble.

[absolut]

if the live-iso was booted from a usb-flash-drive, it might be that this drive has been added to the fstab during install, and thus have led to the issue (?)

human error should be discarded last, though.

[LRC1962]

Figured it out. Was installing a 64bit version on an ssd and for some reason grub kept on picking it. Pulled it and things went better.
Did run into a snag where install setup created directories on root partition instead of links (although did create directories there also. Then ran into a snag where I had to change video drivers and also run 'export DISPLAY=0.0 command and now things I think are working right. Doing some last checking before doing much else.
What too many options you create for yourself can do for one.
Think I also have figured out what was causing part of my trouble with the ssd was the fsab had 2 duplicate entries and a general mess. Will fix that and a couple of other issues and I should be good to go there also (if I hit the jackpot that is). Thanks for your help.