After I installed Linux OS(for example:SuSE10,redhat5),the [root] parmeter of [kernel] in created grub.conf seems that sometimes it's defined to device name.sometimes it's defined to Label or sometimes UUID. So ,I want to know what is that relative to? Hard disk type or OS version or both?
View 1 RepliesI'm using 2 cloned disks with CentOs5.3 and I need to be able to control which one is booted. I can specify which disk in the BIOS but after stage 2 it is always running from disk 2. When I have puppy linux on one disk and CentOs on the other I can boot off of either as selected by the system BIOS so the BIOS is not the issue. I think it is how the root option is passed in the kernel command in the grub.conf.
kernel /vmlinuz-2.6.18-128.el5 ro root=/dev/VolGroup00/LogVol00
I think when the OS searches for the /dev/VolGroup00/LogVol00 share is locates 2 since the disks are clones and uses the last one found. On information I have found for the kernel command and the root option it appears CentOs uses it differently. CentOs uses a volume name as specified /dev/VolGroup00/LogVol00 instead of a partition designator /dev/hda2. Is there a different way to specify /dev/VolGroup00/LogVol00 in CentOS for the root option for the kernel command of grub.conf?
I am unable to find any ldap.conf parameter or pam.d/system-auth setting from where i can restrict the LDAP users having uidNumber less than a particular number, say 500 to login into the system.I am using OpenLDAP server and tried pam_max_uid 500 in ldap.conf but it didn't work.
View 2 Replies View RelatedI've installed Fedora 10 on the third partition of an external HDD. It has with the following partitions:
(hd0,0) - GRUB bootloader files [PRIMARY]
(hd0,1) - Chainload LILO for another Linux [PRIMARY]
(hd0,2) - Fedora 10, no LVM or Swap (labeled F10) [PRIMARY]
I'm trying to boot Fedora 10 using the following grub.conf:
[Code]....
I am trying to edit my grub.conf file. I am logged in as root. It says it is a read only file. I have tried to set permission with chmod 777 and also tried through GUI. Using VI it says it's a read only file. Using nano it will not write either. I have two choices on boot up. I want to automatically go to second automatically. First at the moment is CentOS-4 i386 (2.6.9-55.ELsmp) and second is CentOS-4 i386 (2.6.9-55.EL).
View 9 Replies View RelatedI am trying to do a fsck on my ext3 partition, but so far failed to let the system come up in single user mode and having the partition mounted read only. It says in the kernel parameter that it is read only (RO) but still mounts it RW. A remount with mount -o remount,ro does not work, since / is always busy. what to do to get a fsck done? I don't want to boot into a rescue system, this should be possible on a running system (like Windows does it, when rebooting)
View 1 Replies View RelatedI am using grub of version 2, and current resolution vga=795 (probably). X runs at 1680x1050. So what I would like to know is, how can I count the right VGA parameter number for grub, to use another resolution?
View 11 Replies View RelatedI got the following modprobe scripts modprobe -k -q streams what does the -k parameter mean?. is it exist in older modprobe? I don't see -k parameter in recent modprobe.
View 1 Replies View RelatedSince certainly half a year I have to add the vga=0x317 parametere at the end of the root parameter in the menu.lst file after each upgrade of the kernel and also recently after upgrading from 11.1 to 11.3. Without this, the splash screen is not shown on my HP Pavilion laptop.
View 5 Replies View RelatedI've just installed Fedora (F13) for the first time, on a new HDD, to give myself a dual-boot system. So currently I have:
So, at the appropriate stage in the install menu, there is an option for where to install GRUB, and a drop-down to choose which drive is the primary BIOS boot drive.
However, in both cases, no other drive except my new sdc is visible. So, I can install GRUB to MBR of sdc, or to first sector of boot partition - but no option to put it to my primary boot drive MBR on sda.
Likewise, in the GRUB configuration page, if I go to Add another OS, the only option it gives me is my new Fedora install. It doesn't list the Vista OS on sda at all.
The result is that I can boot to either OS by changing the boot drive priority in BIOS.
I guess my question is this:
- is this expected behaviour from the installer, meaning that I'll need to configure GRUB manually somehow? (gulp ) or
- did I do something wrong in the install process? or
- is this some weird bug manifesting itself?
since i have installed the nvidia drivers i have lost the graphical boot and just had a bar at the bottom of the screen instead. i tried to get the graphical screen back by adding vga=795 to my /boot/grub/grub.conf but when i rebooted not only did i not get the graphical boot or the toolbar at bottom.
i got list of all the drivers and services it is starting with ok next to it. i have also since doing this lost the bit when restarting or shutting down getting the words restarting or shutting down and just get blank screen with flashing cursor. i removed the vga=795 and i still get the list of drivers/services loading.
how do i get the quiet option back. i have checked /boot/grub/grub.conf and it has the quiet in it.i have also tried running update-grub but get message command not found. i have attached the grub.conf file
I would like to modify the boot loader settings and triedo open the file grub.confHowever, it is said that the file could not be opened, as seen in the attachment.Tried to authenticate as 'root' before opening the file, but the problem still exist...
View 10 Replies View RelatedWhat formula does the installer use to decide the default sizes of /, swap, and home?
View 2 Replies View RelatedI am running Wheezy as my main OS in the first drive in my desktop. I use the 2nd drive for data. I am trying to add another OS to multiboot. When I ran grub-update in Wheezy, I am getting device letter for the root device instead of UUID in grub.cfg, in the os-prober section. Like this
Code: Select allsearch --no-floppy --fs-uuid --set=root 6ee49a8e-a619-49c7-9f66-51a5ca9a48cc
linux /boot/vmlinuz-316-x86_64 root=/dev/sdb3
initrd /boot/initramfs-316-x86_64.img
In the same file, UUID was used for the existing kernels.
Code: Select alllinux /boot/vmlinuz-3.2.0-4-686-pae root=UUID=c2eecf02-d427-4f2e-9fd0-9db61256cbac ro quiet
echo 'Loading initial ramdisk ...'
initrd /boot/initrd.img-3.2.0-4-686-pae
How can I get UUID instead of /dev/sdb3 for the 2nd OS?
I would like to create a 10.04 lucid install on a reiser4 partition, every guide I have seen either only puts a reiser4 directory, or uses grub legacy. These are what the steps I believe I would need to do to accomplish this.
* Partiton my drive with
/(to have ubuntu installed), /(to have ubuntu copied over)
* install kernel source, tools ect... to build a reiser4 enabled kernel
[code]....
On choosing the desired partition, where I wish to install Ubuntu, screen asks to choose the "File System" from the drop-down menu.How to decide on which one to choose from?What's the implication of choosing EXT4 over EXT3?**Point= Iam now fed up with 10.04 release since it is crippled with sporadic issues like --"Shaking Screen on Desktop load" & an abrupt "Screen Blackout"..Now I wish to roll-back to 9.04 again, the ONLY release of Ubuntu that worked "Perfectly" for me without posing any nuisance
View 9 Replies View RelatedIf I boot on a live-CD, then enter in a terminal the following commands:
sudo mount /dev/sda1 /mnt
sudo grub-install --root-directory=/mnt /dev/sda
sudo umount /mnt
..does it install Grub-pc in /dev/sda1 ? even if Grub was already installed in /dev/sda1 ? Furthermore, are the 3 above commands equivalent to the below ones ?
sudo mount /dev/sda1 /mnt
sudo mount --bind /dev /mnt/dev
sudo mount --bind /sys /mnt/sys[code].....
I just updated my server from Ubuntu 8.04 to 10.04 and now it cannot go past grub, at boot time, it would "give up waiting for root device", asking me to check whether I gave the right "root=..." or if I should increase the "rootdelay=..." in the command line argument and end up with the initramfs.
The machine is a Dell Poweredge 2900 with a HW RAID controller (I hope that should not matter, but just in case...). I tried to follow the instructions there to make sure grub is setup correctly, but without any luck.
Below is the output from the bootinfoscript (while running on the LiveCD). Anybody has any idea what can be the problem or what I could do to debug this ? I am running out of ideas.
[Code]...
I just recently installed a kernel, everything works fine after reboot except. When I use nano -w /boot/grub/grub.conf I get /boot/grub/grub.conf: No such file or directoryIs there something i have to do after installing a new kernel in Gentoo Linux.I can't access my /boot all that appears there is a symlink to /boot How can i see my kernels located in /boot.
View 3 Replies View RelatedI'm trying to manually boot (from the GRUB console) into a system set up as follows: crypt partition -> LVM -> root LV, and I'm having some trouble figuring out how to do this from the GRUB console.
I have successfully manually booted a system which is set up as just LVM -> VG -> root LV. All I have to do is load the LVM module. In GRUB, that partition shows up as (hd0,gpt5). Once I load the GRUB LVM module, I can see the logical volume within the LVM as well. (My volume group name is "caesar", and the single logical volume is named "root".)
Code: Select allgrub> ls
... (hd0,gpt5) ...
grub> insmod lvm
grub> ls
... (lvm/caesar-root) ...
It's fairly simple to manually boot:
Code: Select allgrub> set root=(lvm/caesar-root)
grub> linux /vmlinuz root=/dev/mapper/caesar-root
grub> initrd /initrd.img
grub> boot
Where I am having difficulty is in trying to insert crypt before LVM. I can set up such a scheme, and put a minimal installation on it, without issues. It's booting into it upon reboot that I can't figure out. Once I load the GRUB crypto, cryptodisk and luks modules, I can mount the crypto partition:
Code: Select allgrub> ls
... (hd0,gpt5) ...
grub> insmod crypto
grub> insmod cryptodisk
grub> insmod luks
grub> cryptomount (hd0,gpt5)
Attempting to decrypt master key...
Enter passphrase for hd0,gpt5 (<long hex string here>): <type my password>
Slot 0 opened
grub> ls
... (crypto0) ...
At this point, GRUB sees the crypto partition as (crypto0). But the GRUB LVM module doesn't see "inside" of the crypto partition, so I don't see the root logical volume within the LVM listed; all I see is (crypto0).
Code: Select allgrub> insmod lvm
grub> ls
... (crypt0) ...
Setting it as root doesn't work:
Code: Select allgrub> set root=(crypto0)
grub> ls /
error: disk `crypto0' not found.
So, How do I get GRUB to "see" LVM inside the crypto partition?
As recommended, I'm creating a new thread for my configuring GRUB problems commented first hereWe are setting up a new version of a custom system, we are migrating to Ubuntu Karmic from another distribution (Slackware). Besides small differences between these systems (most of them from the most recent versions of software used by the latest Ubuntu, such as GRUB 2), it has been decided that the new system will run an union root partition using aufs and tempfs, basically, we are following the steps provided heree install the system to a new hard drive from an already running Ubuntu Karmic system, usingdebootstrap/chroot, we move the disk to another sytem, so we have to correct disk references, we are able to run this system and it behaves correctly the first time it boots, it bypasses the GRUB menu since there are no other systems detected. However, after halting the system and booting it, the GRUB menu appears with a new "recovery" option, we've managed to remove this recovery option usingGRUB_DISABLE_LINUX_RECOVERY=trueBut then, the GRUB menu appears again, this time with only one option to boot: our system installation. But when this GRUB menu appears, it has no default timeout and so it stays forever unless ENTER is pressed to boot into the selected entry.
The main problem is that we are unable to configure GRUB inside the new installation because it always returns this message:grub-probe error cannot find a device for /If we boot the system "normally" (mounting root to a normal partition), we are able to configure GRUB properly, but it does not behave the same when using the union file system as /We are only looking for a way to bypass the GRUB menu and boot our system, do you have any advice on how to properly configure the GRUB menu for our system
The problem after couple installations (10.10 --> 10.04 --> 10.10 --> 10.04-3) is that system goes to "busybox" after complaining about missing root device. I already have come to conclusion that this problem could be solved by telling the system that the root device is at sda1. However, I'm not able to start grub (by pressing "ESC") at boot before problems start. I'm able to start live-cd and I tried to install "over" the old one (same partitions without format, same username). No luck.
And in the busybox /proc/modules is empty for example. And the grub has worked with previous installations.
just installed ubuntu 10.10 on my external usb hdd from my 8gb flash drive doing this on a laptop, my primary hdd (internal) is running windows (230gb of 250gb used) so i got an external hdd (2tb) and I decided to install ubuntu on it
[Code]....
I am testing my crash recovery strategy for my linux system and I am having trouble with GRUB. I am basically restoring my backup (i.e. tar) unto a different hard drive, but I am having problems getting the machine to boot without me having to type the GRUB commands at the GRUB prompt that is presented when the machine boots up off the new hard drive. I have tried to restore the MBR in two ways (the 2nd one is the one that gets me to the GRUB prompt):
1. Get the MBR off the original drive and write it unto the new drive (all via dd), but that did not work at all: the machine hangs right away during boot up. It seems to hang right at the point where the BIOS tries to read the MBR.
Code:
On original drive:
# dd if=/dev/sda of=mbr+part.bin bs=512 count=1
On new drive (new drive is now in place of original drive):
# dd if=mbr+part.bin of=/dev/sda bs=1 count=446 conv=notrunc
2. By using the FEDORA rescue CD, I installed grub unto the new hard drive as follows:
Code:
# chroot /mnt/sysimage
# grub-install --root-directory=/boot hd0
reboot and remove FEDORA CD Using the 2nd option above, I get the GRUB> prompt during bootup. I can then boot into the system by issuing the commands that are in the menu.lst file, followed by the "boot" command. However, I would like for those commands to happen automatically, just like in the original configuration. It seems to me that GRUB is actually finding all its stage files because I doubt the GRUB program (the one displaying the prompt) fits entirely in the 446 bytes it has on the MBR. So, it must be loading its stage 2 (and stage 1.5??) files from my /boot partition. However, if GRUB is loading its stage files off the boot partition, why does it not load/read the menu.lst/grub.conf contained in the boot partition also?
Code:
# ls -l /boot
total 22888
-rw-r--r--. 1 root root 1274567 2009-05-27 16:39 System.map-2.6.29.4-167.fc11.i686.PAE
-rw-r--r-- 1 root root 1274538 2009-06-16 22:27 System.map-2.6.29.5-191.fc11.i686.PAE
[code]....
I am trying to edit my /etc/resolv.conf file while under root. After saving the changes and reboot my computer, file has not changed. I read a thread on chattr and lsattr on this fourm.(see link below) I ran in terminal lsattr /etc/resolv.conf and got the following results:-----------------e- /etc/resolv.confWhat does the dashes and e mean? I thought I would get ----ia------------ /etc/resolv.conf instead, as shown in the link. What am I doing wrong?
View 4 Replies View RelatedI am trying to fix missing grub.conf on RHEL5.I booted from installation media > entered Rescue Mode > issued following cmds:
chroot /mnt/sysimage
grub-install /dev/sda1
:I get a message that installation is finished with no error and a device map is created.
when i reboot (without installation media) i land up at grub>from grub> i did followingroot (hd0,0)setup (hd0)and got successful installation message.On rebooting I again get the grub> prompt
I have not dug into Ubuntu for almost a year now (Since Jaunty, really). I am trying to come to grips with Grub2, but have just now encountered it in Lucid. I am having a terrible time with the graphics chipset, and it may well be that Ubuntu cannot be used on this computer (an older laptop with the dreaded Intel 82845G graphics chip). There are a number of older bug reports that it is unsupported, but some success in more recent versions.
Anyway, one suggestion has been to add i915.nomodset=1 to the kernel boot line. Now, this was a cinch in Legacy Grub, but I have been reading Grub2 wikis and tutorials for two days now, and I know about the config files, but I cannot find anything which tells me specifically how to add a parameter to the kernel boot line.
i can't edit /etc/resolv.conf with root account (Ubuntu Server 8.02)
root@webserver:~# sudo vim /etc/resolv.conf
"/etc/resolv.conf"
"/etc/resolv.conf" E212: Can't open file for writing
root@webserver:~# ls -l /etc/resolv.conf
-rw-r--r-- 1 root root 287 2010-06-14 15:20 /etc/resolv.conf
I'm trying to install Oracle DB on OpenSuse (is it smart, because it's not certified for that OS?)..and I've set oracle parameters using oracle script, but when I'm runnign through oracle installation, kernel parameters check reports that parametersa are 'n/a', like oracle OS account cannot access those parameters..
View 1 Replies View RelatedWhat is the configuration issue in the other-than-Fedora-11 stanza below that prevents that OS from booting? That stanza is taken directly from the /boot/grub/menu.lst of that OS, whose root partition is on sda5. All I get upon choosing the menu entry is a blinking cursor and a steady HD light. obsessing over this for a couple of weeks, reading what I can find about grub configuration but without joy.
Here is /boot/grub/grub.conf:
# grub.conf generated by anaconda
#
# Note that you do not have to rerun grub after making changes to this file
# NOTICE: You do not have a /boot partition. This means that
# all kernel and initrd paths are relative to /, eg.
[Code]......