1 |
got both devtmpfs options on (that came up googling often). |
2 |
I did not have a run entry in fstab, so I put 1 in, I'll see if that helps. |
3 |
The only later kernel I have is 3.7.10-r1 which I did not notice (otherwise |
4 |
I would have upgraded first). |
5 |
I'll reboot with the new fstab and report back (not convenient to reboot |
6 |
now). |
7 |
If that doesn't help I'll upgrade the kernel too. |
8 |
|
9 |
|
10 |
On Tue, Apr 30, 2013 at 10:58 PM, Drake Donahue <donahue95@×××××××.net>wrote: |
11 |
|
12 |
> On Tue, 2013-04-30 at 18:30 +1000, Daiajo Tibdixious wrote: |
13 |
> > During the startup on 3.7.10 /run fails to mount with this error: |
14 |
> > mount: wrong fs type, bad option, bad superblock on tmpfs, missing |
15 |
> > codepage or helper program, or other error |
16 |
> > |
17 |
> > |
18 |
> > |
19 |
> > Googling shows many people getting this error, and its something to do |
20 |
> > with openrc and moving from /var/run to /run. |
21 |
> > |
22 |
> > |
23 |
> > What I can't understand is why I can boot 3.7.9 without any problems, |
24 |
> > while 3.7.10 bombs. I have DEVTMPFS enabled in the kernel. |
25 |
> > Obviously there is something else wrong with my 3.7.10 kernel but I |
26 |
> > just can't figure what. |
27 |
> > |
28 |
> > |
29 |
> > Is /run supposed to be a physical directory? I thought it was supposed |
30 |
> > to be in ram. I got |
31 |
> > lrwxrwxrwx 1 root root 4 Dec 5 14:13 /var/run -> /run |
32 |
> > drwxr-xr-x 11 root root 360 Apr 30 18:17 /run |
33 |
> > |
34 |
> > |
35 |
> > Before the last upgrade of openrc (to 0.11.8) my 3.7.10 kernel was |
36 |
> > working fine. |
37 |
> mounting devtmpfs at /dev has helped some victims, menuconfig: |
38 |
> Device Drivers ---> |
39 |
> Generic Driver Options ---> |
40 |
> (/sbin/hotplug) path to uevent helper |
41 |
> [*] Maintain a devtmpfs filesystem to mount at /dev |
42 |
> [*] Automount devtmpfs at /dev, after the kernel mounted the rootfs |
43 |
> |
44 |
> |
45 |
> |