On 30/04/2013 9:04 PM, Daiajo Tibdixious wrote:
got both devtmpfs options on (that came up googling often).
I did not have a run entry in fstab, so I put 1 in, I'll see if that
helps.
The only later kernel I have is 3.7.10-r1 which I did not notice
(otherwise I would have upgraded first).
I'll reboot with the new fstab and report back (not convenient to
reboot now).
If that doesn't help I'll upgrade the kernel too.
On Tue, Apr 30, 2013 at 10:58 PM, Drake Donahue <donahu...@comcast.net
<mailto:donahu...@comcast.net>> wrote:
On Tue, 2013-04-30 at 18:30 +1000, Daiajo Tibdixious wrote:
> During the startup on 3.7.10 /run fails to mount with this error:
> mount: wrong fs type, bad option, bad superblock on tmpfs, missing
> codepage or helper program, or other error
>
>
>
> Googling shows many people getting this error, and its something
to do
> with openrc and moving from /var/run to /run.
>
>
> What I can't understand is why I can boot 3.7.9 without any
problems,
> while 3.7.10 bombs. I have DEVTMPFS enabled in the kernel.
> Obviously there is something else wrong with my 3.7.10 kernel but I
> just can't figure what.
>
>
> Is /run supposed to be a physical directory? I thought it was
supposed
> to be in ram. I got
> lrwxrwxrwx 1 root root 4 Dec 5 14:13 /var/run -> /run
> drwxr-xr-x 11 root root 360 Apr 30 18:17 /run
>
>
> Before the last upgrade of openrc (to 0.11.8) my 3.7.10 kernel was
> working fine.
mounting devtmpfs at /dev has helped some victims, menuconfig:
Device Drivers --->
Generic Driver Options --->
(/sbin/hotplug) path to uevent helper
[*] Maintain a devtmpfs filesystem to mount at /dev
[*] Automount devtmpfs at /dev, after the kernel mounted the rootfs
why don't you provide your kernel.config, your fstab file, and your
grub.conf file and we'll see if we can figure it out?
