tmpfs file system causes SLES11 network to not come up when booting
This document (7006027) is provided subject to the disclaimer at the end of this document.
The problem can occur on:
- Xen para-virtualized
- VMware (Workstation, Server, ESX)
- Physical servers
The boot.msg file shows that the setup of eth0 times out:
Setting up (localfs) network interfaces:lo
lo IP address: 127.0.0.1/8
IP address: 127.0.0.2/8
doneWaiting for mandatory devices: eth0 __NSC__
29 28 27 26 24 23 22 21 20 19 17 16 15 14 13 12 10 9 8 7 6 5 4 2 1 0
eth0 device: Broadcom Corporation NetXtreme BCM5704 Gigabit Ethernet
eth0 is down
failed eth0 interface could not be set up until now
failedSetting up service (localfs) network . . . . . . . . . .failed
A change was made beginning with SLES11 SP1 whereas the cause of this issue was removed.
- remove the following line from /etc/fstab
shmfs /dev/shm tmpfs size=240m
- add the following line to /etc/fstab
udev /dev tmpfs noauto,size=240m 0 0
- The 240m size is just included as an example. The default size for tmpfs is 50% of RAM and can be modified (although leaving the default is suggested if no specific application requirements are identified).
udev mnt is visible in the output of "cat /proc/mounts" and is mounted
by the /etc/init.d/boot "System Boot Control" script (boot log mesgs are
"Mounting tmpfs at /dev" and/or "Remounting tmpfs at /dev" [applying
the size parameter]) already before any /etc/init.d/boot.* scripts are
This Support Knowledgebase provides a valuable tool for SUSE customers and parties interested in our products and solutions to acquire information, ideas and learn from one another. Materials are provided for informational, personal or non-commercial use within your organization and are presented "AS IS" WITHOUT WARRANTY OF ANY KIND.
- Document ID:7006027
- Creation Date: 18-May-2010
- Modified Date:03-Mar-2020
- SUSE Linux Enterprise Server
For questions or concerns with the SUSE Knowledgebase please contact: email@example.com