Gentoo Websites Logo
Go to: Gentoo Home Documentation Forums Lists Bugs Planet Store Wiki Get Gentoo!
Bug 104539 - baselayout 1.12.0_pre7-r1 doesnt boot properly with RC_BOOTLOG=yes
Summary: baselayout 1.12.0_pre7-r1 doesnt boot properly with RC_BOOTLOG=yes
Status: RESOLVED FIXED
Alias: None
Product: Gentoo Linux
Classification: Unclassified
Component: [OLD] baselayout (show other bugs)
Hardware: x86 Linux
: High normal
Assignee: Gentoo's Team for Core System packages
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2005-09-01 21:06 UTC by Frank Lomax
Modified: 2007-01-10 12:48 UTC (History)
1 user (show)

See Also:
Package list:
Runtime testing required: ---


Attachments
My rc file (rc,5.64 KB, text/plain)
2005-09-13 05:19 UTC, Frank Lomax
Details
My RC file (rc,4.39 KB, text/plain)
2006-01-26 18:40 UTC, Paul Estes
Details

Note You need to log in before you can comment on or make changes to this bug.
Description Frank Lomax 2005-09-01 21:06:46 UTC
Over in http://forums.gentoo.org/viewtopic.php?p=2692577#2692577 uberlord helped
me upgrade to baselayout 1.12.0_pre7-r1 which fixed the reported problems with
/etc/resolv.conf and such.  However, this version of baselayout has a few
problem, and it was suggested I report them here.

First, the boot hangs after Remounting root filesystem read-only ...

I get the following output:

mount: / is busy
* Checking root filesystem ...
/dev/hda3 is mounted.

WARNING!!!  Running e2fsck on a mounted filesystem may cause
SEVERE filesystem damage

Do you really want to continue (y/n)?

The boot hangs here indefinitely, so I hit 'n' to continue.

After the line "Setting system clock to hardware clock" I get the error message

blogd: no process killed

After that, the boot finishes and the system works fine.

Reproducible: Always
Steps to Reproduce:
1. ACCEPT_KEYWORDS=~x86 emerge baselayout
2. reboot
3.
Comment 1 Martin Schlemmer (RETIRED) gentoo-dev 2005-09-02 03:50:29 UTC
Mike, seems like blogd keeps / from being remounted ro ?
Comment 2 SpanKY gentoo-dev 2005-09-09 22:54:35 UTC
doubtful ... especially since i use it on a bunch of machines w/out any issues ...

afaik blogd works like this:
- start early and fiddle around with /dev
- once / is ready (meaning all critical services are started), flush stored
buffer to log file
- once everything else has been done in the boot runlevel, tell blogd to shutdown

but an easy test would be for Frank to set RC_BOOTLOG to 'no' in /etc/conf.d/rc
and reboot
Comment 3 Frank Lomax 2005-09-12 18:40:41 UTC
So I set RC_BOOTLOG="no" and the machine booted without a hitch.  Is there
anything else you want me to try?
Comment 4 SpanKY gentoo-dev 2005-09-12 19:04:42 UTC
well that's disparaging to say the least ;)

can you post your /etc/conf.d/rc here as an attachment please
Comment 5 Frank Lomax 2005-09-13 05:19:12 UTC
Hopefully not disparaging (you guys do a great job!), but maybe a little
depressing. ;)

Here's my /etc/conf.d/rc file...
Comment 6 Frank Lomax 2005-09-13 05:19:41 UTC
Created attachment 68349 [details]
My rc file
Comment 7 Paul Estes 2006-01-26 18:40:27 UTC
Created attachment 78249 [details]
My RC file
Comment 8 Paul Estes 2006-01-26 18:40:46 UTC
I just encountered the same issue today. During boot, it logged:

 * Remounting root filesystem read-only ...
mount: / is busy
  [ !! ] 
 * Checking root filesystem ...
Reiserfs super block in block 16 on 0x902 of format 3.6 with standard journal
Blocks (total/free): 25001136/15085063 by 4096 bytes
Filesystem is NOT clean
Partition /dev/md2 is mounted with write permissions, cannot check it
 * Filesystem couldn't be fixed :( 
  [ !! ]
Give root password for maintenance
(or type Control-D to continue):


lsof showed that /var/log/boot.msg was open. I changed my /etc/conf.d/rc to RC_BOOTLOG="no" and the problem went away.

Here is my /etc/conf.d/rc (after I changed it, of course):
Comment 9 SpanKY gentoo-dev 2006-01-26 19:03:01 UTC
the question is, *why* is your / in readwrite mode ?  it shouldnt be

what do you guys have for your / filesystem ?  are you using initrd or lvm or raid or something else ?
Comment 10 Frank Lomax 2006-01-27 05:36:10 UTC
I'm using initrd, but I've since been following the ~x86 baselayout updates and as I'm now on 1.12.0_pre15-r1 I don't have this problem anymore.
Comment 11 SpanKY gentoo-dev 2006-01-27 05:49:07 UTC
> I'm using initrd, but I've since been following the ~x86 baselayout updates and
> as I'm now on 1.12.0_pre15-r1 I don't have this problem anymore.

so the only thing you did was upgrade baselayout and it started working ?
Comment 12 Frank Lomax 2006-01-27 09:18:55 UTC
AFAICT, yep!
Comment 13 Peter Tillotson 2006-04-20 07:46:28 UTC
I had the exact same problem - I believed the problem in my case was that  /var/log is on the root partition. I was going to ask for the option to be documented a little further with a warning. 

Comment 14 Roy Marples (RETIRED) gentoo-dev 2007-01-10 12:48:48 UTC
I think we can close this one now.