| 1 |
On Thu, Feb 12, 2009 at 11:52:20AM -0500, John covici wrote: |
| 2 |
> on Thursday 02/12/2009 Joost Roeleveld(joost@××××××××.org) wrote |
| 3 |
> > On Thu, February 12, 2009 3:21 pm, Momesso Andrea wrote: |
| 4 |
> > > On Thu, Feb 12, 2009 at 02:44:15PM +0100, Joost Roeleveld wrote: |
| 5 |
> > >> On Thu, February 12, 2009 2:26 pm, John covici wrote: |
| 6 |
> > >> > on Thursday 02/12/2009 Joost Roeleveld(joost@××××××××.org) wrote |
| 7 |
> > >> > > On Thu, February 12, 2009 2:05 pm, John covici wrote: |
| 8 |
> > >> > > > on Thursday 02/12/2009 Joost Roeleveld(joost@××××××××.org) wrote |
| 9 |
> > >> > > > > On Thu, February 12, 2009 10:52 am, John covici wrote: |
| 10 |
> > >> > > > > > Hi. I just upgraded a gentoo system from about August 2008 |
| 11 |
> > >> to |
| 12 |
> > >> > > > current |
| 13 |
> > >> > > > > > -- including updating baselayout and openrt and now when I |
| 14 |
> > >> boot |
| 15 |
> > >> > I |
| 16 |
> > >> > > > get |
| 17 |
> > >> > > > > > a series of messages quite early in the boot modprobe: fatal |
| 18 |
> > >> > /sys is |
| 19 |
> > >> > > > > > not mounted. Eventually it does boot and all seems to work |
| 20 |
> > >> with |
| 21 |
> > >> > the |
| 22 |
> > >> > > > > > exception of the script for my hsfmodem, but I am curious as |
| 23 |
> > >> to |
| 24 |
> > >> > what |
| 25 |
> > >> > > > > > those message mean and if there is a way to fix them. |
| 26 |
> > >> > > > > > |
| 27 |
> > >> > > > > > Any assistance would be appreciated. |
| 28 |
> > >> > > > > |
| 29 |
> > >> > > > > Did you include sysfs support to your kernel and do you have a |
| 30 |
> > >> > > > directory |
| 31 |
> > >> > > > > '/sys'? (SYSFS) |
| 32 |
> > >> > > > > This can be found in: File systems / Pseudo filesystems in the |
| 33 |
> > >> > kernel |
| 34 |
> > >> > > > > configuration. |
| 35 |
> > >> > > > > |
| 36 |
> > >> > > > > The '/sys' filesystem is as important as '/proc' these days. |
| 37 |
> > >> > > > |
| 38 |
> > >> > > > The plot thickens -- by the time I log in after booting, /sys is |
| 39 |
> > >> > > > mounted with the correct file system. Still very strange. |
| 40 |
> > >> > > |
| 41 |
> > >> > > Hmm... so, something does solve the problem you are seeing at the |
| 42 |
> > >> > > beginning later on. |
| 43 |
> > >> > > Did you update all the configuration files (including the ones in |
| 44 |
> > >> > > /etc/init.d/.. )? |
| 45 |
> > >> > > It could be that something there is not set correctly. |
| 46 |
> > >> > > |
| 47 |
> > >> > > For now, I am assuming the issue is in the boot-sequence/runlevel. |
| 48 |
> > >> > > |
| 49 |
> > >> > > Can you check which services are in your boot-runlevel? |
| 50 |
> > >> > > I have: |
| 51 |
> > >> > > bootmisc, checkfs, checkroot, clock, consolefone, hostname, |
| 52 |
> > >> keymaps, |
| 53 |
> > >> > > localmount, modules, net.lo rmnologin and urandom. |
| 54 |
> > >> > > Think these are the default ones. |
| 55 |
> > >> > > |
| 56 |
> > >> > > Do you use an initrd? If yes, did you update this as well? |
| 57 |
> > >> > |
| 58 |
> > >> > I regenerated the initrd, but I am still using 2.6.20 kernel which I |
| 59 |
> > >> > will update soon, but I wonder if this is the problem -- something |
| 60 |
> > >> > wrong with the initrd, but regenerating did not fix it. In my boot |
| 61 |
> > >> > level I have |
| 62 |
> > >> > bootmisc@ |
| 63 |
> > >> > consolefont@ |
| 64 |
> > >> > device-mapper@ |
| 65 |
> > >> > fsck@ |
| 66 |
> > >> > hibernate-cleanup@ |
| 67 |
> > >> > hostname@ |
| 68 |
> > >> > hwclock@ |
| 69 |
> > >> > keymaps@ |
| 70 |
> > >> > localmount@ |
| 71 |
> > >> > modules@ |
| 72 |
> > >> > mtab@ |
| 73 |
> > >> > net.lo@ |
| 74 |
> > >> > procfs@ |
| 75 |
> > >> > root@ |
| 76 |
> > >> > swap@ |
| 77 |
> > >> > sysctl@ |
| 78 |
> > >> > termencoding@ |
| 79 |
> > >> > urandom@ |
| 80 |
> > >> > in my sysinit I have |
| 81 |
> > >> > devfs@ |
| 82 |
> > >> > dmesg@ |
| 83 |
> > >> > udev@ |
| 84 |
> > >> |
| 85 |
> > >> Do you have "device-mapper" in your boot-level? |
| 86 |
> > >> In that case, you might want to check which init-script mounts the |
| 87 |
> > >> '/sys' |
| 88 |
> > >> filesystem as this script requires the /sys filesystem to be mounted. |
| 89 |
> > >> |
| 90 |
> > >> May I ask why you have this added as I don't use it with my LVM drives. |
| 91 |
> > >> |
| 92 |
> > > |
| 93 |
> > > http://bugs.gentoo.org/show_bug.cgi?id=258442 |
| 94 |
> > |
| 95 |
> > Helpful, but only if OP is using module-init-tools 3.6, which is currently |
| 96 |
> > in unstable for all archs. |
| 97 |
> > |
| 98 |
> > John, can you please confirm which 'module-init-tools' version you are using? |
| 99 |
> Its 3.6 -- I have gone to complete unstable on that box. |
| 100 |
> |
| 101 |
|
| 102 |
Until the bug gets fixed, mask current version, do the downgrade, and |
| 103 |
reboot. |
| 104 |
|
| 105 |
The same problem happened this morning to a guy in #gentoo-it on |
| 106 |
freenode, and was solved this way. |
| 107 |
|
| 108 |
======= |
| 109 |
TopperH |
| 110 |
======= |
Archives