i use a 3rd party boot mgr.i installed jessie over etch on my old computer & only choice i saw for grub was sda & sdb where i wanted to install on sdb9.i tried installing it from my wheezy partition & it did but i ended up with 2 boots to wheezy.so i went back to etch.
my question is how to get grub on sdb9 like it was on etch.is there a trick or did i miss a prompt? on another note, that bug where the format hangs if you try & install over an old system is a little irritating. can't believe it hasn't been fixed.
I want to install grub on the ubuntu root partition because I have another boot loader (boot-us). But when I reach : device for boot loader installation and set the device to the root partition (/dev/sda3) the OK button is not highlighted, I can use the windows partitions but not ubuntu root partition, what goes wrong?
Because I am using one of the new WD disks I am trying to aling my root partition with the real sectors, as described here:[URL]31So I copied all files to a temp location, deleted my partition (/dev/sda3), recreated it a few cylinders later (same name) and copied the files to the newly created partition. But now when I try to boot, I get my old grub menu but after selecting my kernel version it hangs
3 partitions (in order): Windows 7, CentOS and shared data partition.
I need to increase the size of the Windows 7 partition (c:windowswinsxs seems to be something not easily remedied).
GParted didn't work in moving things around (bad sector) so I wiped out its partition (# 2 out of 3) and I was able to increase the size of the Windows 7 partition (I can reinstall CentOS easily and not much work lost).
Except ... no more grub menu (unsurprising). This incantation does allow me to boot into Windows 7.
Is there any way of rebuilding the grub menu short of reinstalling CentOS (5.5)?
So I need to become the root user in order to edit a grub file in a seperate partition, so I can get back into this partition. How can I become and stay as root user in the desktop environment? (I know you shouldn't do this, but I need it.)
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
With the release of CentOS 5.5 ext4 is considered stable in this distribution so I decided to migrate to it. Luckily I started from migrating fresh server with CentOS 5.5 using some instruction I found on the internet. I think I shouldn�t say, that I screwed the whole thing up ;) After about 6 hours cursing, kicking, and crying I solved the task and figured the correct sequence of actions. The small problem with migrating root partition is that you can�t unmount it BTW.
During migration task, I found, that CentOS 5.5 rescue mode is somewhat broken a little in terms of ext4 support. It can mount ext4 partitions successfully. But its e2fsprogs package (tune2fs, e2fsck etc.) doesnt see ext4 partitions and say, that superblock is corrupted on a partition once is converted to ext4 (at least it did it for me. May be I should force filesystem type with -t ext4 switch?). Keep in mind, that if you screw your system up too badly, you will not be able to run tune2fs and e2fsck on it from rescue modeBut you will still able to mount it if it is not corrupted badly. In all below examples,Boot your system normally and login as root. Upgrade kernel if you wish (I usually use yum upgrade to upgrade all on new machines). Then upgrade/install some other packages
I have just configure RAID 1 on my IBM X3400 Server in CENTOS 5 ..Partition information is md0 boot , md1 swap and md2 is root ....but after resyn when i run cat /proc/mdstat I realize that md0 and md1 is ok and present with [UU] status. BUT the md2 is showing on one [U_].. that means my root partition is not properly in RAID 1.. how can i make it active in both drive. Or i need to reinstall complete system again. Screen shot attached [URL]
I'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.
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?
It seemed that it would be simple enough: take the 'f' option in the expert menu of fdisk to put partitions in order after a gap had been created by a deleted partition and then make corresponding changes in /boot/grub/grub.conf because the root partition was shifted.
Well, it didn't work out that way. No matter what I try, I either see the error 15 at Stage1.5 or the error 28, which is even stranger (file does not fit into memory). All this before I even see a grub menu. It just does not get that far.
Does anyone want to take as stab at guessing what might have happened here and whether I have a chance at recovering without having to reinstall? I can provide concrete data, if anyone would be kind to give it a try. Hoping that this is a known problem and something can be guessed from what I stated here but I can be as specific as needed, just don't want to generate noise if there are no takers.
I am running Nagios on CentOS. Everything is working fine, all my clients status is ok. One thing which is confusing me is "Root Partition WARNING" on my own server which has Nagios installed. I think that these things are controlled by nrpe, which is installed in clients servers. what i want to know is how i manage my own server, in which config files i have to make changes?
I have finally been convinced to partition my 500GB hard drive from a two partition setup with root and swap to a three partition setup with root, swap, and home. I found a nice tutorial about how to do this, but here is my question:
A) How much space do I leave for the root partition and the home partition?
when I tried to install Fedora on my pc, I got this error message " Defined Root partition not created a / boot/efi partition. I am trying to install it on a seperate hd. My main one has windows xp pro, but I do not want to interfer with that at all?.
I initially installed SuSe11.2 with /tmp mounted on separate partition on another physical disk( there are two physical disks). Now I want to attach disk with existing SuSe11.2 to another motherboard so I would like that /tmp becomes part of the root partition. Will deleting /tmp mount point in /etc/fstab create automatically new /tmp from root at next startup, or something else has to be done to achieve, that in future, /tmp resides on root partition instead? In this way it would be much easier to move the disk with SuSe11.2 to another motherboard.
I am relatively new to Linux and Opensuse. I created the / root partition and now it is growing and maxing out. I have partitioner available to me but how do I change the partition size when the root partition is mounted. Do I login as root and then umount or modify fstab and restart and change from command line or do I format and reinstall everything? I have room to expand but not sure how to manage this?
I'm currently setting up a dell server with hardware raid 1 on sas 6r. i got 4 sas installed on the server and configured to raid 1 as stated below, array 1: slot 0 & 1
array 2: slot 2 & 3
during the installation, the installer detect the array 2 as sda and array 1 as sdb.. so i proceed with installation on array 2. after completed the installation, the first reboot lead me to a 'grub-rescue" prompt. by following the guide at url Mode, i've noticed that the boot folder has changed to (hd1,1), which i believe it has changed to sdb1. default root device shows that prefix=(hd0,1)/grub.
8.04 64bit LTS no gui loaded Only the root user can write to /tmp. I tried to create a cron job for a user and received an error
crontab -e no crontab file for ed - using an empty one /tmp/crontab.SCQ30O: Permission denied Creation of temporary crontab file failed - aborting
Then I tried a simple touch /tmp/test1 and it failed with a 'touch: cannot touch `/tmp/test1': Permission denied I tried the Windows fix and rebooted, no change. Only root can write to tmp. This may sound lame but... using ls /tmp show reversed video (highlighted blue on green) on the servers the the users have access to, just plain blue on the 'broke' one. I did a sudo chmod a+w /tmp but do not know if that was a smart thing to do or not...
After the fresh installation of openSUSE 11.4 x64 (Gnome 2.32.1) my NTFS drives were mounted automatically. However, I can only write those partitions as root. I' ve already tried everything I found on the internet, but none of those solutions worked and as a rookie, I haven't got any idea how to proceed. My original FSTAB looked like this:
I also installed ntfs-config and according to it my drives are supposed to be writeable (although that might refer to my root account). But none of the above steps made my NTFS partitions writeable for a non-root account. I restarted my system after each time I changed the content of FTSAB.
When I installed Ubuntu, I was asked to enter a user name and password. I chose one that would be a sort of "administrator alias" and gave it a strong password. This is my "su" name and password. That works fine for most things, such as installing software, etc.. Every so often, however, something comes up that can only be accessed by "root" and that is not me, even logged in with my "administrator alias" and password. This happened when I inserted a USB flash drive and tried to copy some files to it that I wished to transfer from my desktop my laptop. The only way I could do this was to format the flash drive. and then add my files to it.
This morning I inserted the flash drive and tried to add another file to it, using "copy" and "paste". Again I got "permission denied" and the owner of the flash drive, seen as "usb0", was again "root", and I could not change its permissions, because I am not "root". It also says the device is not listed in etc/fstab. I have read the Ubuntu paper on mounting USB drives, but I'm not sure that applies here. The drive seems to be mounted, but with the wrong owner.
This problem has also occurred with some software when I tried installing it. I usually give up and don't install it. This flash drive problem, however, is driving me crazy. I need to transfer those files. Is there something I'm missing? Despite installing and upgrading Ubuntu on 2 machines, I'm still pretty much a newbie, and if it involves using the terminal, I need step-by-step instructions,
I got ubuntu 10.04 lucid lynx along with windows (dual boot) and using Grub. On my computer, I have my C:/ (programs) and D:/ (data). I've never used my D:/ before that day that I've lost my windows partition on my grub menu. I usually use my D:/ with windows. The first time I used my D:/ to store data with linux, I lost my windows option in my grub menu. I'm not sure what I did wrong but I do want to restore my windows option in my grub menu.
After "fdisk -l",
I checked in /boot/grub and there is no menu.lst to modify. how I can get back my windows option in my grub menu ?
I having a problem getting my grub loader to see one of my hard drives. I added a drive, and my grub loader lost track of where everything was. I couldn't get my old linux (Red Hat 9) so I installed SuSe on my new hard drive. But I need my be able to boot from my old hard drive because it has apps that only run on the earlier version. From /proc/partitions the old hard drive is sdd
major minor #blocks name 8 0 976762584 sda 8 1 2104483 sda1 8 2 20972857 sda2