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, 25 Aug 2015, Sachin Gupta wrote:
Thank you so much!!!
It worked.
On Tue, Aug 25, 2015 at 8:04 PM, Barry Brimer 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
Thank you so much!!!
It worked.
On Tue, Aug 25, 2015 at 8:04 PM, Barry Brimer 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
>>
>> O
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 wrote:
My grub.conf is as following.
title Linux Init Break
ke
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 wrote:
> My grub.conf is as following.
>>
>> title Linux Init Brea
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.
--On Friday, December 14, 2012 10:53 PM -0800 "James A. Peltier"
wrote:
> It's quite likely a software RAID card and when the OS was installed it
> only installed grub on one of the hard disks, the one that it thought was
> primary. I've seen this happen with quite a few software cards. Each
>
It's quite likely a software RAID card and when the OS was installed it only
installed grub on one of the hard disks, the one that it thought was primary.
I've seen this happen with quite a few software cards. Each time the OS booted
it would load a different hard disk as primary. If you can,
Jerry Geis wrote on Fri, 05 Mar 2010 08:02:19 -0500:
> I accidentally broke the link between
> /etc/grub.conf and /boot/grub/grub.conf
> So any changes to /etc/grub.conf were not reflected.
wait, wait, wait. /etc/grub.conf should be the symlink, not vice versa!
Kai
--
Get your web at Conactiv
Jerry Geis wrote:
> I have a grub.conf (below) with pci=nomsi, also /proc/cmdline and
> dmesg | more
> do not show the pci=nomsi.
>
> How can this be? there are no strange characters after quiet and
> before pci=nomsi.
> It was edited with vi.
>
> What can I do to get this parameter in my kernel
Jerry Geis wrote:
> I have a grub.conf (below) with pci=nomsi, also /proc/cmdline and dmesg
> | more
> do not show the pci=nomsi.
Have you tried booting up, and before GRUB goes on to boot,
trying to edit the command line? Then you'll see what GRUB
actually thinks it needs to do.
Mike
--
p="p=%
11 matches
Mail list logo
