[SOLVED] Systemd-fstab-generator: Out of memory...

adramalech · 2013-10-06 18:07:07

Hello using multilib lib32-systemd 208-1 and systemd208-1... I have a problem where I will boot and it hangs at mounting drives:

systemd-fstab-generator[135]: Out of Memory.

systemd[1]: /usr/lib/systemd/system-generators/systemd-fstab-generator exited with exit status 1.

I have chrooted in and upgrade stuff and modified my fstab and grub config stuff a bit since I was getting the /root read only problem.. (changed to rw) and it works... However I cannot seem to find where this problem is coming from and the only thing that I can think is that systemd cannot parse /etc/fstab correctly.. My fstab has labels like: Label=/home, Label=/, Label=/var, Label=/boot, etc... it was fine till a couple days ago... Using kernel 3.11.3 x86_64...

Last edited by adramalech (2013-10-06 20:50:20)

WonderWoofy · 2013-10-06 18:40:01

The root of the filesystem and /root are not the same thing.

Also, do you seriously have forward slashes in the actual names of your filesystems? I cannot imagine that this is a good idea, though I cannot say that I have tried it either.

I think you need to provide more precise information. Giving generalizations like "I have chrooted in and upgrade stuff" doesn't really give any indication what you actually did. Nor can anyone tell if your fstab is formatted correctly from the information you have provided.

cfr · 2013-10-06 18:40:13

Post fstab.

adramalech · 2013-10-06 19:07:37

Okay so here is my fstab:

tmpfs        /dev/shm    tmpfs    defaults,noatime       0 0

none         /tmp          tmpfs    defaults,noatimenodev,nosuid,mode=1777  0 0

/dev/sdd2  none          swap     sw         0 0

proc         /proc          proc      nodev,noexec,nosuid   0 0


# /dev/sdc2 UUID=0cf15f7d-a6e0-4b4b-8ca0-e3fa32ca79f5
LABEL=/               /                      ext4      errors=remount-ro,defaults,rw,discard,noatime,data=ordered  0 1

# /dev/sdc1 UUID=22cee2cf-55fa-4721-b3da-68191c477643
LABEL=/boot        /boot                ext2       defaults    0 0

# /dev/sdc3  UUID=79bcca95-af9a-4f9f-99ab-78020a3960da
LABEL=/home     /home               ext4       errors=remount-ro,defaults,rw,noatime,discard,data=ordered  0 1

/dev/sdd3            /var                   ext4        errors=remount-ro,defaults,rw,relatime,data=ordered   0 2

LABEL=Storage  /media/Storage  ext4        errors=remount-ro,defaults,rw,relatime,data=ordered    0 2

***EDIT#1***
Storage is a WD 2TB Caviar green, same with /var and swap, /boot, /home, / are on an M4 128GB SSD, and the rest are just stuff put in tmpfs and proc like normal... Tried keeping the heavily read/write data off of the ssd to conservative with writes

I am wondering if I can not just update my damn Labels in fstab and through gparted and call it a day...

***EDIT#2***
Okay so I only went through and thought to update packages that needed updating since that might have fixed the problem... I saw an update for lib32-systemd 208-1 and some other non-essentials stuff so updated rebooted and still same problem I have used this fstab for a considerable amount of years using arch and then back using gentoo for a couple years with no problems... Wondering if now it is being picky with labels...

Last edited by adramalech (2013-10-06 19:19:49)

cfr · 2013-10-06 19:15:31

Please edit your post to use code tags as explained in the wiki.

You should delete the lines for /tmp /dev/shm and /proc. systemd etc. manages that stuff automagically.

Only / should end "0 1". /home, for example, should be "0 2".

Like WonderWoofy, I'm dubious about filesystem labels which include forward slashes. Even if they seem to work, it seems to be asking for trouble to use them.

remount-r0 is incorrect. It should be remount-ro.

I'm not sure if any of this will solve the problem but you should correct these things in any case. So try that and then see if you still get the error.

You could just replace the labels with uuid specifications for now so you don't have to worry about changing the actual labels for the moment.

EDIT:

adramalech wrote:

***EDIT#2***
Okay so I only went through and thought to update packages that needed updating since that might have fixed the problem... I saw an update for lib32-systemd 208-1 and some other non-essentials stuff so updated rebooted and still same problem...

Partial upgrades are not supported. Doing this is known to break stuff. You need to upgrade the system using pacman -Syu to make sure everything works together. Otherwise you are just trying for breakage.

Note: I'm not sure you meant you did a partial upgrade but just in case.

Last edited by cfr (2013-10-06 19:19:17)

adramalech · 2013-10-06 19:24:44

Ohh the error=remount-r0 was a typo...

I will update /home to use 0 2 ... I use to have home as 0 0 since it was an SSD partition... /tmp /proc and /dev/shm have been commented out...

Thanks so far for all the help... I will most likely have to go into a live usb iso fedora 19 image i have laying around and go into gparted and switch the labels and chroot in and fix the labels in fstab... Going to switch them to HOME ROOT BOOT VAR etc... and get rid of the slashes...

Could I regenerate the fstab with just using the UUID... I really like using the labels for organization because I always find it difficult to figure out what was what with a UUID label...

**EDIT#1**

Okay so nope didn't work... going to now next step change labels and modify fstab and reboot and see if that works..

Last edited by adramalech (2013-10-06 19:25:23)

WonderWoofy · 2013-10-06 19:39:37

As mentioned already, using labels is not the potential problem, it is what you have labelled your partitions that raise some concern. Cfr just suggested you use UUIDs to simply see if it is those labels that are causing you trouble. No one has indicated that you cannot use filesystem labels.

I'm not sure why you think you need to regenerate the fstab either. Just replace the filesystem labels with UUIDs and see if it works. If it does, great, you can change the labels to something sane and go back to that method. If not, then you can continue to try to debug.

adramalech · 2013-10-06 20:04:32

So I did change the labels... and now thanks to the livecd distro I used I got GPT instead of MBR stuff I need... so might be using gdisk to rewrite a protective mbr to the dang partition table to get it to work... I need to just modify the labels used in the fstab... I was going to use the uuid... but I just thought of this as I was typing... I could use the damn fdisk -f and copy and paste the UUID and use that for each partition and say f**k it... done...

adramalech · 2013-10-06 20:49:55

Okay success it boots now changed to UUID... and am not using labels any longer... Thanks for the help guys!!!

falconindy · 2013-10-06 22:31:23

This was a bug in systemd... please report it to a bug tracker next time rather than hacking around it.

http://cgit.freedesktop.org/systemd/sys … cb2bbc3cdb

Last edited by falconindy (2013-10-07 00:39:27)

Arch Linux

#1 2013-10-06 18:07:07

[SOLVED] Systemd-fstab-generator: Out of memory...

#2 2013-10-06 18:40:01

Re: [SOLVED] Systemd-fstab-generator: Out of memory...

#3 2013-10-06 18:40:13

Re: [SOLVED] Systemd-fstab-generator: Out of memory...

#4 2013-10-06 19:07:37

Re: [SOLVED] Systemd-fstab-generator: Out of memory...

#5 2013-10-06 19:15:31

Re: [SOLVED] Systemd-fstab-generator: Out of memory...

#6 2013-10-06 19:24:44

Re: [SOLVED] Systemd-fstab-generator: Out of memory...

#7 2013-10-06 19:39:37

Re: [SOLVED] Systemd-fstab-generator: Out of memory...

#8 2013-10-06 20:04:32

Re: [SOLVED] Systemd-fstab-generator: Out of memory...

#9 2013-10-06 20:49:55

Re: [SOLVED] Systemd-fstab-generator: Out of memory...

#10 2013-10-06 22:31:23

Re: [SOLVED] Systemd-fstab-generator: Out of memory...

Board footer