One more question. I am using following grub.conf. title Linux Init Break kernel /vmlinuz root=/dev/sda6 init=/bin/sh initrd /initrd.gz Control comes to the shell command prompt. But the filesystem I am seeing is not initrd filesystem. Is it possible to access initrd file system ? Thanks Sachin On Tue, Aug 25, 2015 at 8:24 PM, Barry Brimer <lists at brimer.org> wrote: > > > On Tue, 25 Aug 2015, Sachin Gupta wrote: > > Thank you so much!!! >> It worked. >> >> On Tue, Aug 25, 2015 at 8:04 PM, Barry Brimer <lists at brimer.org> wrote: >> >> Thanks for reply. >>> >>>> >>>> I replaced break=y with init=/bin/sh. >>>> In that case case system just hangs with the following message. >>>> "Freeing unused kernel memory : 400k freed". >>>> >>>> Thanks!! >>>> Sachin >>>> >>>> On Tue, Aug 25, 2015 at 7:16 PM, Barry Brimer <lists at brimer.org> wrote: >>>> >>>> My grub.conf is as following. >>>> >>>>> >>>>> >>>>>> title Linux Init Break >>>>>> kernel /vmlinuz root=/dev/sda6 ro rootwait break=y >>>>>> initrd /initrd.gz >>>>>> >>>>>> What I expect is by adding *break=y* to cmdline, >>>>>> init will pause early in the boot process and launch an >>>>>> interactive sh shell which can be used for troubleshooting purposes. >>>>>> >>>>>> But kernel is disregarding break=y. And it loads up without >>>>>> launching sh shell. >>>>>> >>>>>> Is it the right way to launch interactive shell ? >>>>>> >>>>>> >>>>>> I would remove the break=y and replace it with init=/bin/sh >>>>> >>>>> What version of CentOS are you running? >>>>> >>>>> >>>> You didn't mention what version of CentOS you are running. I also >>> realized >>> that this kernel line looks a bit non-standard. What is the purpose of >>> the >>> rootwait parameter in this context? Have you tried without it but >>> including >>> init=/bin/sh ? >>> >> > You're welcome. Glad I could help. > > Barry > > _______________________________________________ > CentOS mailing list > CentOS at centos.org > http://lists.centos.org/mailman/listinfo/centos >