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.
Mike, seems like blogd keeps / from being remounted ro ?
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
So I set RC_BOOTLOG="no" and the machine booted without a hitch. Is there anything else you want me to try?
well that's disparaging to say the least ;) can you post your /etc/conf.d/rc here as an attachment please
Hopefully not disparaging (you guys do a great job!), but maybe a little depressing. ;) Here's my /etc/conf.d/rc file...
Created attachment 68349 [details] My rc file
Created attachment 78249 [details] My RC file
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):
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 ?
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.
> 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 ?
AFAICT, yep!
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.
I think we can close this one now.