search for: hd1,0

I was able to get login prompt ( commit 7c62209cde5b13b81685e79b2f9e3757e293aef1 ) first time via serial console:- title Xen 3.4.1  Fedora 12 Serial (2.6.31-rc8 ) (/dev/sdb1)   root (hd1,0)   kernel /xen-3.4.1.gz dom0_mem=1024M loglvl=all guest_loglvl=all com1=19200,8n1 console=com1   module /vmlinuz-2.6.31-rc8 ro root=/dev/mapper/vg_fdr12-lv_root console=hvc0 earlyprintk=xen   module /initrd-2.6.31-rc8.img Then disconnected NUL modem cable and loaded Dom0 via : title Xen 3.4.1 ...

Hi all! Doing some tests with CentOS 5.5 on a KVM virtual machine, after doing the installation, I added a second disk. But when trying to boot from it, I get the following error: --------------------------------------------------------------------- root (hd1,0) Error 21: Selected disk does not exist --------------------------------------------------------------------- The two disks are Virtio devices that are recognized when booting from the first disk: --------------------------------------------------------------------- [root at localhost ~]# fdi...

...~]# -------------- next part -------------- # 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. # root (hd1,0) # kernel /boot/vmlinuz-version ro root=/dev/sda1 # initrd /boot/initrd-[generic-]version.img #boot=/dev/sdb default=0 timeout=5 splashimage=(hd1,0)/boot/grub/splash.xpm.gz hiddenmenu title CentOS (2.6.32-220.17.1.el6.i686) root (hd1,0) kernel /boot/vmlinuz-2.6.32-220.17.1.el6...

...GIN PGP SIGNED MESSAGE----- Hash: SHA1 Hi all! Doing some tests with CentOS 5.5 on a KVM virtual machine, after doing the installation, I added a second disk. But when trying to boot from it, I get the following error: - --------------------------------------------------------------------- root (hd1,0) Error 21: Selected disk does not exist - --------------------------------------------------------------------- The two disks are Virtio devices that are recognized when booting from the first disk: - --------------------------------------------------------------------- [root at localhost ~]#...

...ot=/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 sdb,...

...d... [root at seth ~]# cat /boot/grub/menu.lst # grub.conf generated by anaconda # # Note that you do not have to rerun grub after making changes to this file # NOTICE: You have a /boot partition. This means that # all kernel and initrd paths are relative to /boot/, eg. # root (hd1,1) # kernel /vmlinuz-version ro root=/dev/sda3 # initrd /initrd-version.img #boot=/dev/hdb default=1 timeout=5 splashimage=(hd1,1)/grub/splash.xpm.gz hiddenmenu title CentOS (2.6.9-42.0.3.EL) root (hd1,1) kernel /vmlinuz-2.6.9-42.0.3.EL ro root=LABEL=/ rhgb quiet...

...ed the server it was running with LVM on single disk (sda) I managed to remove LVM and install raid 1 in sda and sdb disks the mirroring is working fine, my only issue now is that everytime I reboot the server I got the grub command line and I have manually boot using comand grub> configfile (hd1,0)/grub/grub.conf OR grub> configfile (hd0,0)/grub/grub.conf then it will boot fine without any error. Any idea how can I make it auto boot ? I tried almost everything I can find in the internet. Note: each disk (sda & sdb) is 2TB size, could this be the problem? . # df -h Filesyst...

I have been trying to multiboot centos 4.1 and the current solaris express build 15. I have two hard drive s, the first one ( hd0 ) devoted to CentOS 4.1 and windows xp (no problems). The second drive (hd1) for Solaris 10 only. I tried to boot solaris from CentOS grub and got the following error messages: Booting Solaris 10 root(hd1,0) Filesystem type unknown, partition type 0Xbf kernel /platform/i86pc/multiboot Error 17: can not mount selected partition press any key to continue.... I googled f...

I have a p4 motherboard with 2 ide interfaces, I connect 2 40 GB drives as hda and hdc, I install Centos 4 from a CDROM, and partition the drives as 2 x raid partition each plus a swap partition on hda, the make md0 and md1 to install /boot and / respectively. Install goes well, everything looks great, go to reboot from drives, and all I get is "grub" but no boot. I have tried this ten

...mnt/rescue # mount /dev/md0 /mnt/rescue/boot # mount -o bind /dev /mnt/rescue/dev # mount -o bind /proc /mnt/rescue/proc # mount -o bind /dev/shm /mnt/rescue/dev/shm # mount -o bind /sys /mnt/rescue/sys # chroot /mnt/rescue *I checked the device.map* # cat /boot/grub/device.map (hd0) /dev/sda (hd1) /dev/sdb *And, install the grub.* # grub Probing devices to guess BIOS drives. This may take a long time. GNU GRUB version 0.97 (640K lower / 3072K upper memory) [ Minimal BASH-like line editing is supported. For the first word, TAB lists possible command completions. Anywhere...

...the server will still be available. i installed grub on /dev/sda using the advanced grub configuration option during the install. after the install is done i boot in linux rescue mode , chroot the filesystem and copy grub to both drives using: grub>root (hd0,0) grub>setup (hd0) grub>root (hd1,0 grub>setup (hd1) grub>quit then reboot, but is still get the error : disk boot faillure, insert linux install disk. does anyone now what i'm doing wrong? here is a copy of my partition scheme. Disk /dev/sda: 251.0 GB, 251000193024 bytes 255 heads, 63 sectors/track, 30515 cylinders Uni...

...I perform a software RAID 1 or RAID 5 installation on a LAN server with several hard disks, I wonder if GRUB already gets installed on each individual MBR, or if I have to do that manually. On CentOS 5.x and 6.x, this had to be done like this: # grub grub> device (hd0) /dev/sda grub> device (hd1) /dev/sdb grub> root (hd0,0) grub> setup (hd0) grub> root (hd1,0) grub> setup (hd1) grub> quit I'd like my server to be able to boot a degraded software RAID after an eventual hard disk failure. Any suggestions? Niki Kovacs -- Microlinux - Solutions informatiques durables 7,...

I have a system that is RAID -1 configured as /dev/md0 is /dev/hda1 /dev/hdb1 /dev/md1 is /dev/hdb3 /dev/hdb3 it seems as though /dev/hda has failed.... I have another disk (identical model) that I can replace hda with. I know about the commands fdisk to repartion and raidhotadd /dev/md0 /dev/hda1 and raidhotadd /dev/md1 /dev/hda3 (to be ran after the system boots). BUT... how do I now get

Unclear on how to recover from failed boot drive? SDA has failed but I'm still able to boot. I need to replace primary boot drive. Upon initial build I created a RAID 1 mirror of /boot dir/partition. How do I get system to boot off second or third drive so that I can replace /sda? I've successfully replaced /sdb & sdc raid 5 drives in the past but have always struggled to get primary

...ut: ... When I pull out the other pendrive [i plug in the first one i tried] it say's: GRUB hard disk error What can I do? I already tried: grub-install /dev/sdc <-that's the pendrive name [bios -> hard drive emulation=hard drive, not auto] or: # grub find /boot/grub/stage1 hd0,0 hd1,0 root (hd0,0) setup (hd0,0) etc. What's the solution? Please help me:\ I can't just dd the first 512 Byte of the "good pendrive", because the uuid is stored there. [needed for the sraid..] It gets to the grub, so it's not a ""boot-order problem"" How...

I must have really shot myself in the foot on this one. I reinstalled CentOS 4.4 (have to, for now) on my test machine, exactly the way it was before (same options anyway), but when it comes up, I get: Booting 'CentOS-4 x86_64 (2.6.9-42.ELsmp)' root(hd1,0) Filesystem type is ext2fs, partition type 0x83 kernel /vmlinuz-2.6.9-42.ELsmp ro root=LABEL=/ rhgb quiet Error 15: File not found Press any key to continue... If I press any key, I get a garbled screen that is nearly impossible to read. So, I rebooted from the DVD in rescue mode, ran fdisk...

...g if "/boot/grub/e2fs_stage1_5" exists... yes Running "embed /boot/grub/e2fs_stage1_5 (hd0)"... 16 sectors are embedded. succeeded Running "install /boot/grub/stage1 (hd0) (hd0)1+16 p (hd0,0)/boot/grub/stage2 /boot/grub/grub.conf"... succeeded Done. #grub> root (hd1,0) Filesystem type is ext2fs, partition type 0xfd #grub> setup (hd1) Checking if "/boot/grub/stage1" exists... yes Checking if "/boot/grub/stage2" exists... yes Checking if "/boot/grub/e2fs_stage1_5" exists... yes Running "embed /boot/grub/e2fs_stage1_5 (...

Hi, I'm installing CentOS 4.4 64 bits with RAID 1 per software. But when the installation finishes, i cannot boot the system. I always get GRUB error 15. Any ideas ? Thanks in advance. Warm Regards, M?rio Gamito -------------- next part -------------- An HTML attachment was scrubbed... URL: <http://lists.centos.org/pipermail/centos/attachments/20070228/9c237e08/attachment.html>

...4.0) Unknown boot option `pciback.hide=(09:04.0)': ignoring I also tried to update initrd to include the module but got the same error message as above. mkinitrd --with=pciback /boot/initrd-2.6.18-164.6.1.el5xen_pcipt 2.6.18-164.6.1.el5xen title CentOS (2.6.18-164.6.1.el5xen PCI PT) root (hd1,0) kernel /xen.gz-2.6.18-164.6.1.el5 module /vmlinuz-2.6.18-164.6.1.el5xen ro root=/dev/dom0/root pciback.hide=(09:04.0) module /boot/initrd-2.6.18-164.6.1.el5xen_pcipt Is there any option to use pciback.hide kernel parameter without compiling a custom kernel? Thanks in advance G?nter...

...ev/md0 (hda1 + hdb1) /boot /dev/md1 (hda2 + hdb2) / /dev/md2 (hda3 + hdb3) swap done with disk druid during initial setup from server disk, so far so good. Then I installed grub to hdb. grub-install complained all the time (I may have given it the wrong parameter), so I used grub directly: root (hd1,0) setup (hd1) That's correct, isn't it? (Is there a way to determine if grub is installed on the correct disk?) I added a third boot entry to the grub.conf (see below). I then removed disk 1 (hda) from the array by unpowering it and rebooted. Unfortunately, that sent me right in the BIO...