search for: rootnoverify

I installed C 6.0 in an empty partition. It functioned. Despite using the usually successful methods of booting into another operating system from C 5.7, I can't get into C 6.0 Tried:- title C6-0 (2.6.32-71.el6.x86_64) rootnoverify (hd0,6) chainloader +1 and root (hd0,6) kernel /boot/vmlinuz-2.6.32-71.el6.x86_64 ro root=UUID=67c62872-0c69-451c-8412-3c218c0d2cb0 rd_NO_LUKS rd_NO_LVM rd_NO_MD rd_NO_DM LANG=en_US.UTF-8 SYSFONT=latarcyrheb-sun16 KEYBOARDTYPE=pc KEYTABLE=uk initrd /boot/initramfs-2.6.32-71.el6.x86_64.img M...

Dear All Please be informed that I tried to install the "Real VMX" application on my Cent OS client . I setup the environment variables and build kernel . Then I add the following entry to my /boot/grub/menu.lst : title Real VMX rootnoverify (hd0,0) kernel -type=netbsd /vmx I tried to reboot my Cent OS client and at the boot loader when I select "Real VMX" I got the following error : "Error 1 : File name must be either an absolute pathname or blocklist" Can you please do me favor and let me know how can I overc...

...t (hd1,1) # kernel /vmlinuz-2.6.9-42.ELsmp ro root=LABEL=/ rhgb quiet # initrd /initrd-2.6.9-42.ELsmp.img #title CentOS-4 i386-up (2.6.9-42.EL) # root (hd1,1) # kernel /vmlinuz-2.6.9-42.EL ro root=LABEL=/ rhgb quiet # initrd /initrd-2.6.9-42.EL.img title XP SP2 rootnoverify (hd1,0) makeactive chainloader +1 And, finally... [root at seth ~]# cat /boot/grub/device.map # this device map was generated by anaconda (fd0) /dev/fd0 (hd0) /dev/hdb (hd1) /dev/sda Alls seems good but the problem stills there: no error messages, simply hangs... ?An...

...6.x86_64 ro root=/dev/mapper/vg_amrl01-lv_root rd_NO_LUKS LANG=en_US.UTF-8 rd_LVM_LV=vg_amrl01/lv_swap rd_NO_MD SYSFONT=latarcyrheb-sun16 crashkernel=128M KEYBOARDTYPE=pc KEYTABLE=us rd_LVM_LV=vg_amrl01/lv_root rd_NO_DM rhgb quiet initrd /initramfs-2.6.32-358.14.1.el6.x86_64.img title Windows 7 rootnoverify (hd1,0) chainloader +1 The system boots into CentOS just fine, but selecting the "Windows 7" entry results in invalid EFI file path Error 1: Filename must be either an absolute pathname or blocklist Press any key to continue... By my understanding, since grub is installed on...

...ystem loaded cleanly and gave me the opportunity to tell grub about the other system. CentOS boots fine. Grub Stage 2 will show me both systems. However, If I choose the FC7T2 system I get the following output: --------------------------------------------------------- Booting 'FC7T2' rootnoverify(hd0,0) chainloader +1 Error 13: Invalid or unsupported executable format --------------------------------------------------------- The CentOS grub.conf on /dev/hda5 looks like: #: cat /boot/grub/grub.conf # grub.conf generated by anaconda # # Note that you do not have to rerun grub after making c...

...kernel$ /boot/grub/unix -B install_media=192.168.20.57:/srv/pxeboot/opensolaris module /boot/grub/x86.microroot title OpenSolaris 2008.05 text console kernel$ /platform/i86pc/kernel/$ISADIR/unix -B livemode=text module /boot/x86.microroot title Boot from Hard Disk rootnoverify (hd0) chainloader +1 If someone has input in this manner, either how to use the mboot.c32 module, or what is wrong with my kernel line, help would be greatly appreciated. Knut Petter

Adding title Windows XP rootnoverify (hd0,1) chainloader +1 to /etc/grub.conf has always worked for me on every dual boot Win2k, XP, 2k3 / linux boxes I have ever built. Install Windows first then install Linux. You do not need a kernel that has NTFS support and you don't have to play with NTLDR. I know that this goes...

...tion to a primary, hda4. Then I ran "syslinux d:" from a Win98SE DOS-box to (try to) initialize the partition's boot record. And added this from a DOS/Windows example to grub.conf: title LEAF/Bering via syslinux hide (hd0,0) unhide (hd0,3) makeactive rootnoverify (hd0,3) chainloader +1 But the boot failed in grub. I'm also going the path of making grub boot LEAF-Bering directly, and I seem to have that part-way to working. Paul Rogers (paul.rogers at juno.com) http://www.xprt.net/~pgrogers/ http://www.angelfire.com/or/paulrogers/ Rogers'...

HI all, I had centos on a laptop (dual boot xp). I am giving the laptop to another person so I removed centos. Now when I reboot grub is confused... I tried to manually enter rootnoverify (hd0,0) makeactive chainloader +1 boot This does boot into XP but how do I tell grub that this is the new rules and do this everytime at boot. Thanks, Jerry

.../boot/vmlinuz-2.6.23.9-85.fc8 ro root=LABEL=/1 rhgb quiet initrd /boot/initrd-2.6.23.9-85.fc8.img title Fedora (2.6.23.1-42.fc8) root (hd0,2) kernel /boot/vmlinuz-2.6.23.1-42.fc8 ro root=LABEL=/1 rhgb quiet initrd /boot/initrd-2.6.23.1-42.fc8.img title Other rootnoverify (hd0,1) chainloader +1 [root@zadapi1L log]# df -h Filesystem Size Used Avail Use% Mounted on /dev/sda3 20G 3.0G 17G 16% / /dev/sda5 95G 211M 90G 1% /home tmpfs 470M 24K 470M 1% /dev/shm Again, any hints or pointers to doc...

...(hd0,5) kernel /vmlinuz-2.6.9-11.EL ro root=LABEL=/ rhgb quiet initrd /initrd-2.6.9-11.EL.img title Solaris 10 root (hd1,0) kernel /platform/i86pc/multiboot module /platform/i86pc/boot_archive makeactive chainloader +1 title Windows xp rootnoverify (hd0,0) chainloader +1 Note: This is my first post and I have learned a lot from your forum since I moved from mandrake 3 months ago. Thanks alot guys __________________________________________________ Do You Yahoo!? Tired of spam? Yahoo! Mail has the best spam protection around http...

I have one SATA drive with windows xp installed. I added a second SATA drive to install CentOS on. During the install, both drives are listed. If I use the auto-partition feature and deselect the drive with windows on it, only selecting the new drive, I get an error message that it could not create the partitions. The same thing happened a few months ago and I manually setup to partitions.

...l Linux (DSL) was downloaded an unzipped to the root of sdb5 (zip-file dsl-4.2.5-embedded) - sdb5 was made bootable by: syslinux -sf /dev/sdb5 (SYSLINUX version 3.63) - Now the USB flash drive is bootable - After reset, the grub prompt appeared, and I tried to boot from sdb5: root (hd0,5) rootnoverify (hd0,5) chainloader --force (hd0,5)+1 boot Boot error --- My question is, why there is the boot error? I've successfully tried the following: - Booting DSL from sdb1, sdb2, sdb3 without any problems -> OK. - Booting a 2nd GRUB, installed in the logical partition sdb5 -> OK. - Booting DSL...

...and swap space is on /dev/hda4 The details of grub file are: default=0 timeout=10 splashimage=(hd0,1)/grub/splash.xpm.gz title Red Hat Enterprise Linux WS (2.4.21-4.EL) root (hd0,1) kernel /vmlinuz-2.4.21-4.EL ro root=LABEL=/ initrd /initrd-2.4.21-4.EL.img title DOS rootnoverify (hd0,0) chainloader +1 title Xen 2.0 / XenLinux 2.6 root(hd0,1) kernel /xen-2.0.gz dom0_mem=131072 com1=115200,8n1 noht console=com1 module /vmlinuz-2.4-xen0 ro root=/dev/hda3 console=tty0 Can anyone advise me what is the source of problem? Make sure that the file...

...host xen-3.3.0]# make world [root@localhost xen-3.3.0]# make install [root@localhost xen-3.3.0]# depmod 2.6.18.8-xen [root@localhost xen-3.3.0]# mkinitrd initrd-2.6.18.8-xen.img 2.6.18.8-xen then i moved "initrd-2.6.18.8-xen.img" to /boot edited the grub.conf title WindowsXP rootnoverify (hd0,0) chainloader +1 title Fedora-base (2.6.23.1-42.fc8) root (hd0,5) kernel /vmlinuz-2.6.23.1-42.fc8 ro root=LABEL=/ rhgb quiet initrd /initrd-2.6.23.1-42.fc8.img title Fedora (2.6.21-2950.fc8xen) root (hd0,5) kernel /xen.gz-2.6.21-2950.fc8...

I've recently upgraded from RedHat 9 to CentOS 4.4. With RH9 I had a dual boot system with Windows XP (RH9 as the default of course!), which was automatically set up when I installed RH9 in the remaining partition after I'd installed XP. However, I appear to have lost my dual boot with CentOS 4.4 (no option to boot into DOS now), even though I still have the Windows XP partition, so how

...v/hda4 - extended /dev/hda5 - / for CentOS 5 The system loaded cleanly and gave me the opportunity to tell grub about the other system. CentOS boots fine. Grub Stage 2 will show me both systems. However, If I choose the FC7T2 system I get the following output: Booting 'FC7T2' rootnoverify(hd0,0) chainloader +1 Error 13: Invalid or unsupported executable format Any clues on how to fix this? Note, I am posting to both groups since I follow both and cannot figure out which is the better choice. Robert E. Styma Principal Engineer (DMTS) Alcatel-Lucent, Phoenix

...d0,2) kernel /vmlinuz-2.6.18-53.1.13.el5 ro root=LABEL=/ rhgb initrd /initrd-2.6.18-53.1.13.el5.img title CentOS (2.6.18-53.1.6.el5) root (hd0,2) kernel /vmlinuz-2.6.18-53.1.6.el5 ro root=LABEL=/ rhgb initrd /initrd-2.6.18-53.1.6.el5.img title Windoze rootnoverify (hd0,0) chainloader +1 with the following partition table (both Windoze and Linux on the same disk): [dave at spindle ~]# sudo fdisk -l /dev/hda Disk /dev/hda: 100.0 GB, 100030242816 bytes 255 heads, 63 sectors/track, 12161 cylinders Units = cylinders of 16065 * 512 = 8225280 bytes...

...machines work fine though. I reported this problem almost 2 years ago but no solution was found then. Use grub4dos v 0.4.1 - it is the most stable at the moment. Here is an example syslinux.cfg: default grub.exe --config-file="map --mem dosfloppy.gz (fd0); map --hook; chainloader (fd0)+1; rootnoverify (fd0); boot" Good luck, Quinn On 8/28/06, Uli Raich <Uli.Raich at cern.ch> wrote: > Hi all, > I try to boot an msdos system using pxelinux and memdisk on my PC > engines Wrap-2.c card and I have problems with it This is what I see: > PXELINUX 3.11 Debian-2006-03-16 Copyri...

Hello, I have a Dell 1850 with dual Xeon procs and two u320 36Gb drives. I would like to set this up as dual boot system with 4.2 on disk 0 and 3.6 on disk 1. I imagine that I would install 4.2 first and then 3.6. Would I need to remove the other hard drive while installing a given version? Any gotchas? How about setting up GRUB? Anything special or does the install take care of it? Thanks,